Telephony Advisor for Exchange Server 2007
Telephony Advisor for Exchange Server 2007
Introduction
Deploying Exchange 2007 Unified Messaging (UM) requires integrating Exchange Server 2007 with your organization’s existing telephony system. A successful deployment requires careful analysis of your existing telephony infrastructure and proper planning, which can be a significant challenge to Exchange Administrators who have little or no telephony knowledge. To assist your organization in this aspect, we are making available the following planning resources:
UM Specialists
These are Systems Integrators who have received technical training on Exchange UM conducted by Microsoft Exchange Engineering Team. To ensure a smooth transition to Exchange UM from legacy voicemail systems, Microsoft recommends all customers to engage the assistance of the UM Specialists. For contact information, visit here.
Top 10 Questions You need to Answer
Prior to engaging the UM Specialists, you should have ready the answers to the 10 most-commonly-asked questions listed below. This is to facilitate the interaction between you and the UM Specialist.
|
1. |
How many existing phone and/or voicemail users are there in your organization and how many users do you intend to provide with Exchange 2007 UM? |
|
2. |
Which PBX(s) do you intend to use for integration with Exchange 2007 UM? |
|
3. |
How many PBX(s) does your organization have? Please specify the vendors, types (circuit- or IP-based), models and firmware versions. |
|
4. |
Are the PBXs networked? Are they centralized or located in multiple locations? |
|
5. |
What voicemail system(s) is your organization currently using? Please specify the vendors, types, models and firmware versions. |
|
6. |
How are the voicemail system(s) integrated into your PBX(s) (Analog, T1/E1, PRI, Digital set emulation, VoIP etc)? |
|
7. |
Are you currently using voice networking? |
|
8. |
What fax service(s) is your organization using? Does the fax system(s) support inbound fax routing to Exchange? |
|
9. |
Are you using Automated Attendant system(s)? |
|
10. |
Do you require support for phone-only users (i.e., no email)? |
Supported VoIP Gateways
Integrating Exchange 2007 UM with TDM-based PBXs requires the use of VoIP gateway(s) to translate the media and signaling data between circuit-switched protocol formats (understood by TDM-based PBXs) and IP-based, packet-switched formats (understood by Exchange 2007 UM). Currently, there are two vendors and several models of VoIP gateways that have been tested and are supported for Exchange 2007 UM, including:
|
AudioCodes |
MediaPack 114/8 FXO |
| • |
Analog with In-Band DTMF |
| • |
Analog with SMDI | |
|
AudioCodes |
Mediant 2000 |
| • |
T1/E1 CAS |
| • |
T1/E1 Q.SIG | |
|
Dialogic |
PIMG80PBXDNI |
|
|
Dialogic |
PIMG80LS |
| • |
Analog with In-Band DTMF |
| • |
Analog with SMDI | |
|
Dialogic |
TIMG300DTI, TIMG600DTI |
|
For more information about AudioCodes MP-114/8 FXO gateways, visit AudioCodes website.
For more information about AudioCodes Mediant gateways, visit AudioCodes website.
For more information on Dialogic gateways, visit Dialogic website.
Supported PBXs
The following PBXs are supported through AudioCodes gateways (MediaPack-114 FXO, MediaPack-118 FXO and Mediant 2000).
|
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
Mediant2000/ySpans/SIP |
|
Avaya |
Magix/Merlin |
MediaPack 11x/FXO/AC/SIP-0 |
|
Avaya |
S8300 |
MediaPack 11x/FXO/AC/SIP-0
Mediant2000/ySpans/SIP |
|
Avaya |
S8700 |
MediaPack 11x/FXO/AC/SIP-0
Mediant2000/ySpans/SIP |
|
Avaya |
IP Office |
MediaPack 11x/FXO/AC/SIP-0
Mediant2000/ySpans/SIP |
|
NEC |
Electra Elite |
MediaPack 11x/FXO/AC/SIP-0 |
|
NEC |
NEAX2400 |
MediaPack 11x/FXO/AC/SIP-0
Mediant2000/ySpans/SIP/RS232 |
|
Nortel |
CS-1000M, 1000S, 1000E |
Mediant2000/ySpans/SIP |
|
Nortel |
Option 81c |
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 |
|
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
Mediant2000/ySpans/SIP |
|
Tadiran Telecom |
Coral |
MediaPack 11x/FXO/AC/SIP-0
Mediant2000/ySpans/SIP |
The following PBXs are supported through the Dialogic® PBX IP Media Gateway (PIMG). When an analog PIMG is used, supplemental signaling (RS232 SMDI, MD110 or MCI protocols, or Inband DTMF signaling) is required.
|
Alcatel |
Omni PCX 4400 |
PIMG80LS |
|
Avaya |
Definity G3 S8100, S8300, S8700, & S8710 (Communications Mgr SW V2.0 or greater) |
PIMG80DNI |
|
Mitel |
SX-200D, SX-200 Light, SX-2000 Light, SX-2000 S, SX-2000 VS, SX-200 ICP |
PIMG80MTLDNI |
|
Nortel |
Meridian 1 - Option 11, 21, 21A, 51, 61, 71, and 81
Meridian SL1 - Generic X11, Release 15 or greater
Nortel Communication Server - 1000M, 1000S, 1000E with Rls V3.0 or greater |
PIMG80DNI |
|
Nortel |
SL 100 |
PIMG80LS
Analog connectivity using SMDI serial protocol |
|
NEC |
2000, 2400, 2400 IPX |
PIMG80DNI |
|
Siemens |
HiCom 300E CS |
PIMG80DNI |
|
Siemens |
HiCom 300E (European) |
PIMG80LS
Analog connectivity using Inband DTMF signaling. |
|
Siemens/ROLM |
8000 (SW release 80003 or greater)
9000 (All versions)
9751 (All version of SW release 9005)
9751 (SW release 9006.4 or greater) |
PIMG80RLMDNI |
|
Siemens |
HiPath 4000 |
PIMG80LS |
|
Ericsson |
MD110 |
PIMG80LS
Analog connectivity using the MD110 RS232 protocol |
|
Intecom |
|
PIMG800LS
Analog connectivity using SMDI serial protocol |
|
Toshiba |
CTX (SW version AR1ME021.00) |
PIMG80LS |
|
Others |
Various |
PIMG80LS
Analog connectivity using either Inband DTMF or SMDI |
The following PBXs are supported through the Dialogic® T1/E1 Media Gateway (TIMG). The gateway, which comes in single span (TIMG300DTIQ), dual span (TIMG600DTIQ) or quad span (TIMG1200DTIQ) densities, supports the following protocols:
| • |
T1 CAS |
| • |
T1 QSIG |
| • |
E1 QSIG |
If CAS signaling is used, supplemental signaling (RS232 SMDI, MD110 or MCI protocols, or Inband DTMF signaling) is required. If QSIG signaling is used, the PBX must support the supplemental services associated with Call Party Information and the Call Transfer capabilities required by Exchange 2007 UM.
|
Alcatel |
Omni PCX 4400 |
Version 3.2.712.5 |
T1 QSIG
E1 QSIG |
|
Avaya |
Definity G3 |
Version 3 or greater |
T1 CAS |
|
Avaya |
S8500 |
Manager SW V2.0 or greater |
T1 CAS
T1 QSIG
E1 QSIG |
|
Nortel |
Meridian 1 - Option 11 |
Release 15 or greater, and options 19 and 46 are required |
T1 QSIG |
|
Nortel |
Communications Server 1000 |
Version 2121, Release 4 |
T1 QSIG |
|
NEC |
2400 IMX |
Release 5200 Dec. 92 1b or greater |
CAS (w/ MCI serial protocol) |
|
NEC |
2400 IPX |
R17 Release 03.46.001 |
T1 QSIG |
|
Siemens |
HiCom 300E CS |
Release 9006.4 or greater (Note: North American software load only) |
T1 CAS |
|
Siemens |
HiPath 4000 |
V2 SMR 9 SMPO |
T1 QSIG
E1 QSIG |
|
Mitel |
SX-2000 S, SX-2000 VS |
LW 34 |
T1 QSIG
E1 QSIG |
|
Mitel |
3300 |
Version 5.1.4.8 |
T1 QSIG
E1 QSIG |
|
Intecom |
|
|
CAS (w/ SMDI serial protocol) |
Supported IP-PBXs
The following PBXs are supported through direct SIP connection with Exchange Server 2007 UM.
|
Cisco |
CallManager |
5.0, 5.1 |
|
Interactive Intelligence |
Customer Interaction Center |
2.4 |
|
Mitel |
3300 CXi, CX / MXe |
7.1 UR2 |
PBX Configuration Notes
When Microsoft or another company installs Exchange 2007 UM with a new PBX, the installation is documented into a standardized configuration note. Each PBX configuration note contains information about deploying Exchange 2007 UM with a particular PBX. Since PBXs are so diverse and proprietary, PBX planning is probably the most difficult pre-deployment task. To assist you in this planning, we are making available previews of all the PBX configuration notes for your reference. You can use these previews to help decide if Exchange 2007 UM is the appropriate solution for your organization. In each preview, you will find the following:
| • |
The VoIP gateway, if any, required for this deployment, |
| • |
Authors - individuals or companies that participated in creating this configuration note, |
| • |
Detailed pre-requisites to this deployment, including:
| • |
Features that need to be enabled/disabled on the PBX, |
| • |
Specialized PBX hardware that needs to be installed, |
| • |
Features that need to be present on the VoIP gateway, and |
| • |
Specific cabling requirements between the PBX and the VoIP gateway. | |
| • |
Exchange UM feature limitations (a list of UM features that are not available with a particular PBX configuration). |
For the list of available configuration notes, see:
