Dialogic 2000 Series Quick guide

July 2011 05-2696-002
www.dialogic.com
Dialogic®2000 Media Gateway Series
Installation and Configuration Note
for Microsoft®Lync 2010

2
Copyright and Legal Notice
Copyright © 2010-2011 Dialogic Inc. All Rights Reserved. You may not reproduce this document in whole or in part
without permission in writing from Dialogic Inc. at the address provided below.
All contents of this document are furnished for informational use only and are subject to change without notice and do not
represent a commitment on the part of Dialogic Inc. and its affiliates or subsidiaries (“Dialogic”). Reasonable effort is made
to ensure the accuracy of the information contained in the document. However, Dialogic does not warrant the accuracy of
this information and cannot accept responsibility for errors, inaccuracies or omissions that may be contained in this
document.
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH DIALOGIC® PRODUCTS. NO LICENSE, EXPRESS
OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT.
EXCEPT AS PROVIDED IN A SIGNED AGREEMENT BETWEEN YOU AND DIALOGIC, DIALOGIC ASSUMES NO LIABILITY
WHATSOEVER, AND DIALOGIC DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF
DIALOGIC PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE,
MERCHANTABILITY, OR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHT OF A THIRD PARTY.
Dialogic products are not intended for use in certain safety-affecting situations. Please see
http://www.dialogic.com/about/legal.htm for more details.
Due to differing national regulations and approval requirements, certain Dialogic products may be suitable for use only in
specific countries, and thus may not function properly in other countries. You are responsible for ensuring that your use of
such products occurs only in the countries where such use is suitable. For information on specific products, contact
Dialogic Inc. at the address indicated below or on the web at www.dialogic.com.
It is possible that the use or implementation of any one of the concepts, applications, or ideas described in this document,
in marketing collateral produced by or on web pages maintained by Dialogic may infringe one or more patents or other
intellectual property rights owned by third parties. Dialogic does not provide any intellectual property licenses with the sale
of Dialogic products other than a license to use such product in accordance with intellectual property owned or validly
licensed by Dialogic and no such licenses are provided except pursuant to a signed agreement with Dialogic. More detailed
information about such intellectual property is available from Dialogic’s legal department at 926 Rock Avenue, San Jose,
California 95131 USA. Dialogic encourages all users of its products to procure all necessary intellectual property
licenses required to implement any concepts or applications and does not condone or encourage any
intellectual property infringement and disclaims any responsibility related thereto. These intellectual property
licenses may differ from country to country and it is the responsibility of those who develop the concepts or
applications to be aware of and comply with different national license requirements.
Dialogic, Dialogic Pro, Dialogic Blue, Veraz, Brooktrout, Diva, Diva ISDN, Making Innovation Thrive, Video is the New
Voice, Diastar, Cantata, TruFax, SwitchKit, SnowShore, Eicon, Eiconcard, NMS Communications, NMS (stylized),
SIPcontrol, Exnet, EXS, Vision, PowerMedia, PacketMedia, BorderNet, inCloud9, I-Gate, ControlSwitch, NaturalAccess,
NaturalCallControl, NaturalConference, NaturalFax and Shiva, among others as well as related logos, are either registered
trademarks or trademarks of Dialogic Inc. and its affiliates or subsidiaries. Dialogic’s trademarks may be used publicly only
with permission from Dialogic. Such permission may only be granted by Dialogic’s legal department at 926 Rock Avenue,
San Jose, California 95131 USA. Any authorized use of Dialogic’s trademarks will be subject to full respect of the
trademark guidelines published by Dialogic from time to time and any use of Dialogic’s trademarks requires proper
acknowledgement.
Microsoft is a registered trademark of Microsoft Corporation in the United States and/or other countries. Other names of
actual companies and products mentioned herein are the trademarks of their respective owners.
This document discusses one or more open source products, systems and/or releases. Dialogic is not responsible for your
decision to use open source in connection with Dialogic products (including without limitation those referred to herein), nor
is Dialogic responsible for any present or future effects such usage might have, including without limitation effects on your
products, your business, or your intellectual property rights.

Dialogic®2000 Media Gateway Series Installation and Configuration Note
3
1. Scope
This document is intended to detail a typical installation and configuration of Dialogic®2000 Media
Gateway Series (DMG2000) when used to interface between a PBX or Central Office and
Microsoft®Lync 2010.
2. Gateway Configuration Details
Gateway Model(s) Dialogic®2000 Media Gateway Series
(DMG2030DTIQ, DMG2060DTIQ, DMG2120DTIQ,
DMG2060DTISQ, DMG2120DTISQ)
Software Version(s) Version 6.0 Service 6.0.004_B003
Protocol(s) T1 CAS, T1/E1 ISDN
2.1 System Diagram
Lync Clients
5100 5101
PBX
TDM Stations
2410 2401
DMG2000
Mediation/Front End
Serve
r
T1/E1
IP LAN
Lync
Serve
r

for Microsoft®Lync 2010
4
3. Prerequisites
3.1 Trunk Prerequisites
The T1 or E1 trunk must be configured for T1 (NI2, QSIG, 5ESS or DMS protocols) or E1 (Euro
ISDN or QSIG protocols).
If connecting to a PBX, refer to the Unified Messaging Integration Notes for guidance at:
http://www.dialogic.com/support/helpweb/mg/iw1904.aspx
For more information on PBX programming, refer to:
http://www.dialogic.com/solutions/unified-communications/microsoft-pbx-interop-and-config-
guides.aspx
3.1.1 Cabling Requirements
Cabling for ISDN connections must be CAT5e or better. Standard voice quality cable will not
provide optimum signal quality, and will cause the gateway to experience problems establishing a
connection on the D-Channel.
If connecting the gateway directly to the PBX, it may be necessary to use a T1 crossover cable
(Pin 1 is connected to Pin 4 and Pin 2 is connected to Pin 5). This is dependent on the PBX type to
which the gateway is being connected, so if after connecting the gateway to the PBX the Alarm
light on the front of the gateway remains “Red”, try using the crossover cable.
3.2 Gateway Prerequisites
The DMG2000 must be installed with Version 6.0.SU6.0.004_B003.
4. Summary of Limitations
No limitations noted as of the last update to this document.
5. Gateway Setup Notes
5.1 Initial Setup
There are two options for performing the initial configuration of the DMG2000 – serial or IP. It is
recommended that serial be used.
During the initial setup of the DMG2000, you will be setting the following parameters:
•Assign the gateway a unique IP address, subnet mask and IP network gateway address (if
the latter is required).

Dialogic®2000 Media Gateway Series Installation and Configuration Note
5
•Configure the gateway to use the SIP VoIP protocol.
•Set the Line Mode to T1 or E1.
•Set the Protocol to match your trunk setting.
Connecting to Console Port
Serial:
Connect to the COM 2 port on the DMG2000 using an appropriate program, such as
HyperTerminal.
The serial port configuration is:
Baud rate: 115200
Data Buts 8
Stop Bits: 1
Parity: none
Flow Control: none
Serial Port Pin Out
Pin Signal
1Data Carrier Detect
2Transmit Data
3Receive Data
4Data Terminal Ready
5Signal Ground
6Data Set Ready
7Clear to Send
8Request to Send
9Ring Indicator
Ethernet:
Default DMG2000 IP address: 10.12.13.74
Change the IP address of your computer to be in the same subnet as the default. Telnet into the
DMG2000 and then follow the commands noted below:
Running QuickCFG
Press Enter key until you get to the “PIMG” prompt. Follow the steps below and modify the
settings in red to match your environment. The values in bold are what you will be entering.

for Microsoft®Lync 2010
6
PIMG> pw
d
Enter Password: IpodAdmin
Admin level accepted.
PIMG-admin> quickcfg
LAN 1 IP Address[10.12.13.74] : (Enter new IP Address that matches
gateway IP address entered in Mediation server)
LAN 1 Subnet Mask[255.255.255.0] : (Enter new Subnet Mask)
LAN 1 Default Network Gateway Address[10.2.2.5] : (Enter new Default
Network Gateway Address)
LAN 2 IP Address[10.2.2.2] :
LAN 2 Subnet Mask[255.255.255.0] :
Select Line Mode ...
Valid entries:
1. T1
2. E1
Enter Number for Line Mode Selection [T1] : 1
Select Protocol ...
Valid entries:
1. CAS - Loop Start
2. CAS - Ground Start
3. CAS - E&M Immediate
4. CAS - E&M Delay
5. CAS - E&M Wink
6. ISDN - QSIG
7. ISDN - NI-2
8. ISDN - 5ESS
9. ISDN - DMS-100
Enter Number for Protocol Selection [ISDN - NI-2] : 6
Saving parameters now...
Parameters successfully configured!
******* Restart Required ******* (Type 'restart')
PIMG-admin> restart
rebooting...

Dialogic®2000 Media Gateway Series Installation and Configuration Note
7
5.2 Final Web Configuration
Once the initial configuration is complete and the DMG2000 has been reset, it is necessary to log
into the web interface by browsing to the IP address of the DMG2000 using “admin” as the user
and using the gateway password (“IpodAdmin” is the default).
Sample Configuration files
Download available at:
http://www.dialogic.com/~/media/microsoftuc/DMG2000_Lync_Config.zip
•There are two sample configuration files for adjusting gateway parameters to enable
interoperability with Microsoft®Lync 2010 specific settings. The “DMG2000 Lync Config
u-law.ini” file, among other functions, will set up the codec to be G.711 uLaw for use in
North America and other areas that use uLaw. The “DMG2000 Lync Config a-law.ini”
file, among other functions, will set up the codec to be G.711 aLaw for use in Europe and
other regions that use aLaw. In addition to changing the default settings, these files also
contain some sample Dial Plan configurations to provide a starting point for configuration
the E.164 phone number conversions.
•To import one of these files into the DMG2000, use the Import/Export page on the
DMG2000 web interface. Select IMPORT and browse to reach the desired “.ini” file to
import.
Setting T1 / E1 Parameters
Line Encoding and Framing
It is necessary to ensure that the Line Encoding and Framing match those of the T1
or E1 line coming from the PBX or Central Office.
ISDN Protocol
Since ISDN protocols are not necessarily symmetric protocol it is necessary to
determine which device (PBX or Gateway) is going to function as the Network side
of the protocol. It is recommended that if the PBX can support Network side that it
be configured as Network in which case the gateway needs to be configured as
Terminal. Setting the Protocol side is done by changing the “Telephony Port
Interface Side” to the setting you want the gateway to function.

for Microsoft®Lync 2010
8
Setting Line Encoding, Framing, and ISDN Protocol
Navigate to the TDM > T1/E1 page.
Set ISDN
Network or
Terminal side.
Set T1/E1
Line Encoding
and Framing.

Dialogic®2000 Media Gateway Series Installation and Configuration Note
9
Setting PCM Coding for TDM
Navigate to the TDM > General page.
aLaw – E1
uLaw – T1

for Microsoft®Lync 2010
10
Setting VoIP Parameters
Navigate to the VoIP > General page and the following VoIP parameters will need to be set:
Gateway’s FQDN
DNS server IP addresses
TCP or TLS Listen ports
DNS monitoring if DNS load balancing is being used
Enter the FQDN
assigned to the
g
atewa
y
.
Enter the IP address of a
DNS server and a backup
if available.
Enable TCP and or TLS for
the gateway to listen on.
Configure the Port to
match that defined in
Topology Builder.
Make sure that the TCP
and TLS Inactivity Timers
are set to 120.
If using DNS load
Balancing to
distribute the calls
between multiple
Frontend Servers
set this to Yes.
Ensure that Reliable
Provisional Response is
set to Su
pp
orted.

Dialogic®2000 Media Gateway Series Installation and Configuration Note
11
Setting Network Groups
Navigate to the VoIP > Network Groups page.
On the Network Groups page you will be configuring the outbound transport, voice codec, packet
size and whether you want RTP or SRTP. It is possible to set up multiple different network groups
with different characteristics for different IP endpoints. The Networks groups will be referenced in
the route table setup further down in this document.

for Microsoft®Lync 2010
12
Select the
transport for
outbound calls
from the gateway.
If using SRTP then
set SRTP
Preference to
SRTP_Only.
Set MKI on
Transmit Stream to
No.

Dialogic®2000 Media Gateway Series Installation and Configuration Note
13
Configuring Media Settings
Navigate to the VoIP > Media page.
On this page, you will be setting up Early Media, configuring fax for G.711 pass-through, setting
the DTMF digit transmission to RFc2833 with the lowest latency possible. You will also be
configuring the RTP port validation.
Enable Early Media
Sending the 183
messages and
Reliable Provisional
Responses.
Set the Digit Relay
mode to RFC2833-
LowLatency to
minimize latency.
Set the Fax mode
to G.711-
Passthrough.
Turn off both RTP
port and address
validation.

for Microsoft®Lync 2010
14
Configuring DSP Settings
Navigate to the DSP Settings page.
Configure the Jitter
Buffer.
Enable Echo
Cancellation with
NLP and normal
Aggressiveness.

Dialogic®2000 Media Gateway Series Installation and Configuration Note
15
Turn AGC off in
both Directions.

