Yealink Telkom W52P User manual

BroadSoft Partner Configuration Guide
Yealink W52P IP DECT Phone
May 2013
Document Version 1.2
4
th
-5
th
Floor, No.63 Wanghai Road, 2
nd
Software Park,
Xiamen, Fujian, China 361008
Tel: [phone]
Fax: [phone]
WWW.YEALINK.COM

BROADSOFT PARTNER CONFIGURATION GUIDE – YEALINK W52P IP DECT PHONE 20-BD5392-00
©2013 YEALINK PAGE 2 OF 54
BroadWorks®Guide
Copyright Notice
Copyright© 2008-2018. Yealink Network Technology Co., Ltd. All rights reserved. While
reasonable efforts have been made to ensure the accuracy of this document, Yealink
assumes no liability resulting from any omission or inaccuracies in this document or from
use of the information obtained herein. 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. Yealink does not assume any
liability arising out of the application or use of any product described herein; neither does it
convey license under its patent rights or the rights of others.
Trademarks
BroadWorks®and BroadWorks Assistant–Enterprise™, BroadWorks Call Center™,
BroadWorks Communicator™, BroadWorks Receptionist™, and BroadWorks
Deployment Studio™ are trademarks of BroadSoft, Inc.
Microsoft, MSN, Windows, and the Windows logo are registered trademarks of Microsoft
Corporation. Other product names mentioned in this document may be trademarks or
registered trademarks of their respective companies and are hereby acknowledged.
This document is printed in the United States of America.

BROADSOFT PARTNER CONFIGURATION GUIDE – YEALINK W52P IP DECT PHONE 20-BD5392-00
©2013 YEALINK PAGE 3 OF 54
Document Revision History
Version Reason for Change
1.1 Introduced document for Yealink W52P IP DECT Phone version 25.30.0.10 validation with
BroadWorks Release 19.sp1.
1.2 Edited and published document.

BROADSOFT PARTNER CONFIGURATION GUIDE – YEALINK W52P IP DECT PHONE 20-BD5392-00
©2013 YEALINK PAGE 4 OF 54
Table of Contents
1Overview.............................................................................................................................................6
2Interoperability Status......................................................................................................................7
2.1 Verified Versions...........................................................................................................................7
2.2 Interface Capabilities Supported..................................................................................................8
2.3 Known Issues ............................................................................................................................ 12
3BroadWorks Configuration .......................................................................................................... 13
3.1 BroadWorks Device Profile Type Configuration ...................................................................... 13
3.2 BroadWorks Configuration Steps............................................................................................. 14
4W52P IP DECT Phone Configuration.......................................................................................... 15
4.1 System Level Configuration...................................................................................................... 15
4.2 Subscriber Level Configuration Parameters............................................................................ 17
5Device Management ...................................................................................................................... 18
5.1 Device Management Capabilities Supported .......................................................................... 18
5.2 Device Management Configuration.......................................................................................... 19
5.2.1 Configure BroadWorks Tags ........................................................................................... 20
5.2.2 Configure BroadWorks Device Profile............................................................................. 24
5.2.3 Create Device Profile Instance ........................................................................................ 37
5.2.4 Configure BroadWorks User............................................................................................ 38
5.2.5 Configure Edge Device .................................................................................................... 39
5.2.6 Configure Yealink W52P IP DECT Phone...................................................................... 40
Appendix A: Sample W52P Configuration Files............................................................................... 42
References ............................................................................................................................................... 54

BROADSOFT PARTNER CONFIGURATION GUIDE – YEALINK W52P IP DECT PHONE 20-BD5392-00
©2013 YEALINK PAGE 5 OF 54
Table of Figures
Figure 1 System Default Tag Settings.....................................................................................................21
Figure 2 Device Type Specific Tag Settings...........................................................................................23
Figure 3 Device Access FQDN................................................................................................................25
Figure 4 Auto Configuration Option Settings ..........................................................................................26
Figure 5 Device Management Options Settings.....................................................................................28
Figure 6 System File Settings..................................................................................................................31
Figure 7 Device Specific File Settings.....................................................................................................33
Figure 8 Static File Settings .....................................................................................................................35
Figure 9 Identity/Device Profile Add Settings..........................................................................................38
Figure 10 Addresses Settings..................................................................................................................39
Figure 11 Login Screen............................................................................................................................40
Figure 12 Upgrade Screen.......................................................................................................................41

BROADSOFT PARTNER CONFIGURATION GUIDE – YEALINK W52P IP DECT PHONE 20-BD5392-00
©2013 YEALINK PAGE 6 OF 54
1 Overview
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.
This guide describes the specific configuration items that are important for use with
BroadWorks. It does not describe the purpose and use of all configuration items on the
W52P IP DECT Phone. For those details, see the Yealink W52P IP DECT Phone User
Guide [1] supplied by Yealink.

BROADSOFT PARTNER CONFIGURATION GUIDE – YEALINK W52P IP DECT PHONE 20-BD5392-00
©2013 YEALINK PAGE 7 OF 54
2 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. Requests for information and/or issues regarding these aspects
should be directed to Yealink.
2.1 Verified Versions
The following table identifies the verified Yealink W52P IP DECT Phone and BroadWorks
versions and the month/year the testing occurred. If the device has undergone more than
one test cycle, versions for each test cycle are listed, with the most recent listed first.
Compatible Versions in the following table identify specific W52P IP DECT Phone
versions which the partner has identified as compatible and should interface properly with
BroadWorks. Generally, maintenance releases of the validated version are considered
compatible and are not specifically listed here. For any questions concerning
maintenance and compatible releases, contact Yealink.
NOTE: Interoperability testing is usually performed with the latest generally available (GA)
device firmware/software and the latest GA BroadWorks release and service packat the time the
testing occurs. If there is a need to use a non-verified mix of BroadWorks and device software
versions, customers can mitigate their risk by self-testing the combination themselves using the
BroadWorks SIP Access Device Interoperability Test Plan [4].
Verified Versions
Date (mm/yyyy) BroadWorks Release W52P IP DECT
Phone Verified
Version
W52P IP DECT
Phone Compatible
Versions
04/2013 Release 19.sp1 25.30.0.10 None

BROADSOFT PARTNER CONFIGURATION GUIDE – YEALINK W52P IP DECT PHONE 20-BD5392-00
©2013 YEALINK PAGE 8 OF 54
2.2 Interface Capabilities Supported
The Yealink W52P IP DECT Phone has completed interoperability testing with
BroadWorks using the BroadWorks SIP Access Device Interoperability Test Plan [4]. The
results are summarized in the following table.
The BroadWorks test plan is composed of packages, each covering distinct
interoperability areas, such as “Basic” call scenarios and “Redundancy” scenarios. Each
package is composed of one or more test items, which in turn, are composed of one or
more test cases. The test plan exercises the SIP interface between the device and
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:
Yes Test item is supported.
No Test item is not supported.
NA Test item is not applicable to the device type.
NT Test item was not tested.
Caveats and clarifications are identified in the Comments column.
NOTE: DUT in the following table refers to the Device Under Test, which in thiscase is the
Yealink W52P IP DECT Phone.
BroadWorks SIP Access Device Interoperability Test Plan Support Table
Test Plan Package Test Plan Package Items Supported Comments
Basic Call Origination Yes
Call Termination Yes
Session Audit Yes
Session Timer Yes
Ringback Yes
Forked Dialog Yes
Early UPDATE No
Early-Session No
181 Call Being Forwarded Yes
Dial Plan Yes
Dual-Tone Multi-Frequency (DTMF) –
Inband Yes
DTMF – RFC 2833 Yes
DTMF – DTMF Relay Yes
Codec Negotiation Yes
Codec Renegotiation Yes
BroadWorks Services Third-Party Call Control – Basic Yes

BROADSOFT PARTNER CONFIGURATION GUIDE – YEALINK W52P IP DECT PHONE 20-BD5392-00
©2013 YEALINK PAGE 9 OF 54
BroadWorks SIP Access Device Interoperability Test Plan Support Table
Test Plan Package Test Plan Package Items Supported Comments
Third-Party Call Control – Advanced NS
Voice Message Deposit or Retrieval Yes
Message Waiting Indicator Yes
Voice Portal Outcall Yes
Advanced Alerting Yes
Calling Line ID Yes
Calling Line ID with Unicode
Characters No
Connected Line ID Yes
Connected Line ID with Unicode
Characters No
Connected Line ID on UPDATE Yes
Connected Line ID on Re-INVITE Yes
Diversion Header Yes
History-Info Header Yes
Advice of Charge No
Meet-Me Conferencing Yes
DUT Services – Call
Control Services Call Waiting Yes
Call Hold Yes
Call Transfer Yes
Three-Way Calling Yes Does not support three-
way call before answer.
Network-Based Conference No
DUT Services –
Registration and
Authentication
Register Authentication Yes
Maximum Registration Yes
Minimum Registration Yes
Invite Authentication Yes
Re-Invite or Update Authentication Yes
Refer Authentication Yes
Device Authenticating BroadWorks No
DUT Services – Fax G711 Fax Passthrough No
G711 Fax Fallback No
T38 Fax Messaging No
DUT Services –
Emergency Call Emergency Call No
Emergency Call with Ringback No
DUT Services – Do Not Disturb Yes

