Using Exchange Server 2007 for Unified Messaging
•
1 like•471 views
Using Exchange 2007 for Unified Messaging
![Agenda ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
What's hot
What's hot (19)
Similar to Using Exchange Server 2007 for Unified Messaging
Similar to Using Exchange Server 2007 for Unified Messaging (20)
Recently uploaded
Recently uploaded (20)
Using Exchange Server 2007 for Unified Messaging
- 1. How Microsoft IT designed and deployed unified messaging in the enterprise network Using Exchange Server 2007 for Unified Messaging Published: August 2007
- 5. Unified Messaging Prior to Exchange Server 2007 ( Telephony and Network Infrastructure ) Site PBX Connectivity Users Third-party UM servers Redmond Intecom 5 T1 lines 40,000 5 Silicon Valley Nortel SL100 2 T1 lines 1,500 2 Shinjuku Nortel Meridian 2 sets of 16 digital SMDI lines 1,600 2 Mexico City Nortel Meridian 2 sets of 8 digital SMDI lines 500 2 Bangalore Nortel Meridian 2 sets of 8 digital SMDI lines 200 2 Singapore Nortel Meridian 2 sets of 8 digital SMDI lines 600 2 Sao Paulo Nortel Meridian 2 sets of 8 digital SMDI lines 500 2 Austin Nortel Meridian 2 sets of 8 digital SMDI lines 70 2
- 6. Unified Messaging Prior to Exchange Server 2007 ( Connectivity )
- 8. Unified Messaging Prior to Exchange Server 2007 ( E-Mail Messaging Infrastructure ) Data center Region Users Redmond Main campus, other locations in North America, and Latin America 60,000 Dublin Office locations in Europe, Africa, and the Middle East 25,000 Singapore Office locations in Asia and the South Pacific 15,000 Sao Paolo South America 2,000
- 13. Exchange Server 2007 Unified Messaging Design ( Model Configurations )
- 16. Exchange Server 2007 Unified Messaging Design ( Supported VoIP Gateways ) Gateway Connectivity to telecommunications provider Signaling integration Intel PIMG80PBXDNI Digital set emulation Not applicable Intel PIMGG80LS Analog In-band Dual Tone Multiple Frequency (DTMF) or SMDI integration Intel TIMG300DTI00DTI T1 CAS or T1/E1 with Q.SIG Not applicable AudioCodes MediaPack 114/8 FXO Analog In-band DTMF or SMDI integration AudioCodes Mediant 2000 T1/E1 with CAS, and T1/E1 PRI with Q.SIG In-band DTMF or SMDI integration
- 18. Exchange Server 2007 Unified Messaging Design ( VoIP Gateways Selected ) Site connectivity type Example sites Gateway SMDI details T1 CAS–based connection Redmond Intel TIMG600DTI, Intel TIMG300DTI Two gateways connected to a split SMDI cable. Other gateways receive SMDI data through an IP network. T1 Q.SIG–based connection Sao Paulo AudioCodes Not applicable; integration data is carried by the twenty-fourth channel in the T1 PRI. Digital set emulation–based connection Austin, Mexico City Two PIMG80PBXDNI Not applicable.
- 22. Exchange Server 2007 Unified Messaging Implementation ( Migration Approach ) Migration possibilities Overnight migration Staged migration Requires all hardware components to be available at one time. X Can install and configure hardware components over time. X User migration occurs in groups. X Requires configuration and testing. X X Very rapid transition that requires user education before migration. X Can evaluate and fix major configuration issues before large numbers of users are affected. X Allows monitoring of port and server capacity for gradual growth. X Allows periodic issue resolution. X Can pilot with smaller set of users. X
- 34. This document is provided for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY. Microsoft, Microsoft Press, Visual Studio, Visual SourceSafe, Windows and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.
- 35. Appendix
Editor's Notes
- Abstract This technical white paper describes how Microsoft IT provides users the next generation of Unified Messaging functionality with Exchange Server 2007. Introduction The technological advances from the 1970s to the 1990s enabled the birth of new messaging systems such as voice mail, e-mail, and fax, in addition to new methods for voice transmission, such as Voice over IP (VoIP). Traditionally, voice communication involved analog or digital transmission of data over distances by using physical wire through the plain old telephone service (POTS). Voice mail and fax communication occurred through POTS. The advent of the Internet and popularization of IP packet-switched networks gave rise first to e-mail, and then to VoIP communication. All these developments have gradually led to a convergence of disparate communication systems toward a common, unified infrastructure. Microsoft incorporates emerging communication systems and technologies into its corporate environment according to business needs. By deploying Microsoft® Exchange Server 2007, Microsoft benefited from new unified messaging (UM) capabilities that combine voice mail, e-mail, and fax messages into a single Inbox for users. Technologically, Exchange Server 2007 accomplishes this through a new UM server role, which accepts traditional voice data from private branch exchanges (PBXs) through VoIP gateways or directly through IP PBXs. This results in considerable cost savings and flexibility for the Microsoft Information Technology (Microsoft IT) group, which is responsible for designing and implementing Exchange Server 2007 UM servers at Microsoft. With Exchange Server 2007 and VoIP technology, Microsoft IT eliminated separate physical telephony links between PBX switches and enterprise devices such as UM servers. Instead, VoIP gateways enable Microsoft IT to integrate traditional PBX switches into the unified IP-based communications infrastructure.