Page tree

Transport Layer Security (TLS) provides mechanisms to secure your phone traffic. Typically it is used to protect your SIP and HTTP connections from eavesdropping and tampering.

TLS handshake overview

Initially, when a client wants to establish a secure connection to a server, some parameters are negotiated, this phase is called the handshake procedure. One of these parameters is the supported cipher suites defining the encryption algorithms required to encrypt the traffic. In a next step, the server sends a digital certificate that contains its public encryption key, the trusted certificate authority (issuer) and a signature of the certificate.

The client may reject the connection if the identity of the server or the issuer is unknown. Usually, the client has a list of trusted server certificates and a list of trusted certificate authorities (CA). If the server certificate is considered trusted or if the identification from the server is signed by one of these CAs, the client typically permits the connection and delivers a random number encrypted with the server's public key to the server. As only the server can decrypt this number with its private key, it is used as the session key to encrypt and decrypt the traffic.

Optionally the server can "ask" the client for the certificate. In that case the client must send a TLS certificate. Now the server can authenticate or deny the request based on the client certificate.

If the identification from the server is signed by one of these CAs, the client typically permits the connection and delivers a random number encrypted with the server's public key to the server. As only the server can decrypt this number with its private key, it is used as the session key to encrypt and decrypt the traffic.

Your phone acts as a TLS client in various cases:

  • SIP connections with TLS as transport protocol
  • Provisioning requests
  • Action URL HTTPs requests
  • HTTPS requests to an URL triggered by function keys
  • Minibrowser applications served by an HTTPS server
  • LDAP server providing the business contacts

When TLS is used a mutual authentication of the client and the server can be performed by the phone and the server.

Setting-Up the phone for TLS

The built-in certificate

Every Snom phone (except the old 3xx series) is produced with a built-in TLS certificate on board.

Every device certificate is issued by the Snom Certification Authority. The built-in certificate contains the the device MAC address into the DN x.509 attribute.

Thanks to the built-in certificate, a server using the TLS protocol can:

  • verify the issuer of the certificate, checking the certificate signature against the Snom CA: in other words the server can make sure that the request comes from a Snom phone
  • verify the DN of the client certificate, checking the MAC within the offered certificate and the requested resource. The server can authorise the specific device to the resource

Uploading the Phone Certificate

In fact, no special configuration is required. Every out-of-the-box Snom phone has a certificate built-in to the firmware along with its private key. You can retrieve this certificate by pointing your browser to your phone's web interface via secure HTTP (HTTPS). Usually you will have to confirm that you trust this identification since your browser could not identify your phone. After confirming, your connection to the web interface will be encrypted.

You can also specify your own client certificate in the webserver_cert setting. In this case, make sure you are provisioning the certificate and the key in a trusted environment, see below how to provision a custom certificate.

Authentication of the devices

The TLS server can be configured to check the client identity via the TLS authentication: as described into the previous section, during the TLS handshake, the server asks the client for the certificate. The Snom phone will send the built-in certificate, now the server can check the issuer of the client certificate and permit or deny the request.

Since device MAC address is mentioned into the built-in certificate CN, the web server can also authorize or deny the request based on the requested URL and the presented client certificate.

In order to configure the client authentication, you will need to import the Snom Certification Authority certificates into your TLS server.


Starting with fw and 10.1.x we support the SHA-2 algorithm, new phone models are already equipped with a SHA-2 built-in certificate. In case you are using devices with SHA-2 certificate you will need to import also the Snom SHA-2 CA public certificate.

