Application Notes Rev. 1.0 Last Updated: January 9, 2015

SBC 1000/2000 Series Configuration Guide with Cisco Unified Call Manager v9.1 for Level 3 Voice Complete SM SIP Trunk Deployments Application Notes Rev. 1.0 Last Updated: January 9, 2015

Contents 1 Document Overview... 1 1.1 SBC Overview... 1 2 Introduction... 2 2.1 Audience... 2 2.2 Requirements... 2 2.3 Reference Configuration... 3 3 Configuring Sonus SBC 1000 and SBC 2000 Series... 4 3.1 Overview... 4 3.2 External Peer Side SBC Configuration... 5 Node Interfaces... 5 Node Ports... 5 Logical interfaces... 5 SIP Profile... 6 Media Profile... 7 Media Lists... 8 SIP Server Tables... 9 Hosts Table... 9 Signaling Groups... 10 Call Routing Table... 10 Transformation Tables... 12 3.3 Internal Side SBC configuration... 13 Node Interfaces... 13 Node Ports... 13 SIP Profile... 14 Media Profiles... 15 Media Lists... 16 Signaling Group... 17 SIP Server Table... 18 Call Routing Table... 19 Transformation Tables... 20 3.4 Tenor SBC configuration... 21 SIP Profile... 21 Media Profiles... 22 Media Lists... 23 SIP Local Registrar Table... 24 Signaling Groups... 25 Call Routing Table... 26 Transformation Tables... 27 4 Configuration of Analog Tenor for use with Fax... 28 4.1 Summary... 28 Assumptions... 28 Basic Call Flow Example... 28 Dial Plan... 28 DNS... 29 Gateway... 29 SIP Signaling Group... 30 DN Channel Map... 32 Voice Codec... 33 Codec Profile... 34

IPRG... 34 CAS SG-Phone... 35 LCRG-Phone... 37 Analog Interface Phone... 37 4.2 TENOR REGISTRATION TO SBC... 38 Overview... 38 Create Local SIP Registrar for Tenor... 38 Check SIP User Registration... 38 Check Transport Protocol... 39 Create Tenor Translation Table and Entries... 39 Create Tenor Call Routing Group... 39 Create Tenor SIP Signal Group (Pop up summary)... 40 5 Cisco Unified Call Manager (CUCM) configuration... 41 5.1 CUCM 9.1 Configuration Settings... 41 Login to CUCM as Administrator.... 41 Create a New TG... 42 Create New Route Group... 42 Create a New Route List... 43 Create a New Route Pattern... 43

1 Document Overview These Application Notes describe the configuration steps required for the Sonus Session Border Controller (SBC) 1000 and SBC 2000 to interoperate with the Cisco Unified Call Manager v9.1 (CUCM 9.1) system and Level 3 Voice Complete SM. The objective of the document is to describe the configuration procedures to be followed during interoperability testing of SBC 1000 and SBC 2000 with CUCM 9.1 over Level 3 Voice Complete SM. For additional information on Sonus SBC 1000 and SBC 2000 series, visit http://www.sonus.net For additional information on CUCM 9.1, visit http://www.cisco.com For additional information on Level 3 Voice Complete SM, visit http://www.level3.com/en/products/voicecomplete/ 1.1 SBC Overview The Sonus SBC 1000 and SBC 2000 session border controllers have been designed to use the same application software, boot image and Survivable Branch Appliance (SBA) software. The SBCs differ in the number of physical Ethernet, ISDN, and analog port connections and also processing power but are otherwise viewed from a software standpoint as being the same. With this in mind, this particular effort was tested with an SBC 2000 but is fully applicable to an SBC 1000. 1

2 Introduction This document provides a configuration guide for Sonus SBC 1000/2000 Series (Session Border Controller) when connecting Level 3 Voice Complete SM and the CUCM 9.1. The Sonus SBC 1000 and SBC 2000 are Session Border Controllers that connect disparate SIP trunks, SIP PBXs, and communication applications within an enterprise. The SBC can also be used as a SIP routing and integration engine. The Sonus SBC is the point of connection between the Level 3 Voice Complete SM and the CUCM 9.1. 2.1 Audience This technical document is intended for telecommunication engineers with the purpose of configuring the Sonus SBC 1000 and SBC 2000 and aspects of the SIP trunk group together with the CUCM 9.1 product. There will be steps that require navigating the third-party and Sonus SBC Web browser user interface or WebUI. Understanding the basic concepts of IP/Routing and SIP/RTP is also necessary to complete the configuration and perform troubleshooting tasks, if required. This configuration guide is offered as a convenience to Sonus customers. The specifications and information regarding the product in this guide are subject to change without notice. All statements, information, and recommendations in this guide are believed to be accurate but are presented without warranty of any kind, express or implied, and are provided AS IS. Users must take full responsibility for the application of the specifications and information in this guide. Technical support on SBC 1000 and SBC 2000 can be obtained through the following: Phone: +1 888-391-3434 (Toll-free) or +1 978-614-8589 (Direct) Web: http://www.sonus.net/company/maintenance/log-trouble-tickets 2.2 Requirements The following equipment and software was used for the sample configuration provided: Sonus Equipment Type Version SBC 2000 SBC 2000 4.0.1 Build 356 Tenor AFM200 Analog VoIP Gateway P108-09-26 3rd Party Equipment Type Version Cisco Unified Call Manager IP-PBX 9.1.2.11900-12 Cisco IP Phone 7942 SIP Phone 4.0.7577.4066 Brother Fax Intellifax 775 N/A 2

2.3 Reference Configuration A simulated enterprise site consisting of a CUCM 9.1 and a Voice Complete SM SIP trunk group to Level 3 connected over the SBC 2000. A SIP group also allows the analog Tenor AFM200 to register to the SBC 2000. A standard fax is connected to the FXS port of the Tenor. The SBC 2000 was running software version 4.0.1, build 354 and the Tenor was running P108-09-26 code during testing. Figure 2.1 Network Topology The preceding figure represents the equipment used for the integration and certification testing. The SBC 2000 is used to route and facilitate calls between the Level 3 and the CUCM 9.1 system. The SBC 2000 under test has two Ethernet ports configured. The SBC 2000 can have up to four physical Ethernet ports and two physical T1/E1 ports. For more information on Media port deployment options or other network connectivity queries, refer to the SBC 2000 Network Deployment Guide or contact the local Sonus Sales Team for information regarding the Sonus Network Design professional services offerings. 3

3 Configuring Sonus SBC 1000 and SBC 2000 Series In this section, all settings used in the call testing are shown as seen in the WebUI or web browser user interface. For more detailed information on the parameters and the WebUI, please refer to the Administration and Configuration guides for the SBC 1000 and SBC 2000 in the documentation pages at: https://support.sonus.net/display/alldoc/sonus+product+documentation CUCM 9.1 10.35.180.108:5060 Internal/Private Signaling Group: To/From CM8 Call Routing: From CM9 CUCM Signaling Group SIP over TCP Signaling Group: To/From CM9 Call Routing: From CM9 10.35.177.228:5060 External/Public Signaling Group: To/From Level3 Call Routing: From Level3 63.145.56.61:5060 SIP over UDP 4.55.40.225:5060 Level3 SIP over UDP Tenor 10.160.186.162:5060 Signaling Group: To/From Tenor Call Routing: From Tenor FXS to FAX Fax Figure 3.1 SBC 2000 SIP Trunk Diagram 3.1 Overview The preceding network diagram shows the IP address configuration between the CUCM 9.1 system, the SBC 2000, and the Level 3 Voice Complete SM SIP trunk. Also, an optional fax configuration is depicted. There are several ways to implement a fax setup into a network but the simple scenario as shown in this diagram was implemented for testing faxes. The Tenor registers the assigned dialed numbers (DNs) configured on the Tenor to the SBC SIP Server table. A SIP Registrar and a Tenor SIP Signaling Group (SIP trunk) are configured on the SBC 2000. The Tenor configuration is covered in the following sections. 4

3.2 External Peer Side SBC Configuration Node Interfaces The Sonus SBC 1000/2000 WebUI allows the configuration of the Identification information, Physical Data Layer, and Networking Layer for the ports. Use the associated Logical Interface to configure the IP address or other IP parameter. Those settings can be modified using the Modify Ethernet IP task found under the Tasks tab. The following figure shows the settings for the Ethernet connections (SIP signaling/rtp) between the Sonus SBC 2000 and the Public internet (SIP Trunk) to Level 3. Node Ports Figure 3.2 External (public) Network Node Port Logical interfaces Figure 3.3 Logical Interface 1 5

SIP Profile SIP Profiles control the how the Sonus SBC 1000/2000 communicates with SIP devices. These control important characteristics such as: session timers, SIP Header customization, SIP timers, MIME payloads, and option tags. The following figure shows the default SIP profile used for the SBC 2000 for this testing effort. Figure 3.4 SIP profile 6

Media Profile Media Profiles specify the individual voice and fax compression codecs and their associated settings for inclusion into a Media List. Different codecs provide varying levels of compression, allowing one to reduce bandwidth requirements at the expense of voice quality. The following figures show the media profiles of the voice codecs used for the SBC 2000 in this testing effort. These figures are for reference only. Figure 3.5 Voice Codec G.711U Figure 3.6 Voice Codec G.729 Figure 3.7 T.38 Fax Codec 7

Media Lists The Media List shows the selected voice and fax compression codecs and their associated settings. Figure 3.8 Media List 8

SIP Server Tables SIP Server Tables contain information about the SIP devices connected to the Sonus SBC 1000/2000. The entries in the tables provide information about the IP addresses, ports, and protocols used to communicate with each SIP server. The entries also contain links to counters that are useful for troubleshooting. Figure 3.9 SIP Server Table Hosts Table The Hosts Table feature allows editing of the /etc/hosts file from the WebUI or through a REST interface. Each line in the hosts file contains one IP address and at least one host name. Hosts File Example: 127.0.0.1 localhost testux218 192.168.199.15 anon.who.com 192.168.72.99 somemachine.anywhere.com 192.168.99.215 anothermachine.nowhere.net This allows applications on the Sonus SBC 1000/2000, such as SIP Signaling Groups, AD, RADIUS, and so on to resolve FQDNs when a DNS server is not reachable. Sonus recommends that only a few, very critical, host-ip pairs be stored on the Sonus SBC 1000/2000. Figure 3.10 SIP Host Table 9

Signaling Groups Signaling Groups allow telephony channels to be grouped together for the purposes of routing and shared configuration. These groups are the entity to which calls are routed, as well as the location from which Call Routes are selected. These are also the location from which Tone Tables and Action Sets are selected. In the case of SIP, this will specify protocol settings and link to server, media and mapping tables. Figure 3.11 SIP Signaling Group to Level 3 Call Routing Table Call Routing allows calls to be carried between signaling groups, thus allowing calls to be carried between ports, and between protocols (like ISDN to SIP). Routes are defined by Call Routing Tables that allow for flexible 10

configuration of which calls will be carried, and also how the calls are translated. These tables are one of the central connection points of the system, linking Transformation Tables, Message translations, Cause Code Reroute, Tables, Media Lists and the three types of Signaling Groups (ISDN, SIP and CAS). Figure 3.12 Call Routing Table Level 3 to CM9 11

Transformation Tables Transformation Tables facilitate the conversion of names, numbers and other fields when routing a call. For example, transformations can convert a public PSTN number into a private extension number, or into a SIP address (URI). Every entry in a Call Routing Table requires a Transformation Table, and are sequentially selected from there. In addition, Transformation tables will be configurable as a reusable pool that Action Sets can reference. Figure 3.13 Transformation Table Match Number and Change Number Figure 3.14 Transformation Table - Pass-through 12

3.3 Internal Side SBC configuration Node Interfaces The Sonus SBC 1000/2000 allows configuration of the Identification information, physical data layer, and networking layer for the Ethernet ports. If the IP address must be changed, configure the associated Logical Interface or use the Modify Ethernet IP task found under the Tasks tab. The following figures show the settings for the Ethernet connection between the Sonus SBC 2000 and CUCM 9.1 Node Ports Figure 3.15 Node Port Figure 3.16 Logical Interface 13

SIP Profile SIP Profiles control the how the Sonus SBC 1000/2000 communicates with other SIP devices. The profiles control important characteristics such as: session timers, SIP header customization, SIP timers, MIME payloads, and option tags. The following figure shows the default SIP profile used for the SBC 2000 for this testing effort. Figure 3.17 SIP Profile 14

Media Profiles Media Profiles specify the individual voice and fax compression codecs and the associated settings for inclusion into a Media List. Different codecs provide varying levels of compression, allowing one to reduce bandwidth requirements at the expense of voice quality. The following figures show the media profiles of the voice codecs used for the SBC 2000 in this testing effort. These figures and are for reference only. Figure 3.18 Voice Codec Configuration G.711u Figure 3.19 Voice Codec Configuration G.729 Figure 3.20 Voice Codec Configuration T.38 15

Media Lists Figure 3.21 Media List 16

Signaling Group Signaling groups allow telephony channels to be grouped together for the purposes of routing and shared configuration. They are the entity to which calls are routed, as well as the location from which Call Routes are selected. Also, Signaling Groups are the location from which Tone Tables and Action Sets are selected. In the case of SIP, protocol settings and link to server, media and mapping tables are specified there. Figure 3.22 Signaling Group 17

SIP Server Table SIP Server Tables contain information about the SIP devices connected to the Sonus SBC 1000/2000. In essence, the server tables emulate a traditional SIP Trunk group. The entries in the tables provide information about the IP addresses, ports, and protocols used to communicate with each server. The Table entries also contain links to counters that are useful for troubleshooting. Figure 3.24 Level 3 Sip Server Table 18

Call Routing Table Call Routing allows calls to be carried between signaling groups, thus allowing calls to be carried between ports, and between protocols (like ISDN to SIP). Routes are defined by Call Routing Tables that allow for flexible configuration of which calls are routed, and how digits are translated. These tables are one of the central connection points of the system, linking Transformation Tables, Message translations, Cause Code Reroute, Tables, Media Lists and the three types of Signaling Groups (ISDN, SIP and CAS). Figure 3.25 SIP Call Routing Table Level 3 to CUCM 9.1 19

Transformation Tables Transformation Tables facilitate the conversion of names, numbers and other fields when routing a call. For example, convert a public PSTN number into a private extension number, or into a SIP address (URI). Every entry in a Call Routing Table requires an associated Transformation Table, and each are selected sequentially from there. In addition, Transformation tables are configurable as a reusable pool that Action Sets can reference. Some examples are as follows: Figure 3.26 Transformation Table Match +1212588102X Figure 3.27 Transformation Table Match ALL Redirected 20

3.4 Tenor SBC configuration A standard fax machine is connected to an FXS port on the Tenor gateway. The Tenor registers the assigned fax number to the Local Tenor Registrar configured on the SBC 2000. Faxes received by the SBC are sent to the Tenor and then onto the fax machine. When the fax machine sends a fax, the Tenor routes it to the SBC. SIP Profile SIP Profiles control the how the Sonus SBC 1000/2000 communicates with SIP devices. Profiles control important characteristics such as: session timers, SIP header customization, SIP timers, MIME payloads, and option tags. The following figure shows the default SIP profile used for the SBC 2000 for this testing effort. Figure 3.28 Default SIP Profile 21

Media Profiles Media Profiles allow one to specify the individual voice and fax compression codecs and the associated settings for inclusion into a Media List. Different codecs provide varying levels of compression, allowing one to reduce bandwidth requirements at the expense of voice quality. The following figures show the media profiles of the voice codecs used for the SBC 2000 in this testing effort. These figures are for reference only. Figure 3.29 Voice Codec Configuration Default G.711U Figure 3.30 Voice Codec Configuration Default G.729 20 ms Figure 3.31 Voice Codec Configuration T.38 Support 22

Media Lists Figure 3.32 Media List 23

SIP Local Registrar Table SIP provides a registration function that allows users to upload their current locations for use by proxy servers. Registration creates bindings in a location service for a particular domain that associates an address-of-record URI with one or more contact addresses. Registration entails sending a REGISTER request to a special type of UAS (User-Agent Server) known as a registrar. A registrar acts as the front end to the location service for a domain, reading and writing mappings based on the contents of REGISTER requests. This location service is then typically consulted by a proxy server that is responsible for routing requests for that domain. SIP Local Registrar contain information about the SIP devices connected to the Sonus SBC 2000. The entries in the tables provide information about the IP Addresses, ports, and protocols used to communicate with each server. The table entries also contain links to counters and to the corresponding SIP Registered Users Table and are very useful for troubleshooting. Figure 3.33 SIP Server Table Figure 3.34 SIP Registrar User Table 24

Signaling Groups Signaling groups allow telephony channels to be grouped together for the purposes of routing and shared configuration. Signaling groups are the entity to which calls are routed, as well as the location from which Call Routes are selected. These are also the locations from which Tone Tables and Action Sets are selected. In the case of SIP signaling groups, protocol settings, links to server, media and mapping tables are configured here. Figure 3.35 Signaling Group - Tenor 25

Call Routing Table Call routing allows calls to be carried between signaling groups, thus allowing calls to be carried between ports, and between protocols (like ISDN to SIP). Routes are defined by Call Routing Tables that allow for flexible configuration of which calls are carried, and how the digits are translated. These tables are one of the central connection points of the system, linking Transformation Tables, Message translations, Cause Code Reroute, Tables, Media Lists and the three types of Signaling Groups (ISDN, SIP and CAS). Figure 3.36 Signaling Groups 26

Transformation Tables Transformation Tables facilitate the conversion of names, numbers and other fields when routing a call. For example, the transformation table can convert a public PSTN number into a private extension number, or into a SIP address (URI). Every entry in a Call Routing Table requires a Transformation Table, and each are selected sequentially from there. In addition, Transformation tables are configurable as a reusable pool that Action Sets can reference. Figure 3.37 Transformation Table - Match All From Tenor Figure 3.38 Transformation Table - Match Fax Number to Tenor 27

4 Configuration of Analog Tenor for use with Fax 4.1 Summary This procedure demonstrates how to configure the Tenor AF/AX to support faxes to and from the SBC 2000. It also shows the basic configuration of the SBC 2000 to accept and send faxes to and from the Tenor. The SBC 1000 and SBC 2000 share a common code base and user interface. In this example, we are using an SBC 2000. Assumptions The Tenor is set up for IP communication; has been set to factory defaults, and is upgraded to P108-09-26 code or later. The SBC has been installed into the network, and is running code V4.0.1 build 354 or later. Basic Call Flow Example Outbound Fax: Inbound Fax: FAX FXS Tenor SIP SBC 2000 PRI or SIP Trunk PRI or SIP Trunk SBC 2000 SIP Tenor FAX The following screenshots of the Tenor Configuration Manager (TCM) show the configuration of the Tenor FXS gateway using selected check boxes, radio buttons, entering values, submitting changes, etc. After each parameter change, select Confirm/OK and save configuration changes by clicking asterisk. (See greyed out pound sign/hash mark {#} in tool bar change to red asterisk {*} on blue field). Dial Plan Use defaults, remove all prefixes as shown. Figure 4.1 Dial Plan Configuration 28

Note: All screenshots are in Advanced Explorer view DNS Enter an IP address of the primary and secondary DNS servers when using FQDNs. Figure 4.2 DNS Server Gateway The Tenor typically defaults to H.323 for outbound protocol. Select SIP only. Figure 4.3 Gateway Settings 29

SIP Signaling Group General Tab Enter the IP address of the SBC 2000 as Primary SIP Server. Register Expiry Time should match the value set in the SBC s SIP Signaling Group (Tenor). The default value is 600 sec. Figure 4.4 SIP Signaling Group User Agent Tab: Add a User Agent (UA) for each number listed in the DN Channel Map. Notice that the UA and the Listening Port (LP) increment accordingly. When highlighted, DN displays in the Contacts field. Figure 4.5 Add User Agents 30

Edit User Agent 101 (example) Figure 4.6 User Agent 101 Edit User Agent 102 Figure 4.7 User Agent 102 31

Add Channel 1 DN Channel Map Configure DN and Calling name for each DN assigned to Tenor Figure 4.8 Configure Channel 1 Add Channel 2 Figure 4.9 Configure Channel 2 32

DN Channel Mapping is Completed Figure 4.10 2 Channels Configured Voice Codec Create a new G.711u codec or change the value in the current codec properties. Figure 4.11 G.711u Codec 33

Codec Profile Figure 4.12 Codec 1 Selected IPRG Advanced Tab Figure 4.13 T303 Timer Setting 34

Fax/QoS Tab Figure 4.14 Fax Settings CAS SG-Phone General Tab Figure 4.15 Select Signaling Type 35

Signaling Tab Figure 4.16 Caller ID Generation Analog Specific Tab Figure 4.17 Set Rx/Tx Gain 36

LCRG-Phone Advanced Tab Figure 4.18 Modem Bypass - Disabled Analog Interface Phone Figure 4.19 Enable Ports 37

4.2 TENOR REGISTRATION TO SBC Overview The following screenshots demonstrate how to configure the SBC 2000 for Tenor SIP Registration and fax routing. The SIP server table and Tenor Registrar were already created in section three of this guide. Create Local SIP Registrar for Tenor Figure 4.20 Tenor Registrar Check SIP User Registration Figure 4.21 Registered SIP Users 38

Check Transport Protocol Figure 4.22 Transport UDP Create Tenor Translation Table and Entries Figure 4.23 Tenor Pass-through Create Tenor Call Routing Group Figure 4.24 Fax to Level 3 39

Create Tenor SIP Signal Group (Pop up summary) Figure 4.25 SIP Signaling Group Tenor 40

5 Cisco Unified Call Manager (CUCM) configuration This section assumes that the CUCM 9.1 components have been installed. The user should be familiar with administration and configuration of CUCM 9.1. This section does not cover the installation of CUCM 9.1. 5.1 CUCM 9.1 Configuration Settings The CUCM 9.1 was configured per the details provided in the Cisco Configuration and Administration Guide: This guide is available online at the following location: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/configadminguide/10_5_2/cup0_bk_ceb3e82e_00_configadmin-guide-imp-1052.html In order to connect Cisco CUCM 9.1 PBX to the SBC 2000 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 as Administrator. Figure 5.1 CUCM Administration Page 41

Create a New TG On the Home page, select Device > Trunk. Click Add New. Enter TRUNK TYPE and DEVICE PROTOCOL and click NEXT (refer to CUCM 9.1 user guide for more detail). Figure 5.2 Trunk Groups Create New Route Group From the main CUCM page, navigate to Call Routing > Route-Hunt > Route Group and 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. Select the appropriate TG and click the "Add to Route Group" button. Fill out Route Group Name (refer to CUCM 9.1 guide for more detail). Figure 5.3 Route Groups 42

Create a New Route List Navigate to Call Routing > Route-Hunt > Route List and click Add New. Enter the Name and Description and then click Add Route Group. On the next screen, select the Route Group that was just created (refer to CUCM 9.1 guide for more detail). Figure 5.4 Route Lists Create a New Route Pattern Navigate to Call Routing > Route-Hunt > Route Pattern and click Add New: Enter the Route Pattern and click Save. Figure 5.5 Route Patterns 43