Unified. Simplified. Unified Communications Launch 2007

Unified. Simplified. VoIP Topologies and Interoperability Unified Communications Microsoft Corporation

Unified. Simplified. Workbook and Lessons Voice Deployment Topologies A: Direct PSTN connection B: Tie-line off existing TDM PBX C: PRI off existing IP/PSTN gateway D: Greenfield

Unified. Simplified. Direct PSTN Connection Around 1/5 of early adopter customers Great for quick lab/pilot setup – no PBX interop! Good match for Centrex and PBX if you can swing existing numbers over to new PRI, otherwise typically need new numbers OCS PSTN phone PSTN 21%21%

Unified. Simplified. Tie-line off existing TDM PBX Most Common – nearly 2/3 of early adopter customers Requires integration w/ existing telephony infrastructure for call routing and PRI port Gateway number manipulation typically needed OCS 2007 PSTN phone SIP/PSTN Gateway PSTN PBX Phone PRI(s) 57%57%

Unified. Simplified. PRI off existing SIP/PSTN Gateway Around 1/5 of early adopter Customers Some pushback on B2B gateways Vendors able to certify IP PBX for Direct SIP connectivity; none available yet Call Manager does not require Cisco gateway, but several are certified OCS 2007 PSTN phone SIP/PSTN Gateway PSTN IP PBX Phone PRI(s) Existing SIP/PSTN Gateway Existing IP PBX 21 %

Unified. Simplified. Greenfield A couple of early adopter deployments Typically requires purchase/config of small PBX Possibly better match for small customers with minimal telephony requirements OCS 2007 SIP/PSTN Gateway Small PBX PSTN phone PSTN Fax, Analog/ ISDN Devices PRI(s) 1%1%

Unified. Simplified. Voice – lessons learned General AD/Contacts should be RFC3966. ABS can normalize for galContacts.db and keyed numbers msRTCSIP-line attribute for RNL Quality of headset / device prominent factor OCS approved: us/bb aspxhttp://technet.microsoft.com/en- us/bb aspx RCC with OC 2007 does not include CSTA conferencing – may impact legacy LCS customer WMI needed to modify some config items QoS vs QoE QoE Monitoring Server – key for troubleshooting voice Microsoft UC Quality of Experience Whitepaper

Unified. Simplified. “The ripe taste of cheese improves with age. Act on these orders with great speed. “ CodecPerfect NetworkWith Network Loss G.711 G.729 RT Audio Narrowband

Unified. Simplified. Per User Calculation Type of usage is important when planning Media Stack adjusts to available bandwidth every 5 seconds Consider the whole path end-to-end Media TypeBandwidth Needed Audio45 Kbps Video250 Kbps Data~45 Kbps Signaling10 Kbps Total350 Kbps per direction

Unified. Simplified. QoS Support OCS 2007 does not require DiffServ, RSVP or CAC We do work within a DiffServ environment DSCP marking by the end-points By default, end-points mark all media Audio: Expedited Forwarding Video: Class 3 of Assured Forwarding DSCP marking can also be tuned through policy Windows Vista has centralized policy enforcement

Unified. Simplified. Scaled Edge Topologies Lessons Learned 3 flavors: Single Site, Scaled Single Site, Multiple Site Most common: scaled single site provides local HA and scale. Co-home AE and Web Edge Requires hardware load balancers Disable IPSec across A/V port range Talking to the firewall/DMZ teams OCS 2007 Security Guide Limited to one geographic instance of AE

Unified. Simplified. Having the Edge Conversation 1. Meet with various security/DMZ/Firewall teams 2. Explain Protocols, ports, roles, security 3. Repeat 1&2 … Translate diagram at left into firewall rules include ports, direction, etc…

Unified. Simplified. ScenarioWhen to DeployInfrastructure Required OCS Co-existence All the features of the existing PBX, plus all features of OC and OCS Modern PBX that can natively interoperate with OCS OCS Standalone Pilot the future with specific groups: Highly collaborative employees Mobile employees PSTN Gateway or existing TDM or Hybrid-IP PBX. Software-Powered VoIP Architecture Deployment scenarios for today

Unified. Simplified. Simultaneous ringing Interoperability with PBX systems Users have both OC and legacy phone Utilize existing PBX capabilities Receptionist and boss-admin needs Emergency call requirements Analog lines (e.g., fax machines) Voic Software-Powered VoIP Architecture Deployment scenario: OCS 2007 Co-existence OCS 2007 Co-existence Mediation Server Mediation Server SIP Existing PBX Existing PBX OCS 2007 IM, Presence, Audio, Video, Conferencing, IVR Inbound Routing Outbound Routing Voic Routing SIP/PSTN Gateway

Unified. Simplified. Migrate groups to Software-powered VoIP Typically information or mobile workers All users have IM and presence Standard PBX migration procedures Common PBX network interfaces PBX numbering plans No PBX upgrade required OCS 2007 Stand-Alone Existing PBX Existing PBX Mediation Server Mediation Server SIP OCS 2007 IM, Presence, Audio, Video, Conferencing, IVR Inbound Routing Outbound Routing Voice Mail Routing SIP/PSTN Gateway Software-Powered VoIP Architecture Deployment scenario: OCS 2007 Standalone

Unified. Simplified. Mediation Server Connects OCS and SIP/PSTN Gateway or IP-PBX Front-end of the Microsoft OCS voice world Intermediate signaling and call flow Manage innovative elements of the SIP transaction Transcode RTP flows from G.711 to RTAudio and SIREN Act as an ICE Client for PSTN-originated calls Enables OCS to… Provide IP telephony Interconnect with the legacy PSTN

Unified. Simplified. QOE Monitoring Archiving CDR OCS 2007 Voice Components Public IM Clouds MSN AOL Yahoo Remote Users Remote Users DMZ Federated Businesses Front-End Server(s) (IM, Presence) Front-End Server(s) (IM, Presence) Inbound Routing Inbound Routing Outbound Routing Outbound Routing PSTN Backend SQL server Backend SQL server Exchange 2007 Server UM Voic UC endpoints Active Directory Voice Mail Routing Voice Mail Routing Conferencing Server(s) Conferencing Server(s) PBX (SIP-PSTN GW) Access Server Data Audio/ Video SIP Mediation Server PRI

Unified. Simplified. SIP/PSTN Gateways Basic Media Gateway Standalone appliance Supports TDM features SIP over TCP RFC 3261 compliant SIP G.711 Works with Mediation Server Hybrid Media Gateway Media Gateway appliance Collocated with Mediation Server VendorModelTypeAvailability AculabHybrid for OCSHybridFall 2007 AudiocodesMediant 2000BasicToday AudiocodesHybrid Winter 2007 Dialogic1000BasicOct 16 th Dialogic2000BasicOct 16 th Dialogic4000HybridOct 16 th QuintumTenor DXBasicOct 16 th QuintumHybrid Winter 2007

Unified. Simplified. PBX VendorAvailability Alcatel-LucentTBD AvayaTBD CiscoTBD EricssonTBD MitelTBD NECTBD NortelDecember 2007 SiemensTBD PBXs: Current Partners and Categories Many vendors committed to working natively with OCS TDM-based PBXs No UC interoperability Use SIP gateway

Unified. Simplified. Gateway-Only Configuration Steps Define location profile for lab environment Configure Media gateway Mediation server Define Phone usages Voice policies Outbound call routes Call restrictions: Blocking numbers Use Communicator to dial a PSTN number

Unified. Simplified. Gateway-Only Configuration

PBX Interoperability (TDM or IP)

Unified. Simplified. PBX Interoperability (TDM or IP) Define location profile for additional sites (examples for London and Hong Kong) Configuring four-digit dialing across all PBXs Expand call routes PSTN toll bypass

PBX Interoperability (TDM or IP)

Native IP-PBX Interoperability

Unified. Simplified. Implementing PBX Integration StandaloneCo-Existence GatewayDirect SIPDual ForkingDual Forking with RCC

Unified. Simplified.

Resources Integrating Telephony with OCS Integrating Telephony with OCS Visit the OCS 2007 Tech Center Visit the OCS 2007 Tech Center Gateways qualified with Office Communications Server Gateways qualified with Office Communications Server

Unified. Simplified.

© 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. This document may contain information related to pre-release software, which may be substantially modified before its first commercial release. Accordingly, the information may not accurately describe or reflect the software product when first commercially released MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.