BROADSOFT PARTNER CONFIGURATION GUIDE – YEALINK W52P IP DECT PHONE 20-BD5392-00
©2013 YEALINK PAGE 10 OF 54
BroadWorks SIP Access Device Interoperability Test Plan Support Table
Test Plan Package Test Plan Package Items Supported Comments
Miscellaneous
Call Forwarding Always Yes
Call Forwarding Always Diversion
Inhibitor Yes
Anonymous Call Yes
Anonymous Call Block Yes
Remote Restart Via Notify Yes
Advanced Phone
Services – Busy
Lamp Field
Busy Lamp Field No
Call Park Notification No
Advanced Phone
Services – Feature
Key Synchronization,
Private Line
Do Not Disturb Yes Does not support
activating DND for
multiple lines.
Do Not Disturb Ring Splash Yes
Call Forwarding Yes
Call Forwarding Always Ring Splash Yes
Call Forwarding Always Diversion
Inhibitor Yes
Call Center Agent Logon or Logoff No
Call Center Agent Unavailable Code No
Advanced Phone
Services – Feature
Key Synchronization,
Shared Line
Do Not Disturb No
Do Not Disturb Ring Splash No
Call Forwarding No
Call Forwarding Always Ring Splash No
Call Forwarding Always Diversion
Inhibitor No
Advanced Phone
Services – Missed
Calls Display
Synchronization
Missed Calls Display Sync No
Advanced Phone
Services – Shared
Call Appearance
using Call Info
Line-Seize No
Call-Info or Lamp Management No
Public Hold No
Private Hold No
Hybrid Key System No
Multiple Call Arrangement No
Bridging No
Call Park Notification No
Advanced Phone
Services – Call Center Hold Reminder No
Call Information No

BROADSOFT PARTNER CONFIGURATION GUIDE – YEALINK W52P IP DECT PHONE 20-BD5392-00
©2013 YEALINK PAGE 11 OF 54
BroadWorks SIP Access Device Interoperability Test Plan Support Table
Test Plan Package Test Plan Package Items Supported Comments
Hoteling Event No
Status Event No
Disposition Code No
Emergency Escalation No
Customer Originated Trace No
Advanced Phone
Services – Call Park
Notification
Call Park Notification No
Redundancy Domain Name System (DNS)
SRV Lookup Yes
Register Failover or Failback Yes
Invite Failover or Failback Yes
Bye Failover Yes
Session Border
Controller
(SBC)/Application
Layer Gateway (ALG)
Register Yes
Outgoing Invite Yes
Incoming Invite Yes
Video – Basic Video
Calls Call Origination No
Call Termination No
Call Hold No
Call Waiting No
Call Transfer No
Video – BroadWorks
Video Services Auto Attendant No
Auto Attendant – HD No
Voice Messaging No
Voice Messaging – HD No
Custom Ringback No
TCP Register Yes
Outgoing Invite Yes
Incoming Invite Yes
IPV6 Call Origination No
Call Termination No
Session Audit No
Ringback No
Codec Negotiation or Renegotiation No
Voice Message Deposit or Retrieval No
Call Control No

BROADSOFT PARTNER CONFIGURATION GUIDE – YEALINK W52P IP DECT PHONE 20-BD5392-00
©2013 YEALINK PAGE 12 OF 54
BroadWorks SIP Access Device Interoperability Test Plan Support Table
Test Plan Package Test Plan Package Items Supported Comments
Registration with Authentication No
T38 Fax Messaging No
Busy Lamp Field No
Redundancy No
SBC No
Video No
Dual Stack with Alternate
Connectivity No
2.3 Known Issues
This section lists the known interoperability issues between BroadWorks and specific
partner release(s). Issues identified during interoperability testing and known issues
identified in the field are listed.
The following table provides a description of each issue and, where possible, identifies a
workaround. The verified partner device versions are listed with an “X” indicating that the
issue occurs in the specific release. The issues identified are device deficiencies or bugs,
and are typically not BroadWorks release dependent.
If the testing was performed by BroadSoft, then the Issue Number is a BroadSoft
ExtraView partner issue number. If the testing was performed by the partner or a third
party, then the partner may or may not supply a tracking number.
For more information on any issues related to the particular partner device release, see
the partner release notes.
Issue Number Issue Description Partner Version
25.30.0.10
No issues identified.

