Lync Server 2013 in Office 365 Hybrid Architecture Sandi Jordan, Microsoft
Agenda Lync 2013 Hybrid Goals Lync 2013 Hybrid Architecture Lync 2013 Hybrid Voice
What is Hybrid? Integration of on-premise infrastructure with cloud services (e.g. Office 365): Directory synchronization Identity and Single Sign-on (SSO) Services (e.g. Exchange Online)
Lync Hybrid - Office 365 GA Office 365 General Availability (GA) Old Office 365 Based on 2010 products version Released June 2012 Enable new customers to get Lync services through Microsoft Office 365 Interoperability with Microsoft Exchange and Microsoft Office SharePoint in the cloud Enable existing Microsoft customers to move to Office 365 service offering for Exchange
Lync 2010 Deployment Models Lync Server (On-Premises) IM/Presence Online meetings On-premises Public Switched Telephone Network (PSTN) audio conferencing Voice and telephony Email, Voice mail SharePoint Online Exchange Online
Lync 2010 Deployment Models (Cont d) Lync federation enables interoperability for online and server deployments Users in two separate Lync deployments can see presence and communicate through Lync Requires two separate domains for server and online deployments Optimized for person-to-person communications (Lync directory search not supported over federation)
Lync Hybrid Goals Enable new customers to get Lync services through a combination of on-premises and cloud deployments Enable existing Microsoft customers to move to Microsoft Office 365 service offerings Multi-release effort
Lync 2013 Hybrid - Architecture
Lync 2013 Hybrid Scenarios 1. Exchange moves to the cloud, Lync stays on-premises 2. Move/onboard department/branch office to the cloud 3. Enable a subset of users for based on usage profile 4. Start with the cloud, migrate users on-premises for extra features 5. Predictable all in migration to the cloud
Lync 2013 Hybrid Features What are the critical features that will get existing customers to the cloud? Feature Shared Session Initiation Protocol (SIP) address space between on-premises and online Priority High Interoperability between on-premises users and online users High User migration IM/Presence, Contact list, groups, federated contacts User migration meetings Migration to/from cloud; no client redeployment High Medium High
Hybrid Deployment Models Lync major workloads: IM/P Instant Messaging and Presence Conferencing IM, audio, video, web conferencing Enterprise Voice - Telephony Deployment model On-Premises Online Comments Supported IM/P, conferencing, voice On-premises only Yes User is homed and managed onpremises IM/P, Enterprise Voice Conferencing Model familiar for customers of the Live Meeting Service Not in Lync 2013 User is homed online IM/P, conferencing, voice All in in the cloud Yes, Lync to Phone Voice IM/P, conferencing Split workload with voice delivered through on-premises infrastructure Yes, Hybrid Voice
Lync 2013 Hybrid Migration Overview Cross-workload scenarios assume Exchange in the cloud (voice mail, OWA) Online coexistence requires Lync 2010 or Lync 2013 Server roles deployed on-premises Migration experience depends on workload No split workload of conferencing for a user; only for voice as part of Hybrid Voice Migration user data IM/P: Contact list, Groups, ACLs EV: User level call routing capabilities Not migrated Meeting content and scheduled meetings ( Rescheduling tool is planned to help with this transition) On-premises policies and configuration (Online/On-premises require separate configuration) Data from Legacy versions (< R2) (Complete migration to supported version before you proceed) Client migration Lync 2010 Client CU2+ supported against /Lync on-premises For R2 environments, a move to a Lync 2013 pool prior to migration
Lync 2013 Hybrid Migration Migration Online Coexistence IM/P Conf Voice IM/P Conf Voice LCS 2005 SP1 X N/A N/A X N/A N/A OCS 2007 X X X X X X OCS 2007 R2 Lync Server 2010 Lync Server 2013 Legend X No specific action required End user/admin action required Not supported
Lync 2013 Hybrid Deployment Requirements Server Deployment Component Description Notes Office 365 DirSync Active Directory Federation Services (AD FS) Lync 2010+ Federation Edge Synchronization of on-premises Active Directory (AD) with Office 365 Single sign-in (SSO) authentication infrastructure; end users get Office 365 services with on-premises credentials Interoperability between online and on-premises is built on the federation framework Common requirement with Exchange Common requirement with Exchange Coexistence between online and on-premises IM/Presence Conferencing Lync 2013 admin interface Cross-premise migration is available through Lync Management Shell Admin interface can be used to move 2010 or 2013 users directly to online Lync 2013 pool for hybrid voice features Hybrid Voice with E911 and Media Bypass require that a Lync 2013 pool/server be deployed on-premises Only required for these two specific hybrid voice features
Lync 2013 Hybrid Coexistence Lync Federation Edge Office 365 Microsoft Federation Gateway Exchange Online SharePoint Online Lync 2010+ Pool Edge Directory Sync Integration between local IT systems and the cloud Legacy OCS 2007 R2 Lync 2010 Pool Active Directory AD FS v2 (Geneva) Same as Exchange DirSync Provisioning, GAL Federation for SSO Lync Hybrid Interoperability
Lync 2013 Hybrid Migration Approach Lync Hybrid Coexistence Requires Lync 2013 Server Roles On-Premises On-Premises Version(s) Lync 2013 Hybrid Topology Migration Strategy OCS 2007 R2 Lync Server 2010 OCS 2007 R2 user pools Lync 2013 Federation Edge (federation route) Lync 2013 pool (CMS) Lync 2010 Federation Edge Server and next hop for the federation traffic; requires Lync 2010 CU5+ version Hybrid Voice requires one Lync 2013 Server deployed on-premises 1. Move R2 user to Lync 2013 pool 2. Deploy Lync 2013 client 3. Migrate user to 4. Postmigration tasks: Reschedule meetings 1. Move Lync 2010 user to Both Lync 2010 and Lync 2013 Client are supported 2. Postmigration tasks: Reschedule meetings Lync 2013 Server Edge + pools 1. Move Lync 2013 user to 2. Postmigration tasks: Reschedule meetings
Lync IM/Presence Profile Lync capabilities OCS 2007 R2 On-Premises Lync 2010+ Office 365 GA Office 365 Lync 2013 Lync Online Rich Presence IM PC-to-PC audio/video calling Click To Communicate in Office Federation with /Live Mac client Mobility iphone N/A IM archiving X
Lync IM/Presence Profile (Cont d) Lync Capabilities OCS 2007 R2 On-Premises Lync 2010+ Office 365 GA Office 365 Lync 2013 Lync Online Activity feed N/A Persistent chat X X IM/Presence* (through OWA) X Skill search in SharePoint N/A X X Federation with Yahoo, AOL X TBD Mobility BES N/A X X Mobility Nokia Mobility Windows Mobile
Lync Online Meetings Profile Lync Capabilities OCS 2007 R2 On-Premises Lync 2010+ Office 365 Office 365 Lync 2013 Multiparty PC audio/video Ad hoc meetings Dial out to PSTN Desktop sharing Application sharing Scheduled meetings Rich client for meetings Reach client for meetings CAA PSTN dial-in meetings X X Audio Conferencing Provider PSTN dial-in meetings X Meeting content archiving X
Lync - Voice Profile Lync Capabilities OCS 2007 R2 On-Premises Lync 2010+ Hybrid Voice Lync to Phone Call hold/retrieve Call transfer Call forwarding Voice mail (UM) USB peripherals Outside voice mobile Delegation, team call Integration with on-premises PBX X Remote call control (RCC) X X
Lync - Voice Profile Lync Capabilities OCS 2007 R2 On-Premises Lync 2010 Hybrid Voice Lync to Phone Private line N/A X Voice resiliency N/A X X Enhanced 911 (E911) N/A X Unified Communications (UC) devices Response Group Service (RGS)/Call Park Service (CPS) Analog devices, common area phone Integration with on-premises Call Center solutions X X X X X Media bypass X N/A
Lync 2013 Hybrid Voice
What is Hybrid Voice? Hybrid Voice enables Public Switched Telephone Network (PSTN)/PBX connectivity for cloud users through the PSTN infrastructure that is part of the onpremises deployment Kathy Lync On- Premises Dave Infrastructure PSTN GW Lync FE Pool Edge Server PSTN Internet John
Registration 1. client discovers the server through the Domain Name Service (DNS) Service Location (SRV) resource record PSTN Lync On-Premises DNS SRV 1 PSTN Infra 2 0 Dave 3 Internet Infrastructure 2. On-premises server redirects the client to the cloud Lync FE Edge Server Media Signaling
Call Flows
Call Flow Peer to Peer: Two Lync Online Users 1. Session Initiation Protocol (SIP) signaling flows through 2. Media flows using the optimal path between the client endpoints PSTN Lync On-Premises John 3 2 Internet 4 Dave 1 PSTN GW Lync FE Edge Server Infrastructure Media Signaling
Call Flow Peer to Peer: On-Premises to Users 1. SIP signaling is routed between the on-premises deployment and 2. Media flows using the optimal path between the client endpoints Kathy Internet Lync On- Dave Premises 5 4 1 Lync On- Premises Lync FE 2 Edge Server 3 Infrastructure Media Signaling
Call Flow Incoming PSTN Call 1. An incoming PSTN call is routed to the on-premises gateway, then moves to the on-premises Lync Server 2. The number is located via Reverse Number Lookup (RNL), routed to, and then routed to the endpoint 3. Media flows using the optimal path between the client endpoint and PSTN infrastructure/ms Call Bypassed PSTN Lync On-Premises PSTN GW 5a 1 2 5b Lync FE Dave 5b 3 Edge Server 5 4 Internet 4 Infrastructure 5a is the media path when bypassed 5b is the media path when not bypassed Media Signaling Bypassed Media
Call Flow Incoming PSTN Call (Internet User) 1. An incoming PSTN call is routed to the on-premises gateway, then moves to the on-premises Lync Server 2. The number is located via RNL, routed to, and then routed to the endpoint (on the Internet) PSTN 1 2 PSTN GW 5 Lync On-Premises On-Premises Lync Server 2 5 Internet 3 Edge Server 3 Infrastructure 3. Media flows using the optimal path between the client endpoint and the MS 5 John 4 Most likely through the on-premises Edge Server; if not, between the online and on-premises Edge Server Media Signaling
Call Flow Outgoing PSTN Call 1. An outgoing PSTN call request is placed by a user hosted on Lync Online 2. An RNL is performed and fails to associate a user 3. The request is assumed to be a PSTN/PBX call and is proxied to the on-premises Lync Server 4. Voice policy enforcement and call authorization are performed onpremises 5. The call is routed to PSTN egress and media bypass setup to client Call Bypassed PSTN Voice policy enforcement and call authorization done on-premises PSTN GW 4a Lync On-Premises 4b 3 Dave 4b On-Premises Lync Server 2 1 Internet 2 Edge Server Infrastructure 6. Media flows using the optimal path between the client endpoint and PSTN infrastructure/ms Media Signaling Bypassed Media
Call Flow Outgoing PSTN Call (Internet User) 1. An outgoing PSTN call request is placed by a user hosted on Lync Online 2. An RNL is performed and fails to associate a user 3. The request is assumed to be a PSTN/PBX call and is proxied to onpremises Lync Server 4. Voice policy enforcement and call authorization are performed onpremises 5. The call is routed to PSTN egress 6. Media flows using the optimal path between the client endpoint and MS PSTN PSTN GW 5 4 Lync On-Premises On-Premises Lync Server 5 3 5 John 1 Edge Server Internet 2 2 Infrastructure Most likely through the on-premises Edge Server; if not, between the online and onpremises Edge Server Media Signaling
Call Routing Summary Inbound call flow User s Direct Inward Dial (DID) number terminates at PSTN gateway or PBX Call is routed to on-premises Lync deployment User s Active Directory object indicates a different deployment locator Request is proxied through on-premises Edge proxy to Invite is routed to end user s logged-in endpoints If accepted, media is routed either locally or through the company s Edge Server or firewall If rejected, media is routed to Microsoft Exchange Online Unified Messaging (UM) Outbound call flow User instantiates a PSTN call Client normalizes number and sends invite to home server Voice policy enforcement and call authorization is performed on-premises Call is routed to PSTN egress and Media Bypass setup to client
Call Routing Summary (Cont d) Requirements PSTN gateway, IP-PBX system, or IP telephony service provider terminating on-premises Connectivity to on-premises Lync installation with Mediation Server role (same, separate, or virtualized server) Basic Hybrid Voice feature will be supported in a Lync Server 2010 deployment Call Hold/Retrieve, Call Transfer, Call Forwarding, Voice Mail, USB Peripherals, Outside Voice Mobile, Delegation, Team Call, integration with on-premises PBX, calling onpremises analog devices and common area phones Advanced Hybrid Voice features require one Lync Server 2013 pool E.911, Media Bypass
Summary Customers want to move enterprise services to the cloud Phased transitions will be performed that will lead to a complete transition to the cloud While a transition is being planned, you need an approach that: Cleanly moves existing functionality to the cloud Gives time to validate quality, reliability, and the security of the offering Continues to allow existing investments to be utilized To facilitate the transition, Lync will offer support for hybrid environments Hybrid Voice allows customers to integrate with their on-premises infrastructure to: Migrate users from Lync on-premises to online Leverage an existing PBX infrastructure Maintain existing carrier relationships
VPRAŠANJA Prosimo vas, da po koncu predavanja izpolnite vprašalnike. Nekoga izmed vas bomo nagradili z Nokio Lumia 820. Vprašalniki bodo poslani na vaš e-naslov, dostopni pa bodo tudi preko profila na spletnem mestu www.ntk.si Najlepša hvala! Iščete kakovostno izobraževanje? Obiščite Microsoftove izobraževalne centre: Uspeh = Znanje = Microsoftovi uradni tečaji + predavatelji Microsoft Certified Trainer