Export (0) Print
Expand All

Telephony Advisor for Exchange Server 2007

 

Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1

Topic Last Modified: 2010-12-13

Unified Messaging (UM) requires that you integrate Microsoft Exchange Server 2007 with the existing telephony system for your organization. A successful deployment requires careful analysis of your existing telephony infrastructure and for you to perform the correct planning steps to deploy Unified Messaging. However, the planning phase can be a significant challenge to Exchange administrators who have little or no experience with a telephony network. To help address this challenge, see Resources to Help With Your UM Deployment later in this topic.

To see the supported IP gateways for Unified Messaging, if your PBX is supported using a specific IP gateway model or manufacturer, or if your IP PBX is supported using direct SIP connection, click one of the following links:

Telephony networks are quite diverse and proprietary because they can include IP gateways, IP PBXs, and PBXs that all have different configuration settings, firmware, and requirements. This diversity makes planning and deploying Unified Messaging somewhat challenging. However, several resources are available to assist you in successfully deploying Unified Messaging:

  • Unified Messaging specialists   UM Specialists are systems integrators who have received technical training about Exchange 2007 Unified Messaging that was conducted by the Microsoft Exchange engineering team. To help ensure a smooth transition to Exchange 2007 Unified Messaging from legacy voice mail systems, Microsoft recommends that all customers engage with a UM Specialist. For contact information, visit Microsoft Exchange Server 2007 Unified Messaging (UM) Specialists.

  • PBX configuration notes   PBX configuration notes contain configuration settings and other information that is very useful when you are configuring IP gateways, IP PBXs, and PBXs to communicate with the Unified Messaging servers that are on the network. For more information about PBX Configuration Notes, see PBX Configuration Notes Tested by Microsoft or IP Gateway Vendor Partners.

Before you engage a Unified Messaging specialist, you should be able to answer key questions that they will ask. Having the answers to the following questions will help make the conversation between you and the UM Specialist productive:

  • How many existing telephone or voice mail users, or both, are in your organization?

  • How many users do you intend to provide with Exchange 2007 Unified Messaging?

  • Which PBX or PBXs do you intend to use for integration with Exchange 2007 Unified Messaging?

  • How many PBXs does your organization have? Please specify the vendors, types (circuit- or IP-based), models, and firmware versions.

  • Are the PBXs networked, and are they centralized or located in multiple locations?

  • What voice mail system or systems does your organization currently use? Please specify the vendors, types, models, and firmware versions.

  • How are the voice mail systems integrated into your PBXs (Analog, T1/E1, PRI, Digital set emulation, VoIP, other)?

  • Are you currently using voice networking?

  • What type of fax system or systems does your organization use, and does the fax system or systems support inbound fax routing to Exchange?

  • Does your organization use automated attendants?

  • Do you require support for phone-only users, that is, users that will have no e-mail access?

Integrating Exchange 2007 Unified Messaging with PBXs requires that you use one or more IP gateways to translate the circuit-switched protocols that are used by TDM-based PBXs to IP-based, packet-switched protocols that are used by Exchange 2007 Unified Messaging. IP gateway vendors with several models of IP gateways have been tested and are supported for Exchange 2007 Unified Messaging.

Interoperability testing of Exchange 2007 Unified Messaging with IP gateways is now integrated with the Microsoft Unified Communications Open Interoperability Program. For more information, see Microsoft Unified Communications Open Interoperability Program.

The Microsoft Unified Communications Open Interoperability Program qualification program for IP gateways and IP PBXs ensures that customers have a seamless setup and support experience when they're using qualified telephony gateways and IP-PBXs with Microsoft Unified Communications software.

Only products that meet rigorous and extensive testing requirements and conform to the specifications and test plans receive qualification.

Interoperability was verified for the following IP gateway vendors in the following years:

  • AudioCodes and Dialogic: 2006

  • NET and Quintum: 2008

Table 1 shows the IP gateway vendor, the IP gateway model, and the protocols that are supported by each model.

Table 1   Supported IP gateways for Unified Messaging

Vendor Model Supported protocols

AudioCodes

MediaPack 114/8 FXO

  • Analog with In-Band DTMF

  • Analog with SMDI

AudioCodes

Mediant 1000

  • Analog with In-Band DTMF

  • Analog with SMDI

  • BRI Q.SIG

  • T1/E1 Q.SIG

  • IP-to-IP

AudioCodes

Mediant 2000

  • T1/E1 CAS

  • T1/E1 Q.SIG

  • IP-to-IP

Dialogic

DMG1000PBXDNIW

Digital Set Emulation

Dialogic

DMG1000LSW

  • Analog with In-Band DTMF

  • Analog with SMDI

Dialogic

DMG2000

  • T1 CAS

  • T1/E1 Q.SIG

Dialogic

DMG3000

  • BRI Q.SIG

NET

VX Series

  • T1 E1 Q.SIG

Quintum

Tenor DX Series

  • CAS T1 E1 Q.SIG

For more information about AudioCodes Mediant and MP-114/8 FXO IP gateways, see AudioCodes Media Gateways for Microsoft Unified Communications.

For more information about Dialogic IP gateways, see Dialogic Media Gateways for Microsoft Exchange Server Unified Messaging.

For more information about NET IP gateways, see NET Intelligent Voice Gateways.

For more information about Quintum IP gateways, see Quintum Enterprise Solutions - VoIP Products.

noteNote:
The third-party Web site information in this topic is provided to help you find the technical information you need. The URLs are subject to change without notice.

Table 2 shows the PBXs that are supported using AudioCodes IP gateways including MediaPack-114 FXO, MediaPack-118 FXO, and Mediant 2000.

Table 2   PBXs Supported with an AudioCodes IP gateway

PBX manufacturer PBX model/type AudioCodes model “x” - replace with 4 or 8 per need “y” - replace with 1, 2, 4, 8 or 16 per need

Alcatel

OmniPCX 4400

  • MediaPack 11x/FXO/AC/SIP-0

  • Mediant2000/ySpans/SIP

Astra

M1000, M2000

  • Mediant2000/ySpans/SIP

Avaya

Definity G3

  • MediaPack 11x/FXO/AC/SIP-0

  • Mediant1000/ySpans/SIP

  • Mediant2000/ySpans/SIP

Avaya

Magix/Merlin

  • MediaPack 11x/FXO/AC/SIP-0

Avaya

S8300

  • MediaPack 11x/FXO/AC/SIP-0

  • Mediant1000/ySpans/SIP

  • Mediant2000/ySpans/SIP

Avaya

S8700

  • MediaPack 11x/FXO/AC/SIP-0

  • Mediant1000/ySpans/SIP

  • Mediant2000/ySpans/SIP

Avaya

IP Office

  • MediaPack 11x/FXO/AC/SIP-0

  • Mediant2000/ySpans/SIP

Cisco

CallManager 4.x

  • Mediant1000/IP-to-IP

  • Mediant2000/IP-to-IP

NEC

Electra Elite

  • MediaPack 11x/FXO/AC/SIP-0

NEC

NEAX2400

  • MediaPack 11x/FXO/AC/SIP-0

  • Mediant2000/ySpans/SIP/RS232

NeXspan

S

  • MediaPack 11x/FXO/AC/SIP-0

Nortel

Communication Server-1000M, 1000S, 1000E

  • Mediant1000/ySpans/SIP

  • Mediant2000/ySpans/SIP

Nortel

Meridian 11c, 51c, 61c, 81c

  • Mediant1000/ySpans/SIP

  • Mediant2000/ySpans/SIP

Panasonic

KX-TES824, KX-TEA308

  • MediaPack 11x/FXO/AC/SIP-0

Panasonic

KX-TDA30, KX-TDA100, KX-TDA200, KX-TDA600

  • MediaPack 11x/FXO/AC/SIP-0

Shortel

IP Telephony System

  • MediaPack 11x/FXO/AC/SIP-0

Siemens

HiCom 150E

  • MediaPack 11x/FXO/AC/SIP-0

Siemens

HiPath 3550

  • MediaPack 11x/FXO/AC/SIP-0

Siemens

HiPath 4000

  • MediaPack 11x/FXO/AC/SIP-0

  • Mediant1000/ySpans/SIP

  • Mediant2000/ySpans/SIP

Tadiran Telecom

Coral Flexicom, Coral IPX

  • MediaPack 11x/FXO/AC/SIP-0

  • Mediant1000/ySpans/SIP

  • Mediant2000/ySpans/SIP

Each Dialogic IP gateway model supports different PBXs. Tables 3, 4, and 5 show you the PBX manufacturer and model and which Dialogic IP gateway can be used. Each IP gateway uses different signaling methods, densities, and protocols.

Table 3 shows the PBXs that are supported with the low-density Dialogic Media Gateway (DMG1000). However, when an analog DMG1000 is used, supplemental signaling (RS232 SMDI, MD110, MCI protocols, or Inband DTMF signaling) is required.

Table 3   PBXs supported using a low-density Dialogic DMG1000 series IP gateway

PBX manufacturer PBX model/type DMG model and additional signaling

Aastra

Aastra MD110 (formerly Ericsson MD110)

DMG1008LSW

Analog connectivity using the MD110 RS232 protocol

Alcatel

Omni PCX 4400

DMG1008LSW

Avaya

Definity G3 S8100, S8300, S8700, and S8710 (Communications Mgr SW V2.0 or later)

DMG1008DNIW

Intercom

 

DMG1008LSW

Analog connectivity using SMDI serial protocol

Mitel

SX-200D, SX-200 Light, SX-2000 Light, SX-2000 S, SX-2000 VS, SX-200 ICP

DMG1008MTLDNIW

NEC

2000, 2400, 2400 IPX

DMG1008DNIW

Nortel

Meridian 1 - Option 11, 21, 21A, 51, 61, 71, and 81

Meridian SL1 - Generic X11, Release 15 or later

Nortel Communication Server - 1000M, 1000S, 1000E with V3.0 or later

DMG1008DNIW

Nortel

SL 100

DMG1008LSW

Analog connectivity using SMDI serial protocol

Siemens

HiCom 300E CS

DMG1008DNIW

Siemens

HiCom 300E (European)

DMG1008LSW

Analog connectivity using Inband DTMF signaling

Siemens/ROLM

8000 (SW release 80003 or later)
9000 (All versions)

9751 (All versions of SW release 9005)

9751 (SW release 9006.4 or later)

DMG1008RLMDNIW

Siemens

HiPath 4000

DMG1008LSW

Toshiba

CTX (SW version AR1ME021.00)

DMG1008LSW

Others

Various

DMG1008LSW

Analog connectivity using either Inband DTMF or SMDI

Table 4 shows the PBXs that are supported with the T1/E1 Dialogic Media Gateway (DMG2000). The DMG2000 gateway, which comes in single span (DMG2030DTIQ), dual span (DMG2060DTIQ), or quad span (DMG2120DTIQ) densities, supports the following protocols:

  • T1 CAS

  • T1 Q.SIG

  • E1 Q.SIG

  • T1 NI-2

  • T1 5ESS

  • T1 DMS100

If Channel Associated Signaling (CAS) signaling is used, supplemental signaling (RS232 SMDI, MD110, MCI protocols, or Inband DTMF signaling) is required. If Q.SIG signaling is used, the PBX must support the supplemental services that are associated with calling and called party Information and the call transfer capabilities required by Exchange 2007 Unified Messaging.

Table 4   PBXs supported with the DMG2000 Media Gateway

PBX manufacturer PBX model/type Required software version Protocol and additional signaling

Alcatel

Omni PCX 4400

Version 3.2.712.5

T1 Q.SIG

E1 Q.SIG

Avaya

Definity G3

Version 3 or later

T1 CAS

Avaya

S8500

Manager SW V2.0 or later

T1 CAS

T1 Q.SIG

E1 Q.SIG

Ericsson

MD110

Release MX1 TSW R2A (BC13)

E1 Q.SIG

Intercom

 

 

CAS (w/ SMDI serial protocol)

NEC

2400 IMX

Release 5200 Dec. 92 1b or later

CAS (w/ MCI serial protocol)

NEC

2400 IPX

R17 Release 03.46.001

T1 Q.SIG

Nortel

Meridian 1 - Option 11

Release 15 or later, and options 19 and 46 are required

T1 Q.SIG

E1 Q.SIG

Nortel

Communication Server 1000

Version 2121, Release 4

T1 Q.SIG

E1 Q.SIG

Siemens

HiCom 300E CS

Release 9006.4 or later (Note: North American software load only)

T1 CAS

Siemens

HiPath 4000

V2 SMR 9 SMPO

T1 Q.SIG

E1 Q.SIG

Mitel

SX-2000 S, SX-2000 VS

LW 34

T1 Q.SIG

E1 Q.SIG

Mitel

3300

Version 5.1.4.8

T1 Q.SIG

E1 Q.SIG

The DMG4000 series Media Gateway comes in several TDM interface options. The DMG4008BRI supports 4-port/8-channel densities and supports the following protocols:

  • ISDN BRI Q.SIG

  • ETSI-DSS1 (Euro ISDN)

  • NET 3 (Belgium)

  • VN3 (France)

  • 1TR6 (Germany)

  • INS-64 (Japan)

  • 5ESS Custom (North America - AT&T)

  • National ISDN (NI1 - North America)

Table 5 shows the PBXs that are supported using a DMG4008BRI Media Gateway.

Table 5   PBXs supported using a DMG4008BRI Series Media Gateway

PBX manufacturer PBX model/type Required software version Protocol and additional signaling

Siemens

HiCom 300

SA300-V3.05

BRI-Q.SIG (ECMAV2)

Siemens

HiPath 4000

S.0 B4400

BRI-Q.SIG (ECMAV2)

NET and Quintum gateways come in a variety of port densities, up to 8 × T1 spans. Table 6 shows the PBXs that are supported using NET and Quintum IP gateways.

Table 6   PBXs supported using NET and Quintum IP Gateways

PBX manufacturer PBX model/type Make and Model

Avaya

Communication Manager (S8700/S8500/S8400)

  • NET VX1200

  • NET VX 1800

Avaya

IP Office

  • NET VX1200

  • NET VX1800

Nortel

Meridian 11c

  • NET VX1200

  • Quintum Tenor DX Series (available with 2, 4, 6, or 8 T1 spans)

IP PBXs are also supported by Exchange 2007 Unified Messaging. Table 7 shows the IP PBXs that are supported using a direct SIP connection to Exchange 2007 Unified Messaging.

Table 7   IP PBXs supported using a direct SIP connection

PBX manufacturer PBX model/type Required software version

Avaya

Communications Manager

4.0.1

Avaya

Communications Manager

5.0

Cisco

CallManager

5.0, 5.1, 6.0, 6.1, and 7.0

Interactive Intelligence

Customer Interaction Center

2.4

Mitel

3300 CXi, CX / MXe

7.1 UR2

Nortel

Communication Server 1000

5.0, 5.5

Nortel

Communication Server 2000

SN10, CVM11

Nortel

Communication Server 2100

SE10, SE11

Pbxnsip Inc.

Pbxnsip

2.2

IP PBXs are also supported by Exchange 2007 Unified Messaging. Table 8 shows the IP PBXs that are supported using IP to IP capabilities of SIP media gateways to connect to Exchange 2007 Unified Messaging.

Table 8   IP PBXs supported using a SIP Media Gateway

PBX manufacturer PBX model/type SIP Gateway Model

Cisco

CallManager 4.x

AudioCodes Mediant 1000/2000 (IP-to-IP enabled)

Microsoft Exchange Server 2007 Unified Messaging with Service Pack 1 (SP1) and Microsoft Office Communications Server 2007 can be deployed together to provide voice messaging, Instant Messaging (IM), enhanced user presence, audio-video conferencing, and an integrated e-mail and messaging experience for users in your organization. For more information, see:

To find out more about the Microsoft Unified Communications Open Interoperability Program for enterprise telephony infrastructure, including finding qualified SIP PSTN gateways and IP PBXs and the process for telephony infrastructure vendors to join and participate in the program, see Microsoft Unified Communications Open Interoperability Program.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft