Plan for Mobility for Skype for Business Server 2015

Skype for Business Server 2015

마지막으로 수정된 항목: 2016-05-19

Plan for your implementation of 모바일 for 비즈니스용 Skype 서버 2015.

With 비즈니스용 Skype 서버 2015, you can deploy the 모바일 feature to provide 비즈니스용 Skype 서버 2015 functionality on mobile devices. This article provides details about the 모바일 feature, and helps you plan for your deployment.

The 모바일 feature for 비즈니스용 Skype 서버 2015 is able to support mobile clients for 비즈니스용 Skype, as well as Lync clients going back to 2010. Once it's deployed, your users can connect to your 비즈니스용 Skype 서버 2015 deployment using supported iOS, Android and Windows Phone mobile devices to take advantage of several different features, including Enterprise Voice features. We've included a partial list below, and you can also check 비즈니스용 Skype 서버 2015의 클라이언트 비교 표 for more info:

  • Send and receive messages

  • View presence

  • View contacts

  • Click to join a conference

  • Call via work

  • Single number reach

  • Voice mail

  • Missed call notification

  • Voice over IP (VoIP)

  • Attendee video (H.264)

  • Viewing meeting content (PowerPoint and desktop/application sharing)

All this is accomplished through the Unified Communications Web API, or UCWA. UCWA was first introduced in Lync Server 2013, and it's still in use for 비즈니스용 Skype 서버 2015 today. There's an additional functionality for communicating with Lync 2010 clients, and that's 모바일 Service (MCX). These are complimentary services, allowing for Lync Server 2010 and 2013 clients, as well as 비즈니스용 Skype clients, to access 비즈니스용 Skype 서버 deployments successfully.

We've included MCX here, but want to be clear that while this is supported, we plan to deprecate this in our next release, so that should be something you keep in mind for planning purposes. We will continue to use the UCWA, and recommend Lync 2013 and 비즈니스용 Skype clients be used going forward in an eventual post-MCX environment.

It's important to note that while all these features are available once 모바일 has been implemented, they may work a little differently on some devices. We've got a website that discusses what features work on what devices, at Mobile client comparison tables for Skype for Business. We also have some great device and OS information at 비즈니스용 Skype 서버 2015의 클라이언트 및 장치 계획.

모바일 makes use of the Autodiscover feature, which allows clients to automatically locate 비즈니스용 Skype 서버 web services without users needing to enter in any URLs (they won't even need to know them). If you need to do some troubleshooting, manual entry of URLs is still supported.

Push notifications are also supported, for when the 비즈니스용 Skype app isn't running in the background (or for mobile devices that don't support applications running in the background). A push notification is sent to a mobile device about an event that occurs when the device or app is inactive. A good example is missing an IM message when your phone's not active, which would result in a push notification being sent (this is presented as a toast or notification, like when the app is running in the background). With push notifications, users won't miss IM or voice calls.

For more information, we have the following sections:

There are four services that comprise 모바일 for 비즈니스용 Skype 서버 2015:

  • Unified Communications Web API (UCWA)

    Provides services for real-time communications with mobile and web clients for 비즈니스용 Skype 서버 2015. When 비즈니스용 Skype 서버 is deployed, a UCWA virtual directory's created in the internal and external web services. A virtual component in this virtual directory that accepts calls from UCWA-enabled clients. The client apps communicate over a representational state transfer (REST) interface for:

    • presence

    • contacts

    • instant messaging (IM)

    • VoIP

    • video conferencing

    • collaboration

    UCWA uses a P-GET based channel to send events, such as an incoming call, incoming IM, or a message to the client app.

  • Mobility service (MCX)

    Supports 비즈니스용 Skype 서버 functionality, such as IM, presence, and contacts, on mobile devices. The 모바일 service is installed on every 프런트 엔드 서버 in each pool that's intended to support 비즈니스용 Skype 서버 functionality on mobile devices. When you install 비즈니스용 Skype 서버 2015 a new virtual directory (Mcx) is created under both the internal and external websites on your 프런트 엔드 서버.

    As mentioned above, MCX is going to be deprecated in the next version of the product.
  • Autodiscover service

    Identifies the location of the user and enables mobile devices and other 비즈니스용 Skype clients to locate resources (such as the internal and external URLS for 비즈니스용 Skype 서버 2015 웹 서비스, the Mcx URL , or UCWA URL) regardless of network location. Automatic discovery uses hardcoded host names (lyncdiscoverinternal for users inside the network, lyncdiscover for users outside the network), and the SIP domain of the user. It supports client connections that use either HTTP or HTTPS.

    The Autodiscover service is installed on every 프런트 엔드 서버 and on every 디렉터 in each pool that's intended to support 비즈니스용 Skype 서버 functionality on mobile devices. When you install the service, a new virtual directory (Autodiscover) is created under both the internal and external websites on your 프런트 엔드 서버 and 디렉터.

  • Push notification service

    A cloud-based service that's located in your 비즈니스용 Skype 온라인 data center. On phones that don't have 비즈니스용 Skype client running in the background, when a new event happens, notification of a missed event (called a push notification) gets sent to the mobile device instead. The 모바일 service sends a notification to the push notification service (MPNS), which then sends it to the mobile device. The user can then respond to the notification on their mobile device to activate the app. An 에지 서버 is required for this functionality.

We have the following supported 비즈니스용 Skype 서버 applications for your topology planning:

  • 모바일 Standard Edition

  • 모바일 Enterprise Edition

You should be able to use this functionality with 비즈니스용 Skype 서버 에지 서버 or Lync Server 2013 에지 서버.

The 모바일 service is supported on 프런트 엔드 서버 when collocated with the 중재 서버 role, with two network interfaces, but you need to take appropriate steps to configure those interfaces. You'll need to assign IP addresses to the specific interface that will communicate as the 중재 서버, and the network IP interface that will communicate as the 프런트 엔드 서버. You can do this in 토폴로지 작성기 by selecting the correct IP address for each service, instead of using the default Use all configured IP addresses selection.

It's important to plan for the various mobile application scenarios your mobile users may encounter. For example, someone might start using a mobile app outside of work by connecting through a 3G network, then switch to the corporate Wi-Fi network when they reach work. They may switch to 4G when leaving their building. Planning now will allow you to support these network transitions and guarantee a consistent user experience.

The 모바일 services Mcx and UCWA use DNS in the same way. With Automatic Discovery, mobile devices use DNS to locate resources. During DNS lookup, a connection's attempted to the FQDN that's associated with the internal DNS record (lyncdiscoverinternal.[internal domain name]). If the internal DNS record can't be used to make that connection, a second connection is attempted, this time to the external DNS record (lyncdiscover.[sipdomain]). So why have two? A mobile device that's internal to your network will be able to use the internal Autodiscover URL. External mobile devices will use the external Autodiscover URL. In either case, the Autodiscover service will return all Web service URLs for the user's home pool, which includes the 모바일 service (Mcx and UCWA).

It's expected that the external Autodiscover requests will go through the UNRESOLVED_TOKEN_VAL(reverseproxy_nocaps) you've configured for 비즈니스용 Skype 서버 2015. However, both the internal 모바일 service URL and the external 모바일 service URL are associated with the external 웹 서비스 FQDN. Therefore, regardless of whether a mobile device is internal or external to your network, the device always connects to the 비즈니스용 Skype 서버 2015 모바일 service externally, through your UNRESOLVED_TOKEN_VAL(reverseproxy_nocaps).

