Configuration Note. Connecting Microsoft Lync Server 2013 with ITSP SIP Trunk using AudioCodes E-SBC. Interoperability Laboratory

Transcription

1 AudioCodes Mediant Series Enterprise Session Border Controller (E-SBC) Interoperability Laboratory Configuration Note Connecting Microsoft Lync Server 2013 with ITSP SIP Trunk using AudioCodes E-SBC June 2013 Document #: LTRT-54004

2

3 Configuration Note Contents Table of Contents 1 Introduction Intended Audience About AudioCodes E-SBC Product Series Component Information AudioCodes E-SBC Version Microsoft Lync Server 2013 Version Deploying the E-SBC Example Environment Environment Setup Configuring Microsoft Lync Server Configuring the E-SBC as an IP / PSTN Gateway Configuring 'Route' on Lync Server Configuring AudioCodes E-SBC Step 1: Configuring the E-SBC's Network Interfaces Configuring IP Network Interfaces for LAN and WAN Configuring the Native VLAN ID Step 2: Enabling the SBC Application Step 3: Configuring SRDs Configuring Media Realms Configuring SRDs Configuring SIP Signaling Interfaces Step 4: Configuring Proxy Sets Step 5: Configuring IP Groups Step 6: Configuring IP Profiles Step 7: Configuring Coders Step 8: Configuring a SIP TLS Connection Configuring the NTP Server Address Configuring a Certificate Step 9: Configuring SRTP Step 10: Configuring IP Media Step 11: Configuring IP-to-IP Call Routing Rules Step 12: Configuring IP-to-IP Outbound Manipulation Step 13: Configuring SIP Message Manipulation Rules Step 14: Configuring a Registration Account Step 15: Configuring Miscellaneous E-SBC Functionalities Step 16: Resetting the E-SBC A Configuring E-SBC to Send 414 Request-URI Too Long Response Connecting Microsoft Lync 2013 to a SIP Trunk 3 June 2013

4 Connecting Microsoft Lync 2013 to a SIP Trunk List of Figures Figure 2-1: E-SBC Interworking Lync 2013 and a SIP Trunk in an Example Environment...12 Figure 3-1: Starting the Lync Server Topology Builder...15 Figure 3-2: Topology Builder Options...16 Figure 3-3: Save Topology...16 Figure 3-4: Topology Builder Displaying Downloaded Topology...17 Figure 3-5: Selecting New IP/PSTN Gateway...17 Figure 3-6: Define New IP/PSTN Gateway...18 Figure 3-7: Define the IP Address...19 Figure 3-8: Define the Root Trunk...20 Figure 3-9: E-SBC Added as an IP/PSTN Gateway and Trunk Created...21 Figure 3-10: Selecting 'Publish Topology' from the 'Action' Menu...21 Figure 3-11: Publish Topology...22 Figure 3-12: Publish Topology Progress Screen...23 Figure 3-13: Publish Topology Successfully Completed...24 Figure 3-14: Opening the Lync Server Control Panel...25 Figure 3-15: Lync Server Credentials...26 Figure 3-16: Microsoft Lync Server 2013 Control Panel...26 Figure 3-17: Voice Routing...27 Figure 3-18: Route Option...28 Figure 3-19: Adding New Voice Route...28 Figure 3-20: Adding New Trunk...29 Figure 3-21: List of Deployed Trunks...30 Figure 3-22: Selected E-SBC Trunk...31 Figure 3-23: Associating PSTN Usage with the Route...32 Figure 3-24: Confirmation of New Voice Route...32 Figure 3-25: Committing Voice Routes...32 Figure 3-26: Uncommitted Voice Configuration Settings...33 Figure 3-27: Confirmation of a Successful Voice Routing Configuration...33 Figure 3-28: Voice Routing Screen Displaying Committed Routes...34 Figure 4-1: Network Interfaces...36 Figure 4-2: Multiple Interface Table...37 Figure 4-3: Ports Native VLAN...38 Figure 4-4: Applications Enabling...39 Figure 4-5: Configuring a LAN Media Realm...40 Figure 4-6: Configuring a WAN Media Realm...41 Figure 4-7: Required Media Realm Table...41 Figure 4-8: Configuring the LAN SRD...42 Figure 4-9: Configuring the WAN SRD...42 Figure 4-10: Required SIP Interface Table...43 Figure 4-11: Proxy Set for Microsoft Lync Server Figure 4-12: Configuring a Proxy Set for the SIP Trunk...46 Figure 4-13: Configured IP Group Table...48 Figure 4-14: Configured IP Profile for Lync Server Figure 4-15: Configured IP Profile for SIP Trunk...52 Figure 4-16: Configured Coder Group for Lync Server Figure 4-17: Configured Coder Group for the SIP Trunk...53 Figure 4-18: Allowed Coders Group for SIP Trunk...54 Figure 4-19: Configuring the NTP Server IP Address...55 Figure 4-20: Certificates Page - Creating CSR...56 Figure 4-21: Microsoft Certificate Services Web Page...57 Figure 4-22: Request a Certificate Page...57 Figure 4-23: Advanced Certificate Request Page...58 Figure 4-24: Submit a Certificate Request or Renewal Request Page...58 Figure 4-25: Certificate Issued Page...59 Figure 4-26: Download a CA Certificate, Certificate Chain, or CRL...59 Figure 4-27: Certificates Page (Uploading Certificate)...60 Figure 4-28: Media Security Page...61 AudioCodes Mediant E-SBC 4 Document #: LTRT-54004

5 Configuration Note Contents Figure 4-29: IP Media Settings...62 Figure 4-30: Configured IP-to-IP Routing Rule to Terminate SIP OPTIONS Messages Received from the LAN...64 Figure 4-31: IP-to-IP Routing Rule for LAN to WAN...65 Figure 4-32: Configured IP-to-IP Routing Rule to Route Calls from WAN to LAN...66 Figure 4-33: IP-to-IP Routing Table...66 Figure 4-34: IP-to-IP Outbound Manipulation Rule Rule Tab...67 Figure 4-35: Configured IP-to-IP Outbound Manipulation Rule - Action Tab...68 Figure 4-36: IP-to-IP Outbound Manipulation...68 Figure 4-37: Message Manipulations Page...69 Figure 4-38: Configured SIP Message Manipulation Rule...70 Figure 4-39: Assigning a Manipulation Rule to IP Group Figure 4-40: Configuring a SIP Registration Account...71 Figure 4-41: Configuring Forking Mode...72 Figure 4-42: Resetting the E-SBC...73 Figure A-1: Configuring a Condition for the Route...75 Figure A-2: IP-to-IP Routing Rule for Long-URI Calls...76 Figure A-3: Manipulation Rule to Set a Variable to '1' in Case of Long-URI Call...77 Figure A-4: Manipulation Rule to Convert 408 to '414'...77 Figure A-5: Message Manipulations Page...78 Figure A-6: Assigning Manipulation Rule to IP Group Connecting Microsoft Lync 2013 to a SIP Trunk 5 June 2013

6 Connecting Microsoft Lync 2013 to a SIP Trunk Reader's Notes AudioCodes Mediant E-SBC 6 Document #: LTRT-54004

7 Configuration Note Notices Notice This Configuration Note shows how to connect Microsoft Lync Server 2013 and a SIP Trunk using AudioCodes Mediant E-SBC product series. 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 accuracy of printed material after the Date Published, nor can it accept responsibility for errors or omissions. Updates to this document and other documents as well as software files can be viewed by registered customers at Copyright 2013 AudioCodes Ltd. All rights reserved. This document is subject to change without notice. Date Published: June 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. Product specifications are subject to change without notice. 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. Connecting Microsoft Lync 2013 to a SIP Trunk 7 June 2013

8 Connecting Microsoft Lync 2013 to a SIP Trunk Reader's Notes AudioCodes Mediant E-SBC 8 Document #: LTRT-54004

9 Configuration Note 1. Introduction 1 Introduction This Configuration Note shows how to configure AudioCodes' Enterprise Session Border Controller (E-SBC) for interworking between an ITSP (Internet Telephony Service Provider's) SIP (Session Initiation Protocol) Trunking service and Microsoft's Lync communication platform (Lync Server 2013). The Note shows how to connect Microsoft Lync Server 2013 and a SIP Trunk using AudioCodes Mediant E-SBC product series, which includes the Mediant 1000B Gateway & E-SBC, Mediant 800 Gateway & E-SBC, Mediant 2600 E-SBC, Mediant 4000 E-SBC and Mediant 3000 Gateway & E-SBC. 1.1 Intended Audience The Configuration Note is intended for engineers or AudioCodes and Partners who are responsible for installing and configuring SIP Trunking and Microsoft's Lync communication platform for enabling VoIP calls using AudioCodes' E-SBC. 1.2 About AudioCodes E-SBC Product Series AudioCodes' family of E-SBC devices enables reliable connectivity and security between an enterprise's VoIP network and the ITSP's VoIP network. The E-SBC provides perimeter defense as a way of protecting enterprises from malicious VoIP attacks; mediation for allowing the connection of any PBX and/or IP-PBX to any Service Provider; and Service Assurance for service quality and manageability. Designed as a cost-effective appliance, the E-SBC is based on field-proven VoIP and network services with a native host processor, allowing the creation of purpose-built multiservice appliances, providing smooth connectivity to cloud services, with integrated quality of service, SLA monitoring, security and manageability. The native implementation of SBC provides a host of additional capabilities that are not possible with standalone SBC appliances such as VoIP mediation, PSTN access survivability, and third-party value-added services applications. This enables enterprises to utilize the advantages of converged networks and eliminate the need for standalone appliances. AudioCodes' E-SBC is available as an integrated solution running on top of its field-proven Mediant Media Gateway and Multi-Service Business Router platforms, or as a softwareonly solution for deployment with third-party hardware. Connecting Microsoft Lync 2013 to a SIP Trunk 9 June 2013

10 Connecting Microsoft Lync 2013 to a SIP Trunk Reader's Notes AudioCodes Mediant E-SBC 10 Document #: LTRT-54004

11 Configuration Note 2. Component Information 2 Component Information 2.1 AudioCodes E-SBC Version SBC Vendor AudioCodes Models Mediant 800 Gateway & E-SBC Mediant 1000B Gateway & E-SBC Mediant 2600 E-SBC Mediant 3000 Gateway & E-SBC Mediant 4000 E-SBC Software Version SIP_6.60A or later Protocol SIP/UDP (to the ITSP's SIP Trunk) SIP/TCP or TLS (to the Lync Front End Server) Additional Notes None 2.2 Microsoft Lync Server 2013 Version Vendor Microsoft Model Microsoft Lync Software Version Release Protocol SIP Additional Notes None Connecting Microsoft Lync 2013 to a SIP Trunk 11 June 2013

12 Connecting Microsoft Lync 2013 to a SIP Trunk 2.3 Deploying the E-SBC Example Environment The example scenario below is referred to throughout this document in order to show how to deploy the E-SBC. In the example environment: Microsoft Lync Server 2013 is deployed in an enterprise's private network for enhanced communication within the enterprise. The enterprise wants to offer its employees enterprise-voice capabilities and to connect the enterprise to the PSTN network using a SIP Trunking service provided by the enterprise's ITSP. AudioCodes' E-SBC is implemented to interconnect between the enterprise's LAN and the SIP Trunk. Session: Real-time voice session using IP-based SIP Border: IP-to-IP network border between Lync Server 2013 network in the enterprise LAN and the SIP Trunk located in the public network. The figure below illustrates AudioCodes' E-SBC interworking between Microsoft Lync Server 2013 and an ITSP's SIP Trunking site. Figure 2-1: E-SBC Interworking Lync 2013 and a SIP Trunk in an Example Environment AudioCodes Mediant E-SBC 12 Document #: LTRT-54004

13 Configuration Note 2. Component Information Environment Setup The example scenario includes the following environment setup: Area Setup Network Microsoft Lync Server 2013 environment is located in the enterprise's LAN The SIP Trunk is located in the WAN Signaling Transcoding Microsoft Lync Server 2013 functions with SIP-over-TLS transport type The SIP Trunk operates with SIP-over-UDP transport type Codecs Transcoding Microsoft Lync Server 2013 supports G.711A-law and G.711Ulaw coders The SIP Trunk supports G.711A-law, G.711U-law and G.729 coders Media Transcoding Microsoft Lync Server 2013 operates with SRTP media type The SIP trunk operates with RTP media type Connecting Microsoft Lync 2013 to a SIP Trunk 13 June 2013

14 Connecting Microsoft Lync 2013 to a SIP Trunk Reader's Notes AudioCodes Mediant E-SBC 14 Document #: LTRT-54004

15 Configuration Note 3. Configuring Microsoft Lync Server Configuring Microsoft Lync Server 2013 This section shows how to configure Microsoft Lync Server 2013 to operate with AudioCodes' E-SBC. Note: Dial plans, voice policies, and PSTN usages are also necessary for enterprise voice deployment but are beyond the scope of this document. 3.1 Configuring the E-SBC as an IP / PSTN Gateway This section shows how to configure the E-SBC as an IP / PSTN Gateway. To configure the E-SBC as an IP/PSTN Gateway and associate it with a Mediation Server: 1. On the server where the Topology Builder is installed, start the Lync Server 2013 Topology Builder: Click the Windows Start menu > All Programs > Lync Server Topology Builder. Figure 3-1: Starting the Lync Server Topology Builder Connecting Microsoft Lync 2013 to a SIP Trunk 15 June 2013

16 Connecting Microsoft Lync 2013 to a SIP Trunk This screen is displayed: Figure 3-2: Topology Builder Options 2. Select the Download Topology from existing deployment option and click OK; you're prompted to save the downloaded Topology: Figure 3-3: Save Topology 3. Enter a name for the Topology file and click Save. This step enables you to roll back from any changes you make during the installation. AudioCodes Mediant E-SBC 16 Document #: LTRT-54004

17 Configuration Note 3. Configuring Microsoft Lync Server 2013 The Topology Builder screen with the downloaded Topology is displayed: Figure 3-4: Topology Builder Displaying Downloaded Topology 4. In the tree, expand Lync Server 2013 > your site name > Shared Components. 5. Right-click the PSTN Gateways folder and select New IP/PSTN Gateway from the popup menu: Figure 3-5: Selecting New IP/PSTN Gateway Connecting Microsoft Lync 2013 to a SIP Trunk 17 June 2013

18 Connecting Microsoft Lync 2013 to a SIP Trunk This dialog opens: Figure 3-6: Define New IP/PSTN Gateway 6. Enter the Fully Qualified Domain Name (FQDN) of the E-SBC (e.g., ITSP-GW.ilync15.local). This FQDN should be updated in the relevant DNS record and then, click Next. 7. Define the listening mode (IPv4 or IPv6) of the IP address of your new PSTN gateway and click Next. AudioCodes Mediant E-SBC 18 Document #: LTRT-54004

19 Configuration Note 3. Configuring Microsoft Lync Server 2013 Figure 3-7: Define the IP Address 8. Click Next. 9. Define a root trunk for the PSTN gateway. A trunk is a logical connection between a Mediation Server and a gateway, uniquely identified by the combination {Mediation Server FQDN, Mediation Server listening port (TLS or TCP): gateway IP and FQDN, gateway listening port} When defining a PSTN gateway in Topology Builder, you must define a root trunk to successfully add the PSTN gateway to your topology. The root trunk cannot be removed until the associated PSTN gateway is removed. Connecting Microsoft Lync 2013 to a SIP Trunk 19 June 2013

20 Connecting Microsoft Lync 2013 to a SIP Trunk Figure 3-8: Define the Root Trunk a. In the 'Listening Port for IP/PSTN Gateway' field, type the listening port that the E-SBC will use for SIP messages from the Mediation Server that will be associated with the root trunk of the PSTN gateway (i.e., 5067). b. In the 'SIP Transport Protocol' field, click the transport type (i.e., TLS) that the trunk uses. c. In the 'Associated Mediation Server' field, select the Mediation Server pool to associate with the root trunk of this PSTN Gateway. d. In the 'Associated Mediation Server port' field, type the listening port that the Mediation Server will use for SIP messages from the SBC (i.e., 5067). Click Finish; the SBC is added as a PSTN Gateway and a trunk is created: AudioCodes Mediant E-SBC 20 Document #: LTRT-54004

21 Configuration Note 3. Configuring Microsoft Lync Server 2013 Figure 3-9: E-SBC Added as an IP/PSTN Gateway and Trunk Created 10. Publish the Topology: In the main tree, select the root item Lync Server and from the Action menu, select Publish Topology: Figure 3-10: Selecting 'Publish Topology' from the 'Action' Menu Connecting Microsoft Lync 2013 to a SIP Trunk 21 June 2013

22 Connecting Microsoft Lync 2013 to a SIP Trunk The Publish Topology screen is displayed: Figure 3-11: Publish Topology 11. Click Next; the Topology Builder starts publishing your topology: AudioCodes Mediant E-SBC 22 Document #: LTRT-54004

23 Configuration Note 3. Configuring Microsoft Lync Server 2013 Figure 3-12: Publish Topology Progress Screen 12. Wait for the publishing topology process to successfully complete: Connecting Microsoft Lync 2013 to a SIP Trunk 23 June 2013

24 Connecting Microsoft Lync 2013 to a SIP Trunk Figure 3-13: Publish Topology Successfully Completed 13. Click Finish. AudioCodes Mediant E-SBC 24 Document #: LTRT-54004

25 Configuration Note 3. Configuring Microsoft Lync Server Configuring 'Route' on Lync Server 2013 This section shows how to configure a 'Route' on the Lync Server 2013 and to associate it with the E-SBC PSTN gateway. To configure a 'route' on Lync Server 2013: 1. Start the Microsoft Lync Server 2013 Control Panel: Click Start > All Programs > Microsoft Lync Server 2013 and then click Lync Server Control Panel: Figure 3-14: Opening the Lync Server Control Panel You're prompted to enter your login credentials: Connecting Microsoft Lync 2013 to a SIP Trunk 25 June 2013

26 Connecting Microsoft Lync 2013 to a SIP Trunk Figure 3-15: Lync Server Credentials 2. Enter your domain 'User name' and 'Password' and click OK; the Microsoft Lync Server 2013 Control Panel is displayed: Figure 3-16: Microsoft Lync Server 2013 Control Panel 3. In the left navigation pane, select Voice Routing: AudioCodes Mediant E-SBC 26 Document #: LTRT-54004

27 Configuration Note 3. Configuring Microsoft Lync Server 2013 Figure 3-17: Voice Routing Connecting Microsoft Lync 2013 to a SIP Trunk 27 June 2013

28 Connecting Microsoft Lync 2013 to a SIP Trunk 4. In the Voice Routing page, click the Route tab: Figure 3-18: Route Option 5. Click New; the New Voice Route dialog opens: Figure 3-19: Adding New Voice Route AudioCodes Mediant E-SBC 28 Document #: LTRT-54004

29 Configuration Note 3. Configuring Microsoft Lync Server In the 'Name' field, enter a name for this route (e.g., SIP Trunk Route). 7. In the 'Build a Pattern to Match' field, enter the starting digits you want this route to handle (e.g., *, i.e., to match all numbers). 8. Click Add. Figure 3-20: Adding New Trunk 9. Associate the route with the E-SBC Trunk that you created: a. In the Associated Trunks pane, click Add; a list of all the deployed gateways is displayed: Connecting Microsoft Lync 2013 to a SIP Trunk 29 June 2013

30 Connecting Microsoft Lync 2013 to a SIP Trunk Figure 3-21: List of Deployed Trunks b. Select the E-SBC Trunk you created and click OK: AudioCodes Mediant E-SBC 30 Document #: LTRT-54004

31 Configuration Note 3. Configuring Microsoft Lync Server 2013 Figure 3-22: Selected E-SBC Trunk Connecting Microsoft Lync 2013 to a SIP Trunk 31 June 2013

32 Connecting Microsoft Lync 2013 to a SIP Trunk 10. Associate a PSTN Usage with this route: In the Associated PSTN Usages group, click Select and then add the associated PSTN Usage. Figure 3-23: Associating PSTN Usage with the Route 11. Click OK (located under the New Voice Route section); the New Voice Route (Uncommitted) is displayed: Figure 3-24: Confirmation of New Voice Route 12. From the Commit drop-down list, choose Commit all: Figure 3-25: Committing Voice Routes The Uncommitted Voice Configuration Settings dialog opens: AudioCodes Mediant E-SBC 32 Document #: LTRT-54004

33 Configuration Note 3. Configuring Microsoft Lync Server 2013 Figure 3-26: Uncommitted Voice Configuration Settings 13. Click Commit; a message is displayed confirming a successful voice routing configuration: Figure 3-27: Confirmation of a Successful Voice Routing Configuration Connecting Microsoft Lync 2013 to a SIP Trunk 33 June 2013

34 Connecting Microsoft Lync 2013 to a SIP Trunk 14. Click Close; the newly committed Route is displayed in the Voice Routing screen: Figure 3-28: Voice Routing Screen Displaying Committed Routes AudioCodes Mediant E-SBC 34 Document #: LTRT-54004

35 Configuration Note 4. Configuring AudioCodes E-SBC 4 Configuring AudioCodes E-SBC This section shows how to configure AudioCodes' E-SBC for interworking between Microsoft Lync Server 2013 and an ITSP's SIP Trunk: E-SBC WAN interface: SIP Trunking environment E-SBC LAN interface: Lync Server 2013 environment Configure the E-SBC using the Web-based management interface (embedded Web server). Notes: The E-SBC must be installed with a Software Feature Key that includes the following items: Microsoft SBC Security DSP RTP SIP For more information about the Key, contact your AudioCodes representative. The scope of this document does not cover security aspects of connecting a 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 Recommended Security Guidelines Technical Note. The E-SBC must be installed with SIP firmware version 6.6 or later. Before beginning to configure the E-SBC, select the Full option in the Web interface to display the full Navigation tree: When the E-SBC is reset, the Web interface reverts to Basic display. This document applies to Microsoft Lync 2013 and to Microsoft Lync Connecting Microsoft Lync 2013 to a SIP Trunk 35 June 2013

36 Connecting Microsoft Lync 2013 to a SIP Trunk 4.1 Step 1: Configuring the E-SBC's Network Interfaces The subsections below show how to configure the E-SBC's network interfaces. Several methods can be used. The scenario exemplified in this document uses this method: The E-SBC interfaces are between the Lync servers located on the LAN and the SIP Trunk located on the WAN. The E-SBC connects to the WAN through a DMZ network. The type of physical LAN connection depends on the method used to connect to the enterprise's network. In this example, the E-SBC connects to the LAN and WAN using dedicated LAN ports (i.e., two ports and network cables). In addition, the E-SBC uses two logical network interfaces; one to the LAN (VLAN ID 1) and one to the WAN (VLAN ID 2). Figure 4-1: Network Interfaces LAN Port LAN Port Vlan ID 1 Vlan ID 2 Management Station (OAMP) LAN DMZ WAN Edge Router / Firewall ITSP MS Lync Server DC+DNS+Certificate Server AudioCodes Mediant E-SBC 36 Document #: LTRT-54004

37 Configuration Note 4. Configuring AudioCodes E-SBC Configuring IP Network Interfaces for LAN and WAN This subsection shows how to configure IP network interfaces for: LAN VoIP (Voice) WAN VoIP (WANSP) To configure the interfaces: 1. Open the Multiple Interface Table page (Configuration tab > VoIP > Network Settings > IP Settings). Figure 4-2: Multiple Interface Table 2. Modify the existing LAN network interface: a. Select the 'Index' radio button adjacent to Application Type OAMP + Media + Control and click Edit. b. Configure like this: Parameter Example Setting for IPv4 Example Setting for IPv6 Application Type Interface Mode OAMP + Media + Control (application) See IPv4 in the E-SBC documentation. IP Address " " (E-SBC IP address) Prefix Length "16" for (Subnet mask, in bits) Gateway Default Gateway " " VLAN ID VLAN ID. "1". "1" Interface Name Primary DNS Server IP Address Underlying Interface Arbitrary descriptive name "Voice" DNS IP address " " GROUP_1 (Ethernet port group) Media + Control. The OAMP application can be configured only with IPv4. See IPv6 in the E-SBC documentation. "2001::101" (only a global address can be entered) "64" (only 64 is supported) "2001::1" "IP6Voice" "2001::10" GROUP_1 Connecting Microsoft Lync 2013 to a SIP Trunk 37 June 2013

38 Connecting Microsoft Lync 2013 to a SIP Trunk 3. Add another network interface for the WAN side: a. Enter 1 and click Add Index. b. Configure like this: Parameter Example Setting for IPv4 Example Setting for IPv6 Application Type Media + Control (application) Interface Mode See IPv4 in the E-SBC documentation. IP Address " " (WAN IP address) Media + Control See IPv6 in the E-SBC documentation. "2002::155" Prefix Length "16" for "64" (only 64 is supported) Gateway " " (Default Gateway - router s IP address) VLAN ID "2" (WAN VLAN ID) "2" Interface Name Primary DNS Server IP Address Secondary DNS Server IP Address Underlying Interface 4. Click Apply and Done. "WANSP" (arbitrary descriptive name of WAN interface) " " (DNS IP address) " " (DNS IP address) GROUP_2 (Ethernet port group) Configuring the Native VLAN ID "2002::129" "IP6WANSP" 2001:4860:4860:: :4860:4860::8844 GROUP_2 This subsection shows how to configure the Native VLAN ID for the two network interfaces (LAN and WAN). To configure the Native VLAN ID for the LAN and WAN interfaces: 1. Open the Physical Ports Settings page (Configuration tab> VoIP > Network > Physical Ports Settings). 2. In the GROUP_1 member ports, set the Native Vlan field to 1; this VLAN is assigned to network interface Voice. 3. In the GROUP_2 member ports, set the Native Vlan field to 2; this VLAN is assigned to network interface WANSP. Figure 4-3: Ports Native VLAN AudioCodes Mediant E-SBC 38 Document #: LTRT-54004

39 Configuration Note 4. Configuring AudioCodes E-SBC 4.2 Step 2: Enabling the SBC Application This step shows how to enable the SBC application. To enable the SBC application: 1. Open the Applications Enabling page (Configuration tab > VoIP > Applications Enabling > Applications Enabling). Figure 4-4: Applications Enabling 2. From the 'SBC Application' drop-down list, select Enable. 3. Reset the E-SBC with a burn to flash for this setting to take effect (see Section 4.16 on page 73). Connecting Microsoft Lync 2013 to a SIP Trunk 39 June 2013

40 Connecting Microsoft Lync 2013 to a SIP Trunk 4.3 Step 3: Configuring SRDs This step shows how to configure Signaling Routing Domains (SRDs). An SRD is a set of definitions comprising IP interfaces, E-SBC resources, SIP behaviors, and Media Realms Configuring Media Realms A Media Realm represents a set of ports, associated with an IP interface, used by the E-SBC to transmit or receive media (RTP or SRTP). Media Realms are associated with SRDs or IP Groups. Simplest is to configure one Media Realm for internal (LAN) traffic and another for external (WAN) traffic as shown below, applied to the example scenario. To configure Media Realms: 1. Open the Media Realm Table page (Configuration tab > VoIP > Media > Media Realm Configuration). 2. Add a Media Realm for the LAN traffic: a. Click Add. b. Configure like this: Parameter Example Setting Index "1" Media Realm Name IPv4 Interface Name IPv6 Interface Name Port Range Start Number of Media Session Legs "MRLan" (an arbitrary name) Voice (the interface name) IP6Voice (the interface name). Note: Only applicable if using IPv6. "6000" (a number representing the lowest UDP port number to be used for media on the LAN) "10" (the number of media sessions assigned with the port range) Figure 4-5: Configuring a LAN Media Realm c. Click Submit. AudioCodes Mediant E-SBC 40 Document #: LTRT-54004

41 Configuration Note 4. Configuring AudioCodes E-SBC 3. Add a Media Realm for the external traffic (WAN): a. Click Add. b. Configure like this: Parameter Example Setting Index "2" Media Realm Name IPv4 Interface Name IPv6 Interface Name Port Range Start Number of Media Session Legs "MRWan" (an arbitrary name) WANSP (the interface name) IP6WANSP (the interface name) Note: Only applicable if using IPv6. "7000" (a number representing the lowest UDP port number to be used for media on the WAN) "10" (the number of media sessions assigned with the port range) Figure 4-6: Configuring a WAN Media Realm c. Click Submit. The configured Media Realm table is shown below: Figure 4-7: Required Media Realm Table Connecting Microsoft Lync 2013 to a SIP Trunk 41 June 2013

42 Connecting Microsoft Lync 2013 to a SIP Trunk Configuring SRDs This subsection shows how to configure the SRDs. To configure the SRDs: 1. Open the SRD Table page (Configuration tab > VoIP > Control Network > SRD Table). 2. Add an SRD for the E-SBC's internal interface (toward Lync Server 2013): a. Configure these parameters: Parameter Example Setting SRD Index 1 SRD Name Media Realm "SRDLan" (descriptive name for the SRD) "MRLan" (associates the SRD with a Media Realm) Figure 4-8: Configuring the LAN SRD b. Click Submit. 3. Add an SRD for the E-SBC s external interface (toward the SIP Trunk): a. Configure these parameters: Parameter Example Setting SRD Index 2 SRD Name Media Realm "SRDWan" (descriptive name for the SRD) "MRWan" (associates the SRD with a Media Realm) Figure 4-9: Configuring the WAN SRD b. Click Submit. AudioCodes Mediant E-SBC 42 Document #: LTRT-54004

43 Configuration Note 4. Configuring AudioCodes E-SBC Configuring SIP Signaling Interfaces A SIP Interface consists of a combination of ports (UDP, TCP, and TLS) associated with a specific IP network interface. The SIP Interface is associated with an SRD. The procedure below shows how to add SIP interfaces. In the example scenario, an internal and external SIP interface must be added for the E-SBC. To add SIP interfaces: 1. Open the SIP Interface Table page (Configuration tab > VoIP > Control Network > SIP Interface Table). 2. Add a SIP interface for the LAN: a. Click Add. b. Configure these parameters: Parameter Example Setting Index "1" Network Interface Application Type "Voice" (for IPv4) / "IP6Voice" (for IPv6) SBC TLS Port "5067" TCP and UDP "0" SRD "1" c. Click Submit. 3. Add a SIP interface for the WAN: a. Click Add. b. Configure these parameters: Parameter Example Setting Index "2" Network Interface Application Type "WANSP" (for IPv4) / "IP6WANSP" (for IPv6) SBC UDP Port "5060" TCP and TLS "0" SRD "2" c. Click Submit. The configured SIP Interface table is shown below: Figure 4-10: Required SIP Interface Table Connecting Microsoft Lync 2013 to a SIP Trunk 43 June 2013

44 Connecting Microsoft Lync 2013 to a SIP Trunk 4.4 Step 4: Configuring Proxy Sets This step shows how to configure the Proxy Sets. A Proxy Set is a group of Proxy servers defined by IP address or fully qualified domain name (FQDN). In the example scenario, two Proxy Sets must be configured for: Microsoft Lync Server 2013 SIP Trunk These Proxy Sets will later be associated with IP Groups. To add Proxy Sets: 1. Open the Proxy Sets Table page (Configuration tab > VoIP > Control Network > Proxy Sets Table). 2. Add a Proxy Set for Lync Server 2013: a. Configure these parameters: Parameter Example Setting Proxy Set ID 1 Proxy Address Transport Type Enable Proxy Keep Alive Proxy Load Balancing Method Is Proxy Hot Swap "FE15.ilync15.local:5067" (the Lync Server 2013 SIP Trunking IP address or FQDN and destination port) TLS Using Options Round Robin Yes SRD Index "1" AudioCodes Mediant E-SBC 44 Document #: LTRT-54004

45 Configuration Note 4. Configuring AudioCodes E-SBC Figure 4-11: Proxy Set for Microsoft Lync Server 2013 b. Click Submit. Connecting Microsoft Lync 2013 to a SIP Trunk 45 June 2013

46 Connecting Microsoft Lync 2013 to a SIP Trunk 3. Add a Proxy Set for the SIP Trunk: a. Configure these parameters: Parameter Example Setting Proxy Set ID 2 Proxy Address Transport Type Enable Proxy Keep Alive Is Proxy Hot Swap Proxy Redundancy Mode SRD Index "SIPTrunk.Company.com:5060" (SIP Trunk IP address or FQDN and destination port) UDP Using Options Yes Homing "2" (enables classification by Proxy Set for this SRD in the IP Group belonging to the SIP Trunk) Figure 4-12: Configuring a Proxy Set for the SIP Trunk b. Click Submit. AudioCodes Mediant E-SBC 46 Document #: LTRT-54004

47 Configuration Note 4. Configuring AudioCodes E-SBC 4.5 Step 5: Configuring IP Groups This step shows how to create IP Groups. An IP Group represents a SIP entity behavior in the E-SBC's network. In the example scenario, IP Groups are created for: Lync Server 2013 (Mediation Server) on the LAN SIP Trunk on the WAN 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 > Control Network > IP Group Table). 2. Add an IP Group for the Lync Server 2013 Mediation Server: a. Click Add. b. Configure the parameters like this: Parameter Example Setting Index "1" Type Description Proxy Set ID "1" SRD "1" Media Realm Name IP Profile ID "1" c. Click Submit. 3. Add an IP Group for the SIP Trunk: a. Click Add. b. Configure the parameters like this: Server "Lync Server" (a descriptive name) "MRLan" Parameter Example Setting Index "2" Type Server Description "SIP Trunk" (a descriptive name) Proxy Set ID "2" SRD "2" Media Realm Name "MRWan" IP Profile ID "2" c. Click Submit. Connecting Microsoft Lync 2013 to a SIP Trunk 47 June 2013

48 Connecting Microsoft Lync 2013 to a SIP Trunk The figure below shows the configured IP Group table: Figure 4-13: Configured IP Group Table AudioCodes Mediant E-SBC 48 Document #: LTRT-54004

49 Configuration Note 4. Configuring AudioCodes E-SBC 4.6 Step 6: Configuring IP Profiles This step shows how to configure IP Profiles. In the example scenario, the IP Profiles are used to configure the SRTP / TLS modes and other parameters that differ between the two entities - Lync Server 2013 and SIP Trunk. Note that the IP Profiles were assigned to the relevant IP Group in the previous step (see Section 4.5 on page 47). In the example, an IP Profile is added for each entity: Microsoft Lync Server to operate in secure mode using SRTP and TLS SIP trunk - to operate in non-secure mode using RTP and UDP To add IP Profiles: 1. Open the IP Profile Settings page (Configuration tab > VoIP > Coders and Profiles > IP Profile Settings). 2. Add an IP Profile for Lync Server 2013: a. Configure the parameters like this: Parameter Example Setting Profile ID 1 Media IP Version Preference Reset SRTP State Upon Re-key Only IPv4 / Only IPv6 Enable Extension Coders Group ID Coders Group 1 Media Security Behavior SBC Remote Early Media RTP RFC 2833 Behavior SBC Remote Update Support SBC Remote Re-Invite Support SBC Remote Refer Behavior SBC Remote 3xx Behavior SBC Remote Hold Format SRTP Delayed (mandatory because the Lync Server 2013 does not immediately send RTP to the remote side if it sends a SIP 18x response) Extend (in case the SIP Trunk does not send RFC 2833 in SDP) Supported Only After Connect Supported Only With SDP Handle Locally (mandatory because Lync Server 2013 does not support receive Refer) Handle Locally (mandatory because Lync Server 2013 does not support receive 3xx) Inactive Connecting Microsoft Lync 2013 to a SIP Trunk 49 June 2013

50 Connecting Microsoft Lync 2013 to a SIP Trunk Figure 4-14: Configured IP Profile for Lync Server 2013 b. Click Submit. AudioCodes Mediant E-SBC 50 Document #: LTRT-54004

51 Configuration Note 4. Configuring AudioCodes E-SBC 3. Add an IP Profile for the SIP Trunk: a. Configure the parameters like this: Parameter Example Setting Profile ID 2 Media IP Version Preference Only IPv4 / Only IPv6 Extension Coders Group ID Coders Group 2 Allowed Coders Group ID Coders Group 2 Allowed Coders Mode Media Security Behavior SBC Remote Refer Behavior Preference (enables the received SDP offer to list Allowed coders first and then the original coders received in the SDP). RTP Handle Locally (the E-SBC handles the incoming REFER request itself, without forwarding the REFER towards the SIP Trunk) Note: The SIP Trunk's IP Profile depends on the SIP Trunk behavior. Refer to the explanations of the IP Profile parameters in the E-SBC User's Manual in order to configure the profile according to SIP Trunk behavior. Connecting Microsoft Lync 2013 to a SIP Trunk 51 June 2013

52 Connecting Microsoft Lync 2013 to a SIP Trunk Figure 4-15: Configured IP Profile for SIP Trunk b. Click Submit. AudioCodes Mediant E-SBC 52 Document #: LTRT-54004

53 Configuration Note 4. Configuring AudioCodes E-SBC 4.7 Step 7: Configuring Coders This step shows how to configure coders (termed Coder Groups). You can configure up to four different Coder Groups. As Lync Server 2013 supports the G.711 coder while the network connection to SIP Trunk may restrict you to operate with a lower bandwidth coder such as G.729, you need to add a Coder Group with the G.711 coders for Lync Server 2013, and Coder Group with the G.729 coder for the SIP Trunk. Note that the Coder Group ID for this entity was assigned to its corresponding IP Profile in the previous step (see Section 4.6 on page 49). To configure coders: 1. Add a Coder Group for Lync Server a. Configure the parameters like this: Parameter Example Setting Coder Group ID 1 Coder Name Coder Name Silence Suppression G.711 U-law G.711 A-law Enable Figure 4-16: Configured Coder Group for Lync Server 2013 b. Click Submit. 2. Add a Coder Group for SIP Trunk: a. Configure the parameters like this: Parameter Example Setting Coder Group ID 2 Coder Name G.729 Figure 4-17: Configured Coder Group for the SIP Trunk b. Click Submit. Connecting Microsoft Lync 2013 to a SIP Trunk 53 June 2013

54 Connecting Microsoft Lync 2013 to a SIP Trunk The step below adds an Allowed Coders Group to ensure that voice sent to the SIP Trunk uses the G.729 coder whenever possible. Note that this Allowed Coders Group ID (and its preference) was assigned to the IP Profile belonging to the SIP Trunk in the previous step (see Section 4.6 on page 49). To set a preferred coder for the SIP Trunk: 1. Open the Allowed Coders Group page (Configuration tab > VoIP > SBC > Allowed Coders Group). 2. From the Allowed Coders Group ID drop-down list, select From the 'Coder Name' drop-down list, select G.729. Figure 4-18: Allowed Coders Group for SIP Trunk 4. Click Submit. AudioCodes Mediant E-SBC 54 Document #: LTRT-54004

55 Configuration Note 4. Configuring AudioCodes E-SBC 4.8 Step 8: Configuring a SIP TLS Connection This step shows how to configure the E-SBC to use a TLS connection with the Lync Server 2013 Mediation Server. This step is mandatory for a secure SIP TLS connection Configuring the NTP Server Address This step shows how to configure the NTP server's IP address. It's recommended to implement an NTP server (Microsoft NTP server or third-party server) to ensure that the E-SBC receives accurate and current date and time. This is necessary for validating certificates of remote parties. To configure the NTP server address: 1. Open the Application Settings page (Configuration tab > System > Application Settings). 2. In the 'NTP Server IP Address' field, enter the IP address of the NTP server (e.g., ). Figure 4-19: Configuring the NTP Server IP Address 3. Click Submit. Connecting Microsoft Lync 2013 to a SIP Trunk 55 June 2013

56 Connecting Microsoft Lync 2013 to a SIP Trunk Configuring a Certificate This step shows how to exchange a certificate with the Microsoft Certificate Authority (CA). The certificate is used by the E-SBC to authenticate the connection with the management station (i.e., the computer used to manage the E-SBC through its embedded Web server). To configure a certificate: 1. Open the Certificates page (Configuration tab > System > Certificates). Figure 4-20: Certificates Page - Creating CSR 2. In the 'Subject Name' field, enter the media gateway name (e.g., ITSP- GW.ilync15.local). This name must be identical to the gateway name configured in the Topology Builder for Lync Server 2013 (see Section 3.1 on page 15). 3. Click Create CSR; a certificate request is generated. 4. Copy the CSR (from the line ----BEGIN CERTIFICATE to the line END CERTIFICATE REQUEST----) to a text file (such as Notepad) and save it to a folder on your computer with the file name certreq.txt. AudioCodes Mediant E-SBC 56 Document #: LTRT-54004

57 Configuration Note 4. Configuring AudioCodes E-SBC 5. Open a Web browser and navigate to the Microsoft Certificates Services Web site at server>/certsrv. Figure 4-21: Microsoft Certificate Services Web Page 6. Click Request a certificate. Figure 4-22: Request a Certificate Page 7. Click advanced certificate request and click Next. Connecting Microsoft Lync 2013 to a SIP Trunk 57 June 2013

58 Connecting Microsoft Lync 2013 to a SIP Trunk Figure 4-23: Advanced Certificate Request Page 8. Click Submit a certificate request... and click Next. Figure 4-24: Submit a Certificate Request or Renewal Request Page 9. Open the certreq.txt file that you created and saved in Step 4 and copy its contents to the Base-64-Encoded Certificate Request field. 10. From the 'Certificate Template' drop-down list, select Web Server. 11. Click Submit. AudioCodes Mediant E-SBC 58 Document #: LTRT-54004

59 Configuration Note 4. Configuring AudioCodes E-SBC Figure 4-25: Certificate Issued Page 12. Select the Base 64 encoded option for encoding and click Download certificate. 13. Save the file with the name gateway.cer to a folder on your computer. 14. Click the Home button (or navigate to the certificate server at Server>/CertSrv). 15. Click the Download a CA certificate, Certificate Chain, or CRL: Figure 4-26: Download a CA Certificate, Certificate Chain, or CRL 16. Under the 'Encoding method' group, select the Base 64 option for encoding. 17. Click Download CA certificate. Connecting Microsoft Lync 2013 to a SIP Trunk 59 June 2013

60 Connecting Microsoft Lync 2013 to a SIP Trunk 18. Save the file with the name certroot.cer to a folder on your computer. 19. In the E-SBC's Web interface, return to the Certificates page and do this: a. In the Device Certificate field, click Choose File and select the gateway.cer certificate file that you saved on your computer in Step 13; then click Send File to upload the certificate to the E-SBC. b. In the 'Trusted Root Certificate Store' field, click Choose File and select the certroot.cer certificate file that you saved on your computer in Step 18; then click Send File to upload the certificate to the E-SBC. Figure 4-27: Certificates Page (Uploading Certificate) 20. Reset the E-SBC with a burn to flash for your settings to take effect (see Section 4.16 on page 73). AudioCodes Mediant E-SBC 60 Document #: LTRT-54004

61 Configuration Note 4. Configuring AudioCodes E-SBC 4.9 Step 9: Configuring SRTP This step shows how to configure media security. If you configure the Microsoft Mediation Server to use Secure Real-Time Transport Protocol (SRTP), configure the E-SBC to do so as well. Note that SRTP was enabled for Lync Server 2013 when you added an IP Profile for Lync Server 2013 (see Section 4.6 on page 49). To configure media security: 1. Open the Media Security page (Configuration tab > VoIP > Media > Media Security). Figure 4-28: Media Security Page 2. Configure the parameters like this: Parameter Example Setting Media Security Enable Master Key Identifier (MKI) Size "1" Symmetric MKI Negotiation Enable 3. Click Submit. 4. Reset the E-SBC with a burn to flash for your settings to take effect (see Section 4.16 on page 73). Connecting Microsoft Lync 2013 to a SIP Trunk 61 June 2013

62 Connecting Microsoft Lync 2013 to a SIP Trunk 4.10 Step 10: Configuring IP Media This step shows how to configure the number of media channels for IP-based media. To perform coder transcoding, define digital signaling processors (DSP) channels. The number of media channels represents the number of DSP channels that the E-SBC allocates to sessions. Note: This step is required only if transcoding is required. To configure IP media: 1. Open the IP Media Settings page (Configuration tab > VoIP > IP Media > IP Media Settings). Figure 4-29: IP Media Settings 2. In the 'Number of Media Channels' field, enter the number of media channels according to your environment's transcoding calls (e.g., 30). 3. Click Submit. AudioCodes Mediant E-SBC 62 Document #: LTRT-54004

63 Configuration Note 4. Configuring AudioCodes E-SBC 4.11 Step 11: Configuring IP-to-IP Call Routing Rules This step shows how to configure IP-to-IP call routing rules (configured in the IP-to-IP Routing table). These rules define the route for forwarding SIP messages (e.g., INVITE) received on one IP interface, to another. The SIP message is routed according to a rule whose configured input characteristics (e.g., Source IP Group) match those of the message. If the characteristics of an incoming message do not match the first rule in the table, they are then compared to the second rule, and so on, until a matching rule is located. If no rule is matched, the message is rejected. In the example scenario, the following IP-to-IP routing rules must be added in order to route calls between Lync Server 2013 (LAN) and SIP Trunk (WAN): Terminate SIP OPTIONS messages on the E-SBC that are received from the LAN Calls from LAN to WAN Calls from WAN to LAN The routing rules use IP Groups to denote the source and destination of the call. As configured in Step 5 (see Section 4.5 on page 47), IP Group ID 1 was assigned to Lync Server 2013, and IP Group ID 2 to SIP Trunk. To add IP-to-IP routing rules: 1. Open the IP-to-IP Routing Table page (Configuration tab > VoIP > SBC > Routing SBC > IP to IP Routing Table). 2. Add a rule to terminate SIP OPTIONS messages received from the LAN: a. Click Add. b. Configure the parameters like this: Parameter Example Setting Index "0" Source IP Group ID "1" Request Type Destination Type Destination Address OPTIONS Dest Address "internal" Connecting Microsoft Lync 2013 to a SIP Trunk 63 June 2013

64 Connecting Microsoft Lync 2013 to a SIP Trunk Figure 4-30: Configured IP-to-IP Routing Rule to Terminate SIP OPTIONS Messages Received from the LAN c. Click Submit. 3. Add a rule to route calls from LAN to WAN: a. Click Add. b. Configure the parameters like this: Parameter Example Setting Index "1" Source IP Group ID "1" Destination Type IP Group Destination IP Group ID "2" Destination SRD ID "2" AudioCodes Mediant E-SBC 64 Document #: LTRT-54004

65 Configuration Note 4. Configuring AudioCodes E-SBC Figure 4-31: IP-to-IP Routing Rule for LAN to WAN c. Click Submit. 4. Add a rule to route calls from WAN to LAN: a. Click Add. b. Configure the parameters like this: Parameter Example Setting Index "2" Source IP Group ID "2" Destination Type IP Group Destination IP Group ID "1" Destination SRD ID "1" Connecting Microsoft Lync 2013 to a SIP Trunk 65 June 2013

66 Connecting Microsoft Lync 2013 to a SIP Trunk Figure 4-32: Configured IP-to-IP Routing Rule to Route Calls from WAN to LAN c. Click Submit. The figure below shows the above configured routing rules in the IP-to-IP Routing Table: Figure 4-33: IP-to-IP Routing Table Note: The routing configuration may change according to the local deployment topology. AudioCodes Mediant E-SBC 66 Document #: LTRT-54004

67 Configuration Note 4. Configuring AudioCodes E-SBC 4.12 Step 12: Configuring IP-to-IP Outbound Manipulation This step shows how to configure IP-to-IP manipulation rules. They concern number manipulation of the source and / or destination number. They use IP Groups to denote the source and destination of the call. As configured in Step 5 (see Section 4.5 on page 47), IP Group ID 1 was assigned to Lync Server 2013 and IP Group ID 2 to the SIP Trunk. Note: Adapt the manipulation table according to you environment dial plan. The step below exemplifies configuring a manipulation rule which adds a plus sign + to the destination number for calls from IP Group 2 (SIP Trunk) destined to IP Group 1 (i.e., Lync Server 2013), when the destination number prefix is any number (*). To add a number manipulation rule: 1. Open the IP to IP Outbound Manipulation page (Configuration tab > VoIP > SBC > Manipulation SBC > IP to IP Outbound). 2. Click Add. 3. Click the Rule tab and configure the parameters like this: Parameter Example Setting Index "1" Source IP Group "2" Destination IP Group "1" Destination Username Prefix "*" Manipulated URI Destination Figure 4-34: IP-to-IP Outbound Manipulation Rule Rule Tab Connecting Microsoft Lync 2013 to a SIP Trunk 67 June 2013

68 Connecting Microsoft Lync 2013 to a SIP Trunk 4. Click the Action tab and configure the parameters like this: Parameter Example Setting Prefix to Add "+" Figure 4-35: Configured IP-to-IP Outbound Manipulation Rule - Action Tab 5. Click Submit. The IP to IP Outbound Manipulation table displayed below includes four manipulation rules for calls between IP Group 1 (i.e., Lync Server 2013) and IP Group 2 (i.e., SIP Trunk): Figure 4-36: IP-to-IP Outbound Manipulation Rule Index Description 0 Calls received from IP Group 2 and destined to IP Group 1 that have any destination number (*), add "+" to the prefix of the destination number. 1 Calls received from IP Group 1 and destined to IP Group 2 that have a prefix destination number of "+", remove "+" from this prefix. 2 Calls received from IP Group 1 and destined to IP Group 2 with source number prefix of "+", remove the "+" from this prefix source number. AudioCodes Mediant E-SBC 68 Document #: LTRT-54004

69 Configuration Note 4. Configuring AudioCodes E-SBC 4.13 Step 13: Configuring SIP Message Manipulation Rules This step shows how to configure SIP message manipulation rules (configured in the Message Manipulations table). SIP message manipulation rules can include insertion, removal and/or modification of SIP headers. Multiple manipulation rules can be configured for the same SIP message. After configuring the SIP message manipulation rules, assign them to the relevant IP Group (in the IP Group table) and determine whether they must be applied to inbound or outbound messages. See an example below of a message manipulation rule configuration; use the E-SBC User's Manual for detailed instructions on how to configure message manipulation rules according to your requirements. In the example scenario, the configured manipulation rule manipulates the P-Asserted- Identity user part of the header, and replaces it with the user part that appears on the Referred-By header. To configure SIP message manipulation rules: 1. Open the Message Manipulations page (Configuration tab > VoIP > SIP Definitions > Msg Policy & Manipulation > Message Manipulations). Figure 4-37: Message Manipulations Page 2. Add the following manipulation rules for Manipulation Set ID 0: Parameter Example Setting Index "0" Manipulation Set ID "0" Message Type Condition Action Subject Action Type Action Value any Note: Enter the value as is. header.referred-by exists Note: Enter the value as is. header.p-asserted-identity Note: Enter the value as is. Modify '<'+header.referred-by.url+'>' Note: Enter the value as is. Connecting Microsoft Lync 2013 to a SIP Trunk 69 June 2013

70 Connecting Microsoft Lync 2013 to a SIP Trunk Figure 4-38: Configured SIP Message Manipulation Rule Click Submit. 3. Assign the Manipulation Set ID 0 to IP Group 2: a. Open the IP Group Table page (Configuration tab > VoIP > Control Network > IP Group Table). b. Select the row of IP Group 2 and click Edit. c. Click the SBC tab. d. Set the Outbound Message Manipulation Set field to 0. Figure 4-39: Assigning a Manipulation Rule to IP Group 2 e. Click Submit. AudioCodes Mediant E-SBC 70 Document #: LTRT-54004

71 Configuration Note 4. Configuring AudioCodes E-SBC 4.14 Step 14: Configuring a Registration Account This step shows how to configure SIP registration accounts (in the Account Table page) so that the E-SBC can register with the SIP Trunk on behalf of Lync Server Note: Not all SIP Trunks require registration (and authentication) to provide service. If your SIP Trunk doesn't require registration, skip this step. In this example, the Served IP Group is Lync Server 2013 (IP Group 1) and the Serving IP Group is SIP Trunk (IP Group 2). To configure a registration account: 1. Open the Account Table page (Configuration tab > VoIP > SIP Definitions > Account Table). Figure 4-40: Configuring a SIP Registration Account 2. Enter an index number (1) and click Add. 3. Configure the account according to the information provided by the SIP Trunk provider, for example: Parameter Example Setting Served IP Group "1" (i.e., Lync Server 2013) Serving IP Group "2" (i.e., SIP Trunk) Username (Provided by the SIP Trunk provider) Password (Provided by the SIP Trunk provider) Register Yes Application Type SBC 4. Click Apply. Connecting Microsoft Lync 2013 to a SIP Trunk 71 June 2013

72 Connecting Microsoft Lync 2013 to a SIP Trunk 4.15 Step 15: Configuring Miscellaneous E-SBC Functionalities This step shows how to configure the E-SBC's handling of SIP 18x responses received due to call forking of an INVITE. In the example scenario, if an 18x with SDP is received, the E-SBC opens a voice stream according to the received SDP. The E-SBC reopens the stream according to subsequently received 18x responses with SDP, or plays a ringback tone if a 180 response without SDP is received. It's mandatory to set this field for the Lync Server 2013 environment. To configure call forking: 1. Open the General Settings page (Configuration tab > VoIP > SBC > General Settings). 2. From the 'SBC Forking Handling Mode' drop-down list, select Sequential. Figure 4-41: Configuring Forking Mode 3. From the SBC Preferences Mode drop-down list, select Include Extensions to ensure that Extension coders and Allowed coders are arranged according to their order of appearance in the Allowed Coders Group table. 4. Click Submit. AudioCodes Mediant E-SBC 72 Document #: LTRT-54004

73 Configuration Note 4. Configuring AudioCodes E-SBC 4.16 Step 16: Resetting the E-SBC After completing the configuration of the E-SBC as described in the preceding steps, save (burn) the configuration to the E-SBC's flash memory with a reset; the settings will now take effect. To save the configuration to flash memory with a reset: 1. Open the Maintenance Actions page (Maintenance tab > Maintenance > Maintenance Actions). Figure 4-42: Resetting the E-SBC 2. Ensure that the 'Burn to FLASH' field is set to Yes (default). 3. Click the Reset button. Connecting Microsoft Lync 2013 to a SIP Trunk 73 June 2013

74 Connecting Microsoft Lync 2013 to a SIP Trunk Reader's Notes AudioCodes Mediant E-SBC 74 Document #: LTRT-54004

75 Configuration Note A. Configuring E-SBC to Send 414 Request-URI Too Long Response A Configuring E-SBC to Send 414 Request- URI Too Long Response This step shows how to configure the E-SBC to send a 414 Request-URI Too Long response when it encounters a Request URI it cannot handle due to excessive length. When the E-SBC receives an INVITE with a long Request URI (a condition rule), it will route it to an unknown destination IP address (i.e., ) and it will set a variable for this call to 1. After a timeout, the E-SBC will generate an internal 408 Request Timeout response. Using message manipulation, the E-SBC will convert this response to a 414 Request-URI Too Long response (only if the variable value is 1). To configure a condition for this route: 1. Open the Condition Table page (Configuration tab > VoIP > SBC > Routing SBC > Condition Table). 2. Click the Add tab and configure the parameters like this: Parameter Example Setting Index "0" Condition header.request-uri.url.host.name len>'100' Note: You can choose the length of the Request-URI to process. Figure A-1: Configuring a Condition for the Route 3. Click Submit. To configure the route: 1. Open the IP-to-IP Routing Table page (Configuration tab > VoIP > SBC > Routing SBC > IP to IP Routing Table). 2. Add a rule to route long-uri calls to unknown IP address: a. Click Add. b. Configure the parameters like this: Parameter Example Setting Index Message Condition Destination Type Destination Address "0" (this rule should be the first rule in the table) "0" (this number is the index of the condition configured above) Dest address " " (unreachable IP address) Connecting Microsoft Lync 2013 to a SIP Trunk 75 June 2013

76 Connecting Microsoft Lync 2013 to a SIP Trunk Figure A-2: IP-to-IP Routing Rule for Long-URI Calls To configure a message manipulation rule: 1. Open the Message Manipulations page (Configuration tab > VoIP > SIP Definitions > Msg Policy & Manipulation > Message Manipulations). 2. Add a rule to set a variable to 1 in the case of a long-uri call: a. Click Add. b. Configure the parameters like this: Parameter Example Setting Index "0" Manipulation Set ID "1" Message Type Condition Action Subject Action Type Action Value invite.request header.request-uri.url.host.name len>'100' var.call.src.0 Modify '1' AudioCodes Mediant E-SBC 76 Document #: LTRT-54004

77 Configuration Note A. Configuring E-SBC to Send 414 Request-URI Too Long Response Figure A-3: Manipulation Rule to Set a Variable to '1' in Case of Long-URI Call c. Click Submit. 3. Add a rule to convert 408 to '414': a. Click Add. b. Configure the parameters like this: Parameter Example Setting Index "1" Manipulation Set ID "2" Message Type Condition Action Subject Action Type Action Value invite.response.408 var.call.src.0 == '1' header.request-uri.methodtype Modify '414' Figure A-4: Manipulation Rule to Convert 408 to '414' c. Click Submit. Connecting Microsoft Lync 2013 to a SIP Trunk 77 June 2013

78 Connecting Microsoft Lync 2013 to a SIP Trunk Figure A-5: Message Manipulations Page 4. Assign the Manipulation Set to IP Group 1 : a. Open the IP Group Table page (Configuration tab > VoIP > Control Network > IP Group Table). b. Select the row of IP Group 1 and click Edit. c. Click the SBC tab. d. Set the Inbound Message Manipulation Set field to 1. e. Set the Outbound Message Manipulation Set field to 2. Figure A-6: Assigning Manipulation Rule to IP Group 1 f. Click Submit. AudioCodes Mediant E-SBC 78 Document #: LTRT-54004