Configuration Note. Connecting XO Communications SIP Trunking Service to Microsoft Lync Server Using

Mediant 800 MSBG E-SBC, Mediant 1000 MSBG E-SBC and Mediant 3000 E-SBC Media Gateway Configuration Note Connecting XO Communications SIP Trunking Service to Microsoft Lync Server 2010 Using AudioCodes Mediant 800 E-SBC, Mediant 1000 MSBG E-SBC and Mediant 3000 E-SBC Media Gateway Document #: LTRT-40800

Configuration Note Contents Table of Contents 1 Introduction... 9 2 Testing Considerations... 11 3 Scenario Overview... 13 4 Configuring Microsoft Lync Server 2010... 15 4.1 Configuring the AudioCodes E-SBC device as a IP/PSTN Gateway. 16 4.2 Associating the IP/PSTN Gateway with the Mediation Server... 21 4.3 Configuring the Route on the Lync Server 2010... 27 5 Configuring E-SBC Device... 37 5.1 Step 1: Configure IP Addresses... 39 5.1.1.1 Configuring the LAN IP Addresses...39 5.1.1.2 Assigning WAN IP Addresses...41 5.2 Step 2: Enable the SIP SBC Application Mode... 43 5.3 Step 3: Configure SIP Interfaces... 44 5.4 Step 4: Configure Media Realm... 45 5.5 Step 5: Configure SRD Table... 46 5.6 Step 6: Configure SBC General Settings... 48 5.7 Step 7: Configure the Number of Media Channels... 49 5.8 Step 8: Configure the Proxy Sets... 50 5.9 Step 9: Configure the IP Groups... 52 5.10 Step 10: Configure the Voice Coders... 56 5.10.1 Step 11: Define Silence Suppression and Comfort Noise... 58 5.11 Step 12: Configure IP Profile Settings... 59 5.12 Step 13: Configure SBC IP-to-IP Routing Rules... 63 5.13 Step 14: Configure Manipulation Rules... 65 5.13.1 Configure IP to IP Inbound Manipulation Rules... 66 5.13.2 Configure IP to IP Outbound Manipulation Rules... 67 5.13.3 Configure Header Manipulation Rules... 69 5.14 Step 15: Configure IP Group for Call Forwarding... 71 5.15 Step 16: Configure IP Group for P-Asserted Identity Header Insertion72 5.16 Step 17: Configuring SIP General Parameters... 73 5.17 Step 18: Defining Reasons for Alternative Routing... 76 6 Troubleshooting... 79 6.1 Debugging Procedures... 79 6.1.1 Case Reporting Procedures... 79 6.1.2 Syslog... 80 6.1.3 Wireshark Network Sniffer... 82 6.2 Verifying Firmware... 86 XO Communications and Microsoft Lync 3 June 2011

XO Communications and Microsoft Lync List of Figures Figure 3-1: Scenario Overview... 13 Figure 4-1: Starting the Lync Server Topology Builder... 16 Figure 4-2: Topology Builder Options... 17 Figure 4-3: Save Topology... 17 Figure 4-4: Downloaded Topology... 18 Figure 4-5: New IP/PSTN Gateway... 19 Figure 4-6: Define New IP/PSTN Gateway... 19 Figure 4-7: IP/PSTN Gateway... 20 Figure 4-8: Associating Mediation Server with IP/PSTN Gateway... 21 Figure 4-9: Before Associating IP/PSTN Gateway to a Mediation Server... 22 Figure 4-10: After Associating IP/PSTN Gateway to Mediation Server... 23 Figure 4-11: Media Server PSTN Gateway Association Properties... 24 Figure 4-12: Publishing Topology... 24 Figure 4-13:Publish Topology Confirmation... 25 Figure 4-14: Publish Topology Confirmation screen... 25 Figure 4-15: Publish Topology Successfully Completed... 26 Figure 4-16: Lync Server Control Panel... 27 Figure 4-17: Lync Server Credentials... 28 Figure 4-18: CSCP Home page... 28 Figure 4-19: Voice Routing Option... 29 Figure 4-20: Route Option... 30 Figure 4-21: Adding New Voice Route... 31 Figure 4-22: List of Deployed Gateways... 32 Figure 4-23: Selecting the PSTN Gateway... 32 Figure 4-24: Associating PSTN Usage to PSTN Gateway... 33 Figure 4-25: Confirmation of New Voice Route... 34 Figure 4-26: Committing Voice Routes... 34 Figure 4-27: Uncommitted Voice Configuration Settings... 35 Figure 4-28: Voice Routing Configuration Confirmation... 36 Figure 4-29: Voice Routing Screen Displaying Committed Routes... 36 Figure 5-1: Web Interface Showing Basic/Full Navigation Tree Display... 38 Figure 5-2: Multiple Interface Table Page... 39 Figure 5-3: Connections Page... 40 Figure 5-4: Defining LAN Data-Routing IP Address... 40 Figure 5-5: Configuring the WAN IP Address... 41 Figure 5-6: Selecting WAN Interface for VoIP Traffic in Multiple Interface Table Page... 42 Figure 5-7: Application Enabling... 43 Figure 5-8: SIP Interfaces... 44 Figure 5-9: Media Realms... 45 Figure 5-10: SRD Table... 46 Figure 5-11: IP Media Channels Settings... 49 Figure 5-12: Proxy Set ID 3 for XO Communications SIP Trunk... 50 Figure 5-13: Proxy Set ID 1 for Lync Mediation Server... 51 Figure 5-14: Proxy Set ID 6 for Fax Supporting Media Gateway... 51 Figure 5-15: IP Group 3 Table... 52 Figure 5-16: IP Group 1 Table Page... 53 AudioCodes Gateway and Microsoft Lync 4 Document #: LTRT-40800

Configuration Note Contents Figure 5-17: IP Group 5 Table Page... 54 Figure 5-18: IP Group 6 Table Page... 55 Figure 5-19: Coders Table Fax Gateway & XO SIP Trunk... 56 Figure 5-20: Coder Group Table 1 - Mediation Server... 57 Figure 5-21: RTP/RTCP Settings Page... 58 Figure 5-22: IP Profile Page- Mediation Server... 59 Figure 5-23: IP Profile Page- XO Communications SIP Trunk & Fax Gateway... 61 Figure 5-24: IP2IP Routing Table Page... 63 Figure 5-25: IP to IP Inbound Manipulation Page... 66 Figure 5-26: IP to IP Outbound Manipulation Page... 67 Figure 5-27: Message Manipulations Page... 69 Figure 5-28: IP Profile Settings for Call Forwarding numbers... 71 Figure 5-29: IP Profile Settings for Inserting P-Asserted Identity Header to all Lync calls... 72 Figure 5-30: SIP General Parameters Page... 73 Figure 5-31: Reasons for Alternative Routing Page... 76 Figure 5-32: Proxy & Registration Page... 77 Figure 5-33: Proxy Set ID 2 for Lync Mediation Server... 78 Figure 6-1: AudioCodes' Proprietary Syslog Server... 80 Figure 6-2: Enabling Syslog... 80 Figure 6-3: Selecting Interface Currently used by the PC... 82 Figure 6-4: Configuring Wireshark Display Options... 83 Figure 6-5: Captures Packets... 84 Figure 6-6: Viewing VoIP Call Flows... 84 Figure 6-7: Playing G.711 RTP Streams... 85 Figure 6-8: Analyzing the RTP Data... 85 Figure 6-9: Viewing active firmware version... 86 XO Communications and Microsoft Lync 5 June 2011

XO Communications and Microsoft Lync Reader s Notes AudioCodes Gateway and Microsoft Lync 6 Document #: LTRT-40800

Configuration Note Notices Notice This document describes the procedure for integrating the XO Communications SIP Trunking service with Microsoft Lync Server using the AudioCodes Mediant 800 MSBG-E-SBC, Mediant 1000 MSBG E-SBC and Mediant 3000 E-SBC Media Gateway. Information contained in this document is believed to be accurate and reliable at the time of printing. However, due to ongoing product improvements and revisions, AudioCodes cannot guarantee the accuracy of printed material after the Date Published nor can it accept responsibility for errors or omissions. Updates to this document and other documents can be viewed at http://www.audiocodes.com/downloads. Copyright 2011 AudioCodes Ltd. All rights reserved. This document is subject to change without notice. Date Published: June-16-2011 Trademarks AudioCodes, AC, AudioCoded, Ardito, CTI2, CTI², CTI Squared, HD VoIP, HD VoIP Sounds Better, InTouch, IPmedia, Mediant, MediaPack, NetCoder, Netrake, Nuera, Open Solutions Network, OSN, Stretto, TrunkPack, VMAS, VoicePacketizer, VoIPerfect, VoIPerfectHD, What s Inside Matters, Your Gateway To VoIP and 3GX are trademarks or registered trademarks of AudioCodes Limited. All other products or trademarks are property of their respective owners. WEEE EU Directive Pursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed of with unsorted waste. Please contact your local recycling authority for disposal of this product. Customer Support Customer technical support and service are generally provided by AudioCodes Distributors, Partners, and Resellers from whom the product was purchased. For technical support for products purchased directly from AudioCodes, or for customers subscribed to AudioCodes Customer Technical Support (ACTS), contact support@audiocodes.com. Abbreviations and Terminology Each abbreviation, unless widely used, is spelled out in full when first used. Note: Throughout this guide, the term E-SBC device refers to AudioCodes' Mediant 800 MSBG E-SBC, Mediant 1000 MSBG E-SBC and the Mediant 3000 E-SBC Media Gateway. XO Communications and Microsoft Lync 7 June 2011

XO Communications and Microsoft Lync Related Documentation Manual Name LTRT-26901_SIP_CPE_Release_Notes_Ver._6.2.pdf LTRT-52306_SIP_CPE_Product_Reference_Manual_Ver_6.2.pdf LTRT-27001 Mediant 1000 MSBG User's Manual Ver 6.2.pdf LTRT-40809 Mediant 1000 MSBG Installation Manual Ver 6.2.pdf LTRT-89710 Mediant 3000 SIP User's Manual Ver 6.2.pdf LTRT-94708 Mediant 3000 SIP-MGCP-MEGACO Installation Manual Ver 6.2.pdf AudioCodes Gateway and Microsoft Lync 8 Document #: LTRT-40800

Configuration Note 1. Introduction 1 Introduction This Configuration Guide describes a sample configuration for a network that uses the AudioCodes Mediant 800 MSBG E-SBC, Mediant 1000 MSBG E SBC or the Mediant 3000 E-SBC Media Gateway to facilitate a connection between Microsoft Lync 2010 and XO Communications SIP Trunking service for superior voice quality services. The Mediant 800 MSBG E-SBC is a networking device that combines multiple service functions such as a Media Gateway, Session Border Controller (SBC), Data Router and Firewall, LAN switch, WAN access, Stand Alone Survivability (SAS) and an integrated general-purpose server. The Mediant 1000 MSBG E-SBC is all-in-one multi-service access solution products for Service Providers (SME s) offering managed services and distributed Enterprises seeking integrated services. This multi-service business gateway is designed to provide converged Voice & Data services for business customers at wire speed, while maintaining SLA parameters for superior voice quality. The Mediant 1000 MSBG E-SBC is based on AudioCodes VoIPerfect Media Gateway technology, combined with Enterprise class Session Border Controller, Data & Voice security elements, Data Routing, LAN Switching and WAN Access. These services allow smooth connectivity to cloud services, while providing protection to the end customer. The Mediant 3000 E-SBC Media Gateway is a High Availability VoIP Gateway and Enterprise Class SBC for medium and large enterprises. Note: The scope of this document does not cover security aspects for connecting the SIP Trunk to the Microsoft Lync environment. Security measures should be implemented in accordance with your organization s security policies. For basic security guidelines, see the AudioCodes Security Guidelines. XO Communications and Microsoft Lync 9 June 2011

XO Communications and Microsoft Lync Reader s Notes AudioCodes Gateway and Microsoft Lync 10 Document #: LTRT-40800

Configuration Note 2. Testing Considerations 2 Testing Considerations Note the following special considerations for the XO Communications test environment: G.711 U-law is the only codec supported for this application. Music on hold does not work properly on XO Communications infrastructure, which forces the utilization of transcoding to bridge the two networks for proper RTCP handling in support of the feature. It is imperative that thehe XO side is properly configured enable Music on Hold to work properly. Please contact XO support to request this change. Change requires the following support a=sendonly. Voice mail, Auto Attendant, and Response Groups should work; however were not tested during the certification process. Transfer calls were tested with the Microsoft Lync environment pre-configured to not send REFER messages towards the SIP trunk. Header manipulation rules are required features supported by the E-SBC to add Diversion and P-Asserted-Identity headers. These headers must be present when sending calls to XO Communications for call forward and outbound caller ID to operate. This functionality is referenced in the Header Manipulation section of step 10 (see Section 5.13 on page 65) and also in step 11 (see Section 5.14 on page 71 ) and step12 (see Section 5.12 on page 63) for configuring the IP Profile parameters for Incoming and Outgoing Message Manipulation Set(s) of the AudioCodes E-SBC. By default Microsoft Lync sends outbound call with FROM and TO number in E164 format. The AudioCodes E-SBCs feature for manipulation was utilized to remove the + sign. This is a required feature configuration on the AudioCodes E-SBC to enable interworking between Microsoft Lync and XO Communications SIP Trunk service. XO Communications and Microsoft Lync 11 June 2011

XO Communications and Microsoft Lync Reader's Notes AudioCodes Gateway and Microsoft Lync 12 Document #: LTRT-40800

Configuration Note 3. Scenario Overview 3 Scenario Overview The configuration scenario described in this document includes the following setup: An Enterprise has a deployed Microsoft Lync server 2010 in its private network for enhanced communication within the company. The enterprise decides to offer its employees Enterprise voice and to connect the company to the PSTN network using the XO Communications SIP Trunking service. The setup requirements are as follows: While the Microsoft Lync Server 2010 environment is located on the Enterprise's Local Area Network (LAN), the XO Communications SIP Trunks are located on the WAN. Microsoft Lync Server 2010 works with the TCP transport type, while the XO Communications SIP trunk works on the SIP over UDP transport type. Both Microsoft Lync Server 2010 and XO Communications SIP Trunk support the G.711-Ulaw coder type. Support for early media handling Support for call forwarding The figure below illustrates an overview of the configuration scenario. Figure 3-1: Scenario Overview The devices and their load are as follows: XO Communications: SONUS NBS: V07.03.01 R006 Broadsoft AS: Rel_17.0_1.458 XO Communications and Microsoft Lync 13 June 2011

XO Communications and Microsoft Lync AudioCodes: Mediant 1000 MSBG E-SBC: 6.20A.023.003 MediaPack 114: 6.20A.021.004 MicroSoft: MicroSoft Lync Server 2010 AudioCodes Gateway and Microsoft Lync 14 Document #: LTRT-40800

Configuration Note 4. Configuring Microsoft Lync Server 2010 4 Configuring Microsoft Lync Server 2010 This section describes how to configure the Microsoft Lync Server 2010 to operate with the E-SBC device. This section describes the following procedures: 1. Configuring the E-SBC device as an IP/PSTN Gateway. See Section 4.1 on page 16. 2. Associating the IP/PSTN Gateway with the Mediation Server. See Section 4.2 on page 21. 3. Configuring a Route to utilize the SIP trunk connected to the E-SBC device. See Section 4.3 on page 27. Note: Dial Plans, Voice Policies, and PSTN usages are also necessary for enterprise voice deployment; however, they are beyond the scope of this document. XO Communications and Microsoft Lync 15 June 2011

XO Communications and Microsoft Lync 4.1 Configuring the AudioCodes E-SBC device as a IP/PSTN Gateway This section describes how to configure the E-SBC device as an IP/PSTN Gateway. Note: The Microsoft Lync Topology Builder interface dialogs refer to the E-SBC device as an IP/PSTN gateway or PSTN gateway. To configure the E-SBC device as a IP/PSTN Gateway and associating it with the Mediation Server: 1. On the server where the Topology Builder is located, start the Microsoft Lync Server 2010 Topology Builder: Click Start, select All Programs, then select Lync Server Topology Builder. Figure 4-1: Starting the Lync Server Topology Builder AudioCodes Gateway and Microsoft Lync 16 Document #: LTRT-40800

Configuration Note 4. Configuring Microsoft Lync Server 2010 The following screen is displayed: Figure 4-2: Topology Builder Options 2. Choose Download Topology from the existing deployment and click OK. You are prompted to save the Topology which you have downloaded. Figure 4-3: Save Topology XO Communications and Microsoft Lync 17 June 2011

XO Communications and Microsoft Lync 3. Enter new File Name and Save this action enables you to rollback from any changes you make during the installation. The Topology Builder screen with the topology downloaded is displayed. Figure 4-4: Downloaded Topology 4. Expand the Site; right-click on the IP/PSTN Gateway and choose New IP/PSTN Gateway. AudioCodes Gateway and Microsoft Lync 18 Document #: LTRT-40800

Configuration Note 4. Configuring Microsoft Lync Server 2010 Figure 4-5: New IP/PSTN Gateway Figure 4-6: Define New IP/PSTN Gateway 5. Enter the FQDN of the E-SBC device (i.e. E-SBC.OCSW14.local ) and click OK. Note that the listening port for the Gateway is 5067 and the transport type is TLS. In certification testing for the XO Communications SIP Trunk, listening port 5060 was used with transport protocol TCP. The E-SBC device is now added as an IP/PSTN Gateway. XO Communications and Microsoft Lync 19 June 2011

XO Communications and Microsoft Lync Figure 4-7: IP/PSTN Gateway AudioCodes Gateway and Microsoft Lync 20 Document #: LTRT-40800

Configuration Note 4. Configuring Microsoft Lync Server 2010 4.2 Associating the IP/PSTN Gateway with the Mediation Server This section describes how to associate the IP/PSTN Gateway (E-SBC device) with the Mediation Server. To associate the IP/PSTN Gateway with the Mediation Server: 1. Right-click on the Mediation Server to use with the IP/PSTN Gateway (i.e. Mediation2.OCSW14.local) and choose Edit Properties. Figure 4-8: Associating Mediation Server with IP/PSTN Gateway XO Communications and Microsoft Lync 21 June 2011

XO Communications and Microsoft Lync The following screen is displayed: Figure 4-9: Before Associating IP/PSTN Gateway to a Mediation Server 2. In the top-left corner, choose PSTN gateway and in the Mediation Server PSTN gateway pane, mark the E-SBC device that is designated as the IP/PSTN gateway (i.e. E-SBC.OCSW14.local ) and click Add to associate it with this Mediation Server. Note that there are two sub-panes, one including a list of IP/PSTN gateways not associated with the Mediation Server and one including a list of IP/PSTN gateways associated with the Mediation server. AudioCodes Gateway and Microsoft Lync 22 Document #: LTRT-40800

Configuration Note 4. Configuring Microsoft Lync Server 2010 Figure 4-10: After Associating IP/PSTN Gateway to Mediation Server In the Mediation Server PSTN gateway pane, the IP/PSTN Gateway that you associated with the Mediation Server is displayed with an adjacent Green. 3. Click OK. XO Communications and Microsoft Lync 23 June 2011

XO Communications and Microsoft Lync Figure 4-11: Media Server PSTN Gateway Association Properties 4. In the Lync Server main menu, choose Action > Publish Topology. Figure 4-12: Publishing Topology AudioCodes Gateway and Microsoft Lync 24 Document #: LTRT-40800

Configuration Note 4. Configuring Microsoft Lync Server 2010 The Publish Topology screen is displayed. Figure 4-13:Publish Topology Confirmation 5. Click Next. The Topology Builder attempts to publish your topology. Figure 4-14: Publish Topology Confirmation screen XO Communications and Microsoft Lync 25 June 2011

XO Communications and Microsoft Lync Wait until the publish topology process has ended successfully. Figure 4-15: Publish Topology Successfully Completed 6. Click Finish. AudioCodes Gateway and Microsoft Lync 26 Document #: LTRT-40800

Configuration Note 4. Configuring Microsoft Lync Server 2010 4.3 Configuring the Route on the Lync Server 2010 This section describes how to configure a Route on the Lync server and associates it with the IP/PSTN gateway. To configure the route on the Lync server: 1. Open the Communication Server Control Panel (CSCP), click Start, select All Programs, and select Lync Server Control Panel. Figure 4-16: Lync Server Control Panel 2. You are prompted for credentials; enter your domain username and password. XO Communications and Microsoft Lync 27 June 2011

XO Communications and Microsoft Lync Figure 4-17: Lync Server Credentials The CSCP Home page is displayed. Figure 4-18: CSCP Home page 3. In the Navigation pane, select the Voice Routing option. AudioCodes Gateway and Microsoft Lync 28 Document #: LTRT-40800

Configuration Note 4. Configuring Microsoft Lync Server 2010 Figure 4-19: Voice Routing Option 4. In the Voice Routing menu at the top of the page, select the Route option. XO Communications and Microsoft Lync 29 June 2011

XO Communications and Microsoft Lync Figure 4-20: Route Option 5. In the content area toolbar, click. 6. In the Build a Pattern to Match pane, fill in a Name for this route (i.e SIP Trunk Route) and a Pattern to Match for the phone numbers you wish this route to handle. In this example, the pattern to match is *, which implies to match all numbers. 7. Click Add. AudioCodes Gateway and Microsoft Lync 30 Document #: LTRT-40800

Configuration Note 4. Configuring Microsoft Lync Server 2010 Figure 4-21: Adding New Voice Route 8. Associate the route with the IP/PSTN gateway you created above; scroll down to the Associated Gateways pane and click Add. A list of all the deployed Gateways is displayed. XO Communications and Microsoft Lync 31 June 2011

XO Communications and Microsoft Lync Figure 4-22: List of Deployed Gateways 9. Select the IP/PSTN Gateway you created above and click OK. Figure 4-23: Selecting the PSTN Gateway AudioCodes Gateway and Microsoft Lync 32 Document #: LTRT-40800

Configuration Note 4. Configuring Microsoft Lync Server 2010 10. Associate a PSTN Usage to this route. In the Associated PSTN Usages toolbar, click Select and add the associated PSTN Usage. Figure 4-24: Associating PSTN Usage to PSTN Gateway 11. Click the OK button in the toolbar at the top of the New Voice Route pane. XO Communications and Microsoft Lync 33 June 2011

XO Communications and Microsoft Lync Figure 4-25: Confirmation of New Voice Route 12. In the Content area Toolbar, click on the arrow adjacent to the Commit button; a drop-down menu is displayed; select the Commit All option. Figure 4-26: Committing Voice Routes AudioCodes Gateway and Microsoft Lync 34 Document #: LTRT-40800

Configuration Note 4. Configuring Microsoft Lync Server 2010 13. In the Uncommitted Voice Configuration Settings window, click Commit. Figure 4-27: Uncommitted Voice Configuration Settings XO Communications and Microsoft Lync 35 June 2011

XO Communications and Microsoft Lync 14. A message is displayed, confirming a successful voice routing configuration; in the Microsoft Lync Server 2010 Control Panel prompt, click Close. Figure 4-28: Voice Routing Configuration Confirmation The new committed Route is now displayed in the Voice Routing screen. Figure 4-29: Voice Routing Screen Displaying Committed Routes AudioCodes Gateway and Microsoft Lync 36 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device 5 Configuring E-SBC Device This section provides step-by-step procedures for configuring the E-SBC device. The following describes the steps required to configure the E-SBC device : Step 1: Configure IP Addresses. See Section 5.1 Step 2: Enable the SBC Capabilities. See Section 5.2 Step 3: Configure the SIP Interfaces. See Section 5.3. Step 4: Configure the Media Realm. See Section 5.4. Step 5: Configure the SRD table. See Section 5.5. Step 6: Configure SBC General Settings. See Section 5.6. Step 7: Configure the Number of Media Channels. See Section 5.7. Step 8: Configure the Proxy Sets. See Section 5.8. Step 9: Configure the IP Groups. See Section 5.9. Step 10: Configure the Voice Coders. See Section 5.10. Step 11: Define Silence Suppression and Comfort Noise. See Section 5.10.1. Step 12: Configure IP Profile Settings. See Section 5.11. Step 13: Configure IP-to-IP Routing Setup. See Section 5.12. Step 14: Configure Manipulation Rules. See Section 5.13. Step 15: Configuring IP Profile for Call Forwarding. See Section 5.14. Step 16: Configuring IP Profile for P-Asserted Identity Insertion. See Section 5.15. Step 17: Configuring SIP General Parameters. See Section 5.16. Step 18: Defining Reasons for Alternative Routing. See Section 5.17. The procedures described in this section are performed using the E-SBC devices Web-based management tool (i.e., embedded Web server). Before you begin configuring the E-SBC device, ensure that the Web interface's Navigation tree is in full menu display mode (i.e., the Full option on the Navigation bar is selected), as displayed below: XO Communications and Microsoft Lync 37 June 2011

XO Communications and Microsoft Lync Figure 5-1: Web Interface Showing Basic/Full Navigation Tree Display AudioCodes Gateway and Microsoft Lync 38 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device 5.1 Step 1: Configure IP Addresses This step describes how to configure IP addresses when utilizing a LAN interface and a WAN interface to connect to the Microsoft Lync environment and XO Communications SIP Trunk respectively. In this configuration, the internal data-routing capabilities of the E-SBC device are used. 5.1.1.1 Configuring the LAN IP Addresses This section describes how to assign the LAN IP addresses. To assign a LAN VoIP and Management IP address using the Web interface: 1. Open the IP Settings page (Configuration tab > VoIP menu > Network submenu > IP Settings). 2. Select the 'Index' radio button corresponding to the Application Type "OAMP + Media + Control (i.e., VoIP and management interface), and then click Edit. 3. Configure the new IP address and prefix length so that it corresponds to your network IP addressing scheme (e.g., 10.15.9.118). 4. Configure additional IP interfaces, if required. Figure 5-2: Multiple Interface Table Page To define the E-SBC devices LAN data-routing IP address: 1. Access the E-SBC devices Web interface with the IP address that you assigned to the VoIP and Management interface. 2. Access the 'Connections' page (Configuration tab > Data menu > Data System > Connections). XO Communications and Microsoft Lync 39 June 2011

XO Communications and Microsoft Lync Figure 5-3: Connections Page 3. Click the Edit icon corresponding to the "LAN Switch VLAN 1" connection, and then click the Settings tab. 4. In the 'IP Address' and 'Subnet Mask' fields, enter the required IP address (e.g., 10.15.9.117) and subnet respectively, and then click OK. Figure 5-4: Defining LAN Data-Routing IP Address AudioCodes Gateway and Microsoft Lync 40 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device 5.1.1.2 Assigning WAN IP Addresses This section describes how to assign the WAN IP addresses. To assign a WAN IP address: 1. Cable the E-SBC device to the WAN network (i.e., ADSL or Cable modem) using the WAN port. 2. Access the E-SBC device Web interface with the Voice and Management IP address. 3. Access the 'Settings' page (Configuration tab > Data menu > WAN Access > Settings tab). Figure 5-5: Configuring the WAN IP Address 4. From the 'Connection Type' drop-down list, select the required connection type for the WAN, and then configure the IP address (e.g., 100.33.2.105). XO Communications and Microsoft Lync 41 June 2011

XO Communications and Microsoft Lync To assign a WAN interface for VoIP traffic: 1. Select the WAN interface. 2. Open the 'Multiple Interface Table' page (Configuration tab > VoIP menu > Network submenu > IP Settings). Figure 5-6: Selecting WAN Interface for VoIP Traffic in Multiple Interface Table Page 3. From the 'WAN Interface Name' drop-down list, select the WAN interface for VoIP traffic. 4. Click Done, and then reset the E-SBC device for your setting to take effect. AudioCodes Gateway and Microsoft Lync 42 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device 5.2 Step 2: Enable the SIP SBC Application Mode This step describes how to enable the gateway-sbc devices SIP SBC application mode. To enable the SIP SBC application mode: 1. Open the 'Application Enabling' page (Configuration tab > VoIP menu > Applications Enabling > Applications Enabling). Figure 5-7: Application Enabling 2 2. From the Enable SBC Application drop-down list, select Enable. Reset with BURN to FLASH is required. Note: To enable the SBC capabilities on the AudioCodes device, your device must be loaded with the feature key that includes the SBC feature and also the E-SBC device must be running SIP version 6.2 or later. XO Communications and Microsoft Lync 43 June 2011

XO Communications and Microsoft Lync 5.3 Step 3: Configure SIP Interfaces This step describes how to create the SIP Interfaces. The SIP Interface represents one SIP signaling entity, which is a combination of UDP, TCP, and TLS ports relating to one specific IP address (configured in the Multiple Interface table, see Section 5.1 on page 39). Each SIP Interface is associated with an SRD (see Section 5.5 on page 46). This allows User Agents on the network to communicate with a specific SRD, using the SIP Interface (signaling interface) associated with it. When creating the SIP interfaces, ensure that the Network Interface name used for the new index matches the name used in the initial IP Settings i.e., Voice (see Section 5.1 on page 39). This is the interface for the SBC Application. In addition, you need to create a second interface for the WAN network. To configure the SIP Interfaces: 1. Open the 'SIP Interface Table' page (Configuration tab > VoIP menu > Control Network submenu > SIP Interface Table). Figure 5-8: SIP Interfaces AudioCodes Gateway and Microsoft Lync 44 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device 5.4 Step 4: Configure Media Realm This step describes how to configure the Media Realms. A Media Realm is a range of UDP ports that is associated with a media IP interface/ip address. Media Realms allow you to divide a media (RTP traffic) IP interface into several realms, where each realm is specified by a UDP port range and is bound to a SIP Interface. Once created, the Media Realm is assigned to other entities for routing; to an IP Group in the 'IP Group' table (see Section 5.9 on page 52) and to an SRD in the 'SRD' table (see Section 5.5 on page 46). You need to bind the Media Realm to a SIP interface (created in Section 5.3 on page 44). In addition, ensure that the Port Range Start and the Number of Media Session Legs are data filled for the required sessions and the port range for each Realm of the device. A Media Realm is required for each of the respective sides of the SBC to work with the MSBG Router. The LAN Realm for the respective LAN based devices (i.e., Microsoft Lync environment and the Fax supporting Media Gateway). The WAN Realm for the WAN based devices ( i.e., XO Communications SIP Trunk). To configure the Media Realms: 1. Open the Media Realm Configuration page (Configuration tab > VoIP menu > Media submenu > Media Realm Configuration submenu) to configure the Media Realm settings. 2. Configure the required parameters. 3. Click the Submit button to save your changes. 4. Save the changes to flash memory. Figure 5-9: Media Realms XO Communications and Microsoft Lync 45 June 2011

XO Communications and Microsoft Lync 5.5 Step 5: Configure SRD Table This step describes how to configure an SRD table. The SRD Signaling routing domain) is configured with a unique name and assigned a Media Realm (defined in the 'SIP Media Realm' table - see Section 5.4 on page 45). In addition, other attributes such as media anchoring and user registration are also configured. You need to create two SRDs; one to support the LAN based realm and another for the WAN based realm. To configure the SRD table: 1. Open the SRD Table page (Configuration tab > VoIP menu > Control Network sub-menu > SRD Table sub-menu). 2. Select an index that is unused Not Exist. 3. Configure the parameters as required. Figure 5-10: SRD Table AudioCodes Gateway and Microsoft Lync 46 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device 4. Create the SRD name and bind it to a previously created Media Realm. Ensure that you define a unique SRD name, which is associated to a previously created Media Realm. 5. Click the Submit button to save your changes. 6. Save the changes to flash memory. 7. Repeat the process for each additional SRD. The sub-panes in the SRD screen i.e., the IP Group Status Table and the Proxy Sets Status Table are automatically filled after the IP Group, and IP Proxy Set tables are respectively configured. XO Communications and Microsoft Lync 47 June 2011

XO Communications and Microsoft Lync 5.6 Step 6: Configure SBC General Settings This step describes how to configure SBC General Settings. To configure the SBC General Settings: 1. Open the SBC General Parameters page (Configuration tab > VoIP menu > SBC submenu > SBC General Settings) to configure the device's SBC General Settings. 2 3 2. Set the Transcoding Mode to Only if Required. 3. Ensure the Minimum Session-Expires is set to 3600 as required by XO Communications. Note: For SBC enabled application, the selection of WAN Ethernet in the Multiple Interface Table (See Section 5.1 on page 39) will automatically set up the internal router. The WAN IP Address field displayed above is for reference purposes only. In future releases, this field will not be displayed. AudioCodes Gateway and Microsoft Lync 48 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device 5.7 Step 7: Configure the Number of Media Channels This step describes how to configure the Media Channels on the device. To perform coder transcoding, you need to define DSP channels. The number of media channels represents the number of digital signaling processors (DSP) channels that the device allocates to SBC calls (the remaining DSP channels can be used for PSTN calls). An IP media channel may be utilized per SBC call depending on call flow and whether Transcoding is required. The maximum number of media channels available on the Mediant 1000 E-SBC device is 120. The maximum number of media channels available on the Mediant 3000 E-SBC Media Gateway device is 1008. To configure the number of media channels: 1. Open the 'IP Media Settings' page (Configuration tab > VoIP menu > IP Media > IP Media Settings). Figure 5-11: IP Media Channels Settings 2 2. In the 'Number of Media Channels, enter 120 to enable up to 120 calls with transcoding. Click Apply New Value. XO Communications and Microsoft Lync 49 June 2011

XO Communications and Microsoft Lync 5.8 Step 8: Configure the Proxy Sets This step describes how to configure the Proxy Sets. The Proxy Sets represent the IP addresses (or FQDN), which are required for communicating with the entities in the network: Proxy Set ID #3 is assigned with the IP address of XO Communications SIP Trunk. Proxy Set ID #1 is assigned with the IP address of Lync Mediation server. Proxy Set ID #6 is assigned with the IP address of Media Gateway supporting the Fax machine. These Proxy Sets are later assigned to IP Groups (see Section 5.9 on page 52). To configure proxy sets: 1. Open the 'Proxy Sets Table' page (Configuration tab > VoIP menu > Control Network > Proxy Sets Table). 2. Configure the Proxy Set for XO Communications SIP Trunk: a. From the 'Proxy Set ID' drop-down list, select "3". b. In the 'Proxy Address' column, enter the IP address or FQDN of the XO Communications SIP Trunk and the listening port of the XO Communications SIP Trunk. c. From the 'Transport Type' drop-down list, corresponding to the IP address entered above, select "UDP". d. Repeat steps b and c as required for alternate XO Communications IP Border Element (if used). Figure 5-12: Proxy Set ID 3 for XO Communications SIP Trunk 2a 2b 2c AudioCodes Gateway and Microsoft Lync 50 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device 3. Configure the Proxy Set for the Lync Mediation Server: a. From the 'Proxy Set ID' drop-down list, select "1". b. In the 'Proxy Address' column, enter the IP address or the FQDN and the listening port of the Lync Mediation Server. c. From the 'Transport Type' drop-down list corresponding to the IP address entered above, select "TCP" Transport Type. Figure 5-13: Proxy Set ID 1 for Lync Mediation Server 3a 3b 3c 4. Configure the Proxy Set for the Fax supporting Media Gateway: d. From the 'Proxy Set ID' drop-down list, select "6". e. In the 'Proxy Address' column, enter the IP address or the FQDN and the listening port of the Fax Supporting Media Gateway. f. From the 'Transport Type' drop-down list corresponding to the IP address entered above, select "UDP" Transport Type. Figure 5-14: Proxy Set ID 6 for Fax Supporting Media Gateway 4d 4e 4f XO Communications and Microsoft Lync 51 June 2011

XO Communications and Microsoft Lync 5.9 Step 9: Configure the IP Groups This step describes how to create IP groups. Each IP group represents a SIP entity in the device's network. You need to create IP groups for the following entities: 1. IP Group Index #3 is assigned to the XO Communications SIP Trunk. 2. IP Group Index #1 is assigned to the Lync Server 2010 Mediation Server. 3. IP Group Index #5 is assigned to the XO Communications SIP Trunk to support transferred calls. 4. IP Group Index #6 is assigned for FAX Support via Analog Media Gateway. These IP groups are later used by the SBC application for routing calls. To configure IP Groups: 1. Open the 'IP Group Table' page (Configuration tab > VoIP menu > Control Network> IP Group Table). Figure 5-15: IP Group 3 Table 2a 2c 2e 2b 2d 2f 2g 2h 2. Define IP Group #3 for the XO Communications SIP Trunk as follows: a. IP Group Index 3 b. Type: SERVER c. Description: arbitrary name. (e.g., XOSIPtrunk ) d. Proxy Set ID: 3 (represents the IP address, configured in Section 5.8 on page 50, for communicating with this IP Group). e. SIP Group Name: The SIP Request-URI host name used in INVITE messages sent to the IP Group, or the host name in the From header of INVITE messages received from the IP Group. Enter the Group Name or leave blank for default. f. SRD: 2 g. Media Realm: WanRealm h. IP Profile ID: 2 : Different IP profile is used for the XO Communications SIP Trunk and the Mediation Server. See Section 5.11 on page 59. AudioCodes Gateway and Microsoft Lync 52 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device Figure 5-16: IP Group 1 Table Page 3a 3b 3c 3e 3d 3h 3f 3g 3i 3. Define IP Group #1 for Mediation Server as follows: a. Select IP Group Index 1. b. Type: SERVER c. Description: <Free Description> (e.g., Lync Mediation Server ) d. Proxy Set ID: 1 e. SIP Group Name: The SIP Request-URI host name used in INVITE messages sent to the IP Group, or the host name in the From header of INVITE messages received from the IP Group. Enter the Gateway Name or leave blank for default. f. SRD: 1 g. Media Realm: LanRealm h. IP Profile ID: 1 (see Section 5.11 on page 59). i. Inbound Message Manipulation Set: 1 XO Communications and Microsoft Lync 53 June 2011

XO Communications and Microsoft Lync Figure 5-17: IP Group 5 Table Page 4a 4c 4e 4b 4d 4h 4f 4g 4i 4. Define IP Group #5 for Mediation Server as follows: a. Select IP Group Index 5. b. Type: SERVER c. Description: <Free Description> (e.g., XO for Lync Diversion calls ) d. Proxy Set ID: 3 e. SIP Group Name: The SIP Request-URI host name used in INVITE messages sent to the IP Group, or the host name in the From header of INVITE messages received from the IP Group. Enter the Gateway Name or leave blank for default. f. SRD: 2 g. Media Realm: WanRealm h. IP Profile ID: 2 (see Section 5.11 on page 59). i. Outbound Message Manipulation Set: 2 AudioCodes Gateway and Microsoft Lync 54 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device Figure 5-18: IP Group 6 Table Page 5a 5c 5e 5b 3d 5f 5h 5g 5. Define IP Group #6 for supporting FAX Media Gateway as follows: a. Select IP Group Index 6. b. Type: SERVER c. Description: <Free Description> (e.g., Fax Gateway ) d. Proxy Set ID: 6 e. SIP Group Name: The SIP Request-URI host name used in INVITE messages sent to the IP Group, or the host name in the From header of INVITE messages received from the IP Group. Enter the Gateway Name or leave blank for default. f. SRD: 1 g. Media Realm: LanRealm h. IP Profile ID: 2 (see Section 5.11 on page 59). XO Communications and Microsoft Lync 55 June 2011

XO Communications and Microsoft Lync 5.10 Step 10: Configure the Voice Coders This step describes how to configure the Voice Coders tables. Since the Mediation Server supports both the G.711A-law and G.711U-law voice coders, while the XO Communications SIP trunk requires the G.711U-law coder, you can configure a single coder table reference for both services by utilizing the G711U-law coder (see Figure 5-20) or you can create a more dynamic servicing interworking based on commonality of supported vocoders (see Figure 5-19). The Coder table is associated with the following IP Profiles. IP Profile index 2 (see Section 5.11 on page 59) references Coders Table (see Figure 5-19) which is associated with the IP Groups 3, 5, and 6 (see Section 5.9 on page 52). IP Profile index 1 (see Section 5.11 on page 59) references Coder Group 1 (see Figure 5-20), which is associated with IP Group 1(see Section 5.9 on page 52). To configure Coder Table for Fax Gateway and XO Communications SIP Trunk: 1. Open the 'Coders Table' page (Configuration tab > VoIP menu > Coders And Profiles > Coders). Figure 5-19: Coders Table Fax Gateway & XO SIP Trunk 3 4 5 2. From the Coders Table prepare to select via drop-down list, coder and attributes. 3. Select the G.711U-law coder, as shown in the figure above. 4. From Silence Suppression drop-down list, select Enable or Disabled as shown in the figure above. 5. Select the T.38 coder, as shown in the figure above to support fax. AudioCodes Gateway and Microsoft Lync 56 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device To configure Coder Table for Mediation Server usage: 1. Open the 'Coders Table' page (Configuration tab > VoIP menu > Coders And Profiles > Coders Group Settings). Figure 5-20: Coder Group Table 1 - Mediation Server 3 4 2. From the Coder Group Setting table, select via drop-down list, the index 1. This index, 1, is referenced by the datafill of parameter 'Coders Group index' of IP Profile index 1. This allows a user to list the allowed vocoders in a supported grouping to be referenced and utilized. This points to table 'Coder Group' for IP Profile index 1, where Coder Group 1 is explicitly referenced. As shown above, Coder Group 1 is declared to support G.711U-law. 3. Select the G.711U-law coder, as shown in the figure above. 4. From Silence Suppression drop-down list, select Enable or Disabled as shown in the figure above. XO Communications and Microsoft Lync 57 June 2011

XO Communications and Microsoft Lync 5.10.1 Step 11: Define Silence Suppression and Comfort Noise This step describes how to define Silence Suppression and Comfort Noise. Overall voice quality has been significantly improved for the Microsoft Lync 2010 environment. These improvements include suppression of typing noise during calls and improved generation of comfort noise, which reduces hissing and smoothes over the discontinuous flow of audio packets. You may need to modify the Silence Suppression and Comfort Noise parameters to achieve this goal. Note that the Echo canceller is enabled by default. To configure silence suppression parameters: 1. Silence Suppression is configured per coder type. (See Section 5.10 on page 56 above to enable Silence Suppression per coder.) 2. Open the 'RTP/RTCP Settings' page (Configuration tab > Media menu > RTP / RTCP Settings). Figure 5-21: RTP/RTCP Settings Page 3 4 3. From the Comfort Noise Generation Negotiation drop-down list, select 'Enable. This action enables negotiation and usage of Comfort Noise (CN). 4. The RTP Base UDP Port can be changed if the RTP is managed by an external device that requires RTP to be within a specific range for QoS purposes (6000 is the default setting). 5. Click Submit. AudioCodes Gateway and Microsoft Lync 58 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device 5.11 Step 12: Configure IP Profile Settings This step describes how to configure the IP Profile Settings. You define two IP Profiles, one for the Mediation Server and one for the XO Communications SIP Trunk and FAX Gateway. To configure IP Profile for XO Communications SIP Trunk: 1. Open the 'IP Profile Settings' page (Configuration tab > VoIP menu > Coders and Profiles > IP Profile Settings). Figure 5-22: IP Profile Page- Mediation Server 2 3 4 XO Communications and Microsoft Lync 59 June 2011

XO Communications and Microsoft Lync 2. From the Profile ID drop-down list, select 1. 3. From the Coder Group drop-down list, select Coder Group 1. 4. From Transcoding Mode drop-down list, select Force. This is to assist with Music on Hold functionality to ensure that the Microsoft Lync 2010 server receives RTCP events in the event that a call is placed on hold. AudioCodes Gateway and Microsoft Lync 60 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device To configure IP Profile for XO Communications SIP Trunk and FAX Gateway: 1. Open the 'IP Profile Settings' page (Configuration tab > VoIP menu > Coders and Profiles > IP Profile Settings). Figure 5-23: IP Profile Page- XO Communications SIP Trunk & Fax Gateway 2 3 4 2. From the Profile ID drop-down list, select 2. 3. From the Coder Group drop-down list, select Default Coder Group. XO Communications and Microsoft Lync 61 June 2011

XO Communications and Microsoft Lync 4. From Transcoding Mode drop-down list, select Only if Required. This is performed to allow the interworking with the Lync side as well as the interworking with the analog Media gateway to support faxing. AudioCodes Gateway and Microsoft Lync 62 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device 5.12 Step 13: Configure SBC IP-to-IP Routing Rules This step describes how to configure the E-SBC device for routing SBC IP-to-IP calls. The SBC identifies the IP Group (i.e., Source IP Group ID) to which the received call belongs. It does this by checking whether the IP address from where the call is received is associated with a specific IP Group. (IP addresses are defined in Proxy Sets, which are associated with IP Groups.) Once the call is identified to an IP Group, you can route the call to the desired destination i.e. another IP Group. The figure shown below illustrates 7 different call scenarios, corresponding to Index #1, Index #2, Index #3, Index #4, Index #5, Index #6 and Index#8 respectively (described below). To configure SBC IP routing: 1. Open the 'Inbound IP Routing Table' page (Configuration tab > VoIP menu > SBC > Routing SBC submenu > IP to IP Routing Table). Figure 5-24: IP2IP Routing Table Page 2 4 6 8 3 5 7 XO Communications and Microsoft Lync 63 June 2011

XO Communications and Microsoft Lync 2. Index #1 configuration identifies all IP calls received from the XO SIP Trunk and the destination is for number 2146355861 (a known number that is one of the assigned XO DID for FAX purposes), and routes them to IP Group 6, which is the Media Gateway supporting FAX services. In addition, this index states that the terminating SRD is the LAN SRD. 3. Index #2 configuration identifies all IP calls received from the XO SIP Trunk and routes them to IP Group 1( the Mediation Server). 4. Index #3 configuration identifies all SIP messages received from XO Communications SIP Trunk that are not associated with a call and routes them internally. This is to support the termination of the Options messages for Keep- Alive messaging: 5. Index #4 configuration identifies all IP calls received from the Mediation Server from 2146355861 and routes them to the IP Group 3 (XO Communications SIP Trunk), via the SRD 2 (WAN). It is important to set the screening for the valid numbers defined in the Mediation Server as assigned XO DID. This allows the identification between direct calls and calls which the Mediation Server is attempting to forward. Note that a range of valid XO DIDs can also be screened in the same manner, such as 214635. 6. Index #5 configuration identifies all IP calls received from the Mediation Server and routes them to IP Group 5 (also the XO Communications SIP Trunk). The difference between IP Group 3 and IP Group 5 is that IP Group 5 uses a manipulation rule for outgoing messages to add a Diversion Header. This is important for supporting PSTN to PSTN based forward calls. 7. Index #6 configuration identifies all SIP messages received from the Mediation Server that are not associated with a call and routes them internally. This is to support the termination of the Options messages for Keep-Alive messaging. 8. Index #8 configuration identifies all IP calls received from the Media Gateway assigned to support FAX services and routes to IP Group 3 (XO Communications SIP Trunk, via SRD 2 (WAN). AudioCodes Gateway and Microsoft Lync 64 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device 5.13 Step 14: Configure Manipulation Rules This section describes how to configure the SIP SBC manipulation rules. The Manipulation Tables submenu allows you to configure number manipulation and mapping of NPI/TON to SIP messages. This sub-menu includes the following options: IP to IP Inbound. See Section 5.13.1 on page 66. IP to IP Outbound. See Section 5.13.1 on page 66. Header Manipulations. See Section 5.13.3 on page 69. XO Communications and Microsoft Lync 65 June 2011

XO Communications and Microsoft Lync 5.13.1 Configure IP to IP Inbound Manipulation Rules This step describes how to configure the SBC IP to IP Inbound manipulation rules. To configure IP to IP Inbound Manipulation: 1. Open the IP to IP Inbound page (Configuration tab > VoIP menu > SBC > Manipulations SBC sub-menu > IP to IP Inbound). Figure 5-25: IP to IP Inbound Manipulation Page 2. Index #1 defines source number manipulation of IP calls from the Lync 2010 Mediation server. For all calls received from IP Group 1 (i.e., from Mediation Server) and the source number prefix begins with '+1214291', remove the +1 from the number. This is done to assist XO with screening the source number in the 10 digit format as one of assigned XO DIDs. AudioCodes Gateway and Microsoft Lync 66 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device 5.13.2 Configure IP to IP Outbound Manipulation Rules This step describes how to configure the IP to IP Outbound Manipulation rules. To configure IP to IP Outbound Manipulation Table: 1. Open the IP to IP Outbound Manipulation page (Configuration tab > VoIP menu > SBC > Manipulations SBC sub-menu > IP to IP Outbound). Figure 5-26: IP to IP Outbound Manipulation Page 2 4 6 8 3 5 7 2. Index #1 defines destination number manipulation of IP calls from Mediation Server to XO Communications SIP Trunk. For all calls received from Source IP Group 1 (i.e., from Microsoft Lync) where the destination number prefix begins with +, remove the first symbol from the destination number. XO Communications and Microsoft Lync 67 June 2011

XO Communications and Microsoft Lync 3. Index #2 defines destination number manipulation of IP calls from Source IP Group 3 (XO Communications SIP Trunk) to Microsoft Lync (IP Group 1), where the destination number prefix begins with '2146355861', remove 10 digits and add the +12142911000 as the new number. This is an example of digit manipulation. XO will deliver a 10 digit number and the Microsoft Lync environment requests to see a +1 added to the incoming 10 digit number. Instead of removing the 10 digits, simply add the desired prefix. 4. Index #3 defines the destination number manipulation of IP calls from the Microsoft Lync environment (Source IP Group 1) towards Destination IP Group 3 (i.e., from XO Communications SIP Trunk) where the source number prefix begins with '2146355861' as a private number when setting to Restrict. 5. Index #4 defines source number manipulation of IP calls from the Microsoft Lync environment, which are calls originally forwarded from the PSTN and terminating to PSTN (XO Communications SIP Trunk). For all calls received from Source IP Group 1 (i.e., from Mediation Server, as a redirect to PSTN for transfer off-net calls) and the source number is prefixed with a +, remove the + prefix from the number. 6. Index #5 defines a rule in conjunction with the previous rule (an additional manipulation set to 1 ). This defines if Index # 4 is TRUE and the destination number is then checked for manipulation of IP calls from the Microsoft Lync environment (calls originally forwarded from the PSTN and terminating to PSTN (XO Communications SIP Trunk)). For all calls received from Source IP Group 1 (i.e., from Mediation Server, as a redirect to PSTN for transfer off-net calls) where the source number is prefixed with a +, remove the + prefix from the number. As for the Is Additional Manipulation field setting of 1 mentioned at the beginning of this rule, this is used to bind the instruction as a single item with the item directly above it (i.e. Index 4). The is designed to perform checks to see if the immediately preceding condition was met, if so, then this rule is executed, if not, then the rule is automatically skipped and the E-SBC proceeds to the next rule below. 7. Index #6 defines destination number manipulation of IP calls from XO Communications SIP Trunk to the FAX supporting Media Gateway. For all calls received from Source IP Group 3 (i.e., from XO Communications SIP Trunk) and the destination number is 2146355861, a known number assigned XO DID for FAX service, remove the 10 digit number and add 2142911100 as the new destination number. This entry reflects a general capabilities reference to show manipulation for the FAX supporting Media Gateway. 8. Index #7 defines destination number manipulation of IP calls from the FAX supporting Media Gateway (Source IP Group 6) to XO Communications SIP Trunk. For all calls received from Source IP Group 1 (i.e., from Lync 2010 Mediation Server) where the destination number is prefixed with a +, remove the + prefix from the left. AudioCodes Gateway and Microsoft Lync 68 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device 5.13.3 Configure Header Manipulation Rules This step describes how to configure Header Manipulation rules. To configure the SBC Message Manipulations: 1. Open the Messages page (Configuration tab > VoIP menu > SBC > Manipulations SBC submenu > Messages). Figure 5-27: Message Manipulations Page 2 4 6 3 5 7 2. Index #1 defines a rule for Manipulation Set ID 1 for Invite Header manipulation to add p-asserted-identity to all messages related to INVITE handling. Action Value: '<sip:' + header.from.url.user + '@100.33.2.105>' 3. Index #2 defines a rule for Manipulation Set ID 2 for Invite Header manipulation to add p-asserted-identity Header to all messages related to INVITE handling. Action Value: '<sip:' + header.from.url.user + '@100.33.2.105>' 4. Index #3 defines a rule for Manipulation Set ID 2 for INVITE Header manipulation to add Diversion Header to all messages related to INVITE handling. This manipulation is performed to create a well known assigned XO DID number in the Diversion header for forwarding calls. Action Value: '<sip:2146355861' + @100.33.2.105>;reason=unconditional;counter=1;screen=no;privacy=off' 5. Index #4 defines a rule for Manipulation Set ID 1 for INVITE Header manipulation to remove p-asserted-identity Header to all 181 messages related to INVITE handling. XO Communications and Microsoft Lync 69 June 2011

XO Communications and Microsoft Lync 6. Index #5 defines a rule for Manipulation Set ID 1 for INVITE Header manipulation to add Session-Expires Header with the value of 180 to all messages related to INVITE request handling. 7. Index #6 defines a rule for Manipulation Set ID 1 for INVITE Header manipulation to add Session-Expires refresh with the value of 2, UAS, to all messages related to INVITE request handling. This advises the XO SIP Trunk to initiate the Re-Invite for Session Expiry. Note: 1. The common Manipulation Set IDs are linked together as a logical grouping of actions that will be applied. All items with Manipulation Set ID = 1 behave as a single entity. All items with Manipulation Set ID = 2 behave as a single entity. 2. These Manipulation Set IDs are associated in the respective IP Group tables datafill under SBC Parameters pane Inbound Message Manipulation Set and Outbound Message Manipulation Set. See Section 5.9 on page 52. AudioCodes Gateway and Microsoft Lync 70 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device 5.14 Step 15: Configure IP Group for Call Forwarding This step describes how to configure the IP Group for Call Forwarding. One of the challenges with the integration of the Microsoft Lync 2010 server and the XO Communications SIP Trunk is the implementation of call forwarding. Since the Microsoft Lync client forwards the call back to the SIP Trunk, it does not provide any information in the forwarded INVITE (such as Diversion header) informing that this call has been forwarded. Consequently, it is necessary to configure the IP Group to add the diversion header toward the SIP trunk in the event of a call forwarding scenario. To configure IP Group for call forwarding: 1. Open the 'IP Group page (Configuration tab > VoIP menu > Control Network submenu > IP Group Table). Figure 5-28: IP Profile Settings for Call Forwarding numbers 2 3 2. From the IP Group ID drop-down list, select 5. This group was created in the IP Groups configuration (see Section 5.9 on page 52). It was assigned to the XO Communications SIP Trunk to support transferred calls. 3. From the Outbound Message Manipulation Set window, select 2 (derived from the previously created SBC Message Manipulations rules) ; this parameter points to the Message Manipulation Set ID rules which add the Diversion Header to the INVITE in the event of a call forwarding scenario. See Section 5.13.3 on page 69. XO Communications and Microsoft Lync 71 June 2011

XO Communications and Microsoft Lync 5.15 Step 16: Configure IP Group for P-Asserted Identity Header Insertion This step describes how to configure an IP Group for P-Asserted Identity Header Insertion. Due to the integration of the Microsoft Lync 2010 server and the XO Communications SIP Trunk, the P-Asserted Identity Header is required; however, not provided by the Microsoft Lync environment. Consequently, header manipulation is required, where the IP Group is configured to add the P-Asserted Identity header toward the SIP trunk. Associations are made with this IP Group in the routing and manipulation tables. To configure IP Group for insertion of P-Asserted Identity Header: 1. Open the 'IP Profile Settings' page (Configuration tab > VoIP menu > Control Network submenu > IP Group Table). Figure 5-29: IP Profile Settings for Inserting P-Asserted Identity Header to all Lync calls 2 3 2. From the IP Group ID drop-down list, select 1. This group was created in the IP Groups configuration (see Section 5.9 on page 52). 3. From the Inbound Message Manipulation Set window, select 1 (derived from the previously created SBC Message Manipulations rules) ; this parameter points to the Message Manipulation Set ID rules which adds the P-Asserted Identity Header to the INVITE and it also adds the Session Expires and the Refresh to the Invite Response messages coming from the Lync environment. Also, in the event of a 181 message, the P-Asserted Identity Header is removed. See Section 5.13.3 on page 69. AudioCodes Gateway and Microsoft Lync 72 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device 5.16 Step 17: Configuring SIP General Parameters This step describes how to configure the SIP general parameters. To configure general SIP parameters: 1. Open the 'SIP General Parameters' page (Configuration tab > VoIP menu > SIP Definitions submenu > General Parameters). Figure 5-30: SIP General Parameters Page 2 3 4 5 6 XO Communications and Microsoft Lync 73 June 2011

XO Communications and Microsoft Lync 7 8 9 2. In the NAT IP Address field, ensure this field is empty (0.0.0.0). It is not used for the Single LAN Interface solution. For applications that use both the WAN and LAN Interface, and the SBC functionality is used, the SBC General Settings will take care of the functionality. This is utilized with a Global (public) IP address of the E-SBC device to enable the static NAT between the E-SBC device and the Internet for gateway and other functionality. 3. From the Enable Early Media drop-down list, select Enable to enable early media. 4. If Gateway functionality or Application IP to IP is utilized, from the Asserted Identity Mode drop-down list, select Adding PAsserted Identity. This will have no affect on a pure SBC call. This is utilized with the E-SBC IP2IP functionality as well as gateway functionality. It is important to note if attempting to utilize methods other than the SBC functionality. For SBC functionality, the header is added in the IP Profile reference of Inbound/Outbound Message Manipulation Set 5. From the SIP Transport Type drop-down list, select TCP in case the Mediation Server is configured to use TCP transport Type. 6. In the SIP TCP Local Port field, enter 5060 ; this port is the listening E-SBC device port for TCP transport type. This port must match the transmitting port of the Mediation Server. 7. From Play Ringback Tone to Tel drop-down list, select Play Local Until Remote Media Arrive. Plays the RBT according to the received media. If a SIP 180 response is received and the voice channel is already open (due to a previous 183 early media response or due to an SDP in the current 180 response), the E- SBC device plays a local RBT if there are no prior received RTP packets. The E- SBC device stops playing the local RBT as soon as it starts receiving RTP packets. At this stage, if the E-SBC device receives additional 18x responses, it does not resume playing the local RBT. AudioCodes Gateway and Microsoft Lync 74 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device 8. From the Forking Handling Mode drop-down list, select Sequential handling ; this parameter determines whether18x with SDP is received. In this case, the E- SBC device opens a voice stream according to the received SDP. The E-SBC device re-opens the stream according to subsequently received 18x responses with SDP. 9. In the Fake Retry After field, enter 60 sec. This parameter determines whether the E-SBC device, upon receipt of a SIP 503 response without a Retry-After header, behaves as if the 503 response included a Retry-After header and with the period (in seconds) specified by this parameter. XO Communications and Microsoft Lync 75 June 2011

XO Communications and Microsoft Lync 5.17 Step 18: Defining Reasons for Alternative Routing This step describes how to configure the reasons for SIP Alternative Routing. A 503 SIP response from the Mediation Server to an INVITE must cause the E-SBC device to perform a failover. In other words, if the Lync Mediation Server primary proxy server is not responding, an attempt is made to establish communication with the secondary proxy server. For this event to occur, you need to perform the following actions: Configure the Reasons for Alternative Routing for Tel-to-IP calls to 503 SIP response. Configure the Lync Mediation Proxy Set for redundancy purposes. To define SIP Reason for Alternative Routing: 1. Open the 'Reasons for Alternative Routing' page (Configuration tab > VoIP menu > SBC > Routing SBC submenu > Alternative Routing Reasons). Figure 5-31: Reasons for Alternative Routing Page 2 2. Under the Tel to IP Reasons group, for Reason 1, select 503. 3. Click Submit. 4. Open the Proxy & Registration page (Configuration > VoIP > SIP Definitions > Proxy & Registration) and configure the Redundant Routing Mode parameter to Proxy as shown below in Figure 5-32. This will allow entry back into the Proxy Set table for the next available route. This redundant route is configured in the next step (on Proxy Set ID 1, see Figure 5-33 below). AudioCodes Gateway and Microsoft Lync 76 Document #: LTRT-40800

Configuration Note 5. Configuring E-SBC Device 5. Open the 'Proxy Sets Table' page (Configuration tab > VoIP menu > Control Network > Proxy Sets Table). Configure the Proxy Set for the Lync Mediation Server: From the 'Proxy Set ID' drop-down list, select "1". a. In the 'Proxy Address' column, enter a second IP address or the FQDN and the listening port of the secondary Lync Mediation Server. b. From the 'Is Proxy Hot Swap drop-down list, select "Yes". 6. Click Submit. Figure 5-32: Proxy & Registration Page 4 XO Communications and Microsoft Lync 77 June 2011

XO Communications and Microsoft Lync Figure 5-33: Proxy Set ID 2 for Lync Mediation Server 5a 5b AudioCodes Gateway and Microsoft Lync 78 Document #: LTRT-40800

Configuration Note 6. Troubleshooting 6 Troubleshooting This section should provide some tips for troubleshooting problems, including troubleshooting commands and contact numbers within Vendor X s Company for trouble escalation. 6.1 Debugging Procedures This section discusses the following debugging procedures: Case Reporting Procedures. See Section 6.1.1 below. Syslog. See Section 6.1.2 on page 80. Wireshark Network Sniffer. See Section 6.1.3 on page 82. 6.1.1 Case Reporting Procedures When reporting a problem to AudioCodes Technical Support department, the following information should be provided: Basic information (required for all types of problems): Problem description (nature of failure, symptoms, call direction, etc.) Network diagram ini configuration file (downloaded to your PC from the device using the Web interface) Syslog trace (without missing messages) Unfiltered IP network trace using the Wireshark application (Note: If you are unable to collect all the network traffic, then at least collect the mandatory protocols SIP, RTP, and T38.) Advanced information (if required upon request): PSTN message traces - for PSTN problems Media stream traces - for problems related to voice quality, modem\fax, DTMF detection, etc. XO Communications and Microsoft Lync 79 June 2011

XO Communications and Microsoft Lync 6.1.2 Syslog Syslog is a standard for forwarding log messages in an IP network. A syslog client, embedded in the device sends error reports/events generated by the device to a remote Syslog server using IP/UDP protocol. This information is a collection of error, warning and system messages that record every internal operation of the device. You can use the supplied AudioCodes proprietary Syslog server "ACSyslog" (shown in the figure below) or any other third-party Syslog server for receiving Syslog messages. Figure 6-1: AudioCodes' Proprietary Syslog Server To activate the Syslog client on the device using the Web interface: 1. Open the 'Syslog Settings' page (Configuration tab > System menu > Syslog Settings). 2. In the 'Syslog Server IP Address' field, enter the IP address of the Syslog server (ini file parameter SyslogServerIP). 3. From the 'Enable Syslog' drop-down list, select 'Enable' to enable the device to send syslog messages to a Syslog server (defined in Step 2). Figure 6-2: Enabling Syslog AudioCodes Gateway and Microsoft Lync 80 Document #: LTRT-40800

Configuration Note 6. Troubleshooting 4. From the 'Debug Level' drop-down list, select '5' if debug traces are required. To enable syslog reporting, using the ini file, load an ini file to the device with the following settings: XO Communications and Microsoft Lync 81 June 2011

XO Communications and Microsoft Lync 6.1.3 Wireshark Network Sniffer Wireshark is a freeware packet sniffer application that allows you to view the traffic that is being passed over the network. Wireshark can be used to analyze any network packets. Wireshark can also be used to analyze RTP data streams and extract the audio from the data packets (only for G.711). The audio can be saved as a *.pcm file. To record traffic that is sent to / from the device: 1. Install Wireshark on your PC. (You can download it from the following Web site: http://www.wireshark.org/ 2. Connect the PC and the device to the same hub. 3. If you are using a switch, use a switch with port mirroring for the port to which the Wireshark is connected. 4. Start Wireshark. 5. Select the network interface that is currently being used by the PC - on the toolbar,click Interfaces, and then in the 'Capture Interfaces' dialog box, click the Options button corresponding to the network interface: Figure 6-3: Selecting Interface Currently used by the PC AudioCodes Gateway and Microsoft Lync 82 Document #: LTRT-40800

Configuration Note 6. Troubleshooting 6. In the 'Capture Options' dialog box, select the desired display options: Figure 6-4: Configuring Wireshark Display Options XO Communications and Microsoft Lync 83 June 2011

XO Communications and Microsoft Lync 7. Click Start. Figure 6-5: Captures Packets 8. To view VoIP call flows, from the Statistics menu, choose VoIP Calls. You can view the statistics in graph format by clicking Graph. Figure 6-6: Viewing VoIP Call Flows 9. To play G.711 RTP streams, click the Player button. AudioCodes Gateway and Microsoft Lync 84 Document #: LTRT-40800

Configuration Note 6. Troubleshooting Figure 6-7: Playing G.711 RTP Streams 10. To analyze the RTP data stream and extract the audio (which can be played using programs such as CoolEdit) from the data packets (only for G.711), from the Statistics menu, point to RTP, and then choose Stream Analysis. Figure 6-8: Analyzing the RTP Data a. Save the audio payload of the RTP stream to a file. b. Save the Payload as a *.pcm file. c. Select the forward option. XO Communications and Microsoft Lync 85 June 2011

XO Communications and Microsoft Lync 6.2 Verifying Firmware To verify the firmware load actively running on the device, log into the device and view the firmware version on the product homepage as shown in the figure below. Figure 6-9: Viewing active firmware version AudioCodes Gateway and Microsoft Lync 86 Document #: LTRT-40800