Topology · Web viewAvaya CS1000E V e ndo r Avaya M od els Communication Server 1000 (CS1K) S oft w a r e V e r si o n 7.50 V o IP Pr oto c o l SIP A d d i t i on al N ot es None Configuration

Integrating Microsoft Lync Server 2013 and Avaya Aura Session Manager 6.1

DOCUMENT REVISION HISTORY

Version Reason for Change Date Created/Updated by

1.1 Initial Draft for Lync 2013 8/26/2013 Srikanth Jonnada

1.2 Updated based on Microsoft’s comments 8/27/2013 Srikanth Jonnada

1.3 Updated with recommendation on RTCP 9/4/2013 Srikanth Jonnada

TEKVIZION PVS, INC. Page 1 of 43

Table of Contents

1 Topology..............................................................................................................................................4

2 Components Information....................................................................................................................5

3 Configuration Overview.......................................................................................................................6

3.1 Lync Server 2013..........................................................................................................................6

3.2 Aura CS1000................................................................................................................................6

4 Avaya Communication Server 1000E Configuration............................................................................7

4.1 Node and key IP address..............................................................................................................7

4.2 D-Channel, Routes and Trunks...................................................................................................12

4.2.1 D-Channel Configuration....................................................................................................12

4.2.2 Add Routes and Trunks......................................................................................................14

4.3 Dialing and Numbering Plans.....................................................................................................18

4.3.1 Configure RLB.....................................................................................................................18

4.3.2 Configure VNR via overlay 15.............................................................................................19

5 Avaya Aura Session Manager Configuration......................................................................................20

5.1 Add Domains.............................................................................................................................20

5.2 Add Location..............................................................................................................................21

5.3 Add Adaptations........................................................................................................................21

5.3.1 Adaptation for Microsoft Lync 2013..................................................................................21

5.3.2 Adaptation for Avaya CS1000E..........................................................................................22

5.4 Add SIP Entities and Entity Link..................................................................................................23

5.4.1 SIP Entity for Session Manager..........................................................................................23

5.4.2 SIP Entity and entity Link for Lync 2013.............................................................................23

5.4.3 SIP Entity and Entity Link for CS1000E...............................................................................24

5.5 Add Routing Polices...................................................................................................................25

5.5.1 Routing policy for call to go to Lync 2013..........................................................................25

5.5.2 Routing Policy for calls to go to CS1000E...........................................................................26

5.6 Add Dial Pattern.........................................................................................................................26

5.6.1 Dial pattern to Lync 2013...................................................................................................26

5.6.2 Dial Pattern to CS1000E.....................................................................................................27

5.7 Configure Local Host Name Resolution to resolve the Mediation Pool FQDN...........................28

6 Lync Server Configuration..................................................................................................................29


6.1 Add Avaya Session Manager to Lync Topology..........................................................................29

6.2 Trunk Configuration...................................................................................................................34

6.3 Route.........................................................................................................................................37

6.4 Voice Policy and PSTN Usage.....................................................................................................38

6.5 Dial Plan.....................................................................................................................................41

6.6 Configure Media Bypass............................................................................................................42


1 Topology

Figure 1: Deployment Topology


2 Components Information

Lync Server 2013 Version

Vendor MicrosoftModels Lync Server 2013

Software Version RTM: Release 2013 5.0.8308.0

VoIP Protocol SIPAdditional Notes None

Avaya Aura Session Manager

Vendor AvayaModels Aura Session Manager

Software Version 6.1.2.0.612004


Avaya CS1000E

Vendor AvayaModels Communication Server 1000 (CS1K)

Software Version 7.50



3 Configuration Overview3.1 Lync Server 2013

Feature ConfigurationREFER EnabledMedia Bypass DisabledSession Timer EnabledRTCP DisabledEncryption Level Support EncryptionHistory-Info Disabled

3.2 Aura CS1000Feature ConfigurationPhone-Context DisabledVNR EnabledLocal Host Name Resolution EnabledSecurity Not enabled


4 Avaya Communication Server 1000E ConfigurationLog into UCM via https://<ip-address>, where <ip-address> is the IP address of Primary UCM.log on with appropriate credentials.

Navigation: Network->Elements

Click on the Element Name corresponding to “CS1000” in the Element Type column. In the abridged screen below, the user would click on the Element Name “EM on tekcs 1k7-5”.

Figure 2: Access Element Manager through UCM

4.1 Node and key IP addressFrom CS1000 Element Manager

Navigation: System -> IP Network/Node: Server, Media cards

The IP Telephony Nodes page is displayed as show below. Click “<Node id>” in the Node ID column to view details of the node. In the sample configuration, Node ID “1” was used.

Figure 3: Node configuration-1

The Node Details screen is displayed with additional details as shown below. Under the Node Details heading at the top of the screen, make a note of the TLAN Node IPV4 address. In the sample screen below, the Node IPV4 address is “10.64.2.131”. This IP address will be needed when configuring Session Manager with a SIP Entity for the CS1000E.


Figure 4: Node Configuration-2

Using the scroll bar on the right side of the screen, navigate to the Applications section on the screen and select the Gateway (SIPGw) link to view or edit the SIP Gateway configuration.

Figure 5: SIP Gateway Configuration-1

On the Node ID: 1 - Virtual Trunk Gateway Configuration Details page, enter the following values and use default values for remaining fields.

Check Enable gateway service on this nodeSIP domain name: lab.avaya.comLocal SIP port: 5060 Gateway endpoint name: nortel---any name as we use Session manager instead of NRSApplication node ID: 1



Scroll down to the SIP Gateway Settings Proxy or Redirect Server section.

Primary TLAN IP address: 10.70.2.6Port:5060Transport protocol :TCP



Scroll down to the SIP Gateway Settings -> SIP URI Map section:

Leave all Public E164 domain names fields to BLANK.

Figure 8: SIP Gateway Configuraiton-4

Click Save to save SIP Gateway configuration settings. This will return the interface to the Node Details screen. Click Save on the Node Details screen.



Select Transfer Now on the Node Saved page as shown below.


Select all components and then ”Start Sync”.


After Sync complete, Restart Applications:



4.2 D-Channel, Routes and TrunksAvaya Communication Server 1000E Call Server utilizes D-channel and associated Route and Trunks to communicate with the Signaling Server and PSTN.

4.2.1 D-Channel ConfigurationFrom CS1000 Element Manager

Navigation: Routes and TrunksD-Channels

4.2.1.1 Add DCH to ISDN Gateway1. As there is no DCH programmed in the system, a pop-up window appear to prompt add DCH,

click “OK”.

Figure 13: D-Channel Configuration-1

2. Choose a D-Channel Number: select 11 from drop-down menu.3. Click “to Add”



4. Set D channel Card Type: TMDI5. Set Media Gateway Card: 0 1 36. Set User: PRI7. Set Interface type for D-channel: NI28. Set D-Channel PRI loop number: 119. Set Release ID of the switch at the far end: select 25 from drop- down10. Leave all other fields as default, click “Submit”.


4.2.1.2 Add Virtual DCH to Signaling Server.1. Choose a D-Channel Number: select 15 from Drop-down, then click “to Add”



2. Set D channel Card Type: DCIP3. Set Interface type for D-channekl: SL14. Set Meridian 1 node type:USR5. Set Release ID of the switch at the far end:select 25 from drop-down6. Set Signaling server resource capacity:18007. Leave all other fields as default and click “Submit”


4.2.2 Add Routes and TrunksNavigation: Routes and TrunksRoute and Trunks

Figure 18: Route & Trunk Configuration-1


