Topic Last Modified: 2013-02-14

During the planning phase for the Lync Server 2013 mobility feature, when you are using Lync 2010 Mobile and Lync 2013 Mobile clients, you make decisions that determine your deployment steps.

Here are the decisions that you must consider:

• Do you want to use automatic discovery for Lync mobile clients?

  If you want to support automatic discovery, you need to create new internal and external Domain Name System (DNS) records, add subject alternative names to certificates on the Front End Servers, Directors, and reverse proxy, and modify the existing publishing rules on the reverse proxy. For details, see Technical Requirements for Mobility. With automatic discovery, users can automatically locate Lync Server 2013 Web Services from anywhere inside or outside the corporate network, without entering URLs in their mobile device settings.

  If you use manual settings instead of automatic discovery, mobile users need to manually enter the following URLs in their mobile devices:

  • https://<ExtPoolFQDN>/Autodiscover/autodiscoverservice.svc/Root for external access

  • https://<IntPoolFQDN>/AutoDiscover/ autodiscoverservice.svc/Root for internal access

  We strongly recommend using automatic discovery. The primary use of manual settings is for troubleshooting.

• If you decide to support automatic discovery, are you willing to update certificates on the reverse proxy with subject alternative names for each SIP domain?

  If you have many SIP domains, updating public certificates on the reverse proxy can become very expensive. If this is the case, you can choose to implement automatic discovery so that the initial Autodiscover Service request uses HTTP on port 80, instead of using HTTPS on port 443. However, this is not the recommended approach. If you decide to choose this alternative, you do not need to update the certificates on the reverse proxy, but you need to create a web publishing rule for HTTP on port 80. For more details, see Technical Requirements for Mobility.

• 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:

  	Copy Code
  Set-CsMcxConfiguration -Identity site:Redmond -ExposedWebURL Internal

  Note:
  There are no additional configurations required for UCWA. UCWA does not have an equivalent internal-only configuration.

  Important:
  If you are using a Lync Server 2013 Front End Server or Front End pools and you do not have any Lync Server 2010 Front End Servers or Front End pools, there is no requirement for cookie-based persistence. If you need to retain any Lync Server 2010 Front End Servers or Front End pools, the same rules still apply as in Lync Server 2010 for cookie-based persistence.

• Do you want to support push notifications for Apple iOS devices and Windows Phones?

  If you support push notifications, supported Apple iOS devices and Windows Phones receive a notification of events that occur when the mobile application is inactive. You must configure your Edge Server to have a federation relationship with the cloud-based Lync Server Push Notification Service, which is located in the Lync Online datacenter, and run a cmdlet to enable push notifications.

  If you want to support push notifications over your Wi-Fi network, in addition to supporting push notifications over the mobile device providers' 3G or data networks, you must open port 5223 outbound on your enterprise Wi-Fi network. Supporting push notifications over the Wi-Fi network supports mobile devices that use only Wi-Fi and mobile devices that have poor indoor reception.

  Important:
  Opening port TCP 5223 is required only when supporting Apple devices running the Lync 2010 Mobile client.

  If you do not support push notifications, users of Apple mobile devices and Windows Phones will not find out about events—such as instant message invitations or missed messages—that occur when the mobile application is inactive.

  Note:
  Lync 2013 Mobile clients on Apple devices do not require push notification. The Lync 2013 Mobile clients on Windows Phone use push notification. Planning for push notification and the push notification clearinghouse remain the same for Lync Mobile on Windows Phone and Apple devices that are not able to run the Lync 2013 Mobile client.

• Do you want all users to have access to mobility features, or do you want to be able to specify which users have access to these features?

  The table describes features available to users in Lync Server 2013. The defaults allow Call via Work, allow Voice over IP (VoIP), and enable Mobility. Here is the full set of available options:

  Feature/Paramater Name/Scope (Policy parameter names may not be the same)	Description	Introduced
  Enable Mobility Parameter Name : EnableMobility Scope: Global/Site/User	Administrative setting to control users in a given scope that have the Lync Mobile installed, If the policy is set to False, the user would not be able to sign into the client. The default setting is True.	Cumulative Update for Lync Server 2010: November 2011
  Enable Outside Voice Parameter Name : EnableOutsideVoice Scope: Global/Site/User	Controls a user’s ability to use Call Via Work, a feature that enables users to make and receive calls by using their work number instead of their mobile number. If set to False, the user will not be able to make or receive calls by using their work number from their mobile device. The default setting is True	Cumulative Update for Lync Server 2010: November 2011
  Enable IP Audio and Video Parameter Name : EnableIPAudioVideo Scope: Global/Site/User	Controls whether a user can use VoIP to make or receive voice or video calls on their mobile device. If set to False, the user will not be able to make or receive VoIP or video calls on their device. The default setting is True.	Microsoft Lync Server 2013
  Require WiFi for IP Audio Parameter Name : RequireWiFiForIPAudio Scope: Global/Site/User	This setting defines whether the client will be required to make and receive calls over VoIP on WiFi instead of the cellular data network. If set to True, the user can make and receive VoIP calls only when connected to a WiFi network. The default setting is False.	Microsoft Lync Server 2013
  Require WiFi for IP Video Parameter Name : RequireWiFiForIPVideo Scope: Global/Site/User	This setting defines whether the client will be required to make and receive video calls on Wi-Fi instead of on the cellular data network. If set to True, the user can make and receive video calls only when connected to a Wi-Fi network. The default setting is False.	Microsoft Lync Server 2013

  For a description of the policy settings that you can configure, and how to manage the policies, see New-CsMobilityPolicy, Set-CsMobilityPolicy, Get-CsMobilityPolicy, Grant-CsMobilityPolicy and Remove-CsMobilityPolicy.

• Do you want users who are not enabled for Enterprise Voice to be able to use Click to Join to join conferences?

  For users to have access to mobility features and Call via Work, they must be enabled for Enterprise Voice. However, users who are not enabled for Enterprise Voice can join conferences by clicking the link on their mobile device, if they have an appropriate voice policy assigned to them. You can either assign a specific voice policy to these users or make sure that a global policy or site-level policy exists that applies to them. The voice policy that you assign must have public switched telephone network (PSTN) usage records and routes that define the areas to which users can dial out to join a conference. For details about setting voice policy, PSTN usage records, and routes, see Configuring Voice Policies, PSTN Usage Records, and Voice Routes.

  Note:
  Mobile users who want to use Click to Join require a voice policy, along with the related PSTN usage records and voice routes, because clicking the link on the mobile device results in an outbound call from Lync Server 2013.

See Also