Transcription

Avaya Solution & Interoperability Test LabSample Configuration for a SIP Trunk between AvayaSIP Enablement Services Server and Cisco Unified CM7.0 – Issue 1.0AbstractThese Application Notes describe the steps for configuring a SIP trunk between AvayaSIP Enablement Services (SES) Server and Cisco Unified Communications Manager(CUCM).AL; Reviewed:SPOC 3/16/2009Solution & Interoperability Test Lab Application Notes 2009 Avaya Inc. All Rights Reserved.1 of 17SES-CUCM-SIPtrk

1. IntroductionSession Initiation Protocol (SIP) is a standards-based communication protocol capable ofsupporting voice, video, instant messaging and other multi-media communication. TheseApplication Notes will outline a solution for using SIP as a trunking protocol to supportcalling between an Avaya Communication Manager and a Cisco IP PBX.2. OverviewThe sample network shown in Figure 1 consists of two IP PBX systems each belongingto a different domain with its own dialing plan. The Avaya system consists of AvayaCommunication Manager and Avaya SIP Enablement Services (SES) Server supporting avariety of Avaya 4600 and 9600 Series IP Telephones with either H.323 or SIP protocolalong with digital and analog fax stations. The Cisco IP PBX system consists of CiscoUnified Communications Manager (CUCM) supporting the Cisco SIP and SCCP stationsalong with analog fax stations through the use of a Cisco 1751 router/gateway. A SIPtrunk is configured between Avaya SES and CUCM to support calling for telephonesbetween the Avaya and Cisco IP PBX systems. With the use of the SIP trunk transcoding, media and protocol conversion, calls between any 2 telephones are supportedregardless in this sample network whether they are between SIP, H.323, DCP, SCCP oranalog stations.3. ConfigurationFigure 1 illustrates the configuration used in these Application Notes. All telephones inthe 172.28.10.0/24 IP network are either registered with Avaya Communication Manageror Avaya SES and use extension 11xxx. All IP telephones in the 172.29.5.0/24 IPnetwork are registered with CUCM and use extension 60xxx. A single SIP trunkbetween Avaya SES and CUCM manages call control between the Avaya and Cisco IPPBX systems.Figure 1: Sample Network ConfigurationAL; Reviewed:SPOC 3/16/2009Solution & Interoperability Test Lab Application Notes 2009 Avaya Inc. All Rights Reserved.2 of 17SES-CUCM-SIPtrk

4. Equipment and Software ValidatedThe following equipment and software/firmware were used for the sample configuration:DEVICE DESCRIPTIONAvaya S8500 Server with G650 Media GatewayAvaya SIP Enablement Services (SES) ServerAvaya 4625SW IP Telephone (H.323)Avaya 9640 IP Telephone (H.323)Avaya 4610SW IP Telephone (SIP)Avaya 9640 IP Telephone (SIP)Avaya 6402D Digital TelephoneAvaya One-X Communicator (SIP)Cisco Unified Communications ManagerCisco 7965 Unified IP Phone (SIP)Cisco 7912 Unified IP Phone (SCCP)Cisco 1751v routerVERSION SIP45.8-4-1SApp Load IDCP7912080003SCCP070409ABoot Load IDLD0100BOOT021112AIOS 12.4(10a)5. Configure Cisco Unified CMThis section describes the SIP Trunk configuration for CUCM as shown in Figure 1. Itis assumed that the basic configuration needed to interoperate with the 1751router/gateway and support for Cisco IP telephones has been completed. For furtherinformation on Cisco Unified CM, please consult references [8] and [9].1. Open Cisco Unified CM Administration by entering the IP address of the CUCM intothe Web Browser address field, and log in using an appropriate Username andPassword.AL; Reviewed:SPOC 3/16/2009Solution & Interoperability Test Lab Application Notes 2009 Avaya Inc. All Rights Reserved.3 of 17SES-CUCM-SIPtrk

