Lync mobility deployment – Quick reference guide

•        Login to frontend server and ensure that mobility services are successfully installed. You can see new virtual directory (McX) created under internal and external web sites . 

•        Verify following DNS records are resolving properly. lyncdiscoverinternal.<sipdomain from internal network and lyncdiscover.<sipdomain from public DNS. Ensure that these IP addresses are pointed to reverse proxy external interface. 

•         Ensure that port 5086 is allowed from internal network and port 5087 is allowed from internet for mobility service process. You should set the ports on external and internal web services using Set-CsWebServer commandlet. 

•         Verify certificate subject alternative name on frontend , director and reverse proxy roles . Following SAN should be added on all boxes . lyncdiscoverinternal.<sipdomain , lyncdiscoverinternal.<sipdomain . Reverse proxy required only external auto discover SAN. 

•        Verify web publishing rule on ISA box and ensure that external traffic is forwarding to frontend server as expected. Port 80-8080 forwarding doesn’t need a SAN entry on reverse proxy. However 443-4443 does required a SAN entry on reverse proxy server . 

•          Have you tested peer to peer mobility instant messaging after deployment? It should be working as expected. 

•        WI-FI internal mobility connectivity required cookie-based persistence set on hardware LB for internal web service URL. 

•      For push notification for apple IOS and windows phones required port 5223 from enterprise WI-FI network . 

•       For joining conference and work call feature required enterprise voice feature to be enabled for users .