AudioCodes Mediant, Mediant 500 E-SBC, Mediant 800B, Mediant 1000B, Mediant 2600 E-SBC Configuration Note

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

1 Introduction ......................................................................................................... 7

1.1 Focus of the Guide ................................................................................................. 8

2 AudioCodes Interoperability with PBX Vendors............................................... 9

3 Preparing 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

4 Configure 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 Leg acy 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: App lication Settings Page ....................................................................................................22

Figure 4-3: SIP Gener al Pa r ameters ......................................................................................................23

Figure 4-4: Pr oxy and Registration Configurati on ..................................................................................24

Figure 4-5: Default Proxy Sets Table Configuration ...............................................................................25

Figure 4-6: Ad vanc e d Para meters Page ................................................................................................26

Figure 7: Codec Configuration ...............................................................................................................27

Figure 4-8: Med ia Sec ur it y Configur a tio n ...............................................................................................28

Figure 9: Trunk Configuration .................................................................................................................29

Figure 10: Q931 Layer Respons e Be ha vior 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: C ertif ic at es .........................................................................................................................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: Su bs c ripti on Mode Conf igur at ion .......................................................................................43

Figure 4-28: R esetting the SBC .............................................................................................................44

List of Tables

Table 2-1: AudioCodes Interoperab il ity 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 Unif ied M essagin g (UM). It also s ho ws ho w to conf igure Ex change O nli ne
UM to work with the AudioCodes gateway.

Information contained in thi s docum ent is believed to be ac curate and rel iable at the tim e of
printing. However, due to ongoing pro duct improvements and revis ions, A udi oCodes 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, InTouc h, IPmedia, Mediant, Med iaPack, NetCoder, Netrak e, Nuera, Open
Solutions Network, OSN, Stretto, TrunkPack, VMAS, VoicePacketizer, VoIPerfect,
VoIPerfectHD, W hat's Inside Matt ers, Your Gateway To VoIP a nd 3GX are trademarks or
registered trademarks of AudioCodes Limited. All other products or trademarks are
property of their res pective owners. Product specif ications are subject to change without
notice.

WEEE EU Directive

Pursuant to the WEEE EU Directive, electronic and el ectrical waste must not be disposed
of with unsorted waste. Please contact your local recycling authority for disposal of this
product.

Customer Support

Customer technical sup port and s ervices are pr ovided by Audio Codes or b y an authorize d
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 Leg acy 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 tele phone calls, Exchange Online UM o nly communicates with
Voice-over-IP (VoIP) protocols. PBXs that support circuit-switched telephony protocols
must be connected t o Exchange Online UM with a s uitable VoIP gateway. The gate way
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 o nline service, in specific Micr osoft 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 comm unication between th em 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 conf iguration is to ensure that traf fic from the PBX, which is s ent to the
gateway TDM interface, is routed to the Exchange Online UM.

Similarly, traffic f rom Exchange Online UM, arriving at the gateway IP i nterface, must be
routed to the PBX.

Configuration of the routing rules between the gateway interfaces is the main subject of this
document.

1

http://technet.microsoft.com/en-us/library/ee364753.aspx

Microsoft Office 365 Exchange UM with Leg acy PBX

AudioCodes Mediant Gateway 8 Document #: LTRT-40512

1.1 Focus of the Guide

This document focuses solely on the AudioCodes Me diant VoIP gateway feature s 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 docum ent. For a complete product des cription, refer to the AudioCodes
gateway documentation.

Figure 1-1: AudioCodes Gateway Interfacing between Legacy PBX and Office 365

Note: The gateway communicate s with the PBX by using either QSIG or Simplified

Message Desk Interfac e (SMDI) vi a the seria l RS-232 connec tion, or s pecial i n­band DTMF digit patterns . This document focuses on QSIG integration. Contact
your A udioCodes sales repres entative for further inform ation 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 Microsof t 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 Leg acy 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 Leg acy 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 st eps that must be foll owed. Specifically, DNS configuration is r equired,
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 conf iguratio n and us e of the Domain N am e Service ( DNS) t o disc over
the address of the gateway.

Assign (have your network administrator assign) an IP address and host name for the
gateway. For example, Co ntoso 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 Authoriti es (see below). The CA will sign and issue a certificate for the de vice.
The details of subm itting the request , making pa yment and receivin g the certificat e 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 cert ificate to the gateway are c ontained

in Section 4.13 on page 36.

Microsoft Office 365 Exchange UM with Leg acy PBX

AudioCodes Mediant Gateway 14 Document #: LTRT-40512

3.3 Configure UM

Before communication c an be established from a telephony solution ( via the gateway) to
Office 365 Exchange Online UM, s pecific online Exchange Online UM configurat ion 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 the y 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 C o n trol 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 th ey call i t from a telephon e, and try to log in t o their m ailbox .
All extension numbers in a Dia l 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 di aling code for the co untry

in which the telephony solutio n (PBX or IP PBX) is operating. For example, ent er '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 inform ation required to s pecify the new UM

Dial Plan. The U M Dial Plan that you creat ed is now listed, as shown i n 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 Leg acy PBX

AudioCodes Mediant Gateway 16 Document #: LTRT-40512

9. In the 'Number for Access' field, enter a number for user acc ess 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 Out look Voice Access s ection 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 Gate ways' tab and create a ne w 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 create d 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 referenc e 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 Leg acy PBX

AudioCodes Mediant Gateway 18 Document #: LTRT-40512

5. Click the Browse… button on the U M IP gateway det ails 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 Confi guration 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 ide ntifies the organizat ion (using
UM) within the Office 365 system.

Microsoft Office 365 Exchange UM with Leg acy PBX

AudioCodes Mediant Gateway 20 Document #: LTRT-40512

Reader's Notes

Configuration Note 4. Configure AudioCodes Mediant Gateway

Version 6.8 21 February 2014

4 Configure AudioCodes Mediant Gateway

Using your Web browser, connect to the gateway's administration interface (the default
address is 192.168.0.2).

After providing the require d credentials (the default u ser name is "Admin" and the defau lt
password is "Admin"), the Home page of the Web interface is displayed.

Use the Full navigation menu tree to perform gateway configuration.

4.1 Configure IP Network Interfaces

The procedure below describes how to assign an IP address to the VoIP / Managem ent
LAN interface.

 To configure the IP network interfaces:

1. Open the IP Interfaces Table page (Configuration tab > VoIP menu > Network > IP

Interfaces Table).

2. Modify the existing LAN network interface:
a. Select the OAMP + Media + Control table row, and click Edit.

b. Configure the interface as follows:

Parameter Value

Interface Mode

IPv4 Manual

IP Address

195.189.192.155 (IP address of gateway)

Prefix Length

25 (subnet mask in bits f or 255. 255. 0. 0)

Default Gateway

195.189.192.129

Interface Name

Voice (arbitrary descriptive name)

Primary DNS

80.179.55.100

Secondary DNS

80.179.52.100

Underlying Device

vlan 1

3. Click Submit; the configured IP network interfaces are shown below:

Figure 4-1: Configured Network Interfaces in IP Interfaces Table

Microsoft Office 365 Exchange UM with Leg acy PBX

AudioCodes Mediant Gateway 22 Document #: LTRT-40512

4.2 Configure Network Time Protocol Server IP Address

The procedure below describes how to configure the Network Time Protocol (NTP) server
IP address. The gateway requ ires NTP for succ essful TLS negotiation with the Office 365
Exchange Online UM system

2

.

 To configure the NTP server IP address:

1. Open the Application Settings page (Configuration tab > System menu >

Application Settings).

2. Configure the NTP (e.g. server IP address), as required.

Figure 4-2: Application Settings Page

3. Click Submit.

2

