Module 1

Module 01Voice Architecture

Microsoft Official Course120337B1: Voice ArchitectureModule OverviewArchitecture and Server RolesVoice Features of Lync Server 2013Site TopologiesCourse 20337: Enterprise Voice and Online Services with Microsoft Lync Server 2013 covers Lync Server 2013 voice features and deploying Lync Online. Throughout most of this course (modules 28, 11, and 12), concentrate on the features, components, and functionality that are specific for integrating Lync as the center of a companys voice call deployment.220337B1: Voice ArchitectureLesson 1: Architecture and Server RolesDeployment OptionsLync 2013 Enterprise Edition TopologyLync Server 2013 Server RolesSession Initiation Protocol SupportThis lesson is common with 20336A to provide a common foundation for the students. Emphasis should be placed on voice and cloud features covered in this course. The major changes in Lync Server 2013 are described. These changes impact planning in a Lync deployment of Enterprise Voice. In addition, the component is a services-oriented architecture is described. Emphasis should be on components that impact voice.320337B1: Voice ArchitectureDeployment OptionsMicrosoft Office 365, Lync OnlinePartner-hosted multi-tenantSingle domain and directory Users splitserver/onlineLync Server 2013Private cloud/dedicatedCloudHybrid On-PremisesEnabling gradual migration and coexistence between Lync private and public cloud

This topic is an overview of the deployment options. The majority of this class will look Lync Server 2013, while module 9 covers Lync Server Online and hybrid deployments.A lot of companies want to try an online solution in production, but only for a portion of their users and with the ability to roll back; Microsoft is the only company to propose this.420337B1: Voice ArchitectureLync 2013 Enterprise Edition TopologyInternalExternalPerimeter Network

Reverse proxy

LyncEdge

HybridFederated NetworkPublic ProvidersPSTN

ADMIISIdentity

EdgeMore Secure Federation and InteroperabilityExternal User IngressPoolFewer, Consolidated ServersVirtualized and Higher ScaleServicesConsolidated ArchivingSCOM, AD, DFSExchangeVoicemail/Archive

SCOMMonitoring

DFSFiles Store

Office Web AppsWeb Access

SQLCDR/QoE/ReportDB

UC End Points

EE Pool

Back-endFront-endIP-PSTN GatewayPersistent Chat (optional)

Mediation Server

PBX

This topic is shows the relationship the Lync Server 2013 Front End pool and other servers. For each zone provide an overview of the functionality provided by the servers in that zone:Enterprise Edition Pool (EE Pool)Unified communications end points (UC End Points): client of choice include Lync client application for PC, apps for mobile devices, USB phones and IP phones.Perimeter Network: Skype interconnection, Extensible Messaging and Presence (XMPP) federation and Office 365 hybrid topology now natively part of the Edge role, including high availability.IP-PSTN Gateway: Mediation Server required to connect with PBX and PSTN through a gatewayBack-end: Includes Active Directory, Exchange, SCOM, DFS, Office Web Apps and SQL Server Describe the simplification of the Lync infrastructure.Server roles consolidation.Because of Edge enhancement, Director is not necessary.Monitoring/archiving consolidation on the Front End server.Audio/Video MCU always collocated on the Front End server.Persistent chat and pool enhancementHighlight the following points critical to this course:For voice support, not only is there a connection to the Internet, but also the PSTN.Office 365 resides in the external network, so requires connection through the Lync Edge Server.520337B1: Voice ArchitectureLync Server 2013 Server RolesMediation ServerFront-End Server

Back-End Server

DirectorPersistent Chat Compliance Back-End Server

Standard Edition Server

Edge ServerLync Server 2013 Server RolesPersistent Chat Back -nd Server

Persistent Chat Server

This slide is common with 20336, so put emphasis on the servers involved in voice: Front End server (dial plans), Mediation Server (connection to PBX and PSTN), and Edge Server (connection to external clients like mobile phones).QuestionWhat are the four functions managed by the Front End server?AnswerThe Front End server:Provides SIP Registrar and Presence aggregation for handling client registrations and publishing aggregated user presence to other users.Provides conferencing services, audio/video conferencing, web conferencing, application sharing, instant messaging conferencing, and dial-in conferencing services.Manages the Central Management Database that deploys configuration data to all other Lync Server 2013 servers, including Edge Servers.Provides device and client updates for Lync Server 2013 phone devices and Lync Server 2013 clients.620337B1: Voice ArchitectureSession Initiation Protocol SupportSIP is an application-layer control or signaling protocol for voice over Internet protocol (VoIP)SIP creates, modifies, and terminates sessions among one or more participantsSessions include Internet-based telephone calls, multimedia distribution, and multimedia conferencesSIP-related RFCs and over 200 IETF Internet drafts and proposed standards form the basis of the Microsoft Unified Communications design

720337B1: Voice ArchitectureLesson 2: Voice Features of Lync Server 2013Enterprise Voice ChangesM:N Interworking RoutingMediation ServerOverview of Inter-Trunk RoutingSurvivable Branch Sites820337B1: Voice ArchitectureEnterprise Voice ChangesDisaster RecoveryE911 RoutingResponse GroupCall ManagementVoice in the CloudVirtual Desktop InfrastructureIPv6

This topic briefly introduces about all topics outlined on this slide with particular emphasis on Enterprise Voice and Lync Online features. Features specific to Lync Online are in italics and will be discussed as follows: Disaster Recovery is covered in Module 12, Voice Resiliency Features of Lync Server 2013.E911 is covered in Module 5, Configuring and Deploying Emergency Calling.Routing is covered in Module 2, Configuring Basic Enterprise Voice Functionality and Module 6, PSTN Integration.Response Group is covered in Module 4, Voice Applications.Call Management is covered in Module 2, Configuring Basic Enterprise Voice Functionality.Voice in the Cloud is covered in Module 9, Online Architecture and Configuration and Module 10, Hybrid Voice and Unified Messaging.QuestionAdatum has deployed Lync Server 2013 in their sales offices around the world. They have sales offices with PSTN gateways in Sydney, Redmond and New York. All support technicians reside in Boston and they are still using a legacy call center PBX. Adatum wants to provide local numbers for their customers that look like they are calling a number in the local sales office, but in reality the call will ring the next available support technicians. Which new feature of Lync Server 2013 are they taking advantage of? AnswerInter-trunk routing 920337B1: Voice ArchitectureM:N Interworking Routing10OCS 2007 R2Lync Server 2010

RouteGWRoute_USLAX_GWRoute_EURDE_GW1DE_GW2Route_APACSYD_GWRouteMSRoute_USLAX_MSRoute_EURDE_MS1DE_MS2Route_APACSYD_MS

Lync Server 2013

RouteTrunkRoute_USLAX_TRRoute_EURDE_TR1DE_TR2Route_APACSYD_TR

Explain the differences in routing from Office Communicator 2007 R2 to Lync Server 2013. Routing is covered in more detail in module 6.QuestionWith Lync a route to the public telephone network is defined as?AnswerA Mediation Server, a gateway server and a gateway port.1020337B1: Voice ArchitectureMediation Server

PSTN

Lync ServerFront End PoolQualified PSTN GatewayLync Server MediationServerMediation Server is required to connect to PBX, SIP gateway or PSTN. QuestionWith Lync Server 2013 a route, to the public telephone network, is defined as?AnswerA mediated server, a gateway server and a gateway port. A mediation server can connect to more than one gateway. Those gateways could be located in different geographies, even different countries, so it is important to specify the correct gateway and the mediation server with a connection to the same gateway.1120337B1: Voice ArchitectureOverview of Inter-Trunk RoutingLync Server 2013: Supports call routing from an incoming trunk to an outgoing trunk to provide routing functionalities to other systemsA possible alternative for PBX integration scenarios Better integration with systems certified to connect with LyncReduces complexity of routing rules on IP-PBX for incoming calls

This is an overview of inter-trunk routing. Details are provided in Module 6. 1220337B1: Voice ArchitectureSurvivable Branch SitesSurvivable Branch ApplianceHardware device that includes a subset of Lync capabilities, including a set of services which run the SBA applications and a GatewayBuilt by partners Survivable Branch ServerWindows Server-based computer that has Registrar and Mediation ServerFull Lync Server Central SiteReview the options for deploying survivable sites. The detail for survivable sites will be covered in Module 11, Voice Resiliency.1320337B1: Voice ArchitectureLesson 3: Site TopologiesNo Branch Office IntegrationSimple Branch Office IntegrationSurvivable Branch OfficeLarge Organization Voice TopologyExample Voice Architecture1420337B1: Voice ArchitectureNo Branch Office Integration

PSTN GatewayCentral SiteBranch Site(zero or more)Or

Front-End Pool

Standard Edition Server

PBX/PSTN GatewayPSTNThis is not a reference topology, but discusses the ramifications of not deploying Lync to all branches. 1520337B1: Voice ArchitectureSimple Branch Office Integration

PSTN GatewayCentral SiteBranch Office (No Lync server)Or

Front End Pool

Standard Edition Server

WAN

PSTN GatewayThis is not a reference topology. The advantage is that calls within the company are no longer using the PSTN. The disadvantage is the branch office cannot make or receive calls if the WAN is down.1620337B1: Voice ArchitectureSurvivable Branch Office

PSTN GatewayCentral SiteBranch Site(one or more)Or

Front-End Pool

Standard Edition Server

Or

SurvivableBranch Appliance

SurvivableBranch ServerWAN

PSTN GatewayThis example is based on the Reference Topology for Medium Organizations. Only voice-related services are discussed in the Student notes.1720337B1: Voice ArchitectureLarge Organization Voice Topology

PSTN GatewayCentral Site ACentralSite BOr

Front-End Pool

Standard Edition Server

WAN

PSTN GatewayOr

Front-End Pool

Standard Edition Server

WANPaired Front End PoolBranch Site CThis example is based on the Reference Topology for Large Organizations. Only voice-related services are discussed in the Student notes. Voice resiliency is discussed in module 11.1820337B1: Voice ArchitectureExample Voice Architecture

PSTNLondon Central Site

New York Survivable Branch

Redmond Office

IP-PBXIP-PBXGatewayLync Server PoolLync SBS

This topic shows the architecture of the complete solution for the lab scenario if PSTN connections were available (blue dashed lines). The lab does not include PSTN connectivity. Discuss routing for various calls. For example:Redmond Lync user to New York Lync userRedmond Lync user to New York PBX userRedmond Lync user to Redmond customer (PSTN user)Redmond Lync user to London customer (PSTN user)Redmond Lync user to New York Lync user if corporate WAN is down1920337B1: Voice ArchitectureModule Review and TakeawaysReview Question(s)Real-world Issues and ScenariosReview Question(s)QuestionWhat are the four functions managed by the Front End server?AnswerThe four functions are:SIP Registrar and PresenceConferencing ServicesCentral Management DatabaseClient UpdatesReal-world Issues and Scenarios2020337B1: Voice Architecture