4.2.2.1 Add DID route and trunks to ISDN gateway1. Set Route number (ROUT): select 11 from drop-down2. Set Trunk type (TKTP): DID3. Set Incoming and outgoing trunk (ICOG): IAO4. Set Access code for the trunk route (ACOD): 70115. Set Digital trunk route (DTRK) :checked6. Integrated services digital network option (ISDN): checked

a. Digital trunk type (DGTP): PRIb. Mode of operation (MODE): PRAc. Interface type for route (IFC): NI2

7. Leave all other fields as default and then “Save”


8. Click “Add trunk” under Routes and Trunk.



9. Set Multiple trunk input number: 2310. Set Terminal number: 11 111. Set Member number: 112. Set Start arrangement Incoming: OWK13. Set Start arrangement Outgoing: OWK14. Leave all other fields as default and “Save”


4.2.2.2 Add Virtual TIE route and trunks to Signaling Server1. Set Route number (ROUT): 102. Set Trunk type (TKTP): TIE3. Set Incoming and outgoing trunk (ICOG): IAO4. Set Access code for the trunk route (ACOD): 70885. Confirm ‘the route is for a virtual trunk route (VTRK)’: checked6. Confirm Integrated services digital network option (ISDN): checked

a. Zone for codec selection and bandwidth management (ZONE): 1b. Node ID of signaling server of this route (NODE)c. Protocol ID for the route (PCID): SIPd. Mode of operation (MODE): ISLDe. D channel number (DCH): 15f. Interface type for route (IFC): SL1

7. Click “Save”



8. Click “Add trunk” for route 10.9. Set Multiple trunk input number: 810. Set Trunk data block: IPTI11. Set Terminal number: 100 0 1 012. Set Start arrangement Incoming: IMM13. Set Start arrangement Outgoing: IMM14. Set Channel ID for this trunk: 115. Click “Save”.



4.3 Dialing and Numbering PlansFor simple configuration, we are using VNR (Vacant Number Routing) in CS1000 to route the call to PSTN via PRI trunk.

4.3.1 Configure RLB.Log into CS via Putty, use proper login to gain access to overlay. Configure RLB via overlay 86.

REQ: newCUST: 0FEAT: rlbRLI: 20ROUT: 11

Figure 24: Route List Index


4.3.2 Configure VNR via overlay 15.REQ: chgTYPE: netVNR: yesRLI: 20UDPL: 11

Figure 25: VNR Configuration


5 Avaya Aura Session Manager ConfigurationAccess Avaya Aura System Manager web login screen via https://<IP Address/FQDN> , in our lab, IP address is 10.70.2.4. Use admin as User ID and associated password, and then “Log on”

Navigation: HomeElementsRouting

Figure 26: System Manager Home page

5.1 Add DomainsUnder page Domain Management:

1. Set Name: This is name of the domain the Session Manager should be on.2. Set Type: sip

Figure 27: Domain Configuration


5.2 Add Location1. Set Name: Enter the name of your location

Figure 28: Location Configuration

5.3 Add Adaptations5.3.1 Adaptation for Microsoft Lync 2013

1. Adaptation name: Lync20132. Module name: DigitConversionAdapter3. Module Parameter: odstd=lab.tekvizion.com4. Under Digit Conversion for Outgoing Calls from SM:5. Matching Pattern: 9726. Min: 107. Max: 108. Delete Digits: 09. Insert Digits: +110. Address to modify: both

Figure 29: Adaptation-1


5.3.2 Adaptation for Avaya CS1000E1. Adaptation name:CS1K_adaptation2. Module name: DigitConversionAdapter3. Module Parameter: osrcd=lab.tekvizion.com odstd=lab.tekvizion.com4. Under Digit Conversion for Incoming Calls to SM:5. Matching Pattern: 16. Min: 117. Max: 118. Delete Digits: 09. Insert Digits: +10. Address to modify: destination

Figure 30: Adaptation-2


5.4 Add SIP Entities and Entity Link5.4.1 SIP Entity for Session Manager

1. Set Name: Enter name of the host, teksm is used here for example.2. Set FQDN or IP Address: Enter the ip address of this device. 10.70.2.6 is used here for example.3. Set Type: Session Manager4. Set Location: Dallas5. Set Time Zone: America/Chicago6. Set SIP Link Monitoring: Use Session manager Configuration

Figure 31: SIP Entity and Entity Link-1

5.4.2 SIP Entity and entity Link for Lync 20131. Set Name: Lync_20132. Set FQDN or IP Address: This is the FQDN of the mediation server pool.3. Set Type: Other4. Set Adaptation: Lync20135. Set Location: Dallas6. Set Time Zone: America/Chicago7. Set SIP Link Monitoring: Use Session Manager Configuration8. Set SIP Entity 1: teksm9. Set Protocol: TCP10. Set Port: 506011. Set SIP Entity 2: Lync_201312. Set Port: 5060



5.4.3 SIP Entity and Entity Link for CS1000E1. Set Name: CS1K2. Set FQDN or IP Address: This is the ip address of CS100E node. 10.64.2.131 is used here for

example.3. Set Type: Other4. Set Adaptation: CS1K_adaptation5. Set Location: Dallas6. Set Time Zone: Chicago7. Set Sip Link Monitoring: Use Session Manager Configuration8. Set SIP Entity 1: teksm9. Set Protocol: TCP10. Set Port: 506011. Set SIP Entity 2: CS1K12. Set Port: 5060



5.5 Add Routing Polices5.5.1 Routing policy for call to go to Lync 2013

1. Set Name: to_Lync20132. Select SIP Entity “Lync_2013” for SIP Entity as Destination

Figure 34: Routing Policy-1


5.5.2 Routing Policy for calls to go to CS1000E1. Set Name: To_CS1K2. Select SIP Entity “CS1K” for SIP Entity as Destination

Figure 35: Routing Policy-2

5.6 Add Dial Pattern5.6.1 Dial pattern to Lync 2013

1. Pattern: +19722. Min: 123. Max: 124. SIP Domain: lab.tekvizion.com5. Original Location Name: Dallas6. Routing Policy Name: to_Lync2013

Figure 36: Dial Pattern-1


5.6.2 Dial Pattern to CS1000E1. Set Pattern: +12142. Set Min: 123. Set Max: 124. Set SIP Domain: lab.tekvizion.com5. Set Original Location Name: Dallas6. Set Routing Policy Name: To_CS1K


7. Set Pattern: +188. Set Min: 129. Set Max: 1210. Set SIP Domain: lab.tekvizion.com11. Set Original Location Name: Dallas12. Set Routing Policy Name: To_CS1K



5.7 Configure Local Host Name Resolution to resolve the Mediation Pool FQDN.Navigation: HomeElementsSession Manager

Select New and add FQDN of mediation severs and associated IP address, Port, protocol, Priority and Weight as below.

Figure 39: Local Host Name Resolution


6 Lync Server Configuration6.1 Add Avaya Session Manager to Lync TopologyLync recognizes Avaya Session Manager as a PSTN gateway connected by SIP. So we need to add Avaya Session Manager to the Lync topology by adding it as a PSTN gateway.

1. To add a PSTN gateway to the Lync topology, run Lync Server Topology Builder as a user in the CSAdministrator group. Then add the Avaya Session Manager to the PSTN gateway topology

Figure 40: Configure PSTN Gateway -1


2. Set FQDN: This is the IP Address or FQDN of the Avaya Session Manager

Figure 41: Configure PSTN Gateway-2




3. Set Trunk Name: This is the FQDN of the Avaya Session Manager4. Set Listening port for IP/PSTN gateway: This Listening port should match the Port setting in the

Session Manager’s Entity Link.5. Set SIP Transport Protocol: TCP6. Set Associate Mediation Server: Assign this PSTN gateway to the Mediation Server.

Medpool.lynclabkm2013.local is used here for example.



7. Publish topology to make the changes effective, refer to below scree capture for the process.

Figure 44: Publish Topology


6.2 Trunk ConfigurationNavigation: Voice Routing -> Trunk Configuration

1. Create a Pool Trunk by selecting New2. Select Service: Select the trunk to Avaya Session Manager you created in topology builder3. Set Maximum early dialogs supported: 204. Set Encryption support level: Optional5. Set Refer Support: Enable sending refer to the gateway6. Confirm Enable media bypass: is unchecked7. Confirm Centralized media processing: is checked8. Confirm Enable RTP latching: is unchecked9. Confirm Enable forward call history: is unchecked10. Confirm Enable forward P-Asserted-Identity data: is unchecked11. Confirm Enable outbound routing failover timer: is checked

Figure 45: Trunk Configuration -1






6.3 RouteNavigation: Voice Routing -> Route

1. Set Name: Enter a name for this route2. Add Associated gateways: Add the gateway (Session Manager here) to which this route should

send all the calls.

Figure 48: Route Configuration


6.4 Voice Policy and PSTN UsageNavigation: Voice Routing -> Voice Policy

1. Create a User policy by selecting New2. Set Name: Enter a name for this Voice Policy3. Set Calling Features:

a. Enable call forwarding : Checkedb. Enable delegation : Checkedc. Enable call transfer : Checkedd. Enable call park : Checkede. Enable simultaneous ringing of phones : Checkedf. Enable team call : Checkedg. Enable PSTN reroute : Checkedh. Enable bandwidth policy override : Uncheckedi. Enable malicious call tracing : Unchecked

4. Set Associated PSTN Usages: a. Select New to create a new PSTN Usageb. Set Name: Enter a name for this PSTN Usagec. Set Associated Routes: Select the route you created under Voice Routing -> Route

Figure 49: Voice Policy -1


Figure 50: Voice Policy -2


Figure 51: PSTN Usage


6.5 Dial PlanCreate a dial plan with normalization rules for all the enterprise and local voice calls.


6.6 Configure Media BypassNavigation: Network Configuration -> Global

1. UnCheck ‘Enable media bypass’ in Global setting.2. Confirm you have also disabled media bypass in the trunk configuration

Figure 52: Media Bypass

Configure RTCP, Session Timer and Encryption level parameters through the Windows PowerShell® command line interface because they are not configurable on Lync Server Control Panel

1. RTCPCallsonHold and RTCPActiveCalls must be turned off. RTCP is a control channel that is opened and is used to monitor the network specific conditions of the RTP channel. CS1000 does not send RTCP when it receives a=inactive, so if the variables are not disabled, the Mediation Server will expect keepalives for the RTCP channel, which may cause unexpected behavior.

Set-CsTrunkConfiguration –identity <Trunk name> –RTCPActiveCalls $false –RTCPCallsonHold $false

2. SessionTimer must be enabled. Because the RTCP channel is disabled, session timers must be enabled so that calls don’t stay up indefinitely in case we don’t get proper teardown of the call.

Set-CsTrunkConfiguration –identity <Trunk name> –EnableSessionTimer $true


3. Media EncryptionLevel must be set to SupportEncryption. Since we have not setup SRTP to Avaya through Direct SIP, we need to set the media configuration’s EncryptionLevel to SupportEncryption so that SRTP will only be used if it can be negotiated. By default, this parameter is set to RequireEncryption, meaning SRTP must be used.

Set-CsMediaConfiguration –identity Global -EncryptionLevel SupportEncryption


Documents

Topology · Web viewAvaya CS1000E V e ndo r Avaya M od els Communication Server 1000 (CS1K) S oft w a r e V e r si o n 7.50 V o IP Pr oto c o l SIP A d d i t i on al N ot es None Configuration