Configuring the Sonus SBC 5200 with Level(3) SIP Trunks and Lync 2013

Transcription

1 Configuring the Sonus SBC 5200 with Level(3) SIP Trunks and Lync 2013 Application Notes Last Updated: July 23, 2014 Sonus Equipment Type Version SBC 5200 SBC R0 3rd Party Equipment Type Version Lync 2013 PBX This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the prior written permission of Sonus. Contents 1 Document Overview... 4 Sonus Network Design Group

2 2 Introduction Audience Requirements Reference Configuration... 6 Network Topology Configuring Sonus SBC 5000 Series SBC Configuration Diagram SBC Naming Conventions SBC Configuration Internal Configuration External Configuration SBC Configuration Workflow Global Configuration SIP Max PDU Size UDP Port Range for RTP (optional) DSP Resource Allocation Codec Entry G.711u Codec Entry G Internal SBC configuration IP Interface Group IP Static Route SBC Configuration for Lync Profile Configuration Packet Service Profile (PSP) Address Context Configuration DNS Group SIP Signaling Port IP Peer SIP Trunk Group SBC Configuration for Fax (optional) Profile Configuration Packet Service Profile (PSP) IP Signaling Profile (IPSP) Address Context Configuration Zone Sonus Network Design Group 2 of 30

3 SIP Signaling Port IP Peer SIP Trunk Group External SBC Configuration IP Interface Group IP Static Route SBC configuration for Level(3) SIP Trunk Group 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 Lync 2013 Routing Routing Label Level(3) Routing Routing Label Routing Configuring Lync 2013 Communication Manager Adding External DIDs to Lync Sonus Network Design Group 3 of 30

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 Lync2013 and Level(3) SIP Trunk. SBC 5000 series functionality was compliance tested using a SIP trunk to Level(3) from an SBC The objective of the document is to describe the configuration procedures to be followed during interoperability testing of SBC 5000 series with Level(3). The interoperability tested was between Lync 2013, a Sonus SBC 5200, and Level(3) SIP Trunks. For additional information on Sonus SBC 5000 series, visit For additional information on Level(3), visit For additional information on Lync, visit Sonus Network Design Group 4 of 30

5 2 Introduction This document provides a configuration guide for Sonus SBC 5000 Series (Session Border Controller) when connecting to a Level(3) SIP Trunk and Lync 2013 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 Lync 2013 and the Level(3) SIP Trunk. 2.1 Audience This technical document is intended for telecommunication engineers with the purpose of configuring both the Sonus SBC 5000 and aspects of the Lync 2013 product. There will be steps that require navigating the thirdparty and Sonus SBC Command Line Interface (CLI). Understanding the basic concepts of IP/Routing and SIP/RTP is also necessary to complete the configuration and for troubleshooting, if necessary. 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 5000 can be obtained through the following: Phone: (Toll-free) or (Direct) Web: Requirements The following equipment and software was used for the sample configuration provided: Sonus Equipment Type Version SBC 5200 SBC R0 3rd Party Equipment Type Version Lync 2013 PBX Sonus Network Design Group 5 of 30

6 2.3 Reference Configuration A simulated enterprise site consisting of Polycom Phones serviced through Lync 2013 PBX. SIP Trunks were used to connect the SBC 5200 externally to Level(3) and internally to the Lync The SBC 5200 was running software version R0 during testing Network Topology Lync 2013 Sonus SBC 5000 PSTN Internal IP Network Figure 1 : Network Topology The figure above represents the equipment used for the integration and certification testing. The SBC 5000 is used to route and facilitate calls between Lync 2013 and the Level(3) SIP Trunk. The SBC 52x0 has 4 media ports: Media0, Media1, Media2, and Media3. Media0/Media1 are used for External connectivity and Media2/Media3 are used for Internal connectivity, if the default Sonus convention is desired. If deploying an SBC 52x0 using only two Media ports, then the convention should be to use Media0 (External) and Media2 (Internal). 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 professional services offerings. A 5200 was used for testing with only two Media ports configured due to the limited media capacity needed. Additional Media ports can be cabled and configured if the additional Media capacity is required. Sonus Network Design Group 6 of 30

7 3 Configuring Sonus SBC 5000 Series This section describes how to use the Sonus Command Line Interface (CLI) to configure the SBC 5000 Series. The SBC can equally be configured and managed by 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 guide. 3.1 SBC Configuration Diagram Internal External :5060 Lync 2013 Fax via ATA : IP Interface Group: INTERNAL_IPIG Zone: AVAYA_ZONE SIP Port: :5060 SIP TrunkGroup: AVAYA_TG IN-SIP-LYNC-2013/ OUT-SIP-LYNC-2013 SIP over TCP SIP over UDP FAX IP Interface Group: INTERNAL Zone: Collab_Demo_Trusted SIP Port: :5060 SIP TrunkGroup: FAX IP Interface Group: UNTRUSTED Zone: ZONE_UNTRUSTED SIP Port: :5060 SIP TrunkGroup: TWO-WAY-LEVEL-3 TWO-WAY-LEVEL-3 SIP over UDP Figure 2: SBC 5000 SIP Trunk Diagram The above diagram also shows the FAX Trunk Group. Fax machines typically get their own Trunk Group(s) which allows Fax-specific Packet Service Profile (PSP) and IP Signaling Profile (IPSP) configurations without affecting non-fax devices. While this document shows a Fax-specific Trunk Group, it does not have a Route or Routing Label to use it. Call Routing to a specific Fax Trunk Group is usually done by called/calling number routing (vs. trunk group routing) which is beyond the scope of this document. The Fax Trunk Group can share the same SIP signaling interface and Zone on the SBC. The preference to control the SIP transport protocol is configured in the IP Signaling Profile, which is applied at the Trunk Group level. This allows the proper SIP signaling transport to be used for both Lync 2013 and Fax machine even though they use different transport protocols with the same SIP signaling interface (SIP Signaling Port) on the SBC Sonus Network Design Group 7 of 30

8 3.2 SBC Naming Conventions SBC Configuration The SBC has both a System Name and a Compute Element (CE) Name (also referred to as a Host or Element Name) whose differentiation is relative to an High Availability deployment (one SBC active, one SBC standby). Each SBC server in an HA pair will have its own unique CE Name, while the HA pair will have a single System Name. Even an SBC deployed in standalone mode will have a separate System Name and CE Name. To follow Sonus best practice naming conventions, each server s CE Name will usually have a simple a/b suffix appended to the System Name: SBC System Name SBC CE Name (active) SBC CE Name (standby) SBC01 SBC01a SBC01b Internal Configuration Unique address contexts, other than default, are only needed when using overlapping IP address space. This deployment assumes no such overlapping IP space, thus all configurations are in address context default. Configuration Entity Lync 2013 FAX (optional) Address Context default default Zone Collab-Demo- Trusted_ZONE ZONE_INT_VOIP Trunk Group IN-SIP-LYNC-2013 OUT-SIP-LYNC-2013 FAX IP Peer Lync-2013 FAX IP Signaling Profile (IPSP) DEFAULT-SIP FAX Packet Service Profile (PSP) TWO-WAY-LEVEL-3 FAX Routing Label TO_LYNC2013 (not configured) External Configuration Unique address contexts, other than default, are only needed when using overlapping IP address space. This deployment assumes no such overlapping IP space, thus all configurations are in address context default. Configuration Entity Address Context Zone Trunk Group IP Peer IP Signaling Profile (IPSP) Packet Service Profile (PSP) Routing Label Level(3) default UNTRUSTED TWO-WAY-LEVEL-3 TWO-WAY-LEVEL-3 LEVEL-3_IP_PROFILE TWO-WAY-LEVEL-3 TO-LEVEL-3 Sonus Network Design Group 8 of 30

9 3.3 SBC Configuration Workflow ---- Global Configuration ----SIP Max PDU Size ----SIP Domain ----Media Port Range (optional) ----DSP Resource Allocation ----Codec Entry-G.711u ----Codec Entry-G Internal side Configuration ----IP Interface and IP Interface Group ----IP Static Routes ---- Lync 2013 Configuration ----Configuring Profiles ----Packet Service Profile ----IP Signaling Profile ----Configuring Address Context ----DNS Group ----Zone ----SIP Signaling Port ----IP Peer ----SIP Trunkgroup ---- Fax Configuration ----Configuring Profiles ----Packet Service Profile ----IP Signaling Profile ----Configuring Address Context ----Zone ----SIP Signaling Port ----IP Peer ----SIP Trunkgroup ---- External side Configuration ----IP Interface and IP Interface Group ----IP Static Routes ---- Level(3) Configuration ----Configuring Profiles ----Packet Service Profile ----IP Signaling Profile ----Configuring Address Context ----Zone ----SIP Signaling Port ----IP Peer ----SIP Trunkgroup Sonus Network Design Group 9 of 30

10 ---- Global Call Routing Configuration ----Level(3) Routing ----Routing Label ----Lync 2013 Routing ----Routing Label ----Routing 3.4 Global Configuration SIP Max PDU Size Increase the maximum SIP PDU size from 6kb to 60kb to accommodate larger SIP packets. set global signaling sipsigcontrols maxpdusizevalue pdusize60kb UDP Port Range for RTP (optional) The Sonus SBC 5000 series defaults to using the UDP port range of for RTP (media) traffic. Many enterprise networking devices, including security devices may assume a range of If required, the following configuration modifies the SBC to work within that more limited range with no changes to the existing devices. This is a global change. set system media mediaportrange baseudpport maxudpport DSP Resource Allocation This configuration only applies if the SBC 5000 has been deployed with (hardware) DSP resources. If it has not, executing this configuration step has no negative impact, but subsequent configuration sections (Packet Service Profiles) assume the SBC has DSP resources for transcoding and/or tone generation set system mediaprofile compression 90 tone Codec Entry G.711u Create a Codec Entry for the G711u codec with DTMF Relay configured for RFC2833, so that DTMF information will be carried in the audio path as RTP events (e.g method). G711u_20ms_2833_T38 G711u Name of codec entry Codec selected, Law selected (G.711 specific) 20 Packet size in milliseconds rfc2833 faxrelayorfallbacktog711 fallbacktog711 Type of DTMF Relay chosen: carriers DTMF as RTP events Fax treatment support for T.38 or G.711 fallback Modem treatment support for G.711 fallback Sonus Network Design Group 10 of 30

11 set profiles media codecentry G711u_20ms_2833_T38 codec g711 packetsize 20 law ULaw set profiles media codecentry G711u_20ms_2833_T38 dtmf relay rfc2833 removedigits enable set profiles media codecentry G711u_20ms_2833_T38 fax tonetreatment faxrelayorfallbacktog711 set profiles media codecentry G711u_20ms_2833_T38 modem tonetreatment fallbacktog Codec Entry G.729 Create another Codec Entry for the G729 codec with DTMF Relay configured for RFC2833 so that DTMF information will be carried in the audio path as RTP events (e.g method). G729ab_20ms_2833_T38 G729ab Name of codec entry Codec selected 20 Packet size in milliseconds rfc2833 faxrelayorfallbacktog711 fallbacktog711 Type of DTMF Relay chosen: carriers DTMF as RTP events Fax treatment support for T.38 or G.711 fallback Modem treatment support for G.711 fallback set profiles media codecentry G729ab_20ms_2833_T38 codec g729ab packetsize 20 set profiles media codecentry G729ab_20ms_2833_T38 dtmf relay rfc2833 removedigits enable set profiles media codecentry G729ab_20ms_2833_T38 fax tonetreatment faxrelayorfallbacktog711 set profiles media codecentry G729ab_20ms_2833_T38 modem tonetreatment fallbacktog Internal SBC configuration IP Interface Group The below configuration is for a Sonus 52x0 system using a single port for internal connectivity (the Sonus convention is to use Media 2 and Media 3 ports for internal connectivity). A similar configuration (not shown) for the Sonus 51x0 system, which only has a total of two media ports, would use the Media 1 port for internal connectivity per Sonus convention. SBC 5000 media ports do not have dedicated Internal/External roles, and while recommended, the Sonus convention does not have 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 professional services offerings. Create an IP Interface Group and assign it interfaces, including an IP address. default TRUSTED verde PKT0 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 pkt2) Gigabit Ethernet port used for internal signaling and media IP address for first internal media port 26 IP subnet prefix (subnet mask in CIDR format) Sonus Network Design Group 11 of 30

12 set addresscontext default ipinterfacegroup TRUSTED set addresscontext default ipinterfacegroup TRUSTED ipinterface PKT3 cename Verde set addresscontext default ipinterfacegroup TRUSTED ipinterface PKT3 portname pkt0 set addresscontext default ipinterfacegroup TRUSTED ipinterface PKT3 ipaddress prefix 26 set addresscontext default ipinterfacegroup TRUSTED ipinterface PKT3 mode inservice state enabled IP Static Route Create a default route to the subnet s IP nexthop 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 TRUSTED IP Interface Group name for the internal side of the SBC PKT0 Name for IP Interface (on pkt3) 100 Preference of the route within the Interface Group set addresscontext default staticroute TRUSTED PKT0 preference SBC Configuration for Lync Profile Configuration Packet Service Profile (PSP) Create a Packet Service Profile (PSP) for the Lync 2013 SIP trunk with a single codec specified. The PSP will be specified within the SIP Trunk Group configuration. We used the G.711u codec for the purpose of interworking with Level(3) SIP Trunks. TWO-WAY-LEVEL-3 G711u_20ms_2833_T38 conditional codecsallowedfortranscoding thisleg g711u otherleg Name of the PSP for the Lync 2013 TG Use of codec created earlier (global config section) Only transcode if certain conditions are met Specify transcode codecs for thisleg and/or otherleg Specify codec list applicable to thisleg Only specify codecs on thisleg Not-specified; otherleg should generally be omitted 184 ToS value in IP Header (TOS 184 = DSCP 46 = DiffServ EF) 101 RTP Payload type for Lync 2013 DTMF Relay set profiles media packetserviceprofile TWO-WAY-LEVEL-3 Sonus Network Design Group 12 of 30

