WIXLIB

Connecting Cisco Unified CommunicationManager [v11.5.1] to CenturyLink IQ SIPTrunks via Cisco Unified Border Elementv11.5.2 [IOS-XE 16.3.2]May 3, 2017 2017 Cisco Systems, Inc. All rights reserved.Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.comPage 1 of 70

Table of ContentsIntroduction . 4Network Topology. 5System Components . 6Hardware Requirements . 6Software Requirements . 6Features . 6Features Supported . 6Features Not Supported. 6Caveats . 7Configuration . 8Configuring Cisco Unified Border Element . 8Network Interface . 8Global Cisco UBE settings. 11Codecs . 12Dial peer . 12Configuration example. 16Configuring CUCM 11.5 cluster . 46Trunk configuration. 46Routing configuration . 54SIP Trunk Security Profile . 59Fax Gateway Configuration . 59Acronyms . 69Important Information . 69Test Results . Error! Bookmark not defined.Cisco Service Provider Test Plan . Error! Bookmark not defined.Century Link Dual Trunk Test Plan . Error! Bookmark not defined. 2017 Cisco Systems, Inc. All rights reserved.Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.comPage 2 of 70

Table of FiguresFigure 1 Network Topology . 5Figure 2 High Availability topology . 8Figure 3 Add new Trunk in CUCM . 46Figure 4 Add SIP Trunk Type . 47Figure 5 SIP Trunk Device name and Device Pool selection . 48Figure 6: Inbound call Configuration. 49Figure 7 Trunk IP Address and security configuration . 50Figure 8 Add a new SIP Trunk to FAX gateway . 51Figure 9 Trunk Type and Device Protocol configuration. 51Figure 10 SIP Trunk Device name and Device Pool selection . 52Figure 11 Inbound call Routing Configuration . 53Figure 12 Outbound Call Routing and Trunk Security Settings . 54Figure 13 Add New Route Pattern to CUBE . 55Figure 14 Route Pattern Configuration for CUBE . 56Figure 15 Add New Route patter to Fax Gateway . 57Figure 16 Route Pattern Configuration to Fax Gateway . 58Figure 17 SIP Trunk Security Profile . 59 2017 Cisco Systems, Inc. All rights reserved.Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.comPage 3 of 70

IntroductionService Providers today, such as CenturyLink, are offering alternative methods to connect to the PSTNvia their IP network. Most of these services utilize SIP as the primary signaling method and centralizedIP to TDM POP gateways to provide on-net and off-net services.CenturyLink IQ SIP Trunk is a service provider offering that allows connection to the PSTN and may offerthe end customer a viable alternative to traditional PSTN connectivity. A demarcation device betweenthese services and customer owned services is recommended. As an intermediary device betweenCUCM 11.5.1 and CenturyLink network, Cisco Unified Border Element (Cisco UBE) v11.5.2 can be used.The Cisco Unified Border Element provides demarcation, security and inter-working and session controlservices for CUCM connected to CenturyLink IP network.This document assumes the reader is knowledgeable with the terminology and configuration of CUCM.Only configuration settings specifically required for CenturyLink interoperability are presented. Featureconfiguration and most importantly the dial plan are customer specific and need individual approach. This application note describes how to configure a CUCM 11.5.1 and Cisco Unified Border Element(Cisco UBE) v11.5.2 for connectivity to CenturyLink IQ SIP Trunking service. The deployment modelcovered in this application note is CUCM to PSTN via Cisco Unified Border Element v11.5.2 [IOSXE] 16.3.2. Testing was performed in accordance to Cisco generic SIP Trunking test methodology and amongfeatures verified were – basic calls, DTMF transport, Music on Hold (MOH), unattended andattended transfers, call forward, conferences and High Availability. Testing was performed in accordance to CenturyLink Dual Trunk Test with Fail-over and LoadBalancing among the trunks. The Cisco Unified Border Element (Cisco UBE) configuration detailed in this document is based ona lab environment with a simple dial-plan used to ensure proper interoperability betweenCenturyLink SIP network and CUCM. The configuration described in this document details theimportant configuration settings to have enabled for interoperability to be successful and caremust be taken by the network administrator deploying CUCM to interoperate to CenturyLink SIPTrunking network. 2017 Cisco Systems, Inc. All rights reserved.Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.comPage 4 of 70

Network TopologyFigure 1 Network Topology The network topology includes the CUCM Cluster, Unity Voicemail system, Cisco Fax gatewayand 2 Cisco Endpoints. CUCM has a trunk configured to CUBE’s Virtual IP Address. CenturyLinkwas used as the service provider with Dual SIP trunks to the Cisco UBE using the WAN Virtual IPAddress.2 Cisco Unified Border Elements are used here for High Availability.SIP Trunk transport type used between Cisco Unified Border Element and CUCM is TCP and toCenturyLink is UDP.CUCM and CUBE Settings:SettingValueTransport from CUBE to CUCMTCP with RTPTransport from CUBE to CenturyLinkUDP with RTPVoice Mail SupportYESSession RefreshYESEarly Media support with PRACKYESG729 Conference SupportYES 2017 Cisco Systems, Inc. All rights reserved.Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.comPage 5 of 70

System ComponentsHardware Requirements Cisco UBE on Cisco ISR 4431 routerCUCM cluster on UCS, 1 Publisher node and 2 Subscriber nodesCisco 2851 with FXS ports and Analog Fax machineGeneric Cisco IP-PhonesSoftware Requirements CUBE-Version: 11.5.2 running IOS-XE 16.3.2CUCM UCOS for 1 Publisher and 2 SubscriberCisco IOS v12.4 for the fax gatewayFeaturesFeatures Supported Incoming and outgoing off-net calls using G711 and G729Cisco Multi-Tenant with Failover and Load Balancing in SIP Trunks.International Calls and digit manipulationsCall Conference with G729 supportCPE Voice Mail supportCall hold & Resume with and without MoHUnattended and Attended Call transferCall forward (all, busy and no answer)DTMF (RFC2833)Fax Pass-throughIP-PBX Calling number privacyHigh AvailabilityFeatures Not Supported Blind Call transfer 2017 Cisco Systems, Inc. All rights reserved.Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.comPage 6 of 70

Caveats As of writing this application note, CenturyLink supports G.711 pass-through for faxing on IQSIP Trunk. Currently T.38 is not supported. The Fax protocol is indicated and set at the timeof implementation of the service and CenturyLink recommends that customers use ourCenturyLink trial process to confirm Fax capability prior to full deployment. Caller ID updates are not observed on attended call transfer scenarios. Testing is done with only one IP PBX. Workaround is done for SIP header manipulations for Register, Call Forward and CallTransfer. The CUBE HA tested here is layer 2 box to box CUBE redundancy. 2017 Cisco Systems, Inc. All rights reserved.Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.comPage 7 of 70

ConfigurationConfiguring Cisco Unified Border ElementNetwork InterfaceThe IP address used are for illustration only, the actual IP address can vary. The Active/Standby pairshare the same virtual IP address and continually exchange status messages.Figure 2 High Availability topology 2017 Cisco Systems, Inc. All rights reserved.Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.comPage 8 of 70

CUBE 1:interface GigabitEthernet0/0/0ip address 10.64.4.19 255.255.0.0media-type rj45negotiation auto!interface GigabitEthernet0/0/1no ip addressshutdownmedia-type rj45negotiation auto!interface GigabitEthernet0/0/2ip address 10.80.22.74 255.255.255.0media-type rj45negotiation autoredundancy rii 1redundancy group 1 ip 10.80.22.100 exclusive!interface GigabitEthernet0/0/3description Wan Interfaceip address 192.65.79.140 255.255.255.128media-type rj45negotiation autoredundancy rii 2redundancy group 1 ip 192.65.79.155 exclusive! 2017 Cisco Systems, Inc. All rights reserved.Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.comPage 9 of 70

CUBE 2:! interface GigabitEthernet0/0/0ip address 10.64.4.20 255.255.0.0media-type rj45negotiation auto!interface GigabitEthernet0/0/1no ip addressshutdownmedia-type rj45negotiation auto!interface GigabitEthernet0/0/2description WANip address 10.80.22.75 255.255.255.0media-type rj45negotiation autoredundancy rii 1redundancy group 1 ip 10.80.22.100 exclusive!interface GigabitEthernet0/0/3description Wan Interfaceip address 192.65.79.141 255.255.255.128media-type rj45negotiation autoredundancy rii 2redundancy group 1 ip 192.65.79.155 exclusive! 2017 Cisco Systems, Inc. All rights reserved.Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.comPage 10 of 70

Global Cisco UBE settingsIn order to enable Cisco UBE IP2IP SBC functionality, following command has to be entered:voice service voipip address trusted listno ip address trusted authenticatertcp keepaliveaddress-hidingmode border-element license capacity 20allow-connections sip to sipredundancy-group 1no supplementary-service sip moved-temporarilyno supplementary-service sip refersupplementary-service media-renegotiateredirect ip2ipfax protocol pass-through g711ulawsipbind control source-interface GigabitEthernet0/0/2bind media source-interface GigabitEthernet0/0/2session refreshasserted-id paiearly-offer forcedmidcall-signaling passthrupass-thru subscribe-notify-events allpass-thru content unsuppsip-profiles inboundsip-profiles 1ExplanationCommandDescriptionallow-connections sip to sipAllow IP2IP connections between two SIP call legsredundancy-group 1Enable High Availability for the VoIP servicertcp keepaliveEnables the CUBE to send rtcp keepalive packets for the session keepalive 2017 Cisco Systems, Inc. All rights reserved.Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.comPage 11 of 70

fax protocolSpecifies the fax protocolearly-offer forcedEnables SIP Delayed-Offer to Early-Offer globallyasserted-idSpecifies the privacy header in the outgoing SIP requests and response messagesCodecsG729 is used primarily towards CenturyLink until specified otherwise.voice class codec 1codec preference 1 g711ulawcodec preference 2 g729r8voice class codec 2codec preference 1 g729r8codec preference 2 g711ulawDial peerOutbound Dial-peer to CenturyLink:dial-peer voice 100 voipdescription Outbound peer to CenturyLink Primarytranslation-profile outgoing ctldestination-pattern .Tsession protocol sipv2session target ipv4: Trunk1 IP :5100voice-class codec 1voice-class sip early-offer forcedvoice-class sip profiles 100voice-class sip tenant 10voice-class sip bind control source-interface GigabitEthernet0/0/3voice-class sip bind media source-interface GigabitEthernet0/0/3dtmf-relay rtp-ntefax protocol pass-through g711ulaw 2017 Cisco Systems, Inc. All rights reserved.Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.comPage 12 of 70