Yealink SIP-T2 Series User manual

Table of Contents
iii

Table of Contents
iii
Table of Contents
Table of Contents .....................................................................iii
Summary of Changes.....................................................................1
Changes for Release 81, Guide Version 81.72 ..............................................................................................1
Changes for Release 81, Guide Version 81.71 ..............................................................................................1
Changes for Release 81, Guide Version 81.70 ..............................................................................................1
Introduction....................................................................................1
Getting Started...............................................................................3
Obtaining the Boot File .........................................................................................................................................3
Obtaining Configuration Files.............................................................................................................................3
Obtaining Phone Information.............................................................................................................................4
Provisioning Yealink IP Phones ....................................................5
Auto Provisioning Process....................................................................................................................................5
Major Tasks for Auto Provisioning....................................................................................................................6
An Instance of Auto Provision Configuration ...............................................................................................7
Managing Boot Files ....................................................................11
Editing Common Boot File ................................................................................................................................ 11
Creating MAC-Oriented Boot File .................................................................................................................. 12
Managing Configuration Files ....................................................15
Editing Common CFG File.................................................................................................................................. 15
Editing MAC-Oriented CFG File....................................................................................................................... 17
Creating a New CFG File..................................................................................................................................... 18
Managing MAC-local CFG File......................................................................................................................... 18
Encrypting Configuration Files......................................................................................................................... 19
Customizing Resource Files .............................................................................................................................. 19
Configuring a Provisioning Server .............................................21
Preparing a Root Directory ............................................................................................................................... 21
Configuring a TFTP Server................................................................................................................................. 22

Yealink IP Phones Auto Provisioning Guide
iv
Obtaining the Provisioning Server Address ..............................25
Zero Touch............................................................................................................................................................... 25
Plug and Play (PnP) Server ................................................................................................................................ 26
DHCP Options ........................................................................................................................................................ 27
Phone Flash ............................................................................................................................................................. 29
Configuring Wildcard of the Provisioning Server URL ........................................................................... 30
Triggering the IP Phone to Perform the Auto Provisioning....33
Power On.................................................................................................................................................................. 33
Repeatedly............................................................................................................................................................... 34
Weekly....................................................................................................................................................................... 35
Flexible Auto Provision ....................................................................................................................................... 36
Auto Provision Now ............................................................................................................................................. 37
Multi-mode Mixed................................................................................................................................................ 38
SIP NOTIFY Message ........................................................................................................................................... 38
Auto Provisioning via Activation Code......................................................................................................... 39
Downloading and Verifying Configurations .............................43
Downloading Boot Files and Configuration Files..................................................................................... 43
Resolving and Updating Configurations ..................................................................................................... 43
Using MAC-local CFG File.................................................................................................................................. 44
Verifying Configurations .................................................................................................................................... 44
Troubleshooting...........................................................................47
Glossary.........................................................................................49
Appendix.......................................................................................51
Configuring an FTP Server................................................................................................................................. 51
Preparing a Root Directory ........................................................................................................................... 51
Configuring an FTP Server............................................................................................................................. 52
Configuring an HTTP Server ............................................................................................................................. 54
Preparing a Root Directory ........................................................................................................................... 54
Configuring an HTTP Server ......................................................................................................................... 55
Configuring a DHCP Server............................................................................................................................... 58
Configuring the DHCP Turbo....................................................................................................................... 59
Add the Option 66 via DHCP Turbo.......................................................................................................... 62

Table of Contents
v
Add the Option 43 via DHCP Turbo.......................................................................................................... 64

Summary of Changes
1
Summary of Changes
This section describes the changes to this guide for each release and guide version.
Changes for Release 81, Guide Version 81.72
Documentations of the newly released CP960 IP phones have also been added.
Changes for Release 81, Guide Version 81.71
Documentations of the newly released CP860/SIP-T54S/T52S IP phones have also been added.
Changes for Release 81, Guide Version 81.70
Documentations of the newly released W56P/W52P/SIP-T58V/T58A/T56A/T40G IP phones have
also been added.

Introduction
1
Introduction
Yealink IP phones are full-featured telephones that can be plugged directly into an IP network
and can be used easily without manual configuration.
This guide provides instructions on how to provision Yealink IP phones with the minimum
settings required. Yealink IP phones support FTP, TFTP, HTTP, and HTTPS protocols for auto
provisioning and are configured by default to use the TFTP protocol.
The purpose of this guide is to serve as a basic guidance for provisioning Yealink IP phones,
including:
Yealink SIP-T58V/A
Yealink SIP-T56A
Yealink SIP-T54S
Yealink SIP-T52S
Yealink SIP-T48G/S
Yealink SIP-T46G/S
Yealink SIP-T42G/S
Yealink SIP-T41P/S
Yealink SIP-T40P/G
Yealink SIP-T29G
Yealink SIP-T27P/G
Yealink SIP-T23P/G
Yealink SIP-T21(P) E2
Yealink SIP-T19(P) E2
Yealink CP860
Yealink CP960
Yealink W52P/W56P
The auto provisioning process outlined in this guide applies to Yealink
SIP-T54S/T52S/46G/T46S/T42G/T42S/T41P/T41S/T40P/T40G/T29G/T27P/T27G/T23P/T23G/
T21(P) E2/T19(P) E2/CP860, W52P and W56P IP phones running firmware version 81 or later
and CP960/SIP-T58V/T58A/T56A IP phones running firmware version 80 or later. We
recommend that IP phones running the latest firmware CANNOT be downgraded to an earlier
firmware version. The new firmware is compatible with old configuration parameters, but not
vice versa.

Yealink IP Phones Auto Provisioning Guide
2

Getting Started
3
Getting Started
This section provides instructions on how to get ready for auto provisioning. To begin the auto
provisioning process, the following steps are required:
Obtaining the Boot File
Obtaining Configuration Files
Obtaining Phone Information
Obtaining the Boot File
You can use a boot file to customize the download sequence of configuration files. The
configuration files are flexible: you can rearrange the configuration parameters within the
Yealink-supplied template configuration files or create your own configuration files from
configuration parameters you want. You can create and name as many configuration files as you
want and your own configuration files can contain any combination of configuration parameters.
It is efficiently for you to provision your IP phones in different deployment scenarios, especially
when you want to apply a set of features or settings to a group of phones.
Before beginning provisioning, you need to obtain the Yealink-supplied template boot file
named as “y000000000000.boot”. The IP phone tries to download the boot file first, and then
download the configuration files referenced in the boot file in sequence during auto
provisioning.
Yealink supports the following two types of boot files:
MAC-Oriented boot file (e.g., 00156574b150.boot)
Common boot file (y000000000000.boot)
You can ask the distributor or Yealink FAE for the template boot file.
Obtaining Configuration Files
Before beginning provisioning, you also need to obtain template 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. You can also create and name as many configuration files as you
want (e.g., account.cfg, sip.cfg, features.cfg) by using the template configuration files. The
custom configuration files can contain the configuration parameters of the same feature
modules for all phones.
If boot file is found on the provisioning server, the IP phones download the boot file first, and
then download the configuration files referenced in the boot file in sequence during auto
provisioning. You can customize the download sequence of configuration files in the boot file as

Yealink IP Phones Auto Provisioning Guide
4
required. If boot file is not found on the provisioning server, IP phones download the common
CFG file first, and then the MAC-Oriented CFG file during auto provisioning –i.e., the old
mechanism for auto provisioning. You can select whether to use the boot file or not for auto
provisioning according to your deployment scenario.
IP phones also support local configuration files named as <MAC>-local.cfg. When a user
modifies configurations via web user interface or phone user interface, the non-static settings
will be automatically saved to the MAC-local CFG file on the IP phone.
You can ask the distributor or Yealink FAE for template configuration files. You can also obtain
the template configuration files online:
http://support.yealink.com/documentFront/forwardToDocumentFrontDisplayPage.
To download template configuration files:
1. Go to Yealink Document Download page and select the desired phone model.
2. Download and extract the combined configuration files to your local system.
For example, the following illustration shows the template files available for SIP-T23G IP
phones running firmware version 80.
3. Open the folder you extracted and identify the files you will edit.
Obtaining Phone Information
Before beginning provisioning, you also need the IP phone information. For example, MAC
address and the SIP account information of the IP phone.
MAC Address: The unique 12-digit serial number of the IP phone. You can obtain it from the
bar code on the back of the IP phone.
SIP Account Information: This may include SIP credentials such as user name, password and IP
address of the SIP server. Ask your system administrator for SIP account information.

Provisioning Yealink IP Phones
5
Provisioning Yealink IP Phones
This section provides instructions on how IP phones interoperate with provisioning server for
auto provisioning, and shows you four major tasks to provision the phones. It will help users
who are not familiar with auto provisioning to understand this process more easily and quickly.
Auto Provisioning Process
When IP phones are triggered to perform auto provisioning, they will request to download the
boot files and configuration files from the provisioning server. During the auto provisioning
process, the IP phone will download and update configuration files to the phone flash.
The following figure shows how the IP phone interoperates with the provisioning server:

Yealink IP Phones Auto Provisioning Guide
6
Major Tasks for Auto Provisioning
You need to complete four major tasks to provision Yealink IP phones.
The following figure shows an overview of four major provisioning tasks:
For more information on how to manage boot files, refer to Managing Boot Files on page 11.
For more information on how to manage configuration files, refer to Managing Configuration
Files on page 15.
For more information on how to configure a provisioning server, refer to Configuring a
Provisioning Server on page 21.
For more information on how to obtain the provisioning server address, refer to Obtaining the
Provisioning Server Address on page 25.
For more information on how to perform the auto provisioning process, refer to Triggering the
IP Phone to Perform the Auto Provisioning on page 33.
If you are not familiar with auto provisioning process on Yealink IP phones, you can refer to An
Instance of Auto Provision Configuration on page 7.

Provisioning Yealink IP Phones
7
An Instance of Auto Provision Configuration
This section shows an instance of auto provision configuration.
1. Manage boot files.
Specify the desired download path (e.g., tftp://10.2.5.193/network.cfg) of the configuration
files in the boot file (e.g., y000000000000.boot). For more information, refer to Managing
Boot Files on page 11.
2. Manage configuration files.
Add/Edit the desired configuration parameters in the CFG file (e.g., features.cfg) you want
the IP phone to download. For more information on how to manage configuration files,
refer to Managing Configuration Files on page 15.
3. Configure the TFTP server.
1) Place boot files and configuration files to TFTP root directory (e.g., D:\TFTP Directory).

Yealink IP Phones Auto Provisioning Guide
8
2) Start the TFTP sever. The IP address of the TFTP server is shown as below:
3) Select Configure TFTP Server. Click the button to locate the TFTP root directory
from your local system.
For more information on how to configure a provisioning server, refer to Configuring a
Provisioning Server on page 21.

Provisioning Yealink IP Phones
9
4. Configure the provisioning server address on the IP phone.
For more information on how to obtain the provisioning server address, refer to Obtaining
the Provisioning Server Address on page 25.
5. Trigger the IP phone to perform the auto provisioning.
For more information on how to trigger the phone to perform the auto provisioning, refer to
Triggering the IP Phone to Perform the Auto Provisioning on page 33.

Yealink IP Phones Auto Provisioning Guide
10

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

Yealink IP Phones Auto Provisioning Guide
12
new downloaded configuration files will override the duplicate parameters in files
downloaded earlier.
“overwrite_mode = 1” means overwrite mode is enabled. The overwrite mode will be
applied to the configuration files specified to download. This parameter can only be used
in boot files. Overwrite mode includes the following features:
-The NULL values take effect (if the value of a parameter in configuration files is left
blank, the factory default value can take effect.)
For example, the label for account 1 is “abc”, and the value of the parameter
“account.1.label” is left blank in the configuration files (e.g., account.1.label = or
account.1.label = “”). The factory default value Blank takes effect after auto
provisioning. So the label for account 1 will be deleted.
-The deletions of the configuration parameters take effect (if a parameter in
configuration files is deleted, the factory default value can take effect immediately.)
For example, account.1.enable = 1 is deleted or commented out in the configuration
files. The factory default value 0 takes effect after auto provisioning. So account 1 is
disabled.
Note that if a boot file is used but the value of the parameter “overwrite_mode” is not
configured, the default value 1 will take effect. If you want to disable the overwrite mode,
configure “overwrite_mode = 0” in the boot file.
Note
Creating MAC-Oriented Boot File
The MAC-Oriented boot file is only effectual for the specific phone. It 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
00156574B150, the MAC-Oriented boot file has to be named as 00156574b150.boot
(case-sensitive) respectively.
The IP phones try to download the MAC-Oriented boot file first from the server during auto
provisioning first. If no matched MAC-Oriented boot file is found on the server, the IP phones
try to download the common boot file.
If you want to create a MAC-Oriented boot file for your phone, follow these steps:
Overwrite mode only affects the non-static settings configured using configuration files.
If you do not use the boot file for auto provisioning,
overwrite mode is disabled by default and
you are not allowed to enable it.