Lync and Avaya IPO integration

Greetings reader! I want to highlight today the issue of sharing MS Lync Server 2010 and external telephony. As the name implies, the example of Avaya IPO. In fact, the specific model of PBX does not matter. It works with everything, including Asterisk, about the integration of which on the Internet is written a lot. With some equipment, Lync can work using the Direct SIP protocol (for example, with CUCM).

For a long time I will not describe the front of the needs that such integration can solve. There are many of them and they do not affect the essence of the process much. In my case, this was done so that users could use the internal telephony and participate in newsgroups from outside the office. That is, in this particular application, it is Lync that complements Avaya, and not vice versa. IPO provides telephony and communication.

So the disposition:
The office is Avaya IPO406v2 (numbers 5xx). Phones are used analog (Panasonic-and mostly cheap), digital (branded devices Avaya) and all sorts of hardware SIP-phones (the zoo in general). The network has Lync 2010 Standart (numbers 4xxx), which was used mainly by remote employees to communicate with the office. The EDGE server is viewed from the Lync on the Internet, and remote employees go outside through it.
')
The challenge in general is to ensure that Lync and Avaya can transmit voice to each other.

Well ... Let's proceed directly to the setting.

Let's start with Lync Server.

First you need to turn on the Mediation server. If the server is standard, then simply enable the Collocated Mediation Server directly on the Front-End server. If the version of Lync is Enterprise, you will have to install a separate server with the role of Mediation. We have a standard, therefore, consider it.




At this stage, the list of gateways will be empty (if not added in advance).
You need to add a PSTN gateway.
When adding a gateway, the system will ask us for the IP address of the gateway, in our case of PBXs. Interaction port and protocol. Protocol select TCP, and port 5060.
By the way, Lync server can work with several gateways at the same time through one Mediation server, unlike OCS.

Then in the place where we enabled Mediation to add a gateway.

After that, publish the topology and start the server Mediation service. In idel, it is better to restart Lync, but this is not necessary.

The next step is to configure the PBX.

Create a SIP Line.

For this line, configure the SIP URI

Well, the codec too. Lync understands only G.711. And although the auto-negotiation of codecs by the PBX selects the correct codec, some kind of subtle glitches still occurred. Therefore it was necessary to specify it forcibly.

Call Routing

From the PBX

It is better to route calls using ARS, but for my specific needs it is redundant, therefore I made a simple Short Code.

This is where Avaya IPO setup ends.

On the Lync side

In this place it is worth making a small lyrical digression:
All users will be able to receive calls from PBX to Lync, however, only those who have Enterprise Voice enabled (for this you need an Enterprise CAL) can call outside.
Plus, in order for the PBX to call the Lync user, all users need to distribute phone numbers. In my cases, I made them 4-digit to visually separate from internal numbers.
Something like this:


Next Dial Plan. Go to Voice Routing on the Lync control panel.
By default, there is a global dial plan. If there is no need to distribute different plans to different users, then you can get by just editing this. Plans themselves (as well as politicians) come in three levels. Global, site level and user level. Priority is inversely proportional to the coverage area.

Create normalization rules.

If someone is friends with regular expressions, you can not use the wizard.

Specifically, I need three rules:

• For calls to PBX. ^ (5 \ d {2}) $
• For calls outside. ^ (\ d {11}) $
• For internal calls. ^ (4 \ d {3}) $

Next, the Voice Policy:
There is also a global default policy here. You can edit it.

Create PSTN Usage:

As part of the PSTN Usage create a route. That is, the link of the type of pattern numbers <-> gateway. As I already upiminal above, you can use multiple gateways for routing.


We repeat this procedure for all three directions.

At each stage, it is possible to test the correctness of the rules entered. You can also create permanent tests, and at each stage of the setup see what stage the call will take at the moment.




Actually after this, you can restart the Survey Mediation service and it will work.
Users with Enterprise Voice enabled in Lync will receive a new dialing mode and redirection settings. If the user settings include internal or mobile numbers, you can call them directly from the contact list.

From the phone is still easier. Just dial the Lync user number and that's it. The names and numbers of the callers are transmitted normally, the Cyrillic is also well understood (if the phone itself understands of course).


PS The configuration process itself is not complicated and clear. However, when you come across this for the first time, it’s not quite clear where to start and where to harness horses at all. In this “instruction”, on a simplest example, I wanted to show the principle of the organization of interaction between Lync and the outside world. I hope the principles are clear and based on them you can understand how to set up a more complex interaction.