Yealink SIP-T23 User manual

Table of Contents
i

Yealink IP Phones Auto Provisioning Guide
ii

Table of Contents
iii
Table of Contents......................................................................iii
Introduction............................................................................... 1
Getting Started......................................................................... 3
Obtaining Configuration Information ................................................................................ 3
Obtaining Configuration Files ......................................................................................... 3
Obtaining Phone Information .......................................................................................... 4
Managing Configuration Files............................................................................................ 4
Editing Common CFG File................................................................................................ 4
Editing MAC-Oriented CFG File...................................................................................... 6
Managing MAC-local CFG File....................................................................................... 7
Encrypting Configuration Files ...................................................................................... 10
Customizing Resource Files............................................................................................ 10
Configuring a TFTP Server...................................................... 27
Preparing a Root Directory................................................................................................ 27
Configuring a TFTP Server................................................................................................. 28
Obtaining the Provisioning Server Address .......................... 29
Zero Touch........................................................................................................................... 29
Plug and Play (PnP) Server ............................................................................................... 31
DHCP Options..................................................................................................................... 32
Phone Flash......................................................................................................................... 34
Configuring Wildcard of the Provisioning Server URL.................................................... 35
Configuring the Update Mode .............................................. 37
Power On............................................................................................................................. 37
Repeatedly.......................................................................................................................... 38
Weekly ................................................................................................................................. 39
Auto Provision Now ............................................................................................................ 40
Multi-mode Mixed ............................................................................................................. 41
SIP NOTIFY Message ......................................................................................................... 41
Auto Provisioning via Activation Code ............................................................................ 42

Yealink IP Phones Auto Provisioning Guide
iv
Downloading and Verifying Configurations .......................... 45
Downloading Configuration Files..................................................................................... 45
Resolving and Updating Configurations ......................................................................... 45
Downloading and Updating <MAC>-local.cfg File...................................................... 46
Verifying Configurations .................................................................................................... 46
Specific Scenarios.............................................................................................................. 48
Configuration Parameters.............................................................................................. 48
Scenario A Protect personalized configuration settings ............................................ 50
Scenario B Clear personalized configuration settings ............................................... 52
Scenario C Protect personalized settings after factory reset .................................... 53
Scenario D Import or export the local configuration file ............................................ 55
Troubleshooting ...................................................................... 59
Glossary.................................................................................. 61
Appendix ................................................................................ 63
Configuring an FTP Server ................................................................................................ 63
Preparing a Root Directory ............................................................................................ 63
Configuring an FTP Server ............................................................................................. 64
Configuring an HTTP Server.............................................................................................. 67
Preparing a Root Directory ............................................................................................ 67
Configuring an HTTP Server .......................................................................................... 68
Configuring a DHCP Server .............................................................................................. 71
Customizing a Ring Tone Using Cool Edit Pro ................................................................. 77
Customizing a Logo File Using PictureExDemo .............................................................. 79
Auto Provisioning Flowchart (Protect personalized configuration settings)................ 80
Description of Configuration Parameters in CFG Files .................................................. 81
Programmable Keys ........................................................................................................ 310
Time Zones........................................................................................................................ 312
BLF LED Mode................................................................................................................... 315

Introduction
1
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-T23
Yealink SIP-T23P
Yealink SIP-T23G
The auto provisioning process outlined in this guide applies to Yealink SIP-T23 (P/G) IP
phones running firmware version X.80.0.5 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
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:
Phone Model
Common CFG File
SIP-T23 (P/G)
y000000000044.cfg
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:

Yealink IP Phones Auto Provisioning Guide
4
http://www.yealink.com/DocumentDownload.aspx?CateId=142&flag=142
To download Common CFG and MAC-Oriented files:
1. Go to Yealink Document Download Page and select the desired phone model under
the Documents and Download tab.
2. Download and uncompress the combined configuration files to your local system.
3. Open the folder you uncompressed to and identify the files you will edit according
to the table introduced above.
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.
Auto provisioning enables Yealink IP phones to update themselves automatically via
downloading Common CFG and MAC-Oriented CFG files. Before beginning
provisioning, you may need to edit and customize your configuration files. Open each
configuration file with a text editor such as UltraEdit. For more information on
configuration parameters in configuration files, refer to Description of Configuration
Parameters in CFG Files on page 81
Common CFG file contains configuration parameters which apply to phones with the
same model, such as language and volume.

Getting Started
5
The following figure shows a portion of the common CFG file:
The partial parameters in the Common CFG file are described as follows:
####################################################
## Common CFG File ##
####################################################
#!version:1.0.0.1
##File header "#!version:1.0.0.1" cannot be edited or deleted, and must be placed in
the first line. This template file is applicable to SIP-T28P/T26P/T23 (P/G)
/T22P/T21P/T20P/T19P/T48G/T46G/T42G/T41P IP phones running firmware version 72 or
later. For more information on configuration parameters, refer to
Yealink_SIP-T2_Series_T19P_T4_Series_IP_Phones_Auto_Provisioning_Guide . ##
######################################################
## Hostname ##
######################################################
network.dhcp_host_name =
######################################################
## PPPoE(Except T41P/T42G Models) ##
######################################################
network.pppoe.user =
network.pppoe.password =
######################################################
## Network Advanced ##
######################################################
##It enables or disables the PC port.0-Disabled,1-Auto Negotiation.
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.

Yealink IP Phones Auto Provisioning Guide
6
##The default value is 1.It takes effect after a reboot.
network.pc_port.enable =
##It configures the transmission mode and speed of the Internet (WAN) port.
##0-Auto negotiate
##1-Full duplex 10Mbps
##2-Full duplex 100Mbps
##3-Half duplex 10Mbps
##4-Half duplex 100Mbps
##5-Full duplex 1000Mbps (only applicable to SIP-T23 (P/G), SIP-T42G and SIP-T46G IP
phones)
##The default value is 0.It takes effect after a reboot.
network.internet_port.speed_duplex =
MAC-Oriented CFG file contains configuration parameters which are expected to be
updated per phone, such as the registration information.
The following figure shows a portion of the MAC-Oriented CFG file:
The partial parameters in the MAC-Oriented CFG file are described as follows:
####################################################
## MAC-Oriented CFG File ##
####################################################
#!version:1.0.0.1
##File header "#!version:1.0.0.1" cannot be edited or deleted, and must be placed in
the first line. This template file is applicable to SIP-T28P/T26P/T23
(P/G)/T22P/T21P/T20P/T19P/ T48G/T46G/T42G/T41P IP phones running firmware version 72
or later. For more information on configuration parameters, refer to
Yealink_SIP-T2_Series_T19P_T4_Series_IP_Phones_Auto_Provisioning_Guide . ##
######################################################
## Account1 Basic Settings ##
######################################################

Getting Started
7
account.1.enable =
account.1.label =
account.1.display_name =
account.1.auth_name =
account.1.user_name =
account.1.password =
account.1.outbound_proxy_enable =
account.1.outbound_host =
account.1.outbound_port =
account.1.dial_tone =
account.1.update_sip_call_id =
##It configures the transport type for account 1. 0-UDP,1-TCP,2-TLS,3-DNS-NAPTR
##The default value is 0.
account.1.sip_server.1.transport_type =
account.1.sip_server.2.transport_type =
MAC-local CFG file is automatically filled with configurations modified via web user
interface or phone user interface. The file is stored locally on the IP phone and can also
be uploaded to the provisioning server.
If your IP phone’s current firmware version doesn’t support generating a
<MAC>-local.cfg file, the IP phone will automatically generate a MAC-local CFG file
after it is upgraded to the latest firmware.
Uploading and downloading the <MAC>-local.cfg file
You can configure whether the IP phone periodically uploads the <MAC>-local.cfg file
to the provisioning server to back up this file, and downloads the <MAC>-local.cfg file
from the provisioning server during auto provisioning to override the one stored on the
phone. This process is controlled by the value of the parameter
“auto_provision.custom.sync”. When the value of the parameter
“auto_provision.custom.sync”is set to 1, the IP phone will periodically upload the
configuration files to the provisioning server, and download the configuration files from
the provisioning server during auto provisioning.
For more information on how to configure this parameter, refer to Configuration
Parameters on page 48.
SIP-T23/T23P/T23G IP phones support 3 accounts.

Yealink IP Phones Auto Provisioning Guide
8
Updating the <MAC>-local.cfg file
You can configure whether the IP phone updates configurations in the <MAC>-local.cfg
file during auto provisioning. This process is controlled by the value of the parameter
“auto_provision.custom.protect”. When the value of the parameter
“auto_provision.custom.protect”is set to 1, the IP phone will update the configurations in
the <MAC>-local.cfg file during auto provisioning. The configurations in the
<MAC>-local.cfg file take precedence over the ones in the downloaded Common CFG
file or <MAC>.cfg file. As a result, the personalized settings of the phone configured via
the phone or web user interface can be remained after auto provisioning.
For more information on how to configure this parameter, refer to Configuration
Parameters on page 48.
Note: The following configurations are defined never to be saved to the
<MAC>-local.cfg file, even if a user modifies the configurations via web user interface
or phone user interface:
Configurations associated with the password.
For example,
#Configure the password for PPPoE connection.
network.pppoe.password =
For more information on the specific configurations which associated with the
password, refer to Description of Configuration Parameters in CFG Files on page
81.
Configurations requiring a reboot during auto provisioning.
For example,
#Configure the IP address mode.
network.ip_address_mode=
For more information on the specific configurations which require a reboot during auto
provisioning, refer to Description of Configuration Parameters in CFG Files on page
81.
The following configuration parameters.
#Configure always forward feature.
forward.always.enable =
forward.always.target =
forward.always.on_code =
forward.always.off_code =
#Configure busy forward feature.
forward.busy.enable =
forward.busy.target =
forward.busy.on_code =

Getting Started
9
forward.busy.off_code =
#Configure no answer forward feature.
forward.no_answer.enable =
forward.no_answer.target =
forward.no_answer.timeout =
forward.no_answer.on_code =
forward.no_answer.off_code =
#Configure DND feature.
features.dnd.enable =
features.dnd.on_code =
features.dnd.off_code =
#Configure always forward feature for account X.
account.X.always_fwd.enable =
account.X.always_fwd.target =
account.X.always_fwd.on_code =
account.X.always_fwd.off_code =
#Configure busy forward feature for account X.
account.X.busy_fwd.enable =
account.X.busy_fwd.target =
account.X.busy_fwd.on_code =
account.X.busy_fwd.off_code =
#Configure no answer forward feature for account X.
account.X.timeout_fwd.enable =
account.X.timeout_fwd.target =
account.X.timeout_fwd.timeout =
account.X.timeout_fwd.on_code =
account.X.timeout_fwd.off_code =
#Configure DND feature for account X.
account.X.dnd.enable =
account.X.dnd.on_code =
account.X.dnd.off_code =
#Configure the access URL of the firmware file.
firmware.url =
#Configure the access URL of configuration files.
auto_provision.server.url=
Note: The following configurations are defined to be bundled together. If a user modifies
one of the configurations in a bundled group via web user interface or phone user

