Yealink SIP-T2xP IP Phone Family Administrator Guide - V2.1

Copyright 2012 YEALINK NETWORK TECHNOLOGY Copyright 2012 Yealink Network Technology CO., LTD. All rights reserved.
d. No parts of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, photocopying, recording, or otherwise, for any purpose, without the express written permission of Yealink Network Technology CO., LTD. Under the law, reproducing includes translating into another language or format. When this publication is made available on media, Yealink Network Technology CO., LTD. gives its consent to downloading and printing copies of the content provided in this file only for private use and not for redistribution. No parts of this publication may be subject to alteration, modification or commercial use. Yealink Network Technology CO., LTD. will not be liable for any damages arising from use of an illegally modified or altered publication.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS GUIDE ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS GUIDE ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF PRODUCTS. YEALINK NETWORK TECHNOLOGY CO., LTD. MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS GUIDE, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Yealink Network Technology CO., LTD. shall not be liable for errors contained herein nor for incidental or consequential damages in connection with the furnishing, performance, or use of this guide.
Hereby, Yealink Network Technology CO., LTD. declares that this phone is in conformity with the essential requirements and other relevant provisions of the CE, FCC.
This device is marked with the CE mark in compliance with EC Directives 2006/95/EC and 2004/108/EC.
This device is compliant with Part 15 of the FCC Rules. Operation is subject to the following two conditions: 1. 2. This device may not cause harmful interference, and This device must accept any interferences received, including interference that may cause undesired operation.
Note: This device is tested and complies with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: 1. 2. 3. 4. Reorient or relocate the receiving antenna. Increase the separation between the equipment and receiver. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experience radio/TV technician for help.
To avoid the potential effects on the environment and human health as a result of the presence of hazardous substances in electrical and electronic equipment, end users of electrical and electronic equipment should understand the meaning of the crossed-out wheeled bin symbol. Do not dispose of WEEE as unsorted municipal waste and have to collect such WEEE separately.
About This Guide
The Yealink SIP-T2xP IP Phone Family Administrator Guide is considered to be an administration-level version, which is intended for administrators who need to properly configure, customize, manage, and troubleshoot Yealink IP phone systems rather than the end-users of the IP phones. It includes details on the functioning and configuration of the IP phones. Many of the features are described in this guide involving the network settings, which could affect the phones performance in the network. For this reason, an understanding of IP networking and prior knowledge of IP telephony concepts are recommended.
This guide covers the Yealink SIP-T28P , T26P , T22P and T20P IP phones. The following related documents for the SIP-T2xP IP phones are available:

Quick Installation Guides, which describe how to assemble the IP phones. Quick Reference Guides, which describe the most basic features available on the IP phones.
User Guides, which describe the basic and advanced features available on the IP phones.
Yealink Auto Provisioning User Guide, which describes how to auto provision the IP phones using the configuration files.
Yealink Configuration Conversion Tool User Guide, which describes how to encrypt the configuration files using the Configuration Conversion Tool.
<y0000000000xx>.cfg and <MAC>.cfg template configuration files. Yealink IP Phones Deployment Guide for BroadWorks Environments, which describes how to configure the BroadSoft features on the BroadWorks web portal and the IP phones.
For support or service, please contact your Yealink reseller or go to Yealink Technical Support at http://www.yealink.com/index.php/Faq/lists/classid/2.
The information detailed in this guide is applicable to the firmware version 70 or higher. This administrator guide is divided into the following chapters:

Chapter 1, Product Overview describes the SIP components and SIP IP phones. Chapter 2, Getting Started describes how to install and connect the Yealink SIP IP v
Administrator s Guide for SIP-T2xP IP Phones
phones and the IP phone interface methods.
Chapter 3, Configuring Basic Features describes how to configure the basic features on the IP phones.
Chapter 4, Configuring Advanced Features describes how to configure the advanced features on the IP phones.
Chapter 5, Security Features describes the encryption information of the IP phones.
Chapter 6, Upgrading the Firmware describes how to upgrade the firmware of the IP phones.
Chapter 7, Resource Files describes the resource files that can be downloaded by the IP phones.
Chapter 8, Troubleshooting describes how to troubleshoot the IP phones and provides some common troubleshooting solutions.
Chapter 9, Appendix provides the glossary, reference information about the IP phones comply with RFC 3261, SIP call flows and the sample configuration file.
The following sections are new for this version:

BLF Call Park on page 44 Web Server Type on page 46 Tones on page 52 Action URL on page 60 Action URI on page 63 Resource Files on page 83 Appendix B: Configuration Parameters on page 101 Appendix E: Sample Configuration File on page 227
Major updates have occurred to the following sections:

Creating Dial Plan on page 21 Phone Lock on page 27 Time and Date on page 28 Busy Lamp Field on page 57 Shared Call Appearance on page 58
vi
About This Guide
Major updates have occurred to the following sections:

Creating Dial Plan on page 21 Do Not Disturb (DND) on page 35 Call Forward on page 38 802.1X Authentication on page 70
vii
Table of Contents
About This Guide ...................................................................... v

Documentations ............................................................................................................................... v In This Guide .................................................................................................................................... v Changes from Previous Versions ................................................................................................... vi Changes from Version 1.0 ....................................................................................................... vi Changes from Version 2.0 ...................................................................................................... vii
Table of Contents ..................................................................... 1 Product Overview ..................................................................... 1

VoIP Principle.................................................................................................................................... 1 SIP Components............................................................................................................................... 2 SIP IP Phone Models ........................................................................................................................ 3 Physical Features of the SIP-T2xP IP Phones ........................................................................... 4 Key Features of the SIP-T2xP IP Phones ................................................................................... 8
Getting Started ....................................................................... 11

Connecting the Phone ................................................................................................................... 11 Installing the SIP-T28P and SIP-T26P IP Phones...................................................................... 11 Installing the SIP-T22P and SIP-T20P IP Phones...................................................................... 13 Initialization Process Overview .................................................................................................... 15 Verifying Startup ............................................................................................................................ 17 Configuration Interfaces ............................................................................................................... 17 Phone User Interface.............................................................................................................. 17 Web User Interface ................................................................................................................ 17 Configuration Files.................................................................................................................. 18 Reading Icons ................................................................................................................................ 19 Configuring Network Parameters Manually ............................................................................... 20 Creating Dial Plan ......................................................................................................................... 21 Replace Rule ........................................................................................................................... 22 Dial-now .................................................................................................................................. 23 Area Code............................................................................................................................... 23 Block Out ................................................................................................................................. 24
Configuring Basic Features .................................................... 25

User Password ............................................................................................................................... 26 1
Administrator Password ................................................................................................................ 26 Phone Lock ..................................................................................................................................... 27 Time and Date ............................................................................................................................... 28 Language ....................................................................................................................................... 30 Loading Language Packs ...................................................................................................... 31 Specifying the Language to Use........................................................................................... 31 Missed Call Log ............................................................................................................................. 32 Local Directory ............................................................................................................................... 33 Call Waiting .................................................................................................................................... 34 Auto Redial ..................................................................................................................................... 35 Do Not Disturb (DND) .................................................................................................................... 35 Call Hold......................................................................................................................................... 37 Call Forward .................................................................................................................................. 38 Call Transfer ................................................................................................................................... 39 Centralized Conference ................................................................................................................ 40 Transfer on Conference Hang Up ................................................................................................ 41 Directed Pickup Key ...................................................................................................................... 41 Group Pickup Key .......................................................................................................................... 42 Call Park Key .................................................................................................................................. 44 BLF Call Park................................................................................................................................... 44 Hotline ............................................................................................................................................ 45 Web Server Type............................................................................................................................ 46 Caller ID Presentation ................................................................................................................... 46 Callee ID Presentation .................................................................................................................. 47 DTMF ............................................................................................................................................... 48 Suppressing the Display of DTMF Digits ..................................................................................... 49
Configuring Advanced Features............................................ 51

Distinctive Ring Tones .................................................................................................................... 51 Tones ............................................................................................................................................... 52 Remote Phonebook ....................................................................................................................... 54 LDAP ................................................................................................................................................ 55 Busy Lamp Field ............................................................................................................................. 57 Shared Call Appearance ............................................................................................................. 58 As-Feature-Event ........................................................................................................................... 59 Action URL ...................................................................................................................................... 60 Action URI ....................................................................................................................................... 63 Server Redundancy ....................................................................................................................... 65 Network Address Translation ....................................................................................................... 67 SNMP .............................................................................................................................................. 69 802.1X Authentication ................................................................................................................... 70 TR-069 Device Management ........................................................................................................ 72
Security Features .................................................................... 75

2
Table of Contents
Transport Layer Security................................................................................................................ 75 Encrypting Configuration Files ..................................................................................................... 78 Changing the AES Keys on the IP Phone .............................................................................. 79
Upgrading the Firmware........................................................ 81 Resource Files ......................................................................... 83

Replace Rule Template ................................................................................................................. 83 Dial-now Template......................................................................................................................... 84 Local Contact File .......................................................................................................................... 85 Remote XML Phonebook ............................................................................................................... 87 Specifying the Access URL of Resource Files .............................................................................. 88
Troubleshooting ...................................................................... 91
Troubleshooting Methods ............................................................................................................. 91 Viewing Log Files .................................................................................................................... 91 Capturing Packets .................................................................................................................. 92 Enabling the Watch Dog Feature .......................................................................................... 93 Getting Information from Status Indicators.......................................................................... 93 Analyzing Configuration Files ............................................................................................... 94 Troubleshooting Solutions ............................................................................................................. 94 Why is the phone LCD screen blank? ................................................................................... 94 Why cant the phone obtain the IP address? ....................................................................... 94 Why does the phone display No Service? ....................................................................... 95 Why cant the phone upgrade successfully? ....................................................................... 95 Why doesnt the phone display time and date correctly? ................................................. 95 Why do I get poor audio during a call? ............................................................................... 95 Why doesnt the phone apply the configuration? ............................................................... 96 How to solve the IP conflict problem? .................................................................................. 96 How to upgrade the phone firmware in the recovery mode? ........................................... 96 How to reset your phone to factory configurations? ........................................................... 96
Appendix ................................................................................ 99
Appendix A: Glossary ................................................................................................................... 99 Appendix B: Configuration Parameters .................................................................................... 101 Setting Parameters in Configuration Files .......................................................................... 101 Basic and Advanced Parameters ....................................................................................... 101 Security Feature Parameters ............................................................................................... 159 Upgrading the Firmware ..................................................................................................... 161 Resource Files ....................................................................................................................... 163 Troubleshooting .................................................................................................................... 165 Configuring DSS Key ............................................................................................................ 166 3
Appendix C: SIP (Session Initiation Protocol)............................................................................ 177 RFC and Internet Draft Support .......................................................................................... 178 SIP Request ............................................................................................................................ 179 SIP Header ............................................................................................................................ 180 SIP Responses ....................................................................................................................... 181 SIP Session Description Protocol (SDP) Usage .................................................................. 184 Appendix D: SIP Call Flows ........................................................................................................ 184 Successful Call Setup and Disconnect ............................................................................... 185 Unsuccessful Call SetupCalled User is Busy .................................................................. 188 Unsuccessful Call SetupCalled User Does Not Answer ................................................ 191 Successful Call Setup and Call Hold .................................................................................. 194 Successful Call Setup and Call Waiting ............................................................................. 197 Call Transfer without Consultation ...................................................................................... 202 Call Transfer with Consultation ............................................................................................ 207 Always Call Forward ............................................................................................................ 213 Busy Call Forward ................................................................................................................ 216 No Answer Call Forward ..................................................................................................... 219 Call Conference .................................................................................................................... 222 Appendix E: Sample Configuration File .................................................................................... 227
Index ......................................................................................233
Product Overview
This chapter contains the following information about the Yealink SIP-T2xP IP phones:

VoIP Principle SIP Components SIP IP Phone Models
VoIP
VoIP (Voice over Internet Protocol) is a technology using the Internet Protocol instead of traditional Public Switch Telephone Network (PSTN) technology for voice communications. It is a family of technologies, methodologies, communication protocols, and transmission techniques for the delivery of voice communications and multimedia sessions over IP networks. The H.323 and Session Initiation Protocol (SIP) are two popular VoIP protocols that are found in widespread implement.
H.323
H.323 is a recommendation from the ITU Telecommunication Standardization Sector (ITU-T) that defines the protocols to provide audio-visual communication sessions on any packet network. The H.323 standard addresses call signaling and control, multimedia transport and control, and bandwidth control for point-to-point and multi-point conferences. It is widely implemented by voice and video conference equipment manufacturers, is used within various Internet real-time applications such as GnuGK and NetMeeting and is widely deployed worldwide by service providers and enterprises for both voice and video services over IP networks.
SIP
SIP (Session Initiation Protocol) is the Internet Engineering Task Forces (IETFs) standard for multimedia conferencing over IP. It is an ASCII-based, application-layer control protocol (defined in RFC 3261) that can be used to establish, maintain, and terminate calls between two or more end points. Like other VoIP protocols, SIP is designed to address the functions of signaling and session management within a packet telephony network. Signaling allows call information to be carried across network boundaries. Session management provides the ability to control the attributes of an end-to-end call.
SIP provides the capabilities to:
Determine the location of the target end point -- SIP supports address resolution, name mapping, and call redirection.
Determine the media capabilities of the target end point -- Via Session Description Protocol (SDP), SIP determines the lowest level of common services between the end points. Conferences are established using only the media capabilities that can be supported by all end points.
Determine the availability of the target end point -- A call cannot be completed because the target end point is unavailable, SIP determines whether the called party is already on the phone or did not answer in the allotted number of rings. It then returns a message indicating why the target end point was unavailable.
Establish a session between the origin and target end point -- The call can be completed, SIP establishes a session between the end points. SIP also supports mid-call changes, such as the addition of another end point to the conference or the changing of a media characteristic or codec.
Handle the transfer and termination of calls -- SIP supports the transfer of calls from one end point to another. During a call transfer, SIP simply establishes a session between the transferee and a new end point (specified by the transferring party) and terminates the session between the transferee and the transferring party. At the end of a call, SIP terminates the sessions between all parties.
SIP is a peer-to-peer protocol. The peers in a session are called User Agents (UAs). A user agent can function as one of the following roles:

User Agent Client (UAC) -- A client application that initiates the SIP request. User Agent Server (UAS) -- A server application that contacts the user when a SIP request is received and that returns a response on behalf of the user.
User Agent Client (UAC)

The UAC is an application that initiates up to six feasible SIP requests to the UAS. The six requests issued by the UAC are: INVITE, ACK, OPTIONS, BYE, CANCEL and REGISTER. When the SIP session is being initiated by the UAC SIP component, the UAC determines the information essential for the request, which is the protocol, the port and the IP address of the UAS to which the request is being sent. This information can be dynamic and this will make it challenging to put through a firewall. For this reason it may be recommended to open the specific application type on the firewall. The UAC is also capable of using the information in the request URI to establish the course of the SIP request to its destination, as the request URI always specifies the host which is essential. The port and protocol are not always specified by the request URI. Thus if the request does not specify a port or protocol, a default port or protocol is contacted. Using this 2
Product Overview
method may be the preferred measure when not using an application layer firewall, application layer firewalls like to know what applications are flowing though which ports and it is possible using content types of other applications other than the one you are trying to let through which has been denied.
User agent server (UAS)

UAS is the Server that hosts the application responsible for receiving the SIP requests from a UAC, and on reception returns a response to the request back to the UAC. The UAS may issue multiple responses to the UAC, not necessarily a single response. Communication between UAC and UAS is client/server and peer-topeer. Typically, a SIP end point is capable of functioning as both a UAC and a UAS, but it functions only as one or the other per transaction. Whether the endpoint functions as a UAC or a UAS depends on the UA that initiates the request.
This section introduces the SIP-T2xP IP phone family. The Yealink SIP-T2xP IP phones are end points in the overall network topology, which are designed to interoperate with other compatible equipments including application servers, media servers, internet-working gateways, voice bridges, and other end points. The SIP-T2xP IP phones are characterized by a large number of functions, which simplify business communication with a high standard of security and can work seamlessly with a large number of SIP PBXs that support SIP . The SIP-T2xP IP phones provide a powerful and flexible IP communication solution for Ethernet TCP/IP networks, delivering excellent voice quality. The high-resolution graphic display supplies content in multiple languages for system status, call history and directory access. The SIP-T2xP IP phones also support advanced functionalities, including LDAP , Busy Lamp Field, Shared Call Appearance and Centralized Conference. The following IP phone models are described:

SIP-T28P SIP-T26P SIP-T22P SIP-T20P
The Yealink SIP-T2xP IP phones comply with the SIP standard (RFC 3261), and they can only be used within a network that supports this type of phone. For the Yealink SIP-T2xP IP phones to successfully operate as SIP endpoints in your network, they must meet the following requirements:

A working IP network is established. Routers are configured for VoIP .
VoIP gateways are configured for SIP . The latest (or compatible) firmware of the SIP-T2xP IP phones is available. A call server is active and configured to receive and send SIP messages.
This section lists the available physical features of the SIP-T2xP IP phones.
SIP-T28P
Physical Features:
TI TITAN chipset and TI voice engine 320x160 graphic LCD with 4-level grayscales 6 VoIP accounts, Broadsoft/Avaya/Asterisk validated HD Voice: HD Codec, HD Handset, HD Speaker 48 keys including 16 programmable keys 1xRJ9 (4P4C) handset port 1xRJ9 (4P4C) headset port 2xRJ45 10/100M Ethernet ports 1XRJ12 (6P6C) expansion module port 19 LEDs: 1xpower, 6xline, 1xmessage, 1xheadset, 10xmemory Power adapter: AC 100~240V input and DC 5V/1.2A output Power over Ethernet (IEEE 802.3af) Multi-language display
Product Overview
SIP-T26P
Physical Features:
TI TITAN chipset and TI voice engine 132x64 graphic LCD 3 VoIP accounts, Broadsoft/Avaya/Asterisk validated HD Voice: HD Codec, HD Handset, HD Speaker 45 keys including 13 programmable keys 1xRJ9 (4P4C) handset port 1xRJ9 (4P4C) headset port 2xRJ45 10/100M Ethernet ports 1XRJ12 (6P6C) expansion module port 16 LEDs: 1xpower, 3xline, 1xmessage, 1xheadset, 10xmemory Power adapter: AC 100~240V input and DC 5V/1.2A output Power over Ethernet (IEEE 802.3af) Multi-language display
SIP-T22P
Physical Features:
TI TITAN chipset and TI voice engine 132x64 graphic LCD 3 VoIP accounts, Broadsoft/Avaya/Asterisk validated HD Voice: HD Codec, HD Handset, HD Speaker 32 keys including 4 programmable keys 1xRJ9 (4P4C) handset port 1xRJ9 (4P4C) headset port 2xRJ45 10/100M Ethernet ports 5 LEDs: 1xpower, 3xline, 1xmessage Power adapter: AC 100~240V input and DC 5V/1.2A output Power over Ethernet (IEEE 802.3af) Wall-mounted Multi-language display
Product Overview
SIP-T20P
Physical Features:
TI TITAN chipset and TI voice engine 3-line LCD with an icon line and 2x15 characters lines 2 VoIP accounts, Broadsoft/Avaya/Asterisk validated HD Voice: HD Codec, HD Handset, HD Speaker 31 keys including 9 programmable keys 1xRJ9 (4P4C) handset port 1xRJ9 (4P4C) headset port 2xRJ45 10/100M Ethernet ports 4 LEDs: 1xpower, 2xline, 1xmessage Power adapter: AC 100~240V input and DC 5V/1.2A output Power over Ethernet (IEEE 802.3af) Wall-mounted Multi-language display
In addition to the physical features introduced above, the SIP-T2xP IP phones also support the following key features when running the latest firmware:
Phone Features
Call Options: emergency call, call waiting, dial plan, call hold, call mute, 3-way conference, speed dial. Basic Features: DND, phone lock, auto redial, call transfer, hotline, call pickup, call forward, calling party identity. Advanced Features: BLF/BLF list, shared call appearance, distinctive ring tones, remote phonebook, SNMP , LDAP , 802.1x.
Codecs and Voice Features

Wideband codec: G.722 Narrowband codec: G.711, G.723.1, G.726, G.729AB VAD, CNG, AEC, PLC, AJB, AGC Full-duplex speakerphone with AEC
Network Features
SIP v1 (RFC2543), v2 (RFC3261) NAT Traversal: STUN mode DTMF: INBAND, RFC2833, SIP INFO Proxy mode and peer-to-peer SIP link mode IP assignment: Static/DHCP/PPPoE Bridge/Router mode TFTP/DHCP/PPPoE client HTTP/HTTPS server DNS client NAT/DHCP server
Management
FTP/TFTP/HTTP/PnP auto-provision Configuration: browser/phone/auto-provision Direct IP call without SIP proxy Dial number via SIP server Dial URL via SIP server TR-069
Product Overview
Security
HTTPS (server/client) SRTP (RFC3711) Transport Layer Security (TLS) VLAN (802.1q), QoS Digest authentication using MD5/MD5-sess Secure configuration file via AES encryption Phone lock for personal privacy protection Admin/User configuration mode
10
Getting Started
This chapter introduces the initialization of the SIP-T2xP IP phones, the installing and connecting process of the IP phones which you need to follow. This chapter provides the following major sections:

Connecting the Phone Initialization Process Overview Verifying Startup Configuration Interfaces Reading Icons Configuring Network Parameters Manually Creating Dial Plan
This section introduces how to install SIP-T2xP IP phones with the components in the packing list. 1. 2. 3. Note Attach the Stand Connect the Handset and optional Headset Connect the Network and Power
A headset is not provided in the packing list.
1)
Attaching the Stand:
11
2)
Connecting the Handset and optional Headset:
3)
Connecting the Network and Power:
You have two options for power and network connections. Select a suitable way according to your actual situation.

AC power Power over Ethernet (PoE)
AC Power
To connect the AC power and network: 1. Connect the DC plug of the power adapter to the DC5V port on the phone and connect the other end of the power adapter into an electrical power outlet. 2. Connect the supplied Ethernet cable between the Internet port on the phone and the Internet port in your network or switch/hub device port.
Power over Ethernet

Using a regular Ethernet cable, the SIP-T28P and SIP-T26P IP phones can be powered from a PoE (IEEE 802.3af) compliant switch or hub.
12
Getting Started
To connect the PoE: 1. Connect the Ethernet cable between the Internet port on the phone and an available port on the in-line power switch/hub.
1)
Attaching the Stand: Desk-mounted Method
Wall-mounted Method
13
2)
Connecting the Handset and optional Headset:
3)

Connecting the Network and Power: AC power Power over Ethernet (PoE)
AC Power
To connect the AC power and network: 1. Connect the DC plug of the power adapter to the DC5V port on the phone and connect the other end of the power adapter into an electrical power outlet. 2. Connect the supplied Ethernet cable between the Internet port on the phone and the Internet port in your network or switch/hub device port.
Power over Ethernet

Using a regular Ethernet cable, the SIP-T22P and SIP-T20P IP phones can be powered from a PoE (IEEE 802.3af) compliant switch or hub.
14
Getting Started
To connect the PoE: 1. Connect the Ethernet cable between the Internet port on the phone and an available port on the in-line power switch/hub.
Note
If in-line power is provided, you dont need to connect the AC adapter. Make sure the Ethernet cable and switch/hub are PoE compliant. The IP phone can also share the network with other network device such as a PC (personal computer). It is an optional connection. Important! Do not unplug or remove power while the IP phone is updating firmware and configuration.
The initialization process of the IP phone is responsible for network connectivity and operation of the IP phone in your local network. Once you connect your phone to the network and to an electrical supply, the phone begins its initialization process. During the initialization process, the following events take place: Loading the ROM file The ROM file resides in the flash memory of the IP phone. The IP phone comes from the factory with a ROM file preloaded. During initialization, the IP phone runs a bootstrap loader that loads and executes the ROM file. Configuring the VLAN If the IP phone is connected to a switch, the switch notifies the IP phone of the VLAN ID defined on the switch. The IP phone can then proceed with the DHCP request for its network settings (if using DHCP).
15
DHCP (Dynamic Host Configuration Protocol) The IP phone is capable of querying a DHCP server. DHCP is enabled on the IP phone by default. The following network settings can be obtained from the DHCP server during initialization:

IP Address Subnet Mask Gateway Primary DNS (Domain Name Server) Secondary DNS
You need to configure the IP phone manually if any of the network parameters is not supplied by the DHCP server. For more information on manually configuring network parameters, refer to Configuring Network Parameters Manually on page 20. Contacting the TFTP server If the IP phone is using the TFTP server to obtain its configurations, there should be a configuration file or files on the TFTP server that the phone will request and download. The IP phone resolves and applies the configurations written in the configuration file or files. In the configuration file or files, SIP parameters that are required by the IP phone to operate in a SIP VoIP environment are defined. If the phone is not obtaining its configurations via the TFTP server, the phone will use configurations that are stored in the flash memory. Verifying the firmware version If the phone determines that the firmware version defined in a configuration file differs from the image it has stored in the flash memory, it performs a firmware upgrade. When performing a firmware upgrade, the phone downloads the firmware image from the TFTP server, programs the image into the flash memory, and reboots. Loading the resource files The IP phone may require resource files that are used by some of the advanced features, which are also defined in the configuration file or files. These resource files are optional, but if the particular feature is being employed, these files are required. Some examples of resource files include:

Language files Ring tones Directories
16
Getting Started
After connecting the power and network, the IP phone begins the startup process by cycling through the following steps: 1. 2. 3. The power indicator LED is illuminated. The message Initializing, Please wait appears as phone starts up. The main LCD screen displays the following:

Time and Date Soft key labels (not supported by T20P)
4.
Press the OK key to verify the phone status, the LCD screen displays the valid IP address, MAC address and firmware version, etc.
If the IP phone has successfully passed through these steps, it starts up properly and is ready for use.
You can use the following ways to setup and configure the IP phone:

Phone User Interface Web User Interface Configuration Files
The following sections describe how to configure the IP phone using each way.
The IP phone user interface provides an easy way to access features and functions for using and configuring the IP phone. Access to specific features and functions are restricted to the administrator. A user can configure a subset of these features and functions. Advanced Settings are password protected by default. Enter the administrator password to unlock. The default password is admin (case-sensitive). Not all features are available for configuring via phone user interface.
An administrator can configure the IP phone using the web user interface. The default administrator s name and password for logging in the web user interface are admin (case-sensitive). Almost all features are available to be configured using the web user interface. The phone web user interface supports both HTTP and HTTPS protocols, you can configure the web server type, refer to Web Server Type on page 46 for more information.
17
An administrator can configure the IP phone using the configuration files. There are two configuration files both of which are CFG format. We call them Common CFG file and MAC-Oriented CFG file. A Common CFG file will be effectual for all IP phones of the same model. However, a MAC-Oriented CFG file will only be effectual for the specific IP phone. The common CFG file has a fixed name for each phone model, while the MAC-Oriented CFG file is named with the MAC address of the IP phone. For example, a SIP-T22P IP phone whose MAC address is 001565113af8, the two configuration files must be: y000000000005.cfg and 001565113af8.cfg. The name of the Common CFG file for each SIP-T2xP IP phone model is:

SIP-T28P: y000000000000.cfg SIP-T26P: y000000000004.cfg SIP-T22P: y000000000005.cfg SIP-T20P: y000000000007.cfg
In order to configure the IP phone using the configuration files (<y0000000000xx>.cfg and <MAC>.cfg), you need to use a text-based editing application to edit the configuration files, and store the configuration files to the root directory of a configuration server. The IP phone supports downloading the configuration files using any of the following protocols: FTP , TFTP , HTTP and HTTPS. You can configure the type of configuration server. The IP phone gets the address of the configuration server during startup through any of the following processes: Zero Touch, PnP , DHCP Option and Phone Flash. Then the IP phone downloads the configuration files from the configuration server, resolves and applies the configurations written in the configuration files. This entire process is called Auto Provisioning. For more information on auto provisioning, refer to the document Yealink Auto Provisioning User Guide. When modifying parameters, remember the following:
Parameters in the configuration files override those stored in the phones flash memory.
The .cfg extension of the configuration files must be in lowercase. Each line in a configuration file must use the following format and adhere to the following rules: variable-name = value Associate only one value with one variable. Separate variable name and value with equal sign. Set only one variable per line. Put the variable and value on the same line, and do not break the line.
18
Getting Started
Use white space before or after a variable or value. Comment the variable on a separated line. Use the pound (#) delimiter to distinguish the comments.
The IP phone can accept two sources of configuration data:

Downloaded from the configuration files Changed on the phone user interface or the web user interface
The latest values to be applied to the IP phone are the values that take effect.
When using or configuring different features on the IP phone, a variety of icons may appear on the LCD screen. The following table lists and describes icons that you might see while using different IP phone models. T28P T26P T22P T20P Description Network unavailable Private line registers successfully Shared line registers successfully Registered fail
Registering Hands-free speakerphone mode Handset mode
Headset mode
Voice Mail
Text Message
Auto Answer
19
T28P
T26P
T22P
T20P
Description Do Not Disturb
Call Forward
Call Hold
Call Mute
Ringer volume is 0
Phone Lock
Received Calls
Dialed Calls
Missed Calls
By default, DHCP is enabled on the IP phone. The IP phone can automatically derive the network settings from the DHCP server. If DHCP is disabled or the phone cannot obtain network settings, you need to manually configure them. The following network parameters must be configured for the IP phone to operate in an IP network:

IP Address Subnet Mask Default Gateway Primary DNS Secondary DNS
Procedure
Network settings can be configured using the configuration files or locally. Configure the basic network Configuration File <y0000000000xx>.cfg parameters of the phone. For more information, refer to 20
Getting Started
Network Settings on page 101. Configure the basic network parameters of the phone. Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bin/ Local ConfigManApp.com?Id=2 Configure the basic network Phone User Interface parameters of the phone. For more information, refer to the SIP-T2xP User Guide. To configure the network settings via web user interface: 1. 2. 3. Click on Network. Mark the Static IP Address radio box. Enter the IP Address, subnet mask, default gateway, primary DNS and secondary DNS in the corresponding fields. 4. Click Confirm to save the change.
Regular expression, often called a pattern, is an expression that specifies a set of strings. A regular expression provides a concise and flexible means to "match" (specify and recognize) strings of text, such as particular characters, words, or patterns of characters. Regular expression is used by many text editors, utilities, and programming languages to search and manipulate text based on patterns. Regular expression can be used to define dial plan for the IP phone. Dial plan is a string of characters that governs the way for the IP phone processing the inputs received from the phone keypad. The IP phone supports the following dial plan features:

Replace Rule Dial-now Area Code Block Out
You need to know the following basic regular expression syntax when creating dial plan: The dot "." can be used as a placeholder or multiple placeholders for
.
x
any string. Example: "12." would match "123", "1234", "12345", "12abc", etc. The "x" can be used as a placeholder for any character. Example:
21
"12x" would match "121", "122", "123", "12a", etc. Numeric ranges are allowed within the brackets: Digit - Digit. Example: [5-7] would match the number 5, 6or 7. The square bracket "[]" can be used as a placeholder for a single [] character which matches any of a set of characters. Example: "91[5-7]1234" would match "9151234", "9161234", "9171234", etc. The parenthesis "( )" can be used to group together patterns, for () instance, to logically combine two or more patterns. Example: "([1-9])([2-7])3" would match "923", "153", "673", etc. The $ followed by the sequence number of a parenthesis means the characters placed in the parenthesis. The sequence number stands for the corresponding parenthesis. Example: $ A replace rule configuration, Prefix: "9([5-7]) (.)", Replace: "5$2". When you dial out "96123" on your phone, the phone will replace the number as "5123" and then dial out. $2 means the characters in the second parenthesis, that is, 123.
Replace rule is an alternated string of characters that replaces the numbers dialed by the user. You can specify at most 20 replace rules for the IP phone. You can create multiple replace rules using a replace rule template and specify which phones are to use the replace rules. For more information on the replace rule template, refer to Replace Rule Template on page 83.
Procedure
Replace rule can be created using the configuration files or locally. Create the replace rule for the Configuration File <y0000000000xx>.cfg phone. For more information, refer to Dial Plan on page 103. Create the replace rule for the phone. Navigate to: Local Web User Interface http://<phoneIPAddress>/cgi-bin/ ConfigManApp.com?Id=12 For more information, refer to the SIP-T2xP User Guide. 22
Getting Started
Dial-now is a string of characters that used to match the numbers dialed by the user, when the dialed numbers match the predefined dial-now rule, the IP phone will automatically dial out the numbers without pressing the send key. You can specify at most 20 dial-now rules for the phone. You can create multiple dial-now rules using the dial-now template and specify which phones are to use. For more information on the dial-now template, refer to Dial-now Template on page 84.
Procedure
Dial-now rule can be created using the configuration files or locally. Create the dial-now rule for the Configuration File <y0000000000xx>.cfg phone. For more information, refer to Dial Plan on page 104. Create the dial-now rule for the phone. Navigate to: Local Web User Interface http://<phoneIPAddress>/cgi-bin/ ConfigManApp.com?Id=12 For more information, refer to the SIP-T2xP User Guide.
Area codes are also known as Numbering Plan Areas (NPAs). They usually indicate geographical areas in one country. You can configure only one area code for the IP phone. When dialing out numbers, the IP phone will automatically add the area code before the dialed numbers. You can also specify the area code for the desired line and the fixed lengths of the dialed numbers.
Procedure
Area code can be configured using the configuration files or locally. Configure the area code and specify the maximum and Configuration File <y0000000000xx>.cfg minimum lengths of the dialed numbers. For more information, refer to Dial Plan on page 104.
23
Configure the area code and specify the maximum and minimum lengths of the dialed numbers. Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bin/ ConfigManApp.com?Id=12 For more information, refer to the SIP-T2xP User Guide.
You can block the IP phone to dial out some specific numbers by configuring block out numbers. You can create at most 10 block out numbers. When dialing out the block out number, the phone LCD screen prompts the message Forbidden Number .
Procedure
Block out number can be specified using the configuration files or locally. Specify the block out number for Configuration File <y0000000000xx>.cfg the phone. For more information, refer to Dial Plan on page 106. Specify the block out number for the phone. Navigate to: Local Web User Interface http://<phoneIPAddress>/cgi-bin/ ConfigManApp.com?Id=12 For more information, refer to the SIP-T2xP User Guide.
24
Configuring Basic Features
The IP phone has specific features you can configure to customize your phone. This chapter provides information for making configuration changes for the following basic features:

User Password Administrator Password Phone Lock Time and Date Language Missed Call Log Local Directory Call Waiting Auto Redial Do Not Disturb (DND) Call Hold Call Forward Call Transfer Centralized Conference Transfer on Conference Hang Up Directed Pickup Key Group Pickup Key Call Park Key BLF Call Park Hotline Web Server Type Caller ID Presentation Callee ID Presentation DTMF Suppressing the Display of DTMF Digits
25
Several setting menus are protected with two privilege levels, user and administrator, each with its own password. When logging in the web user interface, the IP phone will prompt for the username and password before granting access to various menu options. A user or an administrator can change the user password. The IP phone supports alphanumeric characters (- *.+ are included) only in passwords.
Procedure
User password can be changed using the configuration files or locally. Change the user password of the Configuration File <y0000000000xx>.cfg phone. For more information, refer to on User Password page 107. Change the user password of the phone. Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bin/ ConfigManApp.com?Id=8 To change the user password via web user interface: 1. 2. 3. 4. 5. Click on Security. Mark the user radio box. Enter the current user password in the Current Password field. Enter a new password in the New Password and Confirm Password fields. Click Confirm to save the change.
Advanced menu options are restricted to administrator. You must log in as administrator to configure them when using the web user interface. The administrator password can be only changed by the administrator. The IP phone supports alphanumeric characters (- *.+ are included) only in passwords.
Procedure
Administrator password can be changed using the configuration files or locally. Change the administrator Configuration File <y0000000000xx>.cfg password. For more information, refer to Administrator Password on page 26
107. Change the administrator password. Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bin/ ConfigManApp.com?Id=8 To change the administrator password via web user interface: 1. 2. 3. 4. 5. Click on Security. Mark the admin radio box. Enter the current administrator password in the Current Password field. Enter a new password in the New Password and Confirm Password fields. Click Confirm to save the change.
A user or administrator can lock the IP phone to prevent it from unauthorized use. Once the IP phone is locked, the user or administrator needs to enter the password to unlock the phone. The default unlock password is 123. You can change the unlock password and configure the interval to automatically lock the phone. The phone supports numeric characters only in unlock passwords. The maximum length of the password is 15 characters. You can configure a DSS key to be keypad lock key. After enabling the phone lock feature, the phone is locked after a configured period of inactivity. You can long press the pound key or press the keypad lock key on the idle screen to lock the phone immediately. You are only allowed to dial out the emergency numbers when the phone is locked. You can specify one or more emergency numbers for the IP phone. There are four types of "locks" that can apply to the IP phone:
Menu Key: The Menu key is locked. You cannot access the menu of the IP phone until unlocked.
Function Keys: The function keys are locked. All Keys: All keys are locked except the Volume key. The IP phone can only dial out emergency numbers and answer incoming calls by lifting the handset, pressing the Speakerphone key, pressing the HEADSET key or pressing the OK key.
Lock&Answer: All keys are locked, except the Menu key, the HEADSET key and the Volume key. The IP phone can automatically answer the incoming calls and place the previous conversation (if one) on hold, but cannot end the call.
27
Procedure
Phone lock can be configured using the configuration files or locally. Configure the type of phone lock. Change the unlock password and configure the interval to automatically lock the phone. Configuration File <y0000000000xx>.cfg Configure the emergency numbers. For more information, refer to Phone Lock on page 107. Assign a keypad lock key. For more information, refer to Keypad Lock Key on page 171. Configure the type of phone lock. Change the unlock password and configure the interval to automatically lock the phone. Configure the emergency Web User Interface numbers. Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=5 Assign a keypad lock key. Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=21 Configure the type of phone Phone User Interface lock. For more information, refer to the SIP-T2xP User Guide.
Local
The IP phone maintains a local clock and calendar. Time and date display on the idle screen of the IP phone. In addition to configuring the IP phone to obtain the time and date from the Simple Network Time Protocol (SNTP) server, you can also manually set the time and date, the time and date format and the daylight saving time.
28
The following table lists the available methods for each feature: Feature Set Time Methods of Configuration Web User Interface Phone User Interface Configuration Files Set Time Format Web User Interface Phone User Interface Set Time Zone Configuration Files Web User Interface Web User Interface Phone User Interface Configuration Files Set Date Format Web User Interface Phone User Interface Set Daylight Saving Time Configuration Files Web User Interface
Set Date
Time Zone
A time zone is a region on the earth that has a uniform standard time. It is convenient for areas in close commercial or other communication to keep the same time. You can set time zone using the Time Zone option in the web user interface or using the parameters in the configuration files.
Daylight Saving Time

Daylight Saving Time (DST) is the practice of temporarily advancing clocks during the summertime so that evenings have more daylight and mornings have less. Typically clocks are adjusted forward one hour near the start of spring and are adjusted backward in autumn. Many countries have used the DST at various times, details vary by location. The DST can be adjusted automatically from the time zone configuration. Usually there is no need to change this setting.
Procedure
DST, time and date can be configured using the configuration files or locally. Configure the DST, time and date Configuration File <y0000000000xx>.cfg manually. For more information, refer to Time and Date on page 109.
29
Configure the DST, time and date manually. Navigate to: Web User Interface http://<phoneIPAddress>/cgi-bin/ ConfigManApp.com?Id=5 Local For more information, refer to the SIP-T2xP User Guide. Configure the time and date Phone User Interface manually. For more information, refer to the SIP-T2xP User Guide.
The IP phone supports displaying multiple languages. The languages displaying on the phone user interface and web user interface can be specified respectively as required. The following tables list the languages supported by the phone user interface. The phone user interface supports the following languages: Available Language English Chinese_S Chinese_T Deutsch French Italian Portuguese Polish Spanish Turkish Note Associated Language File lang+English.txt lang-Chinese_S.txt lang-Chinese_T.txt lang-Deutsch.txt lang-French.txt lang-Italian.txt lang-Portuguese.txt lang-Polish.txt lang-Spanish.txt lang-Turkish.txt
The Chinese_S and Chinese_T languages are not applicable to the SIP-T20P IP phone.
30
All supported languages may not be available for selection. The available selected languages are dependent on the language packs currently on the IP phone. You can make languages available to display on the phone user interface by loading language files to the IP phone. The language files and file name must be the one listed in the above tables. You can only load language packs to the IP phone using the configuration files. Note
You can only load and delete the language packs of the IP phone using the configuration files. The default (English) language pack for the phone user interface cannot be deleted.
Procedure
Loading language file can be only performed using the configuration files. Specify the access URL of the Configuration File <y0000000000xx>.cfg language file. For more information, refer to Language on page 113.
The default language displays on the phone user interface is English. Once the language pack(s) have been loaded, you can specify which language to use. You need to specify the languages for the phone user interface and web user interface respectively.
Procedure
Specify the display language using the configuration files or locally. Specify the languages for the phone user interface and the Configuration File <y0000000000xx>.cfg web user interface. For more information, refer to Language on page 113. Specify the language for the web user interface. Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bin/ ConfigManApp.com?Id=5
31
For more information, refer to the SIP-T2xP User Guide.
Specify the language for the Phone User Interface phone user interface. For more information, refer to the SIP-T2xP User Guide.
The IP phone can display the number of missed calls and log the missed calls in the Missed Calls list. This missed call log feature is configurable on a per-account basis. When enabled, the prompt message "<number> New Missed Call" along with an indicator icon display on the idle screen of the IP phone. Once the user accesses the Missed Calls list, the prompt "<number> New Missed Call" and the indicator icon on the idle screen are cleared. When disabled, there is no indicator displaying on the LCD screen, the IP phone does not log the missed call in the Missed Calls list.
Procedure
Missed call log can be configured using the configuration files or locally. Configure the missed call log Configuration File <MAC>.cfg feature. For more information, refer to Missed Call Log on page 115. Configure the missed call log. Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bin/ ConfigManApp.com?Id=4 To configure the missed call log via web user interface: 1. 2. 3. 4. Click on Account. Select the desired account from the pull-down list of Account. Select the desired value from the pull-down list of Missed Call Log. Click Confirm to save the change.
32
The built-in phone directory can store up to 300 contacts. You can manually store the frequently used names and numbers to the local directory. You can add multiple contacts by downloading a contact file to the phone. For more information on the contact file, refer to Local Contact File on page 85.
Procedure
Downloading the contact file can be performed using the configuration files or locally. Specify the access URL of the local contact file. Configuration File <y0000000000xx>.cfg For more information, refer to Access URL of Local Contact File on page 164. Download the contact file or add the contact to the phone. Navigate to: Web User Interface http://<phoneIPAddress>/cgi-bin/ ConfigManApp.com?Id=9 Local For more information, refer to the SIP-T2xP User Guide. Add the contact to the local Phone User Interface directory directly. For more information, refer to the SIP-T2xP User Guide.
33
When you are in an active call, the call waiting feature notifies you of the new incoming call, and presents the incoming call visually on the phone LCD screen. If the call waiting feature is disabled, the new incoming call will be automatically rejected by the IP phone with a busy message. Note
If the call waiting feature is disabled and the IP phone is in an active call, the Missed Calls list does not get updated with details of incoming calls.
Call Waiting Tone

You can also enable or disable the playing of a short Call Waiting Tone" when there is an incoming call on your IP phone. This feature is enabled by default. If you have Call Waiting Tone enabled, and a call comes into the IP phone when you are in an active call, a tone is audible to notify you of that incoming call. The Call Waiting Tone feature works only if the Call Waiting feature is enabled.
Procedure
Call waiting and call waiting tone can be configured using the configuration files or locally. Configure the call waiting and Configuration File <y0000000000xx>.cfg call waiting tone features. For more information, refer to Call Waiting on page 115. Configure the call waiting and call waiting tone features. Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bin/ ConfigManApp.com?Id=6 To configure the call waiting via web user interface: 1. 2. 3. Click on Phone->Features->General Information >>. Select the desired value from the pull-down list of Call Waiting. Click Confirm to save the change.
To configure the call waiting tone via web user interface: 1. 2. 3. Click on Phone->Features->Audio Settings>>. Select the desired value from the pull-down list of Call Waiting Tone. Click Confirm to save the change.
34
The auto redial feature allows the IP phone to redial the dialed out number automatically when the dialed number is busy. You can set the times of auto redial and the seconds to wait between redial attempts. The IP phone will retry as many times as configured till the dialed number is no longer busy.
Procedure
Auto redial can be configured using the configuration files or locally. Configure the auto redial feature Configuration File <y0000000000xx>.cfg on the IP phone. For more information, refer to Auto Redial on page 116. Configure the auto redial feature. Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bin/ ConfigManApp.com?Id=6 To configure the auto redial via web user interface: 1. 2. 3. 4. 5. Click on Phone->Features->General Information >>. Select Enabled from the pull-down list of Auto Redial. Enter the desired value in the Auto Redial Interval field. Enter the desired value in the Auto Redial Times field. Click Confirm to save the change.
The DND feature allows the IP phone to reject the incoming calls on a specific line or on all lines. The incoming calls are logged as missed calls while the DND is enabled. You can enable the DND on the phone or on the server. You can enable/disable the DND feature for the phone, or you can customize the DND feature for each account or all accounts. The following describes the DND key modes:
Phone (default): When the DND key mode is phone, it means the DND feature applies to all accounts.
Custom: When the DND key mode is custom, it means that you can configure the DND feature for each account or all accounts.
The DND enabled on the phone disables the local Call Forward settings. The DND enabled on the IP phone may be overridden by the server settings. You can configure a DSS key to be DND key. Press the DND key on the IP phone to toggle the DND mode.
35
Return Message When DND

When the DND mode is activated on the IP phone, any user calls the accounts registered on the IP phone will be rejected automatically and receives a busy tone and a message. The return message displays on the LCD screen of the caller s phone. You can configure the type of the return message.
Procedure
DND features can be configured using the configuration files or locally. Specify the type of return message. For more information, refer to Do Not Disturb on page 117. Configuration File <y0000000000xx>.cfg Assign a DND key. For more information, refer toDND Key on page 171. Specify the DND key mode. For more information, refer to Do Not Disturb on page 117. Specify the type of the return message. Navigate to: http://<phoneIPAddress>/cgi-bin/ ConfigManApp.com?Id=6 Assign a DND key. Navigate to: Web User Interface Local http://<phoneIPAddress>/cgi-bin/ ConfigManApp.com?Id=21 For more information, refer to SIP-T2xP User Guide. Specify the DND key mode. Navigate to: http://<phoneIPAddress>/cgi-bin/ ConfigManApp.com?Id=6 Assign a DND key. Phone User Interface For more information, refer to the SIP-T2xP User Guide. To configure the type of return message via web user interface: 1. 36 Click on Phone->Features->General Information >>.
2. 3.
Select the desired type from the pull-down list of Return Code When DND. Click Confirm to save the change.
To configure the DND key mode via web user interface: 1. 2. 3. Click on Phone->Features->DND>>. Select the desired mode in the DND Key Mode field. Click Confirm to save the change.
Call Hold Tone

The call hold feature allows you to place an active call on hold while you want to initiate or answer a second call. The line LED flashes green and the IP phone plays a warning tone at regular intervals to remind you that there still has a call on hold. You can set the interval for the IP phone to play hold tone. When the play hold tone feature is disabled, the IP phone will not play a warning tone when there is a call on hold.
Call Hold Method

The IP phone supports two SIP call hold methods. One is according to RFC 2543, setting c=0.0.0.0, the other is according to RFC 3261, setting c=IP address. The IP phone uses RFC 3261 to request the remote party to stop sending media by default.
Procedure
Call hold can be configured using the configuration files or locally. Configure the call hold tone and call hold tone delay features. Specify whether to use RFC 2543 Configuration File <y0000000000xx>.cfg (c=0.0.0.0) when outgoing hold signaling. For more information, refer to Call Hold on page 117. Configure the call hold tone and call hold tone delay features. Specify whether to use RFC 2543 Local Web User Interface (c=0.0.0.0) when outgoing hold signaling. Navigate to: http://<phoneIPAddress>/cgi-bin/ ConfigManApp.com?Id=6
37
To configure the call hold method via web user interface: 1. 2. 3. Click on Phone->Features->General Information >>. Select the desired value from the pull-down list of RFC 2543 Hold. Click Confirm to save the change.
To configure the call hold tone and call hold tone delay features via web user interface: 1. 2. 3. 4. Click on Phone->Features->Audio Settings>>. Select the desired value from the pull-down list of Play Hold Tone. Enter the desired time in the Play Hold Tone Delay field. Click Confirm to save the change.
The call forward feature allows the IP phone to forward incoming calls to another party. You can manually forward incoming calls to a predefined or a random number while the phone is in the ringing state. You can also enable the call forward feature to statically forward incoming calls to a predefined number. You can configure three types of call forward:

Always Forward -- Forward the incoming calls immediately. Busy Forward -- Forward the incoming call when the called user is busy. No Answer Forward -- Forward the incoming call after a period of ring time.
You can configure the phone to support the call forward feature for the phone system, or for each account. The following describes the call forward key modes:
Phone: Call forward in phone mode means that the call forward feature is effective for the phone system.
Custom: Call forward in custom mode means that you can configure the call forward feature for each account or all accounts.
You can set on code and off code on the phone to inform the server to sync the settings of call forward configured on the IP phone. The on code and off code may vary in different servers.
Procedure
Call forward can be configured using the configuration files or locally. Specify the Call Forward key mode. Configuration File <MAC>.cfg For more information, refer to Call Forward on page 118. Configure the call forward
38
feature in phone mode. For more information, refer to Call Forward on page 119. Configure the call forward feature in custom mode. For more information, refer to Call Forward on page 123. Configure the call forward feature. Navigate to: Web User Interface http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=6 Local For more information, refer to SIP-T2xP User Guide. Configure the call forward Phone User Interface feature. For more information, refer to SIP-T2xP User Guide.
The call transfer feature allows user to transfer an existing call to another party. The IP phone offers three types of transfer:

Blind Transfer -- Transfer a call directly to another party without consulting. Semi-attended Transfer -- Transfer a call after hearing the ring-back tone. Attended Transfer -- Transfer a call with prior consulting.
Normally, the transfer is completed by pressing the Transfer key. You can configure the IP phone to complete the blind transfer and attended transfer through on-hook. This feature is enabled by default. When performing the semi-attended transfer, you can configure the phone whether to display the prompt 1 New Missed Call(s) on the LCD screen of the destination party s phone. This feature is disabled by default.
Procedure
Call transfer can be configured using the configuration files or locally. Configure the phone to complete Configuration File <y0000000000xx>.cfg the blind or attended transfer through on-hook. Configure the semi-attended 39
transfer feature. For more information, refer to Call Transfer on page 123. Configure the phone to complete the blind or attended transfer through on-hook. Local Web User Interface Configure the semi-attended transfer feature. Navigate to: http://<phoneIPAddress>/cgi-bin/ ConfigManApp.com?Id=6 To configure the call transfer feature via web user interface: 1. 2. Click on Phone->Features->Transfer Settings>>. Select the desired values from the pull-down lists of Semi-Attended Transfer, Blind Transfer on Hook and Attended Transfer on Hook. 3. Click Confirm to save the change.
You can initiate a local conference with the remote parties by using the phones local audio processing resources. There is no dependency on network signaling for local conference. The IP phone also supports centralized conference for which external resources are used such as a conference bridge. The centralized conferences depend on support from the SIP server.
Procedure
Centralized conference can be configured using the configuration files or locally. Configure the type and URI of the centralized conference. Configuration File <MAC>.cfg For more information, refer to Centralized Conference on page 128. Configure the type and URI of the centralized conference. Navigate to: Local Web User Interface http://<phoneIPAddress>/cgi-bin/ ConfigManApp.com?Id=4 For more information, refer to SIP-T2xP User Guide. 40
All parties release from the call when the conference initiator drops from the conference call. You can enable the Transfer on Conference Hang up feature on the initiator s phone, the conference initiator will transfer the call when dropping from the conference call. This feature is only applicable to the local conference.
Procedure
Transfer on conference hang up feature can be configured using the configuration files or locally. Configure the transfer on conference hang up feature. Configuration File <y0000000000xx>.cfg For more information, refer to Transfer on Conference Hang Up on page 128. Configure the transfer on conference hang up feature. Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bin/ ConfigManApp.com?Id=6 To configure the Transfer on Conference Hang up feature via web user interface: 1. 2. Click on Phone->Features->Transfer Settings>>. Select the desired value from the pull-down list of Transfer on Conference Hang Up. 3. Click Confirm to save the change.
The directed pickup feature allows the user to pick up ringing calls of the specific extension. When assigning a directed pickup key on the IP phone, specify the extension you want to intercept. You can configure the IP phone to display the DPickup soft key in the dialing interface. Then you can pick up the incoming calls of the monitored extension using the DPickup soft key or the directed pickup key. When configuring the DPickup soft key, you can configure the directed pickup code on a phone or per-account basis. The settings on a per-account basis take precedence over the settings on a phone basis. If the monitored extension receives multiple incoming calls, the IP phone picks up the first incoming call. The directed pickup feature depends on support from the SIP server.
41
Procedure
Directed pickup can be configured using the configuration files or locally. Assign a directed pickup key. For more information, refer to Directed Pickup Key on page 172. Configure the directed pickup Configuration File <y0000000000xx>.cfg feature on a phone basis. For more information, refer to Directed Pickup on page 129. Configure the directed pickup code on a per-account basis. For more information, refer to Directed Pickup on page 129. Assign a directed pickup key. Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=21 For more information, refer to SIP-T2xP User Guide. Configure the directed pickup Web User Interface Local feature on a phone basis. Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=6 Configure the directed pickup code on a per-account basis. Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=4 Assign a directed pickup key. Phone User Interface For more information, refer to SIP-T2xP User Guide.
The group pickup feature allows the user to pick up ringing calls of the monitored group. When assigning a group pickup key on the IP phone, specify the group you want to intercept. You can configure the IP phone to display the GPickup soft key in the dialing 42
interface. You can pick up the incoming calls of the monitored group using the GPickup soft key or the group pickup key. When configuring the GPickup soft key, you can configure the group pickup code on a phone or per-account basis. The settings on a per-account basis take precedence over the settings on a phone basis. If the group members receive multiple incoming calls, the IP phone picks up the first incoming call. This feature depends on support from the SIP server.
Procedure
Group pickup can be configured using the configuration files or locally. Assign a group pickup key. For more information, refer to Group Pickup Key on page 173. Configure the group pickup feature on a phone basis. Configuration File <y0000000000xx>.cfg For more information, refer to Group Pickup on page 130. Configure the group pickup code on a per-account basis. For more information, refer to Group Pickup on page 130. Assign a group pickup key. Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=21 For more information, refer to SIP-T2xP User Guide. Configure the group pickup Web User Interface Local feature on a phone basis. Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=6 Configure the group pickup code on a per-account basis. Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=4 Assign a group pickup key. Phone User Interface For more information, refer to SIP-T2xP User Guide.
43
The call park feature allows the user to park a call at a special extension and then retrieve it on any other phone in the system. A user can park a call at an extension, known as Call Park Orbit, by pressing the call park key. The current call is put on hold and can be retrieved on another IP phone. This feature depends on support from the SIP server.
Procedure
Call park key can be configured using the configuration files or locally. Assign a call park key. Configuration File <y0000000000xx>.cfg For more information, refer to Call Park Key on page 174. Assign a call park key. Navigate to: Web User Interface Local http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=21 For more information, refer to SIP-T2xP User Guide. Assign a call park key. Phone User Interface For more information, refer to SIP-T2xP User Guide.
The BLF call park feature allows you to monitor a specific user and pick up the parked call of the user using the call park key. In order to use this feature, you need to assign a call park key, and specify the number of the monitored user in the Value filed and apply this key to the line which enabling the BLF call park feature. The call park key will present different status of the monitored user. You can press the call park key to do the following:

To make a call to the monitored user. To end the active call between the monitored user. To forward the incoming call to the monitored user. To blind transfer the active call to the monitored user. To pick up the parked call of the monitored user. To pick up the incoming call of the monitored user.
This feature is configurable on a per-account basis and depends on support from the SIP 44
server.
Procedure
BLF call park feature can be configured using the configuration files or locally. Configure the BLF call park <MAC>.cfg Configuration File feature on the IP phone. For more information, refer to BLF Call Park on page 129. Assign a call park key. <y0000000000xx>.cfg For more information, refer to BLF Call Park Key on page 175. Configure the BLF call park feature on the IP phone. Navigate to: http://<phoneIPAddress>/cgi-bi Local Web User Interface n/ConfigManApp.com?Id=4 Assign a call park key. Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=21
The hotline feature allows the IP phone to dial out a predefined number automatically whenever the phone is off hook. The IP phone uses the first available line to dial out the hotline number. You can specify one hotline number on the phone. You can also specify the delay time for the IP phone to automatically dial out the hotline number.
Procedure
Hotline can be configured using the configuration files or locally. Configure the hotline number Configuration File <y0000000000xx>.cfg and delay time. For more information, refer to Hotline on page 131. Configure the hotline number Local Web User Interface and delay time. Navigate to: http://<phoneIPAddress>/cgi-bi
45
n/ConfigManApp.com?Id=21 For more information, refer to SIP-T2xP User Guide. Configure the hotline number Phone User Interface and delay time. For more information, refer to SIP-T2xP User Guide.
User can access the web user interface of the IP phone using the HTTP and HTTPS protocols. You can configure the access type of the web server. The available options are: Disabled, HTTP & HTTPS, HTTP Only and HTTPS Only. The web server type is HTTP & HTTPS by default. You cannot use the web user interface of the phone when the web server type is configured to Disabled. You can specify the HTTP port and HTTPS port of the web server. Web server type can be configured using the configuration files or locally. Specify the access type, HTTP port and HTTPS port of the web Configuration File <y0000000000xx>.cfg server. For more information, refer to Web Server Type on page 132. Specify the access type, HTTP port and HTTPS port of the web Local Web User Interface server. Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=19
Caller ID Presentation service allows the IP phone to display the caller s name and number, derived from a SIP header contained in the INVITE message. The IP phone supports displaying three types of SIP headers (From, P-Asserted-Identity and Remote-Party-ID). Identity presentation bases on the content contained in the relevant SIP header. The presentation of the caller identity is configurable on a per-account basis. If the caller has existed in the directory, the local name assigned to the caller may be preferentially displayed.
46
Procedure
Caller ID presentation can be configured using the configuration files or locally. Configure the presentation of the caller identity. Configuration File <MAC>.cfg For more information, refer to Caller ID Presentation on page 133. Configure the presentation of the caller identity. Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=4 To configure the presentation of the caller identity via web user interface: 1. 2. 3. 4. 5. Click on Account. Select the desired account from the pull-down list of Account. Click Advanced>>. Select the desired value from the pull-down list of the Caller ID Header. Click Confirm to save the change.
Callee ID Presentation service allows the IP phone to display the identity of the callee specified for outgoing calls. The IP phone can display the Dialed Digits on the LCD screen, or substituted by the content of a SIP header(Remote-Party-ID or P-Asserted-Identity) received, or the content of the From header in the Update message sent by the callee as described in RFC 4916. When the RFC 4916 is enabled on the phone, the caller sends the SIP request message which contains the from-change tag in the Supported header. The caller then receives an Update message from the callee, and displays the content of the From header. The presentation of the callee identity is configurable on a per-account basis. If the callee has existed in the directory, the local name assigned to the callee may be preferentially displayed.
Procedure
Callee ID presentation can be configured only using the configuration files. Configure the presentation of Configuration File <MAC>.cfg the callee identity. For more information, refer to
47
Callee ID Presentation on page 133.
DTMF (Dual Tone Multi-frequency), better known as touch-tone, is used for telecommunication signaling over analog telephone lines in the voice-frequency band. DTMF is the signal sent from the IP phone to the network that you generate when pressing the phones keypad during the call. Each key you press on the phone generates one sinusoidal tone of two frequencies, one is generated from a high frequency group and the other from a low frequency group. The DTMF keypad is laid out in a 4 4 matrix, with each row representing a low frequency, and each column representing a high frequency. Pressing a digit key (such as '1') will generate a sinusoidal tone for each of two frequencies (697 and 1209 hertz (Hz)). DTMF Keypad Frequencies: 1209 Hz 697 Hz 770 Hz 852 Hz 941 Hz 1 4 7 * 1336 Hz 2 5 8 0 1447 Hz 3 6 9 # 1633 Hz A B C D
There are 3 common methods of transmitting DTMF on SIP calls:

RFC 2833 -- DTMF digits are transmitted by RTP events compliant to RFC 2833. INBAND -- DTMF digits are transmitted in the voice band (G.711). SIP INFO -- DTMF digits are transmitted by the SIP INFO messages.
The method of transmitting DTMF is configurable on a per-account basis.
RFC 2833
DTMF digits are transmitted using special IP packets that are sent along with the voice path. These packets use RFC 2833 format and must have a "payload type" that matches what the other end is listening for. The IP phone often defaults to 101 for the payload type, which uses your definition to negotiate with the other end during call establishment.
INBAND
DTMF digits are transmitted within the audio of the phone conversation. It uses the same VoIP codec as your voice and is audible to the conversation partners. 48
SIP INFO
DTMF digits are transmitted by the SIP INFO messages when the voice stream is established after a successful SIP 200 OK-ACK message sequence. The SIP INFO message is sent along the signaling path of the call. The SIP INFO message can support transmitting DTMF digits in three ways: DTMF , DTMF-Relay and Telephone-Event.
Procedure
Method of transmitting DTMF can be configured using the configuration files or locally. Configure the method of transmitting DTMF and the Configuration File <MAC>.cfg payload type. For more information, refer to DTMF on page 134. Configure the method of transmitting DTMF and the Local Web User Interface payload type. Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=4 To configure the method of transmitting DTMF via web user interface: 1. 2. 3. 4. 5. 6. 7. Click on Account. Select the desired account from the pull-down list of Account. Click on Advanced>>. Select the desired value from the pull-down list of DTMF Type. Select the desired value from the pull-down list of How to INFO DTMF. Enter the desired value in the DTMF Payload (Scope: 96~255) field. Click Confirm to save the change.
This Suppress DTMF Display feature allows the IP phone to suppress the display of DTMF digits. When enabled, the digits you dial using the keypad or a DSS key display as * on the LCD screen. This feature is disabled by default (displays DTMF digits). You can enable the Suppress DTMF Display Delay feature on the IP phone to display the dialed digits for a short period before displaying as *. This feature is disabled by default (directly displays as *). Note
The Suppress DTMF Display Delay feature works only if the Suppress DTMF Display feature is enabled.
49
Procedure
Configuration changes can be performed using the configuration files or locally. Configure the hide DTMF and hide DTMF delay features. Configuration File <y0000000000xx>.cfg For more information, refer to Suppressing the Display of DTMF Digits on page 135. Configure the hide DTMF and hide DTMF delay features. Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=6 To configure the Suppress DTMF Display and Suppress DTMF Display Delay features via web user interface: 1. 2. 3. 4. Click on Phone->Features->General Information >>. Select the desired value from the pull-down list of Suppress DTMF Display. Select the desired value from the pull-down list of Suppress DTMF Display Delay. Click Confirm to save the change.
50
Configuring Advanced Features
This chapter provides information for making configuration changes for the following advanced features:

Distinctive Ring Tones Tones Remote Phonebook LDAP Busy Lamp Field Shared Call Appearance As-Feature-Event Action URL Action URI Server Redundancy Network Address Translation SNMP 802.1X Authentication TR-069 Device Management
The Distinctive Ring Tones feature allows specific incoming calls to trigger the IP phone to play the distinctive ring tones. A SIP server can insert the Alert-Info header into the INVITE request, the Alert-Info header specifies an alternative ring tone to the IP phone. When the IP phone receives an incoming call, the IP phone inspects the INVITE request for an "Alert-Info" header. If the INVITE request contains no "Alert-Info" header, the IP phone will play the default ring tone configured on the IP phone. If the INVITE request contains an "Alert-Info" header, the IP phone strips out the URL and keywords. The IP phone tries to download the ring tone from the URL and play it. If failing to download the ring tone, the IP phone maps the keywords to the predefined criteria and plays the distinctive ring tone. The following are two examples of "Alert-Info" headers: Alert-Info: Alert-Info:
http://127.0.0.1/Bellcore-dr3 <http://192.168.0.12:8080/ring.wav>;info=Family;x-line-id=0
If the URL contains the keywords Bellcore-drN or MyMelodyN, the IP phone will strips out the index N from the keywords Bellcore-drN or MyMelodyN, and 51
then map the index N to the relevant ring tone. When N is 1, the IP phone plays the ring tone Emergency.wav . If N is greater than 1 and less than 9, the IP phone plays the ring tone Ring(N-1).wav . If N is greater than 9, the IP phone will play the default ring tone configured on the IP phone.
If the Alert-Info header contains a remote URL, the IP phone will play the ring tone downloaded from the URL. If failing to download the ring tone from the URL, the IP phone will map the keywords to the text which is configured on the phone, and then play the specified ring tone configured on the phone. If there is no text matched, the IP phone will play the default ring tone configured on the IP phone. The IP phone supports mapping ten internal ringer texts.
Procedure
Distinctive ring tones can be configured using the configuration files or locally. Configure the Internal Ringer Text and Internal Ringer File. Configuration File <y0000000000xx>.cfg For more information, refer to Distinctive Ring Tones on page 136. Configure the Internal Ringer Text and Internal Ringer File. Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=29 To configure the distinctive ring tones via web user interface: 1. 2. 3. Click on Phone->Ring. Enter the keywords in the Internal Ringer Text fields. Select the desired ring tones for each text from the pull-down lists of Internal Ringer File. 4. Click Confirm to save the change.
When receiving a message or recording a call, the IP phone will play a warning tone. You can customize tones or select the tones customized for a specific country to indicate different conditions of the IP phone. Tone sets vary from country to country. The default tones used on the phone is the tone sets of US. The tone sets you can configure on the IP phone are (only lists partially):

Australia Austria
52
Brazil China France Germany Great Britain Italy Mexico New Zealand United States
Configured tones can be heard on the phone for the following conditions: Condition Dial Ring Back Busy Congestion Call Waiting Dial Recall Record Info Stutter Message Auto Answer Description In the pre-dialing interface Ring-back tone When the callee is busy When the network is congested Call waiting tone Call hold tone When recording a call When receiving a special message When receiving a voice mail When receiving a text message When automatically answering a call
Procedure
Tones can be configured using the configuration files or locally. Configure the tones for the IP Configuration File <y0000000000xx>.cfg phone. For more information, refer to Tones on page 137. Configure the tones for the IP phone. Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=12
53
Remote phonebook is the phone book which is maintained centrally, you need to configure the access URL of the remote phonebook on the IP phone to access it. The IP phone can establish a session with the remote phonebook and download the entries, the entries then display on the phone user interface. The IP phone supports accessing 5 remote phonebooks. You can also customize the remote phonebook for the IP phone. For more information, refer to Remote XML Phonebook on page 87. The entries of the remote phonebook can be dialed out or added to the local directory, but cannot be deleted or edited locally. You can configure the IP phone to query the entry names from the remote phonebook when receiving incoming calls. You can also set the interval for the IP phone to update information of the remote phonebook. Note
The remote phonebook feature is not applicable to the SIP-T20P IP phone.
Procedure
Remote phonebook can be configured using the configuration files or locally. Specify whether to query the contact names from the remote phonebook when the IP phone receives incoming calls. Configuration File <y0000000000xx>.cfg Set the interval for the IP phone to update the information of the remote phonebook. For more information, refer to Remote Phonebook on page 138. Specify whether to query the contact names from the remote phonebook when the IP phone receives incoming calls. Local Web User Interface Set the interval for the IP phone to update the information of the remote phonebook. Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=6 To configure the features of the remote phonebook via web user interface: 1. Click on Phone->Features->General Information >>.
54
2. 3. 4.
Select the desired value from the pull-down list of SRemote Name. Enter the desired time in the SRemote Name Flash Time (seconds) field. Click Confirm to save the change.
LDAP (Lightweight Directory Access Protocol) is an application protocol for accessing and maintaining information services of the distributed directory over an IP network. The IP phone can be configured to interface with a corporate directory server that supports LDAP (Microsofts Active Directory is included). The biggest plus for LDAP is that the users can access the central LDAP directory of your corporate using the IP phone without having the need to maintain local directories. The central LDAP directory can be browsed or searched. Entries retrieved from the LDAP server can be added to the local directory on the IP phone. Calls can be placed based on the phone number contained in the LDAP entry. The LDAP directory interface shall be read only, so that editing or deleting the existing directory entries as well as adding new directory entries on the IP phone shall not be possible. When LDAP is properly configured, the IP phone can look up entries from the LDAP server in a wide variety of ways. The LDAP server indexes all the data in their entries, and "filters" may be used to select just the contact or the group you want, and return just the information you want. When configuring the LDAP on the IP phone, the configuration limits the amount of displayed entries when querying from the LDAP server, and decides how the attributes are displayed and sorted. Note
The LDAP feature is not applicable to the SIP-T20P IP phone.
There are two ways to perform a LDAP search on the IP phone:
Simply start a search against LDAP by entering a number. All suitable entries will be shown according to your query setup.
Assign a DSS key to be LDAP key. You can enter the LDAP Search interface by pressing the LDAP key when the phone is idle.
LDAP Attributes
Most common attributes are used to configure the LDAP lookup in your phone with: Abbreviation gn Name givenName First name LDAP attribute being made up cn commonName from given name joined to surname. Description
55
Abbreviation sn dn dc mobile ipPhone
Name surname distinguishedName dc company telephoneNumber mobilephoneNumber IPphoneNumber
Description Last name or family name Unique identifier for each entry Domain component Company or organization name Office phone number Mobile or cellular phone number Home phone number
Procedure
LDAP can be configured using the configuration files or locally. Configure the LDAP . For more information, refer to Configuration File <y0000000000xx>.cfg LDAP on page 139. Assign a LDAP key. For more information, refer to LDAP Key on page 176. Configure the LDAP . Navigate to: http://<phoneIPAddress>/cgi-bi Local Web User Interface n/ConfigManApp.com?Id=36 Assign a LDAP key. Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=21 To configure the LDAP via web user interface: 1. 2. 3. 4. Click on Contacts->LDAP. Enter the values in the corresponding fields. Select the desired values from the corresponding pull-down lists. Click Confirm to save the change.
56
The BLF feature on the IP phone allows one or more specific users to be monitored for status changes. A supervisor monitors the status of the users on the IP phone. Different indicators on the IP phone show the status of the monitored user. When the monitored user places a call, a busy indicator on the supervisors phone shows that the user s phone is in use and busy.
BLF Setting
When configuring a memory key (not applicable to the T22P and T20P) or line key to be a BLF key, specify the monitored user and configure the pickup code. When the monitored user is busy, the BLF key LED illuminates solid red (memory key) or flashes green (line key). You can press the BLF key to pick up the incoming call of the monitored user directly.
BLF List Setting

The BLF List feature on the IP phone is specifically designed to support the BroadSoft server. This feature allows the IP phone to monitor a list of users defined through the BroadWorks web portal. The BLF List feature must be provisioned on the BroadWorks web portal in advance, refer to the document Yealink IP Phones Deployment Guide for BroadWorks Environments for more information. The result of the provisioning will be a BLF List URI which represents a list of users to be monitored. You need to specify the BLF list URI on the IP phone to monitor the list of users. The BLF List URI is configurable on a per-account basis. The IP phone then automatically assigns BLF List keys according to the successful response messages from the BroadWorks.
Visual and Audio Alert for BLF Pickup

Commonly, a busy indicator shows on the supervisors phone when the monitored user receives an incoming call. You can configure the IP phone to play an alert tone and display a visual prompt (e.g. 6001<-6002, 6001 is the monitored extension) on the phone LCD screen to notify the supervisor of the incoming call of the monitored user.
Procedure
BLF feature can be configured using the configuration files or locally. Configure the BLF List URI and BLF list pickup and barge in <MAC>.cfg Configuration File codes. For more information, refer to BLF List on page 144. y0000000000xx.cfg Configure the BLF keys. For more information, refer to 57
BLF Key on page 176. Configure the IP phone whether to use visual and audio alert for BLF . For more information, refer to Visual and Audio Alert for BLF Pickup on page 145. Configure the BLF List URI and BLF list pickup and barge in codes. Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=4 Configure the BLF keys. Navigate to: Local Web User Interface http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=21 For more information, refer to the SIP-T2xP User Guide. Configure the IP phone whether to use visual and audio alert for BLF pickup. Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=6
The Shared Call Appearance (SCA) feature allows users to share a SIP line on several IP phones and also provides status monitoring of the shared line. When a user places an outgoing call using such a shared line, all members sharing that line are notified of this usage. LEDs available on the IP phones indicate the status of the shared line. Incoming calls to this line will cause all phones that share this line to ring simultaneously. The incoming call can be answered on one of the IP phones but not all of them. A SCA user can retrieve a call being put on public hold on the shared line. If the SCA bridging is configured, SCA users can barge in an existing call on the shared line. The SCA feature is specially designed to support the BroadSoft server. The SCA feature must be provisioned on the BroadWorks web portal in advance, refer to the document Yealink IP Phones Deployment Guide for BroadSoft BroadWorks Environments for more information. The result of the provisioning will be a primary line with the SCA activated plus one or more secondary lines that share the primary line, each 58
represented by its own unique SIP URI.
Procedure
Register the primary and secondary lines on two IP phones using the configuration files or locally. Configure the shared line on the IP phone. Configuration File <MAC>.cfg For more information, refer to Shared Call Appearance on page 146. Configure the shared line on the IP phone. Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=4 To register the primary and secondary lines via web user interface: 1. 2. Click on Account. Register the line as usual (entering the register name of the primary line in the Register Name field when registering the secondary line). 3. 4. 5. Click on Advanced>>. Select Broadsoft SCA from the pull-down list of Shared Line. Click Confirm to save the change.
The IP phone supports server-side Do Not Disturb (DND), Call Forward (CFWD) and Automatic Call Distribution (ACD) features. The as-feature-event feature allows the IP phone to synchronize the status of the following features with the server:

Do Not Disturb Call Forwarding Always (CFA) Call Forwarding Busy (CFB) Call Forwarding No Answer (CFNA) ACD
If the as-feature-event feature is enabled, a user changes the status of one of these features via web portal or feature access code (FAC), the server notifies the phone of the status change. Conversely, if the user changes the feature status on the IP phone, the IP phone notifies the server of the status change.
59
Procedure
As-feature-event feature can be configured using the configuration files or locally. Configure the as-feature-event. Configuration File <y0000000000xx>.cfg For more information, refer to As-Feature-Event on page 149. Configure the as-feature-event. Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=6 To configure the as-feature-event via web user interface: 1. 2. 3. Click on Phone->Features->General Information >>. Select Enabled from the pull-down list of Feature Synchronization. Click Confirm to save the change.
Action URL is a HTTP GET request allowing the IP phone to interact with web server applications. An administrator can specify a URL that triggers a GET when certain events occur. A HTTP GET request may contain variable name and variable value, which is separated by =. Each variable value starts with $ in the query part of the URL. The URL format is: http://IP address of server/help.xml? variable name=variable value (e.g. http:192.168.1.10/help.xml?mac=$mac). Action URLs can be only triggered by the predefined events (e.g. Log on). The following table lists the predefined events for Action URL triggering: Event Setup Completed Log On Log Off Register Failed Off Hook On Hook Incoming Call Outgoing Call Call Established Call Terminated 60 Description When the phone completes startup. When the phone successfully registers account. When the phone logs off the registered account. When the phone fails to register account. When the phone is off hook. When the phone is on hook. When the phone receives incoming call. When the phone places a call. When the phone establishes a call. When the phone terminates a call.
Event Open DND Close DND Open Always Forward Close Always Forward Open Busy Forward Close Busy Forward Open No Answer Forward Close No Answer Forward Transfer Call Blind Transfer Call Attended Transfer Call Hold Unhold Mute Unmute Missed Call IP Change Forward Incoming Call Reject Incoming Call Answer New Incoming Call Transfer Finished Transfer Failed Idle to Busy Busy to Idle
Description When the phone enables the DND mode. When the phone disables the DND mode. When the phone enables the always forward. When the phone disables the always forward. When the phone enables the busy forward. When the phone disables the busy forward. When the phone enables the no answer forward. When the phone disables the no answer forward When the phone transfers a call. When the phone blind transfers a call. When the phone performs the attended transfer. When the phone places a call on hold. When the phone retrieves a hold call. When the phone mutes a call. When the phone unmutes a call. When the phone misses a call. When the IP address of the phone changes. When the phone forwards an incoming call. When the phone rejects an incoming call. When the phones answers a new call. When the phone completes to forward a call. When the phone fails to transfer a call. When the state of the phone changes from idle to busy. When the state of phone changes from busy to idle.
61
The following table lists the variable values may be used when specifying the URL: Variable $mac $ip $model $firmware Description MAC address of the phone The current IP address of the phone Phone model Phone firmware version The SIP URI of the current account when the $active_url phone is in the incoming, outgoing or connecting state. The username of the current account when the $active_user phone is in the incoming, outgoing or connecting state. The host name of the current account when the $active_host phone is in the incoming, outgoing or connecting state. The SIP URI of the caller when the phone places a $local call. The SIP URI of the callee when the phone receives an incoming call. The SIP URI of the callee when the phone places a $remote call. The SIP URI of the caller when the phone receives an incoming call. The display name of the caller when the phone $display_local places a call. The display name of the callee when receives an incoming call. The display name of the callee when the phone $display_remote places a call. The display name of the caller when the phone receives an incoming call. $call_id The caller ID when in incoming, outgoing or connecting state.
Procedure
Action URL can be configured using the configuration files or locally. Configure the action URL on the Configuration File <y0000000000xx>.cfg IP phone. For more information, refer to Action URL on page 150.
62
Configure the action URL on the IP phone. Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=41
Opposite to Action URL, Action URI allows the IP phone to interact with web server application by receiving and handling HTTP GET requests. When receiving a URI, the IP phone will perform the specified action and response a 200 OK message. The HTTP GET request may contain variable name key and variable value, which is separated by =. The URI format is: http://IP address ofphone/cgi-bin/ConfigManApp.com?key= variable value (e.g. http://192.168.1.5/cgi-bin/ConfigManApp.com?key=MUTE). Entering the URI in the web browser triggers the IP phone to perform the predefined event (e.g. mute the call). The following table lists the variable values may be used when specifying the URI: Variable key=OK/key=ENTER key=SPEAKER key=F_TRANSFER key=VOLUME_UP key=VOLUME_DOWN key=MUTE key=F_HOLD key=X key=0-9/*/POUND key=L1-L6 key=D1-D10 key=F_CONFERENCE key=F1-F4 key=MSG key=HEADSET key=RD key=UP/DOWN/LEFT/RIGHT Phone Action Press the OK key or the Enter soft key. Press the Speaker key. Press the Transfer key. Increase the volume. Decrease the volume. Mute the call. Press the Hold key. Press the X key. Send the DTMF digit (0-9, * or #). Press the Line key. Press the DSS key. Press the Conference key. Press the Soft key. Press the MESSAGE key. Press the HEADSET key. Press the Redial key. Press the Navigation keys.
63
Variable key=Reboot key=AutoP key=DNDOn key=DNDOff
Phone Action Reboot the phone. Let the phone do auto provisioning. Activate the DND mode. Deactivate the DND mode.
Note
The variable does not work with all events. For example, the variable key=MUTE is only applicable when the IP phone is during a call.
For security reasons, the IP phone does not receive and handle the HTTP GET request by default. You need to specify which IP address may send the URI to the IP phone. When receiving the HTTP GET request from the specified IP address, the phone LCD screen prompts the message Allow Remote Control?. You can specify one or more trusted IP addresses on the IP phone, multiple IP addresses are separated by comma. You can also configure the IP phone to receive and handle the URI from any IP address.
Procedure
Specify the trusted IP address for Action URI using the configuration files or locally. Specify the trusted IP address(es) for sending the Configuration File <y0000000000xx>.cfg Action URI to the IP phone. For more information, refer to Action URI on page 151. Specify the trusted IP address(es) for sending the Local Web User Interface Action URI to the IP phone. Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=6 To configure the trusted IP address(es) for Action URI via web user interface: 1. 2. Click on Phone->Features->API Security>>. Enter the IP address in the Trusted Action URI Server List field. Multiple IP addresses are separated by comma. 3. Click Confirm to save the change.
64
Many SIP servers are deployed in redundant pairs, designated as primary and secondary servers. The IP phone must always contact the primary server except in failover conditions. Server redundancy is often required in VoIP deployments to ensure continuity of phone service, for events where the server needs to be taken offline for maintenance, the server fails, or the connection from the IP phone to the server fails. The IP phone is able to route to a secondary (or alternate) server in a failure situation, which requires the use of DNS SRV query for the resolution of proxy address as specified by RFC 3263. When the IP phone accesses the internet, it sends out a DNS SRV query to the server to look up the IP address and port, and then waits for a response from the server. The DNS SRV query involves NAPTR, SRV and A queries, which allows the IP phone to adapt to various deployment environments. The DNS SRV query is configurable on a per-account basis.
NAPTR (Naming Authority Pointer)

First, the IP phone sends the NAPTR query to get the SRV pointer and service type. As an example, consider the IP phone wishes to resolve sip:user@example.com. The IP phone performs a NAPTR query for that domain, and the following NAPTR records may be returned: order IN NAPTR IN NAPTR 90 100 pref 50 50 flags "s" "s" service "SIP+D2T" "SIP+D2U" regexp "" "" replacement _sip._tcp.example.com _sip._udp.example.com
Parameters are explained in the following table: Parameter Description Specifies preferential treatment for the specific record. order The order is from lowest to highest, lower order is MORE preferred. Specifies the preference to process multiple NAPTR pref records with the same order value. Lower value is MORE preferred. flags The flag s means to do an SRV lookup. Specifies the service available for SIP by the following rules: service SIP+D2U: SIP over UDP SIP+D2T: SIP over TCP SIP+D2S: SIP over SCTP SIPS+D2T: SIPS over TCP
65
Parameter regexp replacement
Description Always empty for SIP services. Specifies a DNS name to be used for the next query.
The IP phone picks the first record, because its order of 90 is lower than 100. The pref parameter is unimportant as there is no other record with order 90. The flag s indicates performing the SRV query next. TCP will be used, targeted to a host determined by an SRV query of _sip._tcp.example.com. If the flag of the NAPTR record is returned empty, the IP phone will use "sip:user@example.com" for the next NAPTR query.
SRV (Service Location Record)

The IP phone performs a SRV query on the record returned from the NAPTR for the host name and the port number. The following are examples of the SRV records returned: Priority IN SRV IN SRV 0 0 Weight 1 2 Port 5060 5060 Target server1.example.com server2.example.com
Parameters are explained in the following table: Parameter Priority Description Specifies preferential treatment for the specific host entry. Lower priority is MORE preferred. When priorities are equal, weight is used to differentiate Weight the preference. The preference is from highest to lowest. Again, keep the same to load balance. Port Target Identifies the port number to be used. Identifies the actual hosts for A query.
The two SRV records point to different hosts. The two records have the same priority 0. The weight of the second record is higher than the first one, so the second record is picked first. If there is no IP address returned in the response, the IP phone sends out the A query to look up the IP address. So in this case, the IP phone will use "server2.example.com" for the A query.
A (Host IP Address)
The IP phone performs A query on the record returned from the SRV for the host IP address. The following is an example of the returned A record. IN A 62.10.1.10
66
The following figure illustrates the IP phone is able to failover to an alternate server when there is no response to a REGISTER request.
Procedure
DNS SRV query can be configured using the configuration files or locally. Configure the DNS SRV query on the IP phone. Configuration File <MAC>.cfg For more information, refer to Server Redundancy on page 152. Configure the DNS SRV query on the IP phone. Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=4 To configure the DNS SRV query via web user interface: 1. 2. 3. 4. Click on Account. Select the desired account from the pull-down list of Account. Select DNS-SRV from the pull-down list of the Transport. Click Confirm to save the change.
Network Address Translation (NAT) is essentially a translation table that maps public IP address and port combinations to private IP address and port combinations. This reduces the need for a large amount of public IP addresses. The NAT feature helps ensure security since each outgoing or incoming request must go through a translation process, it also offers the opportunity to qualify or authenticate the request or match it to a previous request. But in the VoIP environment, NAT translation may break end-to-end connectivity.
67
NAT Traversal
In order to maintain connection with the remote party, the NAT traversal can be enabled on the IP phone. NAT traversal is a general term for techniques that establish and maintain IP connections traversing NAT gateways. The NAT traversal technique requires assistance from a STUN server.
STUN (Simple Traversal of UDP over NATs)

STUN is a standardized set of methods, including a network protocol, used in NAT traversal for applications of real-time voice, video, messaging, and other interactive IP communications. The STUN protocol allows applications operating behind a NAT to discover the presence of the network address translator, and to obtain the mapped (public) IP address and port number that the NAT has allocated for the UDP connections to remote parties. The protocol requires assistance from a third-party network server (STUN server) located on the opposing (public) side of the NAT. The NAT traversal and STUN server are configurable on a per-account basis.
Procedure
NAT traversal and STUN server can be configured using the configuration files or locally. Configure the NAT traversal and STUN server on the IP Configuration File <MAC>.cfg phone. For more information, refer to Network Address Translation on page 152. Configure the NAT traversal and STUN server on the IP Local Web User Interface phone. Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=4 To configure the NAT traversal and STUN server via web user interface: 1. 2. 3. 4. 5. Click on Account. Select the desired account from the pull-down list of Account. Select STUN from the pull-down list of NAT Traversal. Enter the IP address or the domain name in the STUN Server field. Click Confirm to save the change.
68
Simple Network Management Protocol (SNMP) is an Internet-standard protocol for managing devices on IP networks. It is used mostly in network management systems to monitor network-attached devices for conditions that warrant administrative attention. SNMP exposes management data in the form of variables on the managed systems, which describe the system configuration. These variables can then be queried by the managing applications. The variables accessible via SNMP are organized in hierarchies, which are described by Management Information Bases (MIBs). The IP phone does not accept the SNMP request by default, because SNMP might introduce unwanted security threats. The IP phone only supports the GET request of SNMP . The SET or other requests are not supported. When enabling SNMP , you need to specify which IP address may send SNMP requests to the IP phone. The following table lists the basic object identifiers (OIDs) supported by the IP phone: MIB OID Description The textual identification of the YEALINK-MIB 1.3.6.1.2.1.37459.2.1.1.0 contact person for the IP phone, together with the contact information. An administratively-assigned YEALINK-MIB 1.3.6.1.2.1.37459.2.1.2.0 name for the IP phone. If the name is unknown, the value is a zero-length string. YEALINK-MIB 1.3.6.1.2.1.37459.2.1.3.0 The physical location of the IP phone. The time (in milliseconds) since YEALINK-MIB 1.3.6.1.2.1.37459.2.1.4.0 the network management portion of the system was last re-initialized. YEALINK-MIB 1.3.6.1.2.1.37459.2.1.5.0 The IP phone's firmware version. The IP phone's hardware version. The IP phones model. The IP phones MAC address. The IP phones IP address. The version of auto provisioning. 69
YEALINK-MIB YEALINK-MIB YEALINK-MIB YEALINK-MIB YEALINK-MIB
1.3.6.1.2.1.37459.2.1.6.0 1.3.6.1.2.1.37459.2.1.7.0 1.3.6.1.2.1.37459.2.1.8.0 1.3.6.1.2.1.37459.2.1.9.0 1.3.6.1.2.1.37459.2.1.10.0
Procedure
SNMP can be configured using the configuration files or locally. Configure the SNMP on the IP Configuration File <y0000000000xx>.cfg phone. For more information, refer to SNMP on page 153. Configure the SNMP . Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=19 To configure the SNMP via web user interface: 1. 2. 3. 4. 5. Click on Network->Advanced. Select Enabled from the pull-down list of Active. Enter the desired port in the Port filed. Enter IP address(es) in the Trusted Address field. Click Confirm to save the change. The IP phone prompts reboot to make the settings effective.
The IP phone supports the IEEE 802.1X authentication. The 802.1X authentication is an IEEE Standard for Port-based Network Access Control (PNAC). It is part of the IEEE 802.1 group of networking protocols. It provides an authentication mechanism to devices wishing to attach to a LAN or WLAN. The 802.1X authentication involves three parties: a supplicant, an authenticator and an authentication server. The supplicant is the IP phone that wishes to attach to the LAN or WLAN. With 802.1X port-based authentication, the IP phone provides credentials, such as a user name and password, to the authenticator, and then the authenticator forwards the credentials to the authentication server for verification. If the authentication server determines the credentials are valid, the IP phone is allowed to access resources located on the protected side of the network. The IP phone supports using the EAP-MD5, EAP-TLS, PEAP-MSCHAPV2 protocols for 802.1X authentication.
Procedure
802.1X authentication can be configured using the configuration files or locally. Configure the 802.1X on the IP Configuration File <y0000000000xx>.cfg phone. For more information, refer to
70
802.1X on page 154. Configure the 802.1X on the IP phone. Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=19 To configure the 802.1X via web user interface: 1. 2. Click on Network->Advanced. Select the desired protocol from the pull-down list of 802.1X Mode. a) If you select EAP-MD5: 1) 2) Enter the username for authentication in the Identity field. Enter the password for authentication in the MD5 Password field.
b) If you select EAP-TLS: 1) 2) 3) Enter the username for authentication in the Identity field. Leave the MD5 Password field blank. In the CA Certificate field, click Browse to select the desired CA certificate from your local system. 4) In the Device Certificate field, click Browse to select the desired client certificate from your local system. 5) c) Click Upload to upload the certificates.
If you select PEAP-MSCHAPV2: 1) 2) 3) Enter the username for authentication in the Identity field. Enter the password for authentication in the MD5 Password field. In the CA Certificate field, click Browse to select the desired certificate from your local system. 4) Click Upload to upload the certificate.
3.
Click Confirm to save the change. The IP phone prompts reboot to make the settings effective.
71
TR-069 (Technical Report 069) is a DSL Forum (which was later renamed as Broadband Forum) technical specification entitled CPE WAN Management Protocol (CWMP). It defines an application layer protocol for remote management of end-user devices. It provides the communication between Customer-premises Equipment (CPE) and Auto Configuration Server (ACS). TR-069 uses common transport mechanisms (HTTP and HTTPS) for communication with CPE. The HTTP(S) messages contain XML-RPC methods defined in the standard for configuration and management of the device. Note
The TR-069 feature is only applicable to some specially designated firmware.
The TR-069 is intended to support a variety of functionalities to manage a collection of CPEs, including the following primary capabilities:

Auto-configuration and dynamic service provisioning Software or firmware image management Status and performance monitoring Diagnostics
The following table lists the RPC (Remote Procedure Call) methods required for the IP phone: RPC Method GetRPCMethods Description This method is used to discover the set of methods supported by the CPE. This method is used to modify the value of one or more CPE parameters. This method is used to obtain the value of one or more CPE parameters. This method is used to discover the parameters accessible on a particular CPE. This method is used to read the attributes associated with one or more CPE parameters. This method is used to modify attributes associated with one or more CPE parameters. This method causes the CPE to reboot. This method is used to cause the CPE to download a Download specified file from the designated location. File type supported by the Yealink IP phones are:
SetParameterValues
GetParameterValues
GetParameterNames
GetParameterAttributes
SetParameterAttributes Reboot
72
RPC Method

Description Firmware Image Configuration File
This method is used by an ACS to cause the CPE to upload a specified file to the designated location. Upload File type supported by the Yealink IP phones are:

Configuration File Log File
This method is used by an ACS to request the CPE to ScheduleInform schedule a one-time Inform method call (separate from its periodic Inform method calls) sometime in the future. FactoryReset This method resets the CPE to its factory default state, and calls for use with extreme caution. This method informs the ACS of the completion (either TransferComplete successful or unsuccessful) of a file transfer initiated by an earlier Download or Upload method call. AddObject This method is used to add a new instance of an object defined on the CPE. This method is used to remove a particular instance of an object.
DeleteObject
Procedure
TR-069 can be configured using the configuration files or locally. Configure theTR-069 feature. Configuration File <y0000000000xx>.cfg For more information, refer to TR-069 on page 156. Configure the TR-069 feature. Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=25 To configure the TR-069 via web user interface: 1. 2. 3. Click on Upgrade->TR069. Select Enabled from the pull-down list of Enable TR069. Enter the username and password authenticated by the ACS in the ACS Username and ACS Password fields. 4. Enter the URL of the ACS in the ACS URL field.
73
5. 6. 7.
Select the desired value from the pull-down list of Enable Periodic Inform. Enter the desired time in the Periodic Inform Interval (seconds) field. Enter the username and password authenticated by the IP phone in the Connection Request Username and Connection Request Password fields.
74
Security Features
This chapter provides information for making configuration changes for the following security-related features:

Transport Layer Security Encrypting Configuration Files
The TLS protocol is a commonly-used protocol for providing communications privacy and managing the security of message transmission. The TLS allows the IP phone to communicate with other remote parties and connect to the HTTPS URL for provisioning in a way that is designed to prevent eavesdropping and tampering. The TLS protocol is composed of two layers: the TLS Record Protocol and the TLS Handshake Protocol. The TLS Record Protocol completes the actual data transmission and ensures the integrity and privacy of the data. The TLS Handshake Protocol allows the server and client to authenticate each other and negotiate an encryption algorithm and cryptographic keys before data is exchanged. The following figure shows the TLS messages are exchanged to establish encrypted communications:
Step1: IP phone sends Client Hello message proposing SSL options. Step2: Server responds with Server Hello message selecting the SSL options, sends its public key information in Server Key Exchange message and concludes its part of the negotiation with Server Hello Done message. Step3: IP phone sends session key information (encrypted with server s public key) in the Client Key Exchange message. Step4: Server sends Change Cipher Spec message to activate the negotiated options for all future messages it will send. The IP phone can encrypt SIP with TLS, which is to say "SIPS". When an account is enabled the TLS, the SIP and RTP messages of this account will be encrypted and 75
cannot be captured, a lock icon appears on the LCD screen when the IP phone is in the connecting state or in the calling state. TLS uses a program layer located between the internet's HTTP and TCP layers. TLS is designed to make use of TCP as a communication layer to provide a reliable end-to-end secure and authenticated connection between two points over a network. TLS provides mechanisms to secure your phone traffic. The IP phone initiates a TLS connection when the IP phone connects to the HTTPS URL for provisioning. In order to use the TLS on the IP phone, you need to do the following steps:

Uploading certificates to the IP phone Configuring the IP phone to use the TLS
Certificates
The IP phone can serve as a TLS client or a TLS server. The TLS requires the use of the following security certificates to perform the TLS handshake:
Trusted Certificate: when the IP phone requests the TLS connection with a server, the IP phone should verify that whether the server can be trusted. The IP phone has no inbuilt trusted certificate. You can upload up to 10 trusted certificates to the IP phone.
Server Certificate: when the other clients request the TLS connection with the IP phone, the IP phone sends the server certificate to the clients for authenticating. The IP phone has no inbuilt server certificate by default. You can only upload one server certificate to the IP phone. The old server certificate will be overwritten by the new uploading one.
In order to authenticate the connected server, you need to enable the Only Accepted Trusted Certificates feature on the IP phone. The IP phone will only accept the same certificates as listed in the Trusted Certificates list. The IP phone will check the certificate sent by the server based on the existing certificates in the Trusted Certificates list. You can configure the TLS on a per-account basis.
Procedure
Configure the TLS and upload certificates using the configuration files or locally. Configure the IP phone to use TLS and authenticate the connected server. For more information, refer to Configuration File <y0000000000xx>.cfg TLS on page 159. Upload certificates to the IP phone. For more information, refer to Uploading Certificates on page
76
Security Features
160. Configure the IP phone to use TLS. Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=4 Upload the certificates to the IP phone. Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=8 Configure the IP phone to authenticate the connected server. Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=32 To configure the TLS via web user interface: 1. 2. 3. 4. Click on Account. Select the desired account from the pull-down list of Account. Select TLS from the pull-down list of the Transport. Click Confirm to save the change.
To configure the Only Accepted Trusted Certificates feature via web user interface: 1. 2. 3. Click on Security->Trusted Certificates. Select the desired value from the pull-down list of Only Accept Trusted Certificates. Click Confirm to save the change.
To upload the trusted certificate via web user interface: 1. 2. 3. Click on Security->Trusted Certificates. Click Browse to select the trusted certificate from your local system. Click Upload to complete uploading the trusted certificate.
To upload the server certificate via web user interface: 1. 2. 3. Click on Security->Server Certificates. Click Browse to select the server certificate from your local system. Click Upload to complete uploading the server certificate.
77
The IP phone can download the encrypted configuration files from the configuration server to protect against unauthorized access and tampering of sensitive information (i.e., login passwords, registration information). Configuration files can be encrypted using a command line tool. The encryption algorithm is AES 128. From a Microsoft Windows command line, an administrator can use the Yealink-supplied encryption tool called "EncryptUtilityWindows.exe" to encrypt the <y0000000000xx>.cfg and <MAC>.cfg files respectively. Note
Yealink also supplies an encryption tool (EncryptUtilityLinux.exe) to support Linux platforms if required. You can also encrypt the configuration files using the Yealink Configuration Conversion Tool. Refer to the Yealink Configuration Conversion Tool User Guide for more information.
The filename extension of the encrypted configuration files must be .cfg. The common AES key is used to encrypt and decrypt the <y0000000000xx>.cfg file and the MAC-Oriented AES key is used to encrypt decrypt the <MAC>.cfg file. The AES keys must be configured on the phone before downloading the encrypted configuration files. The AES keys must be 16 characters.
Procedure to Encrypt Configuration Files

To encrypt the <y0000000000xx>.cfg file: 1. Save the EncryptUtilityWindows.exe tool and <y0000000000xx>.cfg file to the same directory (i.e., D:\). 2. 3. Open a command line window application (i.e., DOS window). Enter the following command, and then press the <Enter> key. D:EncryptUtilityWindows.exe 123456789abcdef0 e F:\y000000000000.cfg D:\y000000000000.cfg #D:EncryptUtilityWindows.exe <a 16-character secret key> e <a new directory and file name for the encrypted configuration file> <the directory and file name of the configuration file to be encrypted> 4. Save the encrypted configuration file to the root directory of the configuration server. To configure the common AES key via web user interface: 1. 2. 3. Click on Upgrade->Advanced. Enter the secret key (i.e., 123456789abcdef0) in the Common AES Key field. Click Confirm to save the change.
The way for encrypting the <MAC>.cfg file is the same as the < y0000000000xx >.cfg file, and then configure the MAC-Oriented AES key in the MAC-Oriented AES Key field. 78
Security Features
For security purposes, it may be necessary for you to change the AES keys on the IP phone frequently. The process of updating the new AES keys includes decrypting the configuration files with the old AES keys and encrypting them with the new AES keys. After changing the AES keys, all encrypted configuration files on the configuration server are expected to be encrypted with the new AES keys.
Procedure
AES keys can be changed using the configuration files or locally. Change the AES keys. Configuration File <y0000000000xx>.cfg For more information, refer to Change AES Keys on page 160. Change the AES keys. Local Web User Interface Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=16 To change the AES keys via web user interface: 1. 2. 3. Click on Upgrade->Advanced. Modify the values in the Common AES Key and MAC-Oriented AES Key fields. Click Confirm to save the change.
79
80
Upgrading the Firmware
This chapter provides information about upgrading the phone firmware. There are two methods that you can use to upgrade the firmware on the IP phone:

Upgrade the firmware manually from the local system Upgrade the firmware periodically or at a specific time from the configuration server
The following table lists the associated firmware for each IP phone model: IP Phone Model SIP-T28P SIP-T26P SIP-T22P SIP-T20P Associated Firmware 2.x.x.x.rom 6.x.x.x.rom 7.x.x.x.rom 9.x.x.x.rom
Note
You can download the latest firmware at: http://www.yealink.com/index.php/Support/.
Upgrade via Web User Interface

To manually upgrade firmware via web user interface, you need to store the firmware to your local system in advance. To upgrade the firmware manually via web user interface: 1. 2. 3. 4. Click on Upgrade. Click Browse. Select the firmware from the local system. Click Upgrade. The web user interface pops up the dialog box Firmware of the IP Phone will be updated. It will take 5 minutes to complete. Please don't power off!. 5. Note Click OK to confirm the upgrading.
Do not unplug the network and power cables when the phone is upgrading the firmware. Do not close the browser when the phone is upgrading the firmware via web user interface.
81
Upgrade Firmware via Configuration Files

The IP phone can download the firmware from the configuration server by stripping out the access URL of the firmware specified in the configuration files. To upgrade the firmware from the configuration server, the configuration server should be ready and able to accept connections. The IP phone can download the firmware stored on the configuration server in one of two ways:
The IP phone checks for both configuration files and firmware stored on the configuration server during the bootup process.
The IP phone automatically updates configuration files and looks for firmware at a fixed interval or at specific time.
You can configure the way for the IP phone to update configuration files and look for firmware.
Procedure
Configuration can be performed using the configuration files or locally. Configure the way for the phone to check for configuration files. Configuration File <y0000000000xx>.cfg Specify the access URL of the firmware. For more information, refer to Upgrading the Firmware on page 161. Configure the way for the phone to check for configuration files (the access URL of the firmware should be Local Web User Interface configured in the configuration files in advance). Navigate to: http://<phoneIPAddress>/cgi-bi n/ConfigManApp.com?Id=16 To configure the way for the phone to check for new configuration files via web user interface: 1. 2. 3. Click on Upgrade->Advanced. Select the desired value from the pull-down list of Check New Config. Click Confirm to save the change.
When the Check New Config is set to Power on, restarting the IP phone forces it to check for both firmware and configuration files stored on the configuration server. 82
Resource Files
When configuring some features, you may need to upload resource files to the IP phone. The resources files can be local contact directory, remote phonebook and so on. If the resource file is to be used for a system of IP phones, the access URL of the resource file is best specified in the <y000000000000>.cfg file. However, if you want to specify the desired phone to use the resource file, the access URL of the resource file is best specified in the <MAC>.cfg file. This chapter will provide the detailed information on how to work with the following resource files and specify the access URL:

Replace Rule Template Dial-now Template Local Contact File Remote XML Phonebook Specifying the Access URL of Resource Files
You can create multiple replace rules using the replace rule template. After creating the replace rule template, save the replace rule template to the root directory of the configuration server and specify the access URL in the configuration files. When creating a replace rule template, remember the following:

A replace rule template must be in .xml format. <DialRule> indicates the start of a template and </DialRule> indicates the end of a template.
At most 20 replace rules can be added to the IP phone. The expression syntax in the replace rule template is the same as introduced in the section Creating Dial Plan on page 21.
Specify the values within double quotes. When specifying the desired line(s) for the replace rule, the valid values are 0 and line ID. 0 stands for all lines, multiple line IDs are separated by comma.
The file name must be dialplan.xml.
Procedure
Use the following procedures to create a replace rule template.
83
Creating a replace rule template: 1. 2. 3. Using an ASCII editor, create a new file. Type <DialRule> to indicate the start of the replace rule template. Add the following string to the template, each starting on a separate line: <Data Prefix="" Replace= LineID=""/> Where: Prefix="" specifies the numbers to be replaced. Replace= specifies the alternate string instead of what the user enters. LineID="" specifies the desired line(s) for this rule. When leaving it blank, the IP phone will apply to all lines. 4. When completed, type </DialRule> to indicate the end of the replace rule template. 5. Save this file to the root directory of the configuration server.
The following is an example of a replace rule template: <DialRule> <Data Prefix="1" Replace="05928665234" LineID=""/> <Data Prefix="2(xx)" Replace="002$1" LineID="0"/> <Data Prefix="5([6-9])(.)" Replace="3$2" LineID="1,2,3"/> <Data Prefix="0(.)" Replace="9$1" LineID="2"/> <Data Prefix="1009" Replace="05921009" LineID="1"/> </DialRule>
You can create multiple dial-now rules using the dial-now template. After creating the dial-now template, save the dial-now template to the root directory of the configuration server and specify the access URL in the configuration files. When creating a dial-now template, remember the following:

A dial-now template must be in .xml format. <DialNow> indicates the start of a template and </DialNow> indicates the end of a template.
At most 20 rules can be added to the IP phone. The expression syntax in the dial-now rule template is the same as introduced in the section Creating Dial Plan on page 21.
Specify the values within double quotes. When specifying the desired line(s) for the dial-now rule, the valid values are 0 and
84
Resource Files
line ID. 0 stands for all lines, multiple line IDs are separated by comma.
The file name must be dialnow.xml.
Procedure
Use the following procedures to create dial-now template. Creating a dial-now template: 1. 2. 3. Using an ASCII editor, create a new file. Type <DialNow> to indicate the start of the dial-now template. Add the following string to the template, each starting on a separate line: <Data DialNowRule="" LineID=""/> Where: DialNowRule="" specifies the dial-now rule. LineID="" specifies the desired line(s) for this rule. When leaving it blank, the IP phone will apply to all lines. 4. 5. When completed, type </DialNow> to indicate the end of the dial-now template. Save this file to the root directory of the configuration server.
The following is an example of a dial-now template: <DialNow> <Data DialNowRule="1234" LineID="1"/> <Data DialNowRule="52[0-6]" LineID="1"/> <Data DialNowRule="xxxxxx" LineID=""/> </DialNow>
You can add contact one by one on the phone directly. In some cases, you may want to add multiple contacts to the phone at the same time or share the contacts on many IP phones. You can create a local contact file, then save the local contact file to the root directory of the configuration server, specify the access URL of the contact file in the configuration files. When creating a local contact file, remember the following:

The contact file must be in .xml or .csv format. <contactData> indicates the start of a contact file and </contactData> indicates the end of a contact file.
<group> indicates the start of a contact list and </group> indicates the end of a contact list.
85
<groupinfo> indicates the start of a group list and </groupinfo> indicates the end of a group list.
Specify the values within double quotes. When specifying a ring tone for the contact or the group, the format of the value must be Auto, Resource:RingN.wav (for the default system ring tone) or Custom:Name.wav (for the customized ring tone).
When specifying the desired line for the contact, the valid values are 0 and line ID, 0 stands for all lines, multiple line IDs are separated by comma.
The name of the contact file must be contactData1.xml or contactData1.csv.
Procedure
Use the following procedures to create a local contact file. Creating a local contact file: 1. 2. 3. 4. Using an ASCII editor, create a new file. Type <contactData> to indicate the start of the contact file. Type <group> to indicate the start of the contact list. For each contact that you wish to add, add the following string to the file, each starting on a separate line: <contact sDisplayName="" sOfficeNumber="" sMobilNumber="" sOtherNumber="" sLine="" sRing="" group=""/> Where: contact sDisplayName= specifies the name of the contact (This value cannot be blank or duplicated). OfficeNumber= specifies the office number of the contact. sMobilNumber= specifies the mobile number of the contact. sOtherNumber= specifies the other number of the contact. sLine= specifies the line you want to add this contact to. sRing= specifies the ring tone for this contact. group= specifies the existing group you want to add the contact to. 5. 6. 7. Type </group> to indicate the end of the contact list. Type <groupinfo> to indicate the start of the group list. For each group that you want to add, add the following string to the file, each starting on a separate line: <group name= ring=/> Where: group name= specifies the name of the group. ring= specifies the desired ring tone for this group. 86
Resource Files
8. 9.
Type </groupinfo> to indicate the end of the group list. When completed, specify </contactData> to indicate the end of the contact file.
10. Save this file to the root directory of the configuration server. The following is an example of a local contact file: <contactData> <group> <contact sDisplayName="Alice" sOfficeNumber="2215" sMobilNumber="" sOtherNumber="" sLine="0" sRing="Auto" group="Friend"/> <contact sDisplayName="Bob" sOfficeNumber="2216" sMobilNumber="" sOtherNumber="" sLine="2" sRing="Resource:Ring2.wav" group="Family"/> </group> <groupinfo> <group name="Friend" Ring="Auto"/> <group name="Family" ring="Custom:family.wav"/> </groupinfo> </contactData>
The IP phone can access 5 remote phonebooks. You can customize the remote XML phonebook for the IP phone as required. Before specifying the access URL of the remote phonebook in the configuration files, you need to create a remote XML phonebook and then store it to the configuration server. When creating a XML phonebook, remember the following:

The phonebook must be in .xml format. <YealinkIPPhoneDirectory> indicates the start of a phonebook and </YealinkIPPhoneDirectory> indicates the end of a phonebook.
<DirectoryEntry> indicates the start of a contact and </DirectoryEntry> indicates the end of a contact.
Procedure
Use the following procedures to create a XML phonebook. Creating a XML phonebook: 1. 2. 3. Using an ASCII editor, create a new file. Type <YealinkIPPhoneDirectory> to indicate the start of the phonebook. Type <DirectoryEntry> to indicate the start of each contact. 87
4.
For each contact that you wish to add, add the following strings to the phonebook, each starting on a separate line: <Name>Mary</Name> <Telephone>1001</Telephone> Where: Specify the contact name between <Name> and </Name>. Specify the contact number between <Telephone> and </Telephone>.
5. 6.
Type </DirectoryEntry> to indicate the end of each contact. When completed, type </YealinkIPPhoneDirectory> to indicate the end of the phonebook.
7.
Save this file to the root directory of the configuration server.
The following is an example of a XML phonebook: <YealinkIPPhoneDirectory> <DirectoryEntry> <Name>Jack</Name> <Telephone>1003</Telephone> </DirectoryEntry> <DirectoryEntry> <Name>John</Name> <Telephone>1004</Telephone> </DirectoryEntry> <DirectoryEntry> <Name>Marry</Name> <Telephone>1005</Telephone> </DirectoryEntry> </YealinkIPPhoneDirectory>
Access URL of the resource file can be configured in the configuration files: Configure the access URL of the replace rule template. Configuration File <y0000000000xx>.cfg For more information, refer to Access URL of Replace Rule Template on page 163. Configuration File <y0000000000xx>.cfg Configure the access URL of the
88
Resource Files
dial-now rule template. For more information, refer to Access URL of Dial-now Template on page 164. Configure the access URL of the local contact file. Configuration File <y0000000000xx>.cfg For more information, refer to Access URL of Local Contact File on page 164. Configure the access URL of the remote XML phonebook. Configuration File <y0000000000xx>.cfg For more information, refer to Access URL of Remote XML Phonebook on page 165.
89
90
Troubleshooting
This chapter provides an administrator with general information for troubleshooting some most common problems that may encounter while using the SIP-T2xP IP phones.
The IP phone can provide feedback in a variety of forms such as log files, packets, status indicators and so on, which helps an administrator quickly find out the cause of failure and do the troubleshooting more easily. If you encounter a problem which is not listed in this chapter, contact your Yealink reseller for further support. The following are some methods for you to learn more about the working status of you IP phone and quickly find out the cause of failure.

Viewing Log Files Capturing Packets Enabling the Watch Dog Feature Getting Information from Status Indicators Analyzing Configuration Files
The IP phone can log various events to log files. So if your IP phone encounters some problems, commonly the log files are used. You can export the log files to a syslog server or the local system. You can specify the location for which to save log files for troubleshooting purposes using the configuration files or the web user interface. You can also set the system log level to specify the severity level of the logs to be reported to a log file. The system log level is 3 by default (Changes to this parameter via web user interface require a reboot). In the configuration files, you can use the following parameters to configure log settings:
syslog.server--Specify the IP address of the syslog server where to export the log files.
syslog.log_level--Specify the severity level of the logs to be reported to a log file.
For more information about the log setting configuration parameters, refer to Log Settings on page 165.
91
To configure the level of the log files via web user interface: 1. 2. 3. Click on Upgrade->Advanced. Select the desired level from the pull-down list of Log Level. Click Confirm to accept the change. The web user interface prompts It will take effect after reboot, reboot now?. 4. Click OK to reboot the phone.
To export log files to a syslog server via web user interface: 1. 2. 3. 4. Click on Upgrade->Advanced. Select Server from the pull-down list of Export System Log. Enter the address of the syslog server. Click Confirm to save the change.
To export log files to the local system via web user interface: 1. 2. 3. Click on Upgrade->Advanced. Select Local from the pull-down list of Export System Log. Click Export to open file download window, and then save the file to your local system. The following figure shows a portion of a log file:
You can capture packets in two ways: capturing the packets via web user interface or 92
Troubleshooting
using the Ethernet software. You can analyze the packets captured for troubleshooting purposes. To capture packets via web user interface: 1. 2. 3. 4. 5. Click on Upgrade->Advanced. Click Start to begin capturing signal traffic. Reproduce the issue to get stack traces. Click Stop to end capturing. Click Export to open file download window, and then save the file to your local system. To capture packets using the Ethernet software: Connect the phones Internet port with the PC to the same HUB, use Sniffer, Ethereal or Wireshark, etc. software to capture the packets. You can also set a mirror port in the switch to monitor the port of the connected IP phone.
The IP phone provides a troubleshooting feature called Watch Dog, which helps you monitor the phone status and provides the ability to get stack traces from the last time the phone failed. When the Watch Dog feature is enabled, the IP phone will automatically reboot when it detects a fatal failure. This feature can be configured using the configuration files or the web user interface. You can use the watch_dog.enable parameter to configure the Watch Dog feature in the configuration files. For more information, refer to Watch Dog on page 166. To enable the Watch Dog feature via web user interface: 1. 2. 3. Click on Phone->Preference. Select Enabled from the pull-down list of Watch Dog. Click Confirm to save the change.
In some cases, the status indicators consist of power LED, message key indicator, line key indicator, headset key indicator and the on-screen icon/error messages, which are useful for you to figure out the cause of your phones failure. The following are two examples of getting the device information from status indicators:
If a LINK failure of the IP phone is detected, a prompting message Network Unavailable and the icon indicate the current network LINK status.
If the power LED is off, which indicates the IP phone is powered off.
For more information about the icons, refer to Reading Icons on page 19. 93
Sometimes, configuration errors may lead to your phones failure. You can export configuration files to view the current configuration of the IP phone and troubleshoot as necessary. To export configuration files via web user interface: 1. 2. Click on Upgrade->Advanced. Click Export to open the file download window, and then save the file to your local system.
This section describes solutions to some most common problems that may occur while using the IP phone.
Do one of the following:

Check that the power LED is on to ensure the phone is powered on. Ensure the phone is properly plugged into a functional AC outlet. Ensure that the phone isnt plugged into a plug controlled by a switch that is off. If the phone is plugged into a power strip, try plugging it directly into a wall outlet instead.
If your phone is powered from PoE, ensure you use a PoE compliant switch or hub.
Ensure that the Ethernet cable is plugged into the Internet port on the phone and the Ethernet cable is not loose.
Ensure the Ethernet cable is not damaged. Ensure the IP address and other network parameters are set correctly. Ensure that the switch or hub in your network is operational.
94
Troubleshooting
The phone LCD screen prompts No Service message when there is no any available SIP account on the IP phone. Do one of the following:
Confirm if any account is actively registered on the IP phone at the path Menu->Status->More ->Accounts.
Check if the SIP parameters of the account have been set up correctly.

Ensure that the target firmware is not the same as the current used firmware. Ensure that the target firmware is applicable to the phone model. Ensure that the current or the target firmware is not protected. Ensure that the power is on and the network is available in the process of upgrading.
Ensure the web browser is open when upgrading the firmware using the web user interface.
Check if you have configured your phone to obtain the time and date from the NTP server automatically. If your phone is unable to access the NTP server, configure the time and date manually.
During a call, you may experience poor audio, including intermittent voice, low volume, echo or other noise. The root cause of audio anomalies can be difficult to diagnose.
Problems may occur simply because the users are seated too far out of recommended microphone range and sound faint, or are seated too close to sensitive microphones and cause feedback.
Intermittent voice is mainly caused by packet loss and jitter. Packet loss may due to network congestion. Jitter is mainly due to message recombination of transmission or receiving equipment, such as timeout handling, retransmission mechanism or buffer under run.
Noisy equipment, such as a computer or a fan, may make it difficult for hear the
95
voice from the other party clearly. Turn off any other noisy equipment in the room such as fans.
A line issue may also cause this problem. Disconnect the old line and redial the call to see if another line provides better connection.

Ensure the configuration is set correctly. Reboot the phone, some configurations need reboot to take effect. Ensure the configuration is applicable to the phone model. The configuration may depend on support from the server.

Try to set another available IP address for the IP phone. Check the configuration of the network via phone user interface at the path Menu->Settings->Advanced Settings->Network->WAN Port. If Static IP Address is select, select DHCP instead.
In the process of upgrading the phone firmware, if the power is powered off or the network is unavailable, the IP phone cant upgrade and boot up successfully. In this case, you need to do the following steps to resume your phone in a recovery mode. 1. Rename the firmware file (<phone model>.rom) that you want to download to the IP phone. For example, T28.rom (for a SIP-T28P IP phone). 2. 3. 4. Save the firmware to the root directory of the TFTP server (required). Unplug the power cable at the rear of the IP phone. Long press the Speakerphone key as soon as you re-plug the power cable. The IP phone prompts you to enter the information: IP address of the IP phone, subnet mask, gateway and the IP address of the TFTP server. After finishing the above steps, the IP phone starts the upgrade process.
Reset your phone to factory configurations after you have tried almost all troubleshooting suggestions but do not correct the problem. You need to note that all 96
Troubleshooting
customized settings will be overwritten after resetting. To reset your phone via web user interface: 1. 2. Click on Upgrade. Click Reset in the Reset to Factory Settings field. The web user interface prompts the message Do you want to reset to factory?. 3. Click OK to confirm the resetting.
97
98
Appendix
802.1x--an IEEE Standard for port-based Network Access Control (PNAC). It is part of the IEEE 802.1 group of networking protocols. It provides an authentication mechanism to devices wishing to attach to a LAN or WLAN. ACD (Automatic Call Distribution)--used to distribute calls from large volumes of incoming calls to the registered IP phone users. ACS (Auto Configuration Server)--responsible for auto-configuration of the Central Processing Element (CPE). Cryptographic Key--a piece of variable data that is fed as input into a cryptographic algorithm to perform operations such as encryption and decryption, or signing and verification. DHCP (Dynamic Host Configuration Protocol)--built on a client-server model, where designated DHCP server hosts allocate network addresses and deliver configuration parameters to dynamically configured hosts. DHCP Option--can be configured for specific values and enabled for assignment and distribution to DHCP clients based on server, scope, class or client-specific levels. DNS (Domain Name System)--a hierarchical distributed naming system for computers, services, or any resource connected to the Internet or a private network. EAP-MD5 (Extensible Authentication Protocol-Message Digest Algorithm 5)--only provides authentication of the EAP peer to the EAP server but not mutual authentication. EAP-TLS (Extensible Authentication Protocol-Transport Layer Security) Provides for mutual authentication, integrity-protected cipher suite negotiation between two endpoints. PEAP-MSCHAPV2 (Protected Extensible Authentication Protocol-Microsoft Challenge Handshake Authentication Protocol Version 2) Provides for mutual authentication, but does not require a client certificate on the phone. FAC (Feature Access Code)--special patterns of characters that are dialed from a phone keypad to invoke particular features. HTTP (Hypertext Transfer Protocol)--used to request and transmit data on the World Wide Web. HTTPS (Hypertext Transfer Protocol over Secure Socket Layer)--a widely-used communications protocol for secure communication over a network. 99
IEEE (Institute of Electrical and Electronics Engineers)--a non-profit professional association headquartered in New York City that is dedicated to advancing technological innovation and excellence. LAN (Local Area Network)--used to interconnects network devices in a limited area such as a home, school, computer laboratory, or office building. MIB (Management Information Base)--a virtual database used for managing the entities in a communications network. OID (Object Identifier)--assigned to an individual object within a MIB. PNP (Plug and Play)--a term used to describe the characteristic of a computer bus, or device specification, which facilitates the discovery of a hardware component in a system, without the need for physical device configuration, or user intervention in resolving resource conflicts. ROM (Read-only Memory)--a class of storage medium used in computers and other electronic devices. RTP (Real-time Transport Protocol)--provides end-to-end service for real-time data. TCP (Transmission Control Protocol)--a transport layer protocol used by applications that require guaranteed delivery. UDP (User Datagram Protocol)--a protocol offers non-guaranteed datagram delivery.
URI (Uniform Resource Identifier)--a compact sequence of characters that identifies an

abstract or physical resource.
URL (Uniform Resource Locator)--specifies the address of an Internet resource.

VLAN (Virtual LAN)-- a group of hosts with a common set of requirements, which communicate as if they were attached to the same broadcast domain, regardless of their physical location. VoIP (Voice over Internet Protocol)--a family of technologies used for the delivery of voice communications and multimedia sessions over IP networks. WLAN (Wireless Local Area Network)--a type of local area network that uses high-frequency radio waves rather than wires to communicate between nodes. XML-RPC (Remote Procedure Call Protocol)--which uses XML to encode its calls and HTTP as a transport mechanism.
100
Appendix
This appendix describes the parameters you can set in the configuration files for the IP phone. The configuration files are <y0000000000xx>.cfg and <MAC> .cfg.
You can set specific parameters in the configuration files for configuring you IP phone. The <y0000000000xx>.cfg and <MAC>.cfg files are stored on the configuration server. The IP phone checks for configuration files and looks for resource files when restarting the IP phone. The <y0000000000xx>.cfg file stores configurations for all phones of the same model. The <MAC>.cfg file stores configurations specific to the IP phone with that MAC address. Configuration changes made in the <mac>.cfg file override the configuration settings in the <y0000000000xx>.cfg file.
Parameternetwork.internet_port.type
Configuration File <y0000000000xx>.cfg Defines the WAN port type.
Description
Note: If you change this parameter, the phone will reboot to make the change take effect.
Format Default Value
Integer 0 Valid values are:
Range
0-DHCP 1-PPPoE 2-Static IP Address
Example
network.internet_port.type = 0
Parameternetwork.internet_port.ip Description
Configuration File <y0000000000xx>.cfg Configures the IP address when using static
101
WAN settings. Note: If you change this parameter, the phone will reboot to make the change take effect. Format Default Value Range Example Dotted Decimal Blank Not Applicable network.internet_port.ip = 192.168.1.20
Parameternetwork.internet_port.mask
Configuration File <y0000000000xx>.cfg Configures the subnet mask.
Description
Format Default Value Range Example
Dotted Decimal Blank Not Applicable network.internet_port.mask = 255.255.255.0
Parameternetwork.internet_port.gateway
Configuration File <y0000000000xx>.cfg Configures the default gateway.
Description
Dotted Decimal Blank Not Applicable network.internet_port.gateway = 192.168.1.254
Parameternetwork.primary_dns
Configuration File <y0000000000xx>.cfg Configures the primary DNS server.
Description
102
Appendix
Dotted Decimal 202.101.103.55 Not Applicable network.primary_dns = 202.101.103.5
Parameternetwork.secondary_dns
Configuration File <y0000000000xx>.cfg Configures the secondary DNS server.
Description
Dotted Decimal 202.101.103.56 Not Applicable network.secondary_dns = 202.101.103.6
Replace Rule
Parameterdialplan.item.x Configuration File <y0000000000xx>.cfg Creates the replace rule. dialplan.item.x = Enabled, Prefix, Replaced, Replaced, Line ID Enabled: Enables or disables the replace rule. Prefix: Specifies the numbers you want to Description replace. Replaced: Specifies the alternate string instead of what the user enters. Line ID: Specifies the desired line to apply this replace rule. X ranges from 1 to 20. Format Default Value Range Integer, String, String, Integer Blank Enabled Valid values are: 0-Disabled 103
1-Enabled Prefix, Replaced: Not Applicable Line ID valid values are: 1 to 6 (for T28P) 1 to 3 (for T26P/T20P) 1 to 2 (for T20P) Note: Multiple line IDs are separated by comma. Example dialplan.item.1 = 1,123,0592,1,2,3
Dial-now
Parameterdialnow.item.x Configuration File <y0000000000xx>.cfg Creates the dial-now rule. dialnow.item.x = Dial-now Rule, Line ID Dial-now Rule: Specifies the number Description automatically dialed out by the phone without pressing the send key. Line ID: Specifies the desired line to apply this dial-now rule. X ranges from 1 to 20. Format Default Value String, Integer Blank Dial-now Rules: Not Applicable Line ID Valid values are: 1 to 6 (for T28P) Range 1 to 3 (for T26P/T20P) 1 to 2 (for T20P) Note: Multiple line IDs are separated by comma. Example dialnow.item.1 = 2216,1,2,3
Area Code
Parameterdialplan.area_code.code Description Configuration File <y0000000000xx>.cfg Defines the area code to add before the entered numbers.
104
Appendix
Integer Blank Not Applicable dialplan.area_code.code = 010
Parameterdialplan.area_code.min_len Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Sets the minimum length of the entered numbers to add the area code. Integer 1 1 to 15 dialplan.area_code.min_len = 2
Parameterdialplan.area_code.max_len
Configuration File <y0000000000xx>.cfg Sets the maximum length of the entered
Description
numbers to add the area code. Note: The value must be larger than the minimum length.
Integer 15 1 to 15 dialplan.area_code.max_len = 13
Parameterdialplan.area_code.line_id Description Format Default Value
Configuration File <y0000000000xx>.cfg Specifies the line for this area code. Integer Blank (for all lines) Valid values are:
Range
1 to 6 (for T28P) 1 to 3 (for T26P/T20P) 105
1 to 2 (for T20P) Note: Multiple line IDs are separated by comma. Example dialplan.area_code.line_id = 1,2
Parameterdialplan.block_out.number.x Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Specifies the block out numbers. X ranges from 1 to 10. String Blank Not Applicable dialplan.block_out.number.1 = 0000
Parameterdialplan.block_out.line_id.x
Configuration File <y0000000000xx>.cfg Specifies the desired line to apply this block
Description
out rule. X ranges from 1 to 10.
Integer Blank (for all lines) Valid values are: 1 to 6 (for T28P)
Range
1 to 3 (for T26P/T20P) 1 to 2 (for T20P) Note: Multiple line IDs are separated by comma.
Example
dialplan.block_out.line_id.1 = 1,2,3
106
Appendix
Parametersecurity.user_password
Configuration File <y0000000000xx>.cfg Sets a new user password for the IP phone.
Description
Note: The IP phone supports numeric and alphabetic characters (- *.+ are included) only in passwords.
The value format is: username:password. user Numeric and alphabetic characters (- *.+ are included). security.user_password = user:password123
Parametersecurity.user_password Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Sets a new administrator password for the IP phone. The value format is: admin name:password. admin Numeric and alphabetic characters (- *.+ are included) security.user_password = admin:password000
Parameterphone_setting.lock Description Format Default Value Range
Configuration File <y0000000000xx>.cfg Specifies the type of phone lock. Integer 0 Valid values are: 0-Disabled 107
1-Menu Key 2-Function Keys 3-All Keys 4-Lock&Answer Example phone_setting.lock = 2
Parameterphone_setting.phone_lock.unlock_pin Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Changes the phone unlock password. Numeric characters only 123 0 to 15 characters phone_setting.phone_lock.unlock_pin = 123456
Parameterphone_setting.phone_lock.lock_time_out Description Format Default Value Range
Configuration File <y0000000000xx>.cfg Configures the interval (in seconds) to automatically lock the IP phone. Integer 0 0 (not automatically lock the phone) to 3600s phone_setting.phone_lock.lock_time_out =8
Example
Parameterphone_setting.emergency.number Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Configures the emergency numbers, each is separated by comma. String 112,911,110 0 to 100 characters phone_setting.emergency.number = 112,911,110,120
108
Appendix
Parameterlocal_time.time_zone Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Defines the time zone. Integer +8 -11 to +13 local_time.time_zone = +9
Parameterlocal_time.time_zone_name Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Defines the desired time zone name. Text China(Beijing) Refer to the SIP-T2xP User Guide for the Time Zone List. local_time.time_zone_name = Korea
Parameterlocal_time.ntp_server1 Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Sets the IP address or the domain name of the primary NTP server. IP address or qualified domain name cn.pool.ntp.org Not Applicable local_time.ntp_server1 = 192.168.0.5
Parameterlocal_time.ntp_server2 Description Format
Configuration File <y0000000000xx>.cfg Sets the IP address or the domain name of the secondary NTP server. IP address or qualified domain name 109
Default Value Range Example
cn.pool.ntp.org Not Applicable local_time.ntp_server2 = 192.168.0.5
Parameterlocal_time.interval Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Sets the interval (in seconds) for the IP phone to update time from the time server. Integer 1000 Not Applicable local_time.interval = 1200
DST
Parameterlocal_time.summer_time Description Format Default Value Configuration File <y0000000000xx>.cfg Enables or disables the use of daylight saving time. Integer 0 Valid values are: Range 0-Disabled 1-Enabled 2-Automatic Example local_time.summer_time = 2
Parameterlocal_time.dst_time_type Description Format Default Value Range
Configuration File <y0000000000xx>.cfg Configures the DST type when the DST is configured as Enabled. Integer Blank Valid values are: 0-By Date
110
Appendix
1-By Week Example local_time.dst_time_type = 1
Parameterlocal_time.start_time Description
Configuration File <y0000000000xx>.cfg Specifies the month, day and hour of day that DST starts. String The value formats are:
Format
MM/DD/HH (for By Date) Month/ Day of Week/ Day of Week Last in Month/ Hour of Day (for By Week)
1/1/0 Not Applicable local_time.start_time = 5/20/12
Parameterlocal_time.end_time Description
Configuration File <y0000000000xx>.cfg Specifies the month, day and hour of day that DST ends. String The value formats are:
Format
MM/DD/HH (for By Date) Month/ Day of Week/ Day of Week Last in Month/ Hour of Day (for by week)
12/31/23 Not Applicable local_time.end_time = 10/25/22
111
Parameterlocal_time.offset_time Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Sets the offset time (in minutes) of DST. Integer 60 -300 to +300 local_time.offset_time = 120
Parameterlocal_time.time_format Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Sets the time format. Integer 1 0-12 Hour 1-24 Hour local_time.time_format = 0
Parameterlocal_time.date_format Description Format Default Value
Configuration File <y0000000000xx>.cfg Sets the date format. Integer 0 Valid values are: 0-WWW MMM DD 1-DD-MMM-YY 2-YYYY-MM-DD 3-DD/MM/YYYY 4-MM/DD/YY 5-DD MMM YYYY 6-WWW DD MMM
Range
Example
local_time.date_format = 1
112
Appendix
Parameterlocal_time.dhcp_time
Configuration File <y0000000000xx>.cfg Specifies the IP phone whether to update time with the offset time obtained from the DHCP
Description
server. Note: This feature is only available to the time zone 0.
Boolean 0 0-Disabled 1-Enabled local_time.dhcp_time = 1
Parameterlocal_time.manual_time_enable Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Sets the time manually or obtains the time from NTP server. Boolean 0 0-NTP server 1-Manual local_time.manual_time_enable = 1
Parametergui_lang.url Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Specifies the access URL of the language pack. String Blank Not Applicable gui_lang.url = http://192.168.10.25/lang-Italian.txt
113
Parameterlang.wui Description Format Default Value
Configuration File <y0000000000xx>.cfg Specifies the language displaying on the web user interface. Text Not Applicable Valid values are: English Chinese_S Deutsch
Range
French Italian Portuguese Spanish Turkish
Example
lang.wui = French
Parameterlang.gui Description Format Default Value
Configuration File <y0000000000xx>.cfg Specifies the language displaying on the phone user interface. Text English Valid values are: English Chinese_S (not applicable to the T20P) Chinese_T (not applicable to the T20P) Deutsch
Range
French Italian Portuguese Polish Spanish Turkish
Example
lang.gui = Italian
114
Appendix
Parameteraccount.x.missed_calllog
Configuration File <MAC>.cfg Enables or disables the missed call log
Description
feature. X ranges from 1 to 6.
Boolean 1 0-Disabled 1-Enabled account.1.missed_calllog = 1
Parametercall_waiting.enable Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Enables or disables the call waiting feature. Boolean 1 0-Disabled 1-Enabled call_waiting.enable = 1
Parametercall_waiting.tone Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Enables or disables the IP phone to play the call waiting tone. Boolean 1 0-Disabled 1-Enabled call_waiting.tone = 1
115
Parameterauto_redial.enable
Configuration File <y0000000000xx>.cfg Enables or disables the IP phone to
Description
automatically redial the called number when it is busy.
Boolean 0 0-Disabled 1-Enabled auto_redial.enable = 1
Parameterauto_redial.interval Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Sets the interval (in seconds) for the IP phone to wait before redial. Integer 10 1 to 300 auto_redial.interval = 30
Parameterauto_redial.times Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Sets the redial times for the IP phone. Integer 10 1 to 300 auto_redial.times = 8
116
Appendix
Return Message When DND

Parameterfeatures.dnd_refuse_code Description Format Default Value Configuration File <y0000000000xx>.cfg Defines the type of the return message when DND. Integer 480 Valid values are: Range 404-No Found 480-Temporarily not available 486-Busy here Example features.dnd_refuse_code = 486
DND Key Mode

Parameterfeatures.dnd_mode Description Format Default Value Range Example Configuration File <y0000000000xx>.cfg Sets the DND key mode for the IP phone. Integer 0 0-Phone 1-Custom features.dnd_mode = 0
Parameterfeatures.play_hold_tone.enable Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Specifies whether to play call hold tone when there is a hold call on the phone. Boolean 1 0-Disabled 1-Enabled features.play_hold_tone.enable = 1
117
Parameterfeatures.play_hold_tone.delay Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Sets the interval (in seconds) for the IP phone to play call hold tone. Integer 30 Not Applicable features.play_hold_tone.delay = 60
Parametersip.rfc2543_hold Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Enables or disables the IP phone to use RFC 2543 when outgoing the hold signaling. Boolean 0 0-Disabled 1-Enabled sip.rfc2543_hold = 1
Call Forward Key Mode

Parameterfeatures.fwd_mode Description Format Default Value Range Example Configuration File <y0000000000xx>.cfg Sets the call forward key mode for the IP phone. Integer 0 0-Phone 1-Custom features.fwd_mode = 0
118
Appendix
Call Forward in Phone Mode Always Forward

Parameterforward.always.enable Description Format Default Value Range Example Configuration File < y0000000000xx >.cfg Enables or disables the always forward feature. Boolean 0 0-Disabled 1-Enabled forward.always.enable = 1
Parameterforward.always.target Description Format Default Value Range Example
Configuration File < y0000000000xx >.cfg Defines the destination number of the always forward. String Blank Not Applicable forward.always.target = 3601
Parameterforward.always.on_code Description Format Default Value Range Example
Configuration File < y0000000000xx >.cfg Sets the on code to inform the server to enable the always forward feature (optional). String Blank Not Applicable forward.always.on_code = *72
119
Parameterforward.always.off_code Description Format Default Value Range Example
Configuration File < y0000000000xx >.cfg Sets the off code to inform the server to disable the always forward feature (optional). String Blank Not Applicable forward.always.off_code = *73
Busy Forward
Parameterforward.busy.enable Description Format Default Value Range Example Configuration File < y0000000000xx >.cfg Enables or disables the busy forward feature. Boolean 0 0-Disabled 1-Enabled forward.busy.enable = 1
Parameterforward.busy.target Description Format Default Value Range Example
Configuration File < y0000000000xx >.cfg Defines the destination number of the busy forward. String Blank Not Applicable forward.busy.target = 3602
Parameterforward.busy.on_code Description Format
Configuration File < y0000000000xx >.cfg Sets the on code to inform the server to enable the busy forward feature (optional). String
120
Appendix
Blank Not Applicable forward.busy.on_code = *74
Parameterforward.busy.off_code Description Format Default Value Range Example
Configuration File < y0000000000xx >.cfg Sets the off code to inform the server to disable the busy forward feature (optional). String Blank Not Applicable forward.busy.off_code = *75
No Answer Forward
Parameterforward.no_answer.enable Description Format Default Value Range Example Configuration File < y0000000000xx >.cfg Enables or disables the no answer forward feature. Boolean 0 0-Disabled 1-Enabled forward.no_answer.enable = 1
Parameterforward.no_answer.target Description Format Default Value Range Example
Configuration File < y0000000000xx >.cfg Defines the destination number of the no answer forward. String Blank Not Applicable forward.no_answer.target = 3603
121
Parameterforward.no_answer.timeout
Configuration File < y0000000000xx >.cfg Defines a period of ring time to wait before
Description
forwarding the ring call. The interval of the ring time is n*6 (0n20), the valid values ranges from 0 to 20.
Integer 2 0 to 20 forward.no_answer.timeout = 5
Parameterforward.no_answer.on_code Description Format Default Value Range Example
Configuration File < y0000000000xx >.cfg Sets the on code to inform the server to enable the no answer forward feature (optional). String Blank Not Applicable forward.no_answer.on_code = *76
Parameterforward.no_answer.off_code
Configuration File < y0000000000xx >.cfg Sets the off code to inform the server to
Description
disable the no answer forward feature (optional).
String Blank Not Applicable forward.no_answer.off_code = *77
122
Appendix
Call Forward in Custom Mode Always Forward

Parameteraccount.x.always_fwd.enable Configuration File <MAC>.cfg Enables or disables the always forward Description feature. X ranges from 1 to 6. Format Default Value Range Example Boolean 0 0-Disabled 1-Enabled account.1.always_fwd.enable = 1
Parameteraccount.x.always_fwd.target
Configuration File <MAC>.cfg Defines the destination number of the always
Description
forward. X ranges from 1 to 6.
String Blank Not Applicable account.1.always_fwd.target = 3601
Parameteraccount.x.always_fwd.on_code
Configuration File <MAC>.cfg Sets the on code to inform the server to enable
Description
the always forward feature (optional). X ranges from 1 to 6.
String Blank Not Applicable account.1.always_fwd.on_code = *72
123
Parameteraccount.x.busy_fwd.off_code
Configuration File <MAC>.cfg Sets the off code to inform the server to
Description
disable the always forward feature (optional). X ranges from 1 to 6.
String Blank Not Applicable account.1.busy_fwd.off_code = *73
Busy Forward
Parameteraccount.x.busy_fwd.enable Description Format Default Value Range Example Configuration File <MAC>.cfg Enables or disables the busy forward feature. X ranges from 1 to 6. Boolean 0 0-Disabled 1-Enabled account.1.busy_fwd.enable = 1
Parameteraccount.x.busy_fwd.target
Configuration File <MAC>.cfg Defines the destination number of the busy
Description
forward. X ranges from 1 to 6.
String Blank Not Applicable account.1.busy_fwd.target = 3602
Parameteraccount.x.busy_fwd.on_code Description 124
Appendix
the busy forward feature (optional). X ranges from 1 to 6 Format Default Value Range Example String Blank Not Applicable account.1.busy_fwd.on_code = *74
Parameteraccount.x.busy_fwd.off_code
Description
disable the busy forward feature (optional). X ranges from 1 to 6
String Blank Not Applicable account.1.busy_fwd.off_code = *75
No Answer Forward
Parameteraccount.x.timeout_fwd.enable Configuration File <MAC>.cfg Enables or disables the no answer forward Description feature. X ranges from 1 to 6. Format Default Value Range Example Boolean 0 0-Disabled 1-Enabled account.1.timeout_fwd.enable = 1
Parameteraccount.x.timeout_fwd.target
Configuration File <MAC>.cfg Defines the destination number of the no
Description
answer forward. X ranges from 1 to 6.
125
String Blank Not Applicable account.1.timeout_fwd.target = 3603
Parameteraccount.x.timeout_fwd.timeout
Configuration File <MAC>.cfg Defines a period of ring time to wait before forwarding the ring call.
Description
The interval of the ring time is n*6 (0n20), the valid values ranges from 0 to 20. X ranges from 1 to 6.
Integer 2 0 to 20 account.1.timeout_fwd.timeout = 5
Parameteraccount.x.timeout_fwd.on_code
Description
the no answer forward feature (optional). X ranges from 1 to 6.
String Blank Not Applicable account.1.timeout_fwd.on_code = *76
Parameteraccount.x.timeout_fwd.off_code
Description
disable the no answer forward feature (optional). X ranges from 1 to 6.
Format 126
String
Appendix
Blank Not Applicable account.1.timeout_fwd.off_code = *77
Parametertransfer.blind_tran_on_hook_enable
Configuration File <y0000000000xx>.cfg Enables or disables the IP phone to
Description
complete the blind transfer through on-hook.
Boolean 1 0-Disabled 1-Enabled transfer.blind_tran_on_hook_enable = 1
Parametertransfer.on_hook_trans_enable Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Enables or disables the IP phone to complete the attended transfer through on-hook. Boolean 1 0-Disabled 1-Enabled transfer.on_hook_trans_enable = 1
Parametertransfer.semi_attend_tran_enable Description Format Default Value Range
Configuration File <y0000000000xx>.cfg Specifies whether to display the missed call prompt on the destination party s phone. Boolean 1 0-Disabled 1-Enabled 127
Example
transfer.semi_attend_tran_enable = 1
Parameteraccount.x.conf_type Description Format Default Value
Configuration File <MAC>.cfg Defines the conference type. X ranges from 1 to 6. Integer 0 Valid values are:
Range
0-Local 2-Network Conference
Example
account.1.conf_type = 2
Parameteraccount.x.conf_uri
Configuration File <MAC>.cfg Defines the conference URI.
Description
This parameter is available only when the account.x.conf_type parameter is set to 2. X ranges from 1 to 6.
String Blank Not Applicable account.1.conf_uri = conference@domain.com
Parametertransfer.tran_others_after_conf_enable Description Format
Configuration File <y0000000000xx>.cfg Enables or disables the Transfer on Conference Hang Up feature. Boolean
128
Appendix
Default Value Range
0 0-Disabled 1-Enabled transfer.tran_others_after_conf_enable =1
Example
Phone Basis
Parameterfeatures.pickup.direct_pickup_enable Description Format Default Value Range Configuration File <y0000000000xx>.cfg Configures the IP phone to display the DPickup soft key in the dialing interface. Boolean 0 0-Disabled 1-Enabled features.pickup.direct_pickup_enable = 1
Example
Parameterfeatures.pickup.direct_pickup_code Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Configures the directed pickup code on a phone basis. String Blank Not Applicable features.pickup.direct_pickup_code = *97
Per-account Basis
Parameteraccount.x.direct_pickup_code Configuration File <y0000000000xx>.cfg Configures the directed pickup code on a Description per-account basis. X ranges from 1 to 6.
129
String Blank Not Applicable account.1.direct_pickup_code = *68
Phone Basis
Parameterfeatures.pickup.group_pickup_enable Description Format Default Value Range Configuration File <y0000000000xx>.cfg Configures the IP phone to display the GPickup soft key in the dialing interface. Boolean 0 0-Disabled 1-Enabled features.pickup.group_pickup_enable = 1
Example
Parameterfeatures.pickup.group_pickup_code Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Configures the group pickup code on a phone basis. String Blank Not Applicable features.pickup.group_pickup_code = *98
Per-account Basis
Parameteraccount.x.group_pickup_code Configuration File <y0000000000xx>.cfg Configures the group pickup code on a Description per-account basis. X ranges from 1 to 6. Format 130 String
Appendix
Blank Not Applicable account.1.group_pickup_code = *69
Parameteraccount.x.dialoginfo_callpickup Description Format Default Value Range Example
Configuration File <MAC>.cfg Configures the BLF call park on the IP phone. X ranges from 1 to 6. Boolean 0 0-Disabled 1-Enabled account.1.dialoginfo_callpickup = 1
Parameterfeatures.hotline_number Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Specifies the hotline number. String Blank Not Applicable features.hotline_number = 1009
Parameterfeatures.hotline_delay
Configuration File <y0000000000xx>.cfg Specifies the delay time (in seconds) for the IP
Description
phone to wait before dialing the hotline number.
Format Default Value Range
Integer 4 0 to 180 131
Example
features.hotline_delay = 6
Parameternetwork.web_server_type
Configuration File <y0000000000xx>.cfg Specifies the access type of the web server.
Description
Integer 1 Valid values are: 0-Disabled
Range
1-HTTP & HTTPS 2-HTTP Only 3-HTTPS Only
Example
network.web_server_type = 2
Parameternetwork.port.http
Configuration File <y0000000000xx>.cfg Specifies the http port of the web server.
Description
Integer 80 1 to 65535 network.port.http = 90
Parameternetwork.port.https
Configuration File <y0000000000xx>.cfg Specifies the https port of the web server.
Description
Format
Integer
132
Appendix
443 1 to 65535 network.port.https = 100
Parameteraccount.x.cid_source
Configuration File <MAC>.cfg Specifies the precedence of presenting the SIP header. X ranges from 1 to 6. 0-FROM (Derives the name and number of the caller from the From header). 1-PAI (Derives the name and number of the caller from the PAI header. If the server does not send the PAI header, displays anonymity on the callees phone). 2-PAI-FROM (Derives the name and number of the caller from the PAI header preferentially. If the server does not send the PAI header, derives from the From header). 3-RPID-PAI-FROM 4-PAI-RPID-FROM 5-RPID-FROM
Description
Integer 0 0 to 5 account.1.cid_source = 2
Parameteraccount.x.cp_source
Configuration File <MAC>.cfg Specifies the precedence of presenting the SIP header.
Description
X ranges from 1 to 6. 0-RPID-FROM (Derives the name and number of the callee from the RPID header 133
preferentially. If the server does not send the RPID header, derives from the From header). 1-Dialed Digits (Preferentially displays the dialed digits on the caller s phone). 2-RFC 4916 (Derives the name and number of the callee from From header in the Update message). Format Default Value Range Example Integer 0 0 to 2 account.1.cp_source = 2
Parameteraccount.x.dtmf.type Description Format Default Value
Configuration File <MAC>.cfg Specifies the method of transmitting DTMF. X ranges from 1 to 6. Integer 1 Valid values are: 0-INBAND 1-RFC 2833
Range
2-SIP INFO 3-AUTO+SIP INFO: Negotiates with the other end to use INBAND or RFC 2833, if there is no negotiation, using SIP INFO by default.
Example
account.1.dtmf.type = 2
Parameteraccount.x.dtmf.dtmf_payload Description Format Default Value
Configuration File <MAC>.cfg Sets the payload type for the RFC 2833. X ranges from 1 to 6. Integer 101
134
Appendix
Range Example
96 to 255 account.1.dtmf.dtmf_payload = 101
Parameteraccount.x.dtmf.info_type
Configuration File <MAC>.cfg Configures the DTMF info type when using SIP
Description
INFO. X ranges from 1 to 6.
Integer 0 Valid values are: 0-Disabled
Range
1-DTMF-Relay 2-DTMF 3-Telephone-Event
Example
account.1.dtmf.info_type = 3
Parameterfeatures.dtmf.hide Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Enables or disables the IP phone to suppress the display of DTMF digits. Boolean 0 0-Disabled 1-Enabled features.dtmf.hide = 1
Parameterfeatures.dtmf.hide_delay
Configuration File <y0000000000xx>.cfg Enables or disables the IP phone to display the
Description
DTMF digits for a short period before displaying as asterisks.
Format
Boolean
135
0 0-Disabled 1-Enabled features.dtmf.hide_delay = 1
Parameterdistinctive_ring_tones.alert_info.x.text
Configuration File <y0000000000xx>.cfg Specifies the texts to map the keywords
Description
contained in the SIP header. X ranges from 1 to 10.
Text Blank Not Applicable distinctive_ring_tones.alert_info.1.text = family
Parameterdistinctive_ring_tones.alert_info.x.ringer
Configuration File <y0000000000xx>.cfg Specifies the desired ring tones for each text.
Description
The value ranges from 1 to 8, the digit stands for the appropriate ring tone. X ranges from 1 to 10.
Integer 1 Valid values are: 1-Ring1.wav 2-Ring2.wav 3-Ring3.wav
Range
4-Ring4.wav 5-Ring5.wav 6-Ring6.wav 7-Ring7.wav 8-Ring8.wav
136
Appendix
Example
distinctive_ring_tones.alert_info.1.ringer =2
Parametervoice.tone.country Description Format Default Value
Configuration File <y0000000000xx>.cfg Configures the tone type for the phone. Text Custom Valid values are:

Custom Australia Austria Brazil Belgium China Czech Denmark Finland France Germany Great Britain Greece Hungary Lithuania India Italy Japan Mexico New Zealand Netherlands Norway Portugal Spain Switzerland Sweden Russia United States Chile Czech ETSI 137
Range
Example
voice.tone.country = Austria
Parametervoice.tone.dial voice.tone.ring voice.tone.busy voice.tone.congestion voice.tone.callwaiting voice.tone.dialrecall voice.tone.record voice.tone.info voice.tone.stutter voice.tone.message voice.tone.autoanswer
Configuration File <y0000000000xx>.cfg
Customizes the tone for each condition. Description This parameter is only applicable when the tone type is configured to Custom. The value format is F/D. F: the frequency of the tone (ranges from 200 to 7000 Hz). When 0 is used to define the frequency, it means a pause between tones. A tone can be composited at most four different Format frequencies (value format: F1+F2+F3+F4). D: the time duration (in milliseconds, ranges from 0 to 30000ms) of ringing the tone. You can configure at most eight different tones for one condition, each tone separated by comma (e.g. 250/200, 0/1000, 200+300/500, 600+700+800+1000/2000). Default Value Range Example Blank Not Applicable voice.tone.dial = 800+200/1000, 0/100, 500/1200, 500+600+950+1500/5000
Parameterfeatures.remote_phonebook.enable Description 138
Configuration File <y0000000000xx>.cfg Enables or disables the IP phone to query
Appendix
the contact names from the remote phonebook when receiving incoming calls. Format Default Value Range Example Boolean 0 0-Disabled 1-Enabled features.remote_phonebook.enable = 1
Parameterfeatures.remote_phonebook.flash_time
Configuration File <y0000000000xx>.cfg Sets the interval (in seconds) for the IP
Description
phone to update the information of the remote phonebook.
Integer 3600 Not Applicable features.remote_phonebook.flash_time = 1800
Parameterldap.name_filter Description Format Default Value Range
Configuration File <y0000000000xx>.cfg Sets the search criteria for name lookups. String Blank Not Applicable ldap.name_filter = (|(cn=%)(sn=%))
Example
(Here, the result of your search will be all LDAP entries which have the common name or the surname field starting with the entered prefix).
139
Parameterldap.number_filter Description Format Default Value Range
Configuration File <y0000000000xx>.cfg Sets the search criteria for number lookups. String Blank Not Applicable ldap.number_filter = (|(telephoneNumber=%)(mobile=%))
Example
(Here, the result of your search will be all LDAP entries which have the telephone number or the mobile phone number field starting with the entered prefix).
Parameterldap.host Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Specifies the IP address of the LDAP server. IP address 0.0.0.0 Not Applicable ldap.host = 192.168.1.20
Parameterldap.port Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Specifies the port of the LDAP server. Integer 389 Not Applicable ldap.port = 390
Parameterldap.base Description
Configuration File <y0000000000xx>.cfg Specifies the LDAP search base which is the location in the directory from which the LDAP
140
Appendix
search is requested to begin. Format Default Value Range Example String Blank Not Applicable ldap.base = dc=yealink,dc=cn
Parameterldap.user Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Sets the login username of the LDAP server. String Blank Not Applicable ldap.user = cn=manager,dc=yealink,dc=cn
Parameterldap.password Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Sets the login password of the LDAP server. String Blank Not Applicable ldap.password = secret
Parameterldap.max_hits Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Specifies the maximum of the displayed search results. Integer 50 1 to 32000 ldap.max_hits = 60
141
Parameterldap.name_attr
Configuration File <y0000000000xx>.cfg Specifies the name attributes of each record
Description
which are to be returned in the LDAP search results.
String Blank Not Applicable ldap.name_attr = cn sn
Parameterldap.numb_attr
Configuration File <y0000000000xx>.cfg Specifies the number attributes of each
Description
record which are to be returned in the LDAP search results.
String Blank Not Applicable ldap.numb_attr = telephoneNumber
Parameterldap.display_name
Configuration File <y0000000000xx>.cfg Specifies the name format of each returned
Description
search result which is to be displayed on the IP phone.
String Blank Not Applicable ldap.display_name = %cn
Parameterldap.version Description
Configuration File <y0000000000xx>.cfg Specifies the protocol version of LDAP server.
142
Appendix
Integer 3 2 or 3 ldap.version = 3
Parameterldap.search_delay Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Sets a delay time (in milliseconds) for the IP phone to display the search results. Integer 0 0 to 2000 ldap.search_delay = 20
Parameterldap.call_in_lookup
Configuration File <y0000000000xx>.cfg Configures the IP phone to query the contact
Description
name from the LDAP server when receiving an incoming call.
Boolean 0 0-Disabled 1-Enabled ldap.call_in_lookup = 1
Parameterldap.ldap_sort Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Configures the IP phone to sort the search results in alphabetical order. Boolean 0 0-Disabled 1-Enabled ldap.ldap_sort = 1
143
Parameterldap.dial_lookup
Configuration File <y0000000000xx>.cfg Configures the IP phone to query the LDAP
Description
server when in the pre-dialing or the dialing state.
Boolean 0 0-Disabled 1-Enabled ldap.dial_lookup = 1
Parameteraccount.x.blf.blf_list_uri
Configuration File <MAC>.cfg Specifies the URI that the IP phone uses to
Description
access the BLF list configured on the BroadSoft server. X ranges from 1 to 6.
String Blank Not Applicable account.1.blf.blf_list_uri = blf_3601
Parameteraccount.x.blf_list_code
Configuration File <MAC>.cfg Enters the feature access code to pick up the
Description
ringing call of the monitored user. X ranges from 1 to 6.
String Blank Not Applicable account.1.blf_list_code = *65
144
Appendix
Parameteraccount.x.blf_list_barge_in_code
Configuration File <MAC>.cfg Specifies the feature access code to barge in
Description
an active call of the monitored user. X ranges from 1 to 6.
String Blank Not Applicable account.1.blf_list_barge_in_code = *33
Parameterfeatures.pickup.blf_visual_enable
Configuration File <y0000000000xx>.cfg Enables or disables the phone to display a
Description
visual prompt when the monitored user receiving an incoming call.
Boolean 0 0-Disabled 1-Enabled features.pickup.blf_visual_enable = 1
Parameterfeatures.pickup.blf_audio_enable
Configuration File <y0000000000xx>.cfg Configures the IP phone to play an alert tone
Description
when the monitored user receiving an incoming call.
Boolean 0 0-Disabled 1-Enabled features.pickup.blf_audio_enable = 1
145
Use the following parameters to register the shared line on the IP phone. Parameteraccount.x.enable Description Format Default Value Range Example Configuration File <MAC>.cfg Enables or disables the account. X ranges from 1 to 6. Boolean 0 0-Disabled 1-Enabled account.1.enable = 1
Parameteraccount.x.label
Configuration File <MAC>.cfg Configures the label of the account to be
Description
displayed on the IP phone. X ranges from 1 to 6.
String Blank Not Applicable account.1.label = sca
Parameteraccount.x.display_name Description Format Default Value Range Example
Configuration File <MAC>.cfg Configures the display name of the account. X ranges from 1 to 6. String Blank Not Applicable account.1.display_name = 2413333601
146
Appendix
Parameteraccount.x.auth_name
Configuration File <MAC>.cfg Configures the register name of the account. X ranges from 1 to 6.
Description
Note: If configuring the secondary line on the phone, enter the register name of the primary line for this parameter.
String Blank Not Applicable account.1.auth_name = 2413333601
Parameteraccount.x.password Description Format Default Value Range Example
Configuration File <MAC>.cfg Configures the password of the account. X ranges from 1 to 6. String Blank Not Applicable account.1.password = userpassword
Parameteraccount.x.user_name Description Format Default Value Range Example
Configuration File <MAC>.cfg Configures the user name of the account. X ranges from 1 to 6. String Blank Not Applicable account.1.user_name = 2413333601
Parameteraccount.x.sip_server_host Description
Configuration File <MAC>.cfg Configures the SIP server address. 147
X ranges from 1 to 6. Format Default Value Range Example IP Address or Domain Name Blank Not Applicable account.1.sip_server_host = server@domain name.net
Parameteraccount.x.sip_server_port Description Format Default Value Range Example
Configuration File <MAC>.cfg Configures the SIP server port. X ranges from 1 to 6. Integer 5060 Not Applicable account.1.sip_server_port = 5060
Parameteraccount.x.outbound_proxy_enable
Configuration File <MAC>.cfg Enables or disables the outbound proxy
Description
server. X ranges from 1 to 6.
Boolean 0 0-Disabled 1-Enabled account.1.outbound_proxy_enable = 1
Parameteraccount.x.outbound_host
Configuration File <MAC>.cfg Configures the address of the outbound proxy
Description
server. X ranges from 1 to 6.
Format
IP Address
148
Appendix
Blank Not Applicable account.1.outbound_host = 199.19.195.10
Parameteraccount.x.outbound_port Description Format Default Value Range Example
Configuration File <MAC>.cfg Configures the outbound proxy server port. X ranges from 1 to 6. Integer 5060 Not Applicable account.1.outbound_port = 5060
Parameteraccount.x.shared_line Description Format Default Value
Configuration File <MAC>.cfg Configures the line type. X ranges from 1 to 6. Integer 0 Valid values are:
Range
0-Disabled 1-Broadsoft SCA 2-BLA
Example
account.1.shared_line = 1
Parameterbw.feature_key_sync Description Format Default Value
Configuration File <y0000000000xx>.cfg Enables or disables the as-feature-event feature. Boolean 0
149
Range Example
0-Disabled 1-Enabled bw.feature_key_sync = 1
Parameteraction_url.setup_completed action_url.log_on action_url.log_off action_url.register_failed action_url.off_hook action_url.on_hook action_url.incoming_call action_url.outgoing_call action_url.call_established action_url.dnd_on action_url.dnd_off action_url.always_fwd_on action_url.always_fwd_off action_url.busy_fwd_on action_url.busy_fwd_off action_url.no_answer_fwd_on action_url.no_answer_fwd_off action_url.transfer_call action_url.blind_transfer_call action_url.attended_transfer_call action_url.hold action_url.unhold action_url.mute action_url.unmute action_url.missed_call action_url.call_terminated action_url.busy_to_idle action_url.idle_to_busy action_url.ip_change action_url.forward_incoming_call 150
Appendix
action_url.reject_incoming_call action_url.answer_new_incoming_call action_url.transfer_finished action_url.transfer_failed Specifies the URL for the predefined event. The value format is: http://IP address of server/help.xml? variable name=variable value Valid values are:

$mac $ip $model $firmware $active_url $active_user $active_host $local $remote $display_local $display_remote $call_id
Description
URL Not Applicable Not Applicable action_url.mute = http://192.168.0.20/help.xml?model=$model
Parameterfeatures.action_uri_limit_ip
Configuration File <y0000000000xx>.cfg Specifies the address(es) (multiple IP
Description
addresses are separated by comma) or enters any (stands for any IP address) from which Action URI will be accepted.
IP Address Blank IP address or any
151
Example
features.action_uri_limit_ip = any
Parameteraccount.x.transport
Configuration File <MAC>.cfg Enables or disables the server redundancy
Description
feature on the IP phone. X ranges from 1 to 6.
Integer 0 (UDP) Valid values are: 0-UDP
Range
1-TCP 2-TLS 3-DNS SRV
Example
account.1.transport = 3
Parameteraccount.x.nat.nat_traversal
Configuration File <MAC>.cfg Enables or disables the NAT traversal on the
Description
phone. X ranges from 1 to 6.
Boolean 0 0-Disabled 1-Enabled account.1.nat.nat_traversal = 1
Parameteraccount.x.nat.stun_server Description
Configuration File <MAC>.cfg Specifies the IP address or the domain name of the STUN server.
152
Appendix
X ranges from 1 to 6. Format Default Value Range Example IP Address or Domain Name Blank Not Applicable account.1.nat.stun_server = 192.168.1.20
Parameteraccount.x.nat.stun_port Description Format Default Value Range Example
Configuration File <MAC>.cfg Specifies the port of the STUN server. X ranges from 1 to 6. Integer 3478 Not Applicable account.1.nat.stun_port = 3479
Parameternetwork.snmp.enable
Configuration File <y0000000000xx>.cfg Enables or disables the SNMP feature on the IP
Description
phone. Note: If you change this parameter, the phone will reboot to make the change take effect.
Boolean 0 0-Disabled 1-Enabled network.snmp.enable = 1
Parameternetwork.snmp.port
Configuration File <y0000000000xx>.cfg Specifies the port used for SNMP
Description
communication. Note: If you change this parameter, the phone
153
will reboot to make the change take effect. Format Default Value Range Example Integer Blank 0 to 65535 network.snmp.port = 1008
Parameternetwork.snmp.trust_ip
Configuration File <y0000000000xx>.cfg Specifies the addresses (at most three addresses, each separated by space) from
Description
which SNMP requests will be accepted. Note: If you change this parameter, the phone will reboot to make the change take effect.
IP Address Blank Not Applicable network.snmp.trust_ip = 192.168.1.50 192.168.1.51
Parameternetwork.802_1x.mode
Configuration File <y0000000000xx>.cfg Enables or disables the IP phone to use the
Description
802.1X authentication. Note: If you change this parameter, the phone will reboot to make the change take effect.
Integer 0 0-Disabled
Range
1-EAP-MD5 2-EAP-TLS 3-PEAP-MSCHAPV2
Example
network.802_1x.mode = 1
154
Appendix
Parameternetwork.802_1x.identity
Configuration File <y0000000000xx>.cfg Enters the identity used for the MD5
Description
authentication of the 802.1X. Note: If you change this parameter, the phone will reboot to make the change take effect.
String Blank Not Applicable network.802_1x.identity = admin
Parameternetwork.802_1x.md5_password
Configuration File <y0000000000xx>.cfg Enters the password used for the MD5 authentication of 802.1X.
Description
It is only applicable to EAP-MD5 and PEAP-MSCHAPV2 protocols. Note: If you change this parameter, the phone will reboot to make the change take effect.
String Blank Not Applicable network.802_1x.md5_password = admin123
Parameternetwork.802_1x.root_cert_url
Configuration File <y0000000000xx>.cfg Specify the access URL of the root certificate used for authentication.
Description
It is only applicable to EAP-TLS and PEAP-MSCHAPV2 protocols. Note: If you change this parameter, the phone will reboot to make the change take effect.
String Blank
155
Range Example
Not Applicable network.802_1x.root_cert_url = http://192.168.1.10/ca.pem
Parameternetwork.802_1x.client_cert_url
Configuration File <y0000000000xx>.cfg Specify the access URL of the client certificate used for authentication.
Description
It is only applicable to the EAP-TLS protocol. Note: If you change this parameter, the phone will reboot to make the change take effect.
String Blank Not Applicable network.802_1x.client_cert_url = http://192.168.1.10/ client.pem
Parametermanagementserver.enable
Configuration File <y0000000000xx>.cfg Configures the TR-069 on the IP phone.
Description
Boolean 0 0-Disabled 1-Enabled managementserver.enable = 1
Parametermanagementserver.username Description 156
Configuration File <y0000000000xx>.cfg Enters the username to authenticate with the
Appendix
ACS. This string is set to the empty string if no authentication is required. Note: If you change this parameter, the phone will reboot to make the change take effect. Format Default Value Range Example String Blank Not Applicable managementserver.username = user
Parametermanagementserver.password
Configuration File <y0000000000xx>.cfg Enters the password to authenticate with the ACS. This string is set to the empty string if no
Description
authentication is required. Note: If you change this parameter, the phone will reboot to make the change take effect.
String Blank Not Applicable managementserver.password = pwd123
Parametermanagementserver.url
Configuration File <y0000000000xx>.cfg Specifies the URL of the ACS.
Description
String Blank Not Applicable managementserver.url = pwd123
Parametermanagementserver.connectio n_request_username
157
Sets the username for the phone to authenticate Description the incoming connection requests. Note: If you change this parameter, the phone will reboot to make the change take effect. Format Default Value Range Example String Blank Not Applicable managementserver.connection_request_userna me = acsuser
Parametermanagementserver.connection _request_password
Sets the password for the phone to authenticate the incoming connection Description requests. Note: If you change this parameter, the phone will reboot to make the change take effect. Format Default Value Range Example String Blank Not Applicable managementserver.connection_request_pass word = acspwd
Parametermanagementserver.periodic_in form_enable
Enables or disables the IP phone to report its Description configuration information to the ACS. Note: If you change this parameter, the phone will reboot to make the change take effect. Format Default Value Range Boolean 0 0-Disabled 1-Enabled
158
Appendix
Example
managementserver.periodic_inform_enable = 1
Parametermanagementserver.periodic_in form_interval
Sets the interval (in seconds) to report its Description configuration information to the ACS. Note: If you change this parameter, the phone will reboot to make the change take effect. Format Default Value Range Example Integer 60 Not Applicable managementserver.periodic_inform_interval = 120
Parameteraccount.x.transport
Configuration File <MAC>.cfg Enables or disables the TLS feature on the
Description
phone. X ranges from 1 to 6.
Integer 0 (UDP) Valid values are: 0-UDP
Range
1-TCP 2-TLS 3-DNS SRV
Example
account.1.transport = 2
Parameter-
Configuration File
159
security.trust_certificates Description Format Default Value Range Example
<y0000000000xx>.cfg Enables or disables the IP phone to authenticate the connected server. Boolean 1 0-Disabled 1-Enabled security.trust_certificates = 1
Parametertrusted_certificates.url Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Specifies the access URL of the trusted certificate. String Blank Not Applicable trusted_certificates.url = http://192.168.1.20/tc.crt
Parameterserver_certificates.url Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Specifies the access URL of the server certificate. String Blank Not Applicable server_certificates.url = http://192.168.1.20/ca.crt
Parameterauto_provision.aes_key_16.com 160
Appendix
Description
Changes the AES key which is used to encrypt or decrypt the <y0000000000xx >.cfg file. String () ><| "& cannot be included. Blank 16 characters auto_provision.aes_key_16.com = 0123456789abcdef
Parameterauto_provision.aes_key_16.mac Description
Configuration File <y0000000000xx>.cfg Changes the AES key which is used to encrypt or decrypt the <MAC >.cfg file. String () ><| "& cannot be included. Blank 16 characters auto_provision.aes_key_16.mac = 0123456789abmins
Parameterauto_provision.mode Description Format Default Value
Configuration File <y0000000000xx>.cfg Specifies the way of phone checking new configuration files. Integer 0 Valid values are: 0-Disabled 1-Power on (when the phone boots)
Range
4-Repeatedly (at a fixed interval) 5-Weekly (at the specified time) 6-Power on + Repeatedly 7-Power on + Weekly
161
Example
auto_provision.mode = 1
Parameterauto_provision.schedule.periodic_minute
Configuration File < y0000000000xx >.cfg Sets the interval (in minutes) for the phone to check new configuration files.
Description
This parameter is only applicable to the Repeatedly and Power on + Repeatedly modes.
Integer 1 1 to 43200 auto_provision.schedule.periodic_minute = 1000
Parameterauto_provision.schedule.time_from
Configuration File < y0000000000xx >.cfg Sets the start time of day in 24-hour period for the phone to check new configuration files. This parameter is only applicable to the Weekly and Power on + Weekly modes.
Description
00:00 00:00 00:00 to 23:59 auto_provision.schedule.time_from = 01:30
Parameterauto_provision.schedule.time_to
Configuration File < y0000000000xx >.cfg Sets the end time of day in 24-hour period for
Description
the phone to check new configuration files. This parameter is only applicable to the Weekly and Power on + Weekly modes.
Format
00:00
162
Appendix
00:00 00:00 to 23:59 auto_provision.schedule.time_to = 21:30
Parameterauto_provision.schedule.dayofweek Description Format Default Value
Configuration File < y0000000000xx >.cfg Defines the desired day(s) of a week for the phone to check new configuration. Integer 0123456 Valid values are: 0-Sunday 1-Monday 2-Tuesday 3-Wednesday 4-Thursday 5-Friday 6-Saturday
Range
Example
auto_provision.schedule.time_to = 123
Parameterfirmware.url Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Specifies the access URL of the firmware. String Blank Not Applicable firmware.url = http://192.168.1.20/2.70.0.50.rom
Parameterdialplan_replace_rule.url
163
Description Format Default Value Range Example
Specifies the access URL of the replace rule template. String Blank Not Applicable dialplan_replace_rule.url = http://192.168.10.25/dialplan.xml
Parameterdialplan_dialnow.url Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Specifies the access URL of the dial-now template. String Blank Not Applicable dialplan_dialnow.url = http://192.168.10.25/dialnow.xml
Parameterlocal_contact.data.url Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Specifies the access URL of the local contact file. String Blank Not Applicable local_contact.data.url = http://192.168.10.25/contactData1.xml
164
Appendix
Parameterremote_phonebook.data.x.url
Configuration File <y0000000000xx>.cfg Specifies the access URL of the remote XML
Description
phonebook. X ranges from 1 to 5.
String Blank Not Applicable remote_phonebook.data.1.url = http://192.168.1.20/phonebook.xml
Parametersyslog.server
Configuration File <y0000000000xx>.cfg Specifies the IP address of the syslog server
Description
where to export the log files. Note: If you change this parameter, the phone will reboot to make the change take effect.
IP Address Blank Not Applicable syslog.server = 192.168.1.50
165
Parametersyslog.log_level
Configuration File <y0000000000xx>.cfg Specifies the severity level of the logs to be
Description
reported to a log file. Note: If you change this parameter, the phone will reboot to make the change take effect.
Integer 3 0 to 6 syslog.log_level = 2
Parameterwatch_dog.enable Description Format Default Value Range Example
Configuration File <y0000000000xx>.cfg Enables or disables the Watch Dog feature. Boolean 1 0-Disabled 1-Enabled watch_dog.enable = 1
This section provides the DSS key parameters you can configure on the IP phone. The DSS key is consist of the memory key and line key. The following table lists the number of DSS keys you can configure for each phone model: Phone Model T28P T26P T22P T20P Line Key 6 3 3 2 Memory Key 10 10 / /
Various key features can be assigned to the DSS key. The SIP-T28P/T26P IP phones support to be assigned features to the memory keys and line keys. The SIP-T22P/T20P IP
166
Appendix
phones only support to be assigned features to the line keys. The configurations of the line key are basically the same as the memory key. The parameters of the DSS key are detailed in the following (take the memory key as an example): Parametermemorykey.x.line Configuration File <y0000000000xx>.cfg Specifies the desired line to apply the key feature. X ranges from 1 to 10. The value 0 stands for Auto (the first available line). 0 stands for Line1 when assigning the following features:

BLF BLF List Call Park Call Pickup ACD Voice Mail Custom Button
When assigning the following features, you dont need to configure this parameter:
DTMF Prefix Local Group XML Group XML Browser LDAP Broadsoft Group Conference Forward Hold DND Redial Call Return SMS Record URL Record Multicast Paging Group Listening Public HoldPrivate Hold Hot Desking Zero Touch 167
Description
URL (not applicable to T20P) Keypad Lock
Integer 0 (Auto) Valid values are:
Range
0 to 6 (for T28P) 0 to 3 (for T26P/T22P) 0 to 2 (for T20P)
Example
memorykey.1.line = 2
Parametermemorykey.x.value Description Format Default Value Range
Configuration File <y0000000000xx>.cfg Specifies the value for some key features. X ranges from 1 to 10. String Blank Not Applicable When assigning the Speed Dial to the memory
Example
key, this parameter is used to specify the number you want to dial out. memorykey.1.value = 1001
Parametermemorykey.x.pickup_value
Configuration File <y0000000000xx>.cfg Specifies the pickup code for the BLF feature.
Description
This parameter only applies to the BLF feature. X ranges from 1 to 10.
String Blank Not Applicable memorykey.1.pickup_value = *88
168
Appendix
Parametermemorykey.x.type
Configuration File <y0000000000xx>.cfg Specifies the key feature for the memory key. X ranges from 1 to 10. Valid types are:

N/A (default for memory key) Conference Forward Transfer Hold DND Redial Call Return SMS Call Pickup Call Park DTMF Voicemail Speed Dial Intercom Line (default for line key) BLF URL (not applicable to T20P) Group Listening Public Hold Private Hold XML Group Group Pickup Multicast Paging Record Hot Desking (not applicable to T20P) XML Browser URL Record LDAP (not applicable to T20P) BLF List Prefix Zero Touch ACD Local Group Broadsoft Group Keypad Lock Custom Button (not applicable to T20P)
Description
169
Integer 0 (N/A) Valid values are: 0-N/A(default for memory key) 1-Conference 2-Forward 3-Transfer 4-Hold 5-DND 6-Redial 7-Call Return 8-SMS 9-Call Pickup 10-Call Park 11-DTMF 12-Voicemail 13-SpeedDial 14-Intercom 15-Line(default for line key)
Range
16-BLF 17-URL 18-Group Listening 19-Public Hold 20-Private Hold 22-XML Group 23-Group Pickup 24- Multicast Paging 25-Record 27-XMLbrowser 34-Hot Desking 35-URLRecord 38-LDAP 39-BLF List 40-Prefix 41- Zero Touch 42-ACD 45-Local Group
170
Appendix
46-Broadsoft Group 48- Custom Button 50-Keypad Lock Example memorykey.1.type = 8
Parametermemorykey.x.xml_phonebook
Configuration File <y0000000000xx>.cfg Specifies the desired phonebook when multiple phonebooks are configured on the phone. This parameter only applies to the Local Group/XML Group/Broadsoft Group features. X ranges from 1 to 10.
Description
Integer 0 Not Applicable Specify the second phonebook when there
Example
are three Broadsoft groups are configured on the phone. memorykey.1.xml_phonebook = 2
Keypad Lock Key

Parametermemorykey.x.type Configuration File <y0000000000xx>.cfg Configures a memory key to be Keypad Lock key on the phone. Description The digit 50 stands for the key type Keypad Lock. X ranges from 1 to 10. Format Value Example Integer 50 memorykey.1.type = 50
DND Key
ParameterConfiguration File 171
memorykey.x.type
<y0000000000xx>.cfg Configures a memory key to be DND key on
Description
the phone. The digit 5 stands for the key type DND. X ranges from 1 to 10.
Format Value Example
Integer 5 memorykey.1.type = 5
Directed Pickup Key

Parametermemorykey.x.type Configuration File <y0000000000xx>.cfg Configures a memory key to be directed Description pickup key on the phone. The digit 9 stands for the key type Call Pickup. X ranges from 1 to 10. Format Value Example Parametermemorykey.x.line Integer 9 memorykey.1.type = 9 Configuration File <y0000000000xx>.cfg Specifies the desired line to apply the directed Description pickup key. X ranges from 1 to 10. Format Integer Valid values are: Range 0 to 5 (for T28P) 0 to 2 (for T26P/T22P) 0 to 1 (for T20P) Example memorykey.1.line = 1
Parametermemorykey.x.value
172
Appendix
Specifies the directed pickup feature code Description followed by the number of monitored extension. X ranges from 1 to 10. Format Range Example String Not Applicable memorykey.1.value = *971001
Group Pickup Key

Parameterlinekey.x.type Configuration File <y0000000000xx>.cfg Configures a line key to be group pickup key on the phone. Description The digit 23 stands for the key type Group Pickup. X ranges from 1 to 10. Format Value Example Integer 23 linekey.1.type = 23
Parameterlinekey.x.line
Configuration File <y0000000000xx>.cfg Specifies the desired line to apply the group
Description
pickup key. X ranges from 1 to 10.
Format
Integer Valid values are:
Range
Example
linekey.1.line = 1
Parameterlinekey.x.value
Configuration File <y0000000000xx>.cfg 173
Description Format Range Example
Specifies the group pickup feature code. X ranges from 1 to 10. String Not Applicable linekey.1.value = *98
Call Park Key

Parametermemorykey.x.type Configuration File <y0000000000xx>.cfg Configures a memory key to be call park key Description on the phone. The digit 10 stands for the key type Call Park. X ranges from 1 to 10. Format Value Example Integer 10 memorykey.2.type = 10
Parametermemorykey.x.line
Configuration File <y0000000000xx>.cfg Specifies the desired line to apply the call
Description
park key. X ranges from 1 to 10.
Format
Range
Example
174
Appendix
Parametermemorykey.x.value Description Format Range Example
Configuration File <y0000000000xx>.cfg Specifies the call park feature code. X ranges from 1 to 10. String Not Applicable memorykey.2.value = *99
BLF Call Park Key

Parametermemorykey.x.type Configuration File <y0000000000xx>.cfg Configures a memory key to be call park key Description on the phone. The digit 10 stands for the key type Call Park. X ranges from 1 to 10. Format Value Example Integer 10 memorykey.2.type = 10
Parametermemorykey.x.line
Configuration File <y0000000000xx>.cfg Specifies the line enabled the BLF call park
Description
feature to apply the call park key. X ranges from 1 to 10.
Format
Range
Example
175
Configuration File <y0000000000xx>.cfg Specifies the number of the monitored user. X ranges from 1 to 10. String Not Applicable memorykey.2.value = 1008
LDAP Key
Parametermemorykey.x.type Configuration File <y0000000000xx>.cfg Configures a memory key to be LDAP key on Description the phone. The digit 38 stands for the key type LDAP. X ranges from 1 to 10. Format Value Example Integer 38 memorykey.2.type = 38
BLF Key
Parametermemorykey.x.type Configuration File <y0000000000xx>.cfg Configures a memory key to be BLF key on the Description phone. The digit 16 stands for the key type BLF. X ranges from 1 to 10. Format Value Example Integer 16 memorykey.3.type = 16
Parametermemorykey.x.line Description 176
Configuration File <y0000000000xx>.cfg Specifies the desired line to apply the BLF key.
Appendix
X ranges from 1 to 10. Format Integer Valid values are: Range 0 to 5 (for T28P) 0 to 2 (for T26P/T22P) 0 to 1 (for T20P) Example memorykey.3.line = 2
Configuration File <y0000000000xx>.cfg Specifies the number of the monitored user. X ranges from 1 to 10. String Not Applicable memorykey.3.value = 1008
Parametermemorykey.x.pickup_value
Configuration File <y0000000000xx>.cfg Specifies the pickup code for the BLF feature.
Description
This parameter only applies to the BLF feature. X ranges from 1 to 10.
String Blank Not Applicable memorykey.3.pickup_value = *88
This section describes how the Yealink SIP-T2xP IP phones comply with the IETF definition of SIP as described in RFC 3261. This section contains compliance information in the following:

RFC and Internet Draft Support SIP Request SIP Header
177
SIP Responses SIP Session Description Protocol (SDP) Usage
The following RFCs and Internet drafts are supported:

RFC 1321The MD5 Message-Digest Algorithm RFC 2327SDP: Session Description Protocol RFC 2387The MIME Multipart / Related Content-type RFC 2976The SIP INFO Method RFC 3261SIP: Session Initiation Protocol (replacement for RFC 2543) RFC 3262Reliability of Provisional Responses in the Session Initiation Protocol (SIP) RFC 3263Session Initiation Protocol (SIP): Locating SIP Servers RFC 3264An Offer/Answer Model with the Session Description Protocol (SDP) RFC 3265Session Initiation Protocol (SIP) - Specific Event Notification RFC 3311The Session Initiation Protocol (SIP) UPDATE Method RFC 3325SIP Asserted Identity RFC 3515The Session Initiation Protocol (SIP) Refer Method RFC 3555MIME Type of RTP Payload Formats RFC 3611RTP Control Protocol Extended reports (RTCP XR) RFC 3665Session Initiation Protocol (SIP) Basic Call Flow Examples draft-ietf-sip-cc-transfer-05.txtSIP Call Control - Transfer RFC 3725Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)
RFC 3842A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)
RFC 3856A Presence Event Package for Session Initiation Protocol (SIP) RFC 3891The Session Initiation Protocol (SIP) Replaces Header RFC 3892The Session Initiation Protocol (SIP) Referred-By Mechanism RFC 3968The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP)
RFC 3969The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP)
RFC 4028Session Timers in the Session Initiation Protocol (SIP) RFC 4235An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)
178
Appendix
RFC 4662Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists
draft-levy-sip-diversion-04.txtDiversion Indication in SIP draft-anil-sipping-bla-02.txtImplementing Bridged Line Appearances (BLA) Using Session Initiation Protocol (SIP)
draft-ietf-sip-privacy-04.txtSIP Extensions for Network-Asserted Caller Identity and Privacy within Trusted Networks
draft-levy-sip-diversion-06.txtDiversion Indication in SIP draft-ietf-sipping-cc-conferencing-03.txtSIP Call Control - Conferencing for User Agents
draft-ietf-sipping-rtcp-summary-02.txt Session Initiation Protocol Package for Voice Quality Reporting Event
draft-ietf-sip-connect-reuse-04.txtConnection Reuse in the Session Initiation Protocol (SIP)
To find the applicable Request for Comments (RFC) document, go to http://www.ietf.org/rfc.html and enter the RFC number.
The following SIP request messages are supported: Method REGISTER Supported Yes The Yealink SIP-T2xP IP phones support mid-call INVITE Yes changes such as putting a call on hold as signaled by a new INVITE that contains an existing Call-ID. ACK CANCEL BYE OPTIONS SUBSCRIBE NOTIFY REFER PRACK Yes Yes Yes Yes Yes Yes Yes Yes Notes
179
Method INFO MESSAGE UPDATE PUBLISH
Supported Yes Yes Yes Yes
Notes
The following SIP request headers are supported: Method Accept Alert-Info Allow Allow-Events Authorization Call-ID Call-Info Contact Content-Length Content-Type CSeq Diversion Event Expires From Max-Forwards Min-SE P-Asserted-Identity P-Preferred-Identity Proxy-Authenticate Proxy-Authorization Supported Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Notes
180
Appendix
Method RAck Record-Route Refer-To Referred-By Remote-Party-ID Replaces Require Route RSeq Session-Expires Subscription-State Supported To User-Agent Via
Supported Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Notes
The following SIP responses are supported:
1xx ResponseInformation Responses

1xx Response 100 Trying 180 Ringing 181 Call Is Being Forwarded 183 Session Progress Supported Yes Yes Yes Yes Notes
2xx ResponseSuccessful Responses

2xx Response 200 OK Supported Yes Notes
181
202 Accepted
Yes
In REFER transfer.
3xx ResponseRedirection Responses

3xx Response 300 Multiple Choices 301 Moved Permanently 302 Moved Temporarily Supported Yes Yes Yes Notes
4xx ResponseRequest Failure Responses

4xx Response 400 Bad Request 401 Unauthorized 402 Payment Required 403 Forbidden 404 Not Found 405 Method Not Allowed 406 Not Acceptable 407 Proxy Authentication Required 408 Request Timeout 409 Conflict 410 Gone 411 Length Required 413 Request Entity Too Large 414 Request-URI Too Long 415 Unsupported Media Type 416 Unsupported URI Scheme 420 Bad Extension 421 Extension Required 423 Interval Too Brief 480 Temporarily Unavailable Supported Yes Yes Yes Yes Yes Yes No Yes Yes No No No No Yes Yes No No No Yes Yes Notes
182
Appendix
4xx Response 481 Call/Transaction Does Not Exist 482 Loop Detected 483 Too Many Hops 484 Address Incomplete 485 Ambiguous 486 Busy Here 487 Request Terminated 488 Not Acceptable Here 491 Request Pending 493 Undecipherable
Supported Yes Yes No Yes No Yes Yes Yes No No
Notes
5xx ResponseServer Failure Responses

5xx Response 500 Internal Server Error 501 Not Implemented 502 Bad Gateway 503 Service Unavailable 504 Gateway Timeout 505 Version Not Supported Supported Yes Yes No No No No Notes
6xx ResponseGlobal Responses

6xx Response 600 Busy Everywhere 603 Decline 604 Does Not Exist Anywhere 606 Not Acceptable Supported Yes Yes No No Notes
183
SDP Headers vProtocol version oOwner/creator and session identifier aMedia attribute cConnection information mMedia name and transport address sSession name tActive time
Supported Yes Yes Yes Yes Yes Yes Yes
SIP uses six request methods:

INVITEIndicates a user is being invited to participate in a call session. ACKConfirms that the client has received a final response to an INVITE request. BYETerminates a call and can be sent by either the caller or the callee. CANCELCancels any pending searches but does not terminate a call that has already been accepted.
OPTIONSQueries the capabilities of servers. REGISTERRegisters the address listed in the To header field with a SIP server.
The following types of responses are used by SIP and generated by the IP phone or the SIP server:

SIP 1xxInformational Responses SIP 2xxSuccessful Responses SIP 3xxRedirection Responses SIP 4xxClient Failure Responses SIP 5xxServer Failure Responses SIP 6xxGlobal Failure Responses
184
Appendix
The following figure illustrates the scenario of a successful call. In this scenario, the two end users are User A and User B. User A and User B are located at the Yealink SIP IP phones. The call flow scenario is as follows: 1. 2. 3. User A calls User B. User B answers the call. User B hangs up.
User A F1. INVITE B
Proxy Server
User B
F2. INVITE B F3. 100 Trying F4. 100 Trying F5. 180 Ringing F6. 180 Ringing F7. 200 OK F8. 200 OK F9. ACK F10. ACK 2-way RTP channel established F11. BYE F12. BYE F13. 200 OK F14. 200 OK
185
Step
Action
Description User A sends a SIP INVITE message to a proxy server. The INVITE request is an invitation to User B to participate in a call session. In the INVITE request:
The IP address of User B is inserted in the Request-URI field.
User A is identified as the call session initiator in the From field.
F1
INVITEUser A to Proxy Server
A unique numeric identifier is assigned to the call and is inserted in the Call-ID field.
The transaction number within a single call leg is identified in the CSeq field.
The media capability User A is ready to receive is specified.
The port on which User B is prepared to receive the RTP data is specified.
F2
INVITEProxy Server to User B
The proxy server maps the SIP URI in the To field to User B. The proxy server sends the INVITE message to User B. User B sends a SIP 100 Trying response
F3
100 TryingUser B to Proxy Server
to the proxy server. The 100 Trying response indicates that the INVITE request has been received by User B. The proxy server forwards the SIP 100
F4
100 TryingProxy Server to User A
Trying to User A to indicate that the INVITE request has been received by User B. User B sends a SIP 180 Ringing response
F5
180 RingingUser B to Proxy Server
to the proxy server. The 180 Ringing response indicates that the User B is being alerted. The proxy server forwards the 180
F6
180 RingingProxy Server to User A
Ringing response to User A. User A hears the ring-back tone indicating that User B is being alerted.
186
Appendix
Step
Action
Description User B sends a SIP 200 OK response to
F7
200 OK User B to Proxy Server
the proxy server. The 200 OK response notifies User A that the connection has been made. The proxy server forwards the 200 OK
F8
200OKProxy Server to User A
message to User A. The 200 OK response notifies User A that the connection has been made. User A sends a SIP ACK to the proxy
F9
ACKUser A to Proxy Server
server. The ACK confirms that User A has received the 200 OK response. The call session is now active. The proxy server sends the SIP ACK to
F10
ACKProxy Server to User B
User B. The ACK confirms that the proxy server has received the 200 OK response. The call session is now active. User B terminates the call session by
F11
BYEUser B to Proxy Server
sending a SIP BYE request to the proxy server. The BYE request indicates that User B wants to release the call. The proxy server forwards the SIP BYE
F12
BYEProxy Server to User A
request to User A to notify that User B wants to release the call. User A sends a SIP 200 OK response to
F13
200 OKUser A to Proxy Server
the proxy server. The 200 OK response indicates that User A has received the BYE request. The call session is now terminated. The proxy server forwards the SIP 200
F14
200 OKProxy Server to User B
OK response to User B to indicate that User A has received the BYE request. The call session is now terminated.
187
The following figure illustrates the scenario of an unsuccessful call due to the reason of the called user being busy. In this scenario, the two end users are User A and User B. User A and User B are located at the Yealink SIP IP phones. The call flow scenario is as follows: 1. 2. User A calls User B. User B is busy on the phone and unable or unwilling to take another call. The call cant be set up successfully.
User A
Proxy Server
User B
F1. INVITE B F2. INVITE B F3. 100 Trying F4. 100 Trying F5. 486 Busy Here F6. 486 Busy Here F7. ACK F8. ACK
188
Appendix
Step
Action
Description User A sends the INVITE message to a proxy server. The INVITE request is an invitation to User B to participate in a call session. In the INVITE request:
F1
F2
The proxy server maps the SIP URI in the To field to User B. Proxy server forwards the INVITE message to User B. User B sends a SIP 100 Trying response
F3
100 TryingUser B to Proxy Server
to the proxy server. The 100 Trying response indicates that the INVITE request has been received by User B. The proxy server forwards the SIP 100
F4
100 TryingProxy Server to User A
Trying to User A to indicate that the INVITE request has already been received. User B sends a SIP 486 Busy Here response to the proxy server. The 486 Busy Here response is a client error response indicating that User B is successfully connected but User B is busy on the phone and unable or unwilling to take the call.
F5
486 Busy HereUser B to Proxy Server
189
Step
Action 486 Busy HereProxy Server to User A
Description The proxy server forwards the 486 Busy Here response to notify User A that User B is busy. User A sends a SIP ACK to the proxy
F6
F7
server. The SIP ACK message indicates that User A has received the 486 Busy Here message. The proxy server forwards the SIP ACK
F8
to User B to indicate that the 486 Busy Here message has already been received.
190
Appendix
The following figure illustrates the scenario of an unsuccessful call due to the reason of the called user not answering the call. In this scenario, the two end users are User A and User B. User A and User B are located at the Yealink SIP IP phones. The call flow scenario is as follows: 1. 2. 3. User A calls User B. User B does not answer the call. User A hangs up. The call cant be set up successfully.
User A
Proxy Server
User B
F1. INVITE B F2. INVITE B F3. 180 Ringing F4. 180 Ringing F5. CANCEL F6. CANCEL F7. 200 OK F8. 200 OK
191
Step
Action
F1
F2
INVITEProxy Server to User B 180 RingingUser B to Proxy
The proxy server maps the SIP URI in the To field to User B. Proxy server forwards the INVITE message to User B. User B sends a SIP 180 Ringing response to the proxy server. The 180 Ringing response indicates that the user is being alerted.
F3
Server
180 RingingProxy Server to F4 User A
The proxy server forwards the 180 Ringing response to User A. User A hears the ring-back tone indicating that User B is being alerted.
CANCELUser A to Proxy Server F5
User A sends a SIP CANCEL request to the proxy server after not receiving an appropriate response within the time allocated in the INVITE request. The SIP CANCEL request indicates that User A wants to disconnect the call.
F6
CANCELProxy Server to
The proxy server forwards the SIP CANCEL request to notify User B that
192
Appendix
Step User B
Action
Description User A wants to disconnect the call. User B sends a SIP 200 OK response to the proxy server. The SIP 200 OK response indicates that User B has received the CANCEL request.
200 OKUser B to Proxy F7 Server
200 OKProxy Server to User F8 A
The proxy server forwards the SIP 200 OK response to notify User A that the CANCEL request has been processed successfully.
193
The following figure illustrates a successful call setup and call hold. In this scenario, the two end users are User A and User B. User A and User B are located at the Yealink SIP IP phones. The call flow scenario is as follows: 1. 2. 3. User A calls User B. User B answers the call. User A puts User B on hold.
User A F1. INVITE B
Proxy Server
User B
F2. INVITE B F3. 180 Ringing F4. 180 Ringing F5. 200 OK F6. 200 OK F7. ACK F8. ACK 2-way RTP channel established F9. INVITE B (sendonly) F10. INVITE B (sendonly) F11. 200 OK F12. 200 OK F13. ACK F14. ACK No RTP packets being sent
194
Appendix
Step
Action
Description User A sends an INVITE message to a proxy server. The INVITE request is an invitation to User B to participate in a call session. In the INVITE request:
F1
F2
The proxy server maps the SIP URI in the To field to User B. The proxy server sends the INVITE message to User B. User B sends a SIP 180 Ringing response
F3
to the proxy server. The 180 Ringing response indicates that the user is being alerted. The proxy server forwards the 180
F4
Ringing response to User A. User A hears the ring-back tone indicating that User B is being alerted. User B sends a SIP 200 OK response to
F5
200 OKUser B to Proxy Server
the proxy server. The 200 OK response notifies the proxy server that the connection has been made. The proxy server forwards the 200 OK
F6
200 OKProxy Server to User A
message to User A. The 200 OK response notifies User A that the connection has been made. 195
Step
Action
Description User A sends a SIP ACK to the proxy
F7
F8
User B. The ACK confirms that the proxy server has received the 200 OK response. The call session is now active. User A sends a mid-call INVITE request
F9
to the proxy server with new SDP session parameters, which are used to place the call on hold.
F10
The proxy server forwards the mid-call INVITE message to User B. User B sends a SIP 200 OK response to
F11
the proxy server. The 200 OK response notifies User A that the INVITE is successfully processed. The proxy server forwards the 200 OK
F12
response to User A. The 200 OK response notifies User B is successfully put on hold. User A sends an ACK message to the proxy server. The ACK confirms that User A has received the 200 OK response. The call session is now temporarily inactive. No RTP packets are being sent. The proxy server sends the ACK
F13
F14
message to User B. The ACK confirms that the proxy server has received the 200 OK response.
196
Appendix
The following figure illustrates a successful call between Yealink SIP IP phones in which parties are in a call, one of the participants receives a call from a third party, then answers the incoming call. In this call flow scenario, the end users are User A, User B, and User C. They are all using Yealink SIP IP phones, which are connected via an IP network. The call flow scenario is as follows: 1. 2. 3. 4. User A calls User B. User B answers the call. User C calls User B. User B accepts the call from User C.
197
User A
Proxy Server
User B
User C
F1. INVITE B F2. INVITE B F3. 180 Ringing F4. 180 Ringing F5. 200 OK F6. 200 OK F7. ACK F8. ACK 2-way RTP channel established F9. INVITE A F10. INVITE A F11. 180 Ringing F12. 180 Ringing F13. INVITE B ( sendonly ) F14. INVITE B ( sendonly ) F15. 200 OK F316 200 OK F17. ACK F18. ACK No RTP Packets being sent F19. 200 OK F20. 200 OK F21. ACK F22. ACK 2-way RTP channel established
198
Appendix
Step
Action
Description User A sends an SIP INVITE message to a proxy server. The INVITE request is an invitation to User B to participate in a call session. In the INVITE request:
F1
F2
F3
F4
F5
the proxy server. The 200 OK response notifies proxy server that the connection has been made. The proxy server forwards the 200 OK
F6
Step
Action
F7
server, The ACK confirms that User A has received the 200 OK response. The call session is now active. The proxy server sends the SIP ACK to
F8
User B. The ACK confirms that the proxy server has received the 200 OK response. The call session is now active. User C sends an SIP INVITE message to the proxy server. The INVITE request is an invitation to User A to participate in a call session. In the INVITE request:
The IP address of User A is inserted in the Request-URI field.
User C is identified as the call session initiator in the From field.
F9
INVITEUser C to Proxy Server
The media capability User C is ready to receive is specified.
The port on which User A is prepared to receive the RTP data is specified.
F10
INVITEProxy Server to User A
The proxy server maps the SIP URI in the To field to User A. The proxy server sends the INVITE message to User A. User A sends a SIP 180 Ringing
F11
180 RingingUser A to Proxy Server
response to the proxy server. The 180 Ringing response indicates that the user is being alerted. The proxy server forwards the 180
F12
180 RingingProxy Server to User C
Ringing response to User C. User C hears the ring-back tone indicating that User A is being alerted.
200
Appendix
Step
Action
Description User A sends a mid-call INVITE request
F13
F14
The proxy server forwards the mid-call INVITE message to User B. User B sends a 200 OK to the proxy
F15
server. The 200 OK response indicates that the INVITE was successfully processed. The proxy server forwards the 200 OK
F16
F17
F18
message to User B. The ACK confirms that the proxy server has received the 200 OK response. User A sends a 200 OK response to the
F19
proxy server. The 200 OK response notifies that the connection has been made.
F20
200 OKProxy Server User C
The proxy server forwards the 200 OK message to User C. User C sends a SIP ACK to the proxy
F21
ACKUser C to Proxy Server
server. The ACK confirms that User C has received the 200 OK response. The call session is now active. The proxy server forwards the SIP ACK
F22
ACKProxy Server to User A
to User A to confirm that User C has received the 200 OK response.
201
The following figure illustrates a successful call between Yealink SIP IP phones in which two parties are in a call and then one of the parties transfers the call to a third party without consulting the third party. This is called a blind transfer. In this call flow scenario, the end users are User A, User B, and User C. They are all using Yealink SIP IP phones, which are connected via an IP network. The call flow scenario is as follows: 1. 2. 3. 4. User A calls User B. User B answers the call. User B transfers the call to User C. User C answers the call. Call is established between User A and User C.
202
Appendix
User A
Proxy Server
User B
User C
F1. INVITE B F2. INVITE B F3. 180 Ringing F4. 180 Ringing F5. 200 OK F6. 200 OK F7. ACK F8. ACK 2-way RTP channel established F9. REFER F10. 202 Accepted F11. REFER F12. 202 Accepted F13. NOTIFY F14. NOTIFY F15. 200 OK F16. 200 OK F17. BYE F18. BYE F19. 200 OK F20. 200 OK F21. INVITE C F22. INVITE C F23. 180 Ringing F24. 180 Ringing F25. 200 OK F26. 200 OK F27. ACK F28. ACK 2-way RTP channel established
203
Step
Action
Description User A sends an INVITE message to the proxy server. The INVITE request is an invitation to User B to participate in a call session. In the INVITE request:
F1
F2
F3
180 RingingUser B to Proxy server
F4
F5
F6
message to User A. The 200 OK response notifies User A that the connection has been made.
204
Appendix
Step
Action
F7
F8
User B. The ACK confirms that the proxy server has received the 200 OK response. The call session is now active. User B sends a REFER message to the
F9
REFERUser B to Proxy Server
proxy server. User B performs a blind transfer of User A to User C. The proxy server sends a SIP 202 Accept
F10
202 AcceptedProxy Server to User B
response to User B. The 202 Accepted response notifies User B that the proxy server has received the REFER message.
F11
REFERProxy Server to User A
The proxy server forwards the REFER message to User A. User A sends a SIP 202 Accept response
F12
202 AcceptedUser A to Proxy Server
to the proxy server. The 202 Accepted response indicates that User A accepts the transfer.
F13
NOTIFYUser A to Proxy Server NOTIFYProxy Server to User B
User A sends a SIP Notify message to the proxy server. The Notify message informs User B the state of User A. The proxy server forwards the Notify message to User B. User B sends a SIP 200 OK response to
F14
F15
the proxy server. The 200 OK response notifies the proxy server that User B has received the Notify message. The proxy server forwards the SIP 200
F16
OK response to User A. The 200 OK response notifies User A that User B has received the Notify message. User B terminates the call session by
F17
BYEUser B to Proxy Server
sending a SIP BYE request to the proxy server. The BYE request indicates that
205
Step
Action
Description User B wants to release the call.
F18
BYEProxy Server to User A
The proxy server forwards the BYE request to User A. User A sends a SIP 200 OK response to
F19
200OKUser A to Proxy Server
the proxy server. The 200 OK response confirms that User A has received the BYE request.
F20
200OKProxy Server to User B
The proxy server forwards the SIP 200 OK response to User B. User A sends a SIP INVITE request to the
F21
proxy server. In the INVITE request, a unique Call-ID is generated and the Contact-URI field indicates that User A requests the call.
F22
INVITEProxy Server to User C
The proxy server maps the SIP URI in the To field to User C. User C sends a SIP 180 Ringing
F23
180 RingingUser C to Proxy Server
F24
Ringing response to User A. User A hears the ring-back tone indicating that User C is being alerted User C sends a SIP 200 OK response to
F25
200OKUser C to Proxy Server
the proxy server. The 200 OK response notifies the proxy server that the connection has been made.
F26
The proxy server forwards the SIP 200 OK response to User A. User A sends a SIP ACK to the proxy
F27
ACK User A to Proxy Server
server. The ACK confirms that User A has received the 200 OK response. The call session is now active. The proxy server forwards the ACK
F28
ACKProxy Server to User C
message to User C. The ACK confirms that User A has received the 200 OK response. The call session is now active.
206
Appendix
The following figure illustrates a successful call between Yealink SIP IP phones in which two parties are in a call and then one of the parties transfers the call to the third party with consultation. This is called attended transfer. In this call flow scenario, the end users are User A, User B, and User C. They are all using Yealink SIP IP phones, which are connected via an IP network. The call flow scenario is as follows: 1. 2. 3. 4. 5. User A calls User B. User B answers the call. User A calls User C. User C answers the call. User A transfers the call to User C. Call is established between User B and User C.
207
User A
Proxy Server
User B
User C
F1. INVITE B F2. INVITE B F3. 180 Ringing F4. 180 Ringing F5. 200 OK F6. 200 OK F7. ACK F8. ACK 2-way RTP channel established F9. INVITE B sendonly F10. INVITE B sendonly F11. 200 OK F12. 200 OK F13. ACK F14. ACK F15. INVITE C F16. INVITE C F17. 180 Ringing F18. 180 Ringing F19. 200 OK F20. 200 OK F21. ACK F22. ACK 2-way RTP channel established F23. REFER F24. 202 Accepted F25. REFER F26. 202 Accepted F27. NOTIFY F28. NOTIFY F29. 200 OK F31. BYE F32. BYE F33. 200 OK F34. 200 OK 2-way RTP channel established F30. 200 OK
208
Appendix
Step
Action
F1
F2
F3
F4
F5
F6
Step
Action
F7
F8
F9
F10
F11
the proxy server. The 200 OK response notifies User A that the INVITE was successfully processed. The proxy server forwards the 200 OK
F12
F13
F14
message to User B. The ACK confirms that the proxy server has received the 200 OK response. User A sends a SIP INVITE request to the
F15
F16
INVITEProxy Server to User
The proxy server maps the SIP URI to in the To field to User C. The proxy server
210
Appendix
Step C
Action
Description sends the INVITE request to User C. User C sends a SIP 180 Ringing
F17
F18
Ringing response to User A. User A hears the ring-back tone indicating that User C is being alerted. User C sends a SIP 200 OK response to
F19
the proxy server. The 200 OK response notifies User A that the connection has been made. The proxy server forwards the SIP 200
F20
OK response to User A. The 200 OK response notifies User A that the connection has been made. User A sends a SIP ACK to the proxy
F21
server. The ACK confirms that User A has received the 200 OK response. The call session is now active. The proxy server forwards the ACK message to User C. The ACK confirms
F22
that the proxy server has received the 200 OK response. The call session is now active.
F23
REFERUser A to Proxy Server
User A sends a REFER message to the proxy server. User A performs a transfer of User B to User C. The proxy server sends a SIP 202
F24
202 AcceptedProxy Server to User A
Accepted response to User A. The 202 Accepted response notifies User A that the proxy server has received the REFER message.
F25
REFERProxy Server to User B 202 AcceptedUser B to Proxy Server
The proxy server forwards the REFER message to User B. User B sends a SIP 202 Accept response to the proxy server. The 202 Accepted
F26
211
Step
Action
Description response indicates that User B accepts the transfer.
F27
NOTIFYUser B to Proxy Server NOTIFYProxy Server to User A
User B sends a SIP Notify message to the proxy server. The Notify message inform User A the state of User B. The proxy server forwards the Notify message to User A. User A sends a SIP 200 OK response to
F28
F29
the proxy server. The 200 OK response notifies the proxy server that User A has received the Notify message. The proxy server forwards the SIP 200
F30
200 OKProxy Server to User B
OK response to User B. The 200 OK response notifies User B that User A has received the Notify message User A terminates the call session by
F31
BYEUser A to Proxy Server
sending a SIP BYE request to the proxy server. The BYE request indicates that User A wants to release the call.
F32
BYEProxy Server to User B
The proxy server forwards the BYE request to User B. User B sends a SIP 200 OK response to
F33
200OKUser B to Proxy Server
the proxy server. The 200 OK response notifies User A that User B has received the BYE request.
F34
The proxy server forwards the SIP 200 OK response to User A.
212
Appendix
The following figure illustrates successful call forwarding between Yealink SIP IP phones in which User B has enabled always call forward. The incoming call is immediately forwarded to User C when User A calls User B. In this call flow scenario, the end users are User A, User B, and User C. They are all using Yealink SIP IP phones, which are connected via an IP network. The call flow scenario is as follows: 1. 2. 3. 4. User B enables always call forward, and the destination number is User C. User A calls User B. User B forwards the incoming call to User C. User C answers the call. Call is established between User A and User C.
User A
Proxy Server
User B
User C
F1. INVITE B F2. INVITE B F3. 302 Move Temporarily F4. ACK F5. 302 Move Temporarily F6. ACK F7. INVITE C F8. INVITE C F9. 180 Ringing F10. 180 Ringing F11. 200 OK F12. 200 OK F13. ACK F14. ACK 2-way RTP channel established
213
Step
Action
The IP address of the User B is inserted in the Request-URI field.
F1
F2
The proxy server maps the SIP URI in the To field to User B. The proxy server sends the INVITE message to User B. User B sends a SIP 302 Moved
F3
302 Move TemporarilyUser B to Proxy Server
Temporarily message to the proxy server. The message indicates that User B is not available at SIP phone B. User B rewrites the contact-URI. The proxy server sends a SIP ACK to
F4
User B, the ACK message notifies User B that the proxy server has received the 302 Move Temporarily message.
F5
302 Move TemporarilyProxy Server to User A
The proxy server forwards the 302 Moved Temporarily message to User A. User A sends a SIP ACK to the proxy
F6
server. The ACK message notifies the proxy server that User A has received the 302 Move Temporarily message.
214
Appendix
Step
Action
Description User A sends a SIP INVITE request to the
F7
proxy server. In the INVITE request, a unique Call-ID is generated and the Contact-URI field indicates that User A requested the call.
F8
The proxy server maps the SIP URI in the To field to User C. The proxy server sends the SIP INVITE request to User C. User C sends a SIP 180 Ringing
F9
F10
F11
F12
F13
server. The ACK confirms that User A has received the 200 OK response. The call session is now active. The proxy server forwards the ACK message to User C. The ACK confirms
F14
that the proxy server has received the 200 OK response. The call session is now active.
215
The following figure illustrates successful call forwarding between Yealink SIP IP phones in which User B has enabled busy call forward. The incoming call is forwarded to User C when User B is busy. In this call flow scenario, the end users are User A, User B, and User C. They are all using Yealink SIP IP phones, which are connected via an IP network. The call flow scenario is as follows: 1. 2. 3. 4. 5. User B enables busy call forward, and the destination number is User C. User A calls User B. User B is busy. User B forwards the incoming call to User C. User C answers the call. Call is established between User A and User C.
User A
Proxy Server
User B
User C
F1. INVITE B F2. INVITE B F3. 180 Ringing F4. 180 Ringing F5. 302 Move Temporarily F6. ACK F7. 302 Move Temporarily F8. ACK F9. INVITE C F10. INVITE C F11. 180 Ringing F12. 180 Ringing F13. 200 OK F14. 200 OK F15. ACK F16. ACK 2-way RTP channel established
Step
Action
Description
216
Appendix
Step
Action
F1
F2
F3
F4
Ringing response to User A. User A hears the ring-back tone indicating that User B is being alerted. User B sends a SIP 302 Moved
F5
F6
User B, the ACK message notifies User B that the proxy server has received the 217
Step
Action
Description ACK message.
F7
F8
server. The ACK message notifies the proxy server that User A has received the ACK message. User A sends a SIP INVITE request to the
F9
F10
The proxy server forwards the SIP INVITE request to User C. User C sends a SIP 180 Ringing
F11
F12
F13
the proxy server. The 200 OK response notifies User A that the connection has been made.
F14
The proxy server forwards the SIP 200 OK response to User A. User A sends a SIP ACK to the proxy
F15
server. The ACK confirms that User A has received the 200 OK response. The call session is now active.
F16
The proxy server sends the ACK message to User C.
218
Appendix
The following figure illustrates successful call forwarding between Yealink SIP IP phones in which User B has enabled no answer call forward. The incoming call is forwarded to User C when User B does not answer the incoming call after a period of time. In this call flow scenario, the end users are User A, User B, and User C. They are all using Yealink SIP IP phones, which are connected via an IP network. The call flow scenario is as follows: 1. 2. 3. 4. 5. User B enables no answer call forward, and the destination number is User C. User A calls User B. User B does not answer the incoming call. User B forwards the incoming call to User C. User C answers the call. Call is established between User A and User C.
User A
Proxy Server
User B
User C
F1. INVITE B F2. INVITE B F3. 180 Ringing F4. 180 Ringing F5. 302 Move Temporarily F6. ACK F7. 302 Move Temporarily F8. ACK F9. INVITE C F10. INVITE C F11. 180 Ringing F12. 180 Ringing F13. 200 OK F14. 200 OK F15. ACK F16. ACK 2-way RTP channel established
Step
Action
Description
219
Step
Action
F1
F2
F3
F4
Ringing response to User A. User A hears the ring-back tone indicating that User B is being alerted. User B sends a SIP 302 Moved
F5
F6
User B, the ACK message notifies User B that the proxy server has received the
220
Appendix
Step
Action
Description ACK message.
F7
F8
server. The ACK message notifies the proxy server that User A has received the ACK message. User A sends a SIP INVITE request to the
F9
F10
The proxy server forwards the SIP INVITE request to User C. User C sends a SIP 180 Ringing
F11
F12
F13
F14
F15
server. The ACK confirms that User A has received the 200 OK response. The call session is now active. The proxy server sends the ACK
F16
message to User C. The ACK confirms that the proxy server has received the 200 OK response.
221
The following figure illustrates successful 3-way calling between Yealink SIP-T2xP IP phones in which User A mixes two RTP channels and therefore establishes a conference between User B and User C. In this call flow scenario, the end users are User A, User B, and User C. They are all using Yealink SIP IP phones, which are connected via an IP network. The call flow scenario is as follows: 1. 2. 3. 4. 5. 6. User A calls User B. User B answers the call. User A put User B on hold. User A calls User C. User C answers the call. User A mixes the RTP channels and establishes a conference between User B and User C.
222
Appendix
User A F1. INVITE B F4. 180 Ringing F6. 200 OK F7. ACK
Proxy Server
User B
User C
F2. INVITE B F3. 180 Ringing F5. 200 OK
F8. ACK
Session1 established between User A and User B is active F9. INVITE(sendonly) Initiate three party conference F10. INVITE (sendonly) F11. 200 OK F12. 200 OK F13. ACK F14. ACK
Session 1 established between User A and User B is hold F15. INVITE C F16. INVITE C F17. 180 Ringing F18. 180 Ringing F20. 200 OK F21. ACK F22. ACK Both calls are active, come into three-party conference F19. 200 OK
223
Step
Action
F1
F2
The proxy server maps the SIP URI in the To field to User B. Proxy server forwards the INVITE message to User B. User B sends a SIP 180 Ringing response
F3
F4
F5
F6
message to User A. The 200 OK response notifies User A that the connection has been made.
224
Appendix
Step
Action
F7
F8
F9
F10
F11
the proxy server. The 200 OK response notifies User A that the INVITE is successfully processed. The proxy server forwards the 200 OK
F12
response to User A. The 200 OK response notifies User A that User B is successfully put on hold. User A sends the ACK message to the proxy server. The ACK confirms that User A has received the 200 OK response. The call session is now temporarily inactive. No RTP packets are being sent. The proxy server sends the ACK
F13
F14
message to User B. The ACK confirms that the proxy server has received the 200 OK response. User A sends a SIP INVITE request to the
F15
F16
INVITEProxy Server to User
The proxy server maps the SIP URI in the To field to User C. The proxy server 225
Step C
Action
Description sends the SIP INVITE request to User C. User C sends a SIP 180 Ringing
F17
F18
F19
F20
F21
server. The ACK confirms that User A has received the 200 OK response. The call session is now active. The proxy server sends the ACK
F22
message to User C. The ACK confirms that the proxy server has received the 200 OK response.
226
Appendix
This section provides the sample configuration file necessary to configure the IP phone. Any line starts with a pound sign (#) is considered to be a comment, unless the # is contained within double quotes. For Boolean fields, 0 = disabled, 1 = enabled. This file contains sample configurations for the <y0000000000xx>.cfg or <MAC>.cfg file. The parameters included here are examples only. Not all possible parameters are shown in the sample configuration file. You can configure or comment the values as you required. The settings in the <y0000000000xx>.cfg file will be overridden by settings which also appear in the <MAC>.cfg file.
T2xP Sample Configuration File

#!version:1.0.0.1 #Note: This file header cannot be edited or deleted.
#Network Settings
network.internet_port.type = #Configure the WAN port type; 0-DHCP, 1-PPPoE, 2-Static IP Address. #If the WAN port type is configured as DHCP, you do not need to set the #following network parameters. #If the WAN port type is configured as Static IP Address, configure the #following parameters. network.internet_port.ip = network.internet_port.mask = network.internet_port.gateway = network.primary_dns= network.secondary_dns = #If the WAN port type is configured as PPPoE, configure the following #parameters. network.pppoe.user = network.pppoe.password =
#Dial Plan Settings

dialplan.area_code.code = dialplan.area_code.min_len = dialplan.area_code.max_len = dialplan.area_code.line_id = dialplan.block_out.number.1 = dialplan.block_out.line_id.1 = dialnow.item.1 = dialplan.item.1 = 227
#Time Settings
local_time.time_zone = local_time.time_zone_name = local_time.ntp_server1 = local_time.ntp_server2 = local_time.interval = local_time.dhcp_time = #Use the following parameters to set the time and date manually. local_time.manual_time_enable = local_time.date_format = local_time.time_format =
#Auto DST Settings

local_time.summer_time = local_time.dst_time_type = local_time.start_time = local_time.end_time = local_time.offset_time =
#Phone Lock
phone_setting.lock = phone_setting.phone_lock.unlock_pin = phone_setting.phone_lock.lock_time_out =
#Language
lang.wui = lang.gui =
#Call Waiting
call_waiting.enable = call_waiting.tone =
#Auto Redial
auto_redial.enable = auto_redial.interval = auto_redial.times =
#Call Hold
features.play_hold_tone.enable = features.play_hold_tone.delay = sip.rfc2543_hold =
228
Appendix
#Hotline
features.hotline_number = features.hotline_delay =
#Web Server Type

network.web_server_type = network.port.http = network.port.https =
#DTMF Suppression
features.dtmf.hide = features.dtmf.hide_delay =
#Call Forward # In Phone Mode

features.fwd_mode = 0 forward.always.enable = forward.always.target = forward.always.on_code = forward.always.off_code = forward.busy.enable = forward.busy.target = forward.busy.on_code = forward.busy.off_code = forward.no_answer.enable = forward.no_answer.target = forward.no_answer.timeout = forward.no_answer.on_code = forward.no_answer.off_code =
# In Custom Mode
features.fwd_mode = 1 account.1.always_fwd.enable = account.1.always_fwd.target = account.1.always_fwd.on_code = account.1.busy_fwd.off_code = account.1.busy_fwd.enable = account.1.busy_fwd.target = account.1.busy_fwd.on_code = account.1.busy_fwd.off_code = account.1.timeout_fwd.enable = account.1.timeout_fwd.target = account.1.timeout_fwd.timeout = account.1.timeout_fwd.on_code = 229
account.1.timeout_fwd.off_code =
#Call Transfer
transfer.semi_attend_tran_enable = transfer.blind_tran_on_hook_enable = transfer.on_hook_trans_enable = transfer.tran_others_after_conf_enable =
#Call Conference
account.1.conf_type = account.1.conf_uri =
#DTMF
account.1.dtmf.type = account.1.dtmf.dtmf_payload = account.1.dtmf.info_type =
#Distinctive Ring Tones

distinctive_ring_tones.alert_info.1.text = distinctive_ring_tones.alert_info.1.ringer =
#Tones
voice.tone.dial = voice.tone.ring = voice.tone.busy = voice.tone.congestion = voice.tone.callwaiting = voice.tone.dialrecall = voice.tone.record= voice.tone.info = voice.tone.stutter = voice.tone.message = voice.tone.autoanswer =
#Remote Phonebook
features.remote_phonebook.enable = features.remote_phonebook.flash_time =
#LDAP
ldap.name_filter = ldap.number_filter = ldap.host = 0.0.0.0 ldap.port = 389 ldap.base =
230
Appendix
ldap.user = ldap.password = ldap.max_hits = ldap.name_attr = ldap.numb_attr = ldap.display_name = ldap.version = ldap.search_delay = ldap.call_in_lookup = ldap.ldap_sort = ldap.dial_lookup =
#BLF List
account.5.blf.blf_list_uri = account.5.blf_list_code = account.5.blf_list_barge_in_code =
#Shared Call Appearance

account.1.enable = account.1.label = account.1.display_name = account.1.auth_name = account.1.password = account.1.user_name = account.1.sip_server_host = account.1.sip_server_port = account.1.outbound_proxy_enable = account.1.outbound_host = account.1.outbound_port = account.1.shared_line =
#Action URL
action_url.setup_completed = action_url.log_on = action_url.log_off = action_url.register_failed = action_url.off_hook = action_url.on_hook = action_url.incoming_call = action_url.outgoing_call = action_url.call_established = action_url.dnd_on = action_url.dnd_off = action_url.always_fwd_on =
231
action_url.always_fwd_off = action_url.busy_fwd_on = action_url.busy_fwd_off = action_url.no_answer_fwd_on = action_url.no_answer_fwd_off = action_url.transfer_call = action_url.blind_transfer_call = action_url.attended_transfer_call = action_url.hold = action_url.unhold = action_url.mute = action_url.unmute = action_url.missed_call = action_url.call_terminated = action_url.busy_to_idle = action_url.idle_to_busy = action_url.forward_incoming_call = action_url.reject_incoming_call = action_url.answer_new_incoming_call = action_url.transfer_finished = action_url.transfer_failed =
#SNMP
network.snmp.enable = network.snmp.port = network.snmp.trust_ip =
#TR069
managementserver.enable = managementserver.username = managementserver.password = managementserver.url = managementserver.connection_request_username = managementserver.connection_request_password = managementserver.periodic_inform_enable = managementserver.periodic_inform_interval =
#Access URL of Resource Files

dialplan_dialnow.url = dialplan_replace_rule.url = local_contact.data.url = remote_phonebook.data.1.url =
232
Index
Numeric 802.1x Authentication A About This Guide Action URL Action URI 60 63 v 94 38 v 70
Centralized Conference Configuration Files 18
40 v
Changes from Previous Versions Configuration Interface 17
Changing the AES Keys on the Phone Configuring Advanced features Configuring Basic Features 25 11 51
79
Configuring Network Parameters Manually 20 Connect the Network and Power Connecting the Phone Creating Dial Plan D 184 Dial-now 23 84 51 35 41 21 11
Administrator Password Always Forward Appendix 99
Analyzing the Configuration Files Appendix A: Glossary Appendix B: SIP Area Code 23 59 11 39 101 99
Appendix C: SIP Call Flows As-Feature-Event Attach the Stand Attended Transfer Auto Redial B BLF Call Park Blind Transfer Block Out 24 38 57 Busy Forward Busy Lamp Field C Call Forward Call Hold 37 44 39 34 34 47 46 38 44 39 34
Dial-now Template Directed Pickup Distinctive Ring Tones Do Not Disturb (DND) Documentations DTMF E 48 v
Encrypting Configuration Files Enabling the Watch Dog Feature G
78 93
Getting Information from Status Indicators Getting Started Group Pickup Key H H.323 Hotline I In This Guide Index 233 v 1 44 11 42
93
Call Park/Retrieve Call Transfer Call Waiting
Call Waiting Tone
Caller ID Presentation Callee ID Presentation Capturing Packets 92
233
Initialization Process Overview K
15
SIP
1 2 3 180 179 181 184
SIP Components SIP Header 8 SIP Request SIP Responses 30 31 SNMP 69
Key Features of the SIP-T2xP IP Phones L Language LDAP 55 85 33
SIP IP Phone Models
SIP Session Description Protocol Usage Specifying the Language to Use STUN Server 67 31
Loading Language Packs Local Contact File Local Directory M Missed Call Log 32
Suppressing the Display of DTMF Digits T Table of Contents Time and Date 69 28 41 75 1
49
Management Information Bases N NAT Traversal 67
Transfer on Conference Hang Up Transport Layer Security (TLS) Troubleshooting 91 91 94 72 Troubleshooting Methods 67 Troubleshooting Solutions TR-069 Device Management U
Network Address Translation (NAT) No Answer Forward P Phone Lock 27 17 38
Upgrading Firmware
81 2 3
Phone User Interface Product Overview R Reading Icons 19 1
User Agent Client (UAC) 4 User Agent Server (UAS) User Password V Verifying Startup 17 91 26
Physical Features of the SIP-T2xP IP Phones
Remote Phonebook Replace Rule 22
54 87 83 37 178
Viewing Log Files VoIP Principle W Web Server Type Web User Interface 1
Remote XML Phonebook Replace Rule Template
Return Message When DND RFC and Internet Draft Support S Security Features Server Redundancy 75 39 58 60
46 17
Semi-attended Transfer Shared Call Appearance 234

Yealink SIP-T2xP IP Phone Family Administrator Guide - V2.1

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Yealink SIP-T2xP IP Phone Family Administrator Guide - V2.1

Uploaded by

Copyright:

Available Formats

Copyright 2012 YEALINK NETWORK TECHNOLOGY Copyright 2012 Yealink Network Technology CO., LTD. All rights reserved.

About This Guide

Administrator s Guide for SIP-T2xP IP Phones

phones and the IP phone interface methods.

Chapter 5, Security Features describes the encryption information of the IP phones.

The following sections are new for this version:

Major updates have occurred to the following sections:

About This Guide

Major updates have occurred to the following sections:

About This Guide ...................................................................... v

Table of Contents ..................................................................... 1 Product Overview ..................................................................... 1

Getting Started ....................................................................... 11

Configuring Basic Features .................................................... 25

Administrator s Guide for SIP-T2xP IP Phones

Configuring Advanced Features............................................ 51

Security Features .................................................................... 75

Upgrading the Firmware........................................................ 81 Resource Files ......................................................................... 83

Administrator s Guide for SIP-T2xP IP Phones

VoIP Principle SIP Components SIP IP Phone Models

Administrator s Guide for SIP-T2xP IP Phones

SIP provides the capabilities to:

User Agent Client (UAC)

User agent server (UAS)

SIP-T28P SIP-T26P SIP-T22P SIP-T20P

A working IP network is established. Routers are configured for VoIP .

Administrator s Guide for SIP-T2xP IP Phones

Administrator s Guide for SIP-T2xP IP Phones

Administrator s Guide for SIP-T2xP IP Phones

Codecs and Voice Features

Administrator s Guide for SIP-T2xP IP Phones

A headset is not provided in the packing list.

Attaching the Stand:

Administrator s Guide for SIP-T2xP IP Phones

Connecting the Handset and optional Headset:

Connecting the Network and Power:

AC power Power over Ethernet (PoE)

Power over Ethernet

Attaching the Stand: Desk-mounted Method

Administrator s Guide for SIP-T2xP IP Phones

Connecting the Handset and optional Headset:

Power over Ethernet

Administrator s Guide for SIP-T2xP IP Phones

Language files Ring tones Directories

Time and Date Soft key labels (not supported by T20P)

Phone User Interface Web User Interface Configuration Files

Administrator s Guide for SIP-T2xP IP Phones

SIP-T28P: y000000000000.cfg SIP-T26P: y000000000004.cfg SIP-T22P: y000000000005.cfg SIP-T20P: y000000000007.cfg

The IP phone can accept two sources of configuration data:

Registering Hands-free speakerphone mode Handset mode

Administrator s Guide for SIP-T2xP IP Phones

Description Do Not Disturb

IP Address Subnet Mask Default Gateway Primary DNS Secondary DNS

Replace Rule Dial-now Area Code Block Out

Administrator s Guide for SIP-T2xP IP Phones

Administrator s Guide for SIP-T2xP IP Phones

Configuring Basic Features

Administrator s Guide for SIP-T2xP IP Phones

Configuring Basic Features

Administrator s Guide for SIP-T2xP IP Phones

Configuring Basic Features

Daylight Saving Time

Administrator s Guide for SIP-T2xP IP Phones