Configuration Note. Enhanced Gateway with Analog Devices for Microsoft Lync Server Microsoft Lync Server 2010.

Size: px
Start display at page:

Download "Configuration Note. Enhanced Gateway with Analog Devices for Microsoft Lync Server Microsoft Lync Server 2010."

Transcription

1 Microsoft Lync Server 2010 Enhanced Gateway Mediant Gateway family Configuration Note Enhanced Gateway with Analog Devices for Microsoft Lync Server 2010 September 2013 Document #: LTRT-40140

2

3 Configuration Note Contents Table of Contents 1 Introduction Component Information AudioCodes Devices Microsoft Lync Server AudioCodes ATA Deploying the Device (Topology) Environment Setup Accessing the Device Initial Access to the Device Assigning IP Address to the Device Configuring the Device Step 1: Modifying IP Address to the Device 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 a SIP TLS Connection Configuring the NTP Server Address Configuring the DNS Server Configuring a Certificate Step 8: Configuring SRTP Step 9: Configuring IP Media Step 10: Configuring Voice Coders Step 11: Configuring PSTN Trunks Enabling Trunks Configuring the Channel Select Method Configuring the Trunk Configuring the TDM Bus Step 12: Configuring Enhanced Gateway Routing Configuring IP-to-Trunk Group Routing Configuring Tel-to-IP Routing Step 13: Configuring SBC Classification and Routing Configuring Classification Rules Configuring IP-to-IP Call Routing Rules Step 14: Configuring Normalization Rules for E.164 Format for PBX/PSTN Connectivity Number Manipulation Examples Example Number Manipulation IP to Tel Example Number Manipulation Tel to IP Step 15: Miscellaneous Configuration Configuring Alternative Routing Restricting Communication to Mediation Server Only Configuring Comfort Noise and Gain Control Version September 2013

4 Enhanced Gateway with Analog Devices Configuring Early Media Step 16: Resetting the Device A Configuring AudioCodes Analog Telephone Adapters (ATA) A.1 Configuring the FXS Endpoints A.2 Configuring Trunk Group Settings A.3 Configuring IP To Trunk Group Routing A.4 Configuring Proxy & Registrations A.5 Configuring Proxy Set A.6 Configuring Coders A.7 Configuring SIP UDP Transport Type and Fax Signaling Method A.8 Configuring Gateway Name B Configuring Lync Server B.1 Configuring the Device as an IP / PSTN Gateway B.1.1 Configuring the Gateway Entity B.1.2 Configuring the SBC Entity B.2 Associating IP / PSTN Gateways with Mediation Server B.3 Configuring Analog Device on the Lync Server Management Shell Microsoft Lync Server Document #: LTRT-40140

5 Configuration Note Contents List of Figures Figure 1-1: High-Level Architecture of Enhanced Gateway with Analog Devices... 9 Figure 2-1: Interworking Device Entities Figure 3-1: PSTN Gateway Default IP Addresses Figure 3-2: Login Screen Figure 3-3: IP Settings Screen (Single Network Interface) Figure 3-4: IP Settings Screen (Multiple Network Interface) Figure 3-5: Maintenance Actions: Reset Gateway Figure 4-1: Device Configuration: Summary of Steps Figure 4-2: IP Settings Screen (Multiple Network Interface) Figure 4-3: Applications Enabling Figure 4-4: Configuring a LAN Media Realm Figure 4-5: Configuring the LAN SRD Figure 4-6: Required SIP Interface Table Figure 4-7: Proxy Set for Microsoft Lync Server 2010 (Gateway Entity) Figure 4-8: IP Group Rule for Microsoft Lync Server 2010 (Gateway entity) Figure 4-9: Classify By Proxy Set (Gateway entity) Figure 4-10: Classify by Proxy Set (SBC Entity) Figure 4-11: Configured IP Group Table Figure 4-12: Configured IP Profile for Lync Server Figure 4-13: Configured IP Profile for Analog Device Figure 4-14: Configuring the NTP Server IP Address Figure 4-15: Certificates Page - Creating CSR Figure 4-16: Microsoft Certificate Services Web Page Figure 4-17: Request a Certificate Page Figure 4-18: Advanced Certificate Request Page Figure 4-19: Submit a Certificate Request or Renewal Request Page Figure 4-20: Certificate Issued Page Figure 4-21: Download a CA Certificate, Certificate Chain, or CRL Figure 4-22: Certificates Page (Uploading Certificate) Figure 4-23: Media Security Page Figure 4-24: IP Media Settings Figure 4-25: Coders Table Page Figure 4-26: Trunk Group Table Page Figure 4-27: Trunk Group Settings Page Figure 4-28: Trunk Settings Page Figure 4-29: TDM Bus Settings Page Figure 4-30: Inbound IP Routing Table Page Figure 4-31: Outbound IP Routing Table Page Figure 4-32: Classification Rule Figure 4-33: Classification Rule Figure 4-34: IP-to-IP Routing Table Figure 4-35: IP-to-IP Routing Rule for Register Figure 4-36: IP-to-IP Routing Rule for Options Figure 4-37: IP-to-IP Routing Rule for 3xx Figure 4-38: IP-to-IP Alt Routing Rule for 3xx Figure 4-39: IP-to-IP Routing Rule for Analog Device Range Figure 4-40: IP-to-IP Routing Rule to the Gateway Figure 4-41: IP-to-IP Default Routing Rule to Lync Figure 4-42: Example Dest Number IP->Tel Number Manipulation Rule Figure 4-43: Destination Number Manipulation Rule for IP Tel Calls Figure 4-44: Destination Number Manipulation Rule for Tel IP Calls Figure 4-45: Reasons for Alternative Routing Page Figure 4-46: SIP General Parameters Page Figure 4-47: Advanced Parameters Page Figure 4-48: RTP/RTCP Settings Page Figure 4-49: IPMedia Settings Page Figure 4-50: SIP General Parameters Page (1) Version September 2013

6 Enhanced Gateway with Analog Devices Figure 4-51: SIP General Parameters Page (2) Figure 4-52: Advanced Parameters Page Figure 4-53: Reset the Device Figure A-1: Summary of Steps for Configuring the ATA Figure A-2: Endpoint Phone Number Table Page Figure A-3: Hunt Group Settings Page Figure A-4: IP to Trunk Group Routing Page Figure A-5: SIP Proxy and Registration Figure A-6: Proxy Set Table Figure A-7: Coders Table Page Figure A-8: SIP General Parameters Page Figure A-9: Configuring Gateway Name Figure B-1: Starting the Lync Server Topology Builder Figure B-2: Topology Builder Options Figure B-3: Save Topology Figure B-4: Downloaded Topology Figure B-5: Choosing New IP/PSTN Gateway Figure B-6: Define New IP/PSTN Gateway Figure B-7: Gateway entity Added as an IP/PSTN Gateway Figure B-8: Choosing New IP/PSTN Gateway Figure B-9: Define New IP/PSTN Gateway Figure B-10: SBC entity Added as an IP/PSTN Gateway Figure 4-11: Choosing Mediation Server Figure 4-12: Before Associating IP/PSTN Gateway to Mediation Server Figure B-13: Choosing Publish Topology Figure B-14: Publish Topology Screen Figure B-15: Publish Topology Progress Screen Figure B-16: Publish Topology Successfully Completed Figure B-17: Starting the Lync Server Management Shell Figure B-18: Management Shell CLI Figure B-19: View Analog Devices Information Microsoft Lync Server Document #: LTRT-40140

7 Configuration Note Notices Notice This document describes the installation and configuration of AudioCodes Mediant Gateway family as Enhanced Gateway with Analog Device deployed in the Microsoft Lync Server 2010 environment. 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 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: September 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 Documentation Feedback AudioCodes continually strives to produce high quality documentation. If you have any comments (suggestions or errors) regarding this document, please fill out the Documentation Feedback form on our Web site at Your valuable feedback is highly appreciated. Version September 2013

8 Enhanced Gateway with Analog Devices Abbreviations and Terminology The following table describes the terms used throughout this document. Term Refers To Device Enhanced Gateway Analog Telephone Adapter ATA Foreign exchange Station FXS Lync Server Microsoft Lync Server 2010 Each abbreviation, unless widely used, is spelled out in full when first used. Related Documentation Manual Name Mediant 800 Gateway and E-SBC User's Manual Mediant 1000B Gateway & E-SBC User's Manual Mediant 3000 User's Manual Mediant 800 Gateway and E-SBC Hardware Installation Manual Mediant 1000B Gateway and E-SBC Hardware Installation Manual Mediant 3000 SIP Installation Manual Microsoft Lync Server Document #: LTRT-40140

9 Configuration Note 1. Introduction 1 Introduction This document describes the installation and configuration of the AudioCodes Enhanced Gateway which is deployed in the Lync Server environment. The device consists of the following entities: Gateway entity interfaces Microsoft Lync to the Digital Trunks SBC entity interfaces Microsoft Lync to the Analog Devices The device is typically co-located with Microsoft Mediation server at the enterprise s headquarters. The Mediation server is the entity that is responsible for interfacing the Lync Server network with the gateway, which provides legacy connections to analog devices (such as fax machines and telephones) and/or the public switched telephone network (PSTN) or private branch exchange (PBX). The device also provides in the Lync Server environment, a connection to AudioCodes MediaPack 1xx series as an Analog Telephone Adapter (ATA). The ATA provides Foreign exchange Station (FXS) port interface for connecting analog devices. This document provides step-by-step instructions on how to configure the device for communication with the ATA. It also covers the ATA configuration communicating with the device. Note: This document doesn t describe how to configure analog devices that are connected directly to the Enhanced Gateway's FXS ports. The figure below shows the high-level architecture of the Enhanced Gateway with Analog Devices. Figure 1-1: High-Level Architecture of Enhanced Gateway with Analog Devices Version September 2013

10 Enhanced Gateway with Analog Devices Reader's Notes Microsoft Lync Server Document #: LTRT-40140

11 Configuration Note 2. Component Information 2 Component Information 2.1 AudioCodes Devices GW Vendor AudioCodes Models Mediant 800 Gateway & E-SBC Mediant 1000B Gateway & E-SBC Mediant 3000 Gateway & E-SBC Software Version SIP_6.60A or later Protocol PRI /BRI (to PSTN) SIP/TCP or TLS (to Lync Server) SIP/UDP or TCP (to ATA) Additional Notes None 2.2 Microsoft Lync Server 2010 Vendor Microsoft Model Microsoft Lync Software Version Release Protocol SIP Additional Notes None 2.3 AudioCodes ATA GW Vendor AudioCodes Models MediaPack MP-11x MediaPack MP-124 Software Version SIP_6.60A or later Protocol FXS (to Analog Devices) SIP/UDP or TCP (to AudioCodes device) Additional Notes None Version September 2013

12 Enhanced Gateway with Analog Devices 2.4 Deploying the Device (Topology) The procedures described in this document show how to deploy the device in the following example scenario: The enterprise deploys Lync Server in its private network for enhanced communication within the enterprise. The enterprise requests to offer its employees enterprise voice capabilities and to connect the enterprise to the PSTN network using an E1/T1 service. The enterprise requests to connect Analog Devices that interact with Lync Server for Management, Monitoring, and Security. Analog Devices are configured using the Lync Server Management Shell. The AudioCodes solution offers a single device that consists of the following entities: The Gateway entity used to manage the connection between the Lync Server and the E1/T1 trunk. The SBC entity used to manage the connection between the Lync Server and the Analog Devices via ATA (SBC entity acts as their gateway to the Lync Server): Each entity communicates separately with Lync Server 2010 Each entity is configured as a PSTN gateway on the Lync topology builder (two Trunks are also created, one for the Gateway entity and one for the SBC entity). The figure below illustrates the device entities interworking with PSTN, Lync Server 2010 and ATA: Figure 2-1: Interworking Device Entities Microsoft Lync Server Document #: LTRT-40140

13 Configuration Note 2. Component Information 2.5 Environment Setup The following describes the elements of the environment setup: Network: Microsoft Lync Server 2010 environment and ATA are located in the enterprise's Local Area Network (LAN). Signaling Transcoding: Microsoft Lync Server works with SIP over TLS transport type; ATA works with SIP over UDP transport type. Codecs Transcoding: Microsoft Lync Server 2010 and ATA support G.711A-law and G.711U-law coders. Media Transcoding: Microsoft Lync Server 2010 works with the SRTP media type, while the ATA works with the RTP media type. Note: When an Analog Phone number (From or To) call is received on the Lync Server, it routes the call to the entity that serves the Analog Phone; however, when a FAX number (From or To) call is received on Lync Server, it routes the call back to the entity that originated the call. The following table clarifies the interworking for the different Call Flow scenarios: Call Flow Scenarios Scenario Call from PSTN to Lync Client Call from PSTN to Analog Phone Call from PSTN to FAX Machine Call from FAX Machine to PSTN Call from Analog Phone to PSTN Call from Analog Phone to Lync Client Call from Lync Client to PSTN Call from Lync Client to Analog Phone Call between 2 FAX Machines Flow GW Lync Server GW Lync Server SBC ATA GW SBC Lync Server SBC ATA ATA SBC Lync Server SBC GW ATA SBC Lync Server GW ATA SBC Lync Server Lync Server GW Lync Server SBC ATA ATA SBC Lync Server SBC ATA Version September 2013

14 Enhanced Gateway with Analog Devices Reader's Notes Microsoft Lync Server Document #: LTRT-40140

15 Configuration Note 3. Accessing the Device 3 Accessing the Device The gateway includes an embedded Web server (Web interface) for device configuration, providing a user-friendly graphical user interface (GUI). Before you can configure the device, you first need to access it with the default VoIP / Management LAN IP address (as described below) and then change this address to suit the networking scheme in which your Enhanced Gateway is deployed. 3.1 Initial Access to the Device To start configuring the device, you need to first access it with the default VoIP / Management LAN IP address as shown in the table below. Figure 3-1: PSTN Gateway Default IP Addresses Device Name IP Address Subnet Mask Mediant 3000 TP-6310 or TP-8410 blade in Slot 1: TP-6310 or TP-8410 blade in Slot 3: (HA mode) Mediant 1000B Mediant To initially access the PSTN gateway: 1. Connect to the first LAN port on the device directly to a PC, using a straight-through Ethernet cable. 2. Ensure that your PC is configured with an IP address in the same subnet as the gateway. 3. Open a standard Web browser, and then in the URL address field, enter the default VoIP / Management LAN IP address (e.g., '' ''). The following login screen appears, prompting you to log in with your login credentials: Figure 3-2: Login Screen 4. Log in with the default, case-sensitive user name (''Admin'') and password (''Admin''), and then click OK; the Web interface appears, displaying the Home page. Version September 2013

16 Enhanced Gateway with Analog Devices 5. Do one of the following: a. For the Mediant 800 and Mediant 1000B devices: Open the Multiple Interface Table page (Configuration tab > VoIP menu > Network > IP Settings) and proceed to Section b. For the Mediant 3000 device: Open the IP Settings page (Configuration tab > VoIP menu > Network > IP Interfaces Table ), as shown below: Figure 3-3: IP Settings Screen (Single Network Interface) Click the Multiple Interface Table button, located under the Multiple Interface Settings group; a confirmation message box appears. Click OK; the Multiple Interface Table page appears; proceed to Section Microsoft Lync Server Document #: LTRT-40140

17 Configuration Note 3. Accessing the Device Assigning IP Address to the Device This section describes how to assign an IP address to the device. To assign an IP address to the device: 1. Select the Index radio button corresponding to the Application Type OAMP + Media + Control (i.e., the VoIP and Management LAN interface), and then click Edit. Figure 3-4: IP Settings Screen (Multiple Network Interface) 2. Configure a LAN network address that corresponds to your network IP addressing scheme. 3. Click Apply, and then click Done to apply and validate your settings. 4. On the toolbar, from the Device Actions drop-down list, choose Reset, and then in the Maintenance Actions page, click the Reset button; the gateway resets and your settings are saved to the flash memory. Figure 3-5: Maintenance Actions: Reset Gateway Maintain the cabled connection between the gateway s LAN port and the computer. Version September 2013

18 Enhanced Gateway with Analog Devices Readers Notes Microsoft Lync Server Document #: LTRT-40140

19 Configuration Note 4. Configuring the Device 4 Configuring the Device This section provides a step-by-step procedure for configuring the device for scenarios where it is used for connecting the Microsoft Lync environment to the PSTN as well for scenarios where there are Analog Devices communicating with Lync Server. The configuration steps described in this section are performed through the embedded Web server (Web interface) of the Enhanced gateway. 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 Lync Server 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 Server 2010 Version September 2013

20 Enhanced Gateway with Analog Devices The flowchart below summarizes the steps for configuring the device: Figure 4-1: Device Configuration: Summary of Steps Microsoft Lync Server Document #: LTRT-40140

21 Configuration Note 4. Configuring the Device 4.1 Step 1: Modifying IP Address to the Device This section describes how to modify the IP address of the device. To modify the existing LAN network interface: 1. Open the Multiple Interface Table page (Configuration > Network Settings > IP Settings). 2. Select the 'Index' radio button adjacent to Application Type OAMP + Media + Control and click Edit. 3. Configure like this: Figure 4-2: IP Settings Screen (Multiple Network Interface) Parameter Setting for IPv4 Application Type Interface Mode OAMP + Media + Control (application) IPv4 Manual IP Address (device IP address) Prefix Length 16 for (Subnet mask, in bits) Gateway Default Gateway VLAN ID VLAN ID 1 Interface Name Primary DNS Server IP Address Arbitrary descriptive name "Voice" DNS IP address Click Apply, and then click Done to apply and validate your settings. 5. Reset the device with a burn to flash for this setting to take effect (see Section 4.16 on page 71). Version September 2013

22 Enhanced Gateway with Analog Devices 4.2 Step 2: Enabling the SBC Application This step describes 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-3: Applications Enabling 2. From the 'SBC Application' drop-down list, select Enable. 3. Reset the device with a burn to flash for this setting to take effect (see Section 4.16 on page 71). Microsoft Lync Server Document #: LTRT-40140

23 Configuration Note 4. Configuring the Device 4.3 Step 3: Configuring SRDs This step describes how to configure Signaling Routing Domains (SRDs). An SRD is a set of definitions comprising IP interfaces, 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 SBC entity and the Gateway entity to transmit or receive media (RTP or SRTP). Media Realms are associated with SRDs or IP Groups. The simplest way is to configure one Media Realm for internal (LAN) 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 0 Media Realm Name IPv4 Interface Name Port Range Start Number of Media Session Legs MRLan (an arbitrary name) Voice (the interface name) 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-4: Configuring a LAN Media Realm c. Click Submit. Version September 2013

24 Enhanced Gateway with Analog Devices Configuring SRDs This section shows how to configure the SRDs. The simplest method for configuring SRDs is to configure a single SRD for internal (LAN) traffic as shown below, applied to the example scenario. Note that this SRD will later be associated with IP Groups. To configure the SRDs: 1. Open the SRD Table page (Configuration tab > VoIP > Control Network > SRD Table). 2. Add an SRD for the device LAN interfaces: 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-5: Configuring the LAN SRD b. Click Submit. Microsoft Lync Server Document #: LTRT-40140

25 Configuration Note 4. Configuring the Device 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, respective SIP interfaces are added for the Gateway entity and SBC entity in the device. 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 Gateway entity: a. Click Add. b. Configure these parameters: Parameter Example Setting Index 0 Network Interface Application Type UDP Port TCP Port 0 TLS Port SRD 1 c. Click Submit. Voice GW & IP2IP 3. Add a SIP interface for the SBC entity: a. Click Add. b. Configure these parameters: 5061 (listening port to the SBC entity) 5067 (listening port to Mediation Server Trunk ACGW.Acsupport.local) Parameter Example Setting Index 1 Network Interface Application Type UDP Port TCP Port 0 TLS Port SRD 1 Voice SBC c. Click Submit. The configured SIP Interface table is shown below: 5060 (listening port to the Gateway entity and the ATA) 5069 (listening port to Mediation Server Trunk ACSBC.Acsupport.local) Figure 4-6: Required SIP Interface Table Version September 2013

26 Enhanced Gateway with Analog Devices 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 an IP address or fully qualified domain name (FQDN). In the example scenario, the following four Proxy Sets are added: Microsoft Lync Server 2010 for the Gateway entity Microsoft Lync Server 2010 for the SBC entity Internal leg to be reached by the Gateway entity Internal leg to be reached by the SBC entity Note: 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 for the Gateway entity: 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 SRD Index b. Click Submit. "LyncS.Acsupport.local:5067" (Lync Mediation Server 2010 FQDN and destination port for Gateway Trunk) TLS Using Options Round Robin Yes 1 (Enables classification by Proxy Set for this SRD in the IP Group belonging to it) Microsoft Lync Server Document #: LTRT-40140

27 Configuration Note 4. Configuring the Device Figure 4-7: Proxy Set for Microsoft Lync Server 2010 (Gateway Entity) 3. Add a Proxy Set for Lync Server for the SBC entity: a. Configure these parameters: Parameter Example Setting Proxy Set ID 2 Proxy Address Transport Type Enable Proxy Keep Alive Proxy Load Balancing Method Is Proxy Hot Swap SRD Index 1 b. Click Submit. " LyncS.acsupport.local:5067" (Lync Mediation Server 2010 FQDN and destination port for SBC Trunk) TLS Using Options Round Robin Yes Version September 2013

28 Enhanced Gateway with Analog Devices 4. Add a Proxy Set for the internal leg to be reached by the Gateway entity. a. Configure these parameters: Parameter Example Setting Proxy Set ID 3 Proxy Address Transport Type SRD Index 1 b. Click Submit :5060 (this is the device IP address and the SBC entity port) UDP 5. Add a Proxy Set for the internal leg to be reached by the SBC entity. a. Configure these parameters: Parameter Example Setting Proxy Set ID 4 Proxy Address Transport Type SRD Index b. Click Submit :5061 (this is the device IP address and the GW entity port) UDP 1 (enables classification by Proxy Set for this SRD in the IP Group belonging to the SIP Trunk) Microsoft Lync Server Document #: LTRT-40140

29 Configuration Note 4. Configuring the Device 4.5 Step 5: Configuring IP Groups This step shows how to create IP Groups. An IP Group represents a SIP entity in the device s network. In the example scenario, the following IP Groups are added: Microsoft Lync Server 2010 for the Gateway entity Microsoft Lync Server 2010 for the SBC entity Internal leg to be reached by the Gateway entity Internal leg to be reached by the SBC entity Analog Devices (assigned as Users and registered to the SBC) Note: These IP Groups are later used by the device 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 for the Gateway entity: a. Click Add. b. Configure the parameters like this: Parameter Example Setting Index 1 Type Server Description Gateway- Lync (a descriptive name) Proxy Set ID 1 SRD 1 Media Realm Name MRLan IP Profile ID 0 c. Click Submit. Figure 4-8: IP Group Rule for Microsoft Lync Server 2010 (Gateway entity) d. On the SBC tab, set the parameter 'Classify By Proxy Set' to Disable. Version September 2013

30 Enhanced Gateway with Analog Devices Figure 4-9: Classify By Proxy Set (Gateway entity) 3. Add an IP Group for the Lync Server 2010 for the SBC entity: a. Click Add. b. Configure the parameters like this: Parameter Example Setting Index 2 Type Description Proxy Set ID 2 SRD 1 Media Realm Name Server SBC - Lync (a descriptive name) MRLan IP Profile ID 1 (this IP Profile is defined in Section 4.6 below). c. Click Submit. Microsoft Lync Server Document #: LTRT-40140

31 Configuration Note 4. Configuring the Device d. Select the SBC tab, and then set the parameter 'Classify By Proxy Set' to Disable. Figure 4-10: Classify by Proxy Set (SBC Entity) 4. Add an IP Group for the Internal SBC leg: a. Click Add. b. Configure the parameters like this: Parameter Example Setting Index 3 Type Description Proxy Set ID 3 SRD 1 Media Realm Name Server SBC Internal (a descriptive name) MRLan IP Profile ID 1 (this IP Profile is defined in Section 4.6 below). c. Click Submit. Version September 2013

32 Enhanced Gateway with Analog Devices 5. Add an IP Group for the Internal Gateway leg: a. Click Add. b. Configure the parameters like this: Parameter Example Setting Index 4 Type Description Proxy Set ID 4 SRD 1 Media Realm Name IP Profile ID 0 c. Click Submit. 6. Add an IP Group for the Analog Devices: a. Click Add. b. Configure the parameters like this: Server GW Internal (a descriptive name) MRLan Parameter Example Setting Index 5 Type Description SRD 1 Media Realm Name User Analog Device (a descriptive name) MRLan IP Profile ID 2 (this IP Profile is defined in Section 4.6 below). c. Click Submit. The figure below shows the configured IP Group table: Figure 4-11: Configured IP Group Table Microsoft Lync Server Document #: LTRT-40140

33 Configuration Note 4. Configuring the Device 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 and Analog Device. Note that the IP Profiles were assigned to the relevant IP Group in the previous step (see Section 4.5 on page 29). In the example scenario, two IP Profiles are added for the following entities: Microsoft Lync Server to operate in secure mode using SRTP and TLS Analog Device - 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: a. Configure the parameters like this: Parameter Example Setting Profile ID 1 Media IP Version Preference Reset SRTP State Upon Rekey Extension Coders Group ID Media Security Behavior Only IPv4 Enable Applies Extended coders Group to this Profile SRTP SBC Remote Early Media RTP Delayed (mandatory because the Lync Server 2010 does not immediately send RTP to the remote side if it sends a SIP 18x response) SBC Remote Update Support Supported Only After Connect SBC Remote Re-Invite Support Supported Only With SDP SBC Remote Refer Behavior SBC Remote 3xx Behavior SBC Remote Delayed Offer Support Handle Locally (mandatory because Lync Server 2010 does not support receive Refer) Handle Locally (mandatory because Lync Server 2010 does not support receive 3xx) Not Supported b. Click Submit. Version September 2013

34 Enhanced Gateway with Analog Devices Figure 4-12: Configured IP Profile for Lync Server 2010 Microsoft Lync Server Document #: LTRT-40140

35 Configuration Note 4. Configuring the Device 3. Add an IP Profile for the Analog device: a. Configure the parameters like this: Parameter Example Setting Profile ID 2 Media IP Version Preference Media Security Behavior b. Click Submit. Only IPv4 RTP Figure 4-13: Configured IP Profile for Analog Device Version September 2013

