2. Jamie Stark Senior Product Manager Microsoft UNC305

3. Agenda Before your deployment Enterprise Voice Elements Deployment Scenarios Recommendations & Next steps

4. Customer's OCS Voice state No voice with Office Communications Server How do I get started with a pilot? Validate the technology & business case Pilot completed and successful How do I move the pilot to production? Breadth - more & different users & cases Initial deployment completed and successful How do I grow production to scale? Business critical, multi-site communications

5. Prerequisites to deployment Windows Server 2003 Domain level and higher AD used to store global settings & groups Single-forest & multiple-forest environments Exchange Server 2010 or Exchange 2007 SP1 Unified Messaging, Missed Call Notification, Auto Attendant, Outlook Voice Access For OCS: Windows Server x64 only Windows Server 2003 x64 SP2 Windows Server 2008 x64 (RTM and SP2) SQL Server 2008 SP1 and SQL 2005 SP2 (SP3)

6. Choosing 2007 R2 Topology

7. Recommended 2007 R2 Topology Enterprise Consolidated topology Primary supported topology Consolidated Edge Server Monitoring Server (collocating CDR and QoE) Dedicated Archiving Server Motivation for Consolidated topology Simplify Office Communications Server deployments Fewer, more powerful systems (64 bit) Collocate server roles Requirements for CDR, Archiving, and QoE Maintain flexibility

9. Hardware Recommendations For Enterprise Edition Front-end server x64 Dual Quad-Core CPU, or 4 way Dual-Core CPU 8 GB Memory 10K rpm disk drives Back-end SQL server x64 Dual Quad-Core CPU, or 4 way Dual-Core CPU 16 GB Memory 10K or 15K rpm disk drives (multiple spindles) Other servers Use Front-end or Back-end spec as appropriate

10. Planning Tool

11. Enterprise Voice Elements Mediation Server: Intermediate signaling & call flow Manage innovative elements of the SIP transaction: Inside, TLS/SRTP – Outside, TCP/RTP Transcode media flows from G.711 to RTAudio and SIREN Act as an ICE Client for PSTN-originated calls Provide quality metrics back to monitoring server Upstream telephony elements SIP/PSTN Gateway IP-PBX SIP Trunking Service

12. UC Open Interoperability Program (UCOIP) Qualification program for telephony infrastructure – SIP/PSTN Gateways, IP-PBXs & SIP Trunking Service Providers Goal for seamless interoperability with Office Communications Server and Exchange Server Ensure Customers have positive experiences with Setup, Support, and Use of qualified devices Allows for scalable qualification of vendors SIP/PSTN GatewaysIP-PBXsSIP Trunking Service Aculab, Audiocodes, Cisco, Dialogic, Ferrari, NEC, NET, Nortel, Nuera, Quintum, Tango Networks, Vegastream Altigen Huawei Innovaphone Mitel Nortel Seltatel Interoute Jajah Global Crossing Sprint ThinkTel http://technet.microsoft.com/UCOIP

13. Tested IP-PBXs PBX vendors qualify their latest versions Customers want support for existing versions Where possible, Microsoft may test IP-PBXs To date: Cisco Unified Communications Manager Listed with qualified infrastructure on UCOIP OCS 2007OCS 2007 R2 CUCM 4.X4.2(3)_SR3a 4.2(3)_SR4b CUCM 5.X5.1(1b) 5.1(3e) CUCM 6.x6.1(1b) 6.1(3a)

14. Call Routing & Handling Location Profiles & Normalization Rules Phone Usages Voice Policies Outbound call routes Response Groups

15. Outbound UC Call – SIP URI Outbound Routing UC endpoint UC endpoint/PSTN SIP INVITE Mediation Server Gateway Called Party Number Translations Application bob@contoso.com sip:bob@contoso.com SIP URI

16. Outbound UC Call – E.164 number Outbound Routing UC endpoint UC endpoint/PSTN SIP INVITE Mediation Server Gateway Routing Fail Mediation Server GW US PSTN sip:+12065551111@contoso.com sip:+12065551111@ms1.contoso.com 555-1111 Reverse Number Lookup Success sip:bob@contoso.com Called Party Number RNL maps E.164 number to SIP URI Converted to Converted to local format MS selected Translations Application +12065551111 E.164 number sip:+12065551111@contoso.com

17. Outbound UC Call – Non E.164 Outbound Routing UC endpoint UC endpoint/PSTN SIP INVITE Mediation Server Gateway Routing Fail Mediation Server GW US PSTN sip:+12065551111@contoso.com sip:+12065551111@ms1.contoso.com 555-1111 Reverse Number Lookup Success sip:bob@contoso.com Called Party Number RNL maps E.164 number to SIP URI Converted to Converted to local format MS selected 51111 Number Normalization sip:+12065551111@contoso.com Converted to E.164 Non-E.164 number sip:51111@contoso.com; Phone-context=Redmond sip:51111@contoso.com; Phone-context=Redmond LocationProfileLocationProfile Translations Application

18. Outbound UC Call – Summary Outbound Routing UC endpoint UC endpoint/PSTN SIP INVITE Mediation Server Gateway Routing Fail Mediation Server GW US PSTN sip:+12065551111@contoso.com sip:+12065551111@ms1.contoso.com 555-1111 Reverse Number Lookup Success sip:bob@contoso.com Called Party Number RNL maps E.164 number to SIP URI Converted to Converted to local format MS selected 51111 Number Normalization sip:+12065551111@contoso.com Converted to E.164 Non-E.164 number sip:51111@contoso.com; Phone-context=Redmond sip:51111@contoso.com; Phone-context=Redmond LocationProfileLocationProfile Translations Application +12065551111 E.164 number sip:+12065551111@contoso.com bob@contoso.com sip:bob@contoso.com SIP URI

19. Inbound PSTN Call – E.164 number UC endpoint Mediation Server Gateway Reverse Number Lookup sip:bob@contoso.com RNL maps E.164 number to SIP URI Called Party Number US PSTN +142555511111 sip:+142555511111@contoso.com E.164 number Fail Success Outbound Routing SIP INVITE Translations Application

20. Inbound PSTN Call – non E.164 UC endpoint 11111 Number Normalization sip:11111@contoso.com; Phone-context=Redmond sip:11111@contoso.com; Phone-context=Redmond LocationProfileLocationProfile sip:+142555511111@contoso.com Converted to E.164 Mediation Server Gateway Reverse Number Lookup sip:bob@contoso.com RNL maps E.164 number to SIP URI Non-E.164 number Called Party Number US PSTN Fail Success Outbound Routing SIP INVITE Translations Application

21. Inbound PSTN Call - Summary UC endpoint 11111 Number Normalization sip:11111@contoso.com; Phone-context=Redmond sip:11111@contoso.com; Phone-context=Redmond LocationProfileLocationProfile sip:+142555511111@contoso.com Converted to E.164 Mediation Server Gateway Reverse Number Lookup sip:bob@contoso.com RNL maps E.164 number to SIP URI Non-E.164 number Called Party Number US PSTN +142555511111 sip:+142555511111@contoso.com E.164 number Fail Success Outbound Routing SIP INVITE Translations Application

22. Call Routing UI

23. Voice Deployment Goals Mixed environment with PBX Some users will be on the PBX, others will move Mix expected to change over time Office Communications Server for Voice Enable a temporary transition state Prepare for your PBX-less future

24. Voice Deployment Scenarios Networked PBX: Split dial plan Mediation Server located behind the PBX Connect using SIP/PSTN Gateway or Direct SIP Direct to PSTN: Owned dial plan Calls are sent/received directly with PSTN SIP Trunking from carrier or circuits to Gateway

25. Voice Deployment Scenarios

26. Networked PBX Using a SIP/PSTN Gateway Users are moved off the PBX Calls delivered from PSTN to PBX and routed to SIP/PSTN Gateway Wide availability of Gateways for geography & circuit configurations Dialing behavior preserved for calls between all users Fast & inexpensive to deploy for pilot & smaller production Double-trunking through the PBX increases cost with scale

27. Networked PBX Direct SIP Users are moved off the PBX Calls delivered from PSTN to IP-PBX Mediation Server connects directly to SIP interface on supported IP-PBX But still a server to server trunk – not client to client due to lack of ICE negotiation, security, etc. May require additional software, licenses or upgrades to the IP-PBX As production deployments grow, Direct SIP has OA&M advantages

28. Voice Deployment Scenarios

29. Direct to PSTN IP-IP Gateways Mediation Server sits behind same SIP/PSTN Gateway used by IP-PBX Supported configuration as long as the Gateway is qualified with OCS Gateway routes based on DID or trunk group, may require configuration on the carrier Some Gateways support doing an AD Query for routing determination Increased flexibility and negligible impact to trunking costs when moving users from PBX

30. Direct to PSTN Using a SIP/PSTN Gateway Separate PSTN interconnect infrastructure from PBX Number routing change or new numbers provisioned by Carrier Requires zero PBX changes, eventually move trunks from PBX to SIP/PSTN Gateway Internal calls between user groups routed through PSTN

31. Direct to PSTN SIP Trunking Connecting Mediation Server to SIP Trunking Service No on-premise third party products (SBCs, etc.) required Uses nailed up VPN to Service Provider for security Brings telephony trunking into datacenter consolidation strategy Still early days… not all carriers signed on to support modern (SIP Connect 1.1) standards

32. More Options All of these can be deployed in a mixed fashion Scenarios can change as deployment matures Trunking both to IP-PBX and PSTN clouds For Example: use Gateways for Pilot, Direct SIP to HQ IP-PBX, keep some users on PBX but move others PilotPilot DeployDeploy ScaleScale

33. Considering User Population Mobile & Remote Great pilot users to validate capability Discontinuous number range Headquarters / Single Site Expect a mix of Communicator & PBX for coverage of all enterprise telephony features Most IW users can use Enterprise Voice exclusively Branch Office Gateways for Least Cost Routing & Local number termination WAN Survivability via Cell Phone & Internet

34. Deployment factors Deployment Goal With Existing IP-PBX Mixed environment OCS for Voice Company Size 250 1000 5000 10,000 50,000 Current Stage No Voice Deployed Pilot Successful Initial Deployment Successful User Population Mobile & Remote Employee HQ / Single Site Branch Office Deployment Scenario Networked PBX Direct to PSTN Interop SIP/PSTN Gateway IP-PBX SIP Trunking Service

35. Recommendations No OCS Voice yet – heading to pilot Start thinking about scale Architecture: HA, DR, Security, Management Validation & Testing of headsets, devices, etc. Build a solid infrastructure foundation Address any outstanding issues with these elements Anything with AD, DNS or Certificates will surface Telephony integration for rapid success Gateways maximize flexibility SIP Trunking maximizes environmental simplicity

36. Recommendations Successful Pilot - heading to production Scale thinking pays off – now take the next step Look at traffic flows on LAN/WAN Managing usage as appropriate Costs of Least Cost Routing vs. PSTN / Carrier Respect the Users Deploy Monitoring End-user training resources Telephony integration for scale IP-PBXs: Direct SIP behind or alongside TDM PBXs: Direct to carrier

37. Recommendations Moving to OCS Voice Deploy SIP Trunking or Gateway to PSTN Roll out OCS Voice to everyone in the company For end-users who don’t need a PBX phone Remove it Port the number if possible or acquire new DIDs For those with unmet requirements Keep the PBX phone – migrate them as features become available. Personal call forwarding to OC to get the experience Give everyone else the choice with an opt-in approach Look at carrier process for new DIDs vs. moving numbers Slowly phase out the IP-PBX

38. What's next? Move your pilot forward to production Know that upgrading your IP-PBX is not the first step on the road to Unified Communications Experience the end-user capability anywhere! FREE Hosted Trial at https://r2.uctrial.comhttps://r2.uctrial.com Check out the administration experience! FREE OCS VMs at http://microsoft.com/VHDhttp://microsoft.com/VHD

39. Related Content at Teched UNC04-IS - Microsoft Office Communications Server Video Strategy 11/10/200913:30 - 14:45Interactive Theatre 5 - Yellow UNC204 - Ten Ways to Become a Hero with Microsoft Office Communications Server 11/11/200909:00 - 10:15Berlin 2 - Hall 7-3a UNC305 - Voice Architecture and Planning 11/11/200910:45 - 12:00Berlin 2 - Hall 7-3a UNC303 - Voice Administration and Monitoring 11/10/200915:15 - 16:30Berlin 2 - Hall 7-3a UNC313 - Audio Conferencing Deep Dive 11/12/200909:00 - 10:15Berlin 2 - Hall 7-3a UNC07-IS - Troubleshooting Microsoft Office Communications Server 2007 R2 11/12/200917:00 - 18:15

40. Voice Resources Programs & Standards Unified Communications Open Interoperability Program Microsoft Office Protocol Documentation White Papers Integrating Telephony with Office Communications Server 2007 and 2007 R2 A Practical Approach to Deploying Real-time Communications Microsoft Quality of Experience Documentation VoIP Architecture Configuring Voice Quality of Service

42. UNC Track Call to Action! Learn More! Related Content at TechEd on “Related Content” Slide Attend in-person or consume post-event at TechEd OnlineTechEd Online Check out learning/training resources at Microsoft TechNet Exchange ServerExchange Server and Office Communications ServerOffice Communications Server Check out Exchange Server 2010 at Virtual Launch Experience (VLE) at the new efficiency.comthe new efficiency.com Try It Out! Download the Exchange Server 2010 TrialExchange Server 2010 Trial Take a simple Web-based test drive of UC solutions through the 60-Day Virtual Experience60-Day Virtual Experience

43. www.microsoft.com/teched Sessions On-Demand & Community http://microsoft.com/technet Resources for IT Professionals http://microsoft.com/msdn Resources for Developers www.microsoft.com/learning Microsoft Certification & Training Resources Resources Required Slide Speakers, TechEd 2009 is not producing a DVD. Please announce that attendees can access session recordings at TechEd Online. Required Slide Speakers, TechEd 2009 is not producing a DVD. Please announce that attendees can access session recordings at TechEd Online.

44. Complete an evaluation on CommNet and enter to win an Xbox 360 Elite!

45. © 2009 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. Required Slide