Phone modelSupported Hash algorithmBuilt-in certificate
Snom 300SHA-1SHA-1
Snom 320
Snom 370
Snom PA1
Snom MP
Snom D120SHA-1, SHA2SHA-2
Snom 710 / D710SHA-1, SHA-2 (fw >=
Snom 715 / D715SHA-1, SHA2 (fw >=
Snom D712SHA-1, SHA2 (fw >=
Snom 720SHA-1, SHA2 (fw >=
Snom 760SHA-1, SHA-2 (fw >=
Snom D725SHA-1, SHA2 (fw >=
Snom D735SHA-1, SHA2SHA-2
Snom D745SHA-1, SHA2 (fw >=
Snom D765SHA-1, SHA2 (fw >=
Snom D785SHA-1, SHA2SHA-2
Snom D305SHA-1, SHA2 (fw >=
Snom D315SHA-1, SHA2 (fw >=
Snom D345SHA-1, SHA2 (fw >=
Snom D375SHA-1, SHA2 (fw >=
Snom D385SHA-1, SHA2SHA-2


The devices:

  • Snom 300,
    Snom 320,
    Snom 370,
    Snom PA1 &
    Snom MP

are manufactured with a shared Snom certificate, so the built-in certificate per device is not unique and the MAC address is not mentioned in the CN.
Unfortunately, these devices cannot be upgraded with a unique SHA 1 or 2 certificate. Therefore, these devices can only use SRAPS for forwarding but not for provisioning.

Upgrade to SHA-2

Depending on the device and the firmware used, with the exception of the devices mentioned above, all Snom deskphones with a unique SHA 1 certificate can be upgraded to a unique SHA 2 certificate using SRAPS to fully benefit from SRAPS.

Upgrading a native SHA 1 device to SHA 2 requires a device specific firmware patch. The step by step guide below, shows how to upgrade your Snom phone.


To upgrade the built-in certificate to SHA-2 version follow these steps:

  1. Factory reset the phone or check that the setting_server parameter has the default value.
  2. Upgrade the phone to the latest firmware version.
  3. Create an account on SRAPS (, if you don't have one.
  4. Add the phone mac address into your SRAPS account.
  5. On SRAPS, for each phone, include provisioning of any parameter (for example the phone language)
  6. When you click "Save" on SRAPS, a popup will appear asking if you want to upgrade the certificate to SHA-2. Accept the injection.
  7. Reboot the phone. → Ready.

Hint: If you want to do this for more then one Phone, you can also create a provisioning profile with one or many parameters, and then assign all devices to it. With this you will save some time.

Snom Certification Authority public certificates

From the following links you can download:

As SHA1 gets widely deprecated and SHA2 becomes more and more the standard, support for it is getting mandatory in real world deployments.

Server Authentication

  • Version 8.x
    In version 8.x, you do not need to worry about the server identification. Snom phones do not verify server identities by default. Starting with FW version 8.2.30 you can enable a setting to require verification of server certificates though. You can activate the feature on the certificates page of the web interface:


Please be careful when enabling this feature. The phone will reject all secure connections from peers offering an unknown certificate that could not be verified by one of the built-in CAs of the Snom phone. Please refer to the Certificate Authorities tab to see which authorities are supported by the phone. Due to security concerns, you can only disable this feature by resetting the phone to the factory defaults.
  • Version 10.x
    As of version 10.x, Snom has decided to force the server identity verification. This verification cannot be disabled because that would create a security weakness for the Snom Phones.
    In addition to the server certificate a phone can also verify the identity of the server checking if the certificate DN matches the server name FQDN. This can be done via the setting check_fqdn_against_server_cert. The behaviour of the server name validation can be modified via the setting host_name_validation_flags.

Adding Unknown Certificates

The phone will reject a connection if it cannot verify the identification with the certificate delivered by the server. If this happens, the following notification will appear on the screen:

A certificate is trusted if its signature is signed by a certificate authority. Snom has pre-installed a list of CAs which are listed on the Certificate Authorities tab of the Certificates page. This list is automatically updated based on the Mozilla official list, at every new firmware upgrade.

All rejected certificates are listed in the Unknown Certificates tab. If you want to permanently trust a certificate you can add it as an exception:

After adding it as an exception in the Server Certificates tab a connection from a peer using this certificate will no longer be rejected.

Manually Uploading Certificates

In admin mode, you can manually upload certificates signed by one of the phone’s accepted authorities or server certificates in the Unknown Certificates tab. Every attempt to upload an unknown certificate will fail. In case of upload failures, please refer to the log and make sure your certificate is in DER format and is signed by one of phone's authorities or server certificates.

Uploading Server Certificates via Provisioning

You can upload a server certificate using auto provisioning. For this, the download link to the certificate needs to be placed within the XML.

The certificates settings (<certificates> tag) contains the trusted server certificates. This XML tag can be used either inside the <settings> tag or as an individual XML file whose URL is listed inside <setting-files> tag

The tag contains an attribute with the URL of the certificate file to fetch:

<certificate url="http://some.url/certificate.der" />

Please note that the download of the certificate is delayed after all provisioning xml files have been loaded and processed.

Beginning with firmware release a second variant of this tag is supported, where the content of the certificate file is included as a base64 encoded string:

<certificate type="base64">...</certificate>

The benefit of this variant is that the certificate is immediately available after processing the line in the provisioning XML.


You can get the base64 encoded certificate out of the PEM format, removing the BEGIN / END taglines:


If you decide to provide the download link(s) in an additional XML file, this is how it could look like: 

 <certificate url="" />
 <certificate url="" />

The attributes url and base64 can be combined in the same file, as the following example:

<?xml version="1.0" encoding="utf-8" ?>
   <certificate url="" />
   <certificate url="" />
   <certificate type="base64">

All provisioned certificates need to be signed by one of the phone's server or authority certificates (this restriction was removed starting with firmware revisions Make sure the supplied certificates are in DER format.

Tech Notes

Phone's Web Server Certificate

The phone uses the built-in certificate also as a certificate for the web user interface when accessed via HTTPS. Currently Snom phones come with SHA1(RSA, 1024 bit key length) or SHA2(RSA, 2048 bit key length) certificates.

Starting from firmware it is possible to switch the certificate via the setting phone_cert_type to a SHA256 certificate .

Supported Cipher Suites

PhoneFirmwareProtocol VersionKey ExchangeAuthenticationBlock CipherKey Length
Mode of OperationMessage Authentication CodeNotes
snom3008. 3, TLS 1.0DH, RSANULL, RSA3DES, DES, NULL, RC456, 128, 168CBCMD5, SHA1Firmware version not
supported anymore (EoL).
It is highly recommended to
upgrade to a higher version.
snom300 1.0DH, RSANULL, RSA3DES, AES, DES, NULL, RC456, 128, 168CBCMD5, SHA1* Since firmware version
the snom710 has the same
TLS-properties as the snom715
(see below).
* Starting with version
have been removed from the
supported block ciphers.
snom715TLS 1.0, TLS 1.1,
TLS 1.2
DH, ECDH, RSA, SRPDSS, ECDSA, RSA3DES, AES, Camellia128, 168, 256CBC, GCMSHA1, SHA256, SHA384
snomD3058.9.3.52TLS 1.0, TLS 1.1,
TLS 1.2

TLS 1.0, TLS 1.1,
TLS 1.2


  • No support of Certificate Revocation Lists (CRL).
  • No support for Certificate Lifecycle Management (e.g. SCEP).