BROADSOFT PARTNER CONFIGURATION GUIDE – YEALINK W52P IP DECT PHONE 20-BD5392-00
©2013 YEALINK PAGE 13 OF 54
3 BroadWorks Configuration
This section identifies the required BroadWorks device profile type for the Yealink W52P
IP DECT Phone as well as any other unique BroadWorks configuration required for
interoperability with the W52P IP DECT Phone.
3.1 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. For an
explanation of the profile parameters, see the BroadWorks Device Management
Configuration Guide [2].
For most of the following parameters, an “X” indicates that the parameter function is
supported and/or required. If the item is blank, it is not supported. For items where text is
supplied, the text content maps directly to the web page to add or to modify a device
profile type.
Yealink W52P IP DECT Phone Identity/Device Profile Type
Signaling Address Type Intelligent Proxy Addressing
Standard Options
Number of Ports 5
Ringback Tone or Early Media
Support Local Ringback – No Early Media
Authentication Enabled
Hold Normalization RFC 3264
Registration Capable X
Static Registration Capable
E.164 Capable
Trusted
Authenticate REFER
Video Capable
Use History-Info Header
Advanced Options
Route Advance
Wireless Integration
PBX Integration
Add P-Called-Party-ID
Auto Configuration Soft Client
Requires BroadWorks Call
Waiting Tone
Advice of Charge Capable

BROADSOFT PARTNER CONFIGURATION GUIDE – YEALINK W52P IP DECT PHONE 20-BD5392-00
©2013 YEALINK PAGE 14 OF 54
Yealink W52P IP DECT Phone Identity/Device Profile Type
Support Emergency Disconnect
Control
Enable Monitoring
Static Line/Port Ordering
Forwarding Override
Conference Device
Music On Hold Device
Requires BroadWorks Digit
Collection
Requires MWI Subscription
Support Call Center MIME Type
Support Identity in UPDATE and
Re-INVITE
Support RFC 3398
Reset Event checkSync
Trunk Mode User
Hold Announcement Method Inactive
Unscreened Presentation Identity
Policy Profile Presentation Identity
Web Based Configuration URL
Extension
Device Configuration Options
Device Configuration Options Device Management
3.2 BroadWorks Configuration Steps
No additional BroadWorks configuration steps are required.

BROADSOFT PARTNER CONFIGURATION GUIDE – YEALINK W52P IP DECT PHONE 20-BD5392-00
©2013 YEALINK PAGE 15 OF 54
4 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. The
W52P IP DECT Phone should be configured to load the configuration file each time it
resets or re-synchronizes. For detailed information on automated provisioning, refer to the
Yealink W52P IP DECT Phone User Guide [1].
The capabilities of the W52P IP DECT Phone have been verified for use with BroadWorks
based on the settings described in the following table. For more information on the
meaning, purpose, and applicability of the individual configuration items refer to the
Yealink W52P IP DECT Phone User Guide [1].
Configuration Files
Files Provided by Partner Level Description
y0000000000<xx>.cfg system configuration file “y0000000000xx.cfg”, where “xx”
associated with the hardware
version of Yealink Device.
<MACADDRESS>.cfg device-specific
configuration file
4.1 System Level Configuration
This section describes system-wide configuration items that are generally required for
each W52P IP DECT Phone to work with BroadWorks. Subscriber-specific settings are
described in the next section.
Step Command Purpose
System Configuration Items y0000000000<xx>.cfg
Step 1 Set SIP Proxy/Domain.
account.SIPServerHost =
as.broadworks.net
account.SIPServerPort = 5060
Set the W52P IP DECT Phone SIP
server to the Fully Qualified Domain
Name (FQDN) for the BroadWorks
Application Server cluster.
The domain must match the domain
configured for the BroadWorks
subscriber’s line/port domain.
Step 2 Set Outbound Proxy.
account.UseOutboundProxy = 1
account.OutboundHost =
sbc.broadworks.net
account.OutboundPort = 5060
Set the Outbound Proxy to the
session border controller (SBC) if one
is deployed between the W52P IP
DECT Phone and BroadWorks.
If there are redundant SBCs, set it to
the FQDN for the SBC cluster.
Step 3
Set SIP Timers.
ADVANCED.default_t1 = 0.5
ADVANCED.default_t2 = 4
ADVANCED.default_t4 = 5
The SIP timers should be set to levels
short enough to support a timely
failover when there is no server
response.

