2. Mario D’Silva National Technology Specialists Unified Communications UNC307

3. Why we need Unified Messaging (UM) Microsoft Exchange Server UM Architecture UM and IP PBX direct inter-operation - DEMO News 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!”

4. Voice and e-mail as separate inboxes Different servers, access mechanisms Desktop software (e-mail) Phone (voice mail) Fax messages Stand-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.

5. Convenient, integrated access to your vital business communications Reducing costs, increasing operational efficiency by consolidating infrastructure, training Unified store, transport, directory Increasing 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

6. VoIP protocols (SIP, RTP, T.38) between UM and IP PBX/gateway Works with many varieties of PBX Well suited to site consolidation Scalable, reliable

7. VoIP Gateway 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

8. 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

9. Johann Kruse National Technology Specialist Unified Communications

10. Microsoft template document covering how to configure PBXs/Gateways to work with UM Config. 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

11. UNC309UNC309 Regulatory Compliance in Microsoft Exchange Server 2007 UNC310UNC310 Planning and Deploying Microsoft Office Communications Server 2007 and Office Communicator 2007 UNC305UNC305 Microsoft Exchange Server 2007 Deployment Planning and High Availability in SP1 UNC306UNC306 Topology and Routing for Microsoft Exchange Server 2007 UNC308UNC308 Microsoft Windows PowerShell Scripting for Microsoft Exchange Server 2007 UNC309UNC309 Regulatory Compliance in Microsoft Exchange Server 2007 UNC311UNC311 On-Premise Conferencing Delivering Enterprise-Class Voice, Video and Web Conferencing with Microsoft Office Communications Server 2007 UNC312UNC312 Planning Voice Deployment for Microsoft Office Communication Server 2007 UNC312UNC312 Voice and Video in Microsoft Office Communication Server 2007: Insights to Quality of Experience and Planning for Network Bandwidth Usage

12. Does 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

15. © 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.