Handset Compatibility

We support a wide variety of handsets and devices. Phones listed as supporting HTTPS provisioning and SRTP will be available on hosted platforms.

Features mentioned here may also require an appropriate PABX software version, as well as updated handset firmware.

Models listed here that support HTTPS/SRTP require v.81 Yealink firmware - this is supported in the current release of the PABX software.

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.

ModelAuto-provisioningTLS-SIP/SRTP supportSupported sinceNotes
LocalHTTPS
CP860HTTPS/SRTP supported since 6.2.17; only supports TLSv1.0
CP9206.2.17
CP9606.2.17
T18
T19If HTTPS/SRTP enabled on the system, this phone won’t be able to provision
T19E2
T20
T21If HTTPS/SRTP enabled on the system, this phone won’t be able to provision
T21E2
T22
T23
T26
T27P
T27G6.2.0
T28
T29
T306.5.8
T316.5.8
T32
T336.5.8
T38
T40P
T40G6.3.11
T41P
T41S
T42G
T42S6.2.0Firmware is identical to T41S
T46G
T46S6.2.0Firmware is identical to T41S
T48G
T48S6.2.0Firmware is identical to T41S
T496.1.0
T526.2.17
T53 T53W6.4.4Both models share firmware. WiFi capability is only on T53W.
T54S6.2.17
T54W6.4.4
T56A6.2.17
T57W6.4.29
T58A6.2.17
T58V6.2.17
VP59
VP530
VP2009
W52P W56PDECT base station; firmware is not managed for this model, as we can only update the base station - not the handsets
W60B6.3.0DECT base station; firmware is not managed for this model, as we can only update the base station - not the handsets
W80B6.4.27DECT 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.

ModelAuto-provisioningTLS-SIP/SRTP supportSupported sinceNotes
LocalHTTPS
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 670Not able to provision over HTTPS - uses self-signed certificate.
SoundStation Duo6.2.14
SoundStation IP 4000
SoundStation IP 5000
SoundStation IP 6000
SoundStation IP 7000
VVX 101
VVX 1506.5.0
VVX 201
VVX 2506.5.0
VVX 300
VVX 301
VVX 310
VVX 311
VVX 3506.5.0
VVX 400
VVX 401
VVX 410
VVX 411
VVX 4506.5.0
VVX 500
VVX 501
VVX 600
VVX 601
VVX 1500
Trio 85006.3.2
Trio 88006.3.2

Snom

ModelAuto-provisioningTLS-SIP/SRTP supportSupported sinceNotes
LocalHTTPS
190
300
320
360
370
710Needs beta firmware for HTTPS provisioning - download here
715
720
725
760
820
821
870
D305
D315
D345
D375
D710Actually identifies itself as a 710; needs beta firmware for HTTPS provisioning - download here
D7126.3.0
D715
D725
D745
D765
M3
M9
M9R
MeetingPoint (MP)
PA1

Gigaset (and ex-Siemens)

Firmware for Gigaset devices is not managed by the system - they must be updated manually.
ModelAuto-provisioningTLS-SIP/SRTP supportSupported sinceNotes
LocalHTTPS
A580IP
C450IP
C460IP
N300IP
N510IP
N720IP
N720DMTreated as a N720
N870IP ProRequires 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.

ModelAuto-provisioningTLS-SIP/SRTP supportSupported sinceNotes
LocalHTTPS
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 UniWe have not tested the device, but deemed it to be compatible. No feature packs are available.

Cisco (and ex-Linksys)

Due to licensing restrictions, firmware is not managed for Cisco devices - they must be updated manually.
Cisco devices typically come in SIP and non-SIP (i.e. Cisco Call Manager) variants. It is critical that any model used supports SIP. (Some models have separate firmware “profiles” that enable this functionality.)
ModelAuto-provisioningTLS-SIP/SRTP supportSupported sinceNotes
LocalHTTPS
7941
7961
7965
CP 78116.2.11
CP 78216.2.11
CP 78416.2.11
CP 78616.2.11
PAP2TEx-Linksys model
SPA 112
SPA 301
SPA 303
SPA 901Ex-Linksys model
SPA 921Ex-Linksys model
SPA 922Ex-Linksys model
SPA 841Ex-Sipura model
SPA 941Ex-Linksys model
SPA 942Ex-Linksys model
SPA 962Ex-Linksys model
SPA 1001Ex-Sipura model
SPA 2000Ex-Sipura model
SPA 2002Ex-Sipura model
SPA 2102Ex-Sipura model
SPA 8000Ex-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:

ModelAuto-provisioningTLS-SIP/SRTP supportSupported sinceNotes
LocalHTTPS
KX-TGP500

Mitel (formerly Aastra)

All Mitel (formerly Aastra) phones are legacy support only and should not be recommended for new installs.
All Mitel (formerly Aastra) phones do not have firmware managed by the PABX for licensing reasons so must have firmware updated manually.
ModelAuto-provisioningTLS-SIP/SRTP supportSupported sinceNotes
LocalHTTPS
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.