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 nband 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
Loading...