When Mobility is being deployed as part of a new deployment or this functionality is being added to an existing environment, the key change to the reverse proxy solution is certificates. When the LyncDiscover service is being deployed through a reverse proxy, there are two possible solutions:
LyncDiscover.<sipdomain> as a subject alternative name (SAN) entry on the web services public certificate. This can become costly when there are many SIP domains supported in the environment.
• Publish the LyncDiscover service over HTTP. When the service allows connections on port 80, the initial request will not be over TLS; clients are then redirected to the external web services FQDN for the Front End Server ...