Handset Compatibility
Estimated reading time: 7 minutes
We support a wide variety of handsets and devices. Phones listed as supporting HTTPS provisioning and SRTP will be available on hosted platforms.
Yealink
Yealink phones must have shipped originally with v.72 firmware for HTTPS provisioning to work. Even if they have been upgraded since, before this version they shipped with a generic certificate - which means we can’t identify them for provisioning.
Theoretically any handset manufactured since 2015 should have shipped with this.
Model | Auto-provisioning | TLS-SIP/SRTP support | Supported since | Notes | |
---|---|---|---|---|---|
Local | HTTPS | ||||
CP860 | HTTPS/SRTP supported since 6.2.17; only supports TLSv1.0 | ||||
CP920 | 6.2.17 | ||||
CP960 | 6.2.17 | ||||
T18 | |||||
T19 | If HTTPS/SRTP enabled on the system, this phone won’t be able to provision | ||||
T19E2 | |||||
T20 | |||||
T21 | If HTTPS/SRTP enabled on the system, this phone won’t be able to provision | ||||
T21E2 | |||||
T22 | |||||
T23 | |||||
T26 | |||||
T27P | |||||
T27G | 6.2.0 | ||||
T28 | |||||
T29 | |||||
T30 | 6.5.8 | ||||
T31 | 6.5.8 | ||||
T32 | |||||
T33 | 6.5.8 | ||||
T38 | |||||
T40P | |||||
T40G | 6.3.11 | ||||
T41P | |||||
T41S | |||||
T42G | |||||
T42S | 6.2.0 | Firmware is identical to T41S | |||
T43U | 6.5.18 | ||||
T46U | 6.5.18 | ||||
T46G | |||||
T46S | 6.2.0 | Firmware is identical to T41S | |||
T48U | 6.5.18 | ||||
T48G | |||||
T48S | 6.2.0 | Firmware is identical to T41S | |||
T49 | 6.1.0 | ||||
T52 | 6.2.17 | ||||
T53 T53W | 6.4.4 | Both models share firmware. WiFi capability is only on T53W. | |||
T54S | 6.2.17 | ||||
T54W | 6.4.4 | ||||
T56A | 6.2.17 | ||||
T57W | 6.4.29 | ||||
T58A | 6.2.17 | ||||
T58V | 6.2.17 | ||||
VP59 | |||||
VP530 | |||||
VP2009 | |||||
W52P W56P | DECT base station; firmware is not managed for this model, as we can only update the base station - not the handsets | ||||
W60B | 6.3.0 | DECT base station; firmware is not managed for this model, as we can only update the base station - not the handsets | |||
W70B | 6.5.18 | DECT base station; firmware is not managed for this model, as we can only update the base station - not the handsets | |||
W80B | 6.4.27 | DECT base station; firmware is not managed for this model, as we can only update the base station - not the handsets | |||
W90B | 6.5.24 | Check software version availability. DECT base station; firmware is not managed for this model, as we can only update the base station - not the handsets |
Polycom
Older Polycom phones (before 2011) may ship without a device certificate, so will self-sign one. If this is the case then they will not work with HTTPS provisioning!
Refer to Polycom documentation to find out which revisions of phone come with a device certificate.
Model | Auto-provisioning | TLS-SIP/SRTP support | Supported since | Notes | |
---|---|---|---|---|---|
Local | HTTPS | ||||
KWS300 | |||||
SoundPoint IP 320 | |||||
SoundPoint IP 321 | |||||
SoundPoint IP 330 | |||||
SoundPoint IP 331 | |||||
SoundPoint IP 335 | |||||
SoundPoint IP 430 | |||||
SoundPoint IP 450 | |||||
SoundPoint IP 500 | |||||
SoundPoint IP 501 | |||||
SoundPoint IP 550 | |||||
SoundPoint IP 560 | |||||
SoundPoint IP 601 | |||||
SoundPoint IP 650 | |||||
SoundPoint IP 670 | Not able to provision over HTTPS - uses self-signed certificate. | ||||
SoundStation Duo | 6.2.14 | ||||
SoundStation IP 4000 | |||||
SoundStation IP 5000 | |||||
SoundStation IP 6000 | |||||
SoundStation IP 7000 | |||||
VVX 101 | |||||
VVX 150 | 6.5.0 | ||||
VVX 201 | |||||
VVX 250 | 6.5.0 | ||||
VVX 300 | |||||
VVX 301 | |||||
VVX 310 | |||||
VVX 311 | |||||
VVX 350 | 6.5.0 | ||||
VVX 400 | |||||
VVX 401 | |||||
VVX 410 | |||||
VVX 411 | |||||
VVX 450 | 6.5.0 | ||||
VVX 500 | |||||
VVX 501 | |||||
VVX 600 | |||||
VVX 601 | |||||
VVX 1500 | |||||
Trio 8500 | 6.3.2 | ||||
Trio 8800 | 6.3.2 |
Snom
Model | Auto-provisioning | TLS-SIP/SRTP support | Supported since | Notes | |
---|---|---|---|---|---|
Local | HTTPS | ||||
190 | |||||
300 | |||||
320 | |||||
360 | |||||
370 | |||||
710 | Needs beta firmware for HTTPS provisioning - download here | ||||
715 | |||||
720 | |||||
725 | |||||
760 | |||||
820 | |||||
821 | |||||
870 | |||||
D305 | |||||
D315 | |||||
D345 | |||||
D375 | |||||
D710 | Actually identifies itself as a 710; needs beta firmware for HTTPS provisioning - download here | ||||
D712 | 6.3.0 | ||||
D715 | |||||
D725 | |||||
D745 | |||||
D765 | |||||
M3 | |||||
M9 | |||||
M9R | |||||
MeetingPoint (MP) | |||||
PA1 |
Gigaset (and ex-Siemens)
Model | Auto-provisioning | TLS-SIP/SRTP support | Supported since | Notes | |
---|---|---|---|---|---|
Local | HTTPS | ||||
A580IP | |||||
C450IP | |||||
C460IP | |||||
N300IP | |||||
N510IP | |||||
N720IP | |||||
N720DM | Treated as a N720 | ||||
N870IP Pro | Requires hardware with a factory certificate | ||||
S450IP | |||||
S685IP |
2N
We have done interop testing with 2N Helios IP door entry (intercom) devices, but we don’t autoprovision them. They must be configured manually.
Model | Auto-provisioning | TLS-SIP/SRTP support | Supported since | Notes | |
---|---|---|---|---|---|
Local | HTTPS | ||||
Helios IP Force | (Manual provisioning required) | SRTP/SIPS requires “Enhanced Security” or “Gold” feature licence, purchased separately | |||
Helios IP Verso | (Manual provisioning required) | We have not tested the device, but deemed it to be compatible. SRTP/SIPS requires “Enhanced Security” or “Gold” feature licence, purchased separately. | |||
Helios IP Vario | (Manual provisioning required) | We have not tested the device, but deemed it to be compatible. “Gold” feature licence is included by default. | |||
Helios IP Uni | We have not tested the device, but deemed it to be compatible. No feature packs are available. |
Cisco (and ex-Linksys)
Model | Auto-provisioning | TLS-SIP/SRTP support | Supported since | Notes | |
---|---|---|---|---|---|
Local | HTTPS | ||||
7941 | |||||
7961 | |||||
7965 | |||||
CP 7811 | 6.2.11 | ||||
CP 7821 | 6.2.11 | ||||
CP 7841 | 6.2.11 | ||||
CP 7861 | 6.2.11 | ||||
PAP2T | Ex-Linksys model | ||||
SPA 112 | |||||
SPA 301 | |||||
SPA 303 | |||||
SPA 901 | Ex-Linksys model | ||||
SPA 921 | Ex-Linksys model | ||||
SPA 922 | Ex-Linksys model | ||||
SPA 841 | Ex-Sipura model | ||||
SPA 941 | Ex-Linksys model | ||||
SPA 942 | Ex-Linksys model | ||||
SPA 962 | Ex-Linksys model | ||||
SPA 1001 | Ex-Sipura model | ||||
SPA 2000 | Ex-Sipura model | ||||
SPA 2002 | Ex-Sipura model | ||||
SPA 2102 | Ex-Sipura model | ||||
SPA 8000 | Ex-Sipura model | ||||
SPA 502G | |||||
SPA 504G | |||||
SPA 525G | |||||
SPA 508G | |||||
SPA 509G |
Panasonic
All Panasonic phones do not have firmware managed by the PABX for licensing reasons so must have firmware updated manually.
Currently we only support/auto-provision one model of Panasonic:
Model | Auto-provisioning | TLS-SIP/SRTP support | Supported since | Notes | |
---|---|---|---|---|---|
Local | HTTPS | ||||
KX-TGP500 |
Mitel (formerly Aastra)
Model | Auto-provisioning | TLS-SIP/SRTP support | Supported since | Notes | |
---|---|---|---|---|---|
Local | HTTPS | ||||
480i | |||||
6751i (51i) | |||||
6753i (53i) | |||||
6755i (55i) | |||||
6557i (57i) | |||||
6730i | |||||
6731i | |||||
9112i | |||||
9133i |
Other vendors
Rebadged Snom Phones
We autoprovision two rebadged models of Snom:
- Doro ip840 - actually a Snom 360
- Elmeg IP290 - actually a Snom 190
Other vendors not listed
It is quite possible that other phones and devices can work with our system, if they support SIP. They will need to be manually configured on the system (as a generic phone) and on the device itself.