Yealink SIP-CP Series, Руководство по автоматической настройке

Страница: 19 / 74

Managing Boot Files
11
Managing Boot Files
Yealink IP phones support downloading CFG files referenced in the boot files in sequence.
Before beginning provisioning, you may need to edit and customize your boot files.
You can edit the template boot file directly or create a new boot file as required. Open each
boot file with a text editor such as UltraEdit.
Editing Common Boot File
The common boot file is effectual for all phones. It uses a fixed name “y000000000000.boot” as
the file name.
The following figure shows the contents of the common boot file:
When editing the boot file, learn the following:

The line beginning with “#” is considered to be a comment.

The file header “#!version:1.0.0.1” is not a comment and must be placed in the first line. It
cannot be edited or deleted.

The file format must be *.boot.

Each “include” statement can reference a configuration file. The referenced configuration
file format must be *.cfg. The “include” statement can be repeated as many times as
needed. It means one or more CFG files can be referenced in the boot file.

Each “include” statement must use the following format:
include:config < download path of the CFG file > or include:config “ download path of the
CFG file ”
The download path of the CFG file must point to a specific CFG file. It supports the
following path forms:
- Relative path (relative to the boot file):
For example, sip.cfg, HTTP Directory/sip.cfg, ../sip.cfg, etc.
- Absolute path (or URL):
For example, http://10.2.5.258/HTTP Directory/sip.cfg.

The CFG files are downloaded in the order listed (top to bottom). The parameters in the