AudioCodes Mediant Series Quick start guide

Version 6.8
February 2014
Document # LTRT-40512
Configuration Note
Mediant Gateway for Microsoft® Office 365
Exchange Online Unified Messaging with Legacy PBX
VoIP Media Gateways
AudioCodes Mediant™ Series
Interoperability Lab

October 2013
Document #: LTRT-XXXXX

Configuration Note Contents
Version 6.8 3 February 2014
Table of Contents
1Introduction .........................................................................................................7
1.1 Focus of the Guide.................................................................................................8
2AudioCodes Interoperability with PBX Vendors...............................................9
3Preparing for AudioCodes Gateway Configuration........................................13
3.1 Configure DNS.....................................................................................................13
3.2 Generate Certificate .............................................................................................13
3.3 Configure UM.......................................................................................................14
3.3.1 Create a UM Dial Plan.............................................................................................14
3.3.2 Create a UM IP Gateway.........................................................................................17
4Configure AudioCodes Mediant Gateway.......................................................21
4.1 Configure IP Network Interfaces...........................................................................21
4.2 Configure Network Time Protocol Server IP Address ...........................................22
4.3 Configure SIP Transport Type..............................................................................23
4.4 Configure Proxy and Registration.........................................................................24
4.5 Restrict Communication to Exchange Online Only ...............................................26
4.6 Configure Codecs.................................................................................................27
4.7 Configure Media Security .....................................................................................28
4.8 Configure PSTN Trunk Settings............................................................................29
4.8.1 Configure TDM Bus .................................................................................................31
4.9 Configure Trunk Group.........................................................................................32
4.10 Configure Trunk Group Settings...........................................................................33
4.11 Configure VoIP Gateway IP-to-Tel Routing Rules ................................................34
4.12 Configure VoIP Gateway Tel-to-IP Routing Rules ................................................35
4.13 Configure Certificates...........................................................................................36
4.13.1 Configure Cryptographic Parameters......................................................................36
4.13.2 Generate Certificate Signing Request (CSR)..........................................................37
4.13.3 Loading the Certificate.............................................................................................38
4.14 Configure Voice Mail Interface..............................................................................42
4.15 Configure Message Waiting Indicator...................................................................43
4.16 Reset the Gateway...............................................................................................44

Microsoft Office 365 Exchange UM with Legacy PBX
AudioCodes Mediant Gateway 4 Document #: LTRT-40512
List of Figures
Figure 1-1: AudioCodes Gateway Interfacing between Legacy PBX and Office 365..............................8
Figure 3-1: Initial (Empty) UM Dial Plans List in Exchange Control Panel.............................................14
Figure 3-2: Specifying Properties for a New UM Dial Plan for a PBX....................................................14
Figure 3-3: List Showing One UM Dial Plan...........................................................................................15
Figure 3-4: Editing the Display Access Numbers for a UM Dial Plan ....................................................16
Figure 3-5: Creating New UM IP Gateway to Represent IP Gateway on Customer's Premises...........17
Figure 3-6: Associating the New UM IP Gateway with a UM Dial Plan..................................................18
Figure 3-7: New UM IP Gateway Associated with a UM Dial Plan ........................................................18
Figure 3-8: UM IP Gateway Forwarding Address Needed for Gateway Configuration Warning ...........19
Figure 3-9: Viewing the Forwarding Address of a UM IP Gateway........................................................19
Figure 4-1: Configured Network Interfaces in IP Interfaces Table.........................................................21
Figure 4-2: Application Settings Page....................................................................................................22
Figure 4-3: SIP General Parameters......................................................................................................23
Figure 4-4: Proxy and Registration Configuration..................................................................................24
Figure 4-5: Default Proxy Sets Table Configuration...............................................................................25
Figure 4-6: Advanced Parameters Page................................................................................................26
Figure 7: Codec Configuration ...............................................................................................................27
Figure 4-8: Media Security Configuration...............................................................................................28
Figure 9: Trunk Configuration.................................................................................................................29
Figure 10: Q931 Layer Response Behavior Configuration ....................................................................30
Figure 4-11: TDM Bus Settings Page.....................................................................................................31
Figure 4-12: Trunk Group Configuration ................................................................................................32
Figure 4-13: Trunk Group Configuration Trunk Group Settings.............................................................33
Figure 4-14: IP-to-Tel Routing Rules Configuration...............................................................................34
Figure 4-15: Tel-to-IP Routing Rules Configuration...............................................................................35
Figure 4-16: Cryptographic Configuration ..............................................................................................36
Figure 4-17: Web Security Settings........................................................................................................36
Figure 4-18: Generating Certificate Signing Requests...........................................................................37
Figure 4-19: Ensuring Certificate Text Starts with 'BEGIN CERTIFICATE' ...........................................38
Figure 4-20: Certificates.........................................................................................................................38
Figure 4-21: GTE CyberTrust Root CA Certificate.................................................................................39
Figure 4-22: Baltimore CyberTrust Root CA ..........................................................................................40
Figure 4-23: Loading Certificates ...........................................................................................................41
Figure 4-24: Voice Mail Interface Configuration.....................................................................................42
Figure 4-25: MWI Configuration .............................................................................................................43
Figure 4-26: Default Destination Number Configuration ........................................................................43
Figure 4-27: Subscription Mode Configuration.......................................................................................43
Figure 4-28: Resetting the SBC .............................................................................................................44
List of Tables
Table 2-1: AudioCodes Interoperability with PBX Vendors......................................................................9

