Configuring the Sonus SBC 5000 with Cisco Unified Communication Manager 8.6 for Verizon Deployments. Application Notes Rev. 1.0

Transcription

1 Configuring the Sonus SBC 5000 with Cisco Unified Communication Manager 8.6 for Verizon Deployments Application Notes Rev. 1.0 Last Updated: March 9, 2015 Revision History Revision Date Revised By Comments 1 3/1/2015 Paul Axtell Initial Publication 2015 Sonus Networks, Inc

2 Contents 1 Document Overview Glossary Introduction Audience Requirements (example) Reference Configuration... 6 Network Topology Features Tested with Verizon SIP Trunk Interworking Architecture Cisco Functionality Cisco Components... 8 Cisco Unified Communication Manager (CUCM) Configuring the Sonus SBC 5000 Session Border Controller SBC Naming Conventions SBC Configuration Workflow Global Configuration UDP Port Range for RTP (media) DSP Resources Codec Entry for G.711U_20ms_2833_T Codec Entry for G.711A_20ms_2833_T Codec Entry for G729A_20ms_2833_T Address Reachability Service Profile Internal Side SBC Configuration IP Static Route SBC Configuration for Cisco UCM Profile Configuration Packet Service Profile (PSP) IP Signaling Profile (IPSP) Address Context Configuration Zone SIP Signaling Port IP Peer SIP Trunk Group Sonus Networks 2

3 4.6 External Side SBC Configuration IP Interface Group IP Static Route SBC Configuration for SIP Carrier Profile Configuration Packet Service Profile (PSP) IP Signaling Profile (IPSP) Address Context Configuration Zone SIP Signaling Port IP Peer SIP Trunk Group Global Call Routing Configuration Element Routing Priority Cisco Routing Routing Label SIP Carrier Routing Routing Label Routing Cisco Configuration CUCM 8.6 Configuration Settings Login to CUCM SIP Trunk Security Profile SIP Profile Create a New TG Create New Route Group Create a New Route List Create a New Route Pattern Sonus Networks 3

4 1 Document Overview These Application Notes describe the configuration steps required for the Sonus Session Border Controller 5000 series (5100, 5110, 5200, 5210) to interoperate with the Cisco UCM system. SBC 5000 series functionality was compliance tested using a VZ SIP trunk to Cisco UCM Server from an SBC The objective of this document is to describe the procedure to be followed during interoperability testing of the SBC 5000 series and Cisco UCM with a Verizon Sip trunk. Testing was based on a test plan provided by Verizon for the functionality required for certification as a solution supported on the IP network. The interoperability tested was between SIP and PSTN clients, Cisco UCM, Verizon SIP trunk and Sonus SBC For additional information on Sonus SBC 5000 series, visit For additional information on Cisco, visit Glossary AOC B2B UA CP CPD CPE CTI DNIS IP MS PBX PSX SDOP SIP UUI Term Advice Of Charge Back to Back User Agent Calling Party Call Progress Detection Definition Customer Premise Equipment Cisco SIP Server is the CPE device in this case. Computer Telephony Integration Dialed Number Identification Service Internet Protocol Media Server Private Branch Exchange Policy Server Exchange Signaled Digits Out-Pulsed Session Initiation Protocol User to User Information 4

5 2 Introduction This document guidance for configuring the Sonus SBC 5000 Series (Session Border Controller) when connecting to the Cisco SIP Server and other internal PBX systems. The Sonus SBC 5200 is a Session Border Controller that connects disparate SIP trunks, SIP PBXs, and communication applications within an enterprise. It can also be used as a SIP routing and integration engine. The Sonus SBC is the point of connection between the Cisco system and local PBX system that hosts internal SIP phones. The Sonus SBC is also the point of connection to external carrier SIP trunk providers for SIP carrier connection. In this case, the internal PBX is out of scope of this document. 2.1 Audience This technical document is intended for telecommunication engineers for the purpose of configuring both the Sonus SBC 5xx0 and aspects of the Cisco UCM products. There will be steps that require navigating the thirdparty and Sonus SBC Command Line Interface (CLI). Understanding the basic concepts of TCP/UDP, IP/Routing, and SIP/RTP are also necessary to complete the configuration and for troubleshooting, if necessary. Technical support on SBC 5000 can be obtained through the following: Phone: (978) or (888) (Toll-free) Web: Requirements (example) The following equipment and software was used for the sample configuration provided: Sonus Equipment Type Version SBC 5200 BMC BIOS ConnexIP OS SonusDB EMA SBC SBC 5000 V V V R000 V R000 V R000 V R000 3rd Party Equipment Type Version Cisco UCM SIP Server Cisco 7942G SIP phone Boot Load: tnp bin Load File: SIP SR4-1S Canon Faxphone L100 Fax machine Venta Fax Fax softphone I 5

6 2.3 Reference Configuration A simulated enterprise site comprising the following elements: Cisco Unified Communication Manager (CUCM) 8.6 and an SBC 5200 system running software version R0. Verizon SIP trunks were used to connect the SBC to the Cisco UCM. Network Topology The following figure represents the equipment that was used for the Cisco integration and certification testing. The Sonus SBC 5200 was used to route the calls to and from a Verizon SIP trunk to and from the Cisco UCM and SIP endpoints, depending on the test being run. Cisco 10.5 Sonus SBC 5000 Internal IP Network Verizon Figure 2.1 Network Topology 6

7 2.4 Features Tested with Verizon SIP Trunk The following features were tested and supported with the Verizon IP SIP Trunk Enhanced Features service: Basic Call Tests Hop-off to PSTN Basic Call Tests Hop-on from PSTN International Call Simultaneous Calls Calling Number Privacy Call Hold and Resume PBX-Based 3-Way Call Conference PBX-Based Unattended Call Transfer PBX-Based Attended Call Transfer PBX-Based Call Forwarding PBX-Based Meet-Me Conference Bridge FAX Tests with T.38 (SG3 FAX Machine at CPE Site) FAX Tests with G.711 (SG3 FAX Machine at CPE Site) Network-based Call Forward Network-Based Call Forwarding Busy (CFB) Network-Based Call Forwarding - Ring No Answer (CFRNA) Network-Based Call Forwarding - Not Reachable (CF-NR) Network-Based Blind Call Transfer Network-Based Consultative Call Transfer (Attended) 7

8 3 Interworking Architecture This section is a discussion of general architectural issues. 3.1 Cisco Functionality General Cisco functionality provides the UCM application All the SIP Phones will register with Cisco Unified Communication Manager 3.2 Cisco Components Cisco Unified Communication Manager (CUCM) Cisco Unified Communications Manager software is the call-processing component of the Cisco Unified Communications system. Cisco Unified Communications Manager extends enterprise telephony features and capabilities to packet telephony network devices such as IP phones, media processing devices, voice over IP (VoIP) gateways, and multimedia applications. Additional services such as unified messaging, multimedia conferencing, collaborative contact centers, and interactive multimedia response systems are made possible through Cisco Unified Communications Manager open telephony APIs. Cisco Unified Communications Manager offers a suite of integrated voice applications and utilities, including the Cisco Unified Communications Manager Attendant Console, an ad-hoc conferencing application, the Cisco Unified Communications Manager Bulk Administration Tool, the Cisco Unified Communications Manager CDR (call detail record) Analysis and Reporting Tool, the Cisco Unified Communications Manager Real-Time Monitoring Tool, and the Cisco Unified Communications Manager Assistant application. The dial plan feature in Unified Communications Manager enable you to: Route calls based on the physical location context of the caller. Represent calling and called party numbers in a global form such as that described by the International Telecommunications Union's E.164 recommendation. Present calls to users in a format based on local dialing habits. Present calls to external networks (for example, the PSTN) in a manner compatible with the local requirements for calling party number, called party number, and their respective numbering types. Derive the global form of the calling party number on incoming calls from gateways, based on the calling number digits and the numbering type. For additional information, go to: 8

9 4 Configuring the Sonus SBC 5000 Session Border Controller This section describes how to use the Sonus Command Line Interface (CLI) to configure and manage the SBC 5000 Series session border controller. The SBC can also be configured and managed using the Embedded Management Application (EMA), which is a Web-based interface management system for the Sonus SBC 5000 Series. However, documentation of the equivalent configuration steps via EMA is beyond the scope of this document. Internal External IP Interface Group: IPIG_INTERNAL Zone: ZONE_INTERNAL SIP Port: :5060 SIP TrunkGroup: CISCO-CUCM-10.5 IP Interface Group: IPIG_EXTERNAL Zone: ZONE_EXTERNAL SIP Port: :5060 SIP TrunkGroup: CARRIER_VZ Cisco UCM 10.5 CISCO-CUCM-10.5 Sonus 5200 CARRIER-VZ Verizon SBC Figure 4.1 SBC 5000 SIP Trunk Diagram 4.1 SBC Naming Conventions Unique address contexts are needed only when using overlapping IP address spaces. This deployment assumes no such overlapping IP space; thus, all configurations are in Address Context default. 9

10 4.2 SBC Configuration Workflow ---- Global Configuration ----Media Port Range ---- DSP Resources ----Codec Entry ---- Internal side Configuration ----IP Interface and IP Interface Group ----IP Static Routes ---- Cisco Configuration ----Configuring Profiles ----Packet Service Profile ----IP Signaling Profile ----Configuring Address Context ----Zone ----SIP Signaling Port ----IP Peer ----SIP Trunk Group ---- Internal Agent Side Configuration (optional) ----Configuring Profiles ----Packet Service Profile ----IP Signaling Profile ----Configuring Address Context ----Zone ----SIP Signaling Port ----IP Peer ----SIP Trunk Group ---- External side Configuration ----IP Interface and IP Interface Group ----IP Static Routes ---- Carrier Configuration ----Configuring Profiles ----Packet Service Profile ----IP Signaling Profile ----Configuring Address Context ----Zone ----SIP Signaling Port ----IP Peer ----SIP Trunk Group ---- Remote Agent Configuration ----Configuring Profiles ----Packet Service Profile ----IP Signaling Profile 10

11 ----Configuring Address Context ----Zone ----SIP Signaling Port ----IP Peer ----SIP Trunk Group ---- Global Call Routing Configuration ----Cisco Side Routing ----Routing Label ----Carrier Side Routing ----Routing Label ----Agent Routing ----Routing 4.3 Global Configuration UDP Port Range for RTP (media) The Sonus SBC 5000 series defaults to using a UDP port range of for RTP (media) traffic. Many enterprise networking devices, including security devices, may assume a range of The following configuration modifies the SBC to work within the designated VZ range with no changes to the existing devices. This configuration is optional for the SBC but required by VZ. set system media mediaportrange baseudpport maxudpport DSP Resources Ensure that the SBC has DSP resources allocated for compression/transcoding. Packet Service Profiles, configured later in this document, use Conditional Transcoding, which only function properly if the SBC has been deployed with DSP resources that have been allocated for transcoding. set system mediaprofile compression 90 tone 10 11