In principle, all that is required is that the gateway and the Office 365 system have a sufficiently
similar view of the current time. It’s possible to set the date and time on the gateway itself, which
provides a clock that maintains the time. However, without the use of NTP, it is likely that the
gateway’s time will eventually offset sufficiently, relative to the Office 365 system, for TLS negotiation
to stop working. This may be difficult to diagnose and therefore it is recommended to use NTP to keep
the gateway’s time synchronized.

Configuration Note 4. Configure AudioCodes Mediant Gateway

Version 6.8 23 February 2014

4.3 Configure SIP Transport Type

The procedure below describes how to set the SIP transport type to TLS.

 To configure SIP Transport Type:

1. Open the SIP General Parameters page (Configuration tab> VoIP menu > SIP

Definitions > General Parameters).

Figure 4-3: SIP General Parameters

2. From the 'SIP Transport Type' drop-down list, select TLS.

3. In the ‘SIP Destination Port’ , enter 5061

4. Click Submit.

Microsoft Office 365 Exchange UM with Leg acy PBX

AudioCodes Mediant Gateway 24 Document #: LTRT-40512

4.4 Configure Proxy and Registr ati on

The procedure below descr ibes how to configure the a ddress (IP address or FQD N) of the
Office 365 Exchange UM which communicates with the gateway. The PSTN gateway
forwards all calls from the PSTN to the Exchange Online UM using this address.

 To configure the Proxy and registration p arameters:

1. Open the Proxy & Registration page (Configuration tab > VoIP menu > SIP

Definitions > Proxy & Registration).

2. Set 'Use Default Proxy' to Yes.

Figure 4-4: Proxy and Registration Configuration

3. Click the arrow beneath the 'Use Default Proxy' parameter.

4. For the Proxy Address you must enter the F orwarding Address ass igned to the UM IP

gateway object created earlier (see Paragraph 8 on page 19). Only the end of a
sample address is visible in the f igure below. The length of the address is s uch that
the view is clipped in the user interface, and only part of the address is visible.

As secured communication is required, note that :5061 must be appended to the
address

3.

5. From the 'Transport Type' drop-down list, select TLS.

3

Port 5061 is used by Office 365 Exchange Online UM for all SIP/TLS traffic.

Configuration Note 4. Configure AudioCodes Mediant Gateway

Version 6.8 25 February 2014

6. From the ‘Enable Proxy Keep Alive’ drop-do w n lis t , select Using Options.

Figure 4-5: Default Proxy Sets Table Configuration

7. Click Submit.

Microsoft Office 365 Exchange UM with Leg acy PBX

AudioCodes Mediant Gateway 26 Document #: LTRT-40512

4.5 Restrict Communication to Exchan ge Online Only

The procedure below describes how to restrict IP communication, by allowing
communication onl y between the PSTN gateway and the Exchange Online. This ensures
that the PSTN gateway accepts and sends SIP calls only fr om and to the Exchange Online
IP address. This is done by enabling the I P Security feature and th en defining the allo wed
(“administrative” list) IP addresses (or FQDNs) in the Proxy Set table.

 To allow IP communication only between the PSTN Gateway and Exchange

Online:

1. Open the Advanced Parameters page (Configuration tab > VoIP menu > SIP

Definitions > Advanced Parameters).

Figure 4-6: Advanced Parameters Page

2. From the ‘IP Security’ drop-down list, select Secure Incoming calls to enable the

security feature to accept and send SIP calls only from and to user-defined IP
addresses or FQDN configured in the ‘Proxy Set table’.

3. Click Submit to apply your settings.

Configuration Note 4. Configure AudioCodes Mediant Gateway

Version 6.8 27 February 2014

4.6 Configure Codecs

The procedure below describes how to configure codecs.

 To configure codecs:

1. Open the Coders page (Configuration tab > VoIP menu > Coders and Profiles >

Coders).

2. From the 'Coder Name' drop-down list, s elect audio codecs supported by Office 365

Exchange Online UM.

Figure 7: Codec Configuration

3. Click Submit.

Microsoft Office 365 Exchange UM with Leg acy PBX

AudioCodes Mediant Gateway 28 Document #: LTRT-40512

4.7 Configure Media Security

The procedure below desc ribes how to conf igure Media Secur ity. This conf iguration for ces
the gateway to reject calls when the SIP peer does not use SRTP. Exchange Online UM
requires that all (audio) media be secured with the SRTP protocol.

 To configure media security:

1. Open the Media Security page (Configuration tab > VoIP menu > Media > Media

Security).

2. Set the 'Media Security' field to Enable.

3. Set the 'Media Security Behavior' field to Mandatory.

4. Set the 'Master Key Identifier (MKI) Size' field to "4".

Figure 4-8: Media Security Configuration

5. Click Submit.

Configuration Note 4. Configure AudioCodes Mediant Gateway

Version 6.8 29 February 2014

4.8 Configure PSTN Trunk Settings

The procedure below describes how to configure PSTN Trunk settings.

 To configure the PSTN Trunk Settings:

1. Open the Trunk Settings page (Configuration tab > VoIP menu > PSTN > Trunk

Settings).

2. Configure the following fields according to your PSTN physical Trunk deployment:

• Protocol Type

• Clock Master

• Line Code

• Framing Method

• ISDN Termination Side

Figure 9: Trunk Configuration

Microsoft Office 365 Exchange UM with Leg acy PBX

AudioCodes Mediant Gateway 30 Document #: LTRT-40512

3. Click the arrow next to the 'Q931 Layer Respo nse Behavior' field and configure th e

‘QSI ENCODE INTEGER’ bit to 1.

Figure 10: Q931 Layer Response Behavior Configuration

Configuration Note 4. Configure AudioCodes Mediant Gateway

Version 6.8 31 February 2014

4.8.1 Configure TDM Bus

The procedure below describes how to configure the TDM bus of the PSTN gateway.

 To configure the TDM bus:

1. Open the TDM Bus Settin gs page (Configuration tab > VoIP menu > TDM > TDM

Bus Settings).

Figure 4-11: TDM Bus Settings Page

2. Configure the TDM bus parameters according to your deployment requirements.

Below is a description of some of the main TDM parameters:

• PCM Law Select: Defines the type of PCM companding law in the input/output

TDM bus. Typically, A-Law is used for E1 and Mu-Law for T1/J1.

• TDM Bus Clock Source: Defines the clock source to which the PSTN gateway

synchronizes - generates clock from local source (Internal) or recovers clock from
PSTN line (Network).

• TDM Bus Local Reference: Defines the physical trunk ID from which the PSTN

gateway recovers (receives) its clock synchronization when the TDM Bus Clock
Source is configured to recover the clock from the PSTN line.

3. Click Submit to apply your changes.

4. On the toolbar, click Burn to save the changes to the PSTN gateway flash memory.

Note: Changes to fields marked will only take effect after a reset.

Microsoft Office 365 Exchange UM with Leg acy PBX

AudioCodes Mediant Gateway 32 Document #: LTRT-40512

4.9 Configure Trunk Group

The procedure below descr ibes how to c onf igure and enable the P STN net work connect ed
to the gateway's PRI TRUNK module.

 To configure the Trunk Group:

1. Open the Trunk Group Table page (Configuration tab> VoIP menu> GW and IP to

IP > Trunk Group > Trunk Group).

2. From the 'Module' drop-down list, select Module 1 PRI.

3. In the 'From Trunk' and 'To Trunk' fields, select 1 (i.e., Trunk 1).

4. In the 'Channels' field, enter "1-24" for the number of channels in the T1 Trunk.

5. In the 'Pho ne Number' field, enter a ny phone number for the c hannels. This is only a

logical phone number (i.e., not used).

6. In the 'Trunk Group ID' field, enter "1" as the Trunk Group ID.

Figure 4-12: Trunk Group Configuration

7. Click Submit.

Configuration Note 4. Configure AudioCodes Mediant Gateway

Version 6.8 33 February 2014

4.10 Configure Trunk Group Settings

The procedure below describes how to configure Trunk Group settings.

 To configure Trunk Group settings:

1. Open th e Trunk Group Settings page ( Configuration tab> VoIP menu > GW and IP

to IP > Trunk Group > Trunk Group Settings).

2. In the 'Trunk Group ID' field, enter "1".

3. From the 'Channel Select Mode' drop-down list, select Cyclic Ascending.

4. From the 'Serving IP Group ID' drop-down list, select 1.

Figure 4-13: Trunk Group Configuration Trunk Group Settings

5. Click Submit.

Microsoft Office 365 Exchange UM with Leg acy PBX

AudioCodes Mediant Gateway 34 Document #: LTRT-40512

4.11 Configure VoIP Gateway IP-to-Tel Routing Rules

The procedure below describes how to configure VoIP gateway IP-to-Tel Routing Rules.

 To configure IP-to-Tel routing rules:

1. Open the Inbound IP Routing T able page (Configuration tab> VoIP menu > GW an d

IP to IP > Routing > IP to Trunk Group Routing).

2. In the 'Dest Phone Prefix' field, enter an asterisk.

3. In the 'Source Phone Prefix' and Source IP Address' f ields, enter an asterisk sym bol

(*) to indicate any.

4. In the 'Trunk Group ID' field, enter "1".

Figure 4-14: IP-to-Tel Routing Rules Configuration

5. Click Submit.

Configuration Note 4. Configure AudioCodes Mediant Gateway

Version 6.8 35 February 2014

4.12 Configure VoIP Gateway Tel-to-IP Routing Rules

The procedure below describes how to configure the VoIP gateway Tel-to-IP Routing
Rules.

As mentioned in Section 4.5 on page 26, the gate way receives INVITEs from the Exchange
server only. When a REFER message is received from the Exchange, the gateway sends a
new INVITE message to itself.

To allow the gatewa y to receive an INVITE from its own IP addr ess, configure T el to IP
routing to use the gateway IP address in this table.

The routing table allows the gateway to route the call back to the PBX to reach the
destination transferee.

 To configure Tel-to-IP routing rules:

1. Open the Outbound IP Routin g Table page (Configuration tab > VoIP menu > GW

and IP to IP > Routing > Tel to IP Routing).

2. In the ‘Src. Trunk Group ID' field, enter an asterisk symbol (*) to indicate any.

3. In the 'Dest Phone Prefix' field, enter an asterisk symbol (*) to indicate any.

4. In the 'Source Phone Prefix' field, enter an asterisk symbol (*) to indicate any.

5. In the ‘Dest. IP Address’ field, enter the IP address of the gateway, i.e.,

"195.189.192.155”.

Figure 4-15: Tel-to-IP Routing Rules Configuration

6. Click Submit.

Microsoft Office 365 Exchange UM with Leg acy PBX

AudioCodes Mediant Gateway 36 Document #: LTRT-40512

4.13 Configure Certificates

As noted earlier in Section 3 on page 13, communicati on between the gateway and Of fice
365 Exchange Online UM requires the use of a digital certificate sign ed by a Certificate
Authority (CA). The gateway is supplied with a self-signed certificate, which cannot be used
because it is not signed by a supported CA.

Before certificate configuration takes place, ensure that the DNS (see Section 3.2 on
page 13 ) and NTP (see Section 4.2 on page 22) settings have been configured correctly. If
this is the case, proceed as follows.

4.13.1 Configure Cryptographic Parameters

The procedure below describes how to configure cryptographic parameters.

 To configure cryptographic parameter s:

1. Open the Certificates page (Configuration tab > System menu > Certificates).

2. Under the Generate new private key and self-signed certificate group, from the

'Private Key Size' drop-down list, select 2048 and then click Generate self-signed.

Figure 4-16: Cryptographic Configuration

3. Open the Web Security Settings page (Configuration tab > System menu >

Management > Web Security Settings).

4. Under the General group, in the 'HTTPS Cipher String' field, enter "ALL".

Figure 4-17: Web Security Settings

5. Click Submit.

6. On the toolbar, click Burn to save the settings, and reset the device.

Configuration Note 4. Configure AudioCodes Mediant Gateway

Version 6.8 37 February 2014

4.13.2 Generate Certificate Signing Request (CSR)

The procedure below describes how to generate certificate signing requests.

 To generate certificate signing requests:

1. Open the Certificates page (Configuration tab > System menu > Certificates).

2. In the 'Subject Name' field, enter the DNS name assigned to your device (see

Section 3.1 on page 13).

3. Enter all other certificate details.

4. Click Create CSR. After a few seconds, a text rendering of the certificate signing

request is displayed:

Figure 4-18: Generating Certificate Signing Requests

5. Copy all the text of the c ert if ic ate request (including t h e B EGIN and END sections and

dashes) and provide it to the Certificate Authority (CA) as part of their certificate
generation process (see Section 3 on page 13).

Microsoft Office 365 Exchange UM with Leg acy PBX

AudioCodes Mediant Gateway 38 Document #: LTRT-40512

4.13.3 Loading the Certificate

The procedure below des cribes how to load the c ertificate. You wil l receive the certificat e
from the CA as a text file (or in a form that can be saved as a text file).

 To load the certificate:

1. Ensure that the text file starts with a "BEGIN CERTIFICATE" header, as shown below:

Figure 4-19: Ensuring Certificate Text Starts with 'BEGIN CERTIFICATE'

-----BEGIN CERTIFICATE----­MIIDkzCCAnugAwIBAgIEAgAAADANBgkqhkiG9w0BAQQFADA/MQswCQYDVQQGEwJGUjETMBEGA1U

EChMKQ2VydGlwb3N0ZTEbMBkGA1UEAxMSQ2VydGlwb3N0ZSBTZXJ2ZXVyMB4XDTk4MDYyNDA4MD
AwMFoXDTE4MDYyNDA4MDAwMFowPzELMAkGA1UEBhMCRlIxEzARBgNVBAoTCkNlcnRpcG9zdGUxG
zAZBgNVBAMTEkNlcnRpcG9zdGUgU2VydmV1cjCCASEwDQYJKoZIhvcNAQEBBQADggEOADCCAQkC
ggEAPqd4MziR4spWldGRx8bQrhZkonWnNm`+Yhb7+4Q67ecf1janH7GcN/SXsfx7jJpreWULf7v
7Cvpr4R7qIJcmdHIntmf7JPM5n6cDBv17uSW63er7NkVnMFHwK1QaGFLMybFkzaeGrvFm4k3lRe
fiXDmuOe+FhJgHYezYHf44LvPRPwhSrzi9+Aq3o8pWDguJuZDIUP1F1jMa+LPwvREXfFcUW+w==

-----END CERTIFICATE-----

2. Save the text file in .cer format on the computer runnin g the Web browser that is bein g

used to configure the gateway (or in a place that is accessible to it).

3. Open the Certificates page again (Configuration tab > System menu > Certificates).

Figure 4-20: Certificates

4. Under the Upload certificate files from your computer grou p, locate the tex t “Send

Device Certificate file from your computer to the device". Click the Browse button
below this text, navigate to the .cer file that contains the certificate, and then click

Send File.

5. Download the following:

• Root CA certificate from the CA Web site (varies from one enterprise CA to

another)

• GTE CyberTrust Root CA certificate (see Figure 4-21 on page 39)

• Baltimore CyberTrust root CA (see Figure 4-22 on page 40).

Configuration Note 4. Configure AudioCodes Mediant Gateway

Version 6.8 39 February 2014

6. Us e a text editor to c om bine all three of them on the sam e file and save th is f ile in .cer

format.

Figure 4-21: GTE CyberTrust Root CA Certificate

-----BEGIN CERTIFICATE----­MIICWjCCAcMCAgGlMA0GCSqGSIb3DQEBBAUAMHUxCzAJBgNVBAYTAlVTMR

gwFgYD
VQQKEw9HVEUgQ29ycG9yYXRpb24xJzAlBgNVBAsTHkdURSBDeWJlclRydX

N0IFNv
bHV0aW9ucywgSW5jLjEjMCEGA1UEAxMaR1RFIEN5YmVyVHJ1c3QgR2xvYm

FsIFJv
b3QwHhcNOTgwODEzMDAyOTAwWhcNMTgwODEzMjM1OTAwWjB1MQswCQYDVQ

QGEwJV
UzEYMBYGA1UEChMPR1RFIENvcnBvcmF0aW9uMScwJQYDVQQLEx5HVEUgQ3

liZXJU
cnVzdCBTb2x1dGlvbnMsIEluYy4xIzAhBgNVBAMTGkdURSBDeWJlclRydX

N0IEds
b2JhbCBSb290MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCVD6C28F

Cc6HrH
iM3dFw4usJTQGz0O9pTAipTHBsiQl8i4ZBp6fmw8U+E3KHNgf7KXUwefU/

ltWJTS
r41tiGeA5u2ylc9yMcqlHHK6XALnZELn+aks1joNrI1CqiQBOeacPwGFVw

1Yh0X4
04Wqk2kmhXBIgD8SFcd5tB8FLztimQIDAQABMA0GCSqGSIb3DQEBBAUAA4

GBAG3r
GwnpXtlR22ciYaQqPEh346B8pt5zohQDhT37qw4wxYMWM4ETCJ57NE7fQM

h017l9
3PR2VX2bY1QY6fDq81yx2YtCHrnAlU66+tXifPVoYb+O7AWXX1uw16OFNM

Qkpw0P
lZPvy5TYnh+dXIVtx6quTx8itc2VrbqnzPmrC3p/

-----END CERTIFICATE-----

Microsoft Office 365 Exchange UM with Leg acy PBX

AudioCodes Mediant Gateway 40 Document #: LTRT-40512

Figure 4-22: Baltimore CyberTrust Root CA

-----BEGIN CERTIFICATE----­MIIDdzCCAl+gAwIBAgIEAgAAuTANBgkqhkiG9w0BAQUFADBaMQswCQYDVQ

QGEwJJ
RTESMBAGA1UEChMJQmFsdGltb3JlMRMwEQYDVQQLEwpDeWJlclRydXN0MS

IwIAYD
VQQDExlCYWx0aW1vcmUgQ3liZXJUcnVzdCBSb290MB4XDTAwMDUxMjE4ND

YwMFoX
DTI1MDUxMjIzNTkwMFowWjELMAkGA1UEBhMCSUUxEjAQBgNVBAoTCUJhbH

RpbW9y
ZTETMBEGA1UECxMKQ3liZXJUcnVzdDEiMCAGA1UEAxMZQmFsdGltb3JlIE

N5YmVy
VHJ1c3QgUm9vdDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAK

MEuyKr
mD1X6CZymrV51Cni4eiVgLGw41uOKymaZN+hXe2wCQVt2yguzmKiYv60iN

oS6zjr
IZ3AQSsBUnuId9Mcj8e6uYi1agnnc+gRQKfRzMpijS3ljwumUNKoUMMo6v

WrJYeK
mpYcqWe4PwzV9/lSEy/CG9VwcPCPwBLKBsua4dnKM3p31vjsufFoREJIE9

LAwqSu
XmD+tqYF/LTdB1kC1FkYmGP1pWPgkAx9XbIGevOF6uvUA65ehD5f/xXtab

z5OTZy
dc93Uk3zyZAsuT3lySNTPx8kmCFcB5kpvcY67Oduhjprl3RjM71oGDHweI

12v/ye
jl0qhqdNkNwnGjkCAwEAAaNFMEMwHQYDVR0OBBYEFOWdWTCCR1jMrPoIVD

aGezq1
BE3wMBIGA1UdEwEB/wQIMAYBAf8CAQMwDgYDVR0PAQH/BAQDAgEGMA0GCS

qGSIb3
DQEBBQUAA4IBAQCFDF2O5G9RaEIFoN27TyclhAO992T9Ldcw46QQF+vaKS

m2eT92
9hkTI7gQCvlYpNRhcL0EYWoSihfVCr3FvDB81ukMJY2GQE/szKN+OMY3EU

/t3Wgx
jkzSswF07r51XgdIGn9w/xZchMB5hbgF/X++ZRGjD8ACtPhSNzkE1akxeh

i/oCr0
Epn3o0WC4zxe9Z2etciefC7IpJ5OCBRLbf1wbWsaY71k5h+3zvDyny67G7

fyUIhz
ksLi4xaNmjICq44Y3ekQEe5+NauQrz4wlHrQMz2nZQ/1/I6eYs9HRCwBXb

sdtTLS
R9I4LtD+gdwyah617jzV/OeBHRnDJELqYzmp

-----END CERTIFICATE-----

7. Download the Root CA certificate from the CA Web site and download the GTE

CyberTrust Root CA certif ic ate. Usi ng a text ed itor, c om bine them in the sam e f ile and
save this file in .cer format.

Configuration Note 4. Configure AudioCodes Mediant Gateway

Version 6.8 41 February 2014

8. In the Upload certificate files from your computer group of the Certificates page,

locate the text "Send Trusted Root Certificate Store file from your computer to the
device", click the Browse button below this text, nav igate to the .cer file that contains
the Root CA certificates, and then click Send File.

Figure 4-23: Loading Certificates

9. When the certificate has loaded, click Burn to save the settings, and reset the device.

Microsoft Office 365 Exchange UM with Leg acy PBX

AudioCodes Mediant Gateway 42 Document #: LTRT-40512

4.14 Configure Voice Mail Interface

The procedure below desc ribes ho w to configure th e voice m ail interf ace. This enabl es the
device's Voice Mail application and determines the communication method between the
PBX and the device.

 To configure the voice mail interface:

1. Open the Voice M ail Settings page (Configuration tab > VoIP menu > Services >

Voice Mail Settings).

Figure 4-24: Voice Mail Interface Configuration

2. From the 'Voice Mail Interface' drop-down list, select your voice m ail interface to the

PBX (i.e. QSIG).

3. Click Submit.

Configuration Note 4. Configure AudioCodes Mediant Gateway

Version 6.8 43 February 2014

4.15 Configure Message Waiting Indicator

The procedure below describes how to configure the Message Waiting Indicator (MWI).

 To configure MWI:

1. Open the Suppl ementary Services pa ge (Configuration tab > VoIP menu > GW an d

IP to IP > DTMF and Supplementary > Supplementary Services).

Figure 4-25: MWI Configuration

2. From the 'Enable MWI’ drop-down list, select Enable.

3. Open the DTMF & D ialing page ( Configuration tab > VoIP menu > GW and IP to IP

> DTMF and Supplementary > DTMF & Dialing).

4. Set the ‘Default Destination Number’ field to "serveduser".

Figure 4-26: Default Destination Number Configuration

5. Open the Proxy & Registration page (Configuration tab > VoIP menu > SIP

Definitions > Proxy & Registration).

6. From the ‘Subscription Mode’ drop-down list, select Per Gateway.

Figure 4-27: Subscription Mode Configuration

Microsoft Office 365 Exchange UM with Leg acy PBX

AudioCodes Mediant Gateway 44 Document #: LTRT-40512

4.16 Reset the Gateway

After completing the co nfiguration of the Gateway, save ("burn") the configuration to the
Gateway's flash memory with a reset, for the settings to take effect.

 To save the configuration to flash me m ory:

1. Open the Maintenance Actions page (Maintenance tab > Maintenance menu >

Maintenance Actions).

Figure 4-28: Resetting the SBC

2. Ensure that the 'Burn to FLASH' field is set to Yes (default).

3. Click the Reset button.

Configuration Note 4. Configure AudioCodes Mediant Gateway

Version 6.8 45 February 2014

Reader's Notes

www.audiocodes.c

Configuration Note

www.audiocodes.com