for Microsoft®Lync 2010
16
Configuring Route Table for E.164 support
Configuring Calls to PSTN Network
Microsoft®Lync sends the phone number to the DMG2000 in E.164 format. It is necessary
to convert this to a dialable number, which, in turn, can be sent to the central office or to
your PBX.
North America (DMG2000 Lync Config u-law.ini)
•The rules in the sample configuration file “DMG2000 Lync Config u-law.ini” perform
the following dial sting manipulations:
Phone number
type Microsoft®Lync sent phone
number Phone number sent to CO or PBX
4-digit extension
from non-DID
number
[phone];ext=1234 1234
4-digit Extension
(starting with
881)
[phone]
Local call [phone] 91234567
Long Distance [phone] 914251234567
International [phone] 901144123456789
•It will be necessary to modify these rules to fit your environment. You will need to
match your internal extension pattern.
•If you are connected directly to a trunk line coming from a phone company, it will be
necessary to remove the trunk access code “9” from these rules. Depending on your
PBX configuration, it might be necessary as well to change the sample trunk access
code to one that matches your environment.
•To change the Routing Table settings, log into the web interface, then open the
“Routing Table”. With the Radio button selected for Inbound VoIP rules select among
the five “Inbound VoIP Rules” to see the routing and CPID manipulations for each rule.
oIn the “non-DID internal” rule the gateway will automatically extract the number
string following the “ext” field of the Invite and pass to the Routing table. Because
of this all that is necessary to do in the CPID manipulation is to pass the extension.
oThe “Internal” rule will extract the last 4 number from the right side to create a 4-
digit extension to be dialed on the local PBX.

Dialogic®2000 Media Gateway Series Installation and Configuration Note
17
oThe “Local” rule is extracting seven (7) digits from the right side (relx(d,7) and pre-
pending the trunk access code “9” to the number. If you are connected directly to
the phone company, you will want to change this rule just to extract the seven (7)
digits. It should look like this: rext(D,7).
oAll the “Domestic” rule is doing is adding the trunk access number. To the 11 digits
following the “+”. Depending on your configuration, this can be changed or deleted.
oThe “International” rule is adding the trunk access number “9” and the international
access number “011”. If necessary, you can change or delete the trunk access
number.

for Microsoft®Lync 2010
18
Europe (DMG2000 Lync Config a-law.ini)
Phone number
type Microsoft®Lync sent phone
number Phone number sent to CO or PBX
National [phone] 0123456789
International [phone] 0049123456789
•Changing “National” dial plan to match your country
oIn this example, and in the applicable attached sample “.ini” configuration
file, the dial plan is set up to determine a “National” number in the UK. If
you are located in another country, you will need to change the National dial
plan to match your specific country code. To do so, you will need to edit the
“Inbound VoIP Routing” rule and modify the “CPID Manipulation” setting to
match your country.
•Inbound VOIP Routing
oThe Inbound routing rules compare the number sent by Microsoft®Lync and
look for the country code. If the located code matches the desired code for
the country in which the DMG2000 is deployed - in this case the UK - then
the manipulation for a national number is run. All other calls are treated as
international calls.
•CPID Manipulation
oFor a “National” number, the country code is replaced with a “0” and the
number is dialed. For international numbers, a “00” is added to the
beginning of the dial string.
oIf the DMG2000 is deployed behind a PBX, it might be necessary to add a
trunk access to the dial strings as well. To accomplish this, the “Called
Number” field of the CPID Manipulation section will need to add the trunk
access code. In the example below, you would need to change the rule to
be:
National repl(D,“+44”,“90”)
International repl(D,“+”,“900”)

Dialogic®2000 Media Gateway Series Installation and Configuration Note
19
Remove the country
code and replace with
“09
”
.
Set the Local Country
code.

for Microsoft®Lync 2010
20
Configuring Calls from TDM to Microsoft®Lync Server
Directing PSTN / PBX Calls to Mediation Server
•It is necessary to direct all incoming calls from the TDM (PSTN) side to the
mediation server. This is done in the Routing Table tab of the web interface. Select
the Inbound TDM Call Routing tab and enter the IP-address or FQDN of the
Mediation server or pool of servers in the URI field.
•Hit “Submit” to save the changes.
Select the Network
Group created in the
previous steps.
Name of VoIP Endpoint
(needed for setting up
route
)
.
Set IP address of
Mediation server or the
FQDN for the pool of
mediation servers. Be
sure to include the port
that you want to
transmit to. In this
exam
p
le 5067.