Bedienungsanleitung Snom M200 SC Base Station (Seite 62 von 120) (Englisch)

809886

Zoom out

Zoom in

Vorherige Seite

1/120

Nächste Seite

v1.01

M200SC Administrator and Provisioning Manual Provisioning using conﬁguration ﬁles

The provisioning process

The automatic provisioning process is as follows:

1. Check for new or updated conﬁguration ﬁles. For ﬁle-checking options, see "Provisioning" on page 51

and "Resynchronization" on page 53. The M200SC maintains a list of the last loaded provisioning ﬁles.

The M200SC compares its current conﬁguration against the ﬁles it ﬁnds on the provisioning server.

If provisioning has been triggered by the resync timer expiring or by remote check-sync, the M200SC checks

for updated ﬁles after one minute of inactivity.

2. Download the conﬁguration ﬁles.

If any ﬁle on the provisioning server has changed, the M200SC treats it as a new ﬁle and downloads it.

If the provisioning URL speciﬁes a path only with no ﬁlename (if the URL ends with “/”), then by default the

M200SC looks for and retrieves the following two ﬁles by appending the two default ﬁlenames to the URL:

-General ﬁle: <model>.cfg.

-MAC-speciﬁc ﬁle: <model>_<MAC Address>.cfg.

The <model> variable is the Snom product model: M200SC, for example.

If the provisioning URL contains a query element (?), or if a ﬁlename ending in “.cfg” is speciﬁed at the end of

the provided URL path, then the M200SC retrieves only the conﬁguration ﬁle speciﬁed.

3. The M200SC restarts after one minute of inactivity.

4. During provisioning, the M200SC reads the conﬁguration ﬁle and validates each module and setting. The

M200SC considers a setting valid if it is:

-a valid data type

-formatted as a valid setting

-within a valid data range

- part of a module that passes an integrity check. That is, the module’s settings are consistent and

logical. For example, in the “network” module, if DHCP is disabled, but no static IP address is

speciﬁed, the module will fail the integrity check and none of the settings will apply.

5. Invalid modules or invalid settings are skipped and logged as ERROR messages in the system log, but will

not interrupt the provisioning process. The system log will include the module parameters that have not

been applied. A recognized module with unrecognized settings will cause all other settings in that module

to be skipped.

6. A successful conﬁguration or ﬁrmware update is reported as an INFO message in the system log.

See "Conﬁguration ﬁle parameter guide" on page 67 for the options and value ranges available for each

conﬁguration ﬁle setting.

Resynchronization: conﬁguration ﬁle checking

You can select a number of options that determine when the M200SC checks for new conﬁguration ﬁles. This

process of checking for conﬁguration ﬁles is called Resynchronization. Resynchronization options are available

on the WebUI Provisioning page, but you can also include them in a conﬁguration ﬁle.

The resynchronization options are:

◦ Mode—setting the M200SC to check for a conﬁguration ﬁle only, a ﬁrmware update ﬁle only, or both

types of ﬁle.

◦Never—conﬁguration ﬁle checking is disabled

◦ Bootup—the M200SC checks for new conﬁguration ﬁles when it boots up. Any updates are applied

during the boot-up process.

Missbrauch melden von Frage und/oder Antwort

Libble nimmt den Missbrauch seiner Dienste sehr ernst. Wir setzen uns dafür ein, derartige Missbrauchsfälle gemäß den Gesetzen Ihres Heimatlandes zu behandeln. Wenn Sie eine Meldung übermitteln, überprüfen wir Ihre Informationen und ergreifen entsprechende Maßnahmen. Wir melden uns nur dann wieder bei Ihnen, wenn wir weitere Einzelheiten wissen müssen oder weitere Informationen für Sie haben.

Snom M200 SC Base Station Seite 62

Brauchen Sie Hilfe? Stellen Sie Ihre Frage.

Missbrauch melden von Frage und/oder Antwort

Art des Missbrauchs:

Forenregeln

Neu registrieren

Das Handbuch wird per E-Mail gesendet. Überprüfen Sie ihre E-Mail.

Ihre Frage wurde zu diesem Forum hinzugefügt

Info