Plan for SIP Gateway
SIP Gateway lets your organization use any compatible SIP device with Microsoft Teams to preserve your investments in SIP devices. Now you can sign-in to Teams with your corporate credentials and make and receive calls with a compatible SIP device. Compatible devices can be Skype for Business IP phones with standard SIP firmware, Cisco IP phones with multiplatform SIP firmware, or SIP devices from vendors such as Poly, Yealink, and AudioCodes. To find out how to configure your SIP devices for SIP Gateway, see Configure SIP Gateway.
Benefits of SIP Gateway
SIP Gateway connects compatible SIP devices to Teams to help your users migrate seamlessly to Teams telephony. Using SIP Gateway, your users can do all of the following:
- Make calls: SIP device users can make calls to the Public Switched Telephone Network (PSTN), to other SIP devices, and to Teams and Skype for Business users. SIP device users can only call users who have phone numbers.
- Receive calls: SIP device users can receive a call from the PSTN, from Teams or Skype for Business users who have SIP devices, and from Teams and Skype for Business client applications. The SIP device acts as a Teams endpoint. Inbound calls will also be forked to the user's SIP device.
- Multiple simultaneous calls: A SIP device user in a call can put the call on hold to make or receive other calls. A SIP device user can also conference two calls.
- Hold/Resume and Mute/Unmute: A SIP device user can hold and resume or mute and unmute a call by using the features for those actions on the device.
- Voicemail: SIP device users can listen to electronically stored voice messages that callers leave for them.
- Message waiting indicator: SIP device users can receive notifications that alert them when they have new voicemail messages.
- Sign-in and sign-out: SIP devices users can sign in and sign out of Teams on the device.
- Dual-tone multi-frequency: SIP device users can press number keys to provide input during interactive voice response calls.
- Teams meetings: A SIP device user can join a Teams meeting by dialing the meeting access number. Meeting participants can add a SIP device user to the meeting by dialing out to user's phone number or simply adding a participant by clicking on 'Request to Join' will also alert the user's SIP device. Guest users from another organization can be added to a Teams meeting by a participant who dials out to a guest user's number to include that guest.
- Call transfers: SIP device users can transfer calls. SIP Gateway supports both blind and consultative transfers.
- Local call forwarding: A SIP device user can set forwarding rules (always, on timeout, and busy) for the device. If the device is connected to the SIP Gateway, then the call will be redirected to the target address based on the rule that the device user set. To make local call forwarding work, the admin must set the
AllowCallRedirect
attribute inSet-CsTeamsCallingPolicy
toEnabled
. - Offboard stale devices: SIP Gateway supports auto offboarding of stale devices provisioned for a tenant. Paired (signed-in) devices will be offboarded if not connected for 30 days, and unpaired (signed-out) devices after 14 days. An offboarded device can be re-onboarded after a factory reset.
- Set DND from SIP devices: You can use your SIP device for setting and fetching your Teams Do Not Disturb (DND) status. To set the DND status for your Teams account from your SIP device, dial the feature code *30* on the SIP device. To reset your Teams DND status, dial *31* from the SIP device. Dialing *31* clears the user-configured presence status, in this case DND.
- Call Queues and voice apps support: Customers can use SIP devices as call queue agents with some restrictions, for instance, SIP Gateway doesn't publish presence for devices hence presence based routing is not supported.
Requirements to use SIP Gateway
Teams users must have a phone number with PSTN calling enabled to use SIP Gateway.
Note
SIP Gateway is now available for government community cloud (GCC) environment. It is not yet available for GCC High and DoD.
Hardware, software, and licenses
If you have a 3PIP or SIP device, you must have the following:
- Microsoft Teams
- Skype for Business Online (Plan 2)
- Skype for Business Online (Plan 2) isn't a standalone license that can be purchased.
- Microsoft Phone System
- PSTN Connectivity
Compatible devices
Vendor | Model | Minimum firmware version | Approved firmware version | Remarks | Links |
---|---|---|---|---|---|
Cisco | Devices running enterprise firmware must be converted to multiplatform firmware. Read the guide at the right to learn how. | Cisco firmware conversion guide | |||
88321 | 11.3.5MPP | 11-3-7MPP | |||
68211 | 11.1.1MPP | 11-3-7MPP | |||
78111 | 11.1.1MPP | 11-3-7MPP | |||
78211 | 11.1.1MPP | 11-3-7MPP | |||
78411 | 11.1.1MPP | 11-3-7MPP | |||
78611 | 11.1.1MPP | 11-3-7MPP | |||
88111 | 11.1.1MPP | 11-3-7MPP | |||
88411 | 11.1.1MPP | 11-3-7MPP | |||
88451 | 11.1.1MPP | 11-3-7MPP | |||
88511 | 11.1.1MPP | 11-3-7MPP | |||
88611 | 11.1.1MPP | 11-3-7MPP | |||
88651 | 11.1.1MPP | 11-3-7MPP | |||
Poly | The device will auto-reboot and install the selected firmware. | ||||
Trio 8500 | 5.9.5.3182 | 7.2.2.1094 | |||
Trio 8800 | 5.9.5.3182 | 7.2.2.1094 | |||
VVX1501 | 5.9.5 | 6.3.1.8427 | |||
VVX2011 | 5.9.5 | 6.3.1.8427 | |||
VVX2501 | 5.9.5 | 6.3.1.8427 | |||
VVX300 | 5.9.5 | 5.9.7.3480 | |||
VVX3011 | 5.9.5 | 6.3.1.8427 | |||
VVX310 | 5.9.5 | 5.9.7.3480 | |||
VVX3111 | 5.9.5 | 6.3.1.8427 | |||
VVX3501 | 5.9.5 | 6.3.1.8427 | |||
VVX400 | 5.9.5 | 5.9.7.3480 | |||
VVX4011 | 5.9.5 | 6.3.1.8427 | |||
VVX410 | 5.9.5 | 5.9.7.3480 | |||
VVX4111 | 5.9.5 | 6.3.1.8427 | |||
VVX4501 | 5.9.5 | 6.3.1.8427 | |||
VVX500 | 5.9.5 | 5.9.7.3480 | |||
VVX5011 | 5.9.5 | 6.3.1.8427 | |||
VVX600 | 5.9.5 | 5.9.7.3480 | |||
VVX6011 | 5.9.5 | 6.3.1.8427 | |||
Rove B1 | 8.0.5.0002 | 8.0.5.0002 | |||
Rove B2 | 8.0.5.0002 | 8.0.5.0002 | |||
Rove B4 | 8.0.5.0002 | 8.0.5.0002 | |||
Rove 20 | 8.0.5.0003 | 8.0.5.0003 | |||
Rove 30 | 8.0.5.0002 | 8.0.5.0002 | |||
Rove 40 | 8.0.5.0002 | 8.0.5.0002 | |||
Yealink | Yealink support | ||||
T21P | 83 | 34.72.0.75 | |||
T21P_E2 | 83 | 52.84.0.125 | |||
T23G | 83 | 44.84.0.140 | |||
T27G1 | 83 | 69.86.0.15 | |||
T29G | 83 | 46.83.0.130 | |||
T301 | 83 | 124.86.0.40 | |||
T30P1 | 83 | 124.86.0.40 | |||
T31G1 | 83 | 124.86.0.40 | |||
T31P1 | 83 | 124.86.0.40 | |||
T33G1 | 83 | 124.86.0.40 | |||
T40G | 83 | 76.84.0.125 | |||
T40P | 83 | 54.84.0.125 | |||
T41P | 83 | 36.83.0.120 | |||
T41S1 | 83 | 66.86.5.1 | |||
T42G | 83 | 29.83.0.130 | |||
T42S1 | 83 | 66.86.5.1 | |||
T42U1 | 83 | 108.86.5.1 | |||
T43U1 | 83 | 108.86.5.1 | |||
T46G | 83 | 28.83.0.130 | |||
T46S1 | 83 | 66.86.5.1 | |||
T46U1 | 83 | 108.86.5.1 | |||
T48G | 83 | 35.83.0.130 | |||
T48S1 | 83 | 66.86.5.1 | |||
T48U1 | 83 | 108.86.5.1 | |||
T531 | 83 | 96.86.5.1 | |||
T53W1 | 83 | 96.86.5.1 | |||
T54W1 | 83 | 96.86.5.1 | |||
T57W1 | 83 | 96.86.5.1 | |||
W56H | 61.85.0.56 | ||||
W73H | 116.85.0.38 | ||||
W59R | 115.85.0.56 | ||||
W70B NOAM | 146.85.5.4 | ||||
W70B EMEA | 146.85.5.2 | ||||
W70B APAC | 146.85.5.3 | ||||
W80 NOAM | 130.85.5.5 | ||||
W80 EMEA | 130.85.5.6 | ||||
W80 APAC | 130.85.5.4 | ||||
W90 NOAM | 130.85.5.5 | ||||
W90 EMEA | 130.85.5.6 | ||||
W90 APAC | 130.85.5.4 | ||||
AudioCodes | Some AudioCodes SIP devices need a provisioning URL setting. Download and install upgrade files for the affected AudioCodes devices at the right. | Downloadable files for affected devices at AudioCodes | |||
4051 | 2.2.8 | 2.2.16.600 | |||
405HD1 | 3.2.1 | 2.2.16.600 | |||
405HDG1 | 3.2.1 | 2.2.16.600 | |||
420HD1 | 3.2.1 | 2.2.16.600 | |||
420HDG1 | 3.2.1 | 2.2.16.600 | |||
430HD1 | 3.2.1 | 2.2.16.600 | |||
430HDG1 | 3.2.1 | 2.2.16.600 | |||
440HD1 | 3.2.1 | 2.2.16.600 | |||
445HD1 | 3.2.1 | 3.4.6.717 | |||
445HDG1 | 3.2.1 | 3.4.6.717 | |||
450HD1 | 3.2.1 | 3.4.6.717 | |||
C450HD1 | 3.2.1 | 3.4.6.717 | |||
445HD1 | 3.2.1 | 3.4.6.717 | |||
RX501 | 3.2.1 | 3.4.6.717 | |||
Spectralink | Spectralink Support | ||||
7202 | PCS22B | PCS22B | Handset | ||
7212 | PCS22B | PCS22B | Handset | ||
7502 | PCS22B | PCS22B | Handset | ||
7522 | PCS22B | PCS22B | Handset | ||
7532 | PCS22B | PCS22B | Handset | ||
7622 | PCS22B | PCS22B | Handset | ||
7642 | PCS22B | PCS22B | Handset | ||
7722 | PCS22B | PCS22B | Handset | ||
7742 | PCS22B | PCS22B | Handset | ||
IP-DECT Server 200 | PCS22Ab | PCS22Ab | IP-DECT Server | ||
IP-DECT Server 400 | PCS22Ab | PCS22Ab | IP-DECT Server | ||
IP-DECT Server 6500 | PCS22Ab | PCS22Ab | IP-DECT Server | ||
Virtual IP-DECT Server One | PCS22Ab | PCS22Ab | IP-DECT Server | ||
IP-DECT Base Station | PCS22Ab | PCS22Ab | IP-DECT Server | ||
Ascom | Ascom Support | ||||
Ascom d43 | 2.11.4 | 3.0.8 | Handset | ||
Ascom d63 | 2.11.4 | 3.0.8 | Handset | ||
Ascom d81 | 4.13.1 | 4.17.3 | Handset | ||
Ascom d83 | 1.3.2 | 1.5.5 | Handset | ||
Ascom Myco 3 DECT | 3.4.1 | 3.4.1 | Wireless Handset | ||
IP-DECT Access Point IPBSx | 11.8.8 | 11.9.11 | IP-DECT Access Point | ||
IP-DECT Gateway IPBL | 11.8.8 | 11.9.11 | IP-DECT Gateway | ||
TDM Base Station | R3N | R4B | IP-DECT Base Station | ||
IP-DECT Virtual Appliance IPVM | 11.8.8 | 11.9.11 | IP-DECT Server | ||
Gigaset | Gigaset Support | ||||
N610 IP PRO | 2.52.0 | 2.52.0 | Base Station | ||
N670 IP PRO | 2.52.0 | 2.52.0 | Base Station | ||
N870 IP PRO | 2.52.0 | 2.52.0 | Base Station | ||
N870E IP PRO | 2.52.0 | 2.52.0 | Base Station | ||
N870 VI PRO | 2.52.0 | 2.52.0 | Base Station |
1 Device supports dynamic emergency calling (E911) with SIP Gateway.
Note
Customers can use AudioCodes OVOC and Poly Lens to manage device side configuration of their AudioCodes 400 series and Poly VVX/Trio devices respectively.
Note
Spectralink Handsets receive firmware updates over the air from Spectralink IP-DECT servers.
Note
Ascom Handsets receive firmware updates over the air from Ascom IP-DECT servers.
Note
Gigaset Handsets receive firmware updates over the air from Gigaset IP-DECT servers. All Gigaset PRO DECT Handset models are compatible with Microsoft Teams SIP Gateway.
Note
For Yealink DECT Base Stations, please use the appropriate region specific firmware version listed above for having the best calling experience.
Note
For support queries, customers using IP-DECT systems with Teams SIP Gateway should reach out to their DECT manufacturer or their implementation channel partners.
Note
For some devices, the minimum firmware version is greater than the approved firmware version. This is because the 3.X version is the Skype for Business version. We update the SIP version which is 2.X.
Feedback
Submit and view feedback for