Blog Post

Microsoft Teams Blog
3 MIN READ

Deadline approaching to migrate 3PIP phones to Microsoft Teams through SIP Gateway

Pete_Daderko's avatar
Pete_Daderko
Icon for Microsoft rankMicrosoft
May 08, 2023

Microsoft retired Skype for Business Online (SfBO) in July 2021, and the deadline to complete your SfBO upgrade/migration is rapidly approaching.

 

To help protect the investment that you have made in Skype for Business Online phones (3PIP phones) and help you upgrade to Teams, we 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 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.


How you can get help with your upgrading to SIP Gateway

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. There are several resources available to support you through the migration process.

  1. To help facilitate your migration, we have prepared a self-serve playbook to help you through the process step by step.
  2. We are also pleased to announce a Microsoft Teams ‘Ask Microsoft Anything’ (AMA) live event specific to maintaining your 3PIP Phone connectivity on Thursday, May 11. Similar to a “YamJam” on Yammer or an “Ask Me Anything” on Reddit, this AMA gives you the opportunity to connect with members of the product engineering team who will be on hand to answer your questions and listen to feedback.
  3. Reach out to us through your Microsoft account representatives or Support if you have any questions and stay tuned for more details.


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:

Updated Jun 01, 2023
Version 3.0
microsoft teams

6 Comments

  • SuryaThapar's avatar
    SuryaThapar
    Copper Contributor
    Aug 04, 2023

    VSurya28

    For Polycom VVX 411 phones. Below guidelines worked

     

    https://support.poly.com/support/s/article/Using-compatible-Poly-IP-phones-to-sign-into-Microsoft-Teams-SIP-Gateway

  • Vincent_Witzel's avatar
    Vincent_Witzel
    Copper Contributor
    Jul 25, 2023

    Update: we ended up fixing the boot looping issue with our phones by isolating the voice traffic on our network. Specifically, we created a separate VLAN on our firewalls for the voice traffic. It was a painful exercise. Hope this helps others!

  • VSURYA28's avatar
    VSURYA28
    Copper Contributor
    Jul 25, 2023

    Getting the same issue with  Poly VVX series.  It goes in rebooting loop. Also, multiple phones are not getting registered even after dialling the code that we get on Microsoft teams admin centre.  The deadline should be extended. 

  • Vincent_Witzel's avatar
    Vincent_Witzel
    Copper Contributor
    Jun 21, 2023

    Unfortunately, in our testing, the Yealink T46S phones went into a boot loop after the last step in the https://aka.ms/SIP-gateway-enablement-migration-playbook (slide 89/170). Specifically, after auto-provisioning the phone from their web UI using Microsoft's Americas URL (http://noam.ipp.sdg.teams.microsoft.com), the phones do the following:

     

    1. Download and install something.
    2. Boot up (their screen shows "Welcome...Initializing").
    3. The top left of the screen shows a gray phone symbol with the text, "No Service."
    4. The top left of the screen shows a green phone symbol.
    5. The colon of the clock stops blinking / freezes.
    6. The phone reboots.

    Doing some googling on the subject, we believe the issue is related to configuration in our switches which are used for PoE. I'll provide an update if we are able to resolve the issue.

  • Vincent_Witzel's avatar
    Vincent_Witzel
    Copper Contributor
    Jun 15, 2023

    A couple of questions:

     

    i) On the https://learn.microsoft.com/en-us/microsoftteams/sip-gateway-plan page, it states that the latest firmware supported for Yealink T46S phones is 66.86.5.1 and the minimum version is 83 (presumably, meaning 66.83.x.x). These versions appear to be specific to the non-Skype for Business (SfB) edition of the T46S (https://support.yealink.com/en/portal/docList?archiveType=document&productCode=95ef8c9dce7c98ba). The latest firmware version for the T46S SfB edition is 66.9.0.89 (https://support.yealink.com/en/portal/docList?archiveType=software&productCode=832014926eb01a2f). Can anyone confirm whether the SfB edition of the phone is supported, or is the suggestion that the non-SfB firmware be deployed on SfB phones?

    EDIT: After some testing, this does appear to be the suggestion (i.e., the non-SfB firmware needs to be deployed on the SfB device after the unlocked license is uploaded).

     

    ii) The https://aka.ms/SIP-gateway-enablement-migration-playbook alludes to licensing requirements being "An Office 365 License: A1/A3, E1/E3, F1/F3 or G1/G3 w/ Teams Phone Standard or A5/E5/G5." Does that mean that M365 licenses (e.g., M365 Business Premium) w/ Teams Phone Standard are not supported?
    EDIT: In our testing, the Yealink T46S phone worked with a M365 Business Premium and Teams Phone Standard license.