...
The SNOM phones are able to use DHCP to obtain the name of the sipXecs server from where they can download the configuration profiles at startup. By default the phone is configured to look for the DHCP option server-name or tftp-server-name to obtain the hostname and port of the server that provides the configuration file. The server-name parameter is the variable with the number 66 (Option 66) in the DHCP Scope Options settings. The DHCP option bootfile-name also known as Option 67 is used to specify the directory and file name of the configuration file. Using the Linux dhcpd DHCP server, the configuration could look as follows:
Code Block |
---|
host snom360 { hardware ethernet 00:04:13:23:20:77; fixed-address 192.168.5.253; option tftp-server-name "http://sipx.example.com:8090"; option bootfile-name "/phone/profile/docroot/{mac}.htmxml"; } |
NOTE: the "{mac}" portion of the bootfile-name should appear exactly like that. Do not use an actual MAC addr in the string. SNOM phones recognize {mac} as a variable, meaning 'include you own MAC addr here'.
...
Note: In a mixed environment with phones from different manufacturers (e.g. SNOM and Polycom), there is a conflict with respect to DHCP parameter settings as both types of phones require DHCP Option 66 (tftp-server-name) to include a string relevant to their respective boot process. This can easily be resolved by defining specific resource allocation records for your phones as shown above.
Alternative Manual Configuration:
...
- Open the phone's configuration Web interface. Go to the Advanced tab:
- Scroll down and find the section labeled Update and configure the following setting in the drop down box as required. The default setting used by sipX Config Server is "Update automatically", which causes the phone to upgrade its firmware and bootloader everytime a new version is made available in the sipXecs server's docroot directory. See additional options below.
- Paste the URL of the profile (path and filename) into the text field labeled "Setting URL" as follows. The {mac} portion is a parameter which will be replaced by the phone with its own MAC address. Refer to this Whitepaper from SNOM for further information.
Panel | ||||||
---|---|---|---|---|---|---|
|
- Select "Save" then reboot the phone.
...
You can verify that a profile exists for your phone on the sipX server (see below on how to generate such a profile using the sipX Configuration Server):
Panel | |||||
---|---|---|---|---|---|
|
Firmware Update
http://wiki.snom.com/FirmwareNote:
Note |
---|
Do not use firmware older than 4.x. SNOM in regular intervals provides updates to its firmware. The latest one tested with sipXecs is release 6.2. |
Firmware Upgrade Procedure
- Find the IP address of the phone by pressing the key market with a '?'. The About screen displays.
- Find the latest firmware version on the SNOM Support Page. A good overview of the latest firmware version of all SNOM phones can be found here. Copy the URL of the firmware to your clipboard. It should look something like this: _http://fox.snom.com/download/snom360-6.0.0-beta-SIP-j.bin_.
- Open the Web configuration portal of the phone by pointing a browser to the IP address of your phone, then go to "Software Update" (_http://10.1.1.156/update.htm_).
- Copy the URL of the firmware binary into the firmware text field and press the "Load" button. NOTE: You will not get any feedback on the web page.
- The phone should now reboot. Dependent on the installed firmware version it might ask for confirmation.
- Navigate to the Web interface and go to the "System Information" link and verify that the last section of the "Version-Code" field matches the firmware version you loaded.
...
Note |
---|
If you upgrade from 3.xx to 4.x, refer to the documentation on the SNOM Web page. |
Note |
---|
...
You have to upgrade to firmware 5.x before you can upgrade to version 6.x. |
Note |
---|
...
Firmware updates can also be initiated using the |
...
sipXecs Configuration Server. This capability is recommended if you want your phone to automatically and periodically check for newly released firmware updates. |
Configuring the SNOM phones with the sipXecs Configuration Server
...
Version 4.6 do NOT use Provision Port 8090
...
in the latest 4.6 (stable/unstable) don't use Port 8090 for provisioning URL, the IPTables Firewall does not have a Rule to allow the traffic. So you can choose to use HTTP Port 80 or add an rule for Port TCP/8090 to /etc/sysconfig/iptables
http://{HOSTNAME}/phone/profile/docroot/{mac}.xml
Configuring the SNOM phones with the sipXecs Configuration Server
Once the phone is able to find its boot server at startup, all remaining configuration is done automatically and remotely using the sipX Configuration Server and Web UI. The tasks required to complete the installation are as follows:
...
- Log into the sipX UI as superadmin
- It is recommended that you add different User Groups as Web UI and Call Handling Permissions are defined for groups and not individual users. Groups can consist of users with different phones.
- Click on Users from the main navigation, then click the Add User button to create a new user:
- Create a new user by entering the requested parameters. The extension number is populated based on the settings in User Extension Pool; however, it can be changed. Note that the PIN is only the password the user needs to login to the voicemail portal. The SIP password the phone will use for registration is automatically generated and assigned. It can be viewed / changed by clicking on Show Advanced Settings. (See here for more information).
5. Edit permissions by going to Group Settings for the group the user belongs to. If the user should be able to record system prompts using the phone, enable it. Also, make sure you set correct permissions for dialing rules.
...