Configuring Sonus SBC 5200 Sonus PSX-HA With Sonus Session Manager

Transcription

1 Configuring Sonus SBC 5200 Sonus PSX-HA With Sonus Session Manager Application Notes Last Updated: June 8, 2012 Sonus Networks Interoperability Test Lab

2 Contents 1 Document Overview Introduction Audience Requirements Acronyms Test Scenario Reference Configuration Support Install and Configure Sonus Application Server Install and Configure SSM on top of SAS in HA mode SSM Configuration details Verifying SAS License Logging Extraction Service (LES) Configuration Configuring call logging Configuring the Logging Extraction Service Configuring Call logging extraction Configure Sonus SBC Requirements Configuring SBC Configure Sonus PSX as a SIP Redirector PSX configuration Details Configuring SIP trunk groups Configuring Feature Control profile Configure Routing Label Configuring Standard Route Conclusion of 53 Sonus Networks Interoperability Test Lab

3 1 Document Overview These Application Notes describe the configuration steps required for Sonus Networks Session Border Controller 5200 (SBC 5200) to interoperate with Sonus Session Manager (SSM) using SIP trunks with PSX configured as Redirector Server. Sonus SBC 5200 is a robust solution that integrates security, call control, quality of service, advanced media services and switching all within a compact platform. SBC 5200 functionality was compliance tested using a SIP trunk to SSM. PSX acts as a redirector server and provides routing information to SSM. The objective of this document is to describe the procedure to be followed during the IOT of SBC 5200 with SSM. This includes identifying the test environment, tools required for testing, testing topology, test points, risks involved in testing, and scope of testing. Sonus Networks Interoperability Test Lab 3 of 53

4 2 Introduction The interoperability compliance testing focuses on verifying inbound and outbound call flows between Sonus SBC 5200 and Sonus Session Manager Audience This is a technical document intended for telecommunications engineers with the purpose of configuring both the Sonus SBC and the Sonus Session Manager. There will be steps that require navigating the third party product and the 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 Requirements The following equipments and software packages were used for the sample configuration provided: Equipment Sonus SBC 5200 BMC BIOS ConnexIP OS SonusDB EMA SBX OS and System requirements for SSM and SASM Software 2.0.6R000 v v1.6.3 v1.7.5 sonusdb-v r000 ema-v r000 sbx-v r000 RHEL bit, 50GB HDD, 4GB RAM, Xwindow support enabled. DNS bind OS and System requirements for MySQL Database Cluster bind el6.x86_64 RHEL bit. Management 50GB HDD, 4GB RAM. Nodes - 50GB HDD, 8GB RAM. MySQL Database (Cluster Mode) DB Driver Java SASM mysql-connector-java bin.jar Jdk-6u21-linux-amd64.rpm (jdk-6u21) SASM Installer Files: uas_manager_sonus_installeruas_manageruas_manager105_1-1.zip SASManager-install jar Sonus Application Server (SAS) SAS of 53 Sonus Networks Interoperability Test Lab

5 SSM solution installer (includes CDM) Installer Files: installer_sonus_sipas-uas9.0-uas9.0.9_2-1.zip sip_sas_installer jar SSM _2_1 Installer Files: sb_solution_sonus_installer zip ssm_solution_installer jar 2.3. Acronyms SASM MS SD SH SSM CDM SBC NTP DNS Sonus Application Server Manager Management Server Service Director Service Host Sonus Session Manager Common Data Model Session Border Controller Network Time Protocol Domain Name Server 2.4. Test Scenario Sonus SBC 5200 was used as a Session Border Controller (SBC) at an enterprise site consisting of Sonus Session Manager. SIP trunks were used to connect Sonus SBC 5200 to the End Points (IP phones). The following features and functionality were covered during compliance testing: Incoming calls to the Enterprise site through the Sonus SBC 5200 Outgoing calls from the Enterprise site through the Sonus SBC The following images show the IOT setup with SBC 5200 and SAS. Sonus Networks Interoperability Test Lab 5 of 53

6 Figure 2: Outbound call Figure 3: Inbound call 6 of 53 Sonus Networks Interoperability Test Lab

7 Figure 4: EPs behind SBC 5200 Note: All end points are registered to SSM. The following diagrams show the IOT setup with SBC 5200, SAS and PSX as redirector: Figure 5: Outbound call Sonus Networks Interoperability Test Lab 7 of 53

8 Figure 6: EPs behind SBC 5200 Note: End point behind SBC 5200 is not registered to SSM Reference Configuration A simulated enterprise site consisting of SSM and Sonus SBC 5200 were used during compliance testing. SIP trunks were used to connect Sonus SBC 5200 with Sonus Session Manager. The Sonus SBC 5200 was also connected to end points (IP phones) through SIP trunks. The following reference configuration shows connectivity between SSM and Sonus SBC 5200 with PSX as Redirector Server. 8 of 53 Sonus Networks Interoperability Test Lab

9 Sonus Networks Interoperability Test Lab 9 of 53

10 2.6. Support Technical support on Sonus SBC 5200 can be obtained through the following: Phone: (978) or (888) (Toll-free) Web: 10 of 53 Sonus Networks Interoperability Test Lab

11 3 Install and Configure Sonus Application Server This section provides the procedures for configuring the Communication Manager. The procedures cover the following areas. Install SAS in HA mode Install SSM on top of SAS in HA mode 3.1. Install and Configure SSM on top of SAS in HA mode Configure VMs using the following procedure. 1. Create two VMs with the following OS and system requirement specifications. OS RHEL bit. System Requirements 50GB HDD, 4GB RAM, Xwindow support enabled. 2. Configure the VM s environmental variables for SAS installation in HA mode as follows. vi /etc/hosts Add the IP and domain name corresponding to the deployment scenario similar to the following example, VM Machine 1: VM Machine 2: sonusha1 sonusha1.sonustp.com sip.mcast.net sonusha2 sonusha2.sonustp.com sip.mcast.net Install JAVA 1.6.0_21 To install JAVA: Copy the rpm package jdk-6u21-linux-amd64.rpm to the VM machine. Execute rpm Uvh jdk-6u21-linux-amd64.rpm to upgrade the java version. Set the JAVA path Perform the following steps to set the JAVA path. As an example, with BASH shell do the following: export PATH=/usr/java/jdk1.6.0_21/bin:$PATH export JAVA_HOME=/usr/java/jdk1.6.0_21/bin/java Enter BASH Shell Sonus Networks Interoperability Test Lab 11 of 53

12 DNS Entries sonusha1.sonustp.com: Resolves to sonusha2.sonustp.com: Resolves to sonusha.sonustp.com: Resolves to SAS cluster Note: Add all the domain name entries in the DNS server with the corresponding resolvable IP s.synchronize all VMs with a NTP server in the test setup environment. 3. Install and configure SAS using any of the following methods. GUI Installation (using Graphical Interface) Silent Installation (using installer.properties file). Note: Refer the following documents for more information on installation and configuration details of SAS _Sonus_Application_Sever_9_Installing_Sonus_Application_Server_ _ Sonus_Application_Sever_9_Administering_Sonus_Application_Server_1 4. Add the installed SAS instances to the SASM. The installed SAS cluster instances must be added in the SASM for further configurations. Note: Configure the Control domain entries under Quick Tasks > view system status > Service Hosts > Domains > Controlled Domains as mentioned in the documents. Control Domain entries must include FMC SAS cluster and FMC Host s domain names. Refer the following documents for more information on how to add and configure SAS instances in SASM _Sonus_Application_Server_Manager_1.0_Installing_SAS_Manager_ _Sonus_Application_Server_Manager_1.0_Administering_SAS_Manager_1 5. Install SSM on top of the SAS in HA mode. Database and schema must be created with desired privileges. Use any of the following methods to install SAS. GUI Installation (using Graphical Interface) Silent Installation (using installer properties file) Note: Refer the following documents for more information on installation and configuration details of SAS _Sonus_Session_Manager_2.0_Installing_Sonus_Session_Manager_ _Sonus_Session_Manager_2.0_Administering_Sonus_Session_Manager_1 SSM is installed on one of the SAS cluster; the same would be deployed/replicated among all the cluster elements. 12 of 53 Sonus Networks Interoperability Test Lab

13 Example install.properties files of SSM solution installer ############################################################################ # installer.properties # # # # To run a "headless" installation of the Common Data Model and Service # # Broker add values for all the properties below. You can then run the # # installer as follows: # # # # java -jar sb_solution_installer-n.n.n.jar -options installer.properties # # # ############################################################################ ############################################################################ # EULA # ############################################################################ # Set to true to agree to the EULA accept.eula=true ############################################################################ # General IzPack Configuration # ############################################################################ # The path to which the core CDM files and/or CLI will be installed INSTALL_PATH=/opt/sonus # The path to the JDK JDKPath=/usr/java/jdk1.6.0_21 # Directory to which we will install the CLI cli.dir=/opt/sonus/cli ############################################################################ # The Packs to Install. Choose one or more of # # # # - CDM.FILES CDM Files & Licences # # - CDM.DBSCRIPTS CDM DB Scripts # # - CDM.CLI CDM CLI # # - CDM.DATABASE (Re-)Create CDM Database entities # # - CDM.APPLICATIONS (Re-)Reploy CDM Application # # - SB.LICENSES Service Broker Licence Files # # - SB.DBSCRIPTS SB DB Scripts # # - SB.CLI SB CLI Plugin # # - SB.DATABASE (Re-)Create SB Database entities # # - SB.APPLICATIONS (Re-)Reploy SB Application # # # # There is a heirarchy to the packs so choosing 'CDM' will include all of # # the CDM packs and 'SB' will include all the SB packs. # ############################################################################ packs=cdm.files,cdm.dbscripts,cdm.cli,cdm.database,cdm.applications,sb.licenses,sb.dbsc RIPTS,SB.CLI,SB.DATABASE,SB.APPLICATIONS ############################################################################ # Information on the UAS Management Server - required so we can connect to # # it to deploy artefacts and/or configure the CLI correctly # ############################################################################ ManagementServer.Address= # By default the port is 5759 ManagementServer.Port=5759 ManagementServer.User=administrator ManagementServer.Password=administrator Sonus Networks Interoperability Test Lab 13 of 53

14 ############################################################################ # Database details # ############################################################################ # The java class of the JDBC driver, e.g. com.mysql.jdbc.driver db.driver.class=com.mysql.jdbc.driver # The path to the JDBC driver jar file db.driver.location=/root/tp/mysql-connector-java bin.jar # Database connection string, e.g. jdbc:mysql://<host>:3306/<schema> db.connection.string=jdbc:mysql:loadbalance:// :3306, :3306/s m_ha1?loadbalanceblacklisttimeout=5000&autoreconnect=true # Default schema (this may be duplicated in the connection string above) db.schema=sm_ha1 # Username and password for access the DB db.user=sonus db.password=sonus # DB Type - either MYSQL, MYSQL_CLUSTER or SQLSERVER db.type=mysql_cluster #The Service Broker Database Health Check period in seconds db.healthcheck.period=30 # Security Realm - this will be added to the database. # Only required if you have selected the CDM Database Pack. # You can change the realm at a later point. security.realm=sonusha.sonustp.com Note: db.connection.string=jdbc:mysql:loadbalance:// :3306, :3306/sm_ha1?loadBalanceBlacklistTimeout=5000&autoReconnect=true Before installing SSM, the DB sm_ha1 is created and is provided with the required privileges in the MySQL Cluster SSM Configuration details SSM must be configured with the following configuration to achieve end to end call through SBC 5200 and redirector dip at PSX. Create person entries. Create entities for PSX redirector and SBC 5200 Create Route. Creating person entries Local End Point: add person set user-name 9100 add credentials set password 111 set type PHONE save add service-profile set name 9100_SP save add address-of-record sip set preference 1 set service-profile 9100_SP set uri/phone 9100@sonusha.sonustp.com add sb-aor set resolution-status CONTACT_RESOLUTION save save 14 of 53 Sonus Networks Interoperability Test Lab

15 save Remote End Points: add person set user-name 9101 add credentials set password 111 set type PHONE save add service-profile set name 9101_SP save add address-of-record sip set preference 1 set service-profile 9101_SP set uri/phone 9101@sonusha.sonustp.com add sb-aor set resolution-status CONTACT_RESOLUTION save save save add person set user-name 9102 add credentials set password 111 set type PHONE save add service-profile set name 9102_SP save add address-of-record sip set preference 1 set service-profile 9102_SP set uri/phone 9102@sonusha.sonustp.com add sb-aor set resolution-status CONTACT_RESOLUTION save save save Creating entities End Point as an entity: SBCli > add entity SBCli / new entity > set name EP_6000 SBCli / new entity > set address SBCli / new entity > save PSX redirector as an entity: SBCli > add entity SBCli / new entity > set name PSX SBCli / new entity > set address iothapsx.sonustp.com SBCli / new entity > save SBC 5200 as an entity: SBCli > add entity SBCli / new entity > set name NBS_HA SBCli / new entity > set address SBCli / new entity > save Sonus Networks Interoperability Test Lab 15 of 53

16 List of entities: SBCli > list entity name address trusted obey-route-headers auth-record-routes rule-set-name NBS_HA true false true EP_ true false true PSX iothapsx.sonust true false false Creating routes 1. Add route with prefix to PSX Redirector: This route is added on SSM for routing calls with prefix 6000 to Entity (EP_6000). SSM queries PSX redirector for subsequent hop. SBCli > add routing SBCli / new routing > set prefix 6000 SBCli / new routing > set domain sonustp.com SBCli / new routing > set url-scheme sip SBCli / new routing > set url-entity PSX SBCli / new routing > save 2. Add route with prefix to PSX Redirector: Reference configuration contains an endpoint with number 7001 and 7002 behind SBC This endpoint is not registered to SSM and it must perform PSX SIP query to retrieve the route data, hence this endpoint can be contacted successfully. SBCli > add routing SBCli / new routing > set prefix 700 SBCli / new routing > set domain sonustp.com SBCli / new routing > set url-scheme sip SBCli / new routing > set url-entity PSX SBCli / new routing > save Note: PSX contains routing information and provides route info to SSM via 3xx response to the SIP query that SSM sends, because of this feature all routes are pointed to PSX redirector in SSM configurations. List of entities: SBCli > list routing id prefix domain url-scheme urluser url-entity url-parameters sonustp.com sip PSX 16 of 53 Sonus Networks Interoperability Test Lab

17 1 700 sonustp.com sip PSX Verifying SAS License SAS license has permissions for features illustrated in these Application Notes. The license file installed on the system controls the maximum permitted capacity. If the capacity is insufficient, contact an authorized Sonus Application Server sales representative for changes. Note: Refer the following document for licensing details. Sonus_Application_Server_9.0_Administering_Sonus_Application_Server_1.pdf 3.3. Logging Extraction Service (LES) Configuration LES is an optional Sonus application server cluster element that extracts call data from a database to files. LES deployment is optional, but LES is recommended when you access SIP message logs for analysis or further processing. For example, extracted SIP message logs may form the data required for billing or account management systems. Use the following steps to configure the LES Configuring call logging Service Hosts are configured to store call logs (also known as SIP message logs) in an RDBMS. Refer Administering Sonus Application Server guide for more information on SIP message logging. 1. Ensure that the required conditions are in place. Refer Required conditions for Sonus Application Server cluster configuration in the help contents of SASM for more details on these conditions. To access this file, Click on the help icon in the top left corner in SASM to see the help contents. 2. Start the Sonus Application Server Management Console. Refer Starting the Sonus Application Server Management Console in SASM help. 3. In the left navigation pane of SASM, click Cluster Administration > Composition > Service Hosts. 4. Click to expand the Call Logging area, in the Service Hosts page. 5. Specify the required configuration values. For more information, see Service Host Call Logging field descriptions in SASM help. 6. Click Save. Note: You may be prompted to restart cluster elements, which may impact servicing of SIP traffic. For more information, see Warning about stopping and restarting of cluster elements in SASM help. Reference screenshots of the Call Logging section is shown below. Sonus Networks Interoperability Test Lab 17 of 53

18 Note: Use the following command for RDBMS Connection String. jdbc:mysql:loadbalance:// :3306, :3306/ha_les?user=s onus&password=sonus A database ha_les is created in MySQL Cluster before configuring Call Logging and LES Configuring the Logging Extraction Service 1. Add the LES under Add Logging Extraction Service as shown in the following image and then click Save. 2. Ensure that the required conditions are in place. For more information. Refer Required conditions for Sonus Application Server cluster configuration in the help contents of SASM for more details on these conditions. To access this file, Click on the help icon in the top left corner in SASM to see the help contents. 3. Start the Sonus Application Server Management Console. For more information, see Starting the Sonus Application Server Management Console in SASM help. 4. Click Cluster Administration > Composition > Logging Extraction Service. 5. Click View. Specify the required configuration. For more information, see Logging Extraction Service field descriptions in SASM help. Note: You may be prompted to restart cluster elements, which may impact the servicing of SIP traffic. For more information, see Warning about stopping and restarting of cluster elements in SASM help. Reference screenshot of the LES section is shown below: 18 of 53 Sonus Networks Interoperability Test Lab

19 3.3.3 Configuring Call logging extraction You can configure call logging extraction for a Sonus Application Server cluster. Enabling this service specifies that the Logging Extraction Service extract SIP message logs (also known as call logs ) from the RDBMS to a file in a specified directory. Before performing this procedure, ensure that the Service Hosts are set up to store call logs in the RDBMS. For more information, see Configuring call logging. 1. Ensure that the required conditions are in place. For more information, see Required conditions for Sonus Application Server cluster configuration in SASM help. 2. Start the Sonus Application Server Management Console. For more information, see Starting the Sonus Application Server Management Console in SASM help. 3. Click Cluster Administration > Composition > Logging Extraction Service. 4. Click View. 5. On the Logging Extraction Service page, expand the Call Logging area. 6. Specify the required configuration. For more information, see Call Logging field descriptions in SASM help. Note: You may be prompted to restart cluster elements, which may impact servicing of SIP traffic. For more information, see Warning about stopping and restarting of cluster elements in SASM help. Reference screenshot of the call logging extraction Service section is shown below: Sonus Networks Interoperability Test Lab 19 of 53

20 Note: Use the following command for RDBMS Connection String. jdbc:mysql:loadbalance:// :3306, :3306/ha_les?user=s onus&password=sonus A database ha_les is used for Call Logging in the above section. This is the common DB used for Call Logging and Call logging extraction. Use the following code for Extract Message Directory. /opt/sonusbase/sas /loggingextractionservice/les_records Note: The following deviation from the execution file (shell script) is expected to resolve the issue observed while configuring LES service. 1. Copy mysql-connector-java bin.jar file in the path /opt/sonusbase/sas /LoggingExtractionService/lib. 2. Edit the file LoggingExtractionService.sh in the path /opt/sonusbase/sas /LoggingExtractionService/bin as given below. 3. Modify the following highlighted text with specific mysql connector used /usr/java/jdk1.6.0_21/bin/java $VM_SWITCH - Dcom.avaya.log.outputdir=$INSTALL_DIR/var -Djava.net.preferIPv4Stack=true -cp.:$install_dir/lib/les.jar:$install_dir/lib/oracle.jar:$install_dir/lib/postgre sql.jar:$install_dir/lib/concurrent-uas jar:$install_dir/lib/log4j jar::$INSTALL_DIR/lib/db2jcc.jar:$INSTALL_DIR/lib/db2jcc_license_cisuz.j ar:$install_dir/lib/db2jcc_license_cu.jar:$install_dir/lib/mysqldriver.jar:$ins TALL_DIR/lib/avaya_common_logging.jar net.ubiquity.asb.les.automaticlogextraction -adminport multicastaddr multicastport clusterid SPEAK_SM_CLUSTER & Modified code snippet is provided below. 20 of 53 Sonus Networks Interoperability Test Lab

21 /usr/java/jdk1.6.0_21/bin/java $VM_SWITCH - Dcom.avaya.log.outputdir=$INSTALL_DIR/var -Djava.net.preferIPv4Stack=true -cp.:$install_dir/lib/les.jar:$install_dir/lib/oracle.jar:$install_dir/lib/postgre sql.jar:$install_dir/lib/concurrent-uas jar:$install_dir/lib/log4j jar::$INSTALL_DIR/lib/db2jcc.jar:$INSTALL_DIR/lib/db2jcc_license_cisuz.j ar:$install_dir/lib/db2jcc_license_cu.jar:$install_dir/lib/mysql-connectorjava bin.jar:$install_dir/lib/avaya_common_logging.jar net.ubiquity.asb.les.automaticlogextraction -adminport multicastaddr multicastport clusterid SPEAK_SM_CLUSTER & 4. Restart the Logging Extraction Service using the following two commands, service LoggingExtractionService stop service LoggingExtractionService start Restart LES through GUI will not reflect the changes in the LoggingExtractionService.sh file, hence perform stop-start through CLI is suggested. Note: Refer the following documents for more information on Logging Extraction Service _ Sonus_Application_Sever_9_Administering_Sonus_Application_Server_1 Help contents in SASM (Click the top left help icon to view the help content). Sonus Networks Interoperability Test Lab 21 of 53

22 4 Configure Sonus SBC 5200 This section provides a snapshot of Sonus SBC 5200 configuration used during compliance testing. The Sonus SBC5200 is typically configured for customers by Sonus Networks. The screenshots and partial configuration supplied by Sonus Networks, is provided only for reference. Other configurations are possible Requirements Use the following login details accessing SBC USERNAME : root PASSWORD : sonus1 Connection Type : SSH Port : Configuring SBC 5200 Perform the following steps to configure Sonus SBC. Login into configure mode. Configure addresscontext, ipinterfacegroup, ipinterface, staticroute and ZONES Configure siptrunkgroup, ingressipprefix, ippeer and dnsgroup Configure ipsignalingprofile and associate it to a Trunkgroup Configure routinglabel and associate with DN and Trunk Based routing 1. Logging into configure mode To configure SBC 5200, user must be in configure mode. Perform the following commands to enter the configure mode. In the following code snippet SBC is referred as Avarsa1. [SSH] Server Version OpenSSH_5.1p1 Debian-5 [SSH] Logged in (password) Sonus ConnexIP OS v1.7.5 GNU/Linux Last login: Fri May 11 10:37: from [root@avarsa1 ~]# cli admin connected from using ssh on avarsa1 admin@avarsa1> configure Entering configuration mode private [ok][ :04:43] [edit] admin@avarsa1% 2. Configure addresscontext, ipinterfacegroup, ipinterface, staticroute and ZONES Perform the following commands to configure addresscontext, ipinterfacegroup, ipinterface, staticroute and ZONES. addresscontext, ipinterfacegroup and ipinterface The address context is a container of objects that corresponds to a specific IP Addressing domain. Address contexts are used in SBC 5200 to contain and segregate objects that deal with IP addresses. For example, 22 of 53 Sonus Networks Interoperability Test Lab

23 multiple IP interfaces are grouped together into an IP interface group and all grouped IP interfaces are going to use the same address context. IP Interface Groups are primary tools for accomplishing disjoint networks (administrative network separation). An IP Interface Group is the local manifestation of a segregated network domain. Configuring addresscontext, ipinterfacegroup and ipinterface admin@avarsa1% set addresscontext default ipinterfacegroup LIF1 ipinterface pkt0_v4 cename avarsa portname pkt0 ipaddress prefix 24 admin@avarsa1% set addresscontext default ipinterfacegroup LIF1 ipinterface pkt0_v4 mode inservice state enabled admin@avarsa1% set addresscontext default ipinterfacegroup LIF2 ipinterface pkt1_v4 cename avarsa portname pkt1 ipaddress prefix 24 admin@avarsa1% set addresscontext default ipinterfacegroup LIF2 ipinterface pkt1_v4 mode inservice state enabled Configuring staticroute The staticroute object is used to configure static IP routes for the IP interfaces. A static route indicates the nexthop gateway and IP interface that is used for a particular peer network IP prefix. admin@avarsa1% set addresscontext default staticroute LIF1 pkt0_v4 preference 100 admin@avarsa1% set addresscontext default staticroute LIF1 pkt0_v4 preference 100 admin@avarsa1% set addresscontext default staticroute LIF1 pkt0_v4 preference 100 admin@avarsa1% set addresscontext default staticroute LIF1 pkt0_v4 preference 100 admin@avarsa1% set addresscontext default staticroute LIF2 pkt1_v4 preference 100 admin@avarsa1% set addresscontext default staticroute LIF2 pkt1_v4 preference 100 Sonus Networks Interoperability Test Lab 23 of 53

24 Configuring ZONE A zone is used to group a set of objects unique in a particular customer environment. A zone can contain one SIP signaling port and one H.323 signaling port. A zone can contain multiple SIP and H.323 trunk groups. In the trial setup the INTERNAL and EXTERNAL zones are created and configured. admin@avarsa1% set addresscontext default zone Z1 id 2 sipsigport 1 state enabled ipaddressv portnumber 5060 transportprotocolsallowed sip-udp,sip-tcp ipinterfacegroupname LIF1 admin@avarsa1% set addresscontext default zone Z2 id 3 sipsigport 2 state enabled ipaddressv portnumber 5060 transportprotocolsallowed sip-udp,sip-tcp ipinterfacegroupname LIF2 3. Configure siptrunkgroup, ingressipprefix, ippeer and dnsgroup Configuring siptrunkgroup SIP trunk group configuration is required for routing SIP traffic through SBC Ingress IP Prefix configuration is required for routing incoming traffic from a specific IP address. admin@avarsa1% set addresscontext default zone Z1 siptrunkgroup TG_SMHA_NBS_EPNR mode inservice state enabled media mediaipinterfacegroupname LIF1 admin@avarsa1% set addresscontext default zone Z1 siptrunkgroup TG_SMHA_NBS_EPR mode inservice state enabled media mediaipinterfacegroupname LIF1 admin@avarsa1% set addresscontext default zone Z2 siptrunkgroup TG_NBS_SMHA mode inservice state enabled media mediaipinterfacegroupname LIF2 TG_SMHA_NBS_EPR The sip trunk between SBC 5200 and an endpoint registered to SSM through SBC TG_SMHA_NBS_EPNR - The sip trunk between SBC 5200 and an endpoint connected to SBC 5200 directly on sip trunk. This endpoint is not registered to SSM. TG_NBS_SMHA The sip trunk between SBC 5200 and SSM. Configuring ingressipprefix to the SIP Trunk Group admin@avarsa1% set addresscontext default zone Z1 siptrunkgroup TG_SMHA_NBS_EPNR ingressipprefix admin@avarsa1% set addresscontext default zone Z1 siptrunkgroup TG_SMHA_NBS_EPNR ingressipprefix admin@avarsa1% set addresscontext default zone Z1 siptrunkgroup TG_SMHA_NBS_EPR ingressipprefix admin@avarsa1% set addresscontext default zone Z1 siptrunkgroup TG_SMHA_NBS_EPR ingressipprefix of 53 Sonus Networks Interoperability Test Lab

25 set addresscontext default zone Z2 siptrunkgroup TG_NBS_SMHA ingressipprefix set addresscontext default zone Z2 siptrunkgroup TG_NBS_SMHA ingressipprefix TG_SMHA_NBS_EPR - This enables TG_SMHA_NBS_EPR trunk to accept to and fro traffic from the IP /198. Here the end points are registered to SSM using SBC 5200). TG_SMHA_NBS_EPNR - This enables TG_SMHA_NBS_EPNR trunk to accept to and fro traffic from the IP /198. Here the end points are on direct sip trunk to SBC 5200, and are not registered to SSM. TG_NBS_SMHA - This enables TG_NBS_SMHA trunk to accept to and fro traffic from the IP /131 (SM HA Cluster). Configuring ippeer Destinations Use IP Peer configuration for routing outgoing traffic to a particular IP. admin@avarsa1% set addresscontext default zone Z1 ippeer NBS_EPNR1_IPP ipaddress ipport 5060 admin@avarsa1% set addresscontext default zone Z1 ippeer NBS_EPNR2_IPP ipaddress ipport 5060 admin@avarsa1% set addresscontext default zone Z1 ippeer NBS_EPR1_IPP ipaddress ipport 5060 admin@avarsa1% set addresscontext default zone Z1 ippeer NBS_EPR2_IPP ipaddress ipport 5060 admin@avarsa1% set addresscontext default zone Z2 ippeer NBS_SMHA_IPP policy sip fqdn sonusha.sonustp.com fqdnport 5060 Configuring dnsgroup Use the external DNS configuration for resolving FQDN entries. In the following example is the DNS server. admin@avarsa1% set addresscontext default dnsgroup TPSMDNS server TPSMDNS_111 ipaddress state enabled admin@avarsa1% show addresscontext default dnsgroup dnsgroup TPSMDNS { server TPSMDNS_111 { state enabled; ipaddress ; } } [ok][ :28:49] [edit] Sonus Networks Interoperability Test Lab 25 of 53

26 4. Configure ipsignalingprofile and associate it to a Trunkgroup This profile is used to specify parameters associated with H.323, SIP, SIP-I, RPH ETS, and IMS communication sent as part of the outgoing signaling message after standard protocol rules have been applied. In this setup the ipsignalingprofile SIP_RMV_PRFX is created and used by changing the flags as required. Perform the following commands to configure ipsignalingprofile and associating it to a Trunkgroup. admin@avarsa1% set profiles signaling ipsignalingprofile SIP_RMV_PRFX admin@avarsa1% set addresscontext default zone Z1 siptrunkgroup TG_SMHA_NBS_EPNR policy signaling ipsignalingprofile SIP_RMV_PRFX admin@avarsa1% set addresscontext default zone Z1 siptrunkgroup TG_SMHA_NBS_EPR policy signaling ipsignalingprofile SIP_RMV_PRFX admin@avarsa1% set addresscontext default zone Z2 siptrunkgroup TG_NBS_SMHA policy signaling ipsignalingprofile SIP_RMV_PRFX Show command output of the profile ipsignalingprofile SIP_RMV_PRFX admin@avarsa1% show profiles signaling ipsignalingprofile SIP_RMV_PRFX ipprotocoltype siponly; commonipattributes { flags { addpathserviceroute callholdinterworking clearmodefordatacalls createpchargingvector createpathheader createservicerouteheader customizedsessiontimerbehavior disablealsoheader disablehosttranslation disablemedialockdown disablerefertouriparameters discardreceivedreasonheader donotincludessattributeinreinvite endtoendbye enable; includeipportsinfromandtoheaders includereasonheader includessattributeininitialinvite includetransporttypeincontactheader insertpeeraddressastoprouteheader mapcauselocation mapsuspendresumeeventinpsvcinfoheader mapuuiinpsiginfoheader mimecauseprecedereasonheadercause minimizerelayingofmediachangesfromothercalllegall nocontentdisposition noportnumber5060 enable; nouserinfoincontactheader onlyselectedcodecinsessionrefresh pchgmsginfo 26 of 53 Sonus Networks Interoperability Test Lab

27 requerypsxonregisterrefresh sdpolineonlycompares sendallallowedcodecsforlatemediainviteorreinvite senddirectmediainfoinsdpattribute sendptimeinsdp sessiontimerrefreshupdate setacceptheadertoapplicationsdponly setolinedash setsessionversionzero setslinedash skippsxqueryforrefer storepathheader storeservicerouteheader terminalportabilityinterworking } calltransferflags { handleipaddressesnotpresentinnetworkselectortablenst routeviatransferringiptg; forcererouteviapsxquery } optiontaginrequireheader { suppressreplacetag } optiontaginsupportedheader { suppressreplacetag } relayflags { dialogeventpackage dtmfbody info message notify enable; options regeventpackage refer enable; sonusmediabody statuscode3xx statuscode4xx6xx enable; thirdpartybodies } transparencyflags { alertinformationheader authcodeheaders enable; contactheader enable; errorinfo fromheader enable; historyinfo maxforwardsheader mwibody pchargingvectorheader pearlymedia pathheader qsigbody reasonheader referredbyheader requesturi enable; Sonus Networks Interoperability Test Lab 27 of 53

28 routeheader servicerouteheader sipbody sipfragbody toheader tonebody unknownbody unknownheader enable; enable; } } egressipattributes { numberglobalizationprofile ""; flags { bgcftargetschemetransparency } bci { convertinactivetosendrecv disable2806compliance enable; disableoptionalregisterparameters map181or182messageto183 mapcontractornumberinpsiginfoheader samecallidforrequiredauthorization suppressunregister ttcisupmapping usecalledpartyinrequesturi usecoloninsdpmediatypeparameter validateisubaddress bciinterworkencountered bciisdnaddess } domainname { usesipdomainnameinfromfield usesipdomainnameinrequesturi } isub { allownsapisub allowuserspecifiedisub includecalledpartyisub includecallingpartyisub } numberportabilityattributes { npdioptions includenpdiyes; disablern } privacy { transparency enable; } redirect { mode acceptredirection; contacthandling mergereceivedcontacts; flags } sipheadersandparameters { callforwarding { datamapping } diversion; diversionheadertransparency 28 of 53 Sonus Networks Interoperability Test Lab

29 includechargeinformation includenone; destinationtrunkgroupoptions includenone; originatingtrunkgroupoptions includenone; flags { includecic includecpcinformation includenpi includeolip includepkadn includepstnparameters includeqvalue skipcseqcheckinearlydialog transparencyfordestinationtrunkgroupparameter } } transport { type1 none; type2 none; type3 none; type4 none; } } ingressipattributes { flags { sip181supported sip182supported mapcalledpartycategoryinpsiginfoheader nosdpin180supported registrationexpiresinexpiresheader registrationsupport3xx send183oninitiatingdisconnecttreatment sendsdpin200okif18xreliable sendsdpinsubsequent18x } carrierinformation { generateterminatingca generateterminatingcic } } [ok][ :59:03] [edit] admin@avarsa1% Configuring routinglabel and associating it with DN/Trunk based routing Call routing configuration defines the routing information to identify the intended destination. This includes creating Routing label that binds the Trunk group to an IP Peer entry within a specific zone and standard route determined to a specific DN pattern or a Trunk to choose the specific routing Label as destination. Global Configuration to create Routing Label admin@avarsa1% set global callrouting routinglabel SMHA_NBS_EPNR1_RL routinglabelroute 1 ippeer NBS_EPNR1_IPP trunkgroup TG_SMHA_NBS_EPNR inservice inservice Sonus Networks Interoperability Test Lab 29 of 53

