330 likes | 542 Views
Exchange 2007 Unified Messaging. Colin Lee Technology Specialist - Unified Communications Microsoft Corporation. Session Objectives. After this session, you will…. Understand the value of Exchange Server 2007 Unified Messaging. Learn about new features in Service Pack 1.
E N D
Exchange 2007 Unified Messaging Colin LeeTechnology Specialist - Unified CommunicationsMicrosoft Corporation
Session Objectives After this session, you will… Understand the value of Exchange Server 2007 Unified Messaging Learn about new features in Service Pack 1 Understand the Microsoft Exchange Server UM Architecture Understand the setup and basic administration process
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 messages • Stand-alone fax machines • Users and administrators must manage their messages from multiple locationswith 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 MessagingDelivering on a clear and simple vision • Convenient, integrated access to your vital business communications • Reducing costs, increasing operational efficiency by consolidating infrastructure, training • Unified store, transport, directory • Increasing client reach to the telephone • “Anywhere access” to your messages, calendar, contacts “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
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 Exchange Server UM Architecture
Setup and Basic Administration • Preparation • Install Exchange Server 2007 • Mailbox • Hub Transport • Client Access • Unified Messaging • Create mailboxes • Set up IP gateway • Demo • Configure UM • Create UM Dial Plan • Create UM IP Gateway • Join UM Server to Dial Plan • Call UM • “Welcome. You are connected to Microsoft Exchange…”
demo UM Setup and Basic Administration
Preparing the System for Callers • Enable Users for UM • Exchange Management Console • Exchange Management Shell • Dial Plan • Log in to Outlook Voice Access • New User Dialog (Record Name, Greeting) • Call UM-enabled user • Hear greeting • Record voice message • Receive fax message • Special storage quota
demo Preparing Exchange UM for Callers
UM Automated Attendants • Call Answering is great, but: • What if caller doesn’t know the user’s phone number? • What if the user doesn’t have a direct-dial number? • Automated Attendant • Create New Auto Attendant (Speech Enabled) • Customise Welcome Greeting • Configure Business Hours, Time Zone • Create Menu, Add Menu Options • Use menu option • Telephone keypad • Speak the option name • Transfer to user by speaking their name
demo UM Automated Attendants
UM in Outlook 2007 and OWA • Custom Rendering • Voice messages • Play (multimedia) • Play on phone • Fax messages • Voice mail options • Reset PIN • E-mail folder • Missed call notifications
demo UM in Outlook Web Access 2007
Outlook Voice Access • Phone interface to Exchange Server 2007 • Speech enabled (English) or Touch Tone • Voice • Play, forward, delete, call sender, etc. • E-mail messages • Language detection, play, forward, delete, find, hide etc. • Calendar • Accept invitation, play details, clear, etc. • Personal contacts, directory • Call (office/cell/home), send a message
demo Outlook Voice Access
UM Configuration and Site Topology • UM Servers can handle calls for multiple UM Dial Plans • UM Server • UM Dial Plan • UM Auto Attendant • UM Mailbox Policy • UM IP Gateway • UM Hunt Group • UM Mailbox • = UM-Enabled User
UM Mailbox Policy • Configure properties for many UM-enabled users through a single object
UM Dialing Rules • Dial Plan defines groups of number patterns, and which of them may be dialed • Mailbox Policy references allowed group(s) and determines who may dial them • Auto Attendants may also reference allowed groups
demo UM Mailbox Policy and Dialing Rules
Monitoring • Based on the Test-UMConnectivitycmdlet • Local (on UM Server) • Test-UMConnectivity • Remote (via gateway/PBX or IP-PBX) • Test-UMConnectivity –Phone 50000 –UMIPGatewayMyGW • End to end (accesses mailbox) • Test-UMConnectivity –TUILogon $true –Phone 56789 −PIN 672316 –UMDialPlanMyDP • UM rules in MOM Pack can build reports
Availability through Redundancy • PBX routes calls to available VoIP gateways • VoIP gateways route calls to available UM servers • UM service redirects calls to worker process • UM accommodates outage in mailbox, transport, DC • Maintains service if possible Service Worker process
Scalability • Provide capacity for concurrent calls • PBX • Provision circuit switched channels • Organise into hunt groups for IP gateways • IP Gateways • Add for capacity, redundancy • UM Servers • Add for capacity, redundancy • ~10,000 UM enabled users each • May be less if access is heavy Capacity required to fix probability (1%, 5%) of caller not being connected to UM in busiest hour (14% calls) of day for different patterns of UM usage
Why UM Scales Better than VM • Typical MORG/LORG voice mail systems have 16 ports (or fewer) • Covers up to ~1000 voice mailboxes • Approx. 10× systems (160 ports) for 10K ORG • UM can cover 10K users with ~80 ports • Voice messages in Outlook (no call required) • Consolidation of spare capacity • 2 UM servers can replace 16 VM servers • (1 + 1) configuration for redundancy • Operating costs greatly reduced
UM Changes in E2K7 SP1 • Support for Office Communicator 2007 and Office Communications Server 2007 • Support for Windows Server 2008 • Fax tone detection by UM Server • Support for SRTP • Support for quality of service for VoIP • Performance Improvements
Fax Tone Detection by UM Server • In E2K7 RTM, UM relied on IP gateway • GW detects fax tone • GW notifies UM server (RFC2833/CNG) • UM Server renegotiates media as fax (T.38) • Did not work with IP PBXs (Cisco, Avaya…) • In SP1, UM can detect fax tone itself • OFF by default • Must configure on each UM Server • EnableInbandFaxDetection (globcfg.xml)
Support for Secure RTP (SRTP) • RTM: UM signaling could be secured • DialPlan.VoIPSecurity = None (TCP, RTP) • DialPlan.VoIPSecurity = SIPSecured (MTLS, RTP) • SP1: signaling and media can be secured • DialPlan.VoIPSecurity = Secured (MTLS, SRTP)
Quality of Service (QoS) • Mark (VoIP) audio for expedited routing • RTC media “under” UM will support QoS • Differentiated Services Code Point (DSCP) • Codepoint for UM audio packets • Default 101000 (0x40); Group Policy control • Requires Windows QoS Packet Scheduler • In Windows Server 2008 • Manual install for W2K3
UM Performance Improvements • Number of concurrent calls is the metric • Depends on codec used to record messages • 2 × 2-core 4 GHz Xeon proc, 4 GB RAM • Tested with Windows Server 2003 and 2008 • G.711 wire codec, TCP, RTP • G.723.1, TLS, SRTP give similar figures
Compliance, Discoverability • Some confusion/concern about voice mail retention • Legal opinion (Covington & Burling LLP) • http://www.microsoft.com/exchange/evaluation/unifiedmessaging/dataretentionwp.mspx • “…no aspect of Exchange alters, by increasing or decreasing, the record retention obligations of … organisations [using it] in the U.S. or E.U.” • Exchange can help the customer • Many features to implement compliance policy • Easier to locate and sort voice mail, if needed
© 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.