13 set profiles media packetserviceprofile TWO-WAY-LEVEL-3 codec codecentry1 G711u_20ms_2833_T38 set profiles media packetserviceprofile TWO-WAY-LEVEL-3 packettopacketcontrol transcode conditional set profiles media packetserviceprofile TWO-WAY-LEVEL-3 packettopacketcontrol codecsallowedfortranscoding thisleg g711u set profiles media packetserviceprofile TWO-WAY-LEVEL-3 preferredrtppayloadtypefordtmfrelay 101 set profiles media packetserviceprofile TWO-WAY-LEVEL-3 typeofservice Address Context Configuration As mentioned earlier, as no overlapping IP addressing is used on the SBC in this document, all configuration will be done under the default Address Context DNS Group DNS Groups set DNS objects that may be used for DNS resolution within a particular Zone. The SBC has the capability to query an external DNS server to resolve hostnames. For scenarios where DNS servers are not available or accessible, the SBC also has the ability to have IP to hostname mappings configured locally 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 Collab-Demo-Trusted Zone and will send and receive SIP packets for Lync The numeric identifier for the Zone and SIP Signaling Port are independent and do not need to match. The SIP Signaling IP address can be the same as the IP address configured for the media interface, but having them match is optional and not a requirement. In this case, they are the different. The SIP Signaling IP address must always be in the same subnet as the media interface IP address. default Name of the address context Collab-Demo-Trusted Name of Zone for the Lync A unique numeric identifier (1-2048) for the signaling port TRUSTED IP Interface Group name for the internal side of the SBC sip_udp,sip_tcp Transport protocols allowed for SIP signaling port IPv4 address for the SIP Signaling Address for the SBC set addresscontext default zone Collab-Demo-Trusted sipsigport 2 ipinterfacegroup TRUSTED set addresscontext default zone Collab-Demo-Trusted sipsigport 2 transportprotocolsallowed sip_udp,sip_tcp set addresscontext default zone Collab-Demo-Trusted sipsigport 2 ipaddressv set addresscontext default zone Collab-Demo-Trusted sipsigport 2 dscpvalue 26 set addresscontext default zone Collab-Demo-Trusted sipsigport 2 state enabled mode inservice IP Peer Create an IP Peer for the Lync 2013 and assign it to the Collab-Demo-Trusted Zone. Sonus Network Design Group 13 of 30

14 The IP Peer entity is used on egress while the ingressipprefix parameter in the siptrunkgroup object is used on ingress, for determining the applicable SIP Trunk Group. default Name of the address context Collab-Demo-Trusted Name of Zone for Lync 2013 Lync-2013 Name of IP Peer for Lync Signaling port of Lync SIP Trunk Group Create a SIP Trunk Group(s) for the Lync 2013 and assign the appropriate Profile(s) configured/discussed earlier in this document. The SIP Trunk Group requires an explicit IP address (and mask) for the ingressipprefix. An FQDN cannot be configured. default Name of the address context Collab-Demo-Trusted Name of Zone for the Lync 2013 IN-SIP-LYNC-2013 OUT-SIP-LYNC-2013 Names for the SIP Trunk Groups to and from the Lync 2013 TRUSTED IP Interface Group name for the internal side of the SBC IP Address of Lync IP prefix (subnet mask in CIDR format) DEFAULT-SIP TWO-WAY-LEVEL-3 Earlier created IPSP is applied in the Trunk Group Earlier created PSP is applied in the Trunk Group set addresscontext default zone Collab-Demo-Trusted siptrunkgroup IN-SIP-LYNC media mediaipinterfacegroupname TRUSTED set addresscontext default zone Collab-Demo-Trusted siptrunkgroup IN-SIP-LYNC ingressipprefix set addresscontext default zone Collab-Demo-Trusted siptrunkgroup IN-SIP-LYNC policy signaling ipsignalingprofile DEFAULT-SIP set addresscontext default zone Collab-Demo-Trusted siptrunkgroup IN-SIP-LYNC policy media packetserviceprofile TWO-WAY-LEVEL-3 set addresscontext default zone Collab-Demo-Trusted siptrunkgroup IN-SIP-LYNC state enabled mode inservice 3.7 SBC Configuration for Fax (optional) Profile Configuration Packet Service Profile (PSP) Create a PSP for the FAX SIP Trunk Group with G.711u and G.729 codecs. This PSP will be specified within the SIP Trunk Group configuration. A Cisco PAP2T IAD was used for testing FAX functionality with Level(3) SIP Trunk for the purpose of this interoperability test. Sonus Network Design Group 14 of 30

15 FAX Name of the PSP for Faxing G711u_20ms_2833_T38 Use of codec created earlier (global config section) G729ab_20ms_2833_T38 Use of codec created earlier (global config section) Conditional Only transcode if certain conditions are met differentdtmfrelay Allow transcoding for different DTMF relay behaviors codecsallowedfortranscoding Specify transcode codecs for thisleg and/or otherleg thisleg Specify codec list applicable to thisleg g711u Only specify codecs on thisleg otherleg Not-specified; otherleg should generally be omitted 101 RTP Payload type for Lync 2013 DTMF Relay 13 RTP Payload Type for G.711 SID packets 184 ToS value in IP Header (TOS 184 = DSCP 46 = DiffServ EF) set profiles media packetserviceprofile FAX codec codecentry1 G711u_20ms_2833_T38 set profiles media packetserviceprofile FAX codec codecentry2 G729ab_20ms_2833_T38 set profiles media packetserviceprofile FAX packettopacketcontrol conditionsinadditiontonocommoncodec differentdtmfrelay enable set profiles media packetserviceprofile FAX preferredrtppayloadtypefordtmfrelay 101 set profiles media packetserviceprofile FAX silenceinsertiondescriptor g711sidrtppayloadtype 13 set profiles media packetserviceprofile FAX typeofservice IP Signaling Profile (IPSP) Create an IPSP for the FAX SIP Trunk Group. The IPSP will be specified within the SIP Trunk Group configuration. A number of flags and parameters are configured with the IPSP for interoperability with a fax machine. FAX Name of the IPSP used for the FAX Trunk set profiles signaling ipsignalingprofile FAX set profiles signaling ipsignalingprofile FAX ipprotocoltype siponly set profiles signaling ipsignalingprofile FAX egressipattributes privacy transparency disable set profiles signaling ipsignalingprofile FAX egressipattributes privacyinformation passertedid transparency disable set profiles signaling ipsignalingprofile FAX ingressipattributes flags nosdpin180supported enable sendsdpinsubsequent18x enable suppress183withoutsdp enable Address Context Configuration As mentioned earlier, as no overlapping IP addressing is used on the SBC in this document, all configuration will be done under the default Address Context Zone The Zone for the FAX SIP Trunk Group was previously created as ZONE_INT_VOIP in step Sonus Network Design Group 15 of 30

16 SIP Signaling Port The SIP Signaling Port for the FAX SIP Trunk Group was created as part of ZONE_INT_VOIP in step IP Peer Create an IP Peer with the signaling IP address of the LinkSys IAD and assign it to Zone: ZONE_INT_VOIP. The IP Peer entity is used on egress. The ingressipprefix parameter in the siptrunkgroup parameter is used on ingress, for determining the SIP Trunk Group assignment. default ZONE_INT_VOIP FAX Name of the address context Name of Zone for the fax device Name of IP Peer for fax device IP Address for fax device 5060 SIP signaling port for fax device set addresscontext default zone ZONE_INT_VOIP ippeer FAX set addresscontext default zone ZONE_INT_VOIP ippeer FAX ipaddress set addresscontext default zone ZONE_INT_VOIP ippeer FAX ipport SIP Trunk Group Create a SIP Trunk group towards the LinkSys PAP2T IAD and assign the corresponding Profiles configured earlier in this document. default ZONE_INT_VOIP FAX TRUSTED Name of the address context Name of Zone for the fax device Name of the SIP Trunk Group for the device IP Interface Group name for the internal side of the SBC IP Address for the device (ingressipprefix) 32 IP prefix (subnet mask in CIDR format) FAX FAX Earlier created IPSP is applied in the Trunk Group Earlier created PSP is applied in the Trunk Group set addresscontext default zone ZONE_INT_VOIP siptrunkgroup FAX media mediaipinterfacegroupname TRUSTED set addresscontext default zone ZONE_INT_VOIP siptrunkgroup FAX ingressipprefix set addresscontext default zone ZONE_INT_VOIP siptrunkgroup FAX policy signaling ipsignalingprofile FAX set addresscontext default zone ZONE_INT_VOIP siptrunkgroup FAX policy media packetserviceprofile FAX set addresscontext default zone ZONE_INT_VOIP siptrunkgroup FAX state enabled mode inservice Sonus Network Design Group 16 of 30

17 3.8 External SBC Configuration IP Interface Group The below configuration is for a Sonus 52x0 system using a single port for internal connectivity (the Sonus convention is to use Media 2 and Media 3 ports for internal connectivity). A similar configuration (not shown) for the Sonus 51x0 system, which only has a total of two Media ports, would use the Media 1 port for internal connectivity per Sonus convention. SBC 5000 Media ports do not have dedicated Internal/External roles, and while recommended, the Sonus convention does not have 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 professional services offerings. Create an IP Interface Group and assign it interfaces, including IP addresses. default UNTRUSTED verde PKT2 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 pkt0) Gigabit Ethernet port used for external signaling and media IP address for first external media port 27 IP subnet prefix (subnet mask in CIDR format) set addresscontext default ipinterfacegroup UNTRUSTED set addresscontext default ipinterfacegroup UNTRUSTED ipinterface PKT2 cename SBC01a set addresscontext default ipinterfacegroup UNTRUSTED ipinterface PKT2 portname pkt0 set addresscontext default ipinterfacegroup UNTRUSTED ipinterface PKT2 ipaddress prefix 27 set addresscontext default ipinterfacegroup UNTRUSTED ipinterface PKT2 mode inservice state enabled IP Static Route Create a default route to the subnet s IP nexthop for the Interface and IP Interface Group. default Name of the address context Destination IP Network (default route) 0 IP subnet prefix (subnet mask in CIDR format) IP Nexthop for subnet UNTRUSTED PKT2 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 set addresscontext default staticroute UNTRUSTED PKT2 preference 100 Sonus Network Design Group 17 of 30

18 3.9 SBC configuration for Level(3) SIP Trunk Group Profile Configuration Packet Service Profile (PSP) Create a Packet Service Profile (PSP) for the SIP trunk with G.711u and G.729 codecs.. The PSP will be specified within the SIP Trunk Group configuration. TWO-WAY-LEVEL-3 G711u_20ms_2833_T38 G729ab_20ms_2833_T38 conditional differentdtmfrelay codecsallowedfortranscoding thisleg g711u,g729 otherleg Name of the PSP for Level(3) Use of codec created earlier (global config section) Use of codec created earlier (global config section) Only transcode if certain conditions are met Allow transcoding for different DTMF relay behaviors Specify transcode codecs for thisleg and/or otherleg Specify codec list applicable to thisleg Only specify codecs on thisleg Not-specified; otherleg should generally be omitted 101 RTP Payload type for Lync 2013 DTMF Relay 13 RTP Payload Type for G.711 SID packets 2 Number of redundant packets for FAX 184 ToS value in IP Header (TOS 184 = DSCP 46 = DiffServ EF) set profiles media packetserviceprofile TWO-WAY-LEVEL-3 set profiles media packetserviceprofile TWO-WAY-LEVEL-3 codec codecentry1 G711u_20ms_2833_T38 set profiles media packetserviceprofile TWO-WAY-LEVEL-3 codec codecentry2 G729ab_20ms_2833_T38 set profiles media packetserviceprofile TWO-WAY-LEVEL-3 packettopacketcontrol transcode conditional set profiles media packetserviceprofile TWO-WAY-LEVEL-3 packettopacketcontrol codecsallowedfortranscoding thisleg g711u,g729 set profiles media packetserviceprofile TWO-WAY-LEVEL-3 packettopacketcontrol conditionsinadditiontonocommoncodec differentdtmfrelay enable set profiles media packetserviceprofile TWO-WAY-LEVEL-3 preferredrtppayloadtypefordtmfrelay 101 set profiles media packetserviceprofile TWO-WAY-LEVEL-3 silenceinsertiondescriptor g711sidrtppayloadtype 13 set profiles media packetserviceprofile TWO-WAY-LEVEL-3 t38 numberofredundantpackets 2 set profiles media packetserviceprofile TWO-WAY-LEVEL-3 typeofservice 184 ` IP Signaling Profile (IPSP) Create an IPSP for the Level(3) SIP Trunk Group. The IPSP will be specified within the SIP Trunk Group configuration. A number of flags and parameters are configured with the IPSP for interoperability with Level(3). LEVEL-3-SIP Name of the IPSP for Level(3) SIP Trunk set profiles signaling ipsignalingprofile LEVEL-3-SIP Sonus Network Design Group 18 of 30

19 set profiles signaling ipsignalingprofile LEVEL-3-SIP ipprotocoltype siponly set profiles signaling ipsignalingprofile LEVEL-3-SIP ingressipattributes flags nosdpin180supported enable sendsdpinsubsequent18x enabled suppress183withoutsdp enable Address Context Configuration As mentioned earlier, as no overlapping IP addressing is used on the SBC in this document, all configuration will be done under the default Address Context Zone This Zone groups the set of objects that is used for the communication to the Level(3) SIP Trunk. default UNTRUSTED Name of the address context Name of Zone for Level(3) SIP Trunk. 2 A unique numeric identifier (2-2048) for the zone set addresscontext default zone UNTRUSTED id 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 Level(3) zone and will send and receive SIP packets on the Level(3) SIP Trunk Group. The numeric identifier for the Zone and SIP Signaling Port are independent and do not need to match. The SIP Signaling IP address can be the same as the IP address configured for the media interface, but matching is optional and is not a requirement. In this case, they match. If they are different, the SIP Signaling IP address must be in the same subnet as the media interface IP address. default UNTRUSTED Name of the address context Name of Zone for Level(3) SIP Trunk 2 A unique numeric identifier (2-2048) for the signaling port UNTRUSTED IP Interface Group name for the external side of the SBC IPv4 address for this SIP Signaling Port 0 DiffServ Code Point value for SIP signaling traffic from SBC set addresscontext default zone UNTRUSTED sipsigport 3 ipinterfacegroup UNTRUSTED set addresscontext default zone UNTRUSTED sipsigport 3 ipaddressv set addresscontext default zone UNTRUSTED sipsigport 3 dscpvalue 0 set addresscontext default zone UNTRUSTED sipsigport 3 state enabled mode inservice Sonus Network Design Group 19 of 30

20 IP Peer Create an IP Peer with the signaling IP address of the Level(3) SIP Trunk and assign it to the EXTERNAL zone. The IP Peer entity is used on egress. The ingressipprefix parameter in the siptrunkgroup is used on ingress, for determining the SIP Trunk Group. default UNTRUSTED TWO-WAY-LEVEL-3 Name of the address context Name of Zone for Level(3) SIP Trunk Name of IP Peer for Level(3) SIP Trunk IP Address of Level(3) SIP peer 5060 SIP signaling port for Level(3) SIP Trunk set addresscontext default zone UNTRUSTED ippeer TWO-WAY-LEVEL-3 ipaddress ipport SIP Trunk Group Create a SIP Trunk Group for Level(3) and assign the corresponding Profiles configured earlier in this document. default Name of the address context UNTRUSTED Name of Zone for Level(3) SIP Trunk TWO-WAY-LEVEL-3 Name of the Level(3) SIP Trunk Group UNTRUSTED IP Interface Group name for the external side of the SBC IP Address of Level(3) peer (ingressipprefix) 32 IP prefix (subnet mask in CIDR format) TWO-WAY-LEVEL-3-IPSP Earlier created IPSP is applied in the Trunk Group TWO-WAY-LEVEL-3 Earlier created PSP is applied in the Trunk Group set addresscontext default zone UNTRUSTED siptrunkgroup TWO-WAY-LEVEL-3 media mediaipinterfacegroupname UNTRUSTED set addresscontext default zone UNTRUSTED siptrunkgroup TWO-WAY-LEVEL-3 ingressipprefix set addresscontext default zone UNTRUSTED siptrunkgroup TWO-WAY-LEVEL-3 policy signaling ipsignalingprofile LEVEL-3-SIP set addresscontext default zone UNTRUSTED siptrunkgroup TWO-WAY-LEVEL-3 policy media packetserviceprofile TWO-WAY-LEVEL-3 set addresscontext default zone UNTRUSTED siptrunkgroup TWO-WAY-LEVEL-3 state enabled mode inservice 3.10 Global Call Routing Configuration A Routing Label (RL) is a user-named object that contains a list of one or more next-hop peers - defined as Routing Label Routes - that can reach a specified destination ip address. 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. Sonus Network Design Group 20 of 30

21 For each call that successfully routes, a Routing Label is assigned. The SBC will advance through the list of RLRs until the call is completed or the RLR list is exhausted. The RL's Prioritization Type determines the order in which the RLR list will be processed. Routing Labels are 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 applied to a Trunk Group entity. When doing simple Trunk Group to Trunk Group routing (such as when there is only one internal PBX and one external SIP carrier), the SBC must have an ERP Profile which prioritizes the Trunk Group entity above other routing types. This allows routing of traffic from the ingress Trunk Group to an egress Trunk Group without further analyzing the Called Number. This prioritization can be accomplished by creating a new ERP Profile and applying it to all 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 trunkgroupcutthrough 2 entitytype none set profiles callrouting elementroutingpriority DEFAULT_IP entry trunkgroupcutthrough 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 set profiles callrouting elementroutingpriority DEFAULT_IP entry longdistanceoperator 1 entitytype trunkgroup set profiles callrouting elementroutingpriority DEFAULT_IP entry othertrunkgroupchosen 2 entitytype none set profiles callrouting elementroutingpriority DEFAULT_IP entry othertrunkgroupchosen 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 Sonus Network Design Group 21 of 30

22 Lync 2013 Routing Routing Label Create a Routing Label with a single Routing Label Route to bind the Lync 2013 Trunk Group with the IP Peer TO_LYNC2013 Name of the Routing Label for Lync 2013 Sequence The prioritization of Routing Label Routes within a Routing Label 1 The first Routing Label Route within the Routing Label OUT-SIP-LYNC Trunk Group for Lync 2013 Lync-2013 IP Peer for Lync 2013 set global callrouting routinglabel TO_LYNC2013 routeprioritizationtype sequence action routes routinglabelroute 1 trunkgroup OUT-SIP-LYNC ippeer Lync-2013 inservice inservice Level(3) Routing Routing Label Create a Routing Label with a single Routing Label Route to bind the Level(3) Trunk Group with the Level(3) IP Peer TO-LEVEL-3 Sequence Name of the Routing Label for Level(3) The prioritization of Routing Label Routes within a Routing Label 1 The first Routing Label Route within the Routing Label TWO-WAY-LEVEL-3 TWO-WAY-LEVEL-3 Trunk Group for Level(3) IP Peer for Level(3) set global callrouting routinglabel TO-LEVEL-3 routeprioritizationtype sequence action routes routinglabelroute 1 trunkgroup TWO-WAY-LEVEL-3 ippeer TWO-WAY-LEVEL-3 inservice inservice Routing Routing must be put in place to send calls to the correct destination. For the purpose of this interoperability test we have used trunk group routing, but additional routing options may be used. See Appendix B for more information. Create Route entries for Trunk Group routing with Matching Criteria and a Route Label destination. trunkgroup IN-SIP-LYNC VERDE 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 Sonus Network Design Group 22 of 30

23 System Name in all upper case (not hostname / element name) standard Sonus_NULL Sonus_NULL all all ALL none Sonus_NULL TO-LEVEL-3 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 trunkgroup TWO-WAY-LEVEL-3 VERDE standard Sonus_NULL Sonus_NULL all all ALL none Sonus_NULL TO_LYNC2013 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 IN-SIP-LYNC VERDE standard Sonus_NULL Sonus_NULL all all ALL none Sonus_NULL routinglabel TO-LEVEL-3 set global callrouting route trunkgroup TWO-WAY-LEVEL-3 VERDE standard Sonus_NULL Sonus_NULL all all ALL none Sonus_NULL routinglabel TO_LYNC2013 Sonus Network Design Group 23 of 30

24 4 Configuring Lync 2013 Communication Manager This section assumes that the Lync 2013 components have been installed along with Lync clients. The user should be familiar with Lync 2013 Server Administration. This section does not cover the basic installation of Lync Adding External DIDs to Lync 2013 Routing for all outgoing DID calls or calls that route through Lync2013 to external phone numbers must be configured in the Lync 2013 server. Remote Desktop to the Lync 2013 Server and login as lync2013\administrator: Sonus Network Design Group 24 of 30

25 Select Voice Routing from the menu on the left and then select the Route Tab to get to the routing table: Since all of our outgoing calls are destined to the Verde SBC, we will add all the DIDs to the Verde SBC Double click on the Verde SBC to bring up the GUI to add all the numbers that will be dialed out to. Sonus Network Design Group 25 of 30

26 To add a number simply enter in in the field and click on the Add button. Sonus Network Design Group 26 of 30

27 Click OK to go back to the routing screen. Here we will need to the changes for them to take effect. From the pull down menu shown in the Diagram below, select from Commit all from the Commit menu. Sonus Network Design Group 27 of 30

28 Sonus Network Design Group 28 of 30

29 Click OK and the routing is saved. Sonus Network Design Group 29 of 30

30 Sonus Network Design Group 30 of 30