microsoftdownload.microsoft.com/.../integrating_lync_server_an… · web viewconfigure static route...

Integrating Microsoft Lync Server 2010 and Avaya Communications Manager S8300

Microsoft Lync Server 2010

Published: April 2011

Authors: Rui Maximo with technical assistance from Nandita Sharma and Mark King

Abstract: If you want to integrate an Avaya S8300 Communications Manager with the Microsoft® Lync™ Server 2010 communications software, you need to establish a Direct SIP connection between the two. This document provides a step-by-step guide for configuring Avaya Communications Manager S8300 with Lync Server 2010.

This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice.

Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.

This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.

© 2011 Microsoft. All rights reserved.

ContentsIntegrating Microsoft Lync Server and Avaya Communications Manager 1

Configure Avaya Communications Manager...............................................................................................2

Configure Call Routing between Avaya Communications Manager and SES 3

Create Signaling Group........................................................................................................................3

Create Trunk Group.............................................................................................................................4

Define Route Pattern...........................................................................................................................5

Configure Dial Plans 5

Configure Avaya SIP Enablement Services...................................................................................................6

Configure Static Route to Lync Server 6

Configure static route to Avaya Communications Manager 9

Configure Lync Server................................................................................................................................10

Adding Avaya SES as a gateway to the Lync Server Topology 10

Define Dial Plan 12

Create Voice Policy 12

Define Trunk Configuration 15

Additional Resources.................................................................................................................................15

Appendix...................................................................................................................................................16

Configure Call Routing between Avaya Communications Manager and the Branch Site SES 16

Create Signaling Group......................................................................................................................16

Create Trunk Group...........................................................................................................................16

Configure Avaya SES at each Branch Site...................................................................................................17

Configure Lync Server to use Branch Site SES............................................................................................17

Adding Branch Site SES as a Gateway to the Lync Topology 17

Integrating Microsoft Lync Server and Avaya Communications ManagerMicrosoft® Lync Server™ 2010 communications software can interoperate with Avaya Communications Manager 4.0.

In this article, Avaya Communications Manager is running on an Avaya S8300 Media Server with an Avaya G350 Media Gateway. The Avaya G350 Media Gateway provides the physical interfaces and resources for Communications Manager. This just happens to be the hardware in our lab, but if you have other versions that you are interested in configuring for Direct SIP with Lync Server 2010, please contact me. We would like to partner with you to author an article on the NextHop blog. For details about the NextHop blog, see http://go.microsoft.com/fwlink/?LinkId=203149.

According to the Avaya support site at http://www.avaya.com/usa/product/servers#S8300 Server, the Avaya S8300 Media Server (shown in Figure 1) resides inside an Avaya G700, G450, G350, or G250 Media Gateway. You can use it as a stand-alone communication system or as a fully survivable remote gateway. The Avaya S8300 Media Server can be the primary controller for up to 50 remote Avaya G250, G350, G450, and G700 Media Gateways.

Figure 1 Avaya S8300

For Avaya Communications Manager to interoperate with Lync Server by using direct SIP, you need to use Avaya SIP Enablement Services (SES) as an interface between the Avaya infrastructure and the Lync Server infrastructure. In SES, SIP trunks are used to connect Communications Manager and Lync Server 2010. Avaya SIP Enablement Services provides core SIP routing and integration services that enable communications between Avaya Communications Manager and the Lync Server Mediation Server. The version of SIP Enablement Services used in our lab is 4.0.0.0-033.6. This Direct SIP topology is illustrated in Figure 2.

1

http://www.avaya.com/usa/product/servers%23S8300%20Server

http://go.microsoft.com/fwlink/?LinkId=203149

Figure 2 Direct SIP topology

This topology requires that you perform the following configuration steps:

1. Configure Avaya Communications Manager 4.0 on an Avaya S8300 Media Gateway.2. Configure Avaya SIP Enablement Services 4.0.0.0-033.6.3. Configure Lync Server 2010.

Before we jump in, a quick point: This configuration involves making changes to your IP-PBX, changes that we recommend be performed by someone with experience in your environment. Although we don’t anticipate any of these changes having an impact on your production system, you should still take any necessary steps to back up your configuration before you begin and edit where appropriate for your environment. Microsoft makes no warranties, express or implied, on this content, and you proceed at your own risk.

Configure Avaya Communications ManagerThe steps to configure Avaya Communications Manager are as follows:

1. Configure call routing between Avaya Communications Manager and SES.2. Configure call routing between Lync Server and SES.3. Configure dial plans to route calls between Avaya Communications Manager and Lync Server.

The rest of this section describes these steps in detail. The Avaya Communications Manager commands described in this section were administered by using the System Access Terminal (SAT). To access the SAT command line interface, use Secure Shell (SSH) or Telnet to connect to the Communications Manager. Open a command prompt window. At the command prompt, type SAT, and then press Enter.

2

Integrating Microsoft Lync Server and Avaya Communications Manager

Configure Call Routing between Avaya Communications Manager and SESThis section describes the configuration steps required on Avaya Communications Manager for routing calls between Communications Manager and SES. The steps are as follows:

1. Create signaling group.2. Create trunk group.3. Define route pattern.

Create Signaling GroupTo create a signaling group between Avaya Communications Manager and SES, perform the following steps:

1. At the SAT command prompt, type: add signaling-group <group-number> where <group-number> is an integer between 1 and 772 (for example, Figure 3 shows “signaling-group 1”).

2. In Group Type, type: sip 3. In Transport Method, accept the default, which is tls.4. In Near-end Node Name, type the display name of your Avaya Communications Manager (for

example, “avayacm”).5. In Far-end Node Name, type the display name of your SES (for example, “avayaSES”).6. In both Near-end Listen Port and Far-end Listen Port, accept the default port, which is 5061. 7. In Alternate Route Timer, type: 308. In Far-end Domain, type the fully qualified domain name (FQDN) of the Mediation Server or

Mediation pool that you want the SIP trunk to point to. Although optional, this configuration is recommended if you plan to have multiple Avaya Communications Manager-to-SES trunks as shown in the Appendix of this document.

9. To submit changes, press Enter.

Figure 3 illustrates these configuration settings.

Figure 3 Create Signaling group between Avaya Communications Manager and SES

3


Create Trunk GroupThe next step is to define a Trunk group that is associated with the signaling group that you created as follows:

1. At the SAT command prompt, type: add trunk-group <trunk-number> where <trunk-number> is an integer between 1 and 772 (for example, Figure 4 shows “trunk-group 2”).

2. On page 1, in Group Type, type: sip3. In Group Name, type a descriptive name for the connection between the Avaya

Communications Manager and SES (for example, “SESMainOffice”).4. In Service Type, type: tie 5. In Signaling Group, type the group number that you specified in the procedure to create a

Signaling Group (for example, Figure 3 used “signaling-group 1”).


Figure 4 Trunk group associated with Signaling group previously created

6. On page 4, in Mark Users as Phone, type: y7. In Prepend ‘+’ to Calling Number, type: y8. In Send Transferring Party Information, type: y

Figure 5 illustrates these configuration changes.

Figure 5 Trunk group configuration

9. On page 5, configure the number of channels you want between Communications Manager and SES.

10. To submit changes, press Enter.

4


Define Route PatternThe following step associates a route pattern with the Trunk group that you created:

1. At the SAT command prompt, type: change route-pattern <route-number> where <route-number> is an unused route pattern.

2. In Grp No, type the <trunk-number> that you specified in step 1 of the “Create Trunk Group” procedure (for example, Figure 6 shows “Grp No 2”, which corresponds to “trunk-group 2”as shown in Figure 4).

3. In Pfx Mrk, type: 14. In the FRL box, type: 0

Note: The 0 (zero) setting is the least restrictive Facility Restriction Level. 5. To submit changes, press Enter.


Figure 6 Route Pattern associated with Trunk group

Configure Dial PlansNow that you have created a route pattern between the Avaya Communications Manager and SES, you need to define a dial plan associated with the route pattern.

1. At the SAT command prompt, type: change ars analysis <number> where <number> is a unique integer between 0 and 999.

2. In Dialed String, enter the leading digits that you will define in phone numbers for Enterprise Voice users, conference dial-in numbers, and Response Groups numbers.

3. In both Min and Max, enter the value 11. This represents the number of digits to expect, which is the number of digits in an E.164 phone number.

4. In Route Pattern, enter the route pattern number defined in step 1 in the “Define Route Pattern” procedure (see Figure 6).

Figure 7 ARS Digit Analysis Table

5


Use the SAT command-line interface to define or modify existing dial plans. For dial plans that are associated with the route pattern that you defined between Avaya Communications Manager and SES, SES will route calls originating from Lync Server that match this dialed string to the Avaya Communications Manager.

To view available dial plans, at the SAT command prompt type: display dialplan analysis

Configure Avaya SIP Enablement ServicesTo configure Avaya SIP Enablement Services (SES), perform the following steps:

1. Configure a static route to Lync Server Mediation Server or Front End Server.2. Configure a static route to Avaya Communications Manager.

The rest of this section provides detailed procedures for the steps.

Configure Static Route to Lync Server1. From your browser, open the SES web interface: In the address box, type http://<SES IP

address>.2. Click the Administration Web Interface link.3. In the console tree, expand Hosts, and then click List.4. In the details pane, click Map.

6


5. Click Add Another Map.

6. In Add Host Address Map, define an outbound phone number regular expression pattern from Avaya to Lync Server by specifying the following:

In Name, type a descriptive name of your choice, such as “Outbound to Lync Server”. In Pattern, type a phone number regular expression (referred to by Avaya as a called

number string). This regular expression pattern must begin with the string ‘^sip:+<regular expression>’. For example, the pattern, ‘^sip:+12065[0-9]{6}’, matches any phone numbers that start with ‘+12065’ followed by 6 digits between 0 and 9, such as 1-206-544-1212.

If Replace URI is not selected, select it now.

7. To add the host address map, click Add.8. To return to the List Host Address Map page, click Continue.

7


9. Click Add Another Contact.

10. In Add Host Contact, specify the IP address or FQDN, port and transport type of the Lync Server 2010, Mediation Server in the Contact field in the format, ‘sip:+$(user)@<Mediation Server IP or FQDN>:5068;transport=tcp’. The plus sign is required to format phone number in E.164 format. The port number of the Mediation Server is 5068, and the transport type is TCP.

Note: This guide doesn’t explain how to configure TLS between Avaya and Lync Server.

11. Click Continue.

8


12. On the List Hosts page, click Update All.

Configure static route to Avaya Communications Manager1. From your browser, open the SES web interface from your browser: In the address box, type

http://<SES IP address>.2. Click the Administration Web Interface link.3. In the console tree, expand Media Servers, and then click List.4. Click Add, and then click Continue.

9


5. In the console tree, expand Media Servers, and then click List.6. Click Map, and then click Add Map In New Group. 7. In Media Server Address Map, do the following:

In Name, type a meaningful string, such as “Inbound_call_from_Lync_to_AvayaCM”, to indicate the direction of the call.

In Pattern, type a regular expression (referred to by Avaya as a called number string) to match on the pattern of incoming calls. A phone number matching the regular expression will be routed to the Avaya Communications Manager. This pattern must begin with the string ‘^sip:<regular expression>’. For example, the pattern, ‘^sip:9[0-9]{10}’, matches any phone numbers that start with ‘9’ followed by 7 digits between 0 and 9, such as 9-425-555-1212.

8. Click Add, and then click Continue.

Configure Lync ServerTo complete the Direct SIP configuration with Avaya Communications Manager, perform the following steps:

1. Add Avaya SES as a gateway to the Lync Server topology.2. Define dial plan by configuring normalization rules.3. Create a voice policy.4. Define a trunk configuration.5. Assign the voice policy that you created to Lync users.

10


Adding Avaya SES as a gateway to the Lync Server Topology1. Log on as a member of the Domain Admins group or the RTCUniversalServerAdmins group to a

computer that has Topology Builder installed.2. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2010, and then

click Lync Server Topology Builder. 3. Expand the Mediation pools node. 4. Right-click the Mediation pool, and then click Edit Properties.

5. If the Avaya SES is not already published as a gateway in your Lync Server topology, click New.6. In the Define New IP/PSTN Gateway dialog box, do the following:

In Gateway FQDN or IP Address, specify the IP address of the Avaya SES. In Listening port for IP/PSTN gateway, set the port to 5060. Under Sip Transport Protocol, click TCP.

11


7. Click OK, and then click OK again.8. To publish your change to the Lync Server topology, in the Actions panel of the Topology

Builder, point to Topology, and then click Publish.

Define Dial PlanTo define dial plan rules in your Lync Server topology, use the Lync Server Control Panel.

12


1. From a user account that is assigned to the CsAdministrator role or other role that has appropriate user rights and permissions for the task to be performed, log on to any computer in your internal deployment.

2. Start Lync Server Control Panel: Open a browser window, and then enter the Admin URL provided by your organization.

3. Click Voice Routing, and then click the Dial Plan tab.4. Create normalization rules specific to your environment so that Lync users can dial Avaya

phones and the PSTN (that is, if you are using Avaya Communications Manager to connect to the PSTN). Contact your local Microsoft field engineer for assistance in engineering your dial plans as necessary.

5. To commit your changes, click Commit, and then click Commit all.

Create Voice PolicyThe voice policy that you create will later be assigned to users. Users assigned this voice policy will be able to dial out through the Direct SIP connection to the Avaya system.



3. Click Voice Routing, and then click the Voice Policy tab.

13


4. Click New, and depending on the scope of the policy you want to create, click Site Policy or User Policy.

5. Specify a unique name for this voice policy, and provide a meaningful description.6. To create a new PSTN usage for this policy, click New.

7. Specify a unique name for the new PSTN usage record. The name must be unique to this specific voice policy. Also, provide a detailed description of the PSTN usage record.

8. To associate a route with this PSTN usage, click New.

14


9. Specify a name for this route, and provide a meaningful description.10. To associate the Avaya SES gateway with this new route, click New.

15


11. Select the Avaya SES gateway that you created earlier.12. Click OK in four different dialog boxes to complete the creation of the voice policy.13. To commit your changes, click Commit, and then click Commit all.

16


Define Trunk ConfigurationThe next step is to assign the Avaya SES gateway to a trunk associated with a pool or a site as follows:



3. Click Voice Routing, and then click the Trunk Configuration tab. 4. Click New, and depending on the scope of the policy you want to create, click Site Configuration

or Pool Configuration. For example, if you are creating a site policy, click Site Configuration.

5. Select a pool or site for this trunk configuration.6. In the New Trunk Configuration dialog box, click OK. 7. To commit your changes, click Commit, and then click Commit all.

Important: Do not forget to associate the Avaya voice policy with the users who will dial out to Avaya phones and the PSTN. For details about associating a voice policy with specific users, see “Enable Users for Enterprise Voice ” at http://go.microsoft.com/fwlink/?LinkId=212817 on the Microsoft TechNet website.

Additional Resources Avaya S8300 Server at http://support.avaya.com/css/Products/P0068 Avaya Application Notes for Configuring Alternate Methods of Domain Based Routing for Outbound

SIP Calls with the Avaya SIP Trunk Architecture at https://devconnect.avaya.com/public/download/interop/Alternate_DBR.pdf

Office Communications Server 2007 R2 interop with Avaya Aura Communications Manager at https://devconnect.avaya.com/public/download/interop/OCSR2-SM-CM.pdf

Avaya G350 Media Gateway CLI Reference at http://www.jaymzworld.com/w/images/d/de/G350_cli_ref.pdf

Avaya SES Guide at http://www.jaymzworld.com/wiki/HowTo:_Quickstart_on_SIP_Enablement_Services

17

http://www.jaymzworld.com/wiki/HowTo:_Quickstart_on_SIP_Enablement_Services

http://www.jaymzworld.com/w/images/d/de/G350_cli_ref.pdf

https://devconnect.avaya.com/public/download/interop/OCSR2-SM-CM.pdf

https://devconnect.avaya.com/public/download/interop/Alternate_DBR.pdf

http://support.avaya.com/css/Products/P0068





Avaya Troubleshooting at http://www.jaymzworld.com/w/images/4/40/Troubleshooting_SES.pdf

AppendixTypically, with enterprise deployments of Microsoft Lync Server and Avaya you have multiple sites that have servers running Avaya SIP Enablement Services and Lync Server deployed at each site. An example of this type of environment would be a branch site with a Lync Server Survivable Branch Appliance or Survivable Branch Server deployed. This environment would require the following configuration:

1. Configure Call Routing between Avaya Communications Manager and the branch site SES.2. Configure Avaya SES at each branch site. 3. Configure the Lync Server Survivable Branch Appliance or Survivable Branch Server with the

corresponding SES at each site.

Configure Call Routing between Avaya Communications Manager and the Branch Site SESTo configure call routing between Avaya Communications Manager and the branch site SES, complete the same effort completed previously with slight modifications. We will create an additional signaling group, trunk group and route pattern, this time with a different set of extensions and signaling target on the branch site SES.

Create Signaling GroupTo create a signaling group between Avaya Communications Manager and SES in each branch site, follow the same steps in the “Create Signaling Group” section, under Configure Call Routing between Avaya CM and SES with the following change.

1. In Far-end Node Name, type the display name of your branch site SES (for example, “Branch1SES”).

2. In Far-end Domain, type the FQDN of the branch site Survivable Branch Appliance or Survivable Branch Server that you want the SIP trunk to point to.

Create Trunk GroupThe next step is to define a Trunk group that is associated with the signaling group we just created. Follow the same steps in the “Create Trunk Group” section, under Configure Call Routing between Avaya CM and SES with the following changes.

1. In Group Name, enter a descriptive name for the connection between the Avaya Communications Manager and SES (for example, “Branch1SES”).

2. On page 5, configure the number of channels you want between Communications Manager and the branch site SES.

18

http://www.jaymzworld.com/w/images/4/40/Troubleshooting_SES.pdf


Configure Avaya SES at each Branch SiteThe configuration for the Avaya SES is identical for a branch site as shown in the section Configure Avaya SIP Enablement Services.

Configure Lync Server to use Branch Site SESTo complete the Direct SIP configuration with the branch site SES, perform the following steps:

1. Add the branch site SES as a gateway to the Lync Server topology.2. Define dial plan by configuring normalization rules.3. Create a voice policy.4. Define a trunk configuration.5. Assign the voice policy that you created to Lync users.

Adding Branch Site SES as a Gateway to the Lync TopologyPerform the following steps:

1. Log on as a member of the Domain Admins group or the RTCUniversalServerAdmins group to a computer that has Topology Builder installed.

2. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Topology Builder.

3. Expand the Mediation pools node. 4. Right-click the Survivable Branch Appliance or Survivable Branch Server, and then click Edit

Properties.5. Click New.6. In the Define New IP/PSTN Gateway dialog box, do the following:

In Gateway FQDN or IP Address, specify the IP address of the branch site SES. In Listening port for IP/PSTN gateway, set the port to 5060. Under Sip Transport Protocol, click TCP.

7. Click OK, and then click OK again.8. To publish your change to the Lync Server topology, in the Actions panel of the Topology

Builder, point to Topology, and then click Publish.

19

microsoftdownload.microsoft.com/.../integrating_lync_server_an… · web viewconfigure static route...

Documents