Getting Started
3
This section provides instructions on how to get ready for auto provisioning. The auto
provisioning process discussed in this guide uses the TFTP server as the provisioning
server.
To begin the auto provisioning process, the following steps are required:
Obtaining Configuration Information
Managing Configuration Files
Before beginning provisioning, you need to obtain configuration files. There are two
configuration files both of which are CFG-formatted. We call these two files Common
CFG file and MAC-Oriented CFG file. The IP phone tries to download these CFG files
from the server during auto provisioning.
IP phones also support a local configuration file named as <MAC>-local.cfg. When a
user modifies configurations via web user interface or phone user interface, the
configurations will be automatically saved to the MAC-local CFG file on the IP phone.
The MAC-Oriented and MAC-local CFG files are only effectual for the specific phone.
They use the 12-digit MAC address of the IP phone as the file name. For example, if the
MAC address of the IP phone is 0015651130F9, the MAC-Oriented CFG and MAC-local
CFG files have to be named as 0015651130F9.cfg and 0015651130F9-local.cfg
respectively. However, the Common CFG file is effectual for all phones of the same
model. It uses a fixed name “y0000000000XX.cfg” as the file name, where "XX" equals to
the first two digits of the hardware version of the IP phone model.
The names of the Common CFG file for the phone model is:
The IP phones can only recognize configuration files using UTF-8 or ANSI encoding.
The <MAC>-local.cfg can be exported/imported via web user interface. For more
information on how to export/import the <MAC>-local.cfg file, refer to Scenario D
Import or export the local configuration file on page 55.
You can ask the distributor or Yealink FAE for Common CFG and MAC-Oriented files. You
can also obtain the Common CFG file and MAC-Oriented file online:
To Next Page
Loading...
Need help?
General