2 microsoft exchange 2010 um prerequisites – AASTRA MX-ONE V4 with Exchange 2010 Quick Setup Guide User Manual
Page 7
Quick Setup Guide
Doc. No.
ASE/MXO/PLM/ 0141/ EN Rev.C Date: 01.12.2011
7/34
• SIP – Aastra 67xxi family or any device supporting baseline SIP. As the Exchange Server also
supports SIP with Direct Media, MX-ONE gateway resources would not be needed for SIP
devices. But, in order to guarantee interoperability with any 3
rd
party SIP terminal, the SIP
route to Exchange UM can be setup as “forced gateway”. The effect is that SIP calls to the
Exchange UM server will always transit via the MX-ONE media gateway (IPLU or MGU) for a
call setup and media.
• Non SIP – All non SIP devices calling into the Exchange UM server will transit via the MX-
ONE Media GW (IPLU or MGU based) for call setup and media. The following is the list of
supported devices:
o H.323 - Aastra Dialog 4400 IP phones and Aastra 7400 IP phones (incl. Dialog 5446
Premium)
o Digital phones: Aastra Dialog 4200 series digital phones
o Analog phones: Aastra Dialog 4100 series analog phones
o Aastra Cordless Phones: DT690, DT390, DT412, DT422, DT432
o Mobiles devices (no MWI functionality) using MX-ONE’s Mobile extension service.
o External callers coming in via the MX-ONE public access, regardless of the type of
terminal or network connection (SIP or TDM).
3.1.2
Microsoft Exchange 2010 UM Prerequisites
This guide does not cover the Exchange 2010 UM installation, our recommendation is that
Microsoft Exchange 2010 UM shall be installed by a trained Microsoft engineer.
Before to start to install Microsoft Exchange 2010 Unified Messaging server role, please read the
Microsoft Exchange 2010 documentation for a better understanding of the solution requirements.
(
Microsoft Exchange 2010 Unified Messaging server role shall be installed, please check the
document Deploying a New Unified Messaging Environment, (
Checklist for deploying Exchange 2010 Unified Messaging (
Please read carefully Microsoft’s document Overview of Unified Messaging:
(http://technet.microsoft.com/en-us/library/bb125141.aspx9), it explains the relation between the
components that are part of the solution.