30 set global callrouting routinglabel SMHA_NBS_EPNR2_RL routinglabelroute 1 ippeer NBS_EPNR2_IPP trunkgroup TG_SMHA_NBS_EPNR inservice inservice admin@avarsa1% set global callrouting routinglabel SMHA_NBS_EPR1_RL routinglabelroute 1 ippeer NBS_EPR1_IPP trunkgroup TG_SMHA_NBS_EPR inservice inservice admin@avarsa1% set global callrouting routinglabel SMHA_NBS_EPR2_RL routinglabelroute 1 ippeer NBS_EPR1_IPP trunkgroup TG_SMHA_NBS_EPR inservice inservice admin@avarsa1% set global callrouting routinglabel NBS_SMHA_RL routinglabelroute 1 ippeer NBS_SMHA_IPP trunkgroup TG_NBS_SMHA inservice inservice Global Configuration to create Standard Route (DN and Trunk based) admin@avarsa1% set global callrouting route none Sonus_NULL Sonus_NULL standard all all ALL none Sonus_NULL routinglabel NBS_SMHA_RL admin@avarsa1% set global callrouting route trunkgroup TG_NBS_SMHA AVARSA standard all all ALL none Sonus_NULL routinglabel SMHA_NBS_EPNR1_RL admin@avarsa1% set global callrouting route trunkgroup TG_NBS_SMHA AVARSA standard all all ALL none Sonus_NULL routinglabel SMHA_NBS_EPNR2_RL admin@avarsa1% set global callrouting route trunkgroup TG_SMHA_NBS_EPNR AVARSA standard Sonus_NULL 1 all all ALL none Sonus_NULL routinglabel NBS_SMHA_RL admin@avarsa1% set global callrouting route trunkgroup TG_SMHA_NBS_EPR AVARSA standard Sonus_NULL 1 all all ALL none Sonus_NULL routinglabel NBS_SMHA_RL Details of Route configured in these commands Use the following commands for routing traffic to SSM from end point registered to SSM through SBC set global callrouting route none Sonus_NULL Sonus_NULL standard all all ALL none Sonus_NULL routinglabel NBS_SMHA_RL Use the following command is for routing the call with prefix 7001 from SSM to the end point behind SBC 5200 which is not registered to SSM. set global callrouting route trunkgroup TG_NBS_SMHA AVARSA standard all all ALL none Sonus_NULL routinglabel SMHA_NBS_EPNR1_RL Use the following command is for routing the call with prefix 7002 from SSM to the end point behind SBC5200 which is not registered to SSM. set global callrouting route trunkgroup TG_NBS_SMHA AVARSA standard all all ALL none Sonus_NULL routinglabel SMHA_NBS_EPNR2_RL Use the following command is for routing all the calls with Trunk group TG_SMHA_NBS_EPNR (End points not registered to SSM) to SSM. 30 of 53 Sonus Networks Interoperability Test Lab

31 set global callrouting route trunkgroup TG_SMHA_NBS_EPNR AVARSA standard Sonus_NULL 1 all all ALL none Sonus_NULL routinglabel NBS_SMHA_RL Use the following command is for routing all the calls with Trunk group TG_SMHA_NBS_EPR to SSM. set global callrouting route trunkgroup TG_SMHA_NBS_EPR AVARSA standard Sonus_NULL 1 all all ALL none Sonus_NULL routinglabel NBS_SMHA_RL Note: Refer the following documents for more information regarding the above configurations _SBC5200_2.0.3S100_Operations_Guide_1.pdf _SBC5200_2.0.3S100_Reference_Guide_1.pdf. Sonus Networks Interoperability Test Lab 31 of 53

32 5 Configure Sonus PSX as a SIP Redirector 5.1. PSX configuration Details PSX is deployed as a SIP redirector in the Harmony test bed. PSX serves as SSM for Call Routing. SSM sends SIP request for unknown numbers (unregistered with SSM) and expects a 3XX response from PSX for further call processing. The following sections define the PSX version and configurations to set PSX as a SIP redirector. EMS and PSX Manager Version: V R000 PSX version: V R000 Activating the SIP Engine The SIP Engine (SIPE) component permits PSX to support SIP operation. It acts as a SIP redirector server or proxy server for incoming SIP calls and communicates with SIP application servers using SIP. It communicates with the PES component using policy requests and policy responses and the SIP Engine has to be enabled for configuring SIP REDIRECTOR server and hence PSX processes SIP messages. Following screenshots show how to enable SIP engine. 32 of 53 Sonus Networks Interoperability Test Lab

33 5.2. Configuring SIP trunk groups P2_TG_SM The trunk group between endpoints and SSM, SAS1 ( ) and SAS2 ( ) IPs are attached as Gateways to the same Trunk group Sonus Networks Interoperability Test Lab 33 of 53

34 34 of 53 Sonus Networks Interoperability Test Lab

35 Sonus Networks Interoperability Test Lab 35 of 53

36 The following screenshot displays how the trunk group is assigned to SAS2 Gateway values are retained in other fields. 36 of 53 Sonus Networks Interoperability Test Lab

37 P2_TG_NBS5K The trunk group between SSM and SBC Sonus Networks Interoperability Test Lab 37 of 53

38 38 of 53 Sonus Networks Interoperability Test Lab

39 Sonus Networks Interoperability Test Lab 39 of 53

40 TG_EP_6000 The Trunk group for EP_6000 entity created at SSM. 40 of 53 Sonus Networks Interoperability Test Lab

41 Sonus Networks Interoperability Test Lab 41 of 53

42 5.3. Configuring Feature Control profile Feature Control Profiles are assigned to Trunk Groups to control PSX functions associated with ingress call processing. Refer PSX Provisioning Guide - Appendix A for a detailed description of each Feature Control Profile fields and their functions. PSX seed data includes the following predefined Feature Control Profiles: DEFAULT_FC_ACCESS: For access Trunk Groups DEFAULT_FC_IXC: For non-access Trunk Groups except as provided below DEFAULT_FC_JAPAN: For Trunk Groups in Japan DEFAULT_SIP_FC_ACCESS: For SIP access Trunk Groups DEFAULT_SIP_FC_IXC: For other SIP Trunk Groups. Feature Control Profile is not a mandatory entry for each Trunk Group. The corresponding GUI field provides<none> as a drop down option. In the absence of an explicit feature control profile selection, PSX uses Feature Control Profile DEFAULT_FC_ACCESS for default settings. User can provision the Feature control profile of their choice to suit the particular behavior. The Feature Control Profile provides one setting specific to SIP call processing. Third party SIP Servers may use PSX (SIPE) either as a SIP Redirector or as a SIP Proxy. On the Feature Control Profile the user can select either Proxy or Redirector. If a particular SIP Server wants to use the PSX as a proxy, user must provision a Feature Control Profile on the virtual Trunk Group associated with that SIP Server and select Proxy. If Proxy is not selected, the system chooses Redirector as the default behavior. Note: Refer the following documents for more information _PSX_8.4_Provisioning_Guide_1.pdf _PSX_8.4_Product_Description_Guide_1.pdf 42 of 53 Sonus Networks Interoperability Test Lab

43 DEFAULT_FC_ACCESS_P2 configuration Sonus Networks Interoperability Test Lab 43 of 53

44 SIP Server configuration: SIP server configuration to SAS1 associated with Trunkgroup P2_TG_SM 44 of 53 Sonus Networks Interoperability Test Lab

45 Following figure displays the SIP Server to SAS2 associated with Trunkgroup P2_TG_SM: Sonus Networks Interoperability Test Lab 45 of 53

46 Following figure displays the SIP Server configured with SBC 5200 to its SIP signaling IP address and associated with Trunkgroup P2_TG_NBS5K. 46 of 53 Sonus Networks Interoperability Test Lab

47 The following figure displays the SIP Server configured with End point EP_6000 s IP address and associated with Trunkgroup TG_EP_6000. Sonus Networks Interoperability Test Lab 47 of 53

48 5.4. Configure Routing Label Routing Label defines the Destination Peer address and the Trunk group to be used to associate its profiles for call processing. Following configuration defines the Routing Label to SBC of 53 Sonus Networks Interoperability Test Lab

49 Following configuration defines the Routing Label to Entity EP_6000. Sonus Networks Interoperability Test Lab 49 of 53

50 50 of 53 Sonus Networks Interoperability Test Lab

51 5.5. Configuring Standard Route Standard route can be defined based on the Destination Number and associate it to the Routing Label to be applied. The following images provide the Standard Routes for SBC 5200 and Entity EP_6000, defined to a prefix pattern match of 700 and 6000 respectively. Sonus Networks Interoperability Test Lab 51 of 53

52 Configure SIP Domain The SIP Domain configuration resolves the FQDN to its associated IP addresses. The following figure shows the SIP domain for SSM cluster. This will be resolved in to SAS1 and SAS2 IPs by DNS server. Note: Refer the following documents for information on these configurations for PSX redirector., _PSX_8.4_Provisioning_Guide_1.pdf _PSX_8.4_Product_Description_Guide_1.pdf 52 of 53 Sonus Networks Interoperability Test Lab

53 6 Conclusion These Application Notes describe the configuration steps required for Sonus SBC 5200, Sonus PSX as Rediretor to successfully interoperate with SSM V Sonus Networks Interoperability Test Lab 53 of 53