BROADSOFT PARTNER CONFIGURATION GUIDE – YEALINK W52P IP DECT PHONE 20-BD5392-00
©2013 YEALINK PAGE 16 OF 54
Step Command Purpose
System Configuration Items y0000000000<xx>.cfg
Step 4 Set Register Expire Timer.
account.Expire = 3600 Set the registration period.
Step 5 Enable reliable response.
account.Enable 100Re = 1
Reliable provisional response
(PRACK) should be enabled.
Step 6
Enable Session Timer.
account.EnableSessionTimer = 1
account.SessionExpires = 300
account.SessionRefresher = 1
Set the W52P IP DECT Phone to
enable Session Timer.
Session Refresher:
0 = uac
1 = uas
Step 7 Enable Call Waiting.
Features.Call_Waiting = 1
Features.Call_WaitingTone = 1
Set the W52P IP DECT Phone series
to enable Call Waiting and Call
Waiting Tone.
Step 8 Enable MWI.
account.SubsribeMWI = 0
account.SubscribeMWIExpire = 3600
MWI: Solicited when setting
SubscribeMWI = 1.
MWI: Not solicited when setting
SubscribeMWI = 0.
Step 9 Enable negotiated DTMF type.
account.DTMFInbandTransfer = 1
Set the W52P IP DECT Phone to
enable inband or RFC 2833
negotiated DTMF.
Step 10 Select Transport Type.
account.Transport = 0
Set the SIP transport:
Transport = 0 (UDP)
Transport = 1 (TCP)
Transport = 2 (TLS) (except T18P)
Transport = 3 (DNS-SRV) (except
T80P)
Step 11 Enable Feature Key Sync.
Features.BroadsoftFeatureKeySync
= 1
Enable Feature Key Sync (except
T18):
1: Enable
0: Disable

BROADSOFT PARTNER CONFIGURATION GUIDE – YEALINK W52P IP DECT PHONE 20-BD5392-00
©2013 YEALINK PAGE 17 OF 54
4.2 Subscriber Level Configuration Parameters
This section identifies the device-specific parameters, including registration and
authentication. These settings must be unique across devices to be matched with the
settings for a BroadWorks subscriber.
Provisioning a subscriber to register with BroadWorks allows calls to terminate to the
subscriber’s line. Registration requires that a unique address of record (AoR) is
provisioned on BroadWorks and the phone; provisioning an AoR on BroadWorks consists
of setting the line/port parameter to a unique value within the Application Server cluster.
Step Command Purpose
Subscriber parameters for the <MACADDRESS>.cfg
Step 1 Enable line 1 to be used.
Example:
account.1.enable = 1
Enable a line of the W52P IP
DECT Phone to be used.
Step 2 Configure display name for a
line.
Example:
account.1.display_name = Joe
For the line, configure the name to
be displayed on the device.
Step 3 Set Register User ID for a line.
Example:
account.1.user_name = 2405551111
The register user ID must
correspond with the line/port
setting on BroadWorks.
Step 4 Enable SIP Authentication for a
line.
Example:
account.1.auth_name = 2405551111
account.1.password = 123456
If the Authentication service is
configured on BroadWorks, these
parameters must be configured to
match the BroadWorks settings.
Step 5 Configure Network Phonebook.
xsi.host = xsp1.iop1.broad
works.net
xsi.user = [email protected].
broadworks.net
xsi.password = yealink
This configures the phone to use
the BroadWorks Xsi interface to
retrieve the group phone directory.
Host: This is the identity of the
BroadWorks Xsp server/cluster
address and relevant xsi-actions
parameters.
User: This is the BroadWorks
user’s login name.
Password: This is the BroadWorks
user’s login password.

BROADSOFT PARTNER CONFIGURATION GUIDE – YEALINK W52P IP DECT PHONE 20-BD5392-00
©2013 YEALINK PAGE 18 OF 54
5 Device Management
The BroadWorks Device Management feature provides the capability to automate
generation of device configuration files to support mass deployment of devices. This
section identifies the device management capabilities supported by the Yealink W52P IP
DECT Phone and the configuration steps required. For Device Management configuration
details not covered here, refer to the BroadWorks Device Management Configuration
Guide [2].
The basic steps to integrate a device with Device Management are as follows:
1) Create device template files for the device with the appropriate BroadWorks Device
Management tags.
2) Define custom and system tags and add them to the device template files. Note that
these custom and system tags must also be defined on BroadWorks.
3) Create a device profile type on BroadWorks for each device model to be integrated
with Device Management.
4) Add the device template files and other associated files to the device profile type.
5) Create a device profile instance of the device profile type and assign it to a user.
A user name and password are assigned to this device profile.
6) The end device is configured with the Device Management URL for device files, as
well as the user name/password access credentials.
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. These files can be uploaded directly to Device Management without
modification. However, the service provider also has the option to modify these template
files as required to fit their deployment needs.
The CPE kit also includes tools to help automate the integration effort. For releases after
Release 17.0, there is a Device Management import/export utility. The CPE kit contains
DTAF files that can be used to import the device type and template files.
5.1 Device Management Capabilities Supported
The Yealink W52P IP DECT Phone has completed Device Management interoperability
testing with BroadWorks using the BroadWorks Device Management Interoperability Test
Plan [5]. The results are summarized in the following table.
The BroadWorks test plan is composed of packages, each covering distinct
interoperability areas. Each package is composed of one or more test items, which in turn
are composed of one or more test cases. The test plan exercises the Device
Management interface between the device and BroadWorks with the intent to ensure
interoperability.
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:
Yes Test item is supported.
No Test item is not supported.
NA Test item is not applicable.

BROADSOFT PARTNER CONFIGURATION GUIDE – YEALINK W52P IP DECT PHONE 20-BD5392-00
©2013 YEALINK PAGE 19 OF 54
NT Test item was not tested.
Caveats or clarifications are identified in the Comments column.
Note that DUT in the following table refers to the Device Under Test,which in this case is
the Yealink W52P IP DECT Phone.
BroadWorks Device Management Interoperability Test Plan Support Table
Test Plan Package Test Plan Package Items Supported Comments
HTTP File Download HTTP Download Using Xsp IP Address Yes
HTTP Download Using Xsp FQDN Yes
HTTP Download Using Xsp Cluster FQDN Yes
HTTP Download With Double Slash Yes
HTTPS File
Download HTTPS Download Using Xsp IP Address Yes
HTTPS Download Using Xsp FQDN Yes
HTTPS Download Using Xsp Cluster FQDN Yes
File Inspection Inspect System Config File Yes
Inspect Device-Specific Config File Yes
Inspect Other Config Files Yes
Inspect Static Files Yes
Device Inspection Inspect SIP Settings Yes
Inspect Line Settings Yes
Inspect Service Settings Yes
HTTP File Upload HTTP Upload Using Xsp IP Address No
HTTP Upload Using Xsp FQDN No
HTTP Upload Using Xsp Cluster FQDN No
Call Processing
Sanity Tests Register with Authentication Yes
Call Origination Yes
Call Termination Yes
Remote Restart Yes
Shared Line Origination No
Shared Line Termination No
Shared Line Status No
Busy Lamp Field No
5.2 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].

BROADSOFT PARTNER CONFIGURATION GUIDE – YEALINK W52P IP DECT PHONE 20-BD5392-00
©2013 YEALINK PAGE 20 OF 54
5.2.1 Configure BroadWorks Tags
The template files in Device Management use tags to represent the data stored on
BroadWorks. When a configuration changes for a user, Device Management parses the
template files and replaces the Device Management tags with the associated data stored
on BroadWorks. There are default tags defined in the Device Management software and
there are custom tags that the service provider can create/define via the web portal for use
by Device Management. There are two types of custom tags that can be defined:
system-default tags are common to all phones on the system; device-type-specific tags
are common to 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.
5.2.1.1 Create System Default Tags
Go to System →Resources →Device Management Tag Sets and select the System
Default tag set. Add the system default tags in the following table if they do not already
exist.
Tag Name Valid Settings Description
%SNTP_SERVER_1% IP address/FQDN NTP server address
%SNTP_SERVER_2% IP address/FQDN NTP server address alternate
%DNS_SERVER_1% IP address DNS server address
%DNS_SERVER_2% IP address DNS server address alternate
%SBC_ADDRESS% IP address/FQDN SBC SIP address
%SBC_PORT% Port SBC SIP port
%USE_SBC_BOOLEAN% 0/1 Use SBC: 1=yes, 0=no