Snom
From Pbxnsip Wiki
Contents |
Available Features
Starting with version 2.1, the PBX is able to provision the snom phones of the 3xx series, including:
- Downloading of the account information through secure HTTPS
- Provisioning of the Dictionary key to access the PBX address book (XML)
- Upgrading the firmware of the phone
- Provisioning of the LED buttons
- Showing the image of the caller on the screen of the snom 370
- Multicast Plug and Play
The goal is that the phones are completely remote managed. The support personal just need to factory reset the phone in order to fix bad configurations.
For the provisioning of the snom M3, see the seperate page snom M3.
Plug and Play Parameters
There are a few parameters that you may or should change before provisioning the phones:
- snom_3xx_phone.xml/vlan: With this parameter you can define in which VLAN the phone should operate. A typical value is "128 5" meaning that the phone will operate in VLAN 128 with the priority 5. Possible values are 0 to 4095 for the VLAN and 0 to 7 for the priority. Please note that the PBX must be in both the provisioning VLAN (typically VLAN 0) and in the destination VLAN.
- snom_3xx_phone.xml/admin_pin: This is the PIN code that is assigned for the admin mode of the phone. The default value "0000" will prompt the phone user to enter a new PIN code, as the value "0000" is considered insecure. So you should assign a different value.
- snom_3xx_phone.xml/transport: By default, the PBX will use transport layer TLS for secure telephony. However, in some environments you may want to use tcp or udp.
- snom_300_fkeys.xml/button[3-6]: Here you can define what should be put on the respective button on the phone. By default, the PBX assigns the printed functionality to the phone and for the address book button the PBX provisions a Action URL that points to the address book of the PBX.
- snom_3xx_fw_snom3[0267]0.xml/firmware30: This settings defines where the phone should get it's firmware from (see below).
Preparing the PBX
Passwords
On the PBX, you want to check the following items:
- Make sure that you have selected the password provisioning method the right way (see Port Setup). If you are provisioning that phone for the first time, you should make sure that the flag for that extension is clear (see Extension for that).
- If you want to have explicit control over the assignment of MAC addresses to extensions, you should enter the MAC address to the extension (see Extension).
- You must have at least one HTTP port and at least one HTTPS port open on the PBX (this is the default). See Port Setup if you changed something there.
- Check if you want to automatically provision passwords. This is done with the flag in the TFTP section of the Port Setup.
Buttons
For other hints, see Prepare an Extension for Plug and Play. In order to assign buttons to the phone, check out Assigning Buttons. The phones have the following button names:
- snom 300: "1"-"6". These keys correspond to the six programmable keys on the device.
- snom 320, 360, 370: "1"-"12". These keys correspond to the twelve keys on the phone, as shown in the snom function key map (1-6 are left, 7-12 are on the right side).
- If you don't assign a button in a profile, the PBX does not provision that key. This way, you can leave the programming for the end user, for example to program local speed dial buttons.
The PBX generates all necessary files on the fly. There is no need to edit files in the file system.
Multicast Paging
The snom devices support one-way paging via multicast. This is a powerful way to use the desktop phones for announcements without having the delay and overhead to invite a large number of phones with SIP messages. The snom phones support only one paging group, which can be automatically provisioned by the PBX.
In order to automatically provision the snom phones with a multicast paging group, you need to have one paging group in multicast mode in the domain where the snom phone is being provisioned. See the example in Paging#Multicast_Mode for a multicast group that can be sued for multicast paging.
Locating the PBX
When a phone boots it, it needs to know the address of the PBX configuration server. There are three ways to do this:
Multicast
The Multicast location method was implemented in order to minimize the effort to set up a phone. It is also the best option in environments where you don’t have full access to the settings of the DHCP server.
By default, the snom phones send out multicast packets into the LAN that ask “where is a PBX that can configure me?” The PBX then answers the request and provides the link for downloading the configuration.
If you are using this method, make sure that you have only one PBX running in the network that has multicast turned on (see Overall System Settings).
DHCP Option 66
DHCP offers an option that tells the DHCP client from here it should get it’s “configuration”. This option is widely know as option 66.
Many low-cost router do include a DHCP server, however that server is not able to provision option 66. If you are using such a router, option 66 is not an option for you and you must use either multicast provisioning or manual setup.
For other DHCP servers, you must assign the IP address of the PBX to option 66. Most DHCP servers allow doing this per MAC address, so that you can do this only for the VoIP phones in your network and other devices are not affected.
Manual Setup
If you want to explicitly tell the phone from where to download the configuration, there are two possibilities.
If you can use tftp (e.g. because the phone is in the same LAN), then just enter the IP address of the PBX. In this case, the PBX must have the tftp port open on the standard port.
If you cannot use tftp, you can use a HTTP URL. This URL must contain the MAC address of the phone as stated below:
http://pbx.pbxnsip.com:9012/provisioning/snom320-00041324006D.htm
The address of the PBX can be a DNS name or it can just be the IP address. If you are not using the standard port 80, you must put the port name behind the server address. The name "provisioning" is hard coded into the PBX, so that it is easier to differentiate the different traffic classes within the PBX web server. The name snom320 indicates the model (choose appropriately for other models). You must put the MAC address (upper case) behind the model name and conclude the name with a ".htm". After entering the address, reboot the phone.
You should put the URL into the Advanced/Update section of the phone (see picture below):
Firmware Upgrade
The PBX is able to provision the firmware for the phones. Before you can use this, you must update the phones manually to version 7. If you need to upgrade to version 7, you should use the link http://provisioning.snom.com/from6to7/update.php to upgrade your phones. Just put that URI into the "Setting URL" (not the firmware URL!) of the phone, set the update policy to "Update Automatically" and reboot the phone. It will boot a couple of times and download several images.
For the provisioning of the firmware, you have two choices. Either you just provide the HTTP link to the firmware (in this case the phone will fetch the firmware from that location, possibly the public Internet), or you can save the firmware locally on the PBX and provision the firmware from there.
You should use version 7.1.33. Earlier versions had problems with registration stability and/or did not support the buttons package.
Once that you are running version 7 and you decide to provision the firmware locally from the phone, put the firmware images from snom into your tftp folder (see example below).
-rw-rw-rw- 1 pbx root 3162524 Sep 28 09:45 snom300-7.1.29-SIP-f.bin -rw-rw-rw- 1 pbx root 3179676 Sep 28 09:45 snom320-7.1.29-SIP-f.bin -rw-rw-rw- 1 pbx root 3246956 Sep 28 09:46 snom360-7.1.29-SIP-f.bin -rw-rw-rw- 1 pbx root 3928736 Sep 28 09:46 snom370-7.1.29-SIP-f.bin
Then copy the filenames into the Plug and Play Parameters of the PBX:
The next time when the phone gets provisioned, the phone will then perform a software upgrade to provided software version.
If you need to reboot a phone, you can do this remotely by clicking on the check-sync link in the registration window for the extension:
Manual Configuration
Registration
If you decide to set the phone up manually, we strongly recommend studying the documentation of the phone.
The best way to configure the phone is from its web interface. You just have to set up the Account (e.g. 123), Password (e.g. bigsecret), Registrar (e.g. localhost) and Outbound Proxy (e.g. 192.168.0.5) on the phone. When you hit the Save button, the phone should already register - you don't have to reboot. If you want to use the SRTP feature of the phone, you must use the TLS transport layer. You can enforce this by using the parameter "transport=tls" in the outbound proxy URI (e.g. "sip:192.168.1.2:5061;transport=tls").
Function Keys (Buttons)
If you want to manually set up the Buttons, you must add the value "buttons" to the "Proxy-Require" section of the line:
Then you need to setup the function keys as buttons:
After you have set the buttons up, you need to assign the button profile to the extension (see above). Then you can program the buttons as you like from the PBX. Please notice that the private line is not a button, it is a "Line" on the phone.
Function Keys (Dialog State)
The snom phones have function keys that can be used to see if CO lines are in use or other extensions are on the phone.
The easiest thing is to use the destination mode. Just enter the number that you want to watch into the setting. Then you will be able to see when that extension is in a call. If the extension rings, you can pick up the call by pressing the associated key.
Starting with version 1.5, you can also monitor the status of "CO" lines - which are nothing else than the status of trunk lines. From a phone's perspective there is no difference between an extension and a trunk line.
If you are using version 6 or higher, you can also use the line modes for the function keys to monitor CO-Lines. Make sure that you fill out the CO-line fields in the trunk that you want to monitor. This way, you can easily see what calls are going on in your office and you can pick up incoming calls by pressing the corresponding function key.
Ringtones
The PBX sends in the Alert-Info header how the phone should ring. This has the puepose that internal calls sound different that external calls. However, sometimes you want to select the ringtone directly on the phone, no matter what the PBX sends.
There is a setting called "Alert Info playback" in the Advanced Settings of the phone. This setting is on be default, so that the phone does take the proposal from the PBX. If you want to play back the ring tone selected locally on the phone, you can turn this setting off.
Images
If you want to upload an image for the snom 370, use a 60 x 79 pixel, greyscale BMP image. These images can be loaded into the extension of the PBX, and when someone calls within the PBX, the phone will display the image of the caller. An example of such an image is shown below (this image is JPEG because the Wiki is not able to show BMP):
Other Topics
- If you enter something in the advanced settings of the phone, make sure that the time zone is selected correctly. The PBX does provide the necessary information to handle the time in the selected time zone, but it does not provision the name of the time zone. If you hit the save button without selecting the right name, the phone will move to the "Hawaii" time zone, which is on top of the list.