Configuration Note Notices
Version 6.8 5 February 2014
Notice
This Configuration Note shows how to configure an AudioCodes gateway to establish
communication between telephony equipment on customer premises and Office 365
Exchange Online Unified Messaging (UM). It also shows how to configure Exchange Online
UM to work with the AudioCodes gateway.
Information contained in this document is believed to be accurate and reliable at the time of
printing. However, due to ongoing product improvements and revisions, AudioCodes cannot
guarantee accuracy of printed material after the Date Published, nor can it accept
responsibility for errors or omissions. Updates to this document and other documents as
well as software files can be viewed by registered customers at
http://www.audiocodes.com/downloads.
© Copyright 2014 AudioCodes Ltd. All rights reserved.
This document is subject to change without notice.
Date Published: February-18-2014
Trademarks
AudioCodes, AC, AudioCoded, Ardito, CTI2, CTI², CTI Squared, HD VoIP, HD VoIP
Sounds Better, InTouch, IPmedia, Mediant, MediaPack, NetCoder, Netrake, Nuera, Open
Solutions Network, OSN, Stretto, TrunkPack, VMAS, VoicePacketizer, VoIPerfect,
VoIPerfectHD, What's Inside Matters, Your Gateway To VoIP and 3GX are trademarks or
registered trademarks of AudioCodes Limited. All other products or trademarks are
property of their respective owners. Product specifications are subject to change without
notice.
WEEE EU Directive
Pursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed
of with unsorted waste. Please contact your local recycling authority for disposal of this
product.
Customer Support
Customer technical support and services are provided by AudioCodes or by an authorized
AudioCodes Service Partner. For more information on how to buy technical support for
AudioCodes products and for contact information, please visit our Web site at
www.audiocodes.com/support.

Microsoft Office 365 Exchange UM with Legacy PBX
AudioCodes Mediant Gateway 6 Document #: LTRT-40512
Related Documentation
Manual Name
Mediant 500 E-SBC User's Manual Ver. 6.8
Mediant 800B Gateway and E-SBC SIP User's Manual Ver. 6.8
Mediant 1000B Gateway & E-SBC User's Manual Ver. 6.8
Mediant 2600 E-SBC User's Manual Ver. 6.8
Mediant 3000 SIP User's Manual Ver. 6.8
Mediant 4000 E-SBC User's Manual Ver. 6.8
Downloadable from AudioCodes Web site at http://www.audiocodes.com/downloads
Documentation Feedback
AudioCodes continually strives to produce high quality documentation. If you have any
comments (suggestions or errors) regarding this document, please fill out the
Documentation Feedback form on our Web site at http://www.audiocodes.com/downloads.

