Exchange Unified Messaging: The Feature Set and PBX ConnectivityMario D’SilvaNational Technology SpecialistsUnified Communications
UNC307
Why we need Unified Messaging (UM)
Microsoft Exchange Server UM Architecture
Session Objectives and Agenda
UM and IP PBX direct inter-operation - DEMONews and demos
UM/PBX connectivity resources
Questions and (hopefully) Answers
“Think Unified Messaging is hard to deploy? Think again! This session will provide an overview of the technical components of Exchange 2007 UM, explain how UM connects to PBX and IP PBX equipment, and demonstrate configurations of UM deployments, all in one session!”
Why We Need Unified MessagingProblems of disunity
Voice and e-mail as separate inboxes Different servers, access mechanisms
Desktop software (e-mail)Phone (voice mail)
Fax messagesStand-alone fax machines
Users and administrators must manage their messages from multiple locations with different tools
“With Exchange Server 2007, we look forward to being able to communicate better…Will this technology help us sell more golf clubs? In this case, yes, we believe that better communication will help us sell more golf clubs.”
—Eric Hart, End-User Computing Manager, PING Inc.
Exchange Server Unified Messaging
Convenient, integrated access to your vital business communicationsReducing costs, increasing operational efficiency by consolidating infrastructure, training
Unified store, transport, directoryIncreasing client reach of Exchange to the telephone
“Anywhere access” to your messages, calendar, contacts
Delivering on a clear, simple vision
“Having anywhere access to e-mail and voice mail is going to be a huge benefit... People can access information and interact with it using a variety of devices, at work, at home, and on the road; and all of this translates directly into productivity.”
—Steven Presley, Senior IT Engineer for Messaging, QUALCOMM
Exchange Server UM Architecture
VoIP protocols (SIP, RTP, T.38) between UM and IP PBX/gatewayWorks with many varieties of PBX Well suited to site consolidationScalable, reliable
Exchange UM with a TDM PBX
VoIP Gatewa
y
Unified Messaging Server Role
Hub Transport
Server Role
Exchange Mailbox Server Role
Active Directory
Phone Company’s
Central Office
Traditional PBX
Internal Phone
External Phone
UM and Direct IP PBX Connectivity
Unified Messaging Server Role
Hub Transport
Server Role
Exchange Mailbox Server Role
Active Directory
Phone Company’s
Central Office
IP PBX
Internal Phone
External Phone
Unified Messaging Setup and Features
Johann KruseNational Technology SpecialistUnified Communications
demo
UM/PBX Configuration Notes
Microsoft template document covering how to configure PBXs/Gateways to work with UMConfig. notes:
Gateway partner config notes – AudioCodes & Dialogic:
Author the docs and publish them on their Web sites
IP PBX config notes:Vendors sign up to support their IP PBX with Exchange UM. Author a config note and publish it on their web sites
UNC309 Regulatory Compliance in Microsoft Exchange Server 2007
UNC310 Planning and Deploying Microsoft Office Communications Server 2007 and Office Communicator 2007
UNC305 Microsoft Exchange Server 2007 Deployment Planning and High Availability in SP1
UNC306 Topology and Routing for Microsoft Exchange Server 2007
UNC308 Microsoft Windows PowerShell Scripting for Microsoft Exchange Server 2007
UNC309 Regulatory Compliance in Microsoft Exchange Server 2007
UNC311 On-Premise Conferencing Delivering Enterprise-Class Voice, Video and Web Conferencing with Microsoft Office Communications Server 2007
UNC312 Planning Voice Deployment for Microsoft Office Communication Server 2007
UNC312 Voice and Video in Microsoft Office Communication Server 2007: Insights to Quality of Experience and Planning for Network Bandwidth Usage
Related Content
ResourcesDoes UM work with my PBX?http://www.microsoft.com/technet/prodtechnol/exchange/tel-advisor.mspx
e.g., Cisco Call Manager 5.x PBX config. noteUM Specialists
http://www.microsoft.com/technet/prodtechnol/exchange/pbx-partners.mspx
Evaluation Forms
Questions?
© 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after
the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.