Topic Last Modified: 2013-02-14
A shared SIP address space, also known as a split-domain deployment, or a hybrid deployment, is a configuration where users are deployed across an on-premise deployment and an online environment. The desired outcome is to have a user, regardless of where their home server is located (on-premise or online), log into the deployment and be redirected to their home server location. To accomplish this, the Autodiscover feature of Lync Server 2013 is used to redirect the online user to the online topology. You can do this by configuring the Autodiscover uniform resource locator (URL) by using the Lync Server Management Shell, the Get-CsHostingProvider cmdlet, and the Set-CsHostingProvider cmdlet.
Mobility for the Split Domain Deployment
You will need to collect and record the following deployed attributes:
From the Lync Server Management Shell, type
In the results, find the online provider with the attribute ProxyFQDN. For example, sipfed.online.lync.com.
Record the value of the ProxyFQDN.
Enable federation in the on-premise Lync Server Control Panel, allowing federation with the online provider.
Enable federation for the online provider. By default, all online users are enabled for domain federation and can communicate with all domains.
If you will define blocked and allowed domains, determine the domains that you will explicitly allow or explicitly block.
For online federation, you must plan for firewall exceptions, certificates, and DNS host (A or AAAA, if using IPv6) records. Additionally, you must configure federation policies. For details, see Planning for Lync Server and Office Communications Server Federation.