36 Enhanced Gateway with Analog Devices 4.7 Step 7: Configuring a SIP TLS Connection This step shows how to configure the device to use a TLS connection with the Lync 2010 Mediation Server. This step is mandatory in order to ensure a secure SIP TLS connection between the device and the Lync Server 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 device receives an 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-14: Configuring the NTP Server IP Address 3. Click Submit Configuring the DNS Server Configure the IP address of the Domain Name System (DNS) servers. This is required if the Mediation server is configured with an FQDN, in which case, the DNS is used to resolve it into an IP address. The procedure for configuring the DNS is described in Section 4.1 on page 21. Microsoft Lync Server Document #: LTRT-40140

37 Configuration Note 4. Configuring the Device Configuring a Certificate This step describes how to exchange a certificate with the Microsoft Certificate Authority (CA). The certificate is used by the device to authenticate the connection with Lync Server. In this procedure, we use SAN (Subject Alternative Names) Certificate that allows specifying a list of host names to be protected by a single SSL certificate. In the example scenario, we use two hosts for our single device: ACGW.Acsupport.local (for the Gateway entity) ACSBC.Acsupport.local (for the SBC entity) We set a virtual CN that represents these two hosts: ACGW_Cert.Acsupport.local To configure a certificate: 1. Open the Certificates page (Configuration tab > System > Certificates). Figure 4-15: Certificates Page - Creating CSR 2. In the 'Subject Name' field, enter the media gateway name (e.g., ACGW_Cert.Acsupport.local). This name must be different to the gateways configured in the Topology Builder for Lync Server 2010 (see Appendix on page 83). 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. Version September 2013

38 Enhanced Gateway with Analog Devices 5. Once you have generated a CSR (as described in the previous above), you need to upload it to Microsoft Certificate server and request a CA and trusted root certificates. Open a Web browser and navigate to the Microsoft Certificates Services Web site at the following link: server>/certsrv Figure 4-16: Microsoft Certificate Services Web Page 6. Click Request a certificate. Microsoft Lync Server Document #: LTRT-40140

39 Configuration Note 4. Configuring the Device Figure 4-17: Request a Certificate Page 7. Click advanced certificate request and click Next. Figure 4-18: Advanced Certificate Request Page 8. Click Submit a certificate request... and click Next. Version September 2013

40 Enhanced Gateway with Analog Devices Figure 4-19: 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. In the 'Additional Attributes' text box enter the 2 FQDN s (these FQDN s must be the same as the FQDN s you defined in the Topology Builder) as follows: san:dns=dns.name[&dns=dns.name] (e.g., san:dns=acgw.acsupport.local&dns=acsbc.acsupport.local) 12. Click Submit. Figure 4-20: Certificate Issued Page 13. Select the Base 64 encoded option for encoding and click Download certificate. 14. Save the file with the name gateway.cer to a folder on your computer. 15. Click the Home button (or navigate to the certificate server at Server>/CertSrv). Microsoft Lync Server Document #: LTRT-40140

41 Configuration Note 4. Configuring the Device 16. Click the Download a CA certificate, Certificate Chain, or CRL: Figure 4-21: Download a CA Certificate, Certificate Chain, or CRL 17. Under the 'Encoding method' group, select the Base 64 option for encoding. 18. Click Download CA certificate. 19. Save the file with the name certroot.cer to a folder on your computer. Version September 2013

42 Enhanced Gateway with Analog Devices 20. In the device s Web interface, return to the Certificates page and do the following: a. In the 'Device Certificate' field, click Browse and select the gateway.cer certificate file that you saved on your computer in Step 14; then click Send File to upload the certificate to the device. b. In the 'Trusted Root Certificate Store' field, click Browse and select the certroot.cer certificate file that you saved on your computer in Step 19; then click Send File to upload the certificate to the device. Figure 4-22: Certificates Page (Uploading Certificate) 21. Reset the device with a burn to flash for your settings to take effect (see Section 4.16 on page 71). Microsoft Lync Server Document #: LTRT-40140

43 Configuration Note 4. Configuring the Device 4.8 Step 8: Configuring SRTP This step describes how to configure media security. If you configure the Microsoft Mediation Server to use Secure Real-Time Transport Protocol (SRTP), then you must also configure the device to do so as well. Note that SRTP was enabled for Lync Server when you added and configured an IP Profile for Lync Server (see Section 4.6 on page 33). To configure media security: 1. Open the Media Security page (Configuration tab > VoIP > Media > Media Security). Figure 4-23: Media Security Page 2. Configure the parameters like this: Parameter Example Setting Media Security Master Key Identifier (MKI) Size 1 Symmetric MKI Negotiation 3. Click Submit. Enable Enable 4. Reset the device with a burn to flash for your settings to take effect (see Section 4.16 on page 71). Version September 2013

44 Enhanced Gateway with Analog Devices 4.9 Step 9: 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 SBC entity 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-24: 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. 4. Reset the device with a burn to flash for this setting to take effect (see Section 4.16 on page 71). Microsoft Lync Server Document #: LTRT-40140

45 Configuration Note 4. Configuring the Device 4.10 Step 10: Configuring Voice Coders The device communicates with the Mediation server using either the G.711 A-law or G.711 µ-law (Mu-Law) voice coder. In addition, silence suppression can be enabled per coder, which is recommended for improving the performance with the Mediation server. The procedure below shows how you can change the default coder. To configure the voice coder and silence suppression: 1. Open the Coders page (Configuration tab > VoIP menu > Coders And Profiles > Coders). Figure 4-25: Coders Table Page 2. From the 'Coder Name' drop-down list, select the required coder. 3. From the 'Silence Suppression' drop-down list, select Enable. 4. Click Submit. Note: The Coder Table above represent Coder Group ID 0, to apply it in SBC entity you need to assign it in the corresponding IP Profile (see Section 4.6 on page 33). Version September 2013

46 Enhanced Gateway with Analog Devices 4.11 Step 11: Configuring PSTN Trunks This section describes how to configure PRI (i.e., E1/T1) or BRI trunks connected to the Enhanced gateway. The following procedures are described: Enabling Trunks. See Section on page 46. Configuring the Channel Select Method. See Section on page 47. Configuring the Trunk. See Section on page 48. Configuring the TDM Bus. See Section on page Enabling Trunks To enable trunks, you need to assign them to Trunk Groups, as described below. To enable trunks: 1. Open the Trunk Group Table page (Configuration tab > VoIP menu > GW and IP to IP > Trunk Group > Trunk Group). Figure 4-26: Trunk Group Table Page 2. In the 'Module' column, select the module number and type (e.g., PRI) on which the trunks are located. 3. In the From Trunk' and 'To Trunk' columns, select the physical trunk range. 4. In the Channel(s) column, enter the B-channels (e.g., 1-31) that you wish to enable. 5. In the 'Phone Number' column, enter the phone number (e.g., 1000) for the first channel; phone numbers 1001, 1002, 1003, and so on are sequentially assigned to subsequent channels. Note that these numbers are used internally. 6. In the 'Trunk Group ID' column, enter the ID for the Trunk Group. 7. Click Submit to apply your changes. Microsoft Lync Server Document #: LTRT-40140

47 Configuration Note 4. Configuring the Device Configuring the Channel Select Method Once you have enabled the trunks and assigned them to Trunk Groups, you need to configure the method to which IP-to-Tel calls are assigned to channels within the Trunk Group. To configure the channel select mode: 1. Open the Trunk Group Settings page (Configuration tab > VoIP menu > GW and IP to IP > Trunk Group > Trunk Group Settings). Figure 4-27: Trunk Group Settings Page 2. In the Trunk Group ID column, enter the Trunk Group ID that you want to configure. 3. From the 'Channel Select Mode' drop-down list, select the method for which IP-to-Tel calls are assigned to channels pertaining to the Trunk Group (i.e. Cyclic Ascending). 4. From the 'Registration Mode' drop-down list, select Don t Register. 5. Click Submit to apply your changes. Version September 2013

48 Enhanced Gateway with Analog Devices Configuring the Trunk The procedure below describes the basic configuration of the physical trunk. To configure the physical trunk: 1. Open the Trunk Settings page (Configuration tab > VoIP menu > PSTN > Trunk Settings). Figure 4-28: Trunk Settings Page 2. On the top of the page, a bar with trunk number icons displays the status of each trunk: Grey - disabled Green - active Yellow - RAI alarm Red - LOS / LOF alarm Blue - AIS alarm Orange - D-channel alarm (ISDN only) Select the Trunk that you want to configure, by clicking the desired trunk number icon. 3. If the trunk is new, configure the trunk as required. If the trunk was previously configured, click the Stop Trunk button to de-activate the trunk. Microsoft Lync Server Document #: LTRT-40140

49 Configuration Note 4. Configuring the Device 4. Basic trunk configuration: a. From the Protocol Type drop-down list, select the required trunk protocol. Notes: If the Protocol Type field displays 'NONE' (i.e., no protocol type selected) and no other trunks have been configured, after selecting a PRI protocol type, you must reset the Enhanced gateway. All PRI trunks of the Enhanced gateway must be of the same line type - E1 or T1. However, different variants of the same line type can be configured on different trunks, for example, E1 Euro ISDN and E1 CAS (subject to the constraints in the Release Notes). BRI trunks can operate with E1 or T1 trunks. If the trunk can t be stopped because it provides the clock (assuming the Enhanced gateway is synchronized with the E1/T1 clock), assign a different E1/T1 trunk to provide the clock or enable 'TDM Bus PSTN Auto Clock' in the 'TDM Bus Settings' page (see Section ). To delete a previously configured trunk, set the parameter 'Protocol Type' to 'None'. b. From the 'Clock Master' drop-down list, select the trunk's clock source: Recovered: clock source is recovered from the trunk. Generated: clock source is provided by the internal TDM bus clock source (according to the parameter 'TDM Bus Clock Source' see Section on page 50). c. From the 'Line Code' drop-down list, select the line code: B8ZS (bipolar 8-zero substitution) for T1 trunks only HDB3 (high-density bipolar 3) for E1 trunks only AMI (for E1 and T1) d. From the 'Framing Method' drop-down list, select the required framing method. For E1 trunks always set this parameter to Extended Super Frame. e. To configure whether the trunk connected to the PBX is 'User' or 'Network' side, from the 'ISDN Termination' drop-down list, select User side or Network side. 5. Continue configuring the trunk according to your requirements. 6. When you have completed the configuration, click the Apply Trunk Settings button to apply the changes to the selected trunk. 7. On the toolbar, click Burn to save the changes to the Enhanced gateway flash memory. 8. Reset the device with a burn to flash for this setting to take effect (see Section 4.16 on page 71). Version September 2013

50 Enhanced Gateway with Analog Devices Configuring the TDM Bus The procedure below describes how to configure the TDM bus of the Enhanced gateway. To configure the TDM bus: 1. Open the TDM Bus Settings page (Configuration tab > VoIP menu > TDM > TDM Bus Settings). Figure 4-29: TDM Bus Settings Page 2. Configure the TDM bus parameters according to your deployment requirements. Below is a description of some of the main TDM parameters: a. PCM Law Select: defines the type of PCM companding law in the input/output TDM bus. Typically, A-Law is used for E1 and Mu-Law for T1/J1. b. TDM Bus Clock Source: defines the clock source to which the Enhanced gateway synchronizes - generate clock from local source (Internal) or recover clock from PSTN line (Network). c. TDM Bus Local Reference: defines the physical trunk ID from which the Enhanced gateway recovers (receives) its clock synchronization when the TDM Bus Clock Source is configured to recover the clock from the PSTN line. 3. Click Submit to apply your changes. 4. On the toolbar, click Burn to save the settings to the Enhanced gateway flash memory. 5. Reset the device with a burn to flash for this setting to take effect (see Section 4.16 on page 71). Microsoft Lync Server Document #: LTRT-40140

51 Configuration Note 4. Configuring the Device 4.12 Step 12: Configuring Enhanced Gateway Routing The procedure below describes how to route calls between the IP side (i.e., Lync Server and SBC entity) to the Trunk Side (e.g., PRI) in the Gateway entity Configuring IP-to-Trunk Group Routing The procedure below describes how to configure an IP-to-Trunk Group routing rule, whereby all incoming calls (i.e., from Mediation server or SBC entity) are routed to Trunk Group 1 (which was configured in Section on page 46). To configure an IP-to-Trunk Group routing rule: 1. Open the Inbound IP Routing Table page (Configuration tab > VoIP menu > GW and IP to IP > Routing > IP to Trunk Group Routing). Figure 4-30: Inbound IP Routing Table Page 2. In the first table entry row, enter the asterisk (*) sign in the 'Dest. Phone Prefix' and in the 'Source Phone Prefix' fields. 3. In the 'Trunk Group ID' field, enter the Trunk Group to where the calls must be routed. 4. Click Submit to apply your changes. Version September 2013

52 Enhanced Gateway with Analog Devices Configuring Tel-to-IP Routing The procedure below describes how to configure a Tel-to-IP routing rule whereby all calls from the Trunk Group 1 (i.e., PSTN) are routed to the Mediation server or to the SBC entity upon the destination number. To configure a Tel-to-IP Group routing rule: 1. Open the Outbound IP Routing Table page (Configuration tab > VoIP menu > GW and IP to IP > Routing > Tel to IP Routing). Figure 4-31: Outbound IP Routing Table Page 2. From the 'Tel To IP Routing Mode' drop-down list, select Route calls after manipulation. 3. Calls from Source Trunk Group ID 1 with Dest. Phone Prefix of the Analog Devices FAX type (e.g., ) will be send to Dest. IPGroup ID 3 (i.e., to SBC) and Dest. SRD 1 (i.e., internal SRD). 4. All other Calls from Source Trunk Group ID '1' will be send to 'Dest. IPGroup ID' 1 (i.e., to Lync Mediation Server). 5. Click Submit to apply your changes. Microsoft Lync Server Document #: LTRT-40140

53 Configuration Note 4. Configuring the Device 4.13 Step 13: Configuring SBC Classification and Routing The procedures below describe how to classify and route between the Different IP s Identities (i.e., Lync Server, Gateway entity, Analog device) in the SBC entity Configuring Classification Rules This procedure describes how to configure Classification rules. Classification rules are used to classify incoming SIP dialog-initiating requests (e.g., SIP INVITE messages) to source IP Groups, from where the SIP dialog request originated. In the example scenario, classification rules are added for classifying the Analog device users. In the example below, the classification is according to the Source Host name. Note that this host name must also be configured on the ATA device (see Section A.8 on page 81). To add classification rules: 1. Open the Classification table page (Configuration > VoIP > SBC > Routing SBC > Classification Table). 2. Add a rule to match Analog devices to the Source Host to IP Group: a. Click Add. b. Configure the parameters as follows: Parameter Settings Index 0 Source Host analog.com Source IP Group ID 5 c. Click Submit. Figure 4-32: Classification Rule Version September 2013

54 Enhanced Gateway with Analog Devices 3. Add a rule to match Lync server (SBC entity) Destination Host to IP Group: a. Click Add. b. Configure the parameters as follows: Parameter Settings Index 1 Destination Host Source IP Group ID 2 c. Click Submit. Figure 4-33: Classification Rule ACSBC.Acsupport.local (SBC entity as configure on the Lync server) Microsoft Lync Server Document #: LTRT-40140

55 Configuration Note 4. Configuring the Device Configuring IP-to-IP Call Routing Rules This step describes how to configure IP-to-IP call routing rules. 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 our example scenario, you need to add the following IP-to-IP routing rules to route calls between the Different IP Groups: Terminate SIP Registration messages received from the ATA Terminate SIP OPTIONS messages received from the Lync Server Route SIP 3xx messages (forward) towards the Analog device users Alternative route SIP 3xx messages (Forward) towards the Lync Route calls from Lync to Analog device number range towards the ATA Route all other calls from Lync to Gateway (PSTN) IP Group Default route calls towards Lync The routing rules use IP Groups to denote the source and destination of the call. As configured in Section 4.5 on page 29: IP Group ID 2 assigned to Lync Server 2010, IP Group ID 3 is assigned to Gateway entity, and IP Group ID 5 is assigned to Analog device users. The figure below shows the configured routing rules (representing the configuration in this section) in the IP-to-IP Routing Table: Figure 4-34: IP-to-IP Routing Table Note: The routing configuration may change according to the local deployment topology. Version September 2013

56 Enhanced Gateway with Analog Devices To add IP-to-IP routing rules: 1. Open the IP2IP Routing Table page (Configuration > VoIP > SBC > Routing SBC > IP to IP Routing Table). 2. Add a rule to terminate SIP Registration messages received from the ATA: a. Click Add. b. Configure the parameters as follows: Parameter Settings Index 0 Source IP Group ID 5 Request Type REGISTER Destination Type IP Group Destination IP Group ID 5 c. Click Submit. Figure 4-35: IP-to-IP Routing Rule for Register Microsoft Lync Server Document #: LTRT-40140

57 Configuration Note 4. Configuring the Device 3. Add a rule to terminate SIP OPTIONS messages received from the Lync Server: a. Click Add. b. Configure the parameters as follows: Parameter Settings Index 1 Source IP Group ID 2 Request Type Destination Type Destination Address c. Click Submit. OPTIONS Dest Address internal Figure 4-36: IP-to-IP Routing Rule for Options Version September 2013

58 Enhanced Gateway with Analog Devices 4. Add a rule to route SIP 3xx messages (forward) towards the analog device: a. Click Add. b. Configure the parameters as follows: Parameter Settings Index 2 Source IP Group ID -1 Destination Type IP Group Call Trigger 3xx Destination IP Group ID 5 c. Click Submit. Figure 4-37: IP-to-IP Routing Rule for 3xx Microsoft Lync Server Document #: LTRT-40140

59 Configuration Note 4. Configuring the Device 5. Add a rule to alternative route SIP 3xx messages towards the Lync Server: a. Click Add. b. Configure the parameters as follows: Parameter Settings Index 3 Source IP Group ID -1 Destination Type IP Group Call Trigger 3xx Destination IP Group ID 2 Alternative Route Options Alt Route Ignore Inputs c. Click Submit. Figure 4-38: IP-to-IP Alt Routing Rule for 3xx Version September 2013

60 Enhanced Gateway with Analog Devices 6. Add a rule to route calls from Lync Server to Analog device number range towards the ATA : a. Click Add. b. Configure the parameters as follows: Parameter Settings Index 4 Source IP Group ID 2 Destination Username Prefix [4-5] Destination Type IP Group Destination IP Group ID 5 c. Click Submit. Figure 4-39: IP-to-IP Routing Rule for Analog Device Range Microsoft Lync Server Document #: LTRT-40140

61 Configuration Note 4. Configuring the Device 7. Add a rule to route any other number from Lync to Gateway s IP Group (PSTN) a. Click Add. b. Configure the parameters as follows: Parameter Settings Index 5 Source IP Group ID 2 Destination Type IP Group Destination IP Group ID 4 c. Click Submit. Figure 4-40: IP-to-IP Routing Rule to the Gateway Version September 2013

62 Enhanced Gateway with Analog Devices 8. Add a rule to default route calls towards the Lync Server: a. Click Add. b. Configure the parameters as follows: Parameter Settings Index 6 Source IP Group ID -1 Destination Type IP Group Destination IP Group ID 2 c. Click Submit. Figure 4-41: IP-to-IP Default Routing Rule to Lync Microsoft Lync Server Document #: LTRT-40140

63 Configuration Note 4. Configuring the Device 4.14 Step 14: Configuring Normalization Rules for E.164 Format for PBX/PSTN Connectivity Microsoft Lync 2010 implements the standard E.164 format, while the PBX or PSTN implements other number formats for dialing. If the Enhanced gateway is connected to a PBX or directly to the PSTN, the Enhanced gateway may need to perform number manipulations for the called and/or calling number to match the PBX or PSTN dialing rules or to match Microsoft Lync 2010 E.164 format. Therefore, the gateway entity must be configured with manipulation rules to translate (i.e., normalize) numbers dialed in standard E.164 format to various formats, and vice versa. Manipulation needs to be done for outbound calls (i.e., calls received from Microsoft Lync clients through Microsoft Lync 2010) and inbound calls (i.e., calls destined to Lync clients). Number manipulation (and mapping of NPI/TON to SIP messages) rules are configured in the following Manipulation tables: For Tel-to-IP calls: Destination Phone Number Manipulation Table for Tel-to-IP Calls Source Phone Number Manipulation Table for Tel-to-IP Calls For IP-to-Tel calls: Destination Phone Number Manipulation Table for IP-to-Tel Calls Source Phone Number Manipulation Table for IP-to-Tel Calls Number manipulation configuration examples are provided for inbound and outbound calls in Section To configure number manipulation rules: 1. Open the required Number Manipulation page (Configuration tab > VoIP menu > GW and IP to IP submenu > Manipulations > Dest Number IP->Tel or Dest Number Tel->IP or Source Number IP->Tel or Source Number Tel->IP); the relevant Manipulation table page is displayed. 2. Click the Add button; the following dialog box appears: Figure 4-42: Example Dest Number IP->Tel Number Manipulation Rule 3. Click the Rule tab, and then configure the matching characteristics. 4. Click the Action tab, and then configure the manipulation operation. 5. Click Submit to apply your changes. Version September 2013

64 Enhanced Gateway with Analog Devices Number Manipulation Examples This section describes two examples for number manipulation Example Number Manipulation IP to Tel The example below provides an example of configuring a manipulation rule that remove the plus sign ("+") to the destination number when the destination number prefix is a plus sign ("+"). Figure 4-43: Destination Number Manipulation Rule for IP Tel Calls Example Number Manipulation Tel to IP The example below provides an example of configuring a manipulation rule that adds the plus sign ("+") to the destination number, when the destination number prefix is any number ("*"). Figure 4-44: Destination Number Manipulation Rule for Tel IP Calls Note: Adapt the manipulation table according to you environment dial plan. Microsoft Lync Server Document #: LTRT-40140

65 Configuration Note 4. Configuring the Device 4.15 Step 15: Miscellaneous Configuration This step describes miscellaneous configuration for the Gateway entity Configuring Alternative Routing When the Enhanced gateway receives a SIP 503 response from the Mediation server in response to an INVITE, it re-sends the INVITE to the redundant Mediation server (located at the datacenter). To achieve this, you need to configure the receipt of a SIP 503 response as a reason for IP alternative routing. To configure alternative routing: 1. Open the Reasons for Alternative Routing page (Configuration tab > VoIP menu > GW and IP to IP > Routing > Alternative Routing Reasons). Figure 4-45: Reasons for Alternative Routing Page 2. Under the Tel to IP Reasons group, from the 'Reason 1' drop-down list, select Click Submit. 4. Open the SIP General Parameters page (Configuration tab > VoIP menu > SIP Definitions > General Parameters). Figure 4-46: SIP General Parameters Page Version September 2013

66 Enhanced Gateway with Analog Devices 5. In the 'Fake Retry After' field, enter the time '60' (in seconds). When the Enhanced gateway receives a SIP 503 response (from the Mediation server) without a Retry-After header, the Enhanced gateway behaves as if the 503 response includes a Retry-After header with this user-defined period. 6. Click Submit Restricting Communication to Mediation Server Only The procedure below describes how to restrict IP communication, by allowing communication only between the Enhanced gateway and the Mediation server. This ensures that the Enhanced gateway accepts and sends SIP calls only from and to the Mediation server (as required by Microsoft). This is done by enabling the IP Security feature and then defining the allowed ( administrative list) IP addresses (or FQDNs) in the Proxy Set table. To allow IP communication only between the Enhanced gateway and Mediation server: 1. Open the Advanced Parameters page (Configuration tab > VoIP menu > SIP Definitions > Advanced Parameters). Figure 4-47: Advanced Parameters Page 2. From the 'IP Security' drop-down list, select Secure Incoming calls to enable the security feature to accept and send SIP calls only from and to user-defined IP addresses or FQDN (i.e., Mediation server) configured in the Proxy Set table (see Section 4.4 on page 26). 3. Click Submit to apply your settings. Microsoft Lync Server Document #: LTRT-40140

67 Configuration Note 4. Configuring the Device Configuring Comfort Noise and Gain Control The Microsoft Lync network provides high voice quality by implementing 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 configure the Enhanced gateway to match these voice quality features, by enabling silence suppression, comfort noise generation, automatic gain control (AGC), and echo canceller (enabled by default). Note: Silence suppression is configured per coder type, as described in Step 10 (Section 4.10 on page 45). To configure voice quality: 1. Open the RTP/RTCP Settings page (Configuration tab > VoIP menu > Media > RTP/RTCP Settings). Figure 4-48: RTP/RTCP Settings Page 2. From the 'Enable RFC 3389 CN payload Type' drop-down list, select Enable. 3. From the 'Comfort Noise Generation Negotiation' drop-down list, select Enable to enable comfort noise generation. 4. Click Submit. 5. Open the IPMedia Settings page (Configuration tab > VoIP menu > Media > IPMedia Settings). Version September 2013

68 Enhanced Gateway with Analog Devices Figure 4-49: IPMedia Settings Page 6. From the 'IPMedia Detectors' drop-down list, select Enable. 7. From the 'Enable AGC' drop-down list, select Enable. 8. Click Submit to apply your changes. 9. Reset the device with a burn to flash for this setting to take effect (see Section 4.16 on page 71) Configuring Early Media Early media refers to audio and video that is exchanged before a call is accepted by the recipient. Early media generated by the caller includes voice commands or dual-tone multi frequency (DTMF) tones to activate interactive voice response (IVR) systems. Early media generated by the call recipient include ringback tones, announcements, and requests for input. Enhanced early media support in Microsoft Lync 2010 enables a caller to hear a ringback tone generated by the call recipient s mobile phone. This is also the case in team-call scenarios, where a call is routed to two team members, one of whom has configured simultaneous ringing for his or her mobile phone. According to Microsoft Lync 2010 requirements, Enhanced gateway must send a SIP 183 with SDP immediately after it receives an INVITE. The RTP packets however, will not be sent until the Enhanced gateway receives an ISDN Progress, Alerting and Progress Indicator or Connect message. For example, if the Enhanced gateway receives ISDN Progress, it starts sending RTP packets according to initial negotiation, but there is no need to re-send the 183 response. You may need to configure the Enhanced gateway's early media feature to support Microsoft Lync 2010 enhanced early media feature. Microsoft Lync Server Document #: LTRT-40140

69 Configuration Note 4. Configuring the Device To configure the Early Media feature: 1. Open the SIP General Parameters page (Configuration tab > VoIP menu > SIP Definitions > SIP General Parameters). Figure 4-50: SIP General Parameters Page (1) 2. From the 'Enable Early Media' drop-down list, select Enable. Figure 4-51: SIP General Parameters Page (2) Version September 2013

70 Enhanced Gateway with Analog Devices 3. From the 'Play Ringback Tone to Tel' drop-down list, select Play Local Until Remote Media Arrive. 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 Enhanced gateway plays a local ringback tone if there are no prior received RTP packets. The Enhanced gateway stops playing the local ringback tone as soon as it starts receiving RTP packets. At this stage, if the Enhanced gateway receives additional 18x responses, it does not resume playing the local ringback tone. 4. From the 'Forking Handling Mode' drop-down list, select Sequential handling. If an 18x response with SDP is received, the device opens a voice stream according to the received SDP. The device re-opens the stream according to subsequently received 18x responses with SDP. 5. Click Submit to apply your changes. 6. Open the Advanced Parameters page (Configuration tab > VoIP menu > SIP Definitions > Advanced Parameters). Figure 4-52: Advanced Parameters Page 7. From the 'Enable Early 183' drop-down list, select Enable. 8. Click Submit to apply your changes. Microsoft Lync Server Document #: LTRT-40140

71 Configuration Note 4. Configuring the Device 4.16 Step 16: Resetting the Device After you have completed the device configuration as described in the steps above, burn the configuration to the device s flash memory and reset it. To reset the device: 1. Open the Maintenance Actions page (Maintenance tab > Maintenance menu > Maintenance Actions). 2. Under the 'Save Configuration' group, click the BURN button; a confirmation message appears when the configuration successfully saves. 3. Click the Reset button to reset the device. Figure 4-53: Reset the Device Note: Reset with BURN to FLASH is required. Version September 2013

72 Enhanced Gateway with Analog Devices Readers Notes Microsoft Lync Server Document #: LTRT-40140

73 Configuration Note A. Configuring AudioCodes Analog Telephone Adapters (ATA) A Configuring AudioCodes Analog Telephone Adapters (ATA) This section describes how to configure the analog telephone adapter (ATA) device. This configuration ensures that the ATA routes its calls to the AudioCodes Enhanced gateway. This section assumes that the ATA device is an AudioCodes MP-1xx series device. For any other non-audiocodes ATA devices, refer to the relevant vendor s instructions. The steps for configuring the ATA are summarized in the flowchart below: Figure A-1: Summary of Steps for Configuring the ATA Version September 2013

74 Enhanced Gateway with Analog Devices A.1 Configuring the FXS Endpoints The procedure below describes how to activate the MP-1xx ports (endpoints). This is done by configuring the endpoints with telephone numbers. The configuration below uses the example of one ATA (IP address ) with analog numbers and To configure endpoints: 1. Open the Endpoint Phone Number Table page (Configuration tab > VoIP menu > GW and IP to IP > Hunt Group > Endpoint Phone Number). Figure A-2: Endpoint Phone Number Table Page 2. In the 'Phone number' field, enter the phone number of the FXS endpoint (e.g., and ). 3. Click Submit to apply your settings. Microsoft Lync Server Document #: LTRT-40140

75 Configuration Note A. Configuring AudioCodes Analog Telephone Adapters (ATA) A.2 Configuring Trunk Group Settings This section describes how to configure the trunk group settings. To configure trunk group settings: 1. Open the Trunk Group Settings page (Configuration tab > VoIP menu > GW and IP to IP > Hunt Group sub-menu > Hunt Group Settings). Figure A-3: Hunt Group Settings Page 2. In the 'Trunk Group ID' field, type In the 'Channel Select Mode' drop-down list, select By Dest Phone Number. 4. In the Registration Mode' drop-down list, select Per Endpoint. 5. Click Submit to apply your settings. Version September 2013

76 Enhanced Gateway with Analog Devices A.3 Configuring IP To Trunk Group Routing This section describes how to configure IP to Trunk Group Routing. To configure IP To Trunk Group Routing: 1. Open the IP to Hunt Group Routing Table page (Configuration tab > VoIP menu > GW and IP to IP > Routing > IP to Trunk Group Routing). Figure A-4: IP to Trunk Group Routing Page 2. In the Trunk Group ID field, enter In the Source Phone Prefix and Dest Phone Prefix and Source IP address enter * (asterisk). 4. In the IP Profile ID field, enter In the Source IP Group ID field, enter Click Submit to apply your settings. Microsoft Lync Server Document #: LTRT-40140

77 Configuration Note A. Configuring AudioCodes Analog Telephone Adapters (ATA) A.4 Configuring Proxy & Registrations This section describes how to configure Proxy & Registrations. To configure Proxy & Registrations: 1. Open the Proxy & Registration page (Configuration tab > VoIP menu > SIP Definitions > Proxy & Registration). Figure A-5: SIP Proxy and Registration 2. In the 'Use Default Proxy' field, type Yes. 3. In the 'Enable registration' field, select Enable. 4. Click Submit to apply your settings. Version September 2013

78 Enhanced Gateway with Analog Devices A.5 Configuring Proxy Set This section describes how to configure Proxy Sets. To configure Proxy Sets: 1. Open the Proxy Sets Table page (Configuration tab > VoIP menu > Control Network> Proxy Sets Table). Figure A-6: Proxy Set Table 2. In the 'Proxy-Address' field, enter the FQDN and Destination Port of the device (the SBC entity). 3. In the 'Transport Type' field drop-down list, select UDP. 4. Click Submit to apply your settings. Microsoft Lync Server Document #: LTRT-40140

79 Configuration Note A. Configuring AudioCodes Analog Telephone Adapters (ATA) A.6 Configuring Coders The procedure below describes how to configure the coders for the MP-11x device. To configure MP-11x coders: 1. Open the Coders page (Configuration tab > VoIP menu > Coders And Profiles submenu > Coders). Figure A-7: Coders Table Page 2. From the Coders Table, select via the drop-down list, coder and attributes in the manner of preference with the first entry the preferred entry, and all others following in descending order. 3. From the 'Coder Name' drop-down list, select the G.711A-law coder, as shown in the figure above. 4. From 'Silence Suppression' drop-down list, select Disabled as shown in the figure above. 5. From the 'Coder Name' drop-down list, select the G.711U-law coder, as shown in the figure above. 6. From 'Silence Suppression' drop-down list, select Disabled as shown in the figure above. 7. Click Submit to apply your settings. Version September 2013

80 Enhanced Gateway with Analog Devices A.7 Configuring SIP UDP Transport Type and Fax Signaling Method The procedure below describes how to configure the fax signaling method for the MP-11x device. To configure the fax signaling method: 1. Open the SIP General Parameters page (Configuration tab > VoIP menu > SIP Definitions > General Parameters). Figure A-8: SIP General Parameters Page 2. From the 'Fax Signaling Method' drop-down list, verify that this parameter is set to No Fax. 3. From the 'SIP Transport Type' drop-down list, verify that this parameter is set to UDP. 4. In the 'SIP UDP Local Port' field, verify that this parameter is set to In the 'SIP Destination Port' field, verify that this parameter is set to 5060 corresponding to the UDP listening port of the device (the SBC entity). 6. Click Submit to apply your settings. Microsoft Lync Server Document #: LTRT-40140

81 Configuration Note A. Configuring AudioCodes Analog Telephone Adapters (ATA) A.8 Configuring Gateway Name The device needs to recognize the incoming calls from the analog device. To do this, the ATA must send the INVITE s with the host name as configured in the SBC Classification table. Therefore, you need to configure the ATA with a gateway name corresponding to the name configured in the device Classification table (see Section 4.13 on page 53). To configure the gateway name: 1. Open the Proxy & Registration page (Configuration tab > VoIP menu > SIP Definitions > Proxy & Registration). Figure A-9: Configuring Gateway Name 2. In the 'Gateway Name' field, enter identifying name (e.g., analog.com). 3. Click Submit to apply your settings. Version September 2013

82 Enhanced Gateway with Analog Devices Reader's Notes Microsoft Lync Server Document #: LTRT-40140

83 Configuration Note B. Configuring Lync Server 2010 B Configuring Lync Server 2010 This appendix describes how to configure Microsoft Lync Server 2010 topology builder to operate with AudioCodes device s entities. It also describes how to configure the Analog device via the Lync Management Shell. Note: Routes, Dial plans, voice policies, and PSTN usages are also necessary for Enterprise voice deployment; however, they are beyond the scope of this document. B.1 Configuring the Device as an IP / PSTN Gateway The procedure below describes how to configure the device as an IP / PSTN Gateway. You need to configure the following entities: Gateway entity ACGW.Acsupport.local SBC entity ACSBC.Acsupport.local B.1.1 Configuring the Gateway Entity This section describes how to configure the gateway entity as an IP/PSTN gateway and to associate it with the Mediation Server. To configure the Gateway entity as an IP/PSTN Gateway and associate it with the Mediation Server: 1. On the server where the Topology Builder is installed, start the Lync Server 2010 Topology Builder (point to Windows Start menu, click All Programs, and then click Lync Server Topology Builder). Figure B-1: Starting the Lync Server Topology Builder Version September 2013

84 Enhanced Gateway with Analog Devices The following screen is displayed: Figure B-2: Topology Builder Options 2. Select the Download Topology from existing deployment option, and then click OK; you are prompted to save the downloaded topology: Figure B-3: Save Topology 3. Enter a name for the Topology file, and then click Save. This step enables you to roll back from any changes you make during the installation. Microsoft Lync Server Document #: LTRT-40140

85 Configuration Note B. Configuring Lync Server 2010 The Topology Builder screen with the downloaded Topology is displayed: Figure B-4: Downloaded Topology 4. In the Navigation tree, select Lync Server 2010 > Site name i.e. AudioCodes > Shared Components > PSTN Gateways. 5. Right-click the PSTN gateways folder, and then in the pop-up dialog, choose New IP/PSTN Gateway as shown below: Figure B-5: Choosing New IP/PSTN Gateway Version September 2013

86 Enhanced Gateway with Analog Devices The following dialog box appears: Figure B-6: Define New IP/PSTN Gateway 6. Enter the Fully Qualified Domain Name (FQDN) of the Gateway (i.e., "ACGW.Acsupport.local"), this FQDN should be updated in the relevant DNS record, and then click OK. The Gateway is added as a PSTN Gateway as shown below: Figure B-7: Gateway entity Added as an IP/PSTN Gateway Microsoft Lync Server Document #: LTRT-40140

87 Configuration Note B. Configuring Lync Server 2010 B.1.2 Configuring the SBC Entity This section describes how to configure the SBC entity as an IP/PSTN gateway and to associate it with the Mediation Server. To configure the SBC entity as an IP/PSTN Gateway and associate it with the Mediation Server: 1. Right-click the PSTN gateways folder, and then in the pop-up dialog, choose New IP/PSTN Gateway as shown below: Figure B-8: Choosing New IP/PSTN Gateway Version September 2013

88 Enhanced Gateway with Analog Devices The following dialog box appears: Figure B-9: Define New IP/PSTN Gateway 2. Enter the Fully Qualified Domain Name (FQDN) of the Gateway (i.e., "ACSBC.Acsupport.local"). This FQDN should be updated in the relevant DNS record. 3. Change the IP/PSTN Gateway listening port to 5069, and then click OK. Figure B-10: SBC entity Added as an IP/PSTN Gateway Microsoft Lync Server Document #: LTRT-40140

89 Configuration Note B. Configuring Lync Server 2010 B.2 Associating IP / PSTN Gateways with Mediation Server The procedure below describes how to associate the IP / PSTN Gateway with the Mediation Server. To associate IP / PSTN Gateway with the Mediation Server: 1. In the Navigation tree, right-click the Mediation Server that uses the E-SBC (e.g., LyncS.Acsupport.local), and then choose Edit Properties as shown below: Figure 4-11: Choosing Mediation Server Version September 2013

90 Enhanced Gateway with Analog Devices The following screen is displayed: Figure 4-12: Before Associating IP/PSTN Gateway to Mediation Server 2. In the left pane, choose PSTN gateway to open the Mediation Server PSTN gateway pane, and then do the following: a. In the list of gateways that are not associated with the Mediation Server, select both Gateways. b. Click Add to associate it with the Mediation Server. Microsoft Lync Server Document #: LTRT-40140

91 Configuration Note B. Configuring Lync Server In the Navigation tree, select the root item Lync Server, and then in the main menu, choose Action > Publish Topology as shown below: Figure B-13: Choosing Publish Topology Version September 2013

92 Enhanced Gateway with Analog Devices The Publish Topology screen is displayed: Figure B-14: Publish Topology Screen 4. Click Next; the Topology Builder starts to publish your topology, as shown below: Figure B-15: Publish Topology Progress Screen Microsoft Lync Server Document #: LTRT-40140

93 Configuration Note B. Configuring Lync Server Wait until the publishing topology process completes successfully, as shown below: Figure B-16: Publish Topology Successfully Completed 6. Click Finish. Version September 2013

94 Enhanced Gateway with Analog Devices B.3 Configuring Analog Device on the Lync Server Management Shell Lync Server provides support for analog devices. In this configuration, the supported analog devices are analog audio phones and analog fax machines. You can configure the qualified gateways to support the use of analog devices in a Lync Server environment. After you do this, analog devices use Lync Server to make and receive calls, and Lync Server makes routing decisions and logs calls in call detail records (CDRs) for analog devices as it does for any other managed device. To configure Analog Device and Associate it with the device: 1. On the Lync server 2010, start the Lync Server Management Shell (point to the Windows Start menu, click All Programs, and then click Lync Server Management Shell). Figure B-17: Starting the Lync Server Management Shell Microsoft Lync Server Document #: LTRT-40140

