Lync: Set up a SIP trunk with Avaya IP Office R9

Over the past 12 months, I have learned to set up and manage a Lync 2013 environment and completed a complex migration from OCS 2007 R1. This post starts a series about the challenges and what I have learned.

PSTN connectivity was one of my first goals after getting the Lync 2013 Standard Edition pool running. Last week, I established a SIP trunk between Avaya IP Office and Lync.

The most important prerequisite is the latest IP Office firmware. I am running R9 on an IP Office 500v2. I could not find a guide covering the whole SIP trunk setup, so I am documenting the configuration that worked for me.

My objectives

• Establish a direct SIP path without an additional proxy.
• Forward a PSTN extension to Lync so the conference bridge can be reached externally.
• Allow Lync users to dial the PSTN.
• Allow IP Office users to reach a Lync extension.

My environment

• Lync 2013 Standard Edition server running as a VM
• Lync 2013 Edge server running as a VM (not needed for the SIP trunk)
• Managed IP VPN network with classes of service for QoS
• No firewall between IP Office and the Lync front-end server
• Avaya IP Office 500v2 with R9 firmware
• SIP trunking license for 10 channels
• A Lync-enabled user with Enterprise Voice

Before starting, configure the Mediation Server to listen on TCP port 5060. I also had to adjust Windows Firewall because the port was not enabled by default.

Step 1: Configure IP Office

Firmware and licensing

My IP Office 500v2 runs firmware 9.0.3.16 build 2.

A SIP Trunk Channel license is required. I have ten channels.

Enable SIP trunks

Select SIP Trunks Enable in the system configuration.

System / LAN1 / VoIP
SIP Trunks Enable: checked

Create a SIP line

I created SIP line 18.

1
2
3
4

ITSP Domain: Networknet.nl
National Prefix: empty
International Prefix: empty
Check OOS: unchecked

Keep the other options at their defaults when creating the line.

Configure SIP transport

1
2
3
4

ITSP Proxy Address: 192.168.200.9 (IP address of the Lync Mediation server)
Layer 4 Protocol: TCP
Send Port: 5060
Listen Port: 5060

SIP URI: Channel 1

1
2
3
4
5
6
7

Local URI: *
Contact: *
Display Name: *
PAI: None
Registration: 0: <None>
Incoming Group: 1
Outgoing Group: 18

SIP URI: Channel 2

1
2
3
4
5
6
7

Local URI: Use Internal Data
Contact: Use Internal Data
Display Name: Use Internal Data
PAI: None
Registration: 0: <None>
Incoming Group: 0
Outgoing Group: 21

Select the VoIP codec

Select the custom G.711 ALAW 64K codec. This completes the SIP line configuration.

Create an ASR route

URIs containing Networknet.nl use the Dial feature and line group 21, the outgoing group for the SIP trunk to Lync.

1
2
3
4

Code: N;
Telephone Number: N"@networknet.nl"
Feature: Dial
Line Group ID: 21

Create a short code for calls to Lync

A short code is needed to reach Enterprise Voice users or a dial-in access number. I send this traffic through ASR group 54.

1
2
3
4

Code: *5962XXX (*LYNCEXTENSION)
Feature: Dial
Telephone Number: N
Line Group ID: 54: Lync

This completes the main IP Office configuration. I also added ASR codes to the main route:

Calling numbers arriving from Lync at IP Office had two additional zeros (00). I removed these in the main ASR route, avoiding further IP Office configuration.

Step 2: Configure Lync Server

Configure TCP port 5060 on the Lync Mediation Server.

Next, create a PSTN gateway for IP Office in Lync Topology Builder.

Create the IP/PSTN gateway

FQDN: ipo.networknet.local

Make sure IP Office has a host A record in DNS.

Enable IPv4

1
2
3
4
5

Trunk name: ipo.networknet.local
Listening port of IP/PSTN gateway: 5060
SIP Transport Protocol: TCP
Associated Mediation Server: Lync-01.Networknet.Local
Associated Mediation Server port: 5060

With the SIP trunk created, I updated the Lync topology so it was ready to publish.

Configure voice routing

During Microsoft Lync Enterprise Voice training a few months ago, I learned about Lync Optimizer. It provides dialing rules for 80 countries for Lync Server 2010/2013. This gave me a working voice-routing configuration and helped me understand how voice policies fit together.

I ran the script on my Lync server, selected the Networknet site and created a user-level dial plan.

After the script finished, I refreshed Lync Control Panel. A new dial plan and the normalization rules for calls to the +31 PSTN network had been created.

This saved a lot of work and worked immediately in my environment, without further troubleshooting on the Lync server.

The script associated the IP Office trunk with a route. The screenshot shows the +316 pattern for the mobile network.

After running the voice-routing test, I could confirm that everything was configured.

I then called out from my Lync client through the new SIP trunk, and my mobile phone rang.

The screenshot uses an example mobile number; I tested with my own number.

I also used Test-CsPstnOutboundCall to check PSTN connectivity:

1

Test-CsPstnOutboundCall -TargetFqdn lync-01.networknet.local -UserSipAddress sip:sip@networknet.nl -TargetPstnPhoneNumber "+31612345678"

The result was Success, and my mobile phone rang.

In later posts, I will cover the dial-in conferencing bridge and troubleshooting SIP communication between IP Office and Lync. The IP Office Monitor tool helped me understand why some calls failed. Each environment has its own Lync and IP Office settings, so compare the logs for working calls with what happens when a call fails.