Reverse Proxy and Hardware Load Balancer Considerations for Mobility

All Lync mobile traffic will go through a reverse proxy regardless of the client location. Given the roaming nature of mobile clients, connection affinity is better controlled when the client connects through the same service. In the case of Lync Mobile, that service will always be the external web services directory, which is published through a reverse proxy solution. When external Lync services are being deployed, a reverse proxy must be configured to publish the Front End Pool Web Services to the Internet. The Mobility Service will run on the same URL as the Front End Pool Web Services, and under a subdirectory for the appropriate Mobile Service. However, the LyncDiscover service, although it will point to the same Front End Server Web Service, will require a unique FQDN defined, and the reverse proxy will require an entry to support that FQDN.