12 Codec Entry for G.711U_20ms_2833_T38 Create Codec Entry for the G711u codec with DTMF Relay configured for RFC2833 so DTMF information is carried in the audio path as RTP events (e.g method). G711U_20ms_2833_T38 G711U Name of codec entry Codec selected 20 Packet size in milliseconds rfc2833 Type of DTMF Relay chosen: carriers DTMF in signaling protocol set profiles media codecentry G711U_20ms_2833_T38 codec g711 law ULaw packetsize 20 set profiles media codecentry G711U_20ms_2833_T38 dtmf relay rfc2833 set profiles media codecentry G711U_20ms_2833_T38 fax tonetreatment faxrelay Codec Entry for G.711A_20ms_2833_T38 Create Codec Entry for the G711a codec with DTMF Relay configured for RFC2833 so DTMF information is carried in the audio path as RTP events (e.g method). G711A_20ms_2833_T38 G711A Name of codec entry Codec selected 20 Packet size in milliseconds rfc2833 Type of DTMF Relay chosen: carriers DTMF in signaling protocol set profiles media codecentry G711A_20ms_2833_T38 codec g711 law ALaw packetsize 20 set profiles media codecentry G711A_20ms_2833_T38 dtmf relay rfc2833 set profiles media codecentry G711A_20ms_2833_T38 fax tonetreatment faxrelay 12

13 Codec Entry for G729A_20ms_2833_T38 Create a Codec Entry for the G729 codec with DTMF Relay configured for RFC2833 so DTMF information is carried in the audio path as RTP events (e.g method). G729A_20ms_2833_T38 G729A Name of codec entry Codec selected 20 Packet size in milliseconds rfc2833 Type of DTMF Relay chosen: carriers DTMF in signaling protocol set profiles media codecentry G729A_20ms_2833_T38 codec g729a packetsize 20 set profiles media codecentry G729A_20ms_2833_T38 dtmf relay rfc2833 set profiles media codecentry G729A_20ms_2833_T38 fax tonetreatment faxrelay Address Reachability Service Profile Create an Address Reachability Service (ARS) Profile for Cisco servers, which is applied to the Cisco SIP Trunk Group. ARS allows peers to be blacklisted when unresponsive, allowing faster route-advancing. CISCO_ARS blklistalgorithms timeouts,retryafter recoveryalgorithm probe Name of Address Reachability Service (ARS) Profile Types of algorithms used for blacklisting endpoints: SIP INVITE timeouts and 503 w/retry-after response. Type of recovery mechanism for blacklisted endpoints. Probe mechanism is a SIP OPTIONS message. set profiles services siparsprofile CISCO_ARS set profiles services siparsprofile CISCO_ARS blklistalgorithms timeouts,retryafter set profiles services siparsprofile CISCO_ARS blklistalgretryaftertype sip-503 set profiles services siparsprofile CISCO_ARS blklistalgtimeoutstype sip-invite set profiles services siparsprofile CISCO_ARS blklistalgtimeoutsnumtimeouts 4 set profiles services siparsprofile CISCO_ARS blklistalgtimeoutsduration 120 set profiles services siparsprofile CISCO_ARS recoveryalgorithm probe set profiles services siparsprofile CISCO_ARS recoveryalgprobeinterval 30 set profiles services siparsprofile CISCO_ARS recoveryalgprobenumresponses 6 set profiles services siparsprofile CISCO_ARS recoveryalgprobeduration

14 4.4 Internal Side SBC Configuration The following configuration is for a Sonus 52x0 system using the Media 0 port for internal connectivity. SBC 5000 media ports do not have dedicated internal/external roles and, while recommended, the Sonus convention does not need to be followed. For more information on Media Port deployment options or other network connectivity queries, refer to the SBC 5000 Network Deployment Guide or contact your local Sales team for information regarding the Sonus Network Design Administrator s Guide (NDAG) professional services offerings. Create an IP Interface Group and assign it interfaces, including IP addresses. default IPIG_INTERNAL LITTLE IPIF_INTERNAL pkt0 Name of the address context IP Interface Group name for the internal side of the SBC SBC element name Name for IP Interface (on pkt0) Gigabit Ethernet port used for internal signaling and media IP address for the first internal media port 26 IP subnet prefix (subnet mask in CIDR format) set addresscontext default ipinterfacegroup IPIG_INTERNAL set addresscontext default ipinterfacegroup IPIG_INTERNAL ipinterface IPIF_INTERNAL cename LITTLE set addresscontext default ipinterfacegroup IPIG_INTERNAL ipinterface IPIF_INTERNAL portname pkt0 set addresscontext default ipinterfacegroup IPIG_INTERNAL ipinterface IPIF_INTERNAL ipaddress prefix 26 set addresscontext default ipinterfacegroup IPIG_INTERNAL ipinterface IPIF_INTERNAL mode inservice state enabled IP Static Route Create a default route to the subnet s IP nexthop for the IP Interface Group and Interfaces. default Default route Name of the address context 0 IP subnet prefix (subnet mask in CIDR format) IP Nexthop for subnet IPIG_INTERNAL IPIF_INTERNAL IP Interface Group name for the internal side of the SBC Name for IP Interface (on pkt0) 100 Preference of the route within the Interface Group set addresscontext default staticroute IPIG_INTERNAL IPIF_INTERNAL preference