Configuration Note 1. Introduction
Version 6.8 7 February 2014
1 Introduction
Exchange Online Unified Messaging (Exchange Online UM) supports a wide range of
telephony/voice solutions, including many PBXs and IP PBXs. A list is published in the
“Telephony Advisor for Exchange 2013”1.
When making or receiving telephone calls, Exchange Online UM only communicates with
Voice-over-IP (VoIP) protocols. PBXs that support circuit-switched telephony protocols
must be connected to Exchange Online UM with a suitable VoIP gateway. The gateway
performs the necessary protocol conversion. VoIP gateways are also listed in the
Exchange Telephony Advisor.
The Exchange Telephony Advisor also includes links to configuration notes that explain
how to configure the PBX to work with Exchange Online UM.
Exchange Online UM is now offered as an online service, in specific Microsoft Office 365
service plans. The telephony/voice solution remains on the customer’s premises, but
Exchange Online UM is now “in the cloud”, and the VoIP communication between them is
carried by the public IP network.
In this guide, we describe the AudioCodes Mediant gateway configuration necessary to
deploy it in an organization's network’s edge for interoperability with Exchange Online UM.
The purpose of the configuration is to ensure that traffic from the PBX, which is sent to the
gateway TDM interface, is routed to the Exchange Online UM.
Similarly, traffic from Exchange Online UM, arriving at the gateway IP interface, must be
routed to the PBX.
Configuration of the routing rules between the gateway interfaces is the main subject of this
document.
1http://technet.microsoft.com/en-us/library/ee364753.aspx

Microsoft Office 365 Exchange UM with Legacy PBX
AudioCodes Mediant Gateway 8 Document #: LTRT-40512
1.1 Focus of the Guide
This document focuses solely on the AudioCodes Mediant VoIP gateway features that are
required for interoperability with Office 365 Exchange Online UM.
The AudioCodes Mediant gateway may support additional characteristics that are not
described in this document. For a complete product description, refer to the AudioCodes
gateway documentation.
Figure 1-1: AudioCodes Gateway Interfacing between Legacy PBX and Office 365
Note: The gateway communicates with the PBX by using either QSIG or Simplified
Message Desk Interface (SMDI) via the serial RS-232 connection, or special in-
band DTMF digit patterns. This document focuses on QSIG integration. Contact
your AudioCodes sales representative for further information about other types
of integration.

Configuration Note 2. AudioCodes Interoperability with PBX Vendors
Version 6.8 9 February 2014
2 AudioCodes Interoperability with PBX
Vendors
The table below lists the PBX vendors for which AudioCodes has successfully proven
interoperability in Microsoft Unified Messaging Exchange 2007 environments.
Table 2-1: AudioCodes Interoperability with PBX Vendors
PBX Vendor PBX Type AudioCodes Product Voice Mail Integration
Alcatel 4400 MP-11x FXO DTMF
Alcatel-Lucent OXE Mediant 1000,
Mediant 2000 E1 QSIG
Alcatel-Lucent OXE Mediant 1000 IP-to-IP
Asterisk Business Edition Mediant 1000,
Mediant 2000 IP-to-IP
Avaya Definity G3 Mediant 2000 T1 CAS (DTMF)
Avaya Definity G3 MP-11x FXO DTMF
Avaya Definity G3 Mediant 1000,
Mediant 2000 T1 QSIG
Avaya Definity G3 Mediant 1000,
Mediant 2000 E1 QSIG
Avaya Merlin Magix MP-11x FXO DTMF
Avaya S8300 MP-11x FXO DTMF
Avaya S8300 Mediant 2000 T1 CAS (DTMF)
Avaya S8300 Mediant 1000,
Mediant 2000 E1 QSIG
Avaya S8700 Mediant 1000,
Mediant 2000 E1 QSIG
Cisco Call Manager 4.0 Mediant 1000,
Mediant 2000 IP-to-IP
Ericsson MD – 110 MP-11x FXO SMDI
Intecom PointSpan M6880 Mediant 2000 T1 CAS (SMDI)
Inter-Tel Axxess MP-11x FXO DTMF
Inter-Tel Axxess Mediant 2000 T1 CAS (DTMF)
Inter-Tel 5000 Mediant 2000 T1 CAS (DTMF)
Inter-Tel 5000 MP-11x FXO DTMF
Mitel 3300 Mediant 1000,
Mediant 2000 T1 QSIG
NEC Electra 192 MP-11x FXO DTMF
NEC NEAX 2400 IPX Mediant 2000 T1 CAS (SMDI – MCI)
NEC NEAX 2400 IPX MP-11x FXO SMDI – MCI
NEC 7600i Mediant 2000 T1 CAS (SMDI)

