Configuration Files - Yealink SIP-T48G Administrator's Manual

Microsoft Lync Edition Administrator's Guide for SIP-T2_Series and T4_Series IP Phones
An administrator can deploy and maintain a mass of IP phones using configuration files.
The configuration files consist of:
Common CFG file

MAC-Oriented CFG file

Common CFG file
A Common CFG file contains parameters that affect the basic operation of the IP phone,
such as language and volume. It will be effectual for all IP phones of the same model.
The common CFG file has a fixed name for each IP phone model. The name of the
Common CFG file for each IP phone model is:
SIP-T48G: y000000000035.cfg

SIP-T22(P): y000000000005.cfg

MAC-Oriented CFG file
A MAC-Oriented CFG file contains parameters unique to a particular phone. It will only
be effectual for a specific IP phone. The MAC-Oriented CFG file is named after the MAC
address of the IP phone. For example, if the MAC address of an IP phone is
00156574B150, the name of the MAC-Oriented CFG file must be 00156574b150.cfg
(case-sensitive).
Central Provisioning
IP phones can be centrally provisioned from a provisioning server using the
configuration files (<y0000000000xx>.cfg and <MAC>.cfg). You can use a text-based
editing application to edit configuration files, and then store configuration files to a
provisioning server. For more information on the provisioning server, refer to
Server on page 20.
IP phones can obtain the provisioning server address during startup. Then IP phones
download configuration files from the provisioning server, resolve and update the
configurations written in configuration files. This entire process is called auto
provisioning. For more information on auto provisioning, refer to Yealink IP Phones Auto
Provisioning Guide, available online:
http://www.yealink.com/DocumentDownload.aspx?CateId=142&flag=142.
When modifying parameters, learn the following:
Parameters in configuration files override those stored in the IP phone's flash

memory by default.
The .cfg extension of configuration files must be in lowercase.

Each line in a configuration file must use the following format and adhere to the

following rules:
18
Provisioning