Yealink SIP-T48G [9/384] Getting started

Getting Started

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 (case-sensitive) and

0015651130f9-local.cfg (case-sensitive) 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:

Phone Model

Common CFG File

SIP-T48G

y000000000035.cfg

SIP-T46G

y000000000028.cfg

SIP-T42G

y000000000029.cfg

SIP-T41P

y000000000036.cfg

SIP-T29G

y000000000046.cfg