Microsoft Office 365 Exchange UM with Legacy PBX
AudioCodes Mediant Gateway 10 Document #: LTRT-40512
PBX Vendor PBX Type AudioCodes Product Voice Mail Integration
NeXspan S MP-11x FXO DTMF
Nortel CS1K (Communication
Succession 1000) Mediant 1000, Mediant 2000 E1 QSIG
Nortel Meridian 11C, Meridian 51C, Meridian 61C,
Meridian 81C
Mediant 1000,
Mediant 2000 T1 QSIG
Nortel Meridian 11C, Meridian 51C, Meridian 61C,
Meridian 81C
Mediant 1000,
Mediant 2000 E1 QSIG
Nortel SL-100/DMS-100 Mediant 2000 T1 CAS (SMDI)
Nortel SL-100/DMS-100 Mediant 1000
MP-11x SMDI
Nortel Meridian 1 Mediant 1000,
Mediant 2000 T1 QSIG
Nortel Meridian 1 Mediant 1000,
Mediant 2000 E1 QSIG
Panasonic KX-TDA30, KX- TDA100, KX-TDA200,
KX-TDA600 MP-11x FXO DTMF
Panasonic KX-TDE2000, KX-
TDE100, KX-TDE600 Mediant 1000 FXO DTMF
Panasonic KX-TES824, KX-
TEA308 MP-11x FXO DTMF
ShoreTel IP Telephony System MP-11x FXO SMDI
ShoreTel IP Telephony System Mediant 1000 FXO SMDI
Siemens Hicom 150E MP-11x FXO DTMF
Siemens HiPath 3550 MP-11x FXO DTMF
Siemens HiPath 4000 Mediant 1000,
Mediant 2000 T1 QSIG
Siemens HiPath 4000 MP-11x FXO DTMF
Siemens HiE9200 Mediant 1000,
Mediant 2000 IP-to-IP
Tadiran Coral Flexicom MP-11x FXO DTMF
Tadiran Coral Flexicom Mediant 2000 E1 CAS (DTMF)
Tadiran Coral Flexicom Mediant 1000,
Mediant 2000 E1 QSIG
Tadiran Coral Flexicom Mediant 1000 BRI QSIG
Tadiran Coral IPX Mediant 1000 BRI QSIG
Tadiran Coral IPX Mediant 2000 E1 CAS (DTMF)

Configuration Note 2. AudioCodes Interoperability with PBX Vendors
Version 6.8 11 February 2014
PBX Vendor PBX Type AudioCodes Product Voice Mail Integration
Tadiran Coral IPX Mediant 1000,
Mediant 2000 E1 QSIG
Tadiran Coral IPX MP-11x FXO DTMF

Microsoft Office 365 Exchange UM with Legacy PBX
AudioCodes Mediant Gateway 12 Document #: LTRT-40512
Reader's Notes

Configuration Note 3. Preparing for AudioCodes Gateway Configuration
Version 6.8 13 February 2014
3 Preparing for AudioCodes Gateway
Configuration
Before configuring the gateway to route traffic to and from Office 365 Exchange Online UM,
there are several steps that must be followed. Specifically, DNS configuration is required,
followed by some Exchange Online UM configuration.
3.1 Configure DNS
The Exchange Online UM service in Office 365 must be able to locate the AudioCodes
gateway when Exchange Online UM needs to initiate communication. Exchange Online
UM relies on its own configuration and use of the Domain Name Service (DNS) to discover
the address of the gateway.
Assign (have your network administrator assign) an IP address and host name for the
gateway. For example, Contoso might decide to use GW.contoso.com as the name. Add
this name and the corresponding address to the public DNS entries for your domain.
3.2 Generate Certificate
You must replace the gateway self-signed certificate. This can be done during the main
process of gateway configuration. The new certificate must meet the following
requirements:

It must be signed by a recognized Certificate Authority (CA). Self-signed certificates
(the kind that customers can generate and sign themselves) are not suitable for
communication with Exchange Online UM.

The Subject Name (CN) that is contained in the certificate must match the fully
qualified domain name (FQDN) of the gateway as described in Section 3.1 above).
For example, if the gateway will be addressed as GW.contoso.com, make sure that
the Subject Name in the certificate contains exactly the same string (i.e.,
GW.contoso.com).

The certificate should be suitable for use for Secure Sockets Layer (SSL).
You must generate and send a Certificate Signing Request to one of the supported
Certificate Authorities (see below). The CA will sign and issue a certificate for the device.
The details of submitting the request, making payment and receiving the certificate issued
will depend on the CA chosen.
At the time of writing, the following Certificate Authorities are supported by Office 365
Exchange Online UM:

DigiCert (http://www.digicert.com/)

Entrust (http://www.entrust.com/)

Geotrust (http://www.geotrust.com/)

GoDaddy (http://www.godaddy.com/)

GTE CyberTrust (http://www.verizonbusiness.com/Products/security/identity/ssl/)

Network Solutions (http://www.networksolutions.com/)

RSA Security (http://www.rsa.com/)

Thawte (http://www.thawte.com/)

Verisign (http://www.verisign.com/)
When the CA issues the certificate and returns it, save the certificate to a text file.
Further details of the process and how to load the certificate to the gateway are contained
in Section 4.13 on page 36.

Microsoft Office 365 Exchange UM with Legacy PBX
AudioCodes Mediant Gateway 14 Document #: LTRT-40512
3.3 Configure UM
Before communication can be established from a telephony solution (via the gateway) to
Office 365 Exchange Online UM, specific online Exchange Online UM configuration must
be performed. This consists of, at least, creating and configuring a Dial Plan and an IP
gateway. These are configuration objects that represent devices that are part of the
telephony solution.
3.3.1 Create a UM Dial Plan
A UM Dial Plan represents a set of fixed-length telephone numbers and the PBX (or
equivalent) to which they are attached. All Exchange users whose mailboxes are enabled
for Exchange Online UM must be associated with a UM Dial Plan.
In the Exchange Control Panel (ECP), create a new UM Dial Plan (as shown below).
To create a new UM Dial Plan:
1. Select the UM Dial Plans tab; the following screen appears.
Figure 3-1: Initial (Empty) UM Dial Plans List in Exchange Control Panel
2. Click on New… to create a new UM Dial Plan.
Figure 3-2: Specifying Properties for a New UM Dial Plan for a PBX

Configuration Note 3. Preparing for AudioCodes Gateway Configuration
Version 6.8 15 February 2014
3. In the 'Name' field, enter the Name for the UM Dial Plan.
4. In the 'Extension length' field, enter the extension number length. The extension
number (along with a PIN) is what UM-enabled users must enter to identify
themselves to UM when they call it from a telephone, and try to log in to their mailbox.
All extension numbers in a Dial Plan must have the same number of digits. This will be
determined by the PBX’s numbering plan.
5. From the 'Dial Plan URI Type' drop-down list select Telephone Extension. This
indicates that the telephony solution in use is a PBX or IP PBX (and not Microsoft
Lync).
6. In the 'Country/Region Code' field, enter the international dialing code for the country
in which the telephony solution (PBX or IP PBX) is operating. For example, enter '1'
for the United States, '44' for the United Kingdom, etc. The field accepts 1 to 4
numbers.
7. Click Save when you have entered all the information required to specify the new UM
Dial Plan. The UM Dial Plan that you created is now listed, as shown in the example
below.
8. Click the Details button to view and edit its properties, and those of associated objects
such as UM Mailbox Policies.
Figure 3-3: List Showing One UM Dial Plan

Microsoft Office 365 Exchange UM with Legacy PBX
AudioCodes Mediant Gateway 16 Document #: LTRT-40512
9. In the 'Number for Access' field, enter a number for user access on the new UM Dial
Plan (see Figure 3-4 below). This can be in any readable format, because it is for
display to users. For example, the user access number could be set to “(425) 266
8676” or “425-CONTOSO”. Two or more values can be supplied. The user access
number(s) should be consistent with call routing number(s), or users will become
confused. The user access number is included in the body of the “Welcome to
Exchange Unified Messaging” e-mail that is sent to each user when they are UM-
enabled. It is also displayed in the Outlook Voice Access section of the user’s Phone
personal options (accessed via OWA/Exchange Control Panel).
Figure 3-4: Editing the Display Access Numbers for a UM Dial Plan

Configuration Note 3. Preparing for AudioCodes Gateway Configuration
Version 6.8 17 February 2014
3.3.2 Create a UM IP Gateway
The procedure below describes how to create a UM IP gateway.
To create a UM IP gateway:
1. In ECP, navigate to the 'UM IP Gateways' tab and create a new UM IP gateway (see
Figure 3-5 below). For UM, this represents (the external interface of) your gateway.
2. Associate the UM IP gateway with the UM Dial Plan that you created by clicking the
Browse… button and selecting the Dial Plan from the list that is displayed (see
Figure 3-6 and Figure 3-7).
Figure 3-5: Creating New UM IP Gateway to Represent IP Gateway on Customer's Premises
3. In the 'Name' field, enter the name of the UM IP gateway (for your reference only). It
must be unique within your Office 365 organization. The object, for example,
represents a gateway on Contoso’s premises. This example shows that the
administrator chose a name to indicate this.
4. In the 'Address' field, enter the Address which must exactly match that of the public
(external) interface of the gateway for your organization.

Microsoft Office 365 Exchange UM with Legacy PBX
AudioCodes Mediant Gateway 18 Document #: LTRT-40512
5. Click the Browse… button on the UM IP gateway details page. It displays a list of all
the UM Dial Plans that have a type 'Telephone Extension'.
Figure 3-6: Associating the New UM IP Gateway with a UM Dial Plan
6. Select one of these and click OK.
Figure 3-7: New UM IP Gateway Associated with a UM Dial Plan

Configuration Note 3. Preparing for AudioCodes Gateway Configuration
Version 6.8 19 February 2014
7. When you create the UM IP gateway, it is automatically assigned a Forwarding
Address. You're alerted to this when you save the gateway configuration (see
Figure 3-8 below).
Figure 3-8: UM IP Gateway Forwarding Address Needed for Gateway Configuration Warning
8. To see the Forwarding Address, view the details of the UM IP Gateway object (see
Figure 3-9 below).
Figure 3-9: Viewing the Forwarding Address of a UM IP Gateway
Note: Forwarding addresses are in the form of guid.um.outlook.com, where guid is
replaced by a 36-character string that uniquely identifies the organization (using
UM) within the Office 365 system.

Microsoft Office 365 Exchange UM with Legacy PBX
AudioCodes Mediant Gateway 20 Document #: LTRT-40512
Reader's Notes