Lync Mobile 2013 client cannot sign in although Lync Mobile 2010 client can sign in
Applies to Lync mobile 2013, 2010 and Lync Server 2013 Enterprise and Standart
In an environment contains 1 Lync 2010 Enterprise Pool and 1 Lync 2013 Standart edition pool, Lync Mobile 2013 client cannot sign in although Lync Mobile 2010 client can sign. None of the server are published via TMG or a reverse proxy.
I immediately started to test Lync 2013 mobile. I installed lync 2013 Updates for lync 2013 on lync server and lync mobile 2013 client but eventually cannot sign in. Although Lync Mobile 2010 client can sign. It seems Lync mobile 2013 client does require external Web site access published via reverse proxy. Although Lync 2010 mobile was working without any problem in my tests.
According to to official docs, If you want your mobile users to connect from inside your lan and Internet, mobile client must always connect to external web site. By default ExposedWebURL is set to External. I f you set it to internal, mobile user only can connect when they are inside the network and cannot connect from internet. But some how I observe that lync mobile 2010 can sign in but lync 2013 mobile cannot sign in from internal network without reverse proxy that publishes the external site. We got network traces and we saw that lync mobile 2013 must connect to external site.
PS C:\> Get-CsMcxConfiguration
Identity : Global
SessionExpirationInterval : 259200
SessionShortExpirationInterval : 3600
ExposedWebURL : External
PushNotificationProxyUri : sip:firstname.lastname@example.org
So here is the solution if you want to test Lync mobile 2013 client inside your network without TMG
Set Windows 2008 r2 server. (say it Proxy1) as reverse proxy. Install IIS and configure ARR based on article: Using IIS ARR as a Reverse Proxy for Lync Server 2013
– Create DNS A record that points to external URL to Proxy1 .That is lyncpoolext.contoso.com points to Proxy1 IP adress.
– Proxy1 accepts connections to 443 port and redirects the connection to the port 4443 of the Lync Server 2013 Front End Server
– Create DNS A record for lyncdiscover.contoso.com that points to the IP address of the Lync Server 2013 Front End Server
– Connect device to your internal WIFI network, install Lync Mobile 2013 and enjoy the voice and video features!
Defining Your Mobility Requirements
Do you want to support Lync mobile clients both internal and external to the corporate network, or support clients only inside the corporate network?
If you want to support mobile clients internal and external to your network, mobile devices can access mobility features from any location. The default configuration is to support clients both internal and external to the corporate network.
Although the default configuration enables mobile client traffic to go through the external site, you can restrict mobile client traffic to the internal corporate network. When you restrict the traffic to the internal network, users can use Lync mobile applications on their mobile devices only when they are inside the network.
For deployments that support mobility using the Mcx mobility service and Lync 2010 Mobile, you run the Set-CsMcxConfiguration cmdlet. To set mobility for internal use only, you would use a command similar to the following:
Set-CsMcxConfiguration -Identity site:Redmond -ExposedWebURL Internal