Thinking of moving to Teams Phone? You may already have a great handset you can re-use

Poly Rove and Polycom VVX500 Handsets. Yes, that’s one of the lab phone numbers.


Many, many orgs are making the move to Teams Phone – making and receiving PSTN calls from your Teams client running on your desktop, laptop, meeting room or mobile device.

It makes sense too – having your desk number come with you no matter where you are in the world (hello beach calls!) rather than having it tie you to your desk makes perfect sense. Want to work from home today? No problem – your desk number comes with you.

What about those desk phones your org invested in a few years ago though? Don’t send them to e-waste just yet – they may make an excellent Teams phone device.


Do all SIP handsets work with Teams?

Not all, but a vast array of very popular pre-Teams handsets (like the Poly VVX range, and a bunch of CISCO, Yealink and others) support calling in Teams.

Here’s the current list (taken from: https://learn.microsoft.com/en-us/microsoftteams/sip-gateway-plan#compatible-devices):

VendorModelMinimum firmware versionApproved firmware versionRemarksLinks
CiscoDevices running enterprise firmware must be converted to multiplatform firmware. Read the guide at the right to learn how.Cisco firmware conversion guide
8832111.3.5MPP11-3-7MPP
6821111.1.1MPP11-3-7MPP
7811111.1.1MPP11-3-7MPP
7821111.1.1MPP11-3-7MPP
7841111.1.1MPP11-3-7MPP
7861111.1.1MPP11-3-7MPP
8811111.1.1MPP11-3-7MPP
8841111.1.1MPP11-3-7MPP
8845111.1.1MPP11-3-7MPP
8851111.1.1MPP11-3-7MPP
8861111.1.1MPP11-3-7MPP
8865111.1.1MPP11-3-7MPP
PolyThe device will auto-reboot and install the selected firmware.
Trio 85005.9.5.31827.2.2.1094
Trio 88005.9.5.31827.2.2.1094
VVX15015.9.56.3.1.8427
VVX20115.9.56.3.1.8427
VVX25015.9.56.3.1.8427
VVX3005.9.55.9.7.3480
VVX30115.9.56.3.1.8427
VVX3105.9.55.9.7.3480
VVX31115.9.56.3.1.8427
VVX35015.9.56.3.1.8427
VVX4005.9.55.9.7.3480
VVX40115.9.56.3.1.8427
VVX4105.9.55.9.7.3480
VVX41115.9.56.3.1.8427
VVX45015.9.56.3.1.8427
VVX5005.9.55.9.7.3480
VVX50115.9.56.3.1.8427
VVX6005.9.55.9.7.3480
VVX60115.9.56.3.1.8427
Rove B28.0.3.00108.0.3.0010
Rove B48.0.3.00108.0.3.0010
Rove 308.0.3.00108.0.3.0010
Rove 408.0.3.00108.0.3.0010
YealinkYealink support
T21P8334.72.0.75
T21P_E28352.84.0.125
T23G8344.84.0.140
T27G18369.86.0.15
T29G8346.83.0.130
T30183124.86.0.40
T30P183124.86.0.40
T31G183124.86.0.40
T31P183124.86.0.40
T33G183124.86.0.40
T40G8376.84.0.125
T40P8354.84.0.125
T41P8336.83.0.120
T41S18366.86.5.1
T42G8329.83.0.130
T42S18366.86.5.1
T42U183108.86.5.1
T43U183108.86.5.1
T46G8328.83.0.130
T46S18366.86.5.1
T46U183108.86.5.1
T48G8335.83.0.130
T48S18366.86.5.1
T48U183108.86.5.1
T5318396.86.5.1
T53W18396.86.5.1
T54W18396.86.5.1
T57W18396.86.5.1
W56H61.85.0.56
W73H116.85.0.38
W59R115.85.0.56
W70B NOAM146.85.5.4
W70B EMEA146.85.5.2
W70B APAC146.85.5.3
W80 NOAM130.85.5.5
W80 EMEA130.85.5.6
W80 APAC130.85.5.4
W90 NOAM130.85.5.5
W90 EMEA130.85.5.6
W90 APAC130.85.5.4
AudioCodesSome 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
40512.2.82.2.16.589
405HD13.2.12.2.16.589
405HDG13.2.12.2.16.589
420HD13.2.12.2.16.589
420HDG13.2.12.2.16.589
430HD13.2.12.2.16.589
430HDG13.2.12.2.16.589
440HD13.2.12.2.16.589
445HD13.2.13.4.6.704
445HDG13.2.13.4.6.704
450HD13.2.13.4.6.704
C450HD13.2.13.4.6.704
445HD13.2.13.4.6.704
RX5013.2.13.4.6.704
SpectralinkSpectralink Support
7202PCS22BPCS22BHandset
7212PCS22BPCS22BHandset
7502PCS22BPCS22BHandset
7522PCS22BPCS22BHandset
7532PCS22BPCS22BHandset
7622PCS22BPCS22BHandset
7642PCS22BPCS22BHandset
7722PCS22BPCS22BHandset
7742PCS22BPCS22BHandset
IP-DECT Server 200PCS22AbPCS22AbIP-DECT Server
IP-DECT Server 400PCS22AbPCS22AbIP-DECT Server
IP-DECT Server 6500PCS22AbPCS22AbIP-DECT Server
Virtual IP-DECT Server OnePCS22AbPCS22AbIP-DECT Server
IP-DECT Base StationPCS22AbPCS22AbIP-DECT Server
AscomAscom Support
Ascom d432.11.42.11.4Handset
Ascom d632.11.42.11.4Handset
Ascom d814.13.14.13.1Handset
Ascom d834.13.14.13.1Handset
Ascom Myco 3 DECT3.4.13.4.1Handset
IP-DECT Access Point IPBSx11.8.811.8.8IP-DECT Access Point
IP-DECT Gateway IPBL11.8.811.8.8IP-DECT Gateway
TDM Base StationR3NR3NIP-DECT Base Station
IP-DECT Virtual Appliance IPVM11.8.811.8.8IP-DECT Serve


How do I get my phones working with Teams?

In short, you:

  • Ensure the firmware is up to date on the phone (you could push this out via your existing phone management platform, or manually update each phone)
  • Configure the SIP Gateway provisioning server for your region. You can do this via DHCP options, or configure each phone manually
  • Add the phones MAC address to the Teams Admin Center (TAC) under SIP Devices > Provision
  • Generate an activation code for each handset in the portal
  • Enter *55* followed by the activation code on each handset to provision them in the TAC
  • Sign the phone in (either remotely from the TAC, or by reading the code off the handset and logging in at microsoft.com/devicelogin).

We have the full steps documented here: Configure SIP Gateway – Microsoft Teams | Microsoft Learn

Poly VVX 500 showing a new voicemail message is waiting, along with a missed call.


What’s the experience like?

You know how your VVX handset worked with Skype For Business? Guess what, It works exactly the same way.

You can:

  • Make and receive calls from the PSTN/Other Teams users
  • Receive voicemails (and set a custom voicemail message)
  • Answer call queue calls and calls transferred from auto attendants
  • Transfer calls internally between other handsets and Teams users, and externally
  • Enable paging (where supported on handsets)

The message waiting indicator will flash when someone leaves a voicemail message, and you can easily access voicemail messages right from the phone.

Calling is as simple as dialling a number. Handsets will adopt any dialling rules you configure in the TAC too, including 3, 4, 5 (etc) digit extensions.

Poly Rove handset showing options during a call


This sounds great! What’s the catch?

No catch! If you have the handsets within your org, you can start using them with Teams calling right away, without having to re-train your end users.

Of course, getting hold of older handsets could be a challenge, and most of these handsets are end of life now too. If you have them though, why not use them.


SIP handset VS Teams Handset – which should I choose?

Ultimately that is up to you of course. If you already have a supported SIP handset and want to sweat out those assets a little more, go right ahead and use them. If you’re after the newer Teams handsets, go down that path.

I love these older SIP handsets. They remind me of Skype for Business, are snappy, simple to use and easy to provision.

Have you given SIP handsets a go in your Teams environment yet?

0 0 votes
Article Rating
Subscribe
Notify of
guest

This site uses Akismet to reduce spam. Learn how your comment data is processed.

0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments