Yealink T58A Teams, Manual

Page: 24 / 65

Auto Provisioning Guide for Yealink
Teams IP
Phones
20
Item Guidelines

The [$MODEL] can be added to the front of configuration
parameter to specify the value for specific phone groups.
$MODEL represents the phone model. The valid phone models
are: T58A, T56A, T55A, VP59 and CP960. Multiple phone models
are separated by commas. For example, [T58A, CP960].
Note: The phone updates model-specific configurations and those
model-unspecified configurations.
Creating a New CFG File
If you want to create a new CFG file for your phone, follow these steps:
To create a new CFG file:
1.
Create a CFG file for your phone. Ensure the file complies with the guidelines that are listed
in
Editing Common CFG File or Editing MAC-Oriented CFG File.
2.
Copy configuration parameters from the template configuration files and set the valid
values for them.
3.
Save the changes and close the CFG file.
You can also make a copy of the template configuration file, rename it and then edit it.
Managing MAC-local CFG File
By default, MAC-local CFG file automatically stores non-static settings modified via web user
interface or phone user interface. This file is stored locally on the IP phone, but a copy can also
be uploaded to the provisioning server. This file enables the phone to keep user’s
personalization settings, even after auto provisioning. As with the MAC-Oriented CFG files,
MAC-local CFG files are only effective 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 phone is
00156574B150, MAC-local CFG file has to be named as 00156574b150-local.cfg (case-sensitive).
If your IP phone with the current firmware version cannot generate a <MAC>-local.cfg file, the
phone will automatically generate a MAC-local CFG file after it is upgraded to the latest
firmware.
For more information on how to keep user’s personalization settings, refer to the latest
Administrator Guide for your phone on
Yealink Technical Support .