Accessibility Skip to content
Article ID: 000063928
Last Modified Date: 08/08/2022
Access Level: Public

Using compatible Poly IP phones to sign into Microsoft Teams SIP Gateway

Our partner Microsoft released in December 2021 the ability to utilize > compatible< and > supported< Poly SIP phones with Microsoft Teams using the new SIP Gateway.
The Microsoft Teams SIP Gateway is for "Basic Calling Only"

To sign in a Poly VVX phone as an example we suggest to factory reset the unit prior to using it. In addition the DHCP Option can be utilized to automatically provision the phones to the Microsoft Server. The device needs to be in Generic Base Profile

1st Step is to ensure the Device(s) are already added to the Microsoft Team Admin Center (TAC) via Teams Devices > Phones


Add the MAC address


Phone Provisioning URL:
  • EMEA:
  • Americas:
  • APAC:
Log on to the Phone Web Interface and enter the URL manually :


Once this has been saved the phone will reboot a couple of times if the software is not on the desired version that our Partner Microsoft prefers:


Once the Phone has been provisioned via the Microsoft server the Phone will present the user with the Log in option:


Select the Sign In Button and the phone will present the Device Login Code:

Go to and enter the code and then the Email and Password of the account that is being used. Once the phone has rebooted again it is signed into the account:



Using a Phone like the Poly Trio 8800 cannot display the Code so another extra steps needs to be done in the TAC. In the Phones section select Actions on the Top Right and Select Provision devices and the Window where the MAC was added should be displayed. Simply select the phone in question and click on Generate verification code. The Code will be displayed.


On the Phone dial *55* verification code aka in our example *55*385977


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 to
  • Onboarded SIP devices are visible in Teams admin center SIP devices tab after first sign-in

IP Desk Phone Localization:

Set a SIP device's UI language

A SIP device can usually display information in many languages. Setting its UI language affects its interface, including softkeys and sign-in/sign-out system messages. Setting the UI language is done in the provisioning server, using DHCP server, or manually by appending a code string in the URL as in the following examples. How to set German for Polycom phones:

Supported languages

Language name Language code]
English (default) en
Spanish es
Japanese ja
German de
French fr
Portuguese pt
  • Japanese is partially supported by Polycom VVX.
  • The system defaults to English if the selected language is not supported by the SIP endpoint.
  • When the lang_xx parameter is not set via the provisioning URL, English is used as the default language.
  • If Sign in to make an emergency call text is not translated to other languages, an abbreviated version in English only will be presented on Press Sign In on the following IP phone models due to a screensize limitations:
    • Poly VVX 150, VVX 201
    • Voice mail softkey label is hardcoded with VM text across all languages for Poly VVX because of a limitation of string length.

Poly Rove IP DECT Base Station

Poly Rove DECT phones work in a similar way to the VVX Phones but do not have the Support of displaying the code on the Phone Screen.

In order for the phones to work with the Microsoft SIP Gateway ensure the Base and the Handsets are already running at least 8.0.3. Upgrade instructions can be found > here<
  • To obtain the IP address of the Rove web admin utility, on any Rove 30 or 40 handset, press more key and enter *47*    
  • Use your PC web browser to access the Rove base station web admin utility.
  • On the Rove web admin utility, select Handset Summary under DECT Wireless
  • To pair a handset, select a handset position and select register
  • On the handset to pair, go to settings and connectivity to initiate easy registration
  Base Station and Handset Firmware Update

To ensure the firmware is updated browse to System Management > Auto Provisioning > Auto Firmware Update and use the following:
FirmwarePath /voice/dect-ip-phones/Rove/
Method Periodically
Interval 30
  • System Management > Auto Provisioning > Firmware Version and Handset Image
  • Ensure the BaseFW and BranchFirmware is set for the Handsets and any Repeater being used (example initial Software to support the Microsoft SIP Gateway 8.0.3)
BaseFW BranchFirmware
8003 0010

  • Platform > Syslog will Display the Firmware status. Also the LED on the Base will flash fast during the firmware download
    loc2 .Info  2022-07-04T02:53:44.600Z 14 [ FWU Downloading File ]
    loc2 .Info  2022-07-04T02:53:52.600Z 14 [ FWU Downloading File ]
    loc2 .Info  2022-07-04T02:53:52.600Z 14 [ ROVE_30_v8003_b0009.fwu: Can't load, waiting for other FWU to finish ]
  • Status > System Status > System Status > FWUpdateStatus will show the statusRove_SIP_Gateway_22.png
Once the base is running at least 8.0. 3 go to  System Management > Auto Provisioning
  • Set Method to Periodically
  • Interval to 3600
  • Provisioning Option to Config URL
  • ConfigURL one of the 3 URL's

Sign into the Microsoft Teams Admin Center TAC and add an endpoint

Sign into Microsoft Teams Admin Center TAC and ADD an endpoint continued
  1. Note the IPEI of the handset you are onboarding
  2. In TAC, add a new provisioned device
  3. Enter a leading 00 and then the IPEI along with a descriptive location
    *note:  do not enter the mac of the base station.  Use the handset's IPEI pre-pended with 00
  4. Generate a verification code for the Rove
  1. On the handset, type *55*<Verification Code> generated in the previous step
  2. Hit Call or speakerphone to dial *55* using the Verification Code
  3. Listen for 3 busy signal tones and hang up

    If you refresh phones waiting for activation, the endpoint disappears
    The endpoint is now successfully paired to your tenant and located in the waiting for sign-in tab

Tac remote web sign-in
  1. Click on the rove handset and select sign-in user
  2. Wait for it to generate a web sign-in code
  3. Follow the normal web sign-in procedure
  4. Sign-in with the account you want on the Rove handset

Rove Screens and their different states  
  • Unpaired Handset
Use the Rove base station to pair the handset to the base
  • Onboard – Waiting for Pairing and Sign-in 
If this handset is not displayed in TAC, then you must create the endpoint in tac for remote sign-in
  • Main - Registered with Phone Number
Will be displayed in TAC as healthy.  You can choose to sign-out of the device in the device details in TAC.
  • Signed out
If this handset exist in TAC, complete remote sign-in on TAC