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

[SteffenBaierUK]

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"

EDIT: Easy Poly Lens Assisted Provisioning >here < to have additional control

To sign in a Poly VVX phone as an example we suggest a 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

Provision devices

Add the MAC address

 

Phone Provisioning URL:

• EMEA: http://emea.ipp.sdg.teams.microsoft.com
• Americas: http://noam.ipp.sdg.teams.microsoft.com
• APAC: http://apac.ipp.sdg.teams.microsoft.com

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 https://microsoft.com/devicelogin 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 Poly Trio or other phones who cannot use the phones Microbrowser

Using a Phone like the Poly Trio 8800 cannot display the Code so another extra step 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

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 Poly handset
   

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. Official detailed guide >here <

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:

FirmwareServer	http://downloads.poly.com
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.8)

BaseFWVersion	8008
BranchFWBranch	0001
Rove20FwVersion	8008
Rove20BranchVersion	0001
Rove30FwVersion	8008
RoveB30branchVersion	0001
Rove40FwVersion	8008
Rove40branchVersion	0001
RoveR8FwVersion	8008
RoveR8BranchVersion	0001

• 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 http://downloads.polycom.com/voice/dect-ip-phones/Rove/ROVE_B2_v8003_b0009.fwu ]
  loc2 .Info  2022-07-04T02:53:52.600Z 14 [ FWU Downloading File http://downloads.polycom.com/voice/dect-ip-phones/Rove/ROVE_30_v8003_b0009.fwu ]
  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 status
  

• Once the base is running at least 8.0.8 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
    URL:
    • http://noam.ipp.sdg.teams.microsoft.com/00${IPEI}.cfg
    • http://emea.ipp.sdg.teams.microsoft.com/00${IPEI}.cfg
    • http://apac.ipp.sdg.teams.microsoft.com/00${IPEI}.cfg
  • Sign into the Microsoft Teams Admin Center TAC and add an endpoint
    
    
  • Sign into Microsoft Teams Admin Center TAC and ADD an endpoint continued
    Note the IPEI of the handset you are onboarding
    
  • In TAC, add a new provisioned device
    
    
    
  • 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
    
  • Generate a verification code for the Rove
    
  • On the handset, type *55*<Verification Code> generated in the previous step
    Hit Call or speakerphone to dial *55* using the Verification Code
    
  • 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 exists in TAC, complete remote sign-in on TAC

Overview

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

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:

• http://emea.ipp.sdg.teams.microsoft.com/lang_de

Supported languages

SUPPORTED LANGUAGES

Language name	Language code]
English (default)	en
Spanish	es
Japanese	ja
German	de
French	fr
Portuguese	pt

 Note

• 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.

ROOT CAUSE

IP Desk Phone Troubleshooting:

• Phone not connecting to Microsoft Server or not downloading Software or not displaying Microsoft Teams Background Picture

Please check our partner Microsoft’s list of officially >supported< Poly IP phones as the User-Agent gets checked when trying to provision so an unsupported model will not be able to provision.
or
Change the Logging to the following:

Settings > Logging > Module Log Level Limits > CURL > Event 3
Settings > Logging > Module Log Level Limits > Copy Utilities > Event 1

Reboot the Phone and then check the logs (Diagnostics > View & Download Logs) as it should show the phone connecting to our Partner Microsoft and a Firewall may block access
 

• Phone not signing into Microsoft Teams after the customer has added the displayed code via https://microsoft.com/devicelogin

Check that these requirements are met:

• Users must be licensed for Teams Phone (via Office 365 E5, Microsoft 365 E5 or 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

Rove IP DECT Troubleshooting:

Caveats

• Re-onboarding a handset will generate a new device ID
• Teams Admin Center has no ability to delete endpoints.  They purge stale endpoints over time.
• You can sign into multiple devices using the same account
• Onboarding tone will be a busy tone while on VVX it’s a chime.
• Do not set config sync interval to quickly like 30 seconds, all your phones might sign out.   Set the config sync interval no lower than 3600 sec. 

How to re-onboard

There are 3 ways to re-onboard if the phone will not onboard or generate a web sign-in code.  This will re-generate the device ID.

1. Clear the handsetURL by setting the default checkbox and you want to re-onboard the handset.  
   
2. Un-pair and Re-pair the handset will cause an immediate re-onboarding of just the one handset without causing a power cycle of the entire base station with other active handsets.
3. Factory reset the base and re-onboard to Microsoft Teams SIP gateway.  This would be the most severe way to re-onboard and should be avoided in a production environment.

Enable SIP Troubleshooting

To enable SIP debug logging, select common settings and under the SIP section, set Service Providers > Common Settings > SIP > X-SIPDebugOptions to Log all messages.  This will display extended SIP logging to the web admin console and Syslog if enabled.   The admin console has a limited log buffer.

Quickly Viewing SIP Log in the web admin via Platform > SIP Log

Configuring >syslog < server via System Management > Device Admin > Syslog