As we just noted, all 모바일 service traffic (internal and external) will go through your UNRESOLVED_TOKEN_VAL(reverseproxy_nocaps). But sometimes an issue comes up when the internal traffic leaves through an interface, only to then try and come back in on the same interface. This can violate your spoofing (formally it's called TCP packet spoofing) security rules. You'll need to allow Hair Pinning to have 모바일 function.
If you're ready to do this, you can also choose to use a UNRESOLVED_TOKEN_VAL(reverseproxy_nocaps) that's separate from your firewall (for security purposes, spoofing prevention should always be enforced at your firewall). This way, the hairpin can happen at the external interface of your UNRESOLVED_TOKEN_VAL(reverseproxy_nocaps), rather than your firewall's external interface. This allows you to detect the spoofing properly at your firewall while you relax the rule at your UNRESOLVED_TOKEN_VAL(reverseproxy_nocaps), and you get your 모바일 functionality.
If you go this route, be sure to use the DNS host or CNAME records to define the UNRESOLVED_TOKEN_VAL(reverseproxy_nocaps) for the hairpin behavior (not the firewall), if possible.

There are some things you'll need to configure to support users inside and outside your corporate network.

These are the rules for internal and external web FQDNs:

  • New CNAME or A (host, if IPv6, AAAA) DNS records, for automatic discovery.

  • New firewall rule, if you want to support push notifications through your Wi-Fi network.

  • Subject alternative names on internal server certificates and UNRESOLVED_TOKEN_VAL(reverseproxy_nocaps) certificates, for automatic discovery.

  • 프런트 엔드 서버 hardware load balanced configuration changes source affinity.

These are the topology requirements needed to support the 모바일 Service and Autodiscover Service:

  • The 프런트 엔드 풀 internal web FQDN must be distinct from the 프런트 엔드 풀 external web FQDN.

  • The internal web FQDN must only resolve to, and be accessible from, inside the corporate network.

  • The external web FQDN must only resolve to, and be accessible from, the internet.

  • For a user inside the corporate network, the 모바일 service URL must be addressed to the external web FQDN. This requirement is for the 모바일 service, and applies only to this URL.

  • For a user outside the corporate network, the request must go to the external web FQDN of the 프런트 엔드 풀 or 디렉터.

If you support automatic discovery, you'll need to make the following DNS records for each SIP domain:

  • An internal DNS record to support mobile users who connect from inside your organization's network.

  • An external, or public, DNS record to support mobile users who connect from the internet.

The internal automatic discovery URL shouldn't be addressable from outside your internal network. The external automatic discovery URL shouldn't be addressable from within your network. But if this isn't possible for the external URL, your mobile client functionality probably won't be affected, because the internal URL will always be tried first.

We've covered most of this in our other documentation, but specifically for 모바일, you're going to want to have the following ports open on your enterprise Wi-Fi network if you have any users homed on a UNRESOLVED_TOKEN_VAL(nm_SurviveBranchApp) (SBA):

  • UcwaSipExternalListeningPort requires 5088.

  • UcwaSipPrimaryListeningPort requires 5089.

If you're using automatic discovery for your 비즈니스용 Skype mobile clients, you'll need to modify the SAN (subject alternative name) lists on your certificates to support secure connections from your mobile clients. If you already have certificates in-place, you'll need to request and assign new certificates with the SAN entries described here. This will need to be done for each 프런트 엔드 서버 and 디렉터 (if in your environment) that runs the Autodiscover service. We'd also recommend modifying the SAN lists on your UNRESOLVED_TOKEN_VAL(reverseproxy_nocaps) certificates, adding SAN entries for every SIP domain in your organization.

This should be a straightforward process if you're requesting the new certs off an internal CA (certificate authority), but public certificates are more complex, and potentially a lot more expensive to re-request, not to mention it may be costly to add a lot of SIP domains to a new public cert. In that situation, there is an approach that's supported, but not recommended. You can configure your UNRESOLVED_TOKEN_VAL(reverseproxy_nocaps) to make the initial Autodiscover service request over port 80, which will use HTTP, rather than port 443, which is HTTPS (and 443 is the default configuration). That incoming request will be redirected to port 8080 on your 프런트 엔드 풀 or 디렉터. By doing this, you won't need to make any certificate changes, because this traffic isn't using HTTPS for requests. But again, we don't recommend this, although it will work for you.

As indicated in our main 비즈니스용 Skype 서버 2015의 서버 요구 사항 article, you should have Windows Server 2012 or Windows Server 2012 R2 for your 비즈니스용 Skype 서버 environment. As a result, you should also have IIS 8 or IIS 8.5 for your mobility needs. There will need to be some changes to the default ASP.NET settings, but the 모바일 service installer will do that automatically.

If you're using a topology for 비즈니스용 Skype 서버 2015 that includes an HLB for your 프런트 엔드 풀 (which would be any topology that includes more than one 프런트 엔드 서버), the external 웹 서비스 virtual IPs (VIPs) for 웹 서비스 traffic need to be configured for source. Source affinity helps to ensure that multiple connections from a single client are sent to the same server to maintain session state.

If you plan to support 비즈니스용 Skype mobile clients only over your internal Wi-Fi network, you should configure your internal 웹 서비스 VIPs for source as described for external 웹 서비스 VIPs. In this situation, you should use source_addr (or TCP) affinity for the internal 웹 서비스 VIPs on the HLB.

For details on all this, please review the 비즈니스용 Skype의 부하 분산 요구 사항 documentation.

In order to support automatic discovery for 비즈니스용 Skype mobile clients, you'll need to update the current publishing rule as follows:

  • If you decide to update the SAN lists on your UNRESOLVED_TOKEN_VAL(reverseproxy_nocaps) certificates, and you're using HTTPS for the initial Autodiscover service request, you need to update the web publishing rule for lyncdiscover.<sipdomain>. This is typically combined with the publishing rul for the external 웹 서비스 URL on the 프런트 엔드 풀.

  • If you've decided to use HTTP for the initial Autodiscover service request to avoid having to update the SAN list for your UNRESOLVED_TOKEN_VAL(reverseproxy_nocaps) certificates (which we don't recommend), you'll need to create a new web publishing rule for port HTTP/TCP 80, if there isn't one already. If that rule exists, update it to include a lyncdiscover.<sipdomain> entry.

Now that we've reviewed the topologies, components and technical requirements, let's look at what your organization may need in terms of a 모바일 implementation.

We do strongly recommend that you do use automatic discovery. It will require the creation of new internal and external DNS records, as documented in the Technical Requirements section above. With automatic discovery, the 비즈니스용 Skype clients can automatically locate 비즈니스용 Skype 서버 2015 웹 서비스 from any location, without needing a URL to be entered in manually.

You can use manual settings if you need to. These URLs will need to be entered by users into their mobile devices:

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

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

Again, we do recommend using automatic discovery. You may find manual settings useful for troubleshooting purposes.

Push notifications are used for mobile applications that support this functionality to notify a user of events while the app's not active. Your 에지 서버 will need to have a federation relationship with your cloud-based 비즈니스용 Skype 서버 푸시 알림 서비스, which is found on the 비즈니스용 Skype 온라인 datacenter. You'll need to run a cmdlet to enable push notifications.

If you have anyone still using Lync Server 2010 clients, they will need TCP port 5223 open outbound on your enterprise WiFi network.

We have a table to help with some of the features that are available to all users, and whether they're set that way or not by default. For a complete list, please review New-CsMobilityPolicy.

The scopes for all these features are Global/Site/User.


FeatureParameter NameDescriptionDefault Setting

Enable Mobility


Controls users in a given scope who have 비즈니스용 Skype mobile client installed. If the policy is set to False, your users won't be able to sign in with their client.


Outside Voice


Enables a user's ability to use Call Via Work, which lets users send and receive calls by using their work number instead of their mobile number. If it's set to False, your users won't be able to make or receive calls on their mobile phone when using their work phone number.


Enable IP Audio and Video


Set to the default, it allows a user to use VoIP to make or receive phone or video calls on their mobile device. When set to False, your users won't be able to use their mobile device to do either of those things.


Require WiFi for IP Audio


Defines whether a client will need to make and receive calls over VoIP on WiFi instead of a cellular data network. If it's set to True, your users will only be able to make and receive VoIP calls when they're connected via WiFi.


Require WiFi for IP Video


Defines whether a client will need to make and receive video calls on WiFi instead of a cellular data network. If it's set to True, your users will only be able to make and receive VoIP calls when they're connected via WiFi.


For users to have access to 모바일 features and Call via Work, they need to be enabled for Enterprise Voice. But even if they aren't enabled, they can still join conferences by clicking on a link on their mobile device, but only 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 and applies to them.

Either way, the Voice policy you assign needs to have public switched telephone network (PSTN) usage records and routes that will define where your users will be able to dial out to join conferences.

Mobile users who want to use Click to Join require a Voice policy, along with the related PSTN usage records and voice routes, because when they click on that link on their mobile devices, an outbound call from 비즈니스용 Skype 서버 2015 will be the result.