Snom Mass Deployment V7, 3 Series User Manual

Overview | Introduction

firmware updates/ downgrades

Mass Deployment V7

Mass deployment (aka „Auto Provisioning“) is a function which is
implemented proprietorily in the default firmware of all snom 3xx
VoIP phones.

Mass deployment allows remote

configuration

and

maintenance

of an unlimited number of distinct snom phone types.

Mass Deployment is particularly useful for out-of-the-box
scenarios in larger phone installations.

Mass Deployment can be used to provide general and specific
configuration parameters to the phones (aka „Settings“, e.g.
language, timezone, tone scheme, SIP identity) and initiates

.

Slide 1

Overview | Methods

(3) M

l

(4) Aut

(5) Fi

o

DHCP

SIP Subscribe

S

S

bootfile

-

e

)

NOTIFY

Confi

provisioning

adapted

OEM

Mass Deployment V7

Implementation depends on the phone installation environment

Private Local Area Networks

(1) DHCP

Option 66/67

Setting Server URL is

set by DHCP Server

(

tftp-server-name/

nam

(2) Plug & Play

Broadcast

Setting Server

URL is set by SIP

Server via SIP

Any Network

anua

Redirection

N

Redirection

Reserved for Reserved for

DHCP

Option 66/67

Setting Server

URL is set by

Manual

guration

snom partners

(distributors)

etting Server

URL is set by

omatic

snom

server

x

Redirection

snom partner

(OEM)

etting Server

URL is

hardcoded in

Firmware

Slide 2

Setting Server | Types

Provisioning of configuration

Provisioning of

HTTPS

Yes

No

Mass Deployment V7

Setting Server provide configuration parameters and
firmware updates to snom phones.

• TFTP Server, e.g. tftp://mytftpserver

• HTTP (S) Server, e.g. http://provisioning.mycompany.com,
https://10.0.0.2

TFTP Yes From V7.2: Yes

HTTP Yes Yes

Slide 3

parameter

firmware images

Setting Server | Network

p

pg py

Redirection

Redirection

Redirection

Public

No

No

Yes

Yes

Yes

Mass Deployment V7

Setting Server can be hosted on private or public
servers de

Private

ending on the mass deployment method

DHCP Plug & Play Manual

Yes Yes Yes No No

Automatic

Fix

Slide 4

Configuration Parameters | Types

yg

Mass Deployment V7

(1) Write- protected system parameters

• are used internally and cannot be changed

• factory value is marked by „&“ symbol

• For example: mac&: 0004132YXXXX

(2) Unprotected system parameters

• are used internally and can only be changed via mass deployment

• For example: dst!: 3600 03.05.07 02:00:00 10.05.07 03:00:00

(3) Free configurable parameters

• are those settings which can be changed via the web user interface

• For example: dhcp!: on

Slide 5

Configuration Parameters | Settings“ page

Mass Deployment V7

All available configuration parameter types are listed
on the web user interface page „Settings“:

Slide 6

Configuration Parameters | WIKI (1)

•

http://wiki.snom.com/Snom3x0/Web_Interface/V6/Settings

Mass Deployment V7

A description of each configuration parameter and its relationship
to the web user interface configuration can be found on the WIKI:

• http://wiki.snom.com/Snom3x0/Web_Interface/V7/Settings

Slide 7

Configuration Parameters | WIKI (2)

•

http://wiki.snom.com/Settings/parameter_name

Mass Deployment V7

In Version 7 each web user interface configuration menu provides
direct access to the description page of the related parameter

Slide 8

Setting Files | Overview

General settings e.g. language$, timezone$, etc.

g

gyy

Internal parameters

update_server, update_filename, update_host_b, update_host_f

Mass Deployment V7

Setting files are container for configuration parameters.
Use as little parameters as necessary:

•

• Account specific settings, e.g. user_pname1$, user_name1$, user_realname1$, user_host1,
user_srtp1$ etc.

• Firmware Update related settings, e.g. firmware_status, update_policy, firmware_interval

Use „$“ flags at the beginning

•$ Æ The parameter is changeable, but will be overwritten on each reboot. In the web user
interface “Settings” page it will appear as ”!”.

•!

• & or no flag Æ will definitely overwrite existing setting and mark it „read-only“ Æ write

Æ Parameter will not be overwritten when it was chan

protection can only be removed by „Factory Reset“ or mass deployment.

Do NOT use

• Network parmeters (if DHCP is used), e.g. dhcp, gateway, dns_server1 etc.

• Setting server URL unless you want to redirect the phone to a different setting server

• Firmware parameters, i.e. firmware/ bootloader

•
sip_port, reset_settings, reboot_after_nr, watch_arp_cache etc.

Slide 9

, e.g.

ed manually by the user.

Æ use ONLY "firmware_status" instead

,

Setting Files | Syntax

8"?

•

<phone

settings>

<function

keys>, <phone

book>

<dialplan>

<firmware

Mass Deployment V7

Setting files are XML tagged ASCII- based files

• XML header is required

•<?xml version="1.0" encoding="utf-

• The following XML tags are supported

­settings>, <setting-files>, <settings>, <gui-languages>, <phrases>, <web­languages>, <w_phrases>

Configuration parameter

,

-

>

-

Flag ValueIdentity

,

,

-

Index

Slide 10

XML Provisioning | Container <setting-files>

more then one file type in one go

onto the phone

The fil

settings format used before firmware release 7 can be included

Mass Deployment V7

XML container is a file construct which allows to load

<setting-files> tag

• Should be the first XML file provided to the phone

•Contains URL's to all setting files to be provisioned

•

• Backwards compatible: Setting files encoded in the older plain

however the new dial plan format cannot be used in this case.

Slide 11

es are requested in the given order

,

XML Provisioning | Container Files

0

-

Mass Deployment V7

(1) XML Container file for general configuration files and
language files

•

http://ss/snom3x0.htm (due to backwards compatibility reasons in

mixed phone type environments use „htm“ extension instead of „xml“
for automatical phone recognition)

(2) XML Container file for specific configuration and language
files

•

http://ss/snom3x

MAC.htm (the „-MAC“ string is automatically

appended by the phone)

Slide 12