Using On-Premise Systems with a Hybrid Deployment

The on-premise requirements for a hybrid deployment depend on whether there is an existing Lync or OCS 2007 R2 installation on-premise, as well as whether hybrid voice will be included in the deployment. If there is an existing OCS 2007 R2 pool, a Lync 2013 Front End pool and Edge pool will need to be installed alongside the OCS installation, and users will need to be moved to the Lync 2013 pool before being migrated to Lync Online.

If there is an existing Lync 2010 Front End pool and Edge pool, the Lync 2010 Edge pool can be federated with Lync Online/Office 365 to create a hybrid deployment that offers basic hybrid voice features. Basic hybrid voice features supported with an on-premise Lync 2010 pool include the following:

• Call hold/retrieve

• Call transfer

• Call forwarding

• Voice mail

• USB peripherals

• Outside voice—mobile

• Delegation

• Team call

• Integration with on-premise PBX

• Analog devices

• Common area phones

Figure 28.6 shows a sample hybrid topology with Lync 2010 on-premise, which can be used to provide basic hybrid voice features for cloud users, and the full Lync voice feature set for on-premise users.

Image

Figure 28.6. Hybrid topology with Lync 2010 on-premise, supporting basic hybrid voice features.

If advanced hybrid voice features are required, at least one Lync 2013 Front End server needs to be installed to handle voice routing. In addition, the Lync 2010 deployment must be running cumulative update 5 and above to support this mixed hybrid topology. Advanced hybrid voice features supported only with an on-premise Lync 2013 pool include the following:

• Enhanced 911

• Response Group Service

• Call Park Service

• Media bypass

Figure 28.7 shows a sample hybrid topology with both Lync 2010 and Lync 2013 on-premise, which can be used to provide advanced hybrid voice features for cloud users, and the full Lync voice feature set for on-premise users.

Image

Figure 28.7. Hybrid topology with Lync 2010 and Lync 2013 on-premise, supporting advanced hybrid voice features.

For a new on-premise deployment of Lync 2013, one Front End pool is required, using either the Standard or the Enterprise Edition. As would be true of any on-premise deployment, voice functionality requires that the Mediation Server role be installed, along with the PSTN infrastructure. The Mediation Server role can either be collocated with the Front End pool or installed in a separate pool.

With any Lync hybrid deployment, regardless of whether the on-premise installation includes earlier versions of Lync/OCS or just Lync 2013, an Edge pool consisting of at least one Edge Server is required. The Edge pool must also be enabled for federation, including the external DNS records that are required for federation.


Note

An Edge pool used with a hybrid deployment takes on additional functions beyond those that are typical for a standard on-premise deployment. In addition to the standard Edge services of remote access and federation, the Lync Edge pool in a hybrid deployment is used for federating with Lync Online/Office 365, routing of SIP signaling traffic between the on-premise deployment and the cloud, and in some circumstances routing of media traffic for Lync Online users who connect via the Internet.


Additional on-premise requirements for a hybrid deployment include the following:

• Directory synchronization must be enabled between the on-premise Active Directory and Lync Online/Office 365, as described in the “Planning for Directory Synchronization” section of this chapter.

• Active Directory Federated Services must be installed and configured to enable SSO between the on-premise Active Directory and the Lync Online/Office 365 directory, as described in the “Planning for Single Sign-On with AD FS” section of this chapter.

• In addition to the standard certificate requirements for the on-premise AD FS deployment, the public SSL certificate used as the server authentication certificate must use a subject name of sts.<SIPdomain>, where <SIPdomain> is the primary SIP domain that will be split across the Lync Online and Lync on-premise deployments. If additional, secondary SIP domains will be used, these can also be added as subject alternative names on the certificate.

• To access Lync Online, either the Lync 2013 client or the Lync 2010 client running cumulative update 2 and above can be used.

Figure 28.8 shows the components included in a typical Lync hybrid topology with only Lync 2013 on-premise, supporting the full feature set including advanced hybrid voice.

Image

Figure 28.8. Components of a typical hybrid topology with Lync 2013 on-premise.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset