Yealink reserves the right to make changes to any products described herein to improve reliability, function, or design, and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes.
This guide describes the configuration procedures required for the Yealink W52P IP DECT Phone for interoperability with BroadWorks. The W52P IP DECT Phone is an IP phone that uses the Session Initiation Protocol (SIP) to communicate with BroadWorks for call control.
Interoperability Status This section provides the known interoperability status of the Yealink W52P IP DECT Phone with BroadWorks. This includes the version(s) tested, capabilities supported and known issues. Interoperability testing validates that the device interfaces properly with BroadWorks via the SIP interface. Qualitative aspects of the device or device capabilities not affecting the SIP interface such as display features, performance, and audio qualities are not covered by interoperability testing.
BroadWorks with the intent to ensure interoperability sufficient to support the BroadWorks feature set. The Supported column in the following table identifies the Yealink W52P IP DECT Phone’s support for each of the items covered in the test plan packages, with the following designations: ...
W52P IP DECT Phone. BroadWorks Device Profile Type Configuration This section identifies the device profile type to use when deploying the Yealink W52P IP DECT Phone with BroadWorks. The following table identifies the required BroadWorks device identity/profile type settings for interoperability between the W52P IP DECT Phone and BroadWorks.
W52P IP DECT Phone Configuration The W52P IP DECT Phone can be configured with a configuration file using the Trivial File Transfer Protocol (TFTP) or through its embedded web server. The following examples describe how to set the parameters using a configuration file. This configuration description assumes the W52P IP DECT Phone uses the Dynamic Host Configuration Protocol (DHCP) to obtain an IP address, TFTP server, and other network settings.
This section describes the steps to integrate the Yealink W52P IP DECT Phones. As part of the Yealink W52P IP DECT Phone CPE kit, BroadSoft has defined a standard device configuration in the device template files that service providers can use on their systems.
Busy Lamp Field Device Management Configuration This section identifies the steps required to enable the Yealink W52P IP DECT Phone phones for device management. For Device Management configuration details not covered here, refer to the BroadWorks Device Management Configuration Guide [2].
Yealink W52P phone models only. The Yealink W52P IP DECT Phone makes use of dynamic tags, which may be configured by a BroadWorks administrator as either system default or device type specific tags. This section identifies the required tags.
Page 22
Configure the tag set name using the device name appended by Tags: Yealink W52P IP DECT Phone Tags. Add the device type specific tags in the following table to the device tag set. If the tag set already exists, ensure the tags are defined in the following table.
Configuration Method 1: Import This section identifies the steps necessary to make use of the Device Management import feature to configure BroadWorks to add the Yealink W52P IP DECT Phone as a Device Management-enabled device type. The import method is available in BroadWorks Release 17.0 and later. For previous releases, use the manual configuration method described in the next section.
Define Device Profile Type Files This section describes the BroadWorks Device Management configuration necessary to identify the configuration files and other files that the Yealink W52P IP DECT Phone downloads. To define the files, configuration templates, firmware and other files the W52P IP DECT Phone uses, they must be uploaded to BroadWorks.
Page 29
This file defines the access level of configuration items in cfg format. The following table identifies other files that the Yealink W52P IP DECT Phone downloads from the server or uploads to the server. These files are not provided in the CPE kit and must be obtained from Yealink.
Page 30
y000000000025.cfg Add a BroadWorks device profile type file to Yealink W52P IP DECT Phone device profile for the system file using the settings described in the following table. Parameters not identified in the following table can usually be left as defaults.
Page 32
<mac-address>.cfg Add a BroadWorks device profile type file to Yealink W52P device profile for the device- specific file using the settings described in the following table. Parameters not identified in the following table can usually be left as defaults.
Page 34
WebItemsLevel.cfg Add a BroadWorks device profile type file to Yealink W52P device profile for each of the static files using the settings described in the following table. Parameters not identified in the following table can usually be left as defaults.
After defining the static file types, upload the corresponding static files. Firmware must be obtained from Yealink. The other files are available from the BroadSoft Xchange. Use the Browse button on the file definition screen. Be sure to click Apply after uploading the file.
Page 36
The CPE kit contains the time zone properties files defined for the continental U.S. and Canadian time zones. For other time zone settings, refer to the Yealink W52P IP DECT Phone User Guide [1]. When using the DTAF import, the TimeZoneAlias files are automatically copied onto the system.
Browse to the BroadWorks <group> → Resources → Identity/Device Profiles and select Add to add a new Yealink W52P IP DECT Phone device profile. Define the device profile instance using the settings described in the following table.
This section describes the steps necessary to configure the Yealink W52P to integrate with BroadWorks Device Management. Log in to the web user interface for the W52P IP DECT Phone (https://<phone-ip- address>). Go to the Phone → Auto Provision web page and set the following: ...
NOTE: The following samples are examples and should be used as a reference only. DO NOT CUT AND PASTE THESE EXAMPLES TO GENERATE YOUR CONFIGURATION FILES. Use the configuration files obtained from Yealink with the specific release to generate your configuration files. System Default File: y000000000025.cfg NOTE: This is an example file and should be used for reference only.
References [1] Yealink, Inc. 2013. Yealink W52P IP DECT Phone User Guide, Release 30. Available from Yealink at http://www.yealink.com/Support.aspx. [2] BroadSoft, Inc. 2013. BroadWorks Device Management Configuration Guide, Release 19.0. Available from BroadSoft at xchange.broadsoft.com. [3] BroadSoft, Inc. 2013. BroadWorks Redundancy Guide, Release 19.0. Available from BroadSoft at xchange.broadsoft.com.
Need help?
Do you have a question about the W52P and is the answer not in the manual?
Questions and answers