Rajeev KrishnanSenior ConsultantMicrosoft Corporation

Scope

Voice with Office Communications Server

Enterprise Voice PlanningDeployment Scenarios

Sizing and Topology considerations

Call Routing and Management

Interoperability with existing telephony infrastructure

Out of Scope

Integrations that don’t involve Voice

Client-based plug-insPBX-based controls hosted inside Communicator

Features, Experience, Capability vary widely

Remote Call ControlOffice Communicator controls a PBX station set

Consider a third party Gateway instead of an upgrade: Corebridge, Genesys, Estos

Agenda

Prerequisites

Enterprise Voice Elements

Deployment Scenarios

Recommendations & Next steps

Your current state?

No voice with Office Communications Server…yetHow do I get started with a pilot?

Validate the technology & business case

Pilot completed and successfulHow do I move the pilot to production?

Breadth - more & different users & cases

Initial deployment completed and successfulHow do I grow production to scale?

Business critical, multi-site communications

Prerequisites to deployment

Windows Server 2003 Domain functional levelAD used to store global settings & groups

Single-forest & multiple-forest environments

Exchange Server 2007 with Service Pack 1Unified Messaging, Missed Call Notification, Auto Attendant, Outlook Voice Access

Assess your IP Network for real-time trafficBandwidth

Latency & other network affects

Your IP Network

BandwidthProvision for streams of 45Kbps audio, 300Kbps video

Modeling calling patterns: Intra/inter-office, external

Other network affectsReduce delay: < 150ms E2E delay considered excellent (G.114)

Some jitter (< 30ms) & loss (< 10%) can be handled

Prioritizing Media with DiffServAudio: Expedited Forwarding; Video: Assured Forwarding

Centralized policy enforcement for Vista PCs

Controlling UsageManage the size of conferences, allowed media

Set port range for media, per session BW limits, video quality

Telecom Regulations

TRAIRegulations prohibit direct interconnect of telephony network with IP

Government now allows use of single IP-PBX that can be logically partitioned

TRAI has recommended additional relaxations of these regulations

Your (future) Voice Network

Enterprise Voice Elements

Mediation Server: Intermediate signaling and 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 elementsSIP/PSTN Gateway

IP-PBX

SIP Trunking Service

UC Open Interoperability Program (UCOIP)

Qualification program for telephony infrastructure –SIP/PSTN Gateways, IP-PBXs & SIP Trunking ServiceGoal for seamless interoperability with Office Communications Server and Exchange ServerEnsure Customers have positive experiences withSetup, Support, and Use of qualified devicesAllows for scalable qualification of vendors

http://technet.microsoft.com/UCOIP

SIP/PSTN Gateways IP-PBXs SIP Trunking Service

Aculab, Audiocodes, Cisco, Dialogic, Ferrari, NEC, NET, Nortel, Nuera, Quintum, Tango Networks, Vegastream

InnovaphoneMitelNortelSeltatel

InterouteGlobal CrossingSprint

Tested IP-PBXs

PBX vendors qualify their latest versions

Customers want support for existing versions

Where possible, Microsoft may test IP-PBXsTo date: Cisco Unified Communications Manager

Listed with qualified infrastructure on UCOIP

OCS 2007 OCS 2007 R2

CUCM 4.X 4.2(3)_SR3a 4.2(3)_SR3a4.2(3)_SR4b

CUCM 5.X 5.1(1b) 5.1(1b)5.1(3e)

CUCM 6.x 6.1(1b) 6.1(1b)6.1(3a)

Voice deployment continuum

Voice Capabilities with an existing IP-PBXLong-term interoperability for all end-users

Combined experience of Communicator & PBX Phone

Mixed environment with PBXSome users will be on the PBX, others will move

Mix expected to change over time

Office Communications Server for VoiceEnable a temporary transition state

Prepare for your PBX-less future

Deployment Scenarios

Overlay PBX: Shared Dial PlanDual Forking: PBX rings to phone & Communicator

Multiple Dial Plans: multiple numbers per user

Networked PBX: Split dial planMediation Server located behind the PBX

Connect using SIP/PSTN Gateway or Direct SIP

Direct to PSTN: Owned dial planCalls are sent/received directly with PSTN

SIP Trunking from carrier or circuits to Gateway

Deployment Scenarios

Overlay PBX Dual Forking

Calls from PSTN & PBX phones are forked by IP-PBX to Office Communications Server

Any calls made by Office Communicator are also forked to IP-PBX

Provides a blended, single number experience for end-users

Each infrastructure elementimplements equivalent dial plan

PBX upgrade required for Direct SIP plus Dual Forking qualification

Overlay PBXMultiple Dial plans

Each user has two numbers – one for Office Communicator & one for PBX

No forking. Users configure personal call forwarding between systems

Configure with SIP/PSTN Gateway or Direct SIP to IP-PBX

If using Gateway, trunk expense rises as size of deployment grows

Fundamentally a transition over time, assume PBX phone goes away

Deployment Scenarios

Networked PBXUsing a SIP/PSTN Gateway

Users are moved off the PBX

Calls delivered from PSTN to PBXand 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 forpilot & smaller production

Double-trunking through the PBX increases cost with scale

Networked PBXDirect 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

Deployment Scenarios

Direct to PSTNIP-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

Direct to PSTNUsing 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

Direct to PSTNSIP 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

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

Use Gateways for Pilot, Direct SIP to HQ IP-PBX, keep some users on PBX but move others

Pilot Deploy Scale

User populations to consider

Mobile & RemoteGreat pilot users to validate capability

Discontinuous number range

Headquarters / Single SiteExpect a mix of Communicator & PBX for coverage of all enterprise telephony features

Most IW users can use Enterprise Voice exclusively

Branch OfficeGateways for Least Cost Routing & Local number termination

WAN Survivability via Cell Phone & Internet

Deployment factors to consider

Deployment Goal

With Existing IP-PBX

Mixedenvironment

OCS for Voice

Company Size

250

1000

5000

10,000

50,000

Current Stage

No VoiceDeployed

Pilot Successful

Initial Deployment Successful

User Population

Mobile & Remote

Employee

HeadquartersSingle Site

Branch Office

Deployment Scenario

Overlay PBX

Networked PBX

Direct to PSTN

Interop

SIP/PSTN Gateway

IP-PBX

SIP TrunkingService

RecommendationsNo OCS Voice yet – heading to pilot

Start thinking about scaleArchitecture: HA, DR, Security, Management

Validation & Testing of headsets, devices, etc.

Build a solid infrastructure foundationAddress any outstanding issues with these elements

Anything with AD, DNS or Certificates will surface

Telephony integration for rapid successGateways maximize flexibility

SIP Trunking maximizes environmental simplicity

Recommendations Successful Pilot , heading to production

Scale thinking pays off – now take the next stepLook at traffic flows on LAN/WAN

Managing usage as appropriate

Costs of Least Cost Routing vs. PSTN / Carrier

Respect the UsersDeploy Monitoring

End-user training resources

Telephony integration for scaleIP-PBXs: Direct SIP behind or alongside

TDM PBXs: Direct to carrier

Moving to OCS Voice"I'm done with my PBX!"

Deploy a gateway to the PSTN or SIP Trunking

Give everyone OCS Voice

Remove desk phones for those who don't need them - give others the choice

Users on PBX can do personal call forwarding from Desk phone to OCS phone

Turn off the PBX

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

Check out the administration experience!FREE OCS VMs at http://microsoft.com/VHD

Voice Resources

Programs & StandardsUnified Communications Open Interoperability Program

Microsoft Office Protocol Documentation

White PapersIntegrating Telephony with Office Communications Server 2007 and 2007 R2

Microsoft Quality of Experience

DocumentationVoIP Architecture

Configuring Voice Quality of Service

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/learningMicrosoft Certification and Training Resources

www.microsoft.com/learning

Microsoft Certification & Training Resources

Resources

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