15 4.5 SBC Configuration for Cisco UCM Profile Configuration Packet Service Profile (PSP) Create a Packet Service Profile (PSP) for the Cisco SIP trunk with a single codec specified. The PSP is specified in the SIP Trunk Group configuration. PSP_CISCO G729A_20ms_2833_T38 G711U_20ms_2833_T38 G711A_20ms_2833_T38 Conditional G729A, G771U, G711A differentdtmfrelay differentpacketsize Name of the Cisco PSP Use the codecs created earlier (global config section) Use the codecs created earlier (global config section) Use the codecs created earlier (global config section) Only transcode, if certain conditions are met Codecs on this leg Allow transcoding for different DTMF relay behaviors Allow transcoding for different codec packet sizes set profiles media packetserviceprofile PSP_CISCO set profiles media packetserviceprofile PSP_CISCO codec codecentry1 G729A_20ms_2833_T38 set profiles media packetserviceprofile PSP_CISCO codec codecentry2 G711U_20ms_2833_T38 set profiles media packetserviceprofile PSP_CISCO codec codecentry3 G711A_20ms_2833_T38 set profiles media packetserviceprofile PSP_CISCO preferredrtppayloadtypefordtmfrelay 101 set profiles media packetserviceprofile PSP_CISCO packettopacketcontrol transcode conditional set profiles media packetserviceprofile PSP_CISCO packettopacketcontrol codecsallowedfortranscoding thisleg g711u set profiles media packetserviceprofile PSP_CISCO packettopacketcontrol conditionsinadditiontonocommoncodec differentdtmfrelay enable differentpacketsize enable differentsilencesuppression enable 15

16 IP Signaling Profile (IPSP) Create a IP Signaling Profile (IPSP) for the Cisco SIP trunk. The IPSP will be specified in the SIP Trunk Group configuration and in order to relay a 4xx, 5xx and 6xx message from Cisco to Verizon, the flag below must be checked. If the Cisco doesn t send back a REASON header on a 4xx, 5xx or 6xx message this flag is not required to be enabled. If the REASON header is present the SBC will turn a 404 into a 502. CISCO_IPSP Status Code4xx6xx Name of the SIP Carrier IPSP Enable this flag to relay the error status codes (4xx, 5xx, or 6xx) in response to initial INVITE requests (does not apply to re- INVITEs). Provision this flag on the trunk group that receives the error response (the egress leg of the call). set profiles signaling ipsignalingprofile CISCO_IPSP set profiles signaling ipsignalingprofile CISCO_IPSP commonipattributes relayflags statuscode4xx6xx enable Address Context Configuration As mentioned earlier, as no overlapping IP addressing is used on the SBC in this document, all configuration will be under the default Address Context. default ZONE_INTERNAL Zone Name of the address context Name of the Cisco Zone 4 A unique numeric identifier (2-2048) for the zone set addresscontext default zone ZONE_INTERNAL id 4 SIP Signaling Port A SIP Signaling Port is a logical address permanently bound to a specific zone, and is used to send and receive SIP call signaling packets. default ZONE_INTERNAL IPIG_INTERNAL sip-udp, sip-tcp Name of the address context Name of the Cisco Zone IP Interface Group name for the internal side of the SBC Transport protocols allowed for SIP signaling to Cisco SIP IPv4 address for the SIP Signaling Address for the SBC 5060 SIP signaling TCP/UDP port of SBC 26 DiffServ Code Point value for SIP signaling traffic from SBC 16

17 set addresscontext default zone ZONE_INTERNAL sipsigport 15 ipinterfacegroup IPIG_ZONE_INTERNAL set addresscontext default zone ZONE_INTERNAL sipsigport 15 transportprotocolsallowed sip-udp,sip-tcp set addresscontext default zone ZONE_INTERNAL sipsigport 15 ipaddressv set addresscontext default zone ZONE_INTERNAL sipsigport 15 portnumber 5060 dscpvalue 26 set addresscontext default zone ZONE_INTERNAL sipsigport 15 state enabled mode inservice IP Peer Create an IP Peer with the signaling IP addresses of the Cisco SIP Servers and assign it to the Cisco Zone. The IP Peer entity is used on egress, while the ingressipprefix parameter in the siptrunkgroup entity is used on ingress, for determining the applicable SIP Trunk Group. These two IP Peers represent an active-standby pair of Cisco SIP Servers for redundancy. default ZONE_INTERNAL PEER-CISCO-10 Name of the address context Name of the Cisco Zone Name of the Cisco IP Peer IP Address of Cisco SIP Server 5060 SIP signaling TCP/UDP port of Cisco SIP Server set addresscontext default zone ZONE_INTERNAL ippeer PEER-CISCO-10 ipaddress ipport 5060 SIP Trunk Group Create a SIP Trunk Group ZONE_INTERNAL for the Cisco SIP Server and assign the corresponding Profiles configured earlier in this document. default ZONE_INTERNAL Name of the address context Name of the Cisco Zone CISCO-CUCM-8.6 Name of the SIP Trunk Group for the Cisco SIP IPIG_ZONE_INTERNAL IP Interface Group name for the ZONE_INTERNAL side of the SBC IP Address of Cisco SIP Server 32 IP prefix (subnet mask in CIDR format) PSP_CISCO CISCO_ARS Earlier created PSP is applied in the Trunk Group ARS Profile 17

18 set addresscontext default zone ZONE_INTERNAL siptrunkgroup CISCO-CUCM-8.6 media mediaipinterfacegroupname ZONE_INTERNAL set addresscontext default zone ZONE_INTERNAL siptrunkgroup CISCO-CUCM-8.6 ingressipprefix set addresscontext default zone ZONE_INTERNAL siptrunkgroup CISCO-CUCM-8.6 policy signaling ipsignalingprofile CISCO_IPSP set addresscontext default zone ZONE_INTERNAL siptrunkgroup CISCO-CUCM-8.6 policy media packetserviceprofile PSP_CISCO set addresscontext default zone ZONE_INTERNAL siptrunkgroup CISCO-CUCM-8.6 services siparsprofile CISCO_ARS set addresscontext default zone ZONE_INTERNAL siptrunkgroup CISCO-CUCM-8.6 signaling methods publish reject register reject subscribe reject set addresscontext default zone ZONE_EXTERNAL siptrunkgroup CISCO-CUCM-8.6 signaling rel100support disabled set addresscontext default zone ZONE_INTERNAL siptrunkgroup CISCO-CUCM-8.6 state enabled mode inservice 18

19 4.6 External Side SBC Configuration IP Interface Group The following configuration is for a Sonus 52x0 system using Media 2 port for external connectivity and Media Port 3 due to the Verizon requirement of separating RTP from the signaling VPN tunnel. If this requirement is not levied on all Verizon SIP trunks then it s possible to use one media port for both signaling and RTP. SBC 5000 Media ports do not have dedicated internal/external roles and, while recommended, the Sonus convention does not need to be followed. For more information on Media port deployment options or other network connectivity queries, refer to the SBC 5000 Network Deployment Guide or contact your local sales team for information regarding the Sonus Network Design Administrator s Guide (NDAG) professional services offerings. Create an IP Interface Group and assign interfaces; including IP addresses. default IPIG_EXTERNAL LITTLE IPIF_EXTERNAL pkt2 Name of the address context IP Interface Group name for the external side of the SBC SBC element name Name for IP Interface (on pkt2) Gigabit Ethernet port used for external signaling and media IP address for the first external media port 26 IP subnet prefix (subnet mask in CIDR format) Create an IP Interface Group for RTP only and assign interfaces; including IP addresses. default Name of the address context IPIG_EXTERNAL_2 IP Interface Group name for the external side of the SBC LITTLE SBC element name IPIF_EXTERNAL_2 Name for IP Interface (on pkt3) Pkt3 Gigabit Ethernet port used for external signaling and media IP address for the first external media port 28 IP subnet prefix (subnet mask in CIDR format) 19

20 set addresscontext default ipinterfacegroup IPIG_EXTERNAL set addresscontext default ipinterfacegroup IPIG_EXTERNAL ipinterface IPIF_EXTERNAL cename LITTLE set addresscontext default ipinterfacegroup IPIG_EXTERNAL ipinterface IPIF_EXTERNAL portname pkt2 set addresscontext default ipinterfacegroup IPIG_EXTERNAL ipinterface IPIF_EXTERNAL ipaddress prefix 26 set addresscontext default ipinterfacegroup IPIG_EXTERNAL ipinterface IPIF_EXTERNAL mode inservice state enabled set addresscontext default ipinterfacegroup IPIG_EXTERNAL_2 set addresscontext default ipinterfacegroup IPIG_EXTERNAL_2 ipinterface IPIF_EXTERNAL_2 cename LITTLE set addresscontext default ipinterfacegroup IPIG_EXTERNAL_2 ipinterface IPIF_EXTERNAL_2 portname pkt3 set addresscontext default ipinterfacegroup IPIG_EXTERNAL_2 ipinterface IPIF_EXTERNAL_2 ipaddress prefix 28 set addresscontext default ipinterfacegroup IPIG_EXTERNAL_2 ipinterface IPIF_EXTERNAL_2 mode inservice state enabled IP Static Route Create a default route to the subnet s IP next hop for the Interface and IP Interface Group. default Default route Name of the address context 0 IP subnet prefix (subnet mask in CIDR format) IP Nexthop for subnet IPIG_INTERNAL IPIF_INTERNAL IP Interface Group name for the external side of the SBC Name for IP Interface (on pkt0) 100 Preference of the route within the Interface Group Create a default route to the subnet s IP next hop for the Interface and IP Interface Group. default Name of the address context Default route 0 IP subnet prefix (subnet mask in CIDR format) IP Nexthop for subnet IPIG_EXTERNAL IP Interface Group name for the external side of the SBC IPIF_EXTERNAL Name for IP Interface (on pkt2) 100 Preference of the route within the Interface Group 20

21 Create a default route to the subnet s IP next hop for the Interface and IP Interface Group. default Name of the address context Default route 0 IP subnet prefix (subnet mask in CIDR format) IP Nexthop for subnet IPIG_EXTERNAL_2 IP Interface Group name for the external side of the SBC IPIF_EXTERNAL_2 Name for IP Interface (on pkt2) 100 Preference of the route within the Interface Group set addresscontext default staticroute IPIG_EXTERNAL IPIF_EXTERNAL preference 100 set addresscontext default staticroute IPIG_INTERNAL IPIF_INTERNAL preference 100 set addresscontext default staticroute IPIG_EXTERNAL_2 IPIF_EXTERNAL_2 preference

22 4.7 SBC Configuration for SIP Carrier This section only applies if callers ingress the enterprise via a SIP Carrier. If callers ingress the enterprise via local PSTN circuits (PRI or CAS trunks), then a SIP Trunk Group needs to be built to whatever Media Gateway is terminating the PSTN circuits (such as a Sonus GSX9000 Media Gateway). This section is also for a generic SIP Carrier. If one is available, refer to the Sonus SBC 5000 Application Note that is specific to your carrier. Profile Configuration Packet Service Profile (PSP) Create a Packet Service Profile (PSP) for the SIP trunk with a single codec specified. The PSP is specified within the SIP Trunk Group configuration. PSP_VZ G729A_20ms_2833_T38 G711U_20ms_2833_T38 G711A_20ms_2833_T38 Conditional G729A, G711U, G711A differentdtmfrelay differentpacketsize Name of the PSP for SIP Carrier Use of codec created earlier (global config section) Use of codec created earlier (global config section) Use of codec created earlier (global config section) Only transcode if certain conditions are met Codecs on this leg Allow transcoding for different DTMF relay behaviors Allow transcoding for different codec packet sizes set profiles media packetserviceprofile PSP_VZ set profiles media packetserviceprofile PSP_VZ codec codecentry1 G729A_20ms_2833_T38 set profiles media packetserviceprofile PSP_VZ codec codecentry2 G711U_20ms_2833_T38 set profiles media packetserviceprofile PSP_VZ codec codecentry3 G711A_20ms_2833_T38 set profiles media packetserviceprofile PSP_VZ preferredrtppayloadtypefordtmfrelay 101 set profiles media packetserviceprofile PSP_VZ packettopacketcontrol transcode conditional set profiles media packetserviceprofile PSP_VZ packettopacketcontrol codecsallowedfortranscoding thisleg g711u set profiles media packetserviceprofile PSP_VZ packettopacketcontrol conditionsinadditiontonocommoncodec differentdtmfrelay enable differentpacketsize enable 22

23 IP Signaling Profile (IPSP) Create a IP Signaling Profile (IPSP) for the SIP Carrier SIP trunk. The IPSP is specified within the SIP Trunk Group configuration. VZ_IPSP Disable2806Compliance NoSdpIn180Supported Suppress183WithoutSdp Name of the SIP Carrier IPSP If enabled, the 2806 Compliance Code is disabled, and no phone context or user=phone parameters are signaled in egress messages. By default, the SBC includes SDP in outbound 180 messages. When enabled, the SBC does not include SDP in outbound 180 messages. It converts the 180 message to a 183 message instead. When disabled, the SBC includes SDP in outbound 180 messages. Never send 183 without SDP. set profiles signaling ipsignalingprofile VZ_IPSP set profiles signaling ipsignalingprofile VZ_IPSP egressipattributes flags disable2806compliance enable set profiles signaling ipsignalingprofile VZ_IPSP ingressipattributes flags nosdpin180supported eable set profiles signaling ipsignalingprofile VZ_IPSP ingressipattributes flags suppress183withoutsdp enable Address Context Configuration As mentioned earlier, as no overlapping IP addressing is used on the SBC in this document, all configuration is done under the default Address Context. Zone This Zone groups the set of objects used for the communication to the SIP Carrier. default ZONE_EXTERNAL Name of the address context Name of the SIP Carrier Zone 20 A unique numeric identifier (2-2048) for the zone set addresscontext default zone ZONE_EXTERNAL id 20 23

24 SIP Signaling Port A SIP Signaling Port is a logical address permanently bound to a specific zone, and is used to send and receive SIP call signaling packets. In this case, it is bound to the SIP Carrier zone and will send and receive SIP packets for the SIP Carrier. NOTE: Verizon requires UDP on its SIP trunk therefore only udp is selected for the SIP signaling port. default Name of the address context ZONE_EXTERNAL Name of the SIP Carrier Zone 4 A unique numeric identifier (1-2048) for the signaling port IPIG_EXTERNAL IP Interface Group name for the external side of the SBC sip-udp Transport protocols allowed for SIP signaling to SIP Carrier IPv4 address for the SIP Signaling Address for the SBC 5060 SIP signaling TCP/UDP port of SBC 46 DiffServ Code Point value for SIP signaling traffic from SBC set addresscontext default zone ZONE_EXTERNAL sipsigport 20 ipinterfacegroup IPIG_EXTERNAL set addresscontext default zone ZONE_EXTERNAL sipsigport 20 transportprotocolsallowed sip-udp set addresscontext default zone ZONE_EXTERNAL sipsigport 20 ipaddressv set addresscontext default zone ZONE_EXTERNAL sipsigport 20 portnumber 5060 dscpvalue 46 set addresscontext default zone ZONE_EXTERNAL sipsigport 20 state enabled mode inservice IP Peer Create an IP Peer with the signaling IP address of the SIP Carrier peer and assign it to the SIP Carrier zone. The IP Peer entity is used on egress. The ingressipprefix parameter in the siptrunkgroup object is used on ingress for determining the applicable SIP Trunk Group. default ZONE_EXTERNAL PEER_CARRIER_VZ Name of the address context Name of the SIP Carrier Zone Name of the SIP Carrier IP Peer IP Address of SIP Carrier SIP Server 5060 SIP signaling TCP/UDP port of SIP Carrier SIP Server set addresscontext default zone ZONE_EXTERNAL ippeer PEER_CARRIER_VZ ipaddress ipport

25 SIP Trunk Group Create a SIP Trunk Group externally for the SIP Carrier and assign the corresponding Profiles configured earlier in this document. default ZONE_EXTERNAL CARRIER_VZ EXTERNAL_IPIG Name of the address context Name of the SIP Carrier Zone Name of the SIP Trunk Group for SIP Carrier IP Interface Group name for the external side of the SBC IP Address of SIP Carrier SIP Server 32 IP prefix (subnet mask in CIDR format) PSP_VZ Earlier created PSP is applied in the Trunk Group set addresscontext default zone ZONE_EXTERNAL siptrunkgroup CARRIER_VZ media mediaipinterfacegroupname IPIG_EXTERNAL set addresscontext default zone ZONE_EXTERNAL siptrunkgroup CARRIER_VZ ingressipprefix set addresscontext default zone ZONE_EXTERNAL siptrunkgroup CARRIER_VZ policy signaling ipsignalingprofile VZ_IPSP set addresscontext default zone ZONE_EXTERNAL siptrunkgroup CARRIER_VZ policy media packetserviceprofile PSP_VZ set addresscontext default zone ZONE_EXTERNAL siptrunkgroup CARRIER_VZ policy digithandling numberingplan NANP_ACCESS set addresscontext default zone ZONE_EXTERNAL siptrunkgroup CARRIER_VZ signaling methods publish reject register reject subscribe reject set addresscontext default zone ZONE_EXTERNAL siptrunkgroup CARRIER_VZ signaling rel100support disabled set addresscontext default zone ZONE_EXTERNAL siptrunkgroup CARRIER_VZ state enabled mode inservice 25

26 4.8 Global Call Routing Configuration A Routing Label (RL) is a user-named object that contains a list of one or more nexthop peers - defined as Routing Label Routes - that can reach a specified destination. A Routing Label Route (RLR) defines a single peer (Trunk Group + IP Peer) to which the call can be delivered. There may be many Routing Label Routes (1 to n) in a Routing Label. For each call placed to a destination Routing Label, the SBC advances through the list of peers (RLRs) until the call is completed or the list is exhausted. The RL's Prioritization Type determines the order in which the list is processed. Routing Labels are then assigned within the Route entity. Element Routing Priority The Element Routing Priority (ERP) Profile determines the priority or precedence for criteria used for call routing. An ERP profile is then applied in the Trunk Group entity. When providing support for SIP registration-based endpoints (sometimes referred to as an Access environment to differentiate it from Trunking), the SBC must have an ERP profile which prioritizes the Trunk Group entity above others. This allows routing of traffic from the ingress Trunk Group to the Trunk Group of the SIP Server for messages lacking called/calling numbers (e.g. SIP Registrations, etc ) This prioritization can be accomplished by creating a new ERP profile and applying it on all the Access-related Trunk Groups or by simply modifying the default ERP profile (DEFAULT_IP). This document modifies the default ERP profile. DEFAULT_IP Name of default object for the profile; in this case, the ERP. set profiles callrouting elementroutingpriority DEFAULT_IP entry nationaltype 2 entitytype none set profiles callrouting elementroutingpriority DEFAULT_IP entry nationaltype 1 entitytype trunkgroup set profiles callrouting elementroutingpriority DEFAULT_IP entry _private 2 entitytype none set profiles callrouting elementroutingpriority DEFAULT_IP entry _private 1 entitytype trunkgroup set profiles callrouting elementroutingpriority DEFAULT_IP entry nationaloperator 2 entitytype none set profiles callrouting elementroutingpriority DEFAULT_IP entry nationaloperator 1 entitytype trunkgroup set profiles callrouting elementroutingpriority DEFAULT_IP entry transit 2 entitytype none set profiles callrouting elementroutingpriority DEFAULT_IP entry transit 1 entitytype trunkgroup set profiles callrouting elementroutingpriority DEFAULT_IP entry carriercutthrough 2 entitytype none set profiles callrouting elementroutingpriority DEFAULT_IP entry carriercutthrough 1 entitytype trunkgroup set profiles callrouting elementroutingpriority DEFAULT_IP entry localoperator 2 entitytype none set profiles callrouting elementroutingpriority DEFAULT_IP entry localoperator 1 entitytype trunkgroup set profiles callrouting elementroutingpriority DEFAULT_IP entry username 2 entitytype none set profiles callrouting elementroutingpriority DEFAULT_IP entry username 1 entitytype trunkgroup set profiles callrouting elementroutingpriority DEFAULT_IP entry internationaloperator 2 entitytype none set profiles callrouting elementroutingpriority DEFAULT_IP entry internationaloperator 1 entitytype trunkgroup set profiles callrouting elementroutingpriority DEFAULT_IP entry longdistanceoperator 2 entitytype none 26

27 set profiles callrouting elementroutingpriority DEFAULT_IP entry longdistanceoperator 1 entitytype trunkgroup set profiles callrouting elementroutingpriority DEFAULT_IP entry othercarrierchosen 2 entitytype none set profiles callrouting elementroutingpriority DEFAULT_IP entry othercarrierchosen 1 entitytype trunkgroup set profiles callrouting elementroutingpriority DEFAULT_IP entry internationaltype 2 entitytype none set profiles callrouting elementroutingpriority DEFAULT_IP entry internationaltype 1 entitytype trunkgroup set profiles callrouting elementroutingpriority DEFAULT_IP entry mobile 2 entitytype none set profiles callrouting elementroutingpriority DEFAULT_IP entry mobile 1 entitytype trunkgroup set profiles callrouting elementroutingpriority DEFAULT_IP entry test 2 entitytype none set profiles callrouting elementroutingpriority DEFAULT_IP entry test 1 entitytype trunkgroup Cisco Routing Routing Label Create a Routing Label with a single Routing Label Route to bind the Cisco SIP Trunk Group with the Cisco SIP IP Peer. RL_TO_CISCO Sequence Name of the Routing Label for Cisco SIP The prioritization of Routing Label Routes within a Routing Label 1 The first Routing Label Route within the Routing Label CISCO-CUCM-8.6 PEER-CISCO-8.6 Trunk Group for Cisco SIP IP Peer for Cisco SIP set global callrouting routinglabel RL_TO_CISCO routeprioritizationtype sequence action routes routinglabelroute 1 trunkgroup CISCO-CUCM-8.6 ippeer PEER-CISCO-8.6 inservice inservice 27

28 SIP Carrier Routing Routing Label Create a Routing Label with a single Routing Label Route to bind the SIP Carrier Trunk Group with the SIP Carrier IP Peers. RL_TO_CARRIER_VZ Sequence Name of the Routing Label for SIP Carrier The prioritization of Routing Label Routes within a Routing Label 1 The first Routing Label Route within the Routing Label CARRIER_VZ PEER_CARRIER_VZ Trunk Group for SIP Carrier IP Peer for SIP Carrier set global callrouting routinglabel RL_TO_CARRIER_VZ routeprioritizationtype sequence action routes routinglabelroute 1 trunkgroup CARRIER_VZ ippeer PEER_CARRIER_VZ inservice inservice Routing Routing is the final step in the SBC configuration which must be provisioned in order to send calls to the correct destination. Within the Route entity, all available Route Match Criteria are used to determine the most specific match which is linked to Routing Labels (destinations). The result of a Route match is a Routing Label. Routing Labels were created in earlier sections of this document. For the purposes of this Application Note, routing was kept simple and limited to lab scenarios. Only trunk group routing was applied for calls from/to Cisco and to/from carrier. Calls from the carrier trunk group CARRIER_VZ are routed to the Cisco servers (via the RL_TO_CISCO Route Label which maps to the CISCO-CUCM-8.6 Trunk Group and Cisco IP Peer) and calls from Cisco (via the RL_TO_CARRIER_VZ Route Label which maps to the CARRIER_VZ Trunk Group and carrier IP Peers) In practice, call routing configuration will likely revolve around the enterprise s dial plan. For specific help in planning and/or implementing your routing contact your local Sales team for information regarding the Sonus Routing Design (SSDB) professional services offerings. Create Route entries for Trunk Group routing with Matching Criteria and a Route Label destination. trunkgroup CARRIER_VZ LITTLE standard / username Sonus_NULL Sonus_NULL all all ALL The entity type for the route elementid1 for an entitytype of trunkgroup, value is the ingress trunk group elementid2 for an entitytype of trunkgroup, value is the SBC System Name in all upper case (not hostname / element name) The type of routing for the route Destination national number Destination country number Call Type Digit Type Time Range Profile (note the capitalization) 28

29 none Sonus_NULL RL_TO_CISCO Call Filter Profile Destination Domain Name Destination Routing Label set global callrouting route trunkgroup CARRIER_VZ LITTLE standard Sonus_NULL Sonus_NULL all all ALL none Sonus_NULL routinglabel RL_TO_CISCO trunkgroup CISCO-CUCM-8.6 LITTLE standard / username Sonus_NULL Sonus_NULL all all ALL none Sonus_NULL RL_TO_CARRIER_VZ The entity type for the route elementid1 for an entitytype of trunkgroup, value is the ingress trunk group elementid2 for an entitytype of trunkgroup, value is the SBC System Name in all upper case (not hostname / element name) The type of routing for the route Destination national number Destination country number Call Type Digit Type Time Range Profile (note the capitalization) Call Filter Profile Destination Domain Name Destination Routing Label set global callrouting route trunkgroup CISCO-CUCM-8.6 LITTLE standard Sonus_NULL Sonus_NULL all all ALL none Sonus_NULL routinglabel RL_TO_CARRIER_VZ 29

30 5 Cisco Configuration This section assumes that the CUCM 8.6 components have been installed. The user should be familiar with administration and configuration of CUCM 8.6. This section does not cover the installation of CUCM CUCM 8.6 Configuration Settings The CUCM 8.6 was configured per the details provided in the Cisco Configuration and Administration Guide: This guide is available online at the following location: In order to connect Cisco CUCM 8.6 PBX to the SBC 5000 the following objects must be created and properly associated. 1. Trunk Group (TG) 2. Route Group (RG) 3. Route List (RL) 4. Route Pattern (RP) Login to CUCM Login to the Administration Portal of the Communication Manager: 1. Enter a valid username and password. 2. Click Login. Figure 5.1 CUCM Administration Page 30

31 SIP Trunk Security Profile 1. From the menu bar, select System > Security Profile > SIP Trunk Security Profile. 2. Select the appropriate SIP Trunk Security Profile. 3. Select the appropriate transport type to be used. This certification utilized UDP between Cisco and the Sonus SBC. Figure 5.2 SIP Security Trunk Profile 31

32 SIP Profile From the menu bar, select Device > Device Settings > SIP Profile. Figure 5.3 SIP Profile 32

33 Figure 5.4 SIP Profile (cont d) 33

34 Figure 5.5 SIP Profile (cont d) Figure 5.6 SIP Profile (cont d) 34

35 Create a New TG From the menu bar: 1. Select Device > Trunk. 2. Click the Add New. 3. Select a Trunk Type. 4. Select a SIP Protocol. 5. Click Next. Figure 5.7 Trunk Group 35

36 Figure 5.8 Trunk Group (cont d) 36

37 Figure 5.9 Trunk Group (cont d) 37

38 Figure 5.10 Trunk Group (cont d) 38

39 Figure 5.11 Trunk Group (cont d) 39

40 From the menu bar: Create New Route Group 1. Select Call Routing > Route-Hunt > Route Group 2. Click Add New.. (Note that the TG must already be added and will be displayed as an Available Devices under the Find Devices to Add to Route Group area. 3. Select the appropriate TG. 4. Click Add to Route. Enter a Route Group Name (refer to CUCM 8.6 guide for more detail). Figure 5.12 Route Group 40

41 Create a New Route List From the menu bar: 1. Select Call Routing > Route-Hunt > Route List 2. Click Add New. 3. Enter the Name and. 4. Click Add Route Group. 5. On the next screen, select the Route Group that was just created (refer to CUCM 8.6 guide for more detail). Figure 5.13 Route List 41

42 Create a New Route Pattern From the menu bar: 1. Select Call Routing > Route-Hunt > Route Pattern. 2. Click Add New. 3. Enter the Route Pattern. 4. Click Save. Figure 5.14 Route Pattern 42

43 Figure 5.15 Route Pattern (cont d) 43