Blog Post

Microsoft Teams Blog
3 MIN READ

Upgrade Skype for Business Online (3PIP) phones to Microsoft Teams using SIP Gateway

Pete_Daderko's avatar
Pete_Daderko
Icon for Microsoft rankMicrosoft
Oct 06, 2022

Microsoft retired Skype for Business Online (SfBO) in July 2021. To help protect the investment that you have made in Skype for Business Online phones (3PIP phones) and help you upgrade to Teams, we now offer a solution through SIP Gateway to enable these devices to securely connect and function as Microsoft Teams endpoints. We encourage you to make necessary updates (detailed later in this blog) as soon as possible because Skype for Business Online will be permanently turned off on July 31, 2023.

 

The following are a few scenarios that can help you chart the course of action for your organization:

  1. ​You have compatible 3PIP devices connecting to Teams via SIP Gateway on July 31, 2023 – no action needed on your part, your phones will continue to work via SIP Gateway.
  2. You have compatible 3PIP devices connecting to Teams, but not through Teams SIP Gateway on July 31, 2023 – your phones will stop working, unless you take steps described below to upgrade your devices to connect to Teams through SIP Gateway.
  3. You have incompatible 3PIP devices connecting to Teams on July 31, 2023 – your devices will stop working, you must replace them with Teams phone devices or compatible Teams SIP devices for continued scenario support.

When should you get started?

SIP Gateway is the recommended approach for customers to continue using 3PIP phones to connect and work with Teams.  We recognize that the upgrade of 3PIP devices to SIP Gateway can be lengthy, and so we highly encourage beginning the process as soon as possible.

 

What is SIP Gateway?

SIP Gateway enables customers to use compatible 3rd-party devices with Teams and leverage the following core Teams calling features:

  • Incoming and outgoing calls with hold/resume and transfer
  • Call forwarding
  • Dial-in to and dial-out from meetings
  • In-a-call presence and “Do not disturb” settings on devices
  • Dynamic E911 support on select SIP Gateway compatible devices
  • Voicemail and message waiting indicator

SIP Gateway is available with your Teams Phone Standard license with PSTN enabled.

 

Why should you upgrade to SIP Gateway?

With SIP Gateway you can continue using your devices with Teams through a more secure, future ready core telephony platform. SIP Gateway provides the following benefits:

  1. Added security: Upgrade to SIP Gateway for a more secure experience for your phone devices with Teams.
  2. Future ready core telephony platform: SIP Gateway will invest in scenarios that are not available for 3PIP phones today.
  3. Join Teams Meetings on SIP Devices: Users can attend Teams meetings from SIP devices, and meetings attendees can invite a SIP device to the meeting.
  4. Manage multiple concurrent calls: Make concurrent calls, receive calls by placing calls on hold, or combine calls into one call.

What is the process to upgrade devices to SIP Gateway?

Your administrator needs to take the following steps:

1. Provision your devices with SIP Gateway

a. For an AudioCodes 3PIP Device

i. Onboard your AudioCodes 400 HD series devices to OVOC and AudioCodes Device Manager

ii. Setup AudioCodes OVOC account if you don’t have one already

iii. Configure the SIP Gateway provisioning URL in Device Manager – Get more information on how to set up the device management tool here

iv. Upgrade the phone firmware version to the minimum supported firmware (or higher) for SIP Gateway

v. In the Monitor Page, under Actions menu, select More, and then select SET as TEAMS SIP Gateway

b. For a Poly 3PIP Devices

i. Onboard (redirect) your Poly VVX and/or Poly Trio devices to Poly Lens from RPRM/PDMS-E or through DHCP server reconfiguration

ii. Setup Lens Account if you don’t have one already

iii. Upgrade the phone firmware version to the approved firmware for SIP Gateway. For more details on the approved firmware version go here.

iv. Remotely reset the devices from Lens

v. Create Phone Policy with SIP Gateway Provisioning enabled and select the SIP Gateway region you want to provision your devices to

c. For a Yealink Device

i. Reset your 3PIP Yealink T40 series devices to factory settings

ii. Redirect your devices to SIP Gateway provisioning server through DHCP server reconfiguration

2, Configure SIP Gateway for your organization

3. Activate your devices to use SIP Gateway. For more information on how to activate your devices go here.

a. Sign-in to the device locally or

b. Enroll device for remote sign in from Teams admin center

 

Reach out to us through your Microsoft account representatives or Support if you have any questions and stay tuned for more details.

Updated Oct 13, 2022
Version 2.0
  • Korbyn's avatar
    Korbyn
    Brass Contributor

    Semi related question, assume SFBO is completely shut down July 31, 2023, will that mean any tenant still in a Teams coexistence/Islands Mode is going to automatically be switched to TeamsOnly, regardless of how far into a migration from Skype a customer might be?  Shutting down SFBO as stated seems to imply this but I can find no statement or commitment to this idea, if its in fact true or not...

  • dailyvmtech's avatar
    dailyvmtech
    Copper Contributor

    Hello Pete, 

    Thanks for sharing these details, much appreciated. Been facing  the same issue for quite some time now, it work intermediately on some users, on same model of different model; vvx 300, vvx400 and vvx500. All are giving same issue. 

     

    I have brought AudioCode handset and found it work perfectly fine and it doesn't give any disconnection symptoms. 

    Tried different firmware, 6.xxxx, 5.9, 5.8 It worked for sometime, after that when the calls droped it will trigger the errors; 

    IceConnectivityChecksFailed
    Q.850;cause=16
    Forbidden
    Temporarily Unavailable
    IceConnectivityChecksFailed
    Busy Here
    Service Unavailable
    EstablishmentTimeout
    Server Internal Error

     

    Logged a case with microsoft and they confirmed, its from their side; 

     

    After consulting with our back-end team, this issue was identified as known issue for poly device. We have as well attached this case to the previously known issues already under investigation and forwarded your request to the engineering team to consider a one-time fix in the future regarding to call dropping. Our internal team advised that currently there are a lot of issue regarding to poly devices so our internal teams is working to fix those issue. Unfortunately, no ETA was provided. 
    
    We will continue to keep an eye on this issue internally and work together with them on priority till the fix this issue. We will update you as soon as we receive any updates from the product team side. 
    In the meantime, we will suggest user to use normal team's desktop apps as a workaround. 

     

    Any workaround, as the business is heavily impacted, and ordering a new phones will take ages to arrive. 

     

    Regards

     

  • Ryan Steele's avatar
    Ryan Steele
    Bronze Contributor

    WARNING: Migrating a Poly device using Poly Lens may not work as expected.

     

    Scenario: You have configured DHCP Options on your Voice VLAN to enroll Poly devices in Poly Lens. You have a device managed in Poly Lens that is currently configured in Skype for Business mode and has a user signed in. You are attempting to re-configure the device to sign into the Microsoft Teams SIP Gateway. You assign a policy with the Lens Assisted Provisioning Feature under Integrations > Microsoft Teams > SIP Gateway enabled and initiate a Factory Reset from the Device page to remove all existing local configuration settings.

     

    Expected result: After the factory reset completes and the device receives its new policy, it is provisioned for the Teams SIP Gateway and can be successfully signed in. 

     

    Actual result: In addition to the Teams SIP Gateway settings, Poly Lens re-applies a backup of local device settings that pertain specifically to the 3PIP gateway. These settings prevent the device from signing into the Teams SIP Gateway. These settings can be viewed from the This Device Tab as documented here.

     

    Workaround: Immediately after initiating the Factory Reset, delete the existing entry for the device in Poly Lens. Once the device boots back up and is directed to re-enroll in Poly Lens by the DHCP Option, find the new device entry, assign the Lens Assisted Provisioning Feature policy and initiate a device reboot.

     

    I hope this helps someone avoid several frustrating days of troubleshooting and an embarrassing email to a Microsoft Support rep explaining that the issue wasn't on their end after all.

  • Discover Your Existing Deployed 3PIP Devices

    To identify existing 3PIP devices deployed within your environment, the sign in logs contained within the Azure AD Admin Center can be leveraged to identify recent sign registration events by filtering on "Skype for Business Certified Phone," as shown below:

     

     

    3PIP Discovery PowerBI Template

    As an additional option to identify remaining active 3PIP devices deployed across your environment, a new PowerBI template has been released leveraging latest media session details (via Call Quality Dashboard) to further summarize locations where 3PIP devices may remain for migration: