Plan Cloud PBX with on-premises PSTN connectivity in Skype for Business Server 2015 or Lync Server 2013

Skype for Business Server 2015

마지막으로 수정된 항목: 2017-05-04

Learn about the planning considerations for UNRESOLVED_TOKEN_VAL(CloudPBX_PSTN_onprem).

This content is relevant if you already have 비즈니스용 Skype 서버 or Lync Server 2013 deployed on-premises. For other scenarios, see Plan your Cloud PBX solution in Skype for Business.

Cloud PBX with on-premises PSTN connectivity is a new offering that enables you to leverage Cloud PBX capabilities for your users. This can help with the following scenarios:

  • You have some of your 비즈니스용 Skype users homed on-premises and others homed in 비즈니스용 Skype 온라인. You can now enable Cloud PBX capabilities and features for your users homed in 비즈니스용 Skype 온라인, but continue to use on-premises PSTN connectivity.

  • You have an on-premises deployment and you want to move some or all of your users to 비즈니스용 Skype 온라인 but continue to use on-premises PSTN connectivity.

    To successfully enable users for UNRESOLVED_TOKEN_VAL(CloudPBX_PSTN_onprem), their SIP address must be in your own domain. The use of the default domain for Office 365,, is not supported.

To learn more about Cloud PBX including licensing and plans, see PSTN Calling plans for Skype for Business.

UNRESOLVED_TOKEN_VAL(HybridVoice) does not offer the same feature set as a fully on-premises Enterprise Voice solution. To help you decide whether UNRESOLVED_TOKEN_VAL(HybridVoice) will provide the right feature set for your organization, see Here's what you get with Cloud PBX.

  • Lync Phone Edition devices MUST be updated to minimum required firmware in your on premises environment PRIOR to moving to Skype for Business Online.

  • If you move your users from on-premises to online prior to updating the firmware, users will be unable to connect using their phones. To correct this problem, users must be moved back to the on premises environment to have their phones updated to the minimum firmware. DO NOT ATTEMPT TO UPDATE TO MINIMUM FIRMWARE OR HARD RESET THE PHONE PRIOR TO MOVING THE USER BACK TO YOUR ON PREMISES ENVIRONMENT.

  • If a hard reset is performed while the device is not at minimum firmware it will default to using PIN Authentication, which is not supported in Skype for Business Online.

For more information, please refer to Getting phones for Skype for Business Online.

By deploying UNRESOLVED_TOKEN_VAL(CloudPBX_PSTN_onprem), you can move your users to the cloud via 비즈니스용 Skype 온라인 at your own pace, while retaining their on-premises PSTN connectivity. If you have a PBX, you continue to use it to provide PSTN connectivity for the users you move to the cloud. Once a user is moved to 비즈니스용 Skype 온라인 and the Cloud PBX, their legacy PBX phone will no longer work, but their phone number will route to any of the 비즈니스용 Skype clients for PCs or Smart phones as well as 비즈니스용 Skype-compliant desk phones. Once ported, Cloud PBX users and legacy PBX users can call each other normally as well as make/receive PSTN calls using their normal phone number.

You may have a custom feature or a major add-on to your legacy PBX, such as a call center. If the custom feature is not currently available on Microsoft’s Cloud PBX, you should leave those users that require that custom feature on-premises with the legacy PBX, and just port the users who do not need to access the custom feature to UNRESOLVED_TOKEN_VAL(HybridVoice).

For a list of legacy PBXs that interoperate directly with 비즈니스용 Skype 서버 2015 see Infrastructure Qualified for Microsoft Lync. If your PBX is not on this list, you can use a Session Border Controller to connect your PBX with the Cloud PBX in 비즈니스용 Skype 온라인.

When deploying a cloud-hosted service like UNRESOLVED_TOKEN_VAL(CloudPBX_PSTN_onprem), you must keep the following in mind. In a purely on-premise 비즈니스용 Skype 서버 2015 Enterprise Voice deployment, all the infrastructure and clients are on the enterprise’s own network. The quality and performance of this network, which is critical for high-quality audio and video, are under the direct control of the enterprise staff. With UNRESOLVED_TOKEN_VAL(CloudPBX_PSTN_onprem) there are three networks involved, two of which the customer is responsible for but only one of which the enterprise staff has direct control over:

  • Microsoft’s Global Media Delivery Network Microsoft’s global cloud network and infrastructure. Office 365 and Cloud PBX servers and traffic traverse this network.

  • Enterprise/Cloud PSTN Interconnect This is the network that connects your enterprise to the Office 365 cloud. This is not necessarily the same as your generic Internet connection.

  • Your enterprise's own network The quality of the real-time media is heavily dependent on your own network: especially the WiFi network and the quality of the interconnect used to reach the Office 365 cloud.

For more information on tuning performance in 비즈니스용 Skype 온라인, see Tune Skype for Business Online performance.

Before you can configure UNRESOLVED_TOKEN_VAL(CloudPBX_PSTN_onprem) and move users to 비즈니스용 Skype 온라인, you must confirm that you have the following prerequisites in place:

  • On-premises server versions. The versions of the servers in your on-premises deployment must be listed in the following table to support UNRESOLVED_TOKEN_VAL(CloudPBX_PSTN_onprem).


    Server roleSupported versions*

    Federation Edge**

    Skype for Business Server 2015

    Next Hop Federation Route Internal Pool Server

    Skype for Business Server 2015, March 2016 Cumulative Update 6.0.9319.235 or higher (Front End or Director)

    Front End User Server

    비즈니스용 Skype 서버 2015

    Lync Server 2013

    에지 서버

    비즈니스용 Skype 서버 2015

    중재 서버

    비즈니스용 Skype 서버 2015

    Lync Server 2013

    *Minimum supported versions are:

    • Skype for Business Server 2015, March 2016 Cumulative Update 6.0.9319.235

    • Lync Server 2013 July 2015 Cumulative Update 5.0.8308.920

    **The federation route for all supported SIP domains must route through the Skype for Business Server 2015 Edge Server running the March 2016 or higher Cumulative Update. If the user pool is on Lync Server 2013, that external pool traffic remains on Lync Server 2013 Edge Server.

  • On-premises Enterprise Voice is configured and tested for on-premises users This includes PSTN connectivity components. For more information, see the following topics if you are using 비즈니스용 Skype 서버 2015, see: 비즈니스용 Skype 서버 2015의 Enterprise Voice 계획 and Deploy Enterprise Voice in Skype for Business Server 2015.

    If you are using Lync Server 2013, see: Planning for Enterprise Voice in Lync Server 2013, and Deploying Enterprise Voice in Lync Server 2013.

  • Active Directory synchronization You must configure Active Directory synchronization using Azure AD Connect. For more information, see Managing Azure AD Connect.

    The version of AAD Connect you use must be version 1.0.9125.0 or later. If you are using an earlier version of AAD Connect tools or DirSync, please upgrade to the supported version. You can upgrade your current installation and maintain any custom rules you have defined in your environment.
  • Configure your hybrid deployment No matter whether all your 비즈니스용 Skype users are currently homed either online or on-premises, or if you currently have a mix, you must have done the steps to configure a hybrid deployment of 비즈니스용 Skype 서버 or Lync Server 2013, as outlined in Deploy hybrid connectivity between Skype for Business Server and Skype for Business Online. For more background information on hybrid deployments, see Plan hybrid connectivity between Skype for Business Server and Skype for Business Online.

    If you are using Lync Server 2013, see Lync Server 2013 hybrid.

  • (Recommended) Active Directory Federation Services (AD FS) We recommend deploying AD FS to support Single Sign-on. For more information, see Active Directory Federation Services (AD FS).

For deployment of Cloud PBX, see Deploy Cloud PBX with on-premises PSTN connectivity in Skype for Business Server 2015 or Lync Server 2013.