Interoperability
Technology Leadership
Reasonable Solutions
Technical Training VON
Europe
Mass Deployment
Interoperability
Technology Leadership
Reasonable Solutions
Overview
Methods for distinct phone environments
Usage in LANs w/ DHCP
- Prerequisites
- Setting file structure
- Hints for setting files
- Firmware Update requirements
- Boot up process diagramm
Demonstration
- Factory reset
- Boot up process
- Analysis: Ethereal/ Setting page
Setting Server Redirection
PnP – new ways of mass provisioning
Mass Deployment: Overview
Interoperability
Technology Leadership
Reasonable Solutions
Mass Deployment is a function which
permits the phone to retrieve its settings
from a remote server (TFTP/ HTTP(S))
Mass Deployment is very useful for larger
phone installations
Mass Deployment can not only be used to
provide general settings (e.g. language,
timezone, tone scheme etc.) or phone
specific settings (e.g. SIP identity settings)
but also initiate firmware updates/
downgrades
Mass Deployment: Methods
Interoperability
Technology Leadership
Reasonable Solutions
Mass Deployment implementation may vary
depending on the phone environment:
Phone environment
Local Area Network
e.g. managed
company/SOHO LAN
•LAN using DHCP
Requirements:
•DHCP Server
•TFTP or HTTP(S) server for
phone settings
•HTTP(S) server for FW
update
•LAN using fix IP
addresses
Requirements:
•TFTP or HTTP(S) server for
phone settings
•HTTP(S) server for FW
update
Randomly distributed
e.g. distributor or ITSP
network
Requirements:
•Redirection of default
provisioning server
•Phone MAC address
management via snom`s
provisioning console
•Public HTTP(S) server
• PHP knowledge
Mass Deployment: Prerequisites
Interoperability
Technology Leadership
Reasonable Solutions
1: Running TFTP/ HTTP(S) Server and setting file
(HTML or script)
- E.g. http://prov.company.com/settings/snom3xx.htm
- E.g. http://prov.company.com/settings/snom.php
- E.g. tftp://prov.company.com/settings/snom.cfg
2: Configuration of option 66/67 on DHCP server
- Option 66/sname: HTTP/HTTPS/TFTP setting server, e.g.
http://prov.company.com
- Option 67/file: Path to HTML/script setting file, e.g.
settings/snom3xx.htm
3: Factory resetted snomXXX
- Setting Server URL should not have been changed
manually before -> Reset to factory values
Mass Deployment: Setting Files
Interoperability
Technology Leadership
Reasonable Solutions
Setting file structure:
- ASCII-based files
-
lines may end with newline or carriage return/newline pairs
Comments start with a # or a < character
The < and > characters allow easy integration of html tags
Names may consist of the characters a-z, A-Z, 0-9 and _.
- Basically all available settings available on the Web Interfaces
setting page may be used
Mass Deployment: Setting Files
Interoperability
Technology Leadership
Reasonable Solutions
Use ONLY as little settings as necessary:
- General settings e.g:
- language$, timezone$,
- Account specific settings:
- user_pname1$, user_name1$, user_realname1$,
user_host1, user_srtp1$ etc.
- Firmware Update related settings
- firmware_status, update_policy, firmware_interval
Use ONLY „$“ flags at the beginning
- ! = Setting may not be overwritten when it was
changed by the user before
- & or no flag will definitely overwrite existing setting and
mark it „read-only“
Mass Deployment: Setting Files
Interoperability
Technology Leadership
Reasonable Solutions
Do NOT use:
- Network settings:
- dhcp, gateway, dns_server1 etc.
- Setting server URL:
- unless you want to redirect the phone to a different
setting server
- Firmware setting:
- firmware/ bootloader
- use ONLY "firmware_status" instead
- Other internal settings:
- update_server, update_filename, update_host_b,
update_host_f, sip_port, reset_settings, reboot_after_nr,
watch_arp_cache etc.
Mass Deployment: Firmware Update
Interoperability
Technology Leadership
Reasonable Solutions
A firmware configuration file must be located on the
TFTP/ HTTP(s) server
- E.g. http://prov.mycompany.com/settings/firmware.htm
- ASCII-based file
- must ONLY use „firmware“ setting w/o flags:
- firmware: http://.../snom3xx-X.X.bin
The setting file „snom3xx.htm“ links to „firmware.htm“
via firmware_status:
- firmware_status:
http://prov.company.com/settings/firmware.htm
Mass Deployment: Boot- up- process
Interoperability
Technology Leadership
Reasonable Solutions
Part1: Setting provisioning :
•
•
1) Loading settings from the flash memory
if DHCP is enabled it will send an DHCP discover
2) DHCP offer:
phone receives its network settings (IP address, net mask, gateway, DNS server, NTP server etc.)
•
setting server URL [-> update_server]/ setting file path [-> update_filename]
3) No MAC parameter specified & HTML
e.g. http://.../snom3xx.htm
4) Request of general settings file
•
Receiving of settings
•
Writing settings to flash memory
5) Request of the setting file appended by
the phone´s MAC address
e.g. http://.../ snom-000413XXXXX.htm
•
Receiving of phone specific settings
•
Writing settings to flash memory
6) Activating new settings
3) MAC parameter specified & Script
e.g. http://.../snom.php?mac= {mac}
4) Request of the resulting setting file
•
Receiving of both general and phone specific
settings at once
•
Writing settings to flash memory
5) Activating new settings
Mass Deployment: Boot- up- process
Interoperability
Technology Leadership
Reasonable Solutions
Part2: FW update
•
6) Firmware Update Check
phone checks the setting „firmware_status“
7) firmware_status: URL
e.g. http://.../snom3xx-firmware.htm
7) firmware_status: <empty>
8) Request of the firmware configuration file
•
Receiving of the setting „firmware“
•
Comparision of the FW image URL and the last one
stored on the phone
9) FW image URL`s
different
•
FW update will be
performed
9) FW image URL`s
equal
•
FW update will NOT be
performed
Provisioning & FW
Update finished
Provisioning finished
Provisioning finished
Mass Deployment: Example using
HTTP & DHCP
Interoperability
Technology Leadership
Web (HTTP) Server installed on 10.0.0.2:
Reasonable Solutions
Mass Deployment : Example using
HTTP & DHCP
Interoperability
Technology Leadership
Reasonable Solutions
Web (HTTP) Server provides:
- General settings file http://10.0.0.2/snom360.htm
- Specific setting file
http://10.0.0.2/snom360-0004132314A4.htm
- Firmware configuration file
http://10.0.0.2/snom360-firmware.htm
- Firmware image file http://10.0.0.2/snom360-6.5.1-SIP-j.bin
Mass Deployment: Example using
HTTP & DHCP
Interoperability
Technology Leadership
Content of setting files:
- snom360.htm
- snom360-0004132314A4 .htm
Reasonable Solutions
Mass Deployment: Example using
HTTP & DHCP
Interoperability
Technology Leadership
Content of firmware configuration files:
- snom360-firmware.htm
Reasonable Solutions
Mass Deployment: Example using
HTTP & DHCP
Interoperability
Technology Leadership
DHCP Server on 10.0.0.2:
- Option 66: http://10.0.0.2
- Option 67: snom360.htm
Reasonable Solutions
Mass Deployment: Example using
HTTP & DHCP
Interoperability
Technology Leadership
Reasonable Solutions
Snom360:
- Out of the box (factory values)/ Factory value reset
- Power up/ Reboot via SIP NOTIFY
- Boot Up Process
Mass Deployment: Example using
HTTP & DHCP
Interoperability
Technology Leadership
Ethereal analysis
- DHCP Discover/ Offer
Reasonable Solutions
Mass Deployment: Example using
HTTP & DHCP
Interoperability
Technology Leadership
Reasonable Solutions
Ethereal analysis: Plug And Play (PnP) default delay
Mass Deployment: Example using
HTTP & DHCP
Interoperability
Technology Leadership
Reasonable Solutions
Ethereal analysis: HTTP Setting File request
Mass Deployment: Example using
HTTP & DHCP
Interoperability
Technology Leadership
Reasonable Solutions
Snom360: Settings page check
Snom360.htm
Snom360.htm
Snom360-firmware.htm
DHCP: 67
Snom360.htm
Factory Value
DHCP: 66
Factory Value
Mass Deployment: Example using
HTTP & DHCP
Interoperability
Technology Leadership
Snom360: Settings page check
Snom360-0004132414A4.htm
Snom360-0004132414A4.htm
Snom360-0004132414A4.htm
Reasonable Solutions
Mass Deployment: Setting Server
Redirection
Interoperability
Technology Leadership
Reasonable Solutions
Snom phones contact snom provisioning server first
(hardcoded in FW):
- http://provisioning.snom.com/snom3x0/snom3x0.php?mac=
{mac}
- Settings script doesn´t deliver any settings back to the
phone
Distributors may ask for redirection ssh accounts to
redirect the setting server URL to their own (public)
HTTP setting servers
Redirection is based on MAC address registration
Registered MAC addresses will be redirected
Mass Deployment: Setting Server
Redirection
Interoperability
Technology Leadership
Snom provisioning
snom.com
ProvDB
Domain1
Domain2
Domain3
LAN
Reasonable Solutions
Customer ssh account
Welcome, arcor190! Type help for help.
==> help
Welcome to the snom configuration tool.
You may use the following commands:
LAN
Domain1
MACxx1
MACxx2
MACxx3
Firewall
NAT solved
SHOW <mac>
: Show the status of a phone.
REGISTER <mac> : Register a phone.
REG <mac>
: Same as REGISTER.
DEREGISTER <mac>: Deregister a phone.
LIST
: List all phones assigned.
BYE
: Leave this tool.
A MAC address may be entered as 3 to 6 digit
hexadecimal number, case does not matter
(e.g. 2e4 --> 0004132202E4)
==> list
000413101214 00041310123C
LAN
Phone
Registered
Phone
MACxx1
Domain1 config
Domain 1 FW
Phone
Phone
FAX
ATA
Cordless
Mass Deployment: PnP configuration
Interoperability
Technology Leadership
Reasonable Solutions
PnP Config:
- "ON" (by default) the phone sends a SUBSCRIBE message
to a multicast address (224.0.1.75)
- All setting servers which have membership to the group can
respond to the SUBSCRIBE and send NOTIFY messages with
the setting server HTTP URL in the body.
- The phone then retrieves its settings from the link specified.
- This is particularly useful for out of the box setup of devices
and mass deployment.
Interoperability
Technology Leadership
Reasonable Solutions
© 2006 snom technology AG
The author has made his best effort to prepare this document. The content is based upon latest information, whenever possible. The author
makes no representation or warranties of any kind with regard to the completeness or accuracy of the contents herein and accepts no
liability of any kind, including, but not limited to, performance, merchantability, fitness for any particular purpose, or any losses or
damages of any kind caused or alleged to be caused directly or indirectly by this document.
For more information, mail info@snom.com
Gradestr. 46, 12347 Berlin, Germany.