Yealink IP Phones Auto Provisioning Guide
10
interface, the other configurations in this group can also be saved to the
<MAC>-local.cfg file (if the parameter isn't configured, the value of this parameter will
be written by “%NULL%”) in addition to the modified configuration.
#Group1: Configure line key.
linekey.X.line =
linekey.X.value =
linekey.X.pickup_value =
linekey.X.type =
linekey.X.xml_phonebook =
linekey.X.label =
#Group2: Configure programable key.
programablekey.X.type =
programablekey.X.line =
programablekey.X.value =
programablekey.X.xml_phonebook =
programablekey.X.history_type =
programablekey.X.label =
To protect against unauthorized access and tampering of sensitive information (e.g.,
login password, registration information), you can encrypt configuration files using
Yealink Configuration Encryption Tool. AES keys must be 16 characters and the
supported characters contain: 0 ~ 9, A ~ Z, a ~ z and the following special characters are
also supported: # $ % * +, - . : = ? @ [ ] ^ _ { } ~. For more information on how to encrypt
configuration files, refer to Yealink Configuration Encryption Tool User Guide .
When configuring some particular features, you may need to upload resource files to IP
phones, such as personalized ring tone file, language package file and logo file. Yealink
supplies some resource file templates for the particular features. Ask the distributor or
Yealink FAE for resource file templates. The following provides information on how to
customize resource files and specify the access URL for the resource files.
We recommend you do not edit the MAC-local CFG file. If you really want to edit
MAC-local CFG file, you can export and then edit it. For more information on how to
export this file, refer to Scenario D Import or export the local configuration file on
page 55. For more information on how to edit this file, refer to Editing Common CFG
File on page 4 and Editing MAC-Oriented CFG File on page 6.

Getting Started
11
Yealink IP phones have built-in system ring tones. You can change the ring type, or
customize a ring tone and upload it to the IP phone via auto provisioning.
The ring tone file must meet the following:
Phone Model
File Format
Single File Size
Total Files Size
SIP-T23 (P/G)
.wav
<=100KB
<=100KB
For more information on customizing a ring tone file, refer to Customizing a Ring Tone
Using Cool Edit Pro on page 77.
####################################################
## Configure the custom ring tone ##
####################################################
#Specify the access URL of the custom ring tone.
ringtone.url =
For example, enter “tftp://192.168.1.100/Customring.wav” in the “ringtone.url =” field.
During the auto provisioning process, the IP phone connects to the provisioning server
“192.168.1.100”, and downloads the ring tone file “Customring.wav”.
To use the custom ring tone for the IP phone, you also need to configure the following
parameter:
#Configure the custom ring tone (e.g., Customring.wav) for the IP phone.
phone_setting.ring_type = Customring.wav
To use the custom ring tone for the desired account, you also need to configure the
following parameter:
#Configure the custom ring tone (e.g., Customring.wav) for account 1.
account.1.ringtone.ring_type = Customring.wav
#Delete all custom ring tones.
ringtone.delete = http://localhost/all
For more information on these parameters, refer to Description of Configuration
Parameters in CFG Files on page 81.
You can modify the existing language translation for phone and web user interface. You
can also add a new language (not included in the available language list) to IP phones.
The ring tone file must be PCMU audio format, mono channel, 8K sample rate and 16 bit
resolution.

Yealink IP Phones Auto Provisioning Guide
12
The following table lists available languages and the associated language files for
phone user interface:
Available Language
Associated Language File
English
000.GUI.English.lang
Simplified Chinese
001.GUI.Chinese_S.lang
Traditional Chinese
002.GUI.Chinese_T.lang
German
003.GUI.German.lang
French
004.GUI.French.lang
Italian
005.GUI.Italian.lang
Polish
006.GUI.Polish.lang
Portuguese
007.GUI.Portuguese.lang
Spanish
008.GUI.Spanish.lang
Turkish
009.GUI.Turkish.lang
Russian
010.GUI.Russian.lang

Getting Started
13
The following figure shows a portion of a lang formatted English language file:
####################################################
## Configure the custom LCD language file ##
####################################################
#Specify the access URL of the custom LCD language file.
gui_lang.url =
If you want to modify the existing language translation for the IP phone user interface,
edit the language translation and then configure the parameter “gui_lang.url =” in the
configuration file, for example:
gui_lang.url = tftp://192.168.1.100/000.GUI.English.lang
During the auto provisioning process, the IP phone connects to the provisioning server
“192.168.1.100”, and downloads the language file “000.GUI.English.lang”. The
language translation will be changed accordingly.

Yealink IP Phones Auto Provisioning Guide
14
If you want to add a new language “wuilan”to SIP-T23G IP phones, prepare the
language file named as 011.GUI.wuilan.lang for downloading and configure the
parameter “gui_lang.url =” in the configuration file, for example:
gui_lang.url = tftp://192.168.1.100/011.GUI.wuilan.lang
During the auto provisioning process, the SIP-T23G IP phone connects to the provisioning
server “192.168.1.100”, and downloads the language file “011.GUI.wuilan.lang”. After
update, you will find a new language selection “wuilan”on the IP phone user interface:
Menu->Settings->Basic Settings->Language.
To use the custom language for the IP phone, you also need to configure the following
parameter:
#Configure the custom language (e.g., English) for the phone user interface.
lang.gui = English
#Delete all custom languages.
gui_lang.delete = http://localhost/all
For more information on these parameters, refer to Description of Configuration
Parameters in CFG Files on page 81.
The note information is integrated in the icon of the web user interface. When you
add a new language for the web user interface, you also need to add the note
language.
The following table lists available languages and the associated language files for web
user interface:
Available Language
Associated Language
Pack
Associated Note Language
Pack
English
1.English.js
1.English_note.xml
Simplified Chinese
2.Chinese_S.js
2.Chinese_S_note.xml
Traditional Chinese
3.Chinese_T.js
3.Chinese_T_note.xml
German
4.French.js
4.French_note.xml
French
5.German.js
5.German_note.xml
Italian
6.Italian.js
6.Italian_note.xml
For existing language files, “X”ranges from 000 to 010. For custom language files, X must
start from 011. “Y”means the language name.
Available languages may vary between different firmware versions.
To modify translation of an existing language, do not rename the language file.

Getting Started
15
Available Language
Associated Language
Pack
Associated Note Language
Pack
Polish
7.Polish.js
7.Polish_note.xml
Portuguese
8.Portuguese.js
8.Portuguese_note.xml
Spanish
9.Spanish.js
9.Spanish_note.xml
Turkish
10.Turkish.js
10.Turkish_note.xml
Russian
11.Russian.js
11.Russian_note.xml
The following figure shows a portion of a js formatted English language file:

Yealink IP Phones Auto Provisioning Guide
16
The following figure shows a portion of an xml formatted English note language file:
####################################################
## Configure the custom web and note language files ##
####################################################
#Specify the access URL of the custom web language file.
wui_lang.url =
#Specify the access URL of the custom note language file.
wui_lang_note.url =
If you want to modify the existing language translation for the web user interface, edit
the language translation and then configure the parameter “wui_lang.url =” in the
configuration file, for example:
wui_lang.url = tftp://192.168.1.100/1.English.js
During the auto provisioning process, the IP phone connects to the provisioning server
“192.168.1.100”, and downloads the language file “1.English.js”. The language
translation will be changed accordingly.
If you want to add a new language “wuilan”to IP phones, prepare the language file
named as 12.wuilan.js and 12.wuilan_note.xml for downloading and configure the
parameter “gui_lang.url =” and “wui_lang_note.url”in the configuration files, for
example:
gui_lang.url = tftp://192.168.1.100/12.wuilan.js
wui_lang_note.url = tftp://192.168.1.100/12.wuilan_note.xml
During the auto provisioning process, the IP phone connects to the provisioning server
“192.168.1.100”, and downloads the language files “12.wuilan.js”and
“12.wuilan_note.xml”. After update, you will find a new language selection “wuilan”on
the web user interface: Setting->Preference->Language, and new note information is
integrated in the icon when the new language is selected.