UNC304 Lync Server 2010 Voice Deployment

2. Required Slide UNC304LyncServer 2010 Voice Deployment Jamie Stark Senior Technical Product Manager Microsoft Corporation

3. Session Objectives • Architectural components • Deployment Topologies • Signaling & media capabilities • New server-side voice features • Core call routing An overview of Lync Server 2010 investments to inform your enterprise voice deployment

4. Topics • Topology changes • Media bypass • Call Admission Control • Location & E911 • Private line • Malicious Call Trace • Analog devices • Caller ID Presentation • Voice Routing & Policy Enhancements

5. Voice Topology: Lync 2010 Archiving Monitoring DMZ PICXMPP MSN UC Endpoints AOL Yahoo Remote Users UC Pool AD DNS AV Conf. Front End (incl. Mediation) Back End Federated Businesses Edge Services Analog Devices Direct SIP SIP Trunking ExUM Mediation Server PSTN IP-PBX Media GW / SBA On-premise or online Circuit Packet

6. Mediation Service ColocationLower TCO and better quality with two enhancements • Multiple Gateways per Mediation Service • Lync allows for Gateways to be connected to the same Mediation Svc • Routes point to a Gateway • Topology document used to find anappropriate Mediation Service, inserted into the routing path • Mediation Service uses the GW-FQDN in the Request-URI to route to appropriate Gateway OCS 2007 R2 Lync Server 2010

7. Mediation Service ColocationLower TCO and better quality with two enhancements • Media Bypass of Mediation Server • Whenever possible media for calls egressing to the PSTN will flow directly to upstream device without traversing Mediation Server • Applies where media can stay local to a capable next hop - a network site or branch office • Does not apply where media is not local • Signaling continues to traverse Mediation Server role • Consolidation of most Mediation resources at the Data Center. • Mediation could be on a Front End, in a SBA, or standalone • Low CPU intensity enables running Mediation role on FE & Appliance

8. Media BypassBenefits of direct routing of media • Topology simplification • Together with Survivable Branch Appliances, removes need for standalone Mediation Server in most local sites. • Greatly reduces total number of servers for lower Total Cost of Ownership. • Optimize media flow and Quality of Experience • Eliminate unnecessary hops and potential points of failure. • Save bandwidth across wide-area network (WAN) by not hair-pinning. • Improve voice quality: • Use of codec with optimal theoretical Mean Opinion Score (MOS). • No needless transcoding. • Reduction in latency and probability of network quality issues.

9. Media Bypass Scenarios • Bypass to a media gateway • Gateways qualified for Lync 2010 will be supported for bypass. • G.711 over SRTP direct from Communicator to Gateway. • Bypass to select IP-PBXs (Specific versions TBD) • Keep in-branch media between IP-PBX and Communicator local without deploying Mediation Server on site. • May require Media Termination Point or similar – testing underway. • G.711 direct from OC to Cisco Unified Communications Manager (CUCM) Media Termination Point (MTP) to Cisco IP phone. • SIP Trunking • Support TBD – Carrier SBCs generally don’t accept connections from any client.

10. Audio/Video Bandwidth Controls • End User maximum allowed bandwidth per modality • Applied whether or not bandwidth is available • Configured via in-band provisioning at sign-in • Wide-area network (WAN) link bandwidth policies (aka Call Admission Control (CAC)) • Applied dynamically when session crosses network link with policy set • Limits to maximum allowed level when bandwidth available • Re-routesor fails session when bandwidth not available

11. Call Admission Control • New Policy Server role introduced in Wave 14 to support CAC • Admins configure logical sites based on groupings of subnets • Enforce policies on links between sites • Bandwidth available for audio, video • Maximum bandwidth allowed per session • Rerouting behavior when bandwidth limited exceeded • Seamless support for roaming users Microsoft Communicator “14” on moving between different sites • Allows Internet to be used for overflow of traffic • Avoid PSTN call charges • Support alternate path & failover of video sessions

12. Example Scenario RT Audio WB (no FEC) New York Berlin WAN Link Policy: Audio Session Limit = 60 kbps

13. Example Scenario Berlin RT Audio WB (No FEC) Internet New York WAN Link Policy: Audio Session Limit = 60 kbps

14. Example Scenario Berlin RT Audio NB (+ FEC) Internet New York WAN Link Policy: Audio Session Limit = 60 kbps

15. Enhanced 911Location Infrastructure • Enablement location provides flexible deployment • “Network Sites” – definition of where E911 services are available • Users – E911 enablement available through user policy • Location Information Server (LIS) added to Lync Server web components • Contains records of civic addresses associated with network identifiers • No additional server roles to purchase or manage • Renders locations to UC clients • Locations can be used independent of E911 • Locations can be based on subnet, switch, port, Wi-Fi access point, and are updated on each client registration or network change

16. Network QoS– DiffServ (DSCP) • When Right Provisioning not possible and so Constrained WAN Links (pair with WAN bandwidth Policies) • Audio prioritization already deployed for other Voice over Internet Protocol (VoIP) solution • Example “Fully Managed” Network Deployment

17. Private Line • LyncServer introduces support for private line • Single SIP URI, single Exchange mailbox, single presence source • Receipt of inbound calls on private DID to same SIP URI • Private lines carry many of the same features • Call pickup & park work as expected • Simultaneous ringing & call deflection on primary line carry to private line • Private lines are different: • Available for inbound calls only • Overrides delegation, call forwarding, do-not-disturb and other routing options – private calls are always going to go through • Calls to a private line have a distinctive ring & “toast” pop-up

18. Malicious Call Trace • Lync provides the end-user the capability of tagging theprior call as a malicious call. • Supported in Communicator, Communicator Phone Edition& Attendant Console. • Tagging is reflected in the backend CDR database, enabling the Lync Server administrator to take action on the call.

19. Analog Device Management • Physical connectivity of Analog devices (FXS) provided by GW partners • All routing and policy enforcement for Analog devices centralized in Lync Server – eliminates the need to manage GWs as “mini-PBX” • Lync Server Call Detail Record (CDR) infrastructure used to track usage • Optimized routing allows Fax call routing through CS “14” without terminating Media PSTN Fax Gateway ATA FXS Lync Analog Device FXS

20. Analog Device Management • Physical connectivity of Analog devices (FXS) provided by GW partners • All routing and policy enforcement for Analog devices centralized in Lync Server – eliminates the need to manage GWs as “mini-PBX” • Lync Server Call Detail Record (CDR) infrastructure used to track usage • Optimized routing allows Fax call routing through CS “14” without terminating Media PSTN Fax Gateway ATA CS “14” Signaling Analog Device Media

21. Caller ID Presentation Controls • Admins can natively control what Caller ID is presented to receiving party (PSTN/PBX): • Per user/group controls to suppress/alter calling party number • Granular controls based on caller and destination number: • Alice calls an external PSTN number, caller ID is presented as +1 425 555 0100 • Alice calls an internal PBX number, caller ID is presented as +1 425 555 2302 • Override for “simultaneous ringing”: Bob calls Alice, who has simultaneous ringing configured to her mobile number; Bob’s caller-id is presented • Calling Name Display feature allows display name to ingress/egress • Also Available for OCS 2007 R2 through KB

22. Caller ID Presentation Controls

23. Voice Routing Enhancements • Centrally manage number formatting prior to routing to PBX/PSTN • Alice calls +44221234567; based on route translation pattern, called number formatted to 01144221234567 when using GW in Redmond • Alice calls +44221234567; based on route translation pattern, called number formatted to 0221234567 when using GW in London

24. Voice Routing Enhancements • Centrally manage number formatting prior to routing to PBX/PSTN • Alice calls +44221234567; based on route translation pattern, called number formatted to 01144221234567 when using GW in Redmond • Alice calls +44221234567; based on route translation pattern, called number formatted to 0221234567 when using GW in London

25. Voice Routing Enhancements • Centrally manage number formatting prior to routing to PBX/PSTN • Alice calls +44221234567; based on route translation pattern, called number formatted to 01144221234567 when using GW in Redmond • Alice calls +44221234567; based on route translation pattern, called number formatted to 0221234567 when using GW in London

26. Voice Policy Enhancements • Provide admins flexibility to control user voice entitlements • Call Forwarding • Delegation • Call Transfer • Call Park • Simultaneous Ringing • Team Call • PSTN Rerouting • BW Policy Override • Malicious Call Tracing • Useful to address Common Area Device requirements

27. Session Objectives • Architectural components • Deployment Topologies • Signaling & media capabilities • New server-side voice features • Core call routing An overview of Lync Server 2010 investments to inform your enterprise voice deployment

28. Session Evaluations Tell us what you think, and you could win! All evaluations submitted are automatically entered into a daily prize draw*  Sign-in to the Schedule Builder at http://europe.msteched.com/topic/list/ * Details of prize draw rules can be obtained from the Information Desk.

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