LTRT-31902 AudioCodes Mediant 1000 MSBG with Microsoft Lync and Verizon SIP Trunk Configuration Note
Add to my manuals102 Pages
advertisement
Contents
Multi-Service Business Gateways
VoIP Media Gateways
Configuration Note
Connecting Microsoft® Lync™ and Verizon SIP
Trunk using AudioCodes Mediant 1000 MSBG
Version 6.2
April 2012
Document #: LTRT-31902
Configuration Note Contents
Table of Contents
AudioCodes Gateway Version ................................................................ 11
Verizon SIP Trunking Version ................................................................ 11
Microsoft Lync Server 2010 Version ...................................................... 11
Mediation Server Version ....................................................................... 12
Microsoft Lync Client Version ................................................................ 12
Lync Server 2010 Specification .............................................................. 13
Configuring the Mediant 1000 MSBG as a 'IP/PSTN Gateway' ............ 15
Associating the ‘IP/PSTN Gateway’ with the Mediation Server ........... 19
Configuring the ‘Route’ on the Lync Server 2010 ................................. 24
Configuring the ‘Dial Plan’ on the Lync Server 2010 ............................ 33
Enabling Voice Mail in the Exchange Server ........................................ 38
Enabling User for Lync Voice ................................................................. 43
Step 1: Configuring IP Addresses .......................................................... 49
LAN and WAN Interface Separation ........................................................ 49
Configuring the LAN IP Addresses ......................................................50
Assigning WAN IP Addresses .............................................................52
Step 2: Enabling the SIP SBC and IP2IP Application ........................... 55
Step 3: Configuring the Number of Media Channels ............................ 56
Step 4: Configuring the Proxy Sets ....................................................... 57
Step 5: Configuring the IP Groups ......................................................... 59
Step 6: Configuring the Voice Coders ................................................... 62
Step 7: Defining Silence Suppression and Comfort Noise .................. 64
Step 8: Configuring IP Profile Settings .................................................. 65
Step 9: Configuring Message Manipulation for Call Forwarding ........ 68
Assigning Inbound Message Manipulation Set to Entire Gateway .......... 70
Assigning Outbound Message Manipulation Set to an IP Group ............. 71
Step 10: Configuring Unscreened ANI using P-Asserted Identity ....... 72
Step 11: Configuring IP-to-IP Routing Setup ........................................ 73
Configure Inbound IP Routing ................................................................. 73
Configuring Outbound IP Routing ............................................................ 75
Step 12: Configuring Number Manipulation .......................................... 77
Configuring Destination Phone Number Manipulation ............................. 78
Configuring Source Phone Number Manipulation ................................... 79
Configuring Redirect Number Manipulation ............................................. 80
Version 6.2 3 April 2012
Lync Server 2010 and Verizon SIP Trunk
Step 13: Configuring SIP General Parameters ...................................... 81
Step 14: Configuring SIP Supplementary Services .............................. 83
Step 15: Defining Reasons for Alternative Routing .............................. 84
Step 16: Supporting Regional Call Progress Tone ............................... 86
Debugging Procedures ........................................................................... 89
Case Reporting Procedures .................................................................... 89
Wireshark Network Sniffer ....................................................................... 92
Step 1: Configure the Endpoint Phone Number Table ......................... 97
Step 2: Configure Tel to IP Routing Table ............................................. 98
Step 3: Configure Coders Table ............................................................. 99
Step 4: Configure SIP UDP Transport Type and Fax Signaling Method100
Configuration Note 4 Document #: LTRT-31902
Configuration Note Contents
List of Figures
Version 6.2 5 April 2012
Lync Server 2010 and Verizon SIP Trunk
Configuration Note 6 Document #: LTRT-31902
Configuration Note Contents
Version 6.2 7 April 2012
Lync Server 2010 and Verizon SIP Trunk
List of Tables
Configuration Note 8 Document #: LTRT-31902
Configuration Note Notices
Notice
This document describes the procedure for integrating the Verizon Internet Telephony Service
Provider (ITSP) SIP Trunk with Microsoft Lync Server 2010 using AudioCodes Mediant 1000 MSBG.
Information contained in this document is believed to be accurate and reliable at the time of printing.
However, due to ongoing product improvements and revisions, AudioCodes cannot guarantee the accuracy of printed material after the Date Published nor can it accept responsibility for errors or omissions. Updates to this document and other documents can be viewed at http://www.audiocodes.com/downloads .
© Copyright 2012 AudioCodes Ltd. All rights reserved.
This document is subject to change without notice.
Date Published: April-16-2012
Trademarks
AudioCodes, AC, AudioCoded, Ardito, CTI2, CTI², CTI Squared, HD VoIP, HD VoIP
Sounds Better, InTouch, IPmedia, Mediant, MediaPack, NetCoder, Netrake, Nuera,
Open Solutions Network, OSN, Stretto, TrunkPack, VMAS, VoicePacketizer,
VoIPerfect, VoIPerfectHD, What’s Inside Matters, Your Gateway To VoIP and 3GX are trademarks or registered trademarks of AudioCodes Limited. All other products or trademarks are property of their respective owners.
WEEE EU Directive
Pursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed of with unsorted waste. Please contact your local recycling authority for disposal of this product.
Customer Support
Customer technical support and service are generally provided by AudioCodes’
Distributors, Partners, and Resellers from whom the product was purchased. For technical support for products purchased directly from AudioCodes, or for customers subscribed to AudioCodes Customer Technical Support (ACTS), contact [email protected]
.
Abbreviations and Terminology
Each abbreviation, unless widely used, is spelled out in full when first used.
Note:
Throughout this guide, the term gateway refers to AudioCodes Mediant 1000
MSBG device.
Version 6.2 9 April 2012
Reader’s Notes
Lync Server 2010 and Verizon SIP Trunk
Configuration Note 10 Document #: LTRT-31902
Configuration Note 1. Components Information
1 Components Information
1.1
Gateway Vendor
Model
Software Version
Interface Type
VoIP Protocol
Additional Notes
AudioCodes Gateway Version
Table 1-1: AudioCodes Gateway Version
AudioCodes
Mediant 1000 MSBG MSBG
SIP_6.20A.028.004
SIP/IP
SIP
With Digital Trunk Module or MPM module for DSP resources
MSFT
– Enable working with Microsoft Lync
IPSEC, MediaEncryption, StrongEncryption and
EncryptControlProtocol
– Enable working with TLS transport type
SBC = 120
– Enable the IP-to-IP feature up to 60 sessions
1.2
Gateway Vendor
Models
Software Version
VoIP Protocol
Additional Notes
Verizon SIP Trunking Version
Table 1-2: Verizon Version
Verizon
SIP
None
1.3
Gateway Vendor
Models
Software Version
VoIP Protocol
Additional Notes
Microsoft Lync Server 2010 Version
Table 1-3: Microsoft Lync Version
Microsoft
Microsoft Lync Server 2010
RTM: Release 2010 4.0.7577.184
SIP
None
Version 6.2 11 April 2012
Lync Server 2010 and Verizon SIP Trunk
1.4
Gateway Vendor
Models
Software Version
VoIP Protocol
Additional Notes
Mediation Server Version
Table 1-4: Microsoft Lync Version
Microsoft
Mediation Server
RTM: Release 2010 4.0.7577.183
SIP
None
1.5
Gateway Vendor
Models
Software Version
VoIP Protocol
Additional Notes
Microsoft Lync Client Version
Table 1-4: Microsoft Lync Version
Microsoft
Microsoft Lync Client
RTM: Release 2010 4.0.7577.4051
SIP
None
Configuration Note 12 Document #: LTRT-31902
Configuration Note
1.6
1. Components Information
Lync Server 2010 Specification
For the purposes of this testing, the following server specification was used to host the
Microsoft Lync environment in a fully functioning Lync Server 2010 deployment, including Active Directory and DNS.
The Domain Controller (DC) and t he Lync standard edition where installed on the
OSN3 server hosted on the Mediant 1000B MSBG chassis.
Table 1-5: OSN3 Specifications
Parameter
CPU
RAM Memory
Hard Drives
Bus/Chipset
L2 Cache
Interfaces
Operating
System
Specification
Intel® Core™ 2 Duo 1.5 GHz processors L7400 with Intel 3100
Chipset (64-bit)
2 G DDR2 with ECC
Up to 2 hard drives (HDMX modules) 160GB
64 Bit
2 M
Gigabit Ethernet
USB 2.0 via Connection Module
RS-232 COM
Windows Server 2008 standard
Version 6.2 13 April 2012
1.7
Lync Server 2010 and Verizon SIP Trunk
Topology
The procedures described in this document describe the following example scenario:
An enterprise has a deployed Lync server 2010 in its private network for enhanced communication within the company.
The enterprise decides to offer its employees Enterprise voice and to connect the company to the PSTN network using the Verizon SIP Trunking service.
AudioCodes Session Border Controller (SBC) is used to manage the connection between the Enterprise LAN and the Verizon SIP trunk.
The “session" refers to the real-time voice session using IP SIP signaling protocol.
The "border" refers to the IP to IP network border between the Microsoft Lync network in the Enterprise LAN and the Verizon SIP trunk in the public network.
Figure 1-1 below illustrates the interoperability topology between the Lync Server 2010
LAN and the Verizon SIP Trunking site.
The setup requirements are characterized as follows:
While the Lync Server 2010 environment is located on the Enterprise's Local Area
Network (LAN), the Verizon SIP Trunks are located on the WAN.
The internal data routing capabilities of the Mediant 1000 MSBG device are used.
Consequently, a separate WAN interface is configured in the LAN.
Lync Server 2010 works with the TLS transport type, while the Verizon SIP trunk works on the SIP over UDP transport type.
Transcoding support: Lync Server 2010 supports G.711A-law and G.711U-law coders, while the Verizon SIP Trunk also supports the G.729 coder type.
ATA - FAX Support via Analog Media Gateway.
Support for early media handling
Figure 1-1: Topology
Configuration Note 14 Document #: LTRT-31902
Configuration Note
2
2. Configuring Lync Server 2010
Configuring Lync Server 2010
This section describes how to configure the Lync Server 2010 to operate with the
Mediant 1000 MSBG. This section describes the following procedures:
1.
Configuring the Mediant 1000 MSBG as a ‘IP/PSTN Gateway’. See Section
2.
Associating the ‘IP/PSTN Gateway’ with the Mediation Server. See Section 2.2
on
3.
Configuring a ‘Route’ to utilize the SIP trunk connected to the Mediant 1000
Note:
Dial Plans, Voice Policies, and PSTN usages are also necessary for enterprise voice deployment; however, they are beyond the scope of this document.
2.1 Configuring the Mediant 1000 MSBG as a 'IP/PSTN
Gateway'
This section describes how to configure the Mediant 1000 MSBG as an IP/PSTN
Gateway.
To configure the Mediant 1000 MSBG as a IP/PSTN Gateway and associating it with the Mediation Server:
1.
On the server where the Topology Builder is located, start the Lync Server 2010
Topology Builder
(Click Start, select All Programs, and select Lync Server
Topology Builder
).
Figure 2-1: Starting the Lync Server Topology Builder
Version 6.2 15 April 2012
Lync Server 2010 and Verizon SIP Trunk
The following screen is displayed:
Figure 2-2: Topology Builder Options
2.
Click the Download Topology from the existing deployment button and click
OK
; you are prompted to save the Topology which you have downloaded.
Figure 2-3: Save Topology
Configuration Note 16 Document #: LTRT-31902
Configuration Note 2. Configuring Lync Server 2010
3.
Enter new File Name and Save (this action enables you to rollback from any changes you make during the installation); the Topology Builder screen with the topology downloaded is displayed.
Figure 2-4: Downloaded Topology
4.
Expand the Site, right-click the IP/PSTN Gateway and choose New IP/PSTN
Gateway
.
Figure 2-5: New IP/PSTN Gateway
Version 6.2 17 April 2012
Lync Server 2010 and Verizon SIP Trunk
Figure 2-6: Define New IP/PSTN Gateway
5.
Enter the FQDN of the Mediant 1000 MSBG (i.e. '‘Verizon.lync.local') and click
OK
.
Note that the listening port for the Gateway is ‘5067’ and the transport type is
‘TLS’.
The Mediant 1000 MSBG is now added as 'IP/PSTN Gateway'.
Figure 2-7: IP/PSTN Gateway
Configuration Note 18 Document #: LTRT-31902
Configuration Note
2.2
2. Configuring Lync Server 2010
Associating the ‘IP/PSTN Gateway’ with the
Mediation Server
This section describes how to associate the ‘IP/PSTN Gateway’ with the Mediation
Server.
To associate the IP/PSTN Gateway with the Mediation Server:
1.
Right-click the Mediation server to use with the MSBG (i.e. 'FE-Lync.Lync.local') and choose Edit Properties.
Figure 2-8: Associating Mediation Server with IP/PSTN Gateway
Version 6.2 19 April 2012
Lync Server 2010 and Verizon SIP Trunk
The following screen is displayed:
Figure 2-9: Before Associating IP/PSTN Gateway to a Mediation Server Associations
2.
In the top-left corner, choose PSTN gateway and in the Mediation Server PSTN gateway pane, mark the MSBG gateway (i.e. 'Verizon.lync.local') and click Add to associate it with this Mediation Server.
Note that there are two sub-panes, one including a list of gateways not associated with the Mediation server and one including a list of gateways associated with the
Mediation server.
Figure 2-10: After Associating IP/PSTN Gateway to Mediation Server
3.
Click OK.
Configuration Note 20
Document #: LTRT-31902
Configuration Note 2. Configuring Lync Server 2010
Figure 2-11: Media Server PSTN Gateway Association Properties
4.
In the Lync Server main menu, choose Action > Publish Topology.
Figure 2-12: Publishing Topology
Version 6.2 21 April 2012
Lync Server 2010 and Verizon SIP Trunk
The Publish Topology screen is displayed.
Figure 2-13:Publish Topology Confirmation
5.
Click Next; the Topology Builder attempts to publish your topology.
Figure 2-14: Publish Topology Confirmation screen
Configuration Note 22 Document #: LTRT-31902
Configuration Note 2. Configuring Lync Server 2010
Wait until the publish topology process has ended successfully.
Figure 2-15: Publish Topology Successfully Completed
6.
Click Finish.
Version 6.2 23 April 2012
2.3
Lync Server 2010 and Verizon SIP Trunk
Configuring the ‘Route’ on the Lync Server 2010
This section describes how to configure a ‘Route’ on the Lync server and associate it with the MSBG PSTN gateway.
To configure the ‘route’ on the Lync server:
1.
Open the Communication Server Control Panel (CSCP), click Start, select All
Programs
, and select Lync Server Control Panel.
Figure 2-16: Lync Server Control Panel
2.
You are prompted for credentials; enter your domain username and password.
Configuration Note 24 Document #: LTRT-31902
Configuration Note 2. Configuring Lync Server 2010
Figure 2-17: Lync Server Credentials
The CSCP Home page is displayed.
Figure 2-18: CSCP Home page
Version 6.2
3.
In the Navigation pane, select the Voice Routing option.
25 April 2012
Lync Server 2010 and Verizon SIP Trunk
Figure 2-19: Voice Routing Option
4.
In the Voice Routing menu at the top of the page, select the Route option.
Figure 2-20: Route Option
5.
In the content area toolbar, click ..
6.
In the Build a Pattern to Match pane, fill in a Name for this route (i.e. Verizon
Route) and a Pattern to Match for the phone numbers you wish this route to handle. In this example, the pattern to match is ‘*’, which means “to match all numbers”.
7.
Click Add.
Configuration Note 26 Document #: LTRT-31902
Configuration Note 2. Configuring Lync Server 2010
Figure 2-21: Adding New Voice Route
8.
Associate the route with the MSBG IP/PSTN gateway you created above; scroll down to the Associated Gateways pane and click Add; a list of all the deployed gateways is displayed.
Version 6.2 27 April 2012
Lync Server 2010 and Verizon SIP Trunk
Figure 2-22: List of Deployed Gateways
9.
Select the MSBG Gateway you created above and click OK.
Configuration Note 28 Document #: LTRT-31902
Configuration Note 2. Configuring Lync Server 2010
Figure 2-23: Selecting the MSBG Gateway
10.
Associate a PSTN Usage to this route. In the Associated PSTN Usages toolbar, click Select and add the associated PSTN Usage.
Version 6.2 29 April 2012
Lync Server 2010 and Verizon SIP Trunk
Figure 2-24: Associating PSTN Usage to MSBG Gateway
11.
Click the OK button in the toolbar at the top of the New Voice Route pane.
Figure 2-25: Confirmation of New Voice Route
12.
In the Content area Toolbar, click on the arrow adjacent to the Commit button; a drop-down menu is displayed; select the Commit All option.
Configuration Note 30 Document #: LTRT-31902
Configuration Note 2. Configuring Lync Server 2010
Figure 2-26: Committing Voice Routes
13.
In the Uncommitted Voice Configuration Settings window, click Commit.
Figure 2-27: Uncommitted Voice Configuration Settings
14.
A message is displayed, confirming a successful voice routing configuration; in the Microsoft Lync Server 2010 Control Panel prompt; click Close.
Figure 2-28: Voice Routing Configuration Confirmation
Version 6.2 31 April 2012
Lync Server 2010 and Verizon SIP Trunk
The new committed Route is now displayed in the Voice Routing screen.
Figure 2-29: Voice Routing Screen Displaying Committed Routes
Configuration Note 32 Document #: LTRT-31902
Configuration Note
2.4
2. Configuring Lync Server 2010
Configuring the ‘Dial Plan’ on the Lync Server
2010
This section describes how to configure a 'Dial Plan' on the Lync server and associate it with 'Normalization' Rules.
To configure the ‘Dial Plan on the Lync Server 2010:
1.
In the Navigation pane, select the Voice Routing option.
Figure 2-30: Voice Routing Option
2.
In the Voice Routing menu at the top of the page, select the Dial Plan option.
Figure 2-31: Dial Plan Option
3.
In the content area toolbar, click . and select the Dial Plan type.
Version 6.2
In this example, we create a 'User Dial Plan'.
4.
In the New Dial Plan pane, fill in a Name for this Dial Plan (i.e. Verizon Users) and create new 'Associated Normalization Rules' to match for the dialing phone numbers you wish this Dial Plan to handle.
33 April 2012
Lync Server 2010 and Verizon SIP Trunk
5.
Click Add.
6.
For creating ‘New Normalization Rules’ in the content area toolbar, click the
option.
Figure 2-32: New Normalization Rules Option
7.
In the New Normalization Rules pane, fill in a name for these Normalization rules
(i.e. Verizon Users) and the Normalization rules for the phone numbers you wish this device to handle.
Figure 2-33: New Normalization Rules Option
Configuration Note 34 Document #: LTRT-31902
Configuration Note 2. Configuring Lync Server 2010
8.
In this example, we created the follow Normalization Rules:
Figure 2-34: Normalization Rules
Version 6.2
9.
Example (and Translation) of Normalization Rules:
•
Call to Operator:
Dial exactly ‘0’ the rule add ‘+1’ Lync will send to the
GW ‘+10’.
•
Call to International Operator:
Dial exactly ‘00’ the rule add ‘+1’ Lync will send to the GW ‘+100’.
•
Call to Operator with Local Area Number:
Dial number that start with ‘0’ and more 7 digits (‘0xxxxxxx’), the rule add ‘+1’ Lync will send to the GW
‘+10xxxxxxx’.
•
Call to Operator with Local Number:
Dial number that start with ‘0’ and more 11 digits (‘0xxxxxxxxxxx’), the rule add ‘+1’ Lync will send to the GW
‘+10xxxxxxxxxxx’.
•
3 Digits:
Dial 3 digits (‘xxx’) the rule add ‘+1’ Lync will send to the GW
‘+1xxx’. This rule using for emergency call (e.g., 911).
• 1411: Dial exactly ‘1411’ the rule add ‘+1’ Lync will send to the GW
‘+11411’.
•
In Site call:
Dial 4 digits (‘xxxx’) the rule complete the number to E-164 standard number and add ‘+1719313’ This rule affect only in site calls and not sending to the GW.
•
Local Area Call:
Dial 7 digits (‘xxxxxxx’) the rule add ‘+1719’ Lync will send to the GW ‘+1719xxxxxxx’.
35 April 2012
Lync Server 2010 and Verizon SIP Trunk
•
US Call:
Dial 10 digits (‘xxxxxxxxxx’) the rule will add ‘+1’ Lync will send to the GW ‘+1xxxxxxxxxx’.
•
Prefix All:
Dial 11 digits (‘xxxxxxxxxxx’) the rule will add ‘+’
‘+1xxxxxxxxxx’ will send to the GW.
•
Call to Operator with International Number:
Dial 8 or more digits that starting with ‘01’ (‘01xxxxxxxxxxxx’) the rule add ‘+1’ ‘+101xxxxxxxxxxxx’ will send to the GW.
•
International:
Dial 9 or more digits (‘xxxxxxxxxxx’) the rule add ‘+011’
‘+011xxxxxxxxxxx’ will send to the GW.
10.
Example of Normalization Rules:
Figure 2-35: Example: Normalization Rules
Configuration Note 36 Document #: LTRT-31902
Configuration Note
2. Configuring Lync Server 2010
•
Name:
The Rule name.
•
Description:
Rule description.
•
Starting digits:
The Digit/s Number/s that the Normalization Rule starting.
•
Length:
Three options: ‘At Least’, ‘Exactly’, and ‘Any’. And then the numbers of dial digits (e.g., exactly 1 digit).
•
Digits to remove:
The number of Digits that need to remove from the dialed number. (e.g., Don’t remove digits)
•
Digits to add:
The number of Digits that need to add to the dialed number.
(e.g., add ‘+1’ as prefix)
•
Pattern to match:
This field automatic filled, based on the previous fields.
•
Translation rule:
This field automatic filled, based on the previous fields.
•
Dialed number to test:
Use for test the rule before approve it.
11.
Gateway number manipulation. The number manipulation configuration of the
AudioCodes device is later described in Section
Version 6.2 37 April 2012
2.5
Lync Server 2010 and Verizon SIP Trunk
Enabling Voice Mail in the Exchange Server
This section describes how to enable voice mail for the user on the Exchange Server.
to enable user for voice mail in the Exchange Server:
1.
Open the Exchange Management Console.
Figure 2-36: Exchange Management Console
2.
In the Navigation pane, select the 'Recipient Configuration >> Mailbox' Tree folder.
3.
Select user for enabling voice mail from the list.
4.
From the dropdown list, right-click on the selected user and choose Enable
Unified Messaging
.
Figure 2-37: Mailbox – Entire Forest
Configuration Note 38 Document #: LTRT-31902
Configuration Note 2. Configuring Lync Server 2010
The Enable Unified Messaging Wizard – Introduction screen is displayed.
Figure 2-38: Enable Unified Messaging
Version 6.2
5.
In the new dialog pane, click the Browse button; the Select UM Mailbox Policy dialog is displayed.
Figure 2-39: Select UM Mailbox Policy
6.
Select ACint Default Policy.
39 April 2012
Lync Server 2010 and Verizon SIP Trunk
7.
Click Next; the Enable Unified Messaging Wizard – Extension Configuration screen is displayed.
Figure 2-40: Enable Unified Messaging Wizard – Extension Configuration
Configuration Note 40 Document #: LTRT-31902
Configuration Note 2. Configuring Lync Server 2010
8.
Click Next; the Enable Unified Messaging Wizard Configuration Summary screen is displayed.
Figure 2-41: Enable Unified Messaging Wizard – Configuration Summary
Version 6.2 41 April 2012
Lync Server 2010 and Verizon SIP Trunk
9.
Click Enable; the Enable Unified Messaging Wizard – Completion screen is displayed.
Figure 2-42: Enable Unified Messaging Wizard – Completion
10.
Click Finish.
Configuration Note 42 Document #: LTRT-31902
Configuration Note
2.6
2. Configuring Lync Server 2010
Enabling User for Lync Voice
This section describes how to enable Lync Voice Mail for a specific Lync user.
To enable Lync Voice Mail:
1.
Open the Lync Server 2010 (Start menu > Programs > Microsoft Lync Server
2010 > Lync Server Control Panel); the CSCP Home page is displayed.
Figure 2-43: CSCP Home page
2.
In the Navigation pane, select the ‘Users’ option.
Figure 2-44: Users Option
Version 6.2
3.
In the content area toolbar, click
43
.
April 2012
Lync Server 2010 and Verizon SIP Trunk
The New Lync Server User screen is displayed.
Figure 2-45: New Lync Server User
4.
In the Users: click ; the Lync search engine opens.
Figure 2-46: Lync Search Engine
Configuration Note 44 Document #: LTRT-31902
Configuration Note 2. Configuring Lync Server 2010
5.
Click for searching un-enable voice user in the Active Directory.
Figure 2-47: Search Un-enable Voice Users
6.
Select one of the users from the list and click OK.
Version 6.2 45 April 2012
Lync Server 2010 and Verizon SIP Trunk
Figure 2-48: User Properties
7.
In the 'Assign users to a pool' field, select the Pools that you working with it.
8.
In the 'Generate user's SIP URI' field, select the format.
9.
In the 'Telephony' field, select Enterprise Voice.
10.
In the 'Line URI' field, add the tel:<phone number> (e.g., tel:17193135665).
11.
In the 'Dial plan policy' field, select the dial plan.
12.
In the 'Voice policy' select the voice policy.
13.
Click Enable.
Configuration Note 46 Document #: LTRT-31902
Configuration Note
3
3. Configuring AudioCodes Gateway
Configuring AudioCodes Gateway
This section provides step-by-step procedures for configuring AudioCodes' gateway.
These procedures are based on the setup example described in the following sections.
The steps for configuring the gateway can be summarized as follows:
Step 1
: Configure IP Addresses. See Section
Step 2
: Enable the SBC Capabilities. See Section
on page
Step 3
: Configure the Number of Media Channels. See Section 3.3
on page
Step 4
: Configure the Proxy Sets. See Section
Step 5
: Configure the IP Groups. See Section
Step 6
: Configure the Voice Coders. See Section 3.6 on page 62.
Step 7
: Define Silence Suppression and Comfort Noise. See Section
Step 8
: Configure IP Profile Settings. See
Step 9:
Configure Header Manipulation for Call Forwarding. See Section
on page
Step 10
: Configure Unscreened ANI for P-Asserted Identity. See Section 3.10
on
Step 11
: Configure IP-to-IP Routing Setup. See Section
on page
Step 12
: Configure Number Manipulation. See
Step 13
: Configuring SIP General Parameters. See Section 3.13 on page 81 .
Step 14
: Configuring SIP Supplementary Services. See Section 3.14 on page 83 .
Step 15
: Defining Reasons for Alternative Routing (see Section 3.15
on page
Step 16
: Configuring Call Progress Tones file for Regional support (see
The procedures described in this section are performed using the gateway's Webbased management tool (i.e., embedded Web server). Before you begin configuring the gateway, ensure that the Web interface's Navigation tree is in full menu display mode (i.e., the Full option on the Navigation bar is selected), as displayed below:
Version 6.2 47 April 2012
Lync Server 2010 and Verizon SIP Trunk
Figure 3-1: Web Interface Showing Basic/Full Navigation Tree Display
Configuration Note 48 Document #: LTRT-31902
Configuration Note
3.1
3.1.1
3. Configuring AudioCodes Gateway
Step 1: Configuring IP Addresses
This section describes how to configure the IP addresses of the MSBG devices’ LAN and WAN interfaces.
LAN and WAN Interface Separation
This section describes how to configure IP addresses when the internal data-routing capabilities of the MSBG device are used in order to connect to the Verizon Business
SIP Trunk. In this case, you must configure a separate WAN interface as shown in the figure below.
Notes:
• The VoIP and Management interface must be in the same subnet as the data-routing interface as shown in the figure below.
• When operating with both VoIP and data-routing functionalities, it is recommended to define the Default Gateway IP address for the VoIP network interface in the same subnet and with the same VLAN ID as the
IP address for the data-routing LAN interface as shown in the figure below.
Figure 3-2: Physical Interface Separation
Version 6.2 49 April 2012
3.1.1.1
Lync Server 2010 and Verizon SIP Trunk
Configuring the LAN IP Addresses
This section describes how to assign the LAN IP addresses.
To assign a LAN VoIP and Management IP address using the Web interface:
1.
Open the ‘IP Settings’ page (Configuration tab > VoIP menu > Network sub-menu > IP Settings).
2.
Select the 'Index' radio button corresponding to the Application Type "OAMP +
Media + Control
(i.e., VoIP and management interface), and then click Edit.
3.
Configure the new IP address and prefix length so that it corresponds to your network IP addressing scheme (e.g., 10.15.4.30).
4.
Configure additional IP interfaces, if required.
Figure 3-3: Multiple Interface Table Page
5.
Click Apply, and then Done to apply and validate settings. If validation fails, the
MSBG device does not reboot.
6.
Save your settings to flash memory and reset the MSBG device.
Configuration Note 50 Document #: LTRT-31902
Configuration Note 3. Configuring AudioCodes Gateway
To define the MSBG device's LAN data-routing IP address:
1.
Access the MSBG device's Web interface with the IP address that you assigned to the VoIP and Management interface.
2.
Access the 'Connections' page (Configuration tab > Data menu > Data System >
Connections
).
Figure 3-4: Connections Page
3.
Click the Edit icon corresponding to the "LAN Switch VLAN 1" connection, and then click the Settings tab.
4.
In the 'IP Address' and 'Subnet Mask' fields, enter the required IP address (e.g.,
10.15.4.31) and subnet respectively, and then click OK.
Figure 3-5: Defining LAN Data-Routing IP Address
Version 6.2 51 April 2012
3.1.1.2
Lync Server 2010 and Verizon SIP Trunk
Assigning WAN IP Addresses
This section describes how to assign the WAN IP addresses.
To assign a WAN IP address:
1.
Cable the MSBG device to the WAN network (i.e., ADSL or Cable modem), using the WAN port.
2.
Access the MSBG device's Web interface with the Voice and Management IP address.
3.
Access the 'Settings' page (Configuration tab > Data menu > WAN Access >
Settings
tab).
Figure 3-6: Configuring the WAN IP Address
4.
From the 'Connection Type' drop-down list, select the required connection type for the WAN, and then configure the IP address (e.g., 195.189.192.138).
To assign a WAN interface for VoIP traffic:
1.
Select the WAN interface.
2.
Open the 'Multiple Interface Table' page (Configuration tab > VoIP menu >
Network
sub-menu > IP Settings).
Figure 3-7: Selecting WAN Interface for VoIP Traffic in Multiple Interface Table Page
3.
From the 'WAN Interface Name' drop-down list, select the WAN interface for VoIP traffic.
4.
Click Done, and then reset the MSBG device for your setting to take effect.
Configuration Note 52 Document #: LTRT-31902
Configuration Note
3.1.2
3. Configuring AudioCodes Gateway
Single LAN Interface
This section describes how to configure IP addresses when a single LAN interface is used to connect to the Verizon Business SIP Trunk. In this configuration, the internal data-routing capabilities of the MSBG device are not used as shown in the figure below. As a c onsequence, you must disable the internal data-routing interface as described in the procedure below.
Figure 3-8: Single LAN Interface
Note:
When operating in LAN VoIP-only mode, do not use the MSBG device’s
WAN port.
To operate the MSBG device as a LAN VoIP gateway only:
1.
Disconnect the network cable from the WAN port and then connect one of the
MSBG device’s LAN ports to the network.
2.
Disable or remove the data-routing IP network interface:
• Access the ‘Connections’ page (Configuration tab > Data menu > Data
System
> Connections).
• Delete the “LAN Switch VLAN 1” connection by clicking the corresponding
Remove
button, and then clicking OK to confirm deletion.
Figure 3-9: Removing Data-Routing Connection Interface
Version 6.2 53 April 2012
Lync Server 2010 and Verizon SIP Trunk
3.
Configure VoIP IP network interfaces in the ‘Multiple Interface’ table (Configuration tab > VoIP menu > Network > IP Settings).
4.
In the ‘Multiple Interface’ table, define a single IP network interface for application types “OAMP + Media + Control”.
Figure 3-10: Multiple Interface Table
5.
Click OK to save settings.
Configuration Note 54 Document #: LTRT-31902
Configuration Note 3. Configuring AudioCodes Gateway
3.2 Step 2: Enabling the SIP SBC and IP2IP
Application
This step describes how to enable the gateway's SIP IP2IP application.
To enable the SIP SBC and IP2IP application:
1.
Open the 'Application Enabling' page (Configuration tab > VoIP menu >
Applications Enabling
> Applications Enabling).
Figure 3-11: Application Enabling
2
2.
From the 'Enable SBC Application' and the 'Enable IP2IP Application' drop-down lists, select Enable.
Reset with BURN to FLASH is required.
Note:
To enable the SBC and IP2IP capabilities on the AudioCodes gateway, your gateway must be loaded with the feature key that includes the SBC feature and also the MSBG device must be running SIP version 6.2 or later.
Version 6.2 55 April 2012
3.3
Lync Server 2010 and Verizon SIP Trunk
Step 3: Configuring the Number of Media
Channels
In order to perform the coder transcoding, you need to define DSP channels. The number of media channels represents the number of digital signaling processors
(DSP) channels that the gateway allocates to IP-to-IP calls (the remaining DSP channels can be used for PSTN calls). Two IP media channels are used per IP-to-IP call. The maximum number of media channels available on the gateway is 120 (i.e., up to 60 IP-to-IP calls).
To configure the number of media channels:
1.
Open the 'IP Media Settings' page (Configuration tab > VoIP menu > IP Media >
IP Media Settings
).
Figure 3-12: IP Media Channels Settings
2
2.
In the 'Number of Media Channels parameter, enter 120 to enable up to 60 IP-to-
IP calls with transcoding; click Apply New Value.
Configuration Note 56 Document #: LTRT-31902
Configuration Note
3.4
3. Configuring AudioCodes Gateway
Step 4: Configuring the Proxy Sets
This step describes how to configure the Proxy Sets. The Proxy Sets represent the IP addresses (or FQDN), which are required for communicating with the entities in the network:
Proxy Set ID #1 is assigned with the IP address of Lync Mediation server.
Proxy Set ID #2 is assigned with the IP address of Verizon Business SIP Trunk.
Proxy Set ID #3 is assigned with the IP address of ATA Media Gateway supporting the Fax machine.
These Proxy Sets are later assigned to IP Groups (see Section
To configure proxy sets:
1.
Open the 'Proxy Sets Table' page (Configuration tab > VoIP menu > Control
Network
> Proxy Sets Table).
2.
Configure the Proxy Set for Lync Mediation Server:
a.
From the 'Proxy Set ID' drop-down list, select 1.
b.
In the 'Proxy Address' column, enter the IP address or FQDN and the listening port of the Lync Mediation Server.
c.
From the 'Transport Type' drop-down list, corresponding to the IP address entered above, select TCP or TLS depending on the deployed Mediation
Server Transport Type.
Figure 3-13: Proxy Set ID 1 for Lync Mediation server
2a
2b
2c v
Version 6.2 57 April 2012
Configuration Note
Lync Server 2010 and Verizon SIP Trunk
3.
Configure the Proxy Set for the Verizon Business SIP Trunk:
a.
From the 'Proxy Set ID' drop-down list, select 2.
b.
In the 'Proxy Address' column, enter the IP address or the FQDN of the
Verizon Business SIP Trunk and the listening port of the Verizon Business SIP
Trunk.
c.
From the 'Transport Type' drop-down list corresponding to the IP address entered above, select UDP.
Figure 3-14: Proxy Set ID 2 for Verizon Business SIP Trunk
3a
3b 3c
4.
Configure the Proxy Set for the Fax supporting Media Gateway:
a.
From the 'Proxy Set ID' drop-down list, select 3.
b.
In the 'Proxy Address' column, enter the IP address or the FQDN and the listening port of the Fax Supporting Media Gateway.
c.
From the 'Transport Type' drop-down list corresponding to the IP address entered above, select UDP Transport Type.
Figure 3-15: Proxy Set ID 3 for Fax Supporting Media Gateway
4a
4b
4c
58 Document #: LTRT-31902
Configuration Note
3.5
3. Configuring AudioCodes Gateway
Step 5: Configuring the IP Groups
This step describes how to create IP groups. Each IP group represents a SIP entity in the gateway's network. You need to create IP groups for the following entities:
Verizon Business SIP Trunk
Lync Server 2010 – Mediation Server
ATA - FAX Support via Analog Media Gateway.
These IP groups are later used by the IP2IP application for routing calls as well as the
SBC application for Header Manipulation.
To configure IP Groups:
1.
Open the 'IP Group Table' page (Configuration tab > VoIP menu > Control
Network
> IP Group Table).
2.
Define IP Group #2 for the Verizon ITSP as follows:
a.
IP Group Index 2
b.
Type: SERVER
c.
Description: arbitrary name. (e.g., “Verizon”)
d.
Proxy Set ID: 2 (represents the IP address, configured in Section
on
for communicating with this IP Group).
e.
SIP Group Name: The SIP Request-URI host name used in INVITE messages sent to the IP Group, or the host name in the From header of
INVITE messages received from the IP Group. Enter the WAN IP address.
f.
IP Profile ID: 2: Different IP profile is used for the Verizon Business SIP
Trunk and the Mediation Server. See Section
Figure 3-16: IP Group 2 Table
2a
2b
2d
2e
2c
2c
2f
Version 6.2 59 April 2012
Lync Server 2010 and Verizon SIP Trunk
Figure 3-17: IP Group 1 Table Page
3a
3b
3d
3e
3c
3f
3.
Define IP Group #1 for Mediation Server as follows:
a.
Select IP Group Index 1
b.
Type: SERVER
c.
Description: <Free Description> (e.g., “Lync Mediation Server”)
d.
Proxy Set ID: 1
e.
SIP Group Name: The SIP Request-URI host name used in INVITE messages sent to the IP Group, or the host name in the From header of
INVITE messages received from the IP Group. Enter the Gateway Name.
f.
IP Profile ID: 0 (see Section
Figure 3-18: IP Group 3 Table Page
4a
4c
4b
4d
4f
Configuration Note 60 Document #: LTRT-31902
Configuration Note 3. Configuring AudioCodes Gateway
4.
Define IP Group #3 for supporting FAX Media Gateway as follows:
a.
Select IP Group Index 3.
b.
Type: SERVER
c.
Description: <Free Description> (e.g., “ATA”)
d.
Proxy Set ID: 3
e.
SIP Group Name: The SIP Request-URI host name used in INVITE messages sent to the IP Group, or the host name in the From header of
INVITE messages received from the IP Group. Enter the Gateway Name or leave blank for default.
f.
IP Profile ID: 3 (see Section 3.8 on page 65 ).
Version 6.2 61 April 2012
3.6
Lync Server 2010 and Verizon SIP Trunk
Step 6: Configuring the Voice Coders
This step describes how to configure the Voice Coders. Since the Mediation Server supports both the G.711A-law and G .711U-law voice coders, while the Verizon SIP trunk supports the G.729 and G.711U-law coders, you can configure a single coder table reference for both services by utilizing the G711U-law coder as a single voice
coder (see Figure 3-20) or you can create a m ore dynamic servicing interworking
based on commonality of supported vocoders via the default Coders and Coders
Group tables (see Figure 3-19).
The Coder table is associated with the following IP Profiles:
IP Profile index 1 and 3 (see Section 3.8
on page
65 ) references ‘Coders Table’
3-19) which is associated with the IP Groups 1 and 3 (see Section 3.5
on page
IP Profile index 2 (see Section
on page
65 ) references ‘Coder Group 1’ (see
3-20), which is associated with IP Group 2 (see Section 3.5
on page
To configure Coder Table for Mediation Server and in-band FAX usage:
1.
Open the 'Coders Table' page (Configuration tab > VoIP menu > Coders And
Profiles
> Coders).
Figure 3-19: Coders Table – Lync Mediation Server
3
5
4
6
2.
From the 'Coders Table', select via the drop-down list, coder and attributes in the manner of preference with the first entry as being the preferred entry, and all others following in descending order.
3.
Select the G.711U-law coder, as shown in the figure above.
4.
From ‘Silence Suppression’ drop-down list, select Enable or Disabled as shown in the figure above.
5.
Select the G.711 A-law coder, as shown in the figure above.
6.
From ‘Silence Suppression’ drop-down list, select Enable or Disabled as shown in the figure above.
Configuration Note 62 Document #: LTRT-31902
Configuration Note 3. Configuring AudioCodes Gateway
To configure Coder Table for Verizon SIP Trunk usage:
1.
Open the 'Coders Table' page (Configuration tab > VoIP menu > Coders And
Profiles
> Coders Group Settings).
Figure 3-20: Coder Group Table 1 – Verizon SIP Trunk
2
3 4
2.
From the ‘Coder Group Setting’ table, select via drop-down list, the index 1. This index, 1, is referenced by the datafill of parameter 'Coders Group index' of IP
Profile index 2. This allows a user to list the allowed vocoders in a supported group to be referenced and utilized. This points to table 'Coder Group' for IP
Profile index 2, where Coder Group 1 is explicitly referenced. As shown above,
Coder Group 1 is declared to support G.729 and G.711U-law.
3.
Select the G.729 and G.711U-law coder, in the specific order as shown in the figure above. This will be the preference as advertised in the SDP for proper
‘Offer/Answer’ interworking.
4.
From ‘Silence Suppression’ drop-down list, select Enabled or Disabled as shown in the figure above.
Version 6.2 63 April 2012
3.7
Lync Server 2010 and Verizon SIP Trunk
Step 7: Defining Silence Suppression and Comfort
Noise
Overall voice quality has been significantly improved for the Microsoft Lync 2010 environment. These improvements include suppression of typing noise during calls and improved generation of “comfort noise,” which reduces hissing and smoothes over the discontinuous flow of audio packets. You may need to change the MSBG Silence
Suppression and Comfort Noise parameters to achieve this goal. Note that the Echo canceller is enabled by default.
To configure silence suppression parameters:
1.
Silence Suppression is configured per coder type. (See Section 3.6 on page 62
above to enable Silence Suppression per coder.)
2.
Open the 'RTP/RTCP Settings' page (Configuration tab > Media menu > RTP /
RTCP Settings
).
Figure 3-21: RTP/RTCP Settings Page
3
3.
From the 'Comfort Noise Generation Negotiation' drop-down list, select Enable.
This enables negotiation and usage of Comfort Noise (CN).
4.
Click Submit.
Configuration Note 64 Document #: LTRT-31902
Configuration Note
3.8
3. Configuring AudioCodes Gateway
Step 8: Configuring IP Profile Settings
This section describes how to configure the IP Profile Settings.
To configure IP Profile for Verizon SIP Trunk Server :
1.
Open the 'IP Profile Settings' page (Configuration tab > VoIP menu > Coders
and Profiles
> IP Profile Settings).
Figure 3-22: IP Profile Page-Verizon SIP Trunk Server
2
3
Version 6.2
2.
From the ‘Profile ID’ drop-down list, select 2.
3.
From the ‘Coder Group’ drop-down list, select Coder Group 1.
65 April 2012
Lync Server 2010 and Verizon SIP Trunk
To configure IP Profile for FAX supporting ATA:
1.
Open the 'IP Profile Settings' page (Configuration tab > VoIP menu > Coders
and Profiles
> IP Profile Settings).
Figure 3-23: IP Profile Page-FAX Supporting ATA
2
3
4
5
2.
From the ‘Profile ID’ drop-down list, select 3.
3.
From the ‘Fax Signaling Method’ drop-down list, select G.711 Transport.
Configuration Note 66 Document #: LTRT-31902
Configuration Note 3. Configuring AudioCodes Gateway
4.
From the ‘Media Security Behavior’ drop-down list, select one of the following options:
•
Mandatory
if Mediation Server is configured to SRTP Required
•
Preferable-Single media
if Mediation Server is configured to SRTP
Optional.
•
Disable
if the Mediation Server is configured to SRTP disabled.
5.
From the ‘Coder Group’ drop-down list, select Default Coder Group. The call associated with this profile utilizes the base coders that were assigned in the
'Coders' table as opposed to coders that were assigned via an index into the
Coder Group Table. The usage of G.711 U-law coder will be based on the previous datafill.
Version 6.2 67 April 2012
3.9
Lync Server 2010 and Verizon SIP Trunk
Step 9: Configuring Message Manipulation for Call
Forwarding
This step describes how to configure Message Manipulation for Call Forwarding.
To configure SBC Header Manipulation Rules:
1.
Open the Manipulation Table page (Configuration tab > VoIP menu > SBC >
Manipulations SBC
> Message).
Figure 3-24: Message Manipulations Table
2. Index #0
defines manipulation of calls to modify a header. For any request received modify the Header.Diversion.URL.host with ‘195.189.192.138’
3. Index #1
defines manipulation of calls to add a header. For any Invite request received and IF a Referred-by header exists, then Add the Diversion Header with what was received within the referred-by header, '<'+header.referred-by.URL+'>'.
Each of these rules bind to a specific Manipulation Set ID as represented within this table. Indexes 0 binds to Manipulation Set ID 0 and Index 1 is bound to Manipulation
Set ID 1.
Note the following:
Index 0
was created for a specific call scenario where a PSTN user originated a call on the Verizon SIP Trunk to an Lync 2010 DID, which has its DID forwarded to the PSTN as well as have its presentation Restricted in the Source number manipulation tables. This was set to change the Diversion URL host from
'anonymous.invalid' to ‘195.189.192.138’, which is the WAN address of the device.
Index 1
is utilized to dynamically capture the original dialed number for Lync DIDs and present them back to Sprint when a call is forwarded back to the PSTN when creating a Diversion Header. This functionality can only be used if Lync Server
2010 is set up to send Referred-by headers. This specific index creates a new
Diversion header for the call using what was presented in the Referred-by header, thus allowing the Verizon service to receive the original dialed DID extension that forwarded the call back to the PSTN SIP trunk.
Configuration Note 68 Document #: LTRT-31902
Configuration Note 3. Configuring AudioCodes Gateway
These newly created message manipulation sets can now be assigned for use. There are several methods to perform this function. One method is to assign the functionality to the entire application via the ini file or via the AdminPage.
This functionality is configured using the parameters
GWINBOUNDMANIPULATIONSET = [1] and GWOUTBOUNDMANIPULATIONSET =
[-1].
When using these parameter settings, the respective Manipulation Set ID is assigned for all inbound and outbound manipulations. When using the IP to IP application, such as in this example, the manipulation for inbound messages must be performed at the gateway level, so therefore set GWINBOUNDMANIPULATIONSET = 1. The outbound message manipulation can be performed either at the gateway level or more dynamically, at the IP Group level.
This section describes the following procedures:
Assign inbound manipulation to the entire gateway via the ini file or via the
AdminPage. See Section 0 below.
Assign outbound manipulation to a specific IP group index. See Section 3.9.2
below.
Version 6.2 69 April 2012
3.9.1
Lync Server 2010 and Verizon SIP Trunk
Assigning Inbound Message Manipulation Set to Entire
Gateway
This step describes how to assign a message manipulation set to the entire gateway via the INI file.
This assignment is configured using the parameters
GWINBOUNDMANIPULATIONSET = [1] and GWOUTBOUNDMANIPULATIONSET =
[-1]. These parameter settings are applied for all inbound and outbound manipulations respectively. For IP2IP applications, GWINBOUNDMANIPULATIONSET must be used for header manipulation requirements on incoming messages.
To assign inbound message manipulation set to gateway:
1.
Open the Admin page, by appending the case-sensitive suffix ‘AdminPage’ to the
Media gateway's IP address in your Web browser's URL field (e.g., http://10.15.9.118/AdminPage ).
2.
On the left pane, click ini Parameters.
Figure 4-30: Output Window
2.
In the 'Parameter Name' field, enter GWINBOUNDMANIPULATIONSET or
GWOUTBOUNDMANIPULATIONSET
.
3.
In the 'Enter Value' field, enter the respective Manipulation Set ID you wish for the specific direction. e.g., 1.
4.
Click Apply New Value (GWINBOUNDMANIPULATIONSET should be s et to 1 for proper interworking).
Configuration Note 70 Document #: LTRT-31902
Configuration Note
3.9.2
3. Configuring AudioCodes Gateway
Assigning Outbound Message Manipulation Set to an IP
Group
This step describes how to assign outbound message manipulation rules to IP groups to support outbound message manipulation. Each IP group represents a SIP entity in the gateway's network. You may assign manipulation rules to IP groups for the Verizon
SIP Trunk entity.
When completed, the IP group is used by the IP2IP, as well as the SBC application for routing calls with advanced outbound header manipulation support.
To assign outbound message manipulation set to IP Group Table 2 (Verizon
SIP Trunk):
1.
Open the IP Group Table page (Configuration tab > VoIP menu > Control
Network
> IP Group Table).
Figure 3-25: IP Group Table 2 (Verizon SIP Trunk)
2
Version 6.2
3
4
2.
Set Index to 2.
3.
Set 'Inbound Message Manipulation Set' to -1. This means that the device does not perform message manipulation at this stage (for IP2IP applications, inbound message manipulation can only be performed at the gateway level).
4.
Set 'Outbound Message Manipulation Set' to 0.
71 April 2012
3.10
Lync Server 2010 and Verizon SIP Trunk
Step 10: Configuring Unscreened ANI using
P-Asserted Identity
This step describes how to support proper termination of an outbound call with the correct Caller ID when the Screened Telephone Number contained in the P-Asserted
Identity Header is different from the CLI contained in the From Header.
This functionality is required to support TC16 of VIT.2010.03154.TPL.001 ‘Test Suite for Retail VoIP Interoperability IP Trunking’ for the Verizon North American retail market.
To configure P-Asserted Identity for Unscreened ANI:
1.
Open the 'Admin' page by appending the case-sensitive suffix 'AdminPage' to the
Media Gateway's IP address in your Web browser's URL field (e.g., http://10.15.4.15/AdminPage).
2.
On the left pane, click ini Parameters.
Figure 3-26: Output Window
3.
In the 'Parameter Name' field, enter the parameter PASSERTEDUSERNAME. In the 'Enter Value' field, enter “7193135662” or any valid number which will be utilized in the P-Asserted Identity header.
4.
Click Apply New Value.
Configuration Note 72 Document #: LTRT-31902
Configuration Note 3. Configuring AudioCodes Gateway
3.11
3.11.1
Step 11: Configuring IP-to-IP Routing Setup
The MSBG’s IP-to-IP call routing capabilities is performed in two stages:
Inbound IP Routing:
Recognizes the received call as an IP-to-IP call, based on the call's source IP address. This stage is configured in the 'Inbound IP Routing
Table'
Outbound IP Routing:
Once recognized as an IP-to-IP call in the first stage (see above), the call is routed to the appropriate destination (i.e., IP address). This stage is configured in the 'Outbound IP Routing Table'.
Configure Inbound IP Routing
This step defines how to configure the MSBG for routing inbound (i.e., received) IP-to-
IP calls to the Microsoft Lync network.
To configure in bound IP routing:
1.
Open the 'Inbound IP Routing Table' page (Configuration tab > VoIP menu >
GW and IP to IP
> Routing sub-menu > IP to Trunk Group Routing).
Figure 3-27: Inbound IP Routing Table
Page
2
3
4
5
Version 6.2
2. Index #1
configuration identifies all IP calls received from FAX supporting ATA as
IP-to-IP calls and assigns them to the IP Group ID configured for the Verizon
Business SIP Trunk:
•
Dest Phone Prefix
: Enter the asterisk (*) symbol to indicate all destinations.
•
Source IP Address
: Enter the IP address of ATA device.
•
Trunk Group ID
: Enter -1 to indicate that these calls are IP-to-IP calls.
•
IP Profile ID
: Enter 3 to indicate the IP Profile for interworking G.711 in-band fax support to Verizon Business SIP Trunk.
•
Source IP Group ID
: Enter 3 to assign these calls to the IP Group pertaining to the ATA supporting fax services.
73 April 2012
Lync Server 2010 and Verizon SIP Trunk
3. Index #2
configuration identifies all IP calls received from the Verizon Business
SIP Trunk in the event of determining a route for a dedicated FAX line call
Scenario as IP-to-IP calls. It then assigns these IP calls to the IP Group ID configured for the FAX supporting ATA and also assigns a specific IP Profile to support the FAX call.:
•
Source Host Prefix
: Enter the asterisk (*) symbol to indicate all destinations.
•
Dest Phone Prefix
: Enter the asterisk (*) symbol to indicate all destinations.
• Source Phone Prefix: Enter the specific DID assigned to support FAX services.
•
Source IP Address
: Enter the IP address of Verizon SIP Trunk Server.
•
Trunk Group ID
: Enter -1 to indicate that these calls are IP-to-IP calls.
•
IP Profile ID
: Enter 3 to indicate that the IP Profile supports the fax call for
G.711 in-band service.
•
Source IP Group ID
: Enter 2 to assign these originated calls to the IP Group pertaining to the Verizon SIP Trunk server.
4. Index #3
configuration identifies all IP calls received from the Mediation Server as
IP-to-IP calls and assigns them to the IP Group ID configured for the Lync
Mediation Server:
•
Dest Phone Prefix
: Enter the asterisk (*) symbol to indicate all destinations.
• Source Phone Prefix: Enter asterisk (*) symbol to indicate all sources.
•
Source IP Address
: Enter the IP address of the Mediation server.
•
Trunk Group ID
: Enter -1 to indicate that these calls are IP-to-IP calls.
•
IP Profile ID
: Enter 0 indicate the IP Profile for Mediation server.
•
Source IP Group ID
: Enter 1 to assign these calls to the IP Group pertaining to the Lync Mediation server.
5. Index #4
configuration identifies all IP calls received from Verizon Business SIP
Trunk as IP-to-IP calls and assigns them to the IP Group ID configured for the
Verizon Business SIP Trunk:
•
Dest Phone Prefix
: Enter the asterisk (*) symbol to indicate all destinations.
•
Source IP Address
: Enter the IP address of Verizon Business SIP Trunk.
•
Trunk Group ID
: Enter "-1" to indicate that these calls are IP-to-IP calls.
•
IP Profile ID
: Enter ‘2’ indicate the IP Profile for Verizon Business SIP Trunk.
•
Source IP Group ID
: Enter "2" to assign these calls to the IP Group pertaining to Verizon Business SIP Trunk.
Configuration Note 74 Document #: LTRT-31902
Configuration Note 3. Configuring AudioCodes Gateway
3.11.2 Configuring Outbound IP Routing
This step defines how to configure the gateway for outbound routing (i.e., sent) IP-to-
IP calls to the Verizon Business SIP Trunk.
To configure outbound IP routing:
1.
Open the 'Outbound IP Routing Table' page (Configuration tab > VoIP menu >
GW and IP to IP
> Routing sub-menu > Tel to IP Routing).
Figure 3-28: Outbound IP Routing Table Page
2
3
4
5
2. Index #1
defines the routing of IP calls to the Verizon Business SIP Trunk. All calls received from IP Group ID 1 (i.e., Lync 2010 Mediation server) are routed to
Destination IP Group ID 2 (i.e., Verizon Business SIP Trunk):
•
Source IP Group ID
: Select 1 to indicate received (inbound) calls identified as belonging to the IP Group configured for the Lync 2010 Mediation Server.
•
Dest Phone Prefix
: Enter the asterisk (*) symbol to indicate all destinations.
•
Source Phone Prefix
: Enter the asterisk (*) symbol to indicate all callers.
•
Dest IP Group ID
: Select 2 to indicate the destination IP Group to where the calls must be sent, i.e., to the Verizon Business SIP Trunk.
•
IP Profile
: Select 2 to indicate usage of IP Profile supporting Verizon coder preference.
3. Index #2
defines the routing of FAX IP calls to the Verizon Business SIP Trunk.
All calls received from IP Group ID 3 (i.e., ATA support FAX) are routed to
Destination IP Group ID 2 (i.e., Verizon Business SIP Trunk):
•
Source IP Group ID
: Select 3 to indicate received (inbound) calls identified as belonging to the IP Group configured for the ATA supporting FAX service.
•
Dest Phone Prefix
: Enter the asterisk (*) symbol to indicate all destinations.
•
Source Phone Prefix
: Enter the asterisk (*) symbol to indicate all callers.
•
Dest
IP Group ID: Select 2 to indicate the destination IP Group to where the calls must be sent, i.e., to the Verizon Business SIP Trunk
•
IP Profile
: Select 3 to indicate usage of IP Profile supporting Fax.
Version 6.2 75 April 2012
Lync Server 2010 and Verizon SIP Trunk
4. Index #3
defines routing of FAX IP calls to the ATA supporting FAX. All calls received from Source IP Group ID 2 (i.e., from the Verizon Business SIP Trunk) are matched against assigned FAX DIDs and then routed to Destination IP Group
ID 3 (i.e., to ATA supporting FAX services):
•
Source IP Group ID
: Select 2 to indicate received (inbound) calls identified as belonging to the IP Group configured for the Verizon Business SIP Trunk.
•
Dest Phone Prefix
: Enter the assigned Verizon DID associated with the customers fax services.
•
Source Phone Prefix
: Enter the asterisk (*) symbol to indicate all callers.
•
Dest IP Group ID
: Select 3 to indicate the destination IP Group to where the calls must be sent, i.e., to ATA supporting FAX services.
•
IP Profile
: Select 3 to indicate usage of IP Profile supporting Fax.
5. Index #4
defines routing of IP calls to the Lync 2010 Mediation server. All calls received from Source IP Group ID 1 (i.e., from the Verizon Business SIP Trunk) are routed to Destination IP Group ID 2 (i.e., to Lync 2010 Mediation server):
•
Source IP Group ID
: Select 2 to indicate received (inbound) calls identified as belonging to the IP Group configured for the Verizon Business SIP Trunk.
•
Dest Phone Prefix
: Enter the asterisk (*) symbol to indicate all destinations.
•
Source Phone Prefix
: Enter the asterisk (*) symbol to indicate all callers.
•
Dest IP Group ID
: Select 1 to indicate the destination IP Group to where the calls must be sent, i.e., to Lync 2010 Mediation server.
•
IP Profile
: Select 0 to indicate no special usage of IP Profile. Instead, service will be selected from the base provisioning such as ‘Coders’.
Configuration Note 76 Document #: LTRT-31902
Configuration Note
3.12
3. Configuring AudioCodes Gateway
Step 12: Configuring Number Manipulation
The Manipulation Tables sub-menu allows you to configure number manipulation and mapping of NPI/TON to SIP messages. This sub-menu includes the following options:
Dest Number Tel->IP. See Section 3.12.1
on page
Source Number Tel->IP. See Section
Redirect Number Tel->IP. See Section
Version 6.2 77 April 2012
Lync Server 2010 and Verizon SIP Trunk
3.12.1 Configuring Destination Phone Number Manipulation
This section describes how to configure the destination phone number manipulation.
To configure Destination Phone Number Manipulation Table for Tel -> IP Calls
Table:
1.
Open the ‘Destination Phone Number Manipulation Table for Tel -> IP calls’ page
(Configuration tab > VoIP menu > GW and IP to IP > Manipulations sub-menu
> Dest Number Tel > IP).
Figure 3-29: Destination Phone Number Manipulation Table for Tel -> IP Calls Page
•
Index #1
defines destination number manipulation of IP calls from Lync
Server 2010. All calls received from Source IP Group 1 (i.e., from Lync
Server 2010), where the destination number prefix begins with '+011', remove the ‘+’.
•
Index #2
defines destination number manipulation of IP calls from Lync
Server. All calls received from Source IP Group 1 (i.e., from Lync Server
2010), where the destination number prefix begins with '+1', remove the ‘+1’.
•
Index #3
defines destination number manipulation of IP calls from Lync
Server. All calls received from Source IP Group 1 (i.e., from Lync Server
2010), where the destination number prefix begins with '+', remove the ‘+’.
•
Index #4
defines destination number manipulation of IP calls from Verizon
Business SIP Trunk. All calls received from Source IP Group 2 (i.e., from
Verizon Business SIP Trunk), where the destination number prefix is ‘719’, add the ‘+1’ prefix to the number.
Configuration Note 78 Document #: LTRT-31902
Configuration Note 3. Configuring AudioCodes Gateway
3.12.2 Configuring Source Phone Number Manipulation
This section describes how to configure the source phone number manipulation.
To configure Source Phone Number Manipulation Table for Tel -> IP Calls
Table:
1.
Open the ‘Source Phone Number Manipulation Table for Tel -> IP calls’ page
(Configuration tab > VoIP menu > GW and IP to IP > Manipulations sub-menu
> Source Number Tel > IP).
Figure 3-30: Source Phone Number Manipulation Table for Tel -> IP Calls Page
•
Index #1
defines Source number manipulation of IP calls from any Source IP
Group, where the Source number or prefix begins with '+17193135662'. In this case, remove the ‘+1’ prefix from the number and set the Presentation to
Restricted. This enables the customer to set restricted presentation for a specific DID or range of DIDs.
•
Index #2
defines Source number manipulation of IP calls from any Source
IP, where the Source number prefix begins with '+1'. In this case, remove the
‘+1’ prefix from the number.
•
Index #3
defines Source number manipulation of anonymous calls from any
Source IP group. All calls received a Source number ‘anonymous’ are replaced with a known valid Verizon DID, such as ‘7193135662’ and the presentation should be set to ‘restricted’. This is a unique interworking to support the forwarding of calls originating from the PSTN and forwarded back to the PSTN when the original calling party was restricted. In this instance, the Lync Server 2010 sends the source as ‘anonymous’.
•
Index #4
defines Source number manipulation of IP calls from any Source IP
Group where the Source number prefix is a ‘+’. In this case, remove the ‘+’ prefix from the number.
Version 6.2 79 April 2012
3.12.3
Lync Server 2010 and Verizon SIP Trunk
Configuring Redirect Number Manipulation
In the event of a call forwarding scenario, a Diversion header needs to be added to the
INVITE towards the Verizon Business SIP Trunk (as configured in Section 3.9 on page
. In this case, the MSBG copies and adds the referred-by number to a newly created Diversion header. For a well known number in the Diversion header (for
Verizon Business SIP Trunk), a manipulation rule should be defined to remove the (+1) from the redirect number to be presented as a well known number derived from the
Referred-by header received from the Lync Server 2010 environment during the forwarding scenario.
To configure redirect number Tel -> IP Table:
1.
Open the ‘Redirect Number Tel -> IP’ page (Configuration tab > VoIP menu >
GW and IP to IP
> Manipulations sub-menu> Redirect Number Tel > IP).
Figure 3-31: Redirect Number Tel -> IP Page
•
Index #1 defines redirect number manipulation for the call forwarding scenario.
The redirect number is changed to remove the “+1” prefix from the number i.e.
“+17193133661” to “7193133661”.
Configuration Note 80 Document #: LTRT-31902
Configuration Note
3.13
3. Configuring AudioCodes Gateway
Step 13: Configuring SIP General Parameters
This section describes how to configure the SIP general parameters.
To configure general SIP parameters:
1.
Open the 'SIP General Parameters' page (Configuration tab > VoIP menu > SIP
Definitions
sub-menu > General Parameters).
Figure 3-32: SIP General Parameters Page
2
3
4
5
6
7
8
Version 6.2
9
2.
In the ‘NAT IP Address’ field, enter the Global (public) IP address of the MSBG device to enable the static NAT between the MSBG device and the Internet.
81 April 2012
Lync Server 2010 and Verizon SIP Trunk
3.
From the ‘Enable Early Media’ drop-down list, select Enable to enable early media.
4.
From the ‘Asserted Identity Mode’ drop-down list, select Adding PAsserted
Identity
.
5.
From the ‘SIP Transport Type’ drop-down list, select TCP in case the Mediation
Server is configured to use TCP transport Type.
6.
In the ‘SIP TCP Local Port’ field, enter 5068; this port is the listening MSBG port for TCP transport type. This port must match the transmitting port of the Mediation
Server.
7.
From 'Play Ringback Tone to Tel' drop-down list, select Play Local Until Remote
Media Arrive
. Plays the RBT according to the received media. If a SIP 180 response is received and the voice channel is already open (due to a previous
183 early media response or due to an SDP in the current 180 response), the
MSBG device plays a local RBT if there are no prior received RTP packets. The
MSBG device stops playing the local RBT as soon as it starts receiving RTP packets. At this stage, if the MSBG device receives additional 18x responses, it does not resume playing the local RBT.
8.
From the 'Forking Handling Mode' drop-down list, select Sequential handling; this parameter determines whether18x with SDP is received. In this case, the
E-SBC device opens a voice stream according to the received SDP. The MSBG device re-opens the stream according to subsequently received 18x responses with SDP.
9.
In the 'Fake Retry After' field, enter 60 sec. This parameter determines whether the MSBG device, upon receipt of a SIP 503 response without a Retry-After header, behaves as if the 503 response included a Retry-After header and with the period (in seconds) specified by this parameter.
10.
Open the 'Admin" page, by appending the case-sensitive suffix ‘AdminPage’ to the Media Gateway's IP address in your Web browser's URL field (e.g., http://10.15.4.15/AdminPage).
11.
On the left pane, click ini Parameters.
12.
In the 'Parameter Name' field, enter the parameter
IGNOREALERTAFTEREARLYMEDIA
. In the 'Enter Value' field, enter “1”.
13.
Click Apply New Value.
Figure 3-33: INI file Output Window
Configuration Note 82 Document #: LTRT-31902
Configuration Note
3.14
3. Configuring AudioCodes Gateway
Step 14: Configuring SIP Supplementary Services
This section describes how to configure the SIP general parameters.
To configure general SIP Supplementary Services parameters:
1.
Open the 'SIP General Parameters' page (Configuration tab > VoIP menu > GW
and IP 2 IP
sub-menu > DTMF and Supplementary sub-menu >
Supplementary Services
).
Figure 3-34: SIP Supplementary Services Page
2
3
4
5
6
2.
In the ‘Enable Hold’ drop-down list, select Enable.
3.
From the ‘Hold Format’ drop-down list, select 0.0.0.0 to enable Hold in the no media in either direction method or select Send Only to enable Hold to support one way audio for Music on Hold type service support.
4.
From the ‘Enable Transfer’ drop-down list, select Enable.
5.
From the ‘Enable Call Forward’ drop-down list, select Enable.
6.
In the ‘Enable Call Waiting’ drop-down list, select Enable.
Version 6.2 83 April 2012
3.15
Lync Server 2010 and Verizon SIP Trunk
Step 15: Defining Reasons for Alternative Routing
A 503 SIP response from the Mediation Server to an INVITE must cause the Media
Gateway to perform a failover. For this event to occur, you need to configure the
Reasons for Alternative Routing for Tel-to-IP calls to be a 503 SIP response.
To define SIP Reason for Alternative Routing:
1.
Open the 'Reasons for Alternative Routing' page (Configuration tab > VoIP menu
> GW and IP to IP > Routing sub-menu > Alternative Routing Reasons).
Figure 3-35: Reasons for Alternative Routing Page
2
2.
Under the Tel to IP Reasons group, for Reason 1, select 503.
3.
Click Submit.
4.
Open the ‘Proxy & Registration’ page (Configuration > VoIP > SIP Definitions >
Proxy & Registration
) and configure the 'Redundant Routing Mode’ parameter to
Proxy
as shown below.
Configuration Note 84 Document #: LTRT-31902
Configuration Note 3. Configuring AudioCodes Gateway
Figure 3-36: Proxy & Registration Page
4
Version 6.2 85 April 2012
Lync Server 2010 and Verizon SIP Trunk
3.16 Step 16: Supporting Regional Call Progress Tone
The 'Load Auxiliary Files' page allows you to load various auxiliary files to the device.
For Regional Call Progress Tones support, use the “Call Progress Tones file” area to select the appropriate regional file stored on your local computer to send to the device for proper support and interworking.
To load an auxiliary file to the device using the Web interface:
1.
Open the 'Load Auxiliary Files' page (Maintenance tab > Software Update menu >
Load Auxiliary Files
).
Figure 3-37:'Load Auxiliary Files Page
Note:
The appearance of certain file load fields depends on the installed Software
Upgrade Key.
Configuration Note 86 Document #: LTRT-31902
Configuration Note 3. Configuring AudioCodes Gateway
2.
Click the Browse button corresponding to the file type that you want to load, navigate to the folder in which the file is located, and then click Open; the name and path of the file appear in the field next to the Browse button.
3.
Click the Load File button corresponding to the file you want to load.
4.
Repeat steps 2 through 3 for each file you wish to load.
5.
Save the loaded auxiliary files to flash memory, and reset the device (if you have loaded a Call Progress Tones file).
Version 6.2 87 April 2012
Reader’s Notes
Lync Server 2010 and Verizon SIP Trunk
Configuration Note 88 Document #: LTRT-31902
Configuration Note
4
4.1
4.1.1
4. Troubleshooting
Troubleshooting
This section should provide some tips for troubleshooting problems, including troubleshooting commands and contact numbers within Vendor X’s Company for trouble escalation.
Debugging Procedures
This section discusses the following debugging procedures:
Case Reporting Procedures. See Section
below.
Syslog. See Section
Wireshark Network Sniffer. See Section 4.1.3 on page 92 .
Case Reporting Procedures
When reporting a problem to AudioCodes’ Technical Support department, the following information should be provided:
Basic information (required for all types of problems):
• Problem description (nature of failure, symptoms, call direction, etc.)
• Network diagram
•
ini
configuration file (downloaded to your PC from the device using the Web interface)
• Syslog trace (without missing messages)
•
Unfiltered IP network trace using the Wireshark application
(Note: If you are unable to collect all the network traffic, then at least collect the mandatory protocols SIP, RTP, and T38.)
Advanced information (if required upon request):
• PSTN message traces - for PSTN problems
• Media stream traces - for problems related to voice quality, modem\fax,
DTMF detection, etc.
Version 6.2 89 April 2012
4.1.2
Lync Server 2010 and Verizon SIP Trunk
Syslog
Syslog is a standard for forwarding log messages in an IP network. A syslog client, embedded in the device sends error reports/events generated by the device to a remote Syslog server using IP/UDP protocol. This information is a collection of error, warning and system messages that record every internal operation of the device. You can use the supplied AudioCodes proprietary Syslog server "ACSyslog" (shown in the figure below) or any other third-party Syslog server for receiving Syslog messages.
Figure 4-1: AudioCodes' Proprietary Syslog Server
To activate the Syslog client on the device using the Web interface:
1.
Open the 'Syslog Settings' page (Configuration tab > System menu > Syslog
Settings
).
2.
In the 'Syslog Server IP Address' field, enter the IP address of the Syslog server
(ini file parameter SyslogServerIP).
3.
From the 'Enable Syslog' drop-down list, select 'Enable' to enable the device to send syslog messages to a Syslog server (defined in Step 2).
Figure 4-2: Enabling Syslog
Configuration Note 90 Document #: LTRT-31902
Configuration Note 4. Troubleshooting
4.
From the 'Debug Level' drop-down list, select '5' if debug traces are required.
To enable syslog reporting, using the ini file, load an ini file to the device with the following settings:
Version 6.2 91 April 2012
4.1.3
Lync Server 2010 and Verizon SIP Trunk
Wireshark Network Sniffer
Wireshark is a freeware packet sniffer application that allows you to view the traffic that is being passed over the network. Wireshark can be used to analyze any network packets. Wireshark can also be u sed to analyze RTP data streams and extract the audio from the data packets (only for G.711). The audio can be saved as a *.pcm file.
To record traffic that is sent to / from the device:
1.
Install Wireshark on your PC. (You can download it from the following Web site: http://www.wireshark.org/
2.
Connect the PC and the device to the same hub.
3.
If you are using a switch, use a switch with port mirroring for the port to which the
Wireshark is connected.
4.
Start Wireshark.
5.
Select the network interface that is currently being used by the PC - on the toolbar,click Interfaces, and then in the 'Capture Interfaces' dialog box, click the
Options
button corresponding to the network interface:
Figure 4-3: Selecting Interface Currently used by the PC
Configuration Note 92 Document #: LTRT-31902
Configuration Note 4. Troubleshooting
6.
In the 'Capture Options' dialog box, select the desired display options:
Figure 4-4: Configuring Wireshark Display Options
Version 6.2 93 April 2012
7.
Click Start.
Lync Server 2010 and Verizon SIP Trunk
Figure 4-5: Captures Packets
8.
To view VoIP call flows, from the Statistics menu, choose VoIP Calls. You can view the statistics in graph format by clicking Graph.
Figure 4-6: Viewing VoIP Call Flows
Configuration Note 94 Document #: LTRT-31902
Configuration Note
9.
To play G.711 RTP streams, click the Player button.
Figure 4-7: Playing G.711 RTP Streams
4. Troubleshooting
10.
To analyze the RTP data stream and extract the audio (which can be played using programs such as CoolEdit) from the data packets (only for G.711), from the Statistics menu, point to RTP, and then choose Stream Analysis.
Figure 4-8: Analyzing the RTP Data
Version 6.2
a.
Save the audio payload of the RTP stream to a file.
b.
Save the Payload as a *.pcm file.
c.
Select the ‘forward’ option.
95 April 2012
4.2
Lync Server 2010 and Verizon SIP Trunk
Verifying Firmware
To verify the firmware load actively running on the device, log into the device and view the firmware version on the product homepage as shown in the figure below.
Figure 4-9: Viewing active firmware version
Configuration Note 96 Document #: LTRT-31902
Configuration Note
A
A.1
A. Configuring Analog Devices (ATA’s)
Configuring Analog Devices (ATA’s)
This section describes how to configure the analog device entity to route its calls to the
AudioCodes Media Gateway. The analog device entity must be configured to send all calls to the Media Gateway without any registration process.
Note:
The configuration described in this section is for ATA devices configured for
AudioCodes MP-11x series.
Step 1: Configure the Endpoint Phone Number
Table
The 'Endpoint Phone Number Table' page allows you to activate the MP-11x ports
(endpoints) by defining telephone numbers. The configuration below uses the example of ATA1 destination phone number ‘‘7193135664’’ (IP address 10.15.7.165) with all routing directed to the AudioCodes MSBG (10.15.4.30).
To configure the Endpoint Phone Number table:
Open the ‘Endpoint Phone Number Table’ page (Configuration tab > Protocol
Configuration
menu > Endpoint Number sub-menu > Endpoint Phone
Number
).
Figure A-1: Endpoint Phone Number Table Page
Version 6.2 97 April 2012
A.2
Lync Server 2010 and Verizon SIP Trunk
Step 2: Configure Tel to IP Routing Table
This step describes how to configure the Tel-to-IP routing rules to ensure that the
MP-11x device sends all calls to the AudioCodes central Media Gateway.
To configure the Tel to IP Routing table:
Open the 'Tel to IP Routing' page (Configuration tab > Protocol Configuration menu> Routing Tables sub-menu > Tel to IP Routing).
Figure A-2: Tel to IP Routing Page
Configuration Note 98 Document #: LTRT-31902
Configuration Note
A.3
A. Configuring Analog Devices (ATA’s)
Step 3: Configure Coders Table
This step describes how to configure the coders for the MP-11x device.
To configure MP-11x coders:
Open the 'Coders' page (Configuration tab > Protocol Configuration menu >
Coders And Profile Definition
sub-menu > Coders).
Figure A-3: Coders Table Page
Version 6.2 99 April 2012
A.4
Lync Server 2010 and Verizon SIP Trunk
Step 4: Configure SIP UDP Transport Type and
Fax Signaling Method
This step 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 > Protocol
Configuration
menu > Protocol Definition sub-menu > SIP General
Parameters
).
Figure A-4: SIP General Parameters Page
2
3
4
5
2.
From the ‘FAX Signaling Method’ drop-down list, select G.711 Transport.
3.
From the ‘SIP Transport Type’ drop-down list, select UDP.
4.
In the ‘SIP UDP Local Port’ field, enter 5060 (corresponding to the Central
Gateway UDP transmitting port configuration).
5.
In the ‘SIP Destination Port’, enter 5060 (corresponding to the Central Gateway
UDP listening port configuration).
Configuration Note 100 Document #: LTRT-31902
Configuration Note
Reader’s Notes
A. Configuring Analog Devices (ATA’s)
Version 6.2 101 April 2012
Configuration Note
Configuration Note
Connecting Microsoft® Lync™ and Verizon SIP-
Trunk using AudioCodes Mediant 1000 MSBG
www.audiocodes.com
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement
Table of contents
- 11 Components Information
- 11 AudioCodes Gateway Version
- 11 Verizon SIP Trunking Version
- 11 Microsoft Lync Server 2010 Version
- 12 Mediation Server Version
- 12 Microsoft Lync Client Version
- 13 Lync Server 2010 Specification
- 14 Topology
- 15 Configuring Lync Server
- 15 Configuring the Mediant 1000 MSBG as a 'IP/PSTN Gateway
- 19 Associating the ‘IP/PSTN Gateway’ with the Mediation Server
- 24 Configuring the ‘Route’ on the Lync Server
- 33 Configuring the ‘Dial Plan’ on the Lync Server
- 38 Enabling Voice Mail in the Exchange Server
- 43 Enabling User for Lync Voice
- 47 Configuring AudioCodes Gateway
- 49 Step 1: Configuring IP Addresses
- 49 LAN and WAN Interface Separation
- 50 Configuring the LAN IP Addresses
- 52 Assigning WAN IP Addresses
- 53 Single LAN Interface
- 55 Step 2: Enabling the SIP SBC and IP2IP Application
- 56 Step 3: Configuring the Number of Media Channels
- 57 Step 4: Configuring the Proxy Sets
- 59 Step 5: Configuring the IP Groups
- 62 Step 6: Configuring the Voice Coders
- 64 Step 7: Defining Silence Suppression and Comfort Noise
- 65 Step 8: Configuring IP Profile Settings
- 68 Step 9: Configuring Message Manipulation for Call Forwarding
- 70 Assigning Inbound Message Manipulation Set to Entire Gateway
- 71 Assigning Outbound Message Manipulation Set to an IP Group
- 72 Step 10: Configuring Unscreened ANI using P-Asserted Identity
- 73 Step 11: Configuring IP-to-IP Routing Setup
- 73 Configure Inbound IP Routing
- 75 Configuring Outbound IP Routing
- 77 Step 12: Configuring Number Manipulation
- 78 Configuring Destination Phone Number Manipulation
- 79 Configuring Source Phone Number Manipulation
- 80 Configuring Redirect Number Manipulation
- 81 Step 13: Configuring SIP General Parameters
- 83 Step 14: Configuring SIP Supplementary Services
- 84 Step 15: Defining Reasons for Alternative Routing
- 86 Step 16: Supporting Regional Call Progress Tone
- 89 Troubleshooting
- 89 Debugging Procedures
- 89 Case Reporting Procedures
- 90 Syslog
- 92 Wireshark Network Sniffer
- 96 Verifying Firmware
- 97 Configuring Analog Devices (ATA’s)
- 97 Step 1: Configure the Endpoint Phone Number Table
- 98 Step 2: Configure Tel to IP Routing Table
- 99 Step 3: Configure Coders Table