Microsoft Teams SIP Gateway - eGroup Enabling Technologies (2024)

Main Menu

What We Do
Who We Are
Customer Success
Events
Blog
Contact Us

Microsoft Teams SIP Gateway

Capital expenses for 1000’s of new IP phones has been a top contributor to delayed migrationsto newer phone systems, including Microsoft Teams.MicrosoftTeams now has the capability toconnect and utilize several legacy, non-native Microsoft IP Phones. This ispossible due therecent announcementof general availability for SIP Gateway.SIP Gateway is a 100%cloud-basedsolution, no infrastructure requiredand no additional cost.

Compatible Devices

SIP Gateway supportsCisco (with MPPfirmware), Polycom VVX,Yealink, and AudioCodes 400series.

If Cisco devices are using Enterprise firmware, they will be required toconvert toMultiplatform firmware. MPP firmware is not supported by Cisco Unified Communication Manager.

AudioCodes devices mayrequire an updateto have all available options(such as Provisioning URL)when configuringSIP Gateway.

Supported Features

At the GA release of SIP Gateway, the following features are supported. While it may not be an extensivelist or advanced feature, itdoes cover all basic calling requirements.

Make calls
Receive calls
Multiple simultaneous calls
Do not disturb
Hold/Resume
Mute/Unmute.
Voicemail
Message waiting indicator
Sign-in and sign-out
Teamsmeetings
Call transfers
Local call forwarding

Requirements

Devices are required to be at a minimum firmware version prior to onboarding
- Common area devices can utilize Common Area Phone licensesPhone System licenses.
- Users can have either E5 or standalone license
PSTN connectivity via Calling Plan, Direct Routing, or Operator Connect.
Factory reset required for all devices
Networking:
- Access to Microsoft 365 and Teams trafficOffice 365 URLs and IP address ranges.Also,the following HTTPS endpoints
- 13.75.175.145
- 52.189.219.201
- 51.124.34.164
- 13.74.250.91
- 13.83.55.36
- https://httpblobsdgemea.blob.core.windows.net
- https://httpblobsdgnoam.blob.core.windows.net
- No HTTP/S proxy allowed
- UDP Port range 49152 to 53247
- TCP port 5061 for IP ranges52.112.0.0/14 to 52.120.0.0/14

Initial Setup

There is a small amount of administrative setup to SIP Gateway, three simple steps.

Verify SIP Gateway is available in your tenant

2. Enable users touse SIP Gateway via Teams Calling Policies. Two methods:

a.) Teams Admin Center (Voice > Calling policies)

b.) PowerShell

Set-CsTeamsCallingPolicy-IdentityGlobal–AllowSIPDevicesCalling$true

3. ConfigureSIP GatewayProvisioning Server URL

Which URL you use depends onyour region. There are three choices.

EMEA: http://emea.ipp.sdg.teams.microsoft.com

Americas: http://noam.ipp.sdg.teams.microsoft.com

APAC: http://apac.ipp.sdg.teams.microsoft.com

Preferably, you would configure DHCP Scope options to push this URL administratively to devices, otherwise you can setup this provisioning URL manually per device.

For Yealink phones, use option 66.
For Cisco, Poly, andAudioCodephones, use option 160.
For Cisco devices, append /$PSN.xml to the provisioning server URL.

Pre-Provision Devices

For better onboarding control, you can addyourdevices to the Teams Admin Center in advance, one at a time or in bulk. In the Teams Admin Center > Devices > SIP Devices, select Actions > Provision devices in the top right corner.

You need twoattributes to pre-provision devices, MACIdand Location. You can add this manually one at a time or use a CSV file to upload in bulk. Once uploaded,you will need to select each device to generate a verification code. This is used on the device to activate it.Once activated, you can go back to the Teams Admin Center Provision Devices page and selectwaiting for sign in.You can use this page to initiate sign in of each deviceusing the Web Sign in method and device code.

End User Experience

After provisioning server is set, the phone will reboot andwill either upgrade or downgrade the firmware to the Microsoft approved version respectively for each device model. After this has processed, you will see a simple interface with the Teams icon and a Sign in option. This sign in process usesMicrosoftdeviceauthenticationweb sign in (https://microsoft.com/devicelogin). Go to this site with any browser, enter the code, and sign in with your account.Once complete, the phone may or may not restart, but once it is ready you will be able to make and receive calls on this device.

Boot Up and Sign-In Page

Making a call

Additional Notes

These are some additional comments to consider when implementing SIP Gateway.

SIP Gateway only supports IPv4
You can assign tags to devices
You can restart or sign out of a device from the Teams Admin Center
Sign in is only possible locally on the device
Default language can be changed by appending a language code (i.e.lang_en) to the end of the provisioning serverURL
Policy changes sync once an hour
AllowCallRedirectattribute in Teams Calling Policy must be set to enabled
Static 911 calling only, no support for dynamic 911 calling
You can view each device status as well as restart, sign out, or check for updates all from the Teams Admin Center.