SBC 1000/2000 Configuration Guide with Lync 2013 for Windstream/ LPAETEC SIP Trunk Deployments

Transcription

1 SBC 1000/2000 Configuration Guide with Lync 2013 for Windstream/ LPAETEC SIP Trunk Deployments Application Notes Rev. 1.0 Last Updated: April 10, 2015 Revision Date Revised By Comments /03/2015 Roman Kokes Initial Publication 0.2 3/16/2015 Grant Gist Internal review 0.4 3/26/2015 Andy N. Tran Customer review 1.0 4/13/2015 Tech Pubs Final Edit and Release 2015 Sonus Networks, Inc. All Rights Reserved

2 Sonus Network Design Group 2 of 39

3 1 Document Overview Glossary Overview Introduction Audience Requirements Reference Configuration... 8 Network Topology Configuring Sonus SBC 1000 and SBC 2000 Series External Peer Side SBC Configuration Node Interfaces SIP profile Media Profile Voice Codec Profiles SIP Server Tables Static IP Route Table Signaling Groups Call Routing Table Transformation Tables Trunk Registration Internal Side SBC configuration Node Interfaces SIP Profile Media Profiles Voice Codec Profiles Signaling Group Sip Server Table Call Routing Table Transformation Tables Lync Server 2013 configuration Lync 2013 Configuration Settings Addition of the SBC to the Lync Server Adding the SBC to Lync Server 2013 Routing Sonus Network Design Group 3 of 39

4 5 SBC and Lync 2013 Specific Configurations Initial Setup for All Calls Calling number manipulation Called number Initiating Transfers with REFER Call transfer via REFER method Initiating Transfers with Re-INVITE Call transfer via Re-Invite method Sonus Network Design Group 4 of 39

5 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 Lync 2013 system and a SIP trunk group to PSTN. The objective of the document is to describe the configuration procedures to be followed during interoperability testing of SBC 1000 and SBC 2000 with Lync 2013 server over SIP trunk to PSTN. For additional information on Sonus SBC 1000 and SBC 2000 series, visit For additional information on Lync 2013, visit Glossary Term AOC B2B UA CP CPD CPE CTI DNIS IP MS PBX PSX SDOP SIP UUI Definition Advice Of Charge Back to Back User Agent Calling Party Call Progress Detection Customer Premise Equipment Cisco SIP Server is the CPE device in this case. Computer Telephony Integration Dialed Number Identification Service Internet Protocol Media Server Private Branch Exchange Policy Server Exchange Signaled Digits Out-Pulsed Session Initiation Protocol User to User Information Sonus Network Design Group 5 of 39

6 1.2 Overview The Sonus SBC 1000 and SBC 2000 session border controllers are designed to use the same application software, boot image and Survivable Branch Appliance software. They differ in the number of physical Ethernet connections and 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 1000 but is fully applicable to an SBC Introduction This document provides a configuration guide for Sonus SBC 1000 Series (Session Border Controller) when connecting to a SIP trunk group and a Lync 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 SIP trunk group to PSTN and the Lync 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 Lync 2013 product. There will be steps that require navigating the third-party 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 1000 and SBC 2000 can be obtained through the following: Phone: (Toll-free) or (Direct) Web: Sonus Network Design Group 6 of 39

7 2.2 Requirements The following equipment and software was used for the sample configuration provided: Sonus Equipment Type Version SBC 1000 SBC Build 369 3rd Party Equipment Type Version Microsoft Lync 2013 Mediation Server Polycom CX500 Lync Edition SIP Phone Windstream Equipment Type Version Broadsoft West Broadsoft platform R17 SP4 ACME SBC ACME Net-Net 4250 SC6.2.0 Patch 3 (Build 497) Build Date=02/12/10 Sonus Network Design Group 7 of 39

8 2.3 Reference Configuration A simulated enterprise site consisting of a Lync 2013 and a SIP trunk group to PSTN connected over the SBC The SBC 1000 was running software version Build 369 during testing. Network Topology Lync 2013 Sonus SBC 1000 PSTN Internal IP Network Windstream Figure 2.1 Network Topology The figure above represents the equipment used for the integration and certification testing. The SBC 1000 is used to route and facilitate calls between the PSTN and the Lync 2013 system. The SBC 1000 under test has 2 Ethernet ports configured. The SBC 2000 can have up to 4 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 1000 Network Deployment Guide or contact your local Sales team for information regarding the Sonus Network Design professional services offerings. Sonus Network Design Group 8 of 39

9 3 Configuring Sonus SBC 1000 and SBC 2000 Series The SBC 1000 and SBC 2000 share a common code base and user interface. In this example, we are using an SBC Internal Signaling Group: To/From Lync Call Routing: From Lync External Signaling Group: To/From Windstream Call Routing: From Windstream :5068 Lync :5060 Lync 2013 Signaling Group SIP over TCP :5060 SIP over UDP :5060 Windstream Figure 3.1 SBC 1000 SIP Trunk Diagram Sonus Network Design Group 9 of 39

10 3.1 External Peer Side SBC Configuration Node Interfaces The Sonus SBC 1000 allows you to configure the identification information, Physical Data Layer, and Networking Layer for the Ethernet ports. If you want to change the IP Address, you must configure the associated Logical Interface or use the Modify Ethernet IP task found under the Tasks tab. Settings for the Ethernet connection between the Sonus SBC 1000 and the public Internet are shown in the figures below. Figure 3.2 External Port Sonus Network Design Group 10 of 39

11 Figure 3.3 Logical Interface Sonus Network Design Group 11 of 39

12 SIP profile SIP Profiles control the how the Sonus SBC 1000/2000 communicates with SIP devices. They control important characteristics such as: session timers, SIP header customization, SIP timers, MIME payloads, and option tags. The default SIP profile used for the SBC 1000 for this testing effort is shown in the following figure. Figure 3.4 SIP profile Sonus Network Design Group 12 of 39

13 Media Profile Media Profiles allow you to specify the individual voice codecs and their associated settings for inclusion in a Media List. Different codecs provide varying levels of compression allowing one to reduce bandwidth requirements at the expense of voice quality. The Media Profile Used for the SBC 1000 is shown in the following figure and is for reference only. Figure 3.5 Media List Sonus Network Design Group 13 of 39

14 Voice Codec Profiles The Voice Codec Profiles used for the SBC 1000 in this testing effort are shown in the figures below. Figure 3.6 Voice codec configuration Figure 3.7 Voice codec configuration Sonus Network Design Group 14 of 39

15 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 server. The Table Entries also contain links to counters that are useful for troubleshooting. Figure 3.8 SIP Server Table Static IP Route Table The Static IP route table feature allows you to route subnets to different IP gateway.. Figure 3.9 SIP Host table Sonus Network Design Group 15 of 39

16 Signaling Groups 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. They are also the location from which Tone Tables and Action Sets are selected. In the case of SIP, they specify protocol settings and link to server, media and mapping tables. Figure 3.10 SIP Signaling Group to Windstream Sonus Network Design Group 16 of 39

17 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, which allow for flexible configuration of which calls are carried, and how they 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.11 Call Routing Table PSTN to Lync 2013 Sonus Network Design Group 17 of 39

18 Transformation Tables Transformation Tables facilitate the conversion of names, numbers and other fields when routing a call. They can, 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 a Transformation Table, and they are selected from there. In addition, Transformation tables are configurable as a reusable pool that Action Sets can reference. Figure 3.12 Transformation Table Match range Sonus Network Design Group 18 of 39

19 Trunk Registration Windstream requires authentication when establishing a SIP Trunk group to the SBC The Contact Registrant Table is used for registration with remote address and specific configuration.the Remote Authorization table is used for authorization configuration for remote registration. Figure 3.13 Contact registrant table Figure 3.14 Remote Authorization table Sonus Network Design Group 19 of 39

20 3.2 Internal Side SBC configuration Node Interfaces The Sonus SBC 1000 allows you to configure the Identification information, Physical Data Layer, and Networking Layer for the Ethernet ports. If you want to change the IP Address, you must configure the associated Logical Interface or use the Modify Ethernet IP task found under the Tasks tab. Settings for the Ethernet connection between the Sonus SBC 100 and Lync 2013 are shown in the figures below. Figure 3.15 Node Port Sonus Network Design Group 20 of 39

21 Figure 3.16 Logical Interface Sonus Network Design Group 21 of 39

22 SIP Profile SIP Profiles control the how the Sonus SBC 1000/2000 communicates with SIP devices. They control important characteristics such as: session timers, SIP header customization, SIP timers, MIME payloads, and option tags. The default SIP profile used for these tests is shown in the figure below. Figure 3.17 SIP profile Sonus Network Design Group 22 of 39

23 Media Profiles Media Profiles allow you to specify the individual voice codecs and their associated settings for inclusion in a Media List. Different codecs provide varying levels of compression allowing one to reduce bandwidth requirements at the expense of voice quality. The Media Profile used for these tests is shown in the figure below. Figure 3.18 Media List Sonus Network Design Group 23 of 39

24 Voice Codec Profiles The default voice codec profiles used in this testing effort are shown in the figures below. Figure 3.19 Voice codec configuration Figure 3.20 Voice codec configuration Sonus Network Design Group 24 of 39

25 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. They are also the location from which Tone Tables and Action Sets are selected. In the case of SIP, they specify protocol settings and link to server, media and mapping tables. Figure 3.21 Signaling Group Sonus Network Design Group 25 of 39

26 Sip Server Table SIP Server Tables contain information about the SIP devices connected to the Sonus SBC 1000/2000. They, in essence, 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.22 Sip Server Table Sonus Network Design Group 26 of 39

27 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, which allow for flexible configuration of which calls are carried, and how they 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.23 SIP Call Routing Table To PSTN Sonus Network Design Group 27 of 39

28 Transformation Tables Transformation Tables facilitate the conversion of names, numbers and other fields when routing a call. They can, 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 a Transformation Table, and they are selected from there. In addition, Transformation tables are configurable as a reusable pool that Action Sets can reference. Figure 3.24 Transformation Table to match US National Figure 3.25 Transformation Table to match US National Sonus Network Design Group 28 of 39

29 Figure 3.26 Transformation Table to match International calls Figure 3.27 Transformation Table to match US Redirected Sonus Network Design Group 29 of 39

30 Figure 3.28 Transformation Table to Match ALL Redirected Figure 3.29 Transformation Table to match ALL Calls Sonus Network Design Group 30 of 39

31 4 Lync Server 2013 configuration This section assumes that the Lync Server components have been installed along with Lync users. The user should be familiar with Lync Server Topology Builder, Lync Server Control Panel and Lync Server management Shell. This section does not cover the basic installation of Lync Server Lync 2013 Configuration Settings Addition of the SBC to the Lync Server. The Lync Server topology needs to be modified by adding the SBC as a Gateway device. The Gateway device is the interface to the Verizon SIP Trunk. 1. Open Lync Server Topology builder. 2. Load the current topology. 3. Expand the topology. 4. Right click the PSTN Gateways link in the left hand pane. 5. Select New IP/PSTN Gateway from the menu as shown and follow thru with the process. Figure 4.1 Create New Gateway Sonus Network Design Group 31 of 39

32 Figure 4.2 Define the FQDN of the Gateway Sonus Network Design Group 32 of 39

33 Figure 4.3 Enable IPV4/IPV6 Sonus Network Design Group 33 of 39

34 Figure 4.4 Define Trunk Port and Protocol Sonus Network Design Group 34 of 39

35 Adding the SBC to Lync Server 2013 Routing. In order for Lync Server 2013 to send calls to the Verizon SIP Trunk the SBC must be added to the routing. 1. Open Lync Server Control Panel and click on the Voice Routing link on the left hand pane. 2. Click on the Route tab on top of the right hand pane and scroll down to show the dialog below: Figure 4.5 Add Routing Sonus Network Design Group 35 of 39

36 Figure 4.6 Select Trunk Ensure the SBC is highlighted in the dialog shown above and click OK. At this point commit these changes to the topology. Sonus Network Design Group 36 of 39

37 5 SBC and Lync 2013 Specific Configurations Required settings for the SBC and Microsoft Lync 2013 product depend on the type of call scenario. 5.1 Initial Setup for All Calls Calling number manipulation Transformation tables were required for the purpose of mapping preconfigured Lync 2013 user extensions to established Windstream SIP Trunk DIDs. This is not expected to be a requirement for deployment scenarios. Called number Normal calling pattern was to dial all digits in E.164 format for both national and international calls. Other dialing patterns tested include Emergency calls. 5.2 Initiating Transfers with REFER Call transfer via REFER method Microsoft Lync Server 2013 needs additional configuration in order to enable SIP REFER Method. Refer support needs to be set to Enable sending refer to gateway under Trunk Configuration profile assigned to the appropriate SBC trunk. Figure 5.1 Sip Server Table Sonus Network Design Group 37 of 39

38 5.3 Initiating Transfers with Re-INVITE Call transfer via Re-Invite method Transferring a call to another phone number is supported via the RFC3261 method. No special flag is required to be set for this method. Ensure that on MS Lync 2013 under the Trunk Configuration element that REFER support is set to none. Sonus Network Design Group 38 of 39

39 Sonus Network Design Group 39 of 39