95 Configuration Note B. Configuring Lync Server 2010 The following screen is displayed: Figure B-18: Management Shell CLI 2. To create a new instance of an analog device that you can manage with Lync Server, use the New-CsAnalogDevice cmdlet. 3. Below are two examples for the Analog Device (FAX and Analog Phone): New-CsAnalogDevice -LineUri tel: DisplayName "Floor3-FAX" RegistrarPool LyncS.Acsupport.local -AnalogFax $True -Gateway ACSBC.Acsupport.local -OU "OU=Domain Controllers,DC=Acsupport,DC=local" New-CsAnalogDevice -LineUri tel: DisplayName "Floor3-Phone" RegistrarPool LyncS.Acsupport.local -AnalogFax $False -Gateway ACSBC.Acsupport.local -OU "OU=Domain Controllers,DC=ACsupport,DC=local" The above commands create a new analog device with the phone number (LineUri) and respectively. The phone number must be specified using the E.164 format. In addition to the LineUri parameter, the other parameters used in this cmdlet are as follows: DisplayName: Specifies the AD DS display name of the device. RegistrarPool: Specifies the Registrar pool. AnalogFax: If set to $False, specifies that this is a phone and not a fax machine. Gateway: Specifies the IP address or FQDN of the PSTN Gateway. In our example scenario the SBC entity serves the analog devices (i.e., ACSBC.Acsupport.local). OU: Specifies the distinguished name (DN) of the AD DS organizational unit (OU) where the contact object for the device should be created. 4. To obtain information about the configured analog devices in the Lync Server, use the Get-CsAnalogDevice cmdlet. Version September 2013

96 Enhanced Gateway with Analog Devices Figure B-19: View Analog Devices Information Microsoft Lync Server Document #: LTRT-40140

Configuration Note Microsoft Lync Server 2013 & tipicall SIP Trunk using Mediant E-SBC

Configuration Note Microsoft Lync Server 2013 & tipicall SIP Trunk using Mediant E-SBC Enterprise Session Border Controllers (E-SBC) AudioCodes Mediant Series Interoperability Lab Configuration Note Microsoft Lync Server 2013 & tipicall SIP Trunk using Mediant E-SBC Version 6.8 December

More information

Configuration Note. Microsoft Lync Server 2013 & ITSP SIP Trunk using AudioCodes Mediant SBC. Interoperability Laboratory. Version 6.

Configuration Note. Microsoft Lync Server 2013 & ITSP SIP Trunk using AudioCodes Mediant SBC. Interoperability Laboratory. Version 6. AudioCodes Mediant Series Session Border Controller (SBC) Interoperability Laboratory Configuration Note Microsoft Lync Server 2013 & ITSP SIP Trunk using AudioCodes Mediant SBC Version 6.8 May 2015 Document

More information

Configuration Note Microsoft Lync Server 2013 & Windstream SIP Trunk using Mediant E-SBC

Configuration Note Microsoft Lync Server 2013 & Windstream SIP Trunk using Mediant E-SBC Enterprise Session Border Controllers (E-SBC) AudioCodes Mediant Series Interoperability Lab Configuration Note Microsoft Lync Server 2013 & Windstream SIP Trunk using Mediant E-SBC Version 6.8 August

More information

Configuration Note Microsoft Lync Server 2013 & Netia SIP Trunk using Mediant E-SBC

Configuration Note Microsoft Lync Server 2013 & Netia SIP Trunk using Mediant E-SBC Enterprise Session Border Controllers (E-SBC) AudioCodes Mediant Series Interoperability Lab Configuration Note Microsoft Lync Server 2013 & Netia SIP Trunk using Mediant E-SBC Version 6.8 June 2014 Document

More information

Configuration Note. Microsoft Lync Server 2013 & NextGenTel SIP Trunk using Mediant E-SBC. Enterprise Session Border Controllers (E-SBC)

Configuration Note. Microsoft Lync Server 2013 & NextGenTel SIP Trunk using Mediant E-SBC. Enterprise Session Border Controllers (E-SBC) Enterprise Session Border Controllers (E-SBC) AudioCodes Mediant Series Interoperability Lab Configuration Note Microsoft Lync Server 2013 & NextGenTel SIP Trunk using Mediant E-SBC Version 6.8 December

More information

SBC Deployment Guide Architecture Options and Configuration Examples

SBC Deployment Guide Architecture Options and Configuration Examples Enterprise Session Border Controllers Mediant E-SBC Series AudioCodes SBC Deployment Guide Architecture Options and Configuration Examples Version 6.4 April 2012 Document # LTRT-31620 Deployment Guide

More information

Spectrum Enterprise SIP Trunking Service AudioCodes Mediant Series IP PBX Configuration Guide

Spectrum Enterprise SIP Trunking Service AudioCodes Mediant Series IP PBX Configuration Guide Spectrum Enterprise SIP Trunking Service AudioCodes Mediant Series IP PBX Configuration Guide About Spectrum Enterprise: Spectrum Enterprise is a division of Charter Communications following a merger with

More information

Microsoft Skype for Business Server 2015 and Flowroute SIP Trunk using AudioCodes Mediant E-SBC

Microsoft Skype for Business Server 2015 and Flowroute SIP Trunk using AudioCodes Mediant E-SBC Configuration Note AudioCodes Professional Services Interoperability Lab Microsoft Skype for Business Server 2015 and Flowroute SIP Trunk using AudioCodes Mediant E-SBC Version 7.0 Configuration Note

More information

Microsoft Skype for Business Server 2015 and ShoreTel UC System using AudioCodes Mediant E-SBC

Microsoft Skype for Business Server 2015 and ShoreTel UC System using AudioCodes Mediant E-SBC Configuration Note AudioCodes Professional Services - Interoperability Lab Microsoft Skype for Business Server 2015 and ShoreTel UC System using AudioCodes Mediant E-SBC Version 7.0 Configuration Note

More information

Configuration Note Microsoft Lync Server 2013 & BluIP SIP Trunk using Mediant E-SBC

Configuration Note Microsoft Lync Server 2013 & BluIP SIP Trunk using Mediant E-SBC Enterprise Session Border Controllers (E-SBC) AudioCodes Mediant Series Interoperability Lab Configuration Note Microsoft Lync Server 2013 & BluIP SIP Trunk using Mediant E-SBC October 2013 Document #

More information

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

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

More information

Microsoft Skype for Business Server 2015 and TELUS SIP Trunk using AudioCodes Mediant E-SBC

Microsoft Skype for Business Server 2015 and TELUS SIP Trunk using AudioCodes Mediant E-SBC Configuration Note AudioCodes Professional Services - Interoperability Lab Microsoft Skype for Business Server 2015 and TELUS SIP Trunk using AudioCodes Mediant E-SBC Version 7.0 Configuration Note Contents

More information

SBC Configuration Examples

SBC Configuration Examples Configuration Note SBC Configuration Examples Mediant Session Border Controllers (SBC) Version 7.0 Configuration Note Contents Table of Contents 1 Introduction... 7 1.1 Configuration Terminology... 7

More information

Microsoft Skype for Business Server 2015 and DTAG SIP Trunk using AudioCodes Mediant MSBR E-SBC

Microsoft Skype for Business Server 2015 and DTAG SIP Trunk using AudioCodes Mediant MSBR E-SBC Configuration Note AudioCodes Professional Services - Interoperability Lab Microsoft Skype for Business Server 2015 and DTAG SIP Trunk using AudioCodes Mediant MSBR E-SBC Version 6.8 Configuration Note

More information

Configuration Guide IP-to-IP Application

Configuration Guide IP-to-IP Application Multi-Service Business Gateways Enterprise Session Border Controllers VoIP Media Gateways Configuration Guide IP-to-IP Application Version 6.8 November 2013 Document # LTRT-40004 Configuration Guide Contents

More information

Microsoft Lync Server 2013 and Twilio SIP Trunk using AudioCodes Mediant E-SBC

Microsoft Lync Server 2013 and Twilio SIP Trunk using AudioCodes Mediant E-SBC Configuration Note AudioCodes Professional Services - Interoperability Lab Microsoft Lync Server 2013 and Twilio SIP Trunk using AudioCodes Mediant E-SBC Version 7.0 Configuration Note Contents Table

More information

One-Voice Resiliency. Branch Sites in Microsoft Lync Server or Skype for Business Environments. Version 7.0. Configuration Note

One-Voice Resiliency. Branch Sites in Microsoft Lync Server or Skype for Business Environments. Version 7.0. Configuration Note Configuration Note AudioCodes One Voice for Skype For Business One-Voice Resiliency Branch Sites in Microsoft Lync Server or Skype for Business Environments Version 7.0 Configuration Note Contents Table

More information

One-Voice Resiliency. Branch Voice Resilience for Microsoft Skype for Business or Lync Server Environments and Skype for Business Online. Version 7.

One-Voice Resiliency. Branch Voice Resilience for Microsoft Skype for Business or Lync Server Environments and Skype for Business Online. Version 7. Configuration Note AudioCodes One Voice for Skype For Business One-Voice Resiliency Branch Voice Resilience for Microsoft Skype for Business or Lync Server Environments and Skype for Business Online Version

More information

SBC Configuration Examples for Mediant SBC

SBC Configuration Examples for Mediant SBC Configuration Note AudioCodes Mediant Series of Session Border Controllers (SBC) SBC Configuration Examples for Mediant SBC Version 7.2 Configuration Note Contents Table of Contents 1 Introduction...

More information

One-Voice Resiliency. Branch Voice Resilience for Microsoft Skype for Business or Lync Server Environments and Skype for Business Online. Version 7.

One-Voice Resiliency. Branch Voice Resilience for Microsoft Skype for Business or Lync Server Environments and Skype for Business Online. Version 7. Configuration Note AudioCodes One Voice for Skype For Business One-Voice Resiliency Branch Voice Resilience for Microsoft Skype for Business or Lync Server Environments and Skype for Business Online Version

More information

One-Voice Resiliency with SIP Trunking

One-Voice Resiliency with SIP Trunking Configuration Note AudioCodes One Voice for Skype For Business One-Voice Resiliency with SIP Trunking For Branch Sites in Microsoft Lync Server or Skype for Business Environments Version 7.2 Configuration

More information

Configuration Note How to Install SPS on the SBA

Configuration Note How to Install SPS on the SBA SIP Phone Support (SPS) Survivable Branch Appliance (SBA) Microsoft Lync Configuration Note How to Install SPS on the SBA Version 2.40 November 2012 Document # LTRT-00823 Configuration Note Contents Table

More information

Configuring MediaPack 1288 Analog Gateway as Third-Party SIP Device (Advanced) in Cisco Unified Communications Manager Ver

Configuring MediaPack 1288 Analog Gateway as Third-Party SIP Device (Advanced) in Cisco Unified Communications Manager Ver Configuration Note AudioCodes Professional Services Interoperability Lab Configuring MediaPack 1288 Analog Gateway as Third-Party SIP Device (Advanced) in Cisco Unified Communications Manager Ver. 10.0.1

More information

Microsoft Skype for Business Server 2015 and ITSP SIP Trunk using AudioCodes Mediant E-SBC

Microsoft Skype for Business Server 2015 and ITSP SIP Trunk using AudioCodes Mediant E-SBC Configuration Note AudioCodes Professional Services Interoperability Lab Microsoft Skype for Business Server 2015 and ITSP SIP Trunk using AudioCodes Mediant E-SBC Version 7.2 Configuration Note Contents

More information

Transport Layer Security (TLS) Configuration Note

Transport Layer Security (TLS) Configuration Note E SBC Series VoIP Gateway Series MSBG Series Transport Layer Security (TLS) Configuration Note January 2012 Document # LTRT 31600 Configuration Note Contents Table of Contents 1 Overview... 7 1.1 AudioCodes

More information

Configuration Note. AireSpring SIP Trunk & Genesys Contact Center using AudioCodes Mediant SBC. Session Border Controllers (SBC)

Configuration Note. AireSpring SIP Trunk & Genesys Contact Center using AudioCodes Mediant SBC. Session Border Controllers (SBC) Session Border Controllers (SBC) AudioCodes Mediant Series Interoperability Lab Configuration Note AireSpring SIP Trunk & Genesys Contact Center using AudioCodes Mediant SBC Version 6.8 October 2014 Document

More information

Mediant E-SBC for BroadCloud SIP Trunk with Microsoft Skype for Business Server 2015

Mediant E-SBC for BroadCloud SIP Trunk with Microsoft Skype for Business Server 2015 Configuration Note AudioCodes Professional Services Interoperability Lab Mediant E-SBC for BroadCloud SIP Trunk with Microsoft Skype for Business Server 2015 Version 7.2 Configuration Note Contents Table

More information

AudioCodes OVR with SIP Trunking

AudioCodes OVR with SIP Trunking Configuration Note AudioCodes One Voice for Skype For Business AudioCodes OVR with SIP Trunking for Microsoft Skype for Business Online Version 7.2 Configuration Note Contents Table of Contents 1 Introduction...

More information

Microsoft Skype for Business Server and EWE TEL SIP Trunk using AudioCodes Mediant SBC

Microsoft Skype for Business Server and EWE TEL SIP Trunk using AudioCodes Mediant SBC Configuration Note AudioCodes Professional Services Interoperability Lab Microsoft Skype for Business Server and EWE TEL SIP Trunk using AudioCodes Mediant SBC Version 7.2 Configuration Note Contents

More information

Microsoft Skype for Business Server 2015 and Exponential-e SIP Trunk using AudioCodes Mediant E-SBC

Microsoft Skype for Business Server 2015 and Exponential-e SIP Trunk using AudioCodes Mediant E-SBC Configuration Note AudioCodes Professional Services Interoperability Lab Microsoft Skype for Business Server 2015 and Exponential-e SIP Trunk using AudioCodes Mediant E-SBC Version 7.2 Configuration Note

More information

Configuration Note Restoring Factory Defaults

Configuration Note Restoring Factory Defaults Multi-Service Business Gateways VoIP Media Gateways SIP Protocol Configuration Note Restoring Factory Defaults Version 6.4 May 2012 Document # LTRT-30302 Configuration Note Contents Table of Contents

More information

Microsoft Skype for Business Server 2015 and Bell Canada SIP Trunk using AudioCodes Mediant E-SBC

Microsoft Skype for Business Server 2015 and Bell Canada SIP Trunk using AudioCodes Mediant E-SBC Configuration Note AudioCodes Professional Services Interoperability Lab Microsoft Skype for Business Server 2015 and Bell Canada SIP Trunk using AudioCodes Mediant E-SBC Version 7.2 Configuration Note

More information

MP-11x, Mediant 1000 & Mediant Application Note

MP-11x, Mediant 1000 & Mediant Application Note MP-11x, Mediant 1000 & Mediant 2000 Application Note AudioCodes Media Gateway s SAS and ENUM Capabilities for Central Routing Decision Making In a Microsoft Office Communications Server 2007 Environment

More information

Installation Guide. Version 1.0. AudioCodes Applications License Server. December 2014 Document # LTRT-00876

Installation Guide. Version 1.0. AudioCodes Applications License Server. December 2014 Document # LTRT-00876 AudioCodes Applications License Server Version 1.0 December 2014 Document # LTRT-00876 Contents Table of Contents 1 Introduction... 7 1.1 Installing License Server Externally Benefits... 7 1.2 Minimum

More information

Technical Application Note

Technical Application Note AudioCodes CPE & Access Gateway Products MP-20x Series MediaPack Series Telephone Adapters with Integrated Router Technical Application Note MP-20x Debugging and Diagnostic Tools Version 3.0.0 Technical

More information

User's Guide. AudioCodes CLI Wizard Utility. Session Border Controllers (SBC) Multi-Service Business Routers (MSBR)

User's Guide. AudioCodes CLI Wizard Utility. Session Border Controllers (SBC) Multi-Service Business Routers (MSBR) Session Border Controllers (SBC) Multi-Service Business Routers (MSBR) VoIP Analog & Digital Media Gateways User's Guide AudioCodes CLI Wizard Utility July 2014 Document # LTRT-52350 User's Guide Contents

More information

Configuration Note. MP-26x Debugging and Diagnostic Tools. MP-26x Series. Version and Later. AudioCodes CPE & Access Gateway Products

Configuration Note. MP-26x Debugging and Diagnostic Tools. MP-26x Series. Version and Later. AudioCodes CPE & Access Gateway Products AudioCodes CPE & Access Gateway Products MP-26x Series MediaPack Series Telephone Adapters with Integrated Router Configuration Note MP-26x Debugging and Diagnostic Tools Version 4.2.2 and Later Configuration

More information

Mediant Software E-SBC. Session Border Controllers. Virtual Edition. Installation Manual. Version 6.6. October 2013 Document #: LTRT-10343

Mediant Software E-SBC. Session Border Controllers. Virtual Edition. Installation Manual. Version 6.6. October 2013 Document #: LTRT-10343 Mediant Software E-SBC Session Border Controllers Virtual Edition Installation Manual Version 6.6 October 2013 Document #: LTRT-10343 Installation Manual Contents Table of Contents 1 Introduction... 7

More information

Administrator and User Manual Hot Desking with SPS for Microsoft Lync

Administrator and User Manual Hot Desking with SPS for Microsoft Lync AudioCodes SPS SIP Phone Support SPS for Microsoft Lync Administrator and User Manual Hot Desking with SPS for Microsoft Lync Version 1.0 April 2012 Document # LTRT 39830 Administrator and User Manual

More information

Configuration Note Microsoft Lync Server 2013 & BT One Voice SIP Trunk using Mediant E-SBC

Configuration Note Microsoft Lync Server 2013 & BT One Voice SIP Trunk using Mediant E-SBC Enterprise Session Border Controllers (E-SBC) AudioCodes Mediant Series Interoperability Lab Configuration Note Microsoft Lync Server 2013 & BT One Voice SIP Trunk using Mediant E-SBC April 2013 Document

More information

Configuration Note How to Backup and Restore SPS

Configuration Note How to Backup and Restore SPS SIP Phone Support VoIP Media Gateways Configuration Note How to Backup and Restore SPS Version 1.0 November 2012 Document # LTRT-40420 Configuration Note Contents Table of Contents 1 Introduction... 7

More information

Configuration Note Microsoft Office 365 Exchange UM with IP PBXs using AudioCodes Mediant SBC

Configuration Note Microsoft Office 365 Exchange UM with IP PBXs using AudioCodes Mediant SBC Session Border Controllers (SBCs) AudioCodes Mediant Series Interoperability Lab Configuration Note Microsoft Office 365 Exchange UM with IP PBXs using AudioCodes Mediant SBC Version 6.8 January 2017 Document

More information

Configuration Note Windstream SIP Trunk & Genesys Contact Center using AudioCodes Mediant SBC

Configuration Note Windstream SIP Trunk & Genesys Contact Center using AudioCodes Mediant SBC Session Border Controllers (SBC) AudioCodes Mediant Series Interoperability Lab Configuration Note Windstream SIP Trunk & Genesys Contact Center using AudioCodes Mediant SBC Version 7.0 December 2015 Document

More information

Configuration Note Recovery from Rescue Mode Procedure

Configuration Note Recovery from Rescue Mode Procedure Multi-Service Business Routers Session Border Controllers Mediant Series Configuration Note Recovery from Rescue Mode Procedure January 2014 Document #: LTRT-30705 Configuration Note Contents Table of

More information

Configuration Note Recover from Rescue Mode Procedure

Configuration Note Recover from Rescue Mode Procedure Multi-Service Business Gateway Mediant 800 MSBG Mediant 1000 MSBG Configuration Note Recover from Rescue Mode Procedure July 2011 Document #: LTRT-30701 Configuration Note Contents Table of Contents 1

More information

Configuration Note. RADIUS for Secure Device Access. Multi-Service Business Routers. Enterprise Session Border Controllers. VoIP Media Gateways

Configuration Note. RADIUS for Secure Device Access. Multi-Service Business Routers. Enterprise Session Border Controllers. VoIP Media Gateways Multi-Service Business Routers Enterprise Session Border Controllers VoIP Media Gateways Configuration Note RADIUS for Secure Device Access December 2012 Document # LTRT-34201 Configuration Note Contents

More information

Performance Monitoring and Alarm Guide

Performance Monitoring and Alarm Guide AudioCodes One Voice Operations Center EMS, SEM and IP Phones Management Performance Monitoring and Alarm Guide Mediant 1000B Gateway and E-SBC Version 7.0 Document #: LTRT-94954 Performance Monitoring

More information

Connecting PBX to BroadSoft's BroadCloud SIP Trunk using AudioCodes Mediant BRI/PRI Gateway

Connecting PBX to BroadSoft's BroadCloud SIP Trunk using AudioCodes Mediant BRI/PRI Gateway Quick Guide AudioCodes Mediant Series BRI/PRI Media Gateways Connecting PBX to BroadSoft's BroadCloud SIP Trunk using AudioCodes Mediant BRI/PRI Gateway Version 7.2 Introduction See Chapter 1 Obtain Software

More information

Configuration Note. Telenor SIP Trunk & Genesys Contact Center using AudioCodes Mediant SBC. Session Border Controllers (SBC)

Configuration Note. Telenor SIP Trunk & Genesys Contact Center using AudioCodes Mediant SBC. Session Border Controllers (SBC) Session Border Controllers (SBC) AudioCodes Mediant Series Interoperability Lab Configuration Note Telenor SIP Trunk & Genesys Contact Center using AudioCodes Mediant SBC Version 6.8 June 2015 Document

More information

Connecting IP-PBX to BroadSoft's BroadCloud SIP Trunk using AudioCodes Mediant SBC

Connecting IP-PBX to BroadSoft's BroadCloud SIP Trunk using AudioCodes Mediant SBC Quick Guide AudioCodes Mediant Session Border Controllers (SBC) Connecting IP-PBX to BroadSoft's BroadCloud SIP Trunk using AudioCodes Mediant SBC Version 7.2 Introduction See Chapter 1 Obtain Software

More information

CloudBond 365 Standard / Standard+ Box Editions

CloudBond 365 Standard / Standard+ Box Editions Quick Start Guide AudioCodes One Voice for Microsoft Skype for Business CloudBond 365 Standard / Standard+ Box Editions Version 7.4.0 Quick Start Guide Contents Table of Contents 1 Introduction... 7 2

More information

Configuration Note. Connecting MSBR to WAN through 3G Cellular Modem. Multi-Service Business Router (MSBR) Mediant 850 MSBR.

Configuration Note. Connecting MSBR to WAN through 3G Cellular Modem. Multi-Service Business Router (MSBR) Mediant 850 MSBR. Multi-Service Business Router (MSBR) Mediant 850 MSBR Mediant 800 MSBR Configuration Note Connecting MSBR to WAN through 3G Cellular Modem April 2013 Document # LTRT-31611 Configuration Note Contents

More information

Configuration Note. SPS Best Practice Preventative Maintenance and Health Check Procedures. Version 1.0. SIP Phone Support (SPS) VoIP Media Gateways

Configuration Note. SPS Best Practice Preventative Maintenance and Health Check Procedures. Version 1.0. SIP Phone Support (SPS) VoIP Media Gateways SIP Phone Support (SPS) VoIP Media Gateways SIP Protocol Configuration Note SPS Best Practice Preventative Maintenance and Health Check Procedures Version 1.0 May 2013 Document # LTRT-31330 Configuration

More information

Configuration File Backup and Restore Procedure

Configuration File Backup and Restore Procedure Configuration Note AudioCodes Family of Media Gateways & Session Border Controllers Configuration File Backup and Restore Procedure Configuration Note Contents Table of Contents 1 Introduction... 7 2

More information

400HD Series of High Definition IP Phones. Configuration Note. Call Recording on AudioCodes. 400HD Series IP Phones. Document #: LTRT-11360

400HD Series of High Definition IP Phones. Configuration Note. Call Recording on AudioCodes. 400HD Series IP Phones. Document #: LTRT-11360 AudioCodes 400HD Series of High Definition IP Phones HD VoIP 400HD Series IP Phones Configuration Note Call Recording on AudioCodes 400HD Series IP Phones Document #: LTRT-11360 Configuration Note Notices

More information

Quick Start Guide. AudioCodes One Voice for Microsoft Skype for Business. CloudBond 365. Pro / Enterprise Box Edition. Version 7.0

Quick Start Guide. AudioCodes One Voice for Microsoft Skype for Business. CloudBond 365. Pro / Enterprise Box Edition. Version 7.0 Quick Start Guide AudioCodes One Voice for Microsoft Skype for Business CloudBond 365 Pro / Enterprise Box Edition Version 7.0 Quick Start Guide Notices Table of Contents 1 Introduction... 7 2 CloudBond

More information

Release Notes. AudioCodes One Voice for Microsoft Skype for Business. Mediant SBA for Microsoft Skype for. Business. Version 7.2

Release Notes. AudioCodes One Voice for Microsoft Skype for Business. Mediant SBA for Microsoft Skype for. Business. Version 7.2 Release Notes AudioCodes One Voice for Microsoft Skype for Business Mediant SBA for Microsoft Skype for Business Version 7.2 Release Notes Contents Contents 1 Introduction... 7 1.1 Supported SBA Models...

More information

Configuration Note 3G Cellular Modem WAN Connection

Configuration Note 3G Cellular Modem WAN Connection Mediant 800 MSBG Multi-Service Business Gateway SIP Protocol Configuration Note 3G Cellular Modem WAN Connection Version 1.0 January 2012 Document # LTRT-31610 Configuration Note Contents Table of Contents

More information

SBA Management Interface for Skype for Business

SBA Management Interface for Skype for Business Release Notes AudioCodes One Voice for Microsoft Skype for Business SBA Management Interface for Skype for Business Version 7.2.24 Release Notes Contents Contents 1 Introduction... 7 1.1 SBA Components...

More information

Teams Direct Routing. Configuration Checklists for BTIP and Business Talk SIP services. 28 january Teams Direct Routing AudioCodes Checklist 0.

Teams Direct Routing. Configuration Checklists for BTIP and Business Talk SIP services. 28 january Teams Direct Routing AudioCodes Checklist 0. Teams Direct Routing Configuration Checklists for BTIP and Business Talk 28 january 2019 Teams Direct Routing AudioCodes Checklist 0.2 Contents 1 Main certified architectures... 3 1.1 Standalone mode...

More information

CloudBond 365 Pro / Enterprise Box Editions

CloudBond 365 Pro / Enterprise Box Editions Quick Start Guide AudioCodes One Voice for Microsoft Skype for Business CloudBond 365 Pro / Enterprise Box Editions Version 7.4.0 Quick Start Guide Contents Table of Contents 1 Introduction... 7 2 CloudBond

More information

Mediant Cloud Edition (CE)

Mediant Cloud Edition (CE) Installation Manual AudioCodes Mediant Family of Session Border Controllers (SBC) Mediant Cloud Edition (CE) Session Border Controller Version 7.2 Installation Manual Contents Table of Contents 1 Introduction...

More information

Microsoft Teams Direct Routing Enterprise Model and Swisscom SIP Trunk "Smart Business Connect" using AudioCodes Mediant SBC

