Supported Handsets

We support a variety of handsets on Hosted Suite / Voice Essentials. Handsets we officially support are listed here.

Vendors

  • CP860
  • CP920
  • CP960
  • T19E2
  • T21E2
  • T23
  • T27P
  • T27G
  • T29
  • T30
  • T31
  • T33
  • T40P
  • T40G
  • T41P
  • T41S
  • T42G
  • T42S
  • T46G
  • T46S
  • T48G
  • T48S
  • T52
  • T53 T53W
  • T54S
  • T54W
  • T56A
  • T57W
  • T58A
  • T58V
  • W52P W56P
  • W60B
  • W80B

Polycom

  • SoundPoint IP 321
  • SoundPoint IP 331
  • SoundPoint IP 335
  • SoundPoint IP 450
  • SoundPoint IP 550
  • SoundPoint IP 560
  • SoundPoint IP 650
  • SoundStation Duo
  • SoundStation IP 5000
  • SoundStation IP 6000
  • SoundStation IP 7000
  • VVX 101
  • VVX 150
  • VVX 201
  • VVX 250
  • VVX 300
  • VVX 301
  • VVX 310
  • VVX 311
  • VVX 350
  • VVX 400
  • VVX 401
  • VVX 410
  • VVX 411
  • VVX 450
  • VVX 500
  • VVX 501
  • VVX 600
  • VVX 601
  • VVX 1500
  • Trio 8500
  • Trio 8800

Snom

  • 710
  • 715
  • 720
  • 725
  • 760
  • 821
  • 870
  • D305
  • D315
  • D345
  • D375
  • D710
  • D712
  • D715
  • D725
  • D745
  • D765
  • MeetingPoint (MP)

Technical criteria for inclusion

Not all handsets are suitable for use on the hosted platform. We rely on a number of modern features that some older handsets do not support.

HTTPS Provisioning

All supported handsets must be able to provision over a HTTPS connection and must use TLSv1.2+.

We utilise mutual TLS certificate authentication - the phone will validate that it is talking to us, and we will validate it is a geniune phone that is connecting. Our certificate will be signed by a publically known CA, and the phone certificate will be signed by their respective manufacturer. In addition, the certificate presented must be able to uniquely identify the handsets. (e.g. Some older Yealink handsets ship with a “yealinkgeneric” certificate we cannot use.)

TLS-SIP and SRTP

Unlike traditional SIP which is unencrypted, we utilise TLS-SIP (also known as Secure SIP or SSIP) to form a TLS connection over which SIP operates. All signalling traffic between a handset and the platform is encrypted.

Similarly we use SRTP (Secure RTP) to protect the audio content of the call. This encrypts the audio between the phone and the platform.

For both TLS-SIP and SRTP, to be considered supported it must use TLSv1.2+.

As of October 2020, due to compatiblity issues we do not validate the client certificate provided by the phone. The phone will still validate our certificate to ensure that the connection is not being intercepted.