Blog Post

Microsoft Teams Blog
2 MIN READ

Enable core Microsoft Teams calling functionality on compatible legacy SIP phones with SIP Gateway

Microsoft_Teams_team's avatar
Microsoft_Teams_team
Icon for Microsoft rankMicrosoft
Dec 06, 2021

While Microsoft Teams phone devices provide the richest and most complete Teams experience, we understand that there are many customers with existing investments in legacy devices. To help customers leverage their existing telephony hardware as they move to Teams Phone, we are excited to announce that SIP Gateway, a solution that enables core Teams calling functionality on compatible SIP phone models from Cisco, Poly, Yealink and AudioCodes is now generally available.

Cisco IP Phones with MPP firmware (6821, 7800 series, 8800 series), Polycom SIP phones (VVX series 100, 200, 300, 400, 500, 600 etc.), Yealink (T20 series, T30 series, T40 series, T50 series), AudioCodes 400 HD series.

 

Currently, SIP Gateway supports the following core Teams calling functionality

  • Inbound and outbound calls
  • Call transfer
  • Meeting dial-in and dial-out
  • Device-based “do not disturb”
  • Voicemail with message waiting indicator

There is no additional cost for organizations to use SIP Gateway, and any users meeting the following requirements can use SIP Gateway

  • Users must be licensed for Teams Phone (via any Office 365 E5, Microsoft 365 license that includes Teams Phone, or as a standalone license)
  • PSTN enablement (i.e., phone number assigned) via a Microsoft Teams Calling Plan, Direct Routing, or Operator Connect
  • Common area devices require a Common Area Phone license

Follow the steps below to enable and manage SIP Gateway

  • Turn on SIP devices can be used for calls calling policy in Teams admin center and go to SIP devices under Teams devices to manage your SIP phones connected to Teams
  • Reset devices to factory settings and point them to SIP Gateway provisioning server
  • Ensure that your firewall is open to traffic from Microsoft 365 and Teams
  • Ensure that SIP devices are not behind a proxy
  • Open UDP ports 49152 to 53247, and TCP port 5061 for IP range 52.112.0.0/14 to 52.120.0.0/14
  • Onboarded SIP devices are visible in Teams admin center SIP devices tab after first sign-in

Learn more about planning for and configuring SIP Gateway in your organization.

 

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

UPDATED October 17, 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 as soon as possible. Click here to learn more.


Upgrade to Teams phone devices

While SIP Gateway and 3PIP Gateway provide valuable flexibility for organizations with SIP phone investments, Teams phone devices provide the most complete Teams experience. Upgrade to Teams phone devices today!

Updated Oct 14, 2022
Version 5.0
Calling
microsoft teams
  • tratz1210's avatar
    tratz1210
    Brass Contributor
    Dec 06, 2021

    What is the feature code to provision a phone.  The document states 

    On the SIP device, dial the enrollment feature code followed by the verification code. For example, if the enrollment feature code is *55* and the verification code is 123456, dial *55*123456 to enroll the device.

     

    What is the enrollment feature code and how do i set it?

     

    --Tracy

  • AValenzuela's avatar
    AValenzuela
    Icon for Microsoft rankMicrosoft
    Dec 06, 2021

    Is there any information on multi-line registration on single SIP phones? 

     

    -Alex

  • ThomasBinder's avatar
    ThomasBinder
    Iron Contributor
    Dec 07, 2021
    Microsoft_Teams_team wrote:
    • Open UDP ports 49152 to 53247, and TCP port 5061 for IP range 52.112.0.0/14 to 52.120.0.0/14

     

     

    I'm surprised to learn that UDP ports except for 3478-3481 need to be open. Would you be able to clarify what the source/destination IPs and ports are to better understand how the ports need to be opened up?

  • Jonathan_Gould's avatar
    Jonathan_Gould
    Copper Contributor
    Mar 09, 2022

    We have hundreds of Audiocodes IP Phones, currently using SfB Gateway, which we'll need to work with SIP Gateway. From my testing so far with SIP Gateway and using the SIP Firmware I've found these major issues:

     

    1. I can't see anyway of hiding/disabling the Sign-Out key. We are a University and these phones are wall mounted in Student Halls, lecture rooms and labs. We cannot have them open to being signed-out.

     

    2. We can't stop MFA on these phones. After using the pairing code and signing-in with a user account with a CAP license, the sign-in process shows that the Gateway is in Netherlands (we are UK) so not an IP address in our domain so MFA is initiated. Obviously we cannot keep using MFA every time we need to sign-in to these phones.

     

    Any comments from Microsoft please?

    Thanks,

    Jon.

  • Peter Farrell's avatar
    Peter Farrell
    Copper Contributor
    Dec 07, 2021

    We’ve found that these 3PIP devices are not compliant with Ray Baum’s Act E911 requirements for providing a dispatchable location for emergency services. How are we supposed to remain compliant while using these on 3PIP or SIP gateway?

  • Robinv65's avatar
    Robinv65
    Copper Contributor
    Dec 07, 2021

    I would also like to know about the enrollment feature code. How to set it with a vvx 501?

  • Chandranshu's avatar
    Chandranshu
    Icon for Microsoft rankMicrosoft
    Dec 09, 2021

    tratz1210  Hi Tracy,

    Apologies for the confusion, we will also edit the document for clarity - the feature code is *55* as described in the doc. You cannot set it to something else. From the SIP phone you must dial the *55*<6 digit verification code generated in TAC for the device>. As the example states, if the verification code is 123456, then you will have to dial *55*123456 to enroll the device for remote sign-in. You will not need to perform the enrollment step if the device has been signed-in locally at least once. Hope this clarifies.

    Cheers,

    Chandranshu