2. Select System Æ Security Profile Æ SIP Trunk Security Profile from the topmenu then click Add New to add a new SIP Trunk Security Profile.The following is a screen capture of the SIP Trunk Security Profile used in the samplenetwork. Configure the highlighted areas and click Save to commit the changes.AL; Reviewed:SPOC 3/16/2009Solution & Interoperability Test Lab Application Notes 2009 Avaya Inc. All Rights Reserved.4 of 17SES-CUCM-SIPtrk

3. Select Device Æ Trunk from the top menu then click Add New to begin adding anew SIP trunk.Select SIP Trunk as the Trunk Type and the Device Protocol field will automaticallybe change to SIP. Click Next to continue.AL; Reviewed:SPOC 3/16/2009Solution & Interoperability Test Lab Application Notes 2009 Avaya Inc. All Rights Reserved.5 of 17SES-CUCM-SIPtrk

Enter the appropriate information for the SIP Trunk. The following screen capture showsthe configuration used in the sample network. Click Save to complete.AL; Reviewed:SPOC 3/16/2009Solution & Interoperability Test Lab Application Notes 2009 Avaya Inc. All Rights Reserved.6 of 17SES-CUCM-SIPtrk

4. Select Call Routing Æ Route/Hunt Æ Route Pattern then click Add New to add anew route pattern for extension 11xxx which are for telephones registered with AvayaCommunication Manager.AL; Reviewed:SPOC 3/16/2009Solution & Interoperability Test Lab Application Notes 2009 Avaya Inc. All Rights Reserved.7 of 17SES-CUCM-SIPtrk

The following screen capture shows the route pattern used in the sample network. Theroute pattern “11xxx” will cause all 5 digit calls beginning with “11” to be routed throughthe “AvayaSES” SIP Trunk defined in Step 3. Click Save to complete.AL; Reviewed:SPOC 3/16/2009Solution & Interoperability Test Lab Application Notes 2009 Avaya Inc. All Rights Reserved.8 of 17SES-CUCM-SIPtrk

6. Configure Avaya Communication ManagerThis section shows the configuration of Avaya Communication Manager. Allconfigurations in this section are administered using the System Access Terminal (SAT).These Application Notes assume that the basic configuration between AvayaCommunication Manager and Avaya SIP Enablement Services (SES) Server has alreadybeen completed and working. For further information on Avaya CommunicationManager, please consult with references [1], [2] and [3].1. Use the add signaling-group command to add a new signaling group into the system.The sample network uses signaling groups 29 and 80. Signaling group 29 is thesignaling group configured for communication between Avaya CommunicationManager and Avaya SES Server that should have been configured as part of the basicconfiguration. This signaling group has interop.com which is the same domain asAvaya Communication Manager configured as its Far-end Domain.display signaling-group 29SIGNALING GROUPGroup Number: 29Group Type: sipTransport Method: tlsNear-end Node Name: CLANNear-end Listen Port: 5061Far-end Node Name: SESFar-end Listen Port: 5061Far-end Network Region: 9Far-end Domain: interop.comBypass If IP Threshold Exceeded? nDTMF over IP: rtp-payloadDirect IP-IP Audio Connections? yIP Audio Hairpinning? nEnable Layer 3 Test? nSession Establishment Timer(min): 3Alternate Route Timer(sec): 6The following signaling-group 80 is added to Avaya Communication Manager for theSIP Trunk that is configured for traffic between Avaya SES and CUCM. The Far-endDomain is left blank to allow for incoming SIP calls from domains not matchinginterop.com. Alternatively, a specific domain that the CUCM system is in can also beentered.display signaling-group 80SIGNALING GROUPGroup Number: 80Group Type: sipTransport Method: tlsNear-end Node Name: CLANNear-end Listen Port: 5061Far-end Node Name: SESFar-end Listen Port: 5061Far-end Network Region: 9Far-end Domain:Bypass If IP Threshold Exceeded? nDTMF over IP: rtp-payloadEnable Layer 3 Test? nSession Establishment Timer(min): 3AL; Reviewed:SPOC 3/16/2009Direct IP-IP Audio Connections? yIP Audio Hairpinning? nAlternate Route Timer(sec): 6Solution & Interoperability Test Lab Application Notes 2009 Avaya Inc. All Rights Reserved.9 of 17SES-CUCM-SIPtrk

2. Use the add trunk-group command to add a new trunk group into the system. Thesample network uses trunk groups 29 and 80. Trunk group 29 is the trunk groupconfigured for communication between Avaya Communication Manager and AvayaSES Server that should have been configured as part of the basic configuration. Thistrunk group is configured to use signaling group 29 shown in Step 1. The followingis a screen capture for trunk group 29.display trunk-group 29Page1 of21TRUNK GROUPGroup Number:Group Name:Direction:Dial Access?Queue Length:Service Type:29To-SEStwo-wayn0tieGroup Type: sipCDR Reports: yCOR: 1TN: 1TAC: 129Outgoing Display? nNight Service:Auth Code? nSignaling Group: 29Number of Members: 50Trunk group 80 is added to Avaya Communication Manager for the SIP Trunk that isconfigured for traffic between Avaya SES and Cisco Unified CM. Trunk group 80 isconfigured to use signaling group 80 shown in Step 1. The following is a screen captureof trunk group 80. It is important to note that the trunk group used for domains otherthan interop.com has a higher trunk group number than the trunk group having the nativedomain, in this case trunk group 29 using interop.com. This helps match domaininformation on incoming SIP calls to the native domain when multiple SIP trunks areconfigured between Avaya Communication Manager and Avaya SES.display trunk-group 80Page1 of21TRUNK GROUPGroup Number:Group Name:Direction:Dial Access?Queue Length:Service Type:80To-CUCM7two-wayn0tieGroup Type: sipCDR Reports: yCOR: 1TN: 1TAC: 180Outgoing Display? nNight Service:Auth Code? nSignaling Group: 80Number of Members: 10AL; Reviewed:SPOC 3/16/2009Solution & Interoperability Test Lab Application Notes 2009 Avaya Inc. All Rights Reserved.10 of 17SES-CUCM-SIPtrk

3. Use the change ip-network-region form to configure the ip-network-region andcodec. The following screen capture shows ip-network-region 9 used in the samplenetwork.display ip-network-region 9Page1 of19IP NETWORK REGIONRegion: 9Location:Authoritative Domain: interop.comName:MEDIA PARAMETERSIntra-region IP-IP Direct Audio: yesCodec Set: 1Inter-region IP-IP Direct Audio: yesUDP Port Min: 2048IP Audio Hairpinning? nUDP Port Max: 3329DIFFSERV/TOS PARAMETERSRTCP Reporting Enabled? yCall Control PHB Value: 46RTCP MONITOR SERVER PARAMETERSAudio PHB Value: 46Use Default Server Parameters? yVideo PHB Value: 26802.1P/Q PARAMETERSCall Control 802.1p Priority: 6Audio 802.1p Priority: 6Video 802.1p Priority: 5AUDIO RESOURCE RESERVATION PARAMETERSH.323 IP ENDPOINTSRSVP Enabled? nH.323 Link Bounce Recovery? yIdle Traffic Interval (sec): 20Keep-Alive Interval (sec): 5Keep-Alive Count: 5display ip-network-region 9Page3 of19Inter Network Region Connection Managementsrcrgn999999999dst codec directWAN-BW-limitsVideoInterveningrgn setWAN UnitsTotal Norm Prio Shr Regions11yNoLimit234567891DynCAC IGAR AGLnall4. Use the change ip-codec-set form to configure the audio codec. The followingscreen capture shows ip-codec-set 1 used in the sample network.display ip-codec-set 1Page1 of2IP Codec SetCodec Set: 1AudioCodec1: G.711MU2:AL; Reviewed:SPOC 3/16/2009SilenceSuppressionnFramesPer Pkt2PacketSize(ms)20Solution & Interoperability Test Lab Application Notes 2009 Avaya Inc. All Rights Reserved.11 of 17SES-CUCM-SIPtrk

5. Use change dialplan analysis to define any 5 digit call beginning with 60 as an aarCall Type. The following screen capture shows the dialplan used in the samplenetwork.display dialplan analysisPageDIAL PLAN ANALYSIS TABLELocation: dacextaarfacfacfacfacDialedStringTotal CallLength Type1 ofPercent Full:DialedString121Total CallLength Type6. Use change aar analysis form to configure the appropriate route pattern for the 5digit dial string that begins with 60. The following screen capture shows the calls to60xxx are routed using Route Pattern 29 in the sample network.display aar analysis 60PageAAR DIGIT ANALYSIS TABLELocation: allDialedStringTotalMin aaraaraar1 ofPercent Full:NodeNum21ANIReqdnnnn7. Use the change route-pattern form to configure the appropriate trunk group. Thefollowing screen capture shows that route pattern 29 directs calls to use trunk group29 in the sample network.change route-pattern 29PagePattern Number: 29 Pattern Name: To-CUCM-7SCCAN? nSecure SIP? nGrp FRL NPA Pfx Hop Toll No. InsertedNoMrk Lmt List Del DigitsDgts1: 2902:3:4:1:2:3:4:AL; Reviewed:SPOC 3/16/2009BCC VALUE TSC CA-TSC0 1 2 M 4 WRequestITC BCIE Service/Feature PARMyyyyrestrestrestrestyyyyyyyyyyyyyyyynnnnnnnn1 of3DCS/QSIGIntwnnnnIXCuseruseruseruserNo. Numbering LARDgts FormatSubaddressnonenonenonenoneSolution & Interoperability Test Lab Application Notes 2009 Avaya Inc. All Rights Reserved.12 of 17SES-CUCM-SIPtrk

7. Configuring Avaya SES ServerThis section shows the configuration of Avaya SES Server. These Application Notesassume that the basic configuration between Avaya Communication Manager and AvayaSES Server has already been completed and working. For further information on AvayaSES, please consult references [4], [5] and [6].1. Open the Avaya SES administration interface by entering the IP address of AvayaSES Server into a Web Browser in the form of http://IP address/admin. Log in usingappropriate credentials.Upon successfully logging into Avaya SES, select Launch SES Administration Interface(not shown below).2. Select Trusted Hosts Æ Add to add the CUCM as a trusted host. The following is ascreen capture of the Trusted Host information. Click Add to completeAL; Reviewed:SPOC 3/16/2009Solution & Interoperability Test Lab Application Notes 2009 Avaya Inc. All Rights Reserved.13 of 17SES-CUCM-SIPtrk

3. Select Hosts Æ List from the left menu panel to display a list of hosts then click onMap to begin adding a new address map.The following screen capture shows the host map to direct any 5 digit number beginningwith “60” to Cisco Unified CM. Click Add to complete.After adding the new host map, click Add Another Contact to configure the contactinformation.AL; Reviewed:SPOC 3/16/2009Solution & Interoperability Test Lab Application Notes 2009 Avaya Inc. All Rights Reserved.14 of 17SES-CUCM-SIPtrk

The following screen capture shows the host contact used in the sample network. TheContact entry “sip: (user)@172.29.5.20:5060;transport tcp” directs the SIP call to theCUCM IP address of 172.29.5.20 using TCP as the transport protocol. Click Add tocomplete.8. VerificationThe following steps may be used to verify the configuration:1. “list trace station” may be used in Avaya Communication Manager via SAT toverify whether calls from Avaya H.323, digital, or analog telephones are beingrouted to the correct trunk group.2. The Real Time Monitoring Tool (RTMT) can be use to monitor events on CiscoUnified CM. This tool can be downloaded by selecting Application Æ Pluginsfrom the top menu of the Cisco Unified CM Administration Web interface. Forfurther information on this tool, please consult with reference [10].9. ConclusionThese Application Notes describe the administrative steps required to configure a SIPtrunk to support calls between an Avaya IP PBX and a Cisco IP PBX system. Basiccalling including Hold, Transfer, Conference and Fax Pass-through as well assupplemental features such as Call Forward All, Call Park/Unpark are supported by thisconfiguration.Due to implementation differences between Cisco SIP and SCCP telephone, there is acertain limitation when using Music-on-Hold between an Avaya telephone and CiscoSCCP telephone. Music can not be heard on an Avaya telephone when a call is placed onHold by the Cisco SCCP telephone. However, Music-on-Hold does work when the Holdis placed by an Avaya telephone. This limitation does not apply to the Cisco SIPtelephone used in this configuration.AL; Reviewed:SPOC 3/16/2009Solution & Interoperability Test Lab Application Notes 2009 Avaya Inc. All Rights Reserved.15 of 17SES-CUCM-SIPtrk

10. Additional ReferencesProduct documentation for Avaya products may be found at istrator Guide for Avaya Communication Manager, Doc # 03-300509, Issue4.0, Release 5.0, January 2008Avaya Communication Manager Advanced Administration Quick Reference, Doc #03-300364, Issue 4, Release 5.0, January 2008Administration for Network Connectivity for Avaya Communication Manager, Doc# 555-233-504, Issue 13, January 2008Administering SIP Enablement Services on the Avaya S8300 Server, Doc # 03602508, Issue 1.0, January 2008SIP Support in Avaya Communication Manager Running on Avaya S8xxx Servers,Doc # 555-245-206, Issue 8, January 2008Configuring Avaya SIP Telephony Users on Avaya SIP Enablement Services andAvaya Communciation Manager, Issue 1.0one-X Communicator Adminsitration Quick Setup, Doc # 16-602603, Issue 3,December 2008Product documentation for Cisco Systems products may be found athttp://www.cisco.com[8]Cisco Unified Communications Manager Administration Guide for Cisco UnifiedCommunications Manager Business Edition, Release 7.0(1), Part Number: OL15405-01[9] Cisco Unified Communications Manager Features and Services Guide for CiscoUnified Communication Manager Business Edition, Release 7.0(1), Part Number:OL-15409-01[10] Cisco Unified Real-Time Monitoring Tool Administration Guide, Release 7.0(1),Part Number: OL-14994-01AL; Reviewed:SPOC 3/16/2009Solution & Interoperability Test Lab Application Notes 2009 Avaya Inc. All Rights Reserved.16 of 17SES-CUCM-SIPtrk

2009 Avaya Inc. All Rights Reserved.Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by and are registered trademarks or trademarks, respectively, of Avaya Inc. All othertrademarks are the property of their respective owners. The information provided inthese Application Notes is subject to change without notice. The configurations,technical data, and recommendations provided in these Application Notes are believed tobe accurate and dependable, but are presented without express or implied warranty.Users are responsible for their application of any products specified in these ApplicationNotes.Please e-mail any questions or comments pertaining to these Application Notes alongwith the full title name and filename, located in the lower right corner, directly to theAvaya Solution & Interoperability Test Lab at [email protected]; Reviewed:SPOC 3/16/2009Solution & Interoperability Test Lab Application Notes 2009 Avaya Inc. All Rights Reserved.17 of 17SES-CUCM-SIPtrk

Session Initiation Protocol (SIP) is a standards-based communication protocol capable of supporting voice, video, instant messaging and other multi-media communication. These Application Notes will outline a solution for using SIP as a trunking protocol to support calling between an Avaya