Microsoft Teams Direct Routing Enterprise Model and Swisscom SIP Trunk Smart Business Connect using AudioCodes Mediant SBC Configuration Note AudioCodes Professional Services Interoperability Lab Microsoft Teams Direct Routing Enterprise Model and Swisscom SIP Trunk "Smart Business Connect" using AudioCodes Mediant SBC Version

More information

SIP Phone Support. Release Notes. Version

SIP Phone Support. Release Notes. Version AudioCodes SIP Phone Support SIP SPS Release Notes SIP Phone Support Version 2.44.13 Release Notes Contents Table of Contents 1 Introduction... 7 2 What s New in Version 2.44.13... 9 2.1 Interoperability

More information

Configuration Note Debug Recording Feature

Configuration Note Debug Recording Feature Multi-Service Business Gateways VoIP Media Gateways SIP, MGCP, MEGACO, TPNCP Protocols Configuration Note Debug Recording Feature July 2011 Document # LTRT-28701 Configuration Note Contents Table of Contents

More information

Performance Monitoring and Alarm Guide

Performance Monitoring and Alarm Guide AudioCodes One Voice Operations Center EMS, SEM and IP Phones Management Performance Monitoring and Alarm Guide Mediant 2600/4000/9000/SW SBC Series Version 7.0 Document #: LTRT- 41602 Peformance Monitoring

More information

User's Guide Call Progress Tones Wizard (CPTWizard) Utility

User's Guide Call Progress Tones Wizard (CPTWizard) Utility Call Progress Tones Wizard (CPTWizard) Utility Version 6.2 Build 2.8 August 2012 Document # LTRT-30530 Contents Table of Contents 1 Introduction... 7 2 Installing CPTWizard... 9 3 CPT Detection and File

More information

Mediant 1000B Chassis. Physical Description

Mediant 1000B Chassis. Physical Description Mediant 1000B Chassis Physical Description Document #: LTRT-1401 November 2009 Physical Description Contents Table of Contents 1 Introduction... 7 2 Chassis Description... 9 2.1 Front-Panel Description...

More information

Microsoft Teams Direct Routing Enterprise Model and DTAG SIP Trunk using AudioCodes Mediant SBC

Microsoft Teams Direct Routing Enterprise Model and DTAG SIP Trunk using AudioCodes Mediant SBC Configuration Note AudioCodes Professional Services Interoperability Lab Microsoft Teams Direct Routing Enterprise Model and DTAG SIP Trunk using AudioCodes Mediant SBC Version 7.2 Configuration Note

More information

Backup and Restore Procedure

Backup and Restore Procedure Configuration Note AudioCodes Family of Media Gateways & Session Border Controllers Backup and Restore Procedure Configuration Note Contents Table of Contents 1 Introduction... 7 2 Backing up Configuration...

More information

Connecting AudioCodes' SBC to Microsoft Teams Direct Routing Hosting Model

Connecting AudioCodes' SBC to Microsoft Teams Direct Routing Hosting Model Configuration Note AudioCodes Mediant Family of Media Gateways & Session Border Controllers Connecting AudioCodes' SBC to Microsoft Teams Direct Routing Hosting Model Version 7.2 Configuration Note Contents

More information

IP Phone Manager Express

IP Phone Manager Express Administrator's Manual AudioCodes 400HD IP Phones Series IP Phone Manager Express Version 7.2 Administrator's Manual Contents Table of Contents 1 Introducing the IPP Manager Express - Windows Edition...

More information

Connecting AudioCodes' SBC to Microsoft Teams Direct Routing Hosting Model

Connecting AudioCodes' SBC to Microsoft Teams Direct Routing Hosting Model Configuration Note AudioCodes Mediant Family of Media Gateways & Session Border Controllers Connecting AudioCodes' SBC to Microsoft Teams Direct Routing Hosting Model Version 7.2 Configuration Note Contents

More information

IP Phone Manager Express

IP Phone Manager Express Administrator's Manual AudioCodes 400HD IP Phones Series IP Phone Manager Express Version 7.2 Administrator's Manual Contents Table of Contents 1 Introducing the IPP Manager Express - Windows Edition...

More information

User's Guide. AudioCodes One Voice Operations Center. SBA ProConnect. Version 7.2

User's Guide. AudioCodes One Voice Operations Center. SBA ProConnect. Version 7.2 User's Guide AudioCodes One Voice Operations Center SBA ProConnect Version 7.2 Version 0.0.0 November 2015 Document #: LTRT-38911 User's Guide Contents Table of Contents 1 Introduction... 7 2 Before Installing

More information

AudioCodes Academy Course Catalog February 2013

AudioCodes Academy Course Catalog February 2013 AudioCodes Academy Course Catalog February 2013 Version 1.0 Document # LTRT-45504 Page 2 AudioCodes Academy Table of Contents Introduction... 5 Technical Training Courses Offered... 5 Future Technical

More information

Connecting AudioCodes' SBC to Microsoft Teams Direct Routing Enterprise Model

Connecting AudioCodes' SBC to Microsoft Teams Direct Routing Enterprise Model Configuration Note AudioCodes Mediant Family of Media Gateways & Session Border Controllers Connecting AudioCodes' SBC to Microsoft Teams Direct Routing Enterprise Model Version 7.2 Configuration Note

More information

AudioCodes Routing Manager (ARM)

AudioCodes Routing Manager (ARM) Release Notes AudioCodes One Voice Operations Center AudioCodes Routing Manager (ARM) Version 8.2 Release Notes Contents Table of Contents 1 Overview... 7 1.1 Managed Devices... 7 1.2 Supported Node Firmware...

More information

Mediant VE SBC. Session Border Controller. Virtual Edition. Installation Manual. Version 6.8. June 2015 Document #: LTRT-10352

Mediant VE SBC. Session Border Controller. Virtual Edition. Installation Manual. Version 6.8. June 2015 Document #: LTRT-10352 Mediant VE SBC Session Border Controller Virtual Edition Installation Manual Version 6.8 June 2015 Document #: LTRT-10352 Installation Manual Contents Table of Contents 1 Introduction... 7 1.1 Product

More information

Microsoft Office 365 X-UM with IP PBXs using AudioCodes CloudBond X-UM Standard

Microsoft Office 365 X-UM with IP PBXs using AudioCodes CloudBond X-UM Standard Release Notes AudioCodes One Voice for Microsoft Skype for Business Microsoft Office 365 X-UM with IP PBXs using AudioCodes CloudBond X-UM Standard Version 0.1 Release Notes Contents Table of Contents

More information

Mediant CCE Appliances

Mediant CCE Appliances Release Notes AudioCodes One Voice for Microsoft Skype for Business Mediant CCE Appliances Mediant 800 CCE & Mediant Server CCE Microsoft Skype for Business Cloud Connector Edition (CCE) Version 2.1.0

More information

CloudBond 365 & User Management Pack 365

CloudBond 365 & User Management Pack 365 Release Notes AudioCodes One Voice for Microsoft Skype for Business CloudBond 365 & User Management Pack 365 Version 7.2.5 Release Notes Contents Table of Contents 1 Introduction... 7 1.1 Items Released...

More information

User's Manual. Version 5.6

User's Manual. Version 5.6 User's Manual Version 5.6 Document #: LTRT-68808 November 2008 SIP User's Manual Contents Table of Contents 1 Overview... 15 1.1 SIP Overview... 16 2 Configuration Concepts... 17 3 Web-Based Management...

More information

User Management Pack 365

User Management Pack 365 Software Installation Manual AudioCodes One Voice for Microsoft Skype for Business User Management Pack 365 Software Installation Version 7.2.5 Software Installation Manual Contents Table of Contents

More information

SmartTAP Call Recording Solution

SmartTAP Call Recording Solution Installation Guide AudioCodes One Voice for Microsoft Skype for Business SmartTAP Call Recording Solution For Windows Failover Cluster (WFC) Version 4.2 Installation Guide Contents Table of Contents 1

More information

User's Manual. Version 5.8

User's Manual. Version 5.8 User's Manual Version 5.8 Document #: LTRT-65412 September 2009 SIP User's Manual Contents Table of Contents 1 Overview... 19 1.1 Gateway Description... 19 1.2 MediaPack Features... 21 1.2.1 MP-11x Hardware

More information

SIP Phone Support (SPS)

SIP Phone Support (SPS) Release Notes AudioCodes One Voice for Microsoft Skype for Business SIP Phone Support (SPS) Version 3.00 Release Notes Contents Table of Contents 1 Introduction... 7 1.1 Windows 2016 Support... 7 2 New

More information

Application Note. AudioCodes One Voice for Microsoft 365. CloudBond 365. Partner Guidelines for Verifying Third-Party Applications

Application Note. AudioCodes One Voice for Microsoft 365. CloudBond 365. Partner Guidelines for Verifying Third-Party Applications Application Note AudioCodes One Voice for Microsoft 365 CloudBond 365 Partner Guidelines for Verifying Third-Party Applications Application Note Contents Table of Contents 1 General Description... 7 2

More information

Administrator's Manual

Administrator's Manual IP Phone Management Server EMS Provisioning Server 400HD Series IP Phones Administrator's Manual Version 7 March 2015 Document # LTRT-91082 Administrator's Manual Contents Table of Contents 1 Introduction...

More information

SEM for AudioCodes Media Gateways and Servers. Session Experience Manager. User's Manual. Version 6.8

SEM for AudioCodes Media Gateways and Servers. Session Experience Manager. User's Manual. Version 6.8 SEM for AudioCodes Media Gateways and Servers SEM Session Experience Manager User's Manual Version 6.8 User's Manual Contents Table of Contents 1 Session Experience Manager... 11 1.1 Overview... 11 1.2

More information

Mediant and MediaPack Series Gateways & SBCs

Mediant and MediaPack Series Gateways & SBCs Release Notes AudioCodes Family of Media Gateways & Session Border Controllers (SBC) Mediant and MediaPack Series Gateways & SBCs Version 7.0 Release Notes Contents Table of Contents 1 Introduction...

More information

Solution SPSS. Compatible. From Ver For. ays

Solution SPSS. Compatible. From Ver For. ays SPS Solution SPSS SIP Phone Support From Technical Note SPSS Upgrade OCS 2007 R2 Compatible to Lync Ver. 1. 2 For AudioCodes Gatewa ays Compatible Document #: LTRT-29200 December 2010 Technical Note Contents

More information

Solution Integration Guide for Multimedia Communication Server 5100 Release 4.0 and AudioCodes

Solution Integration Guide for Multimedia Communication Server 5100 Release 4.0 and AudioCodes Solution Integration Guide for Multimedia Communication Server 5100 Release 40 and AudioCodes NN42020-314 Document status: Standard Document version: 0101 Document date: 18 March 2008 All Rights Reserved

More information

Connecting ShoreTel IP-PBX to BroadCloud SIP Trunk using AudioCodes Mediant E-SBC

Connecting ShoreTel IP-PBX to BroadCloud SIP Trunk using AudioCodes Mediant E-SBC Configuration Note AudioCodes Professional Services - Interoperability Lab Connecting ShoreTel IP-PBX to BroadCloud SIP Trunk using AudioCodes Mediant E-SBC Version 7.0 Configuration Note Contents Table

More information

VOCANOM Web Based Management Tool Administrator's Guide

VOCANOM Web Based Management Tool Administrator's Guide Mediant 800 VOCANOM Auto Attendant Speech Enabled Directory Assistance VOCANOM Web Based Management Tool Administrator's Guide Version 1.04 February 2013 Document # LTRT 28821 VOCANOM Web-Based Management

More information

EMS, SEM and IP Phone Manager

EMS, SEM and IP Phone Manager Security Guidelines AudioCodes One Voice Operations Center Product Suite EMS, SEM and IP Phone Manager Version 7.2 Security Guidelines Contents Table of Contents 1 Introduction... 7 1.1 AudioCodes EMS

More information

AudioCodes Element Management System (EMS) and Session Experience Manager (SEM) Release Notes. Version 6.8

AudioCodes Element Management System (EMS) and Session Experience Manager (SEM) Release Notes. Version 6.8 AudioCodes Element Management System (EMS) and Session Experience Manager (SEM) Release Notes Version 6.8 EMS and SEM Release Notes Contents Table of Contents 1 Managed VoIP Equipment... 9 2 New Features

More information

AudioCodes CPE & Access Gateway Products MP-20x Multimedia Home Gateway Quick Guide MediaPack 20x for BroadSoft s BroadCloud PacketSmart Monitoring

AudioCodes CPE & Access Gateway Products MP-20x Multimedia Home Gateway Quick Guide MediaPack 20x for BroadSoft s BroadCloud PacketSmart Monitoring AudioCodes CPE & Access Gateway Products MP-20x Multimedia Home Gateway Quick Guide MediaPack 20x for BroadSoft s BroadCloud PacketSmart Monitoring Version 4.4.4 Document #: LTRT-25313 Quick Guide Contents

More information

Configuration Details to connect BT One Voice SIP

Configuration Details to connect BT One Voice SIP Thank you for your order for BT s One Voice SIP trunk UK. This Configuration document is provided as a source of guidance for the purpose of ensuring optimum performance when connecting the customer s

More information

Dolby Conference Phone. Configuration guide for Avaya Aura Platform 6.x

Dolby Conference Phone. Configuration guide for Avaya Aura Platform 6.x Dolby Conference Phone Configuration guide for Avaya Aura Platform 6.x Version 3.1 22 February 2017 Copyright 2017 Dolby Laboratories. All rights reserved. Dolby Laboratories, Inc. 1275 Market Street San

More information