Skip to main content

snom D-series


The support for Snom phones goes back to the year 2005 with the first version of the PBX. Support for the Snom phones include the use of TLS/SRTP, support for LDAP/LDAPS (address book), background images, setup of the buttons, customized alert tones, setup of time and language, synchronization of DND and redirection, and usage of the Snom minibrowser for changing selected user settings.

Snom phones can be manually configured, however it is easier and faster to use the automatic provisioning feature of the PBX. For this to work, the phones need to find the PBX.

Required Firmware

Snom releases firmware updates for most models on a regular basis. Unless a specific feature is needed or a specific problem needs to be addressed, the PBX works with a large range of firmware released that date back up to ten years. By default, the PBX does not update the firmware to any specific version; however when needed the firmware URL can be put into the parameter section of the PBX for the Snom phones.


If the phones don't have internet access, you can put the firmware into the tftp directory of the PBX working directory and then have the phones fetch it from the https://pbx/tftp/file path.

Firewall Rules

Traffic betwween the phones and the Internet

After a factory reset, the phones need access to the following locations:

  • NTP (UDP port 123) to and This is important because the phones need the time to be able to verify HTTPS certificates. Alternatively, if the DHCP provides a NTP server that server needs to be available from the phones.

  • HTTPS: When using SRAPS, access to this location is needed in order to receive the initial configuration. If there is no access, the startup process will be delayed because accessing the provisioning site will time out.

Typically the phones also need access to to fetch the latest firmware.

Traffic between the PBX and the phones

In order to work with the PBX, the phones need to have access to the following ports:

  • HTTPS and/or HTTP (typically TCP port 443 and 80): Access to these ports is needed in order to fetch the provisioning information and XML app content.

  • SIP/SIPS (typically TCP port 5060 and 5061 and UDP port 5060): Depending on the transport layer, only one of the three ports are used.

  • LDAP/LDAPS (typically port 2345 and 2346): If the PBX uses a valid certificate, the LDAPS port is used; otherwise the LDAP port.

  • RTP/RTCP (typically UDP ports 49152-65535): These ports are needed for RTP communication.

If the PBX is configured to act as NTP server, the configured NTP server on the PBX (typically UDP port 123) also needs to be allowed.

Typically there is no need to allow access to the TFTP port unless configuration is using that protocol.

Locating the PBX


The PBX supports SRAPS, the cloud provisioning solution; however for this the administrator needs to have an account with SRAPS. Cloud provisioning works when the PBX is on a routable (public) IP address, but it also works for LAN provisioning. In order to use SRAPS, you need to enter the credentials into the /reg_pnp_settings.htm page.

When using SRAPS, it is recommended to double check what the PBX sends to the Snom server after entering a MAC address. At a minimum, for that MAC address there needs to be an entry with the location of the PBX and the HTTP client username and password. If that is the case, the phones should be able to boot up into the PBX without any manual intervention, e.g. after a factory reset.

SIP multicast

If there is no SRAPS account available, the phones can locate the PBX through SIP multicast. In that case, unassigned phones will appear in the PBX page for LAN devices (/reg_prov_phones.htm) where they can be assigned to a specific extension.

After a factory reset, it is neccessary to manually start the provisioning pairing again before the phone can fetch the provisioning information.

Option 66

When using this option, the administrator needs to add the MAC address to the device list before the phones can fetch their configuration information. The MAC needs to be ready for pairing, so that the phone can fetch the credentials.

As with the SIP multicast, after a factory reset, it is neccessary to manually start the provisioning pairing again before the phone can fetch the provisioning information.

Manual setup

The manual setup method can be used as a fallback if the other configuration methods are unavailable. In order to do that, the setting_server of the phone needs to be set to the URL of the phone. This setting is available in Advanced, Update (Section) Setting URL. There is no need to include a path, but the scheme for the URL should be included (e.g.

Button modes

For most D-series models, the PBX automatically generates the configuration for the buttons. Most of the modes don't need any special explanation, however some of them do:

In the Snom mode, the parameter is inserted literally into the configuration for that button. For example, when the parameter is keyevent F_ADR_BOOK, the PBX will insert that into the button. In this example, this put the address book function on the button. This is useful to take advantage of button functionality that is not available through the PBX modes.


The PBX automatically generates background images for the phones when you upload the graphics in the logo page for the tenant. In needed the images can be replaced with specific images for each resolution.

Alert tones are also automatically fetched by the phones according to what was set up for the tenant.

For additional customization, the snom General parameter is available on system, tenant and extension level. The content of this parameter is inserted literally into the provisioning file. If there are overlaps with the template, the phones will choose the content from the parameter. This makes it possible to customize the phones in every detail.


Editing the template itself if not recommended because later software upgrades will create merge conflicts with the modified template.