COPYRIGHTS & TRADEMARKS: For complete copyright and trademark information, go to www.zebra.com/
copyright.
WARRANTY: For complete warranty information, go to www.zebra.com/warranty.
END USER LICENSE AGREEMENT: For complete EULA information, go to www.zebra.com/eula.
Terms of Use
•Proprietary Statement
This manual contains proprietary information of Zebra Technologies Corporation and its subsidiaries
(“Zebra Technologies”). It is intended solely for the information and use of parties operating and
maintaining the equipment described herein. Such proprietary information may not be used, reproduced,
or disclosed to any other parties for any other purpose without the express, written permission of Zebra
Technologies.
•Product Improvements
Continuous improvement of products is a policy of Zebra Technologies. All specifications and designs are
subject to change without notice.
•Liability Disclaimer
Zebra Technologies takes steps to ensure that its published Engineering specifications and manuals are
correct; however, errors do occur. Zebra Technologies reserves the right to correct any such errors and
disclaims liability resulting therefrom.
•Limitation of Liability
In no event shall Zebra Technologies or anyone else involved in the creation, production, or delivery of the
accompanying product (including hardware and software) be liable for any damages whatsoever
(including, without limitation, consequential damages including loss of business profits, business
interruption, or loss of business information) arising out of the use of, the results of use of, or inability to
use such product, even if Zebra Technologies has been advised of the possibility of such damages. Some
jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so the above
limitation or exclusion may not apply to you.
Revision History
Changes to the original guide are listed below:
ChangeDateDescription
-01 Rev A1/2017Initial release.
-02 Rev A7/2017Update to Voice Client 8.2.x.
-03 Rev A9/2017Update licensing information.
-04 Rev A12/2017Add information on configuring multiple PBXs, WiFi Preferred, importing contacts.
2
ChangeDateDescription
-05 Rev A3/2018Add information on Cisco Services feature.
Add information on TCP/UDP port usage.
-06 Rev A5/2019Updating features for most recent release of the client.
-07 Rev A7/2019Updates to custom ringtone and audio prompt file formats. Update to Home Screen
Dashboard section.
-08EN Rev A5/2020Ringtone option added to main menu. Sign out and reload are now separate options
in main menu. When selecting ringtone from SD card, option should read Custom
Ringtones.
IP Phone Services URL (SURL) ................................................................................................... 209
Installing IIS Web Services ..................................................................................................... 210
Creating IP Phone Services XML Files ................................................................................... 211
Example of Main Menu XML File ...................................................................................... 212
Example of Directory Entry XML Files .............................................................................. 213
Enabling the Cisco IP Phone Service ..................................................................................... 217
Using IP Phone Services in the WFC Voice Client ................................................................. 218
10
About This Guide
Introduction
This manual describes how to install, configure and use Workforce Connect Voice Client on a Cisco CUCM
network.
NOTE: Screens and windows pictured in this guide are samples and can differ from actual screens.
PBX Integration Statement
Cisco CUCM configuration references contained within this document is based on Cisco CUCM version 8.6 and
above. Generally Cisco configuration elements are maintained in subsequent releases, however this cannot be
guaranteed. The reader is advised to consult Cisco CUCM configuration guide for releases above 8.6 and use in
conjunction with this documentation.
NOTE: Workforce Connect Voice Client requires a minimum Cisco CUCM version of 8.6.
Chapter Descriptions
Topics covered in this guide are as follows:
•Configuring Basic CUCM, describes the steps you need to take to configure basic Cisco CUCM.
•Configuring Premium CUCM, describes the steps you need to take to configure premium Cisco CUCM.
•Configuring the Client, describes the steps you need to take prior to beginning to configure the device.
•Dynamic Configuration, describes the procedures to dynamically configure the WFC client using an XML
variable file.
•Settings, provides detailed information on configuring settings.
•Logging, describes the process used to capture and collect WFC Voice Client log files and Fusion log files.
•Headless Mode and WFCVoice Service, describes the procedures to configure WFC Voice client as a
background service.
•Using the Client, explains how to use the functions and features of the WFC client.
•Button Actions, includes a table listing the XML tags used to define a button action.
11
•XML Tags, includes a table listing all XML tags used in the Workforce Connect Voice Client configuration
file and where they are valid.
•XML Example - Profile, provides an XML example for the Profile section.
•XML Example - Footer, provides an XML example for the Footer section.
•XML Example - Dashboard, provides an XML example for the Dashboard section.
•XML Example - Call Buttons, provides an XML example for the In-Call Buttons section.
•Directory Button Configuration, describes the process used to configure the Directory button.
•Configuring a Proxy Server, explains how to configure a proxy server.
•Unsupported Features, provides a list of features not supported by Cisco CUCM.
•Network Ports and Protocols, provides an overview of the ports and protocols the WFC Voice Client uses
on supported Zebra devices.
•Services Configuration, provides an overview on configuring Cisco services for the WFC Voice Client.
Notational Conventions
The following conventions are used in this document:
About This Guide
•Bold text is used to highlight the following:
•Dialog box, window and screen names
•Drop-down list and list box names
•Check box and radio button names
•Icons on a screen
•Key names on a keypad
•Button names on a screen.
•Bullets (•) indicate:
•Action items
•Lists of alternatives
•Lists of required steps that are not necessarily sequential.
•Sequential lists (e.g., those that describe step-by-step procedures) appear as numbered lists.
Related Documents and Software
The following documents provide more information about the WFC Voice Client.
For the latest version of this guide and all guides, go to: www.zebra.com/support
.
12
Service Information
If you have a problem with your equipment, contact Zebra Global Customer Support for your region. Contact
information is available at: www.zebra.com/support
When contacting support, please have the following information available:
•Serial number of the unit
•Model number or product name
•Software type and version number.
Zebra responds to calls by email, telephone or fax within the time limits set forth in support agreements.
If your problem cannot be solved by Zebra Customer Support, you may need to return your equipment for servicing
and will be given specific directions. Zebra is not responsible for any damages incurred during shipment if the
approved shipping container is not used. Shipping the units improperly can possibly void the warranty.
If you purchased your Zebra business product from a Zebra business partner, contact that business partner for
support.
About This Guide
.
13
Configuring Basic CUCM
Introduction
This section contains general instructions to configure Basic CUCM.
NOTE: Basic CUCM allows configuration of one phone line with a maximum of two calls per line. For more
information on features available in Basic CUCM, see Using the Client on page 133.
Perform the following steps to configure Cisco Basic CUCM:
•Create SIP Security Profile
•Create End User
•Create Phone Endpoint
•Assign DN to Endpoint
•Configure Workforce Connect Voice Client.
Create SIP Security Profile
To create an optional SIP security profile with digest authentication:
NOTE: If digest authentication is not required, skip to Create End User on page 16.
1.Select System > Security > Phone Security Profile.
14
Figure 1 System Menu
Configuring Basic CUCM
2.Scroll to the bottom of the list and select Third-party SIP Device Basic - Standard SIP Non-Secure Profile.
4.Change the name of the profile to Third-party SIP Device Basic - Digest Required.
5.Select the checkbox next to Enable Digest Authentication to enable.
6.Select Save.
Create End User
To create an End User:
1.Select User Management > End User.
Figure 3 User Management Menu
2.Select Add New.
3.Enter the following:
16
Configuring Basic CUCM
•User ID
•Password
•Confirm Password
•PIN
•Confirm PIN
•Last Name
•First Name
•Telephone Number
•Department
•User Locale
•Digest Credentials
•Confirm Digest Credentials.
Figure 4 End User Configuration Screen
4.Scroll to the bottom of the screen.
5.Select Save.
17
Create Phone Endpoint
To map the End User to the Phone Endpoint:
1.Select Device > Phone.
Figure 5 Device Menu
2.Select Add New.
Configuring Basic CUCM
Figure 6 Find and List Phones Screen
18
Configuring Basic CUCM
3.Select Phone Type Third Party SIP (Basic).
Figure 7 Add New Phone Screen
19
Configuring Basic CUCM
4.For Device Information, complete fields as needed.
Figure 8 Phone Configuration Screen - Device Information
5.For Protocol Specific Information, enter information from Create SIP Security Profile on page 14.
Figure 9 Phone Configuration Screen - Protocol Specific Information
6.Select Save.
7.Select Apply Config.
20
Configuring Basic CUCM
Assign Directory Number to Endpoint
To assign a new Directory Number (DN) to an endpoint:
1.Select Add a new DN.
Figure 10 Phone Configuration Screen - Add a new DN
2.For Directory Number Information, complete fields as needed.
3.For Directory Number Settings, complete fields as needed.
21
Configuring Basic CUCM
Figure 11 Directory Number Configuration Screen
4.Scroll to the bottom of the screen.
5.Select Save.
Configure Workforce Connect Voice Client
To configure the WFC Voice Client, see Configure Workforce Connect Voice Client on page 35.
22
Configuring Premium
CUCM
Introduction
This section contains general instructions to configure Premium CUCM.
Perform the following steps to configure Cisco Premium CUCM:
•Create End User
•Create Phone Endpoint
•Assign DN to Endpoint
•Configure Workforce Connect Voice Client.
Create End User
To create an End User:
1.Select User Management > End User.
Figure 12 User Management Menu
2.Select Add New.
3.Enter the following:
•User ID
•Password
•Confirm Password
•PIN
23
Configuring Premium CUCM
•Confirm PIN
•Last Name
•First Name
•Telephone Number
•Department
•User Locale.
Figure 13 End User Configuration Screen
4.Scroll to the bottom of the screen.
5.Select Save.
24
Create Phone Endpoint
To map the End User to the Phone Endpoint:
1.Select Device > Phone.
Figure 14 Device Menu
2.Select Add New.
Configuring Premium CUCM
Figure 15 Find and List Phones Screen
25
Configuring Premium CUCM
3.Select Phone Type 8865.
Figure 16 Add New Phone Screen
4.For Device Information, complete fields as needed.
Figure 17 Phone Configuration Screen - Device Information
26
Configuring Premium CUCM
5.For Protocol Specific Information, complete fields as needed.
Figure 18 Phone Configuration Screen - Protocol Specific Information
6.Select Save.
7.Select Apply Config.
27
Configuring Premium CUCM
Assign Directory Number to Endpoint
To assign a new Directory Number (DN) to an endpoint:
1.Select Add a new DN.
Figure 19 Phone Configuration Screen - Add a new DN
28
Configuring Premium CUCM
2.For Directory Number Information, complete fields as needed.
3.For Directory Number Settings, complete fields as needed.
Figure 20 Directory Number Configuration Screen
4.Scroll to the bottom of the screen.
5.Select Save.
Configure Workforce Connect Voice Client
To configure the WFC Voice Client, see Configure Workforce Connect Voice Client on page 35.
29
Configuring the Client
Introduction
This chapter describes how to install, activate and configure the Workforce Connect Voice Client (WFC Voice
Client).
Determine Deployment Readiness
Assess the suitability of your Wireless Local Area Network (WLAN) for voice traffic, using the Best Practices Guide:
Deploying VoWLAN Over Aruba Wireless Networks, Deploying VoWLAN Over Cisco Wireless Networks or
Deploying VoWLAN Over WiNG5 Wireless Networks.
.
WARNING: If your WLAN is not suitable for voice traffic, WFC Voice Client will perform on a best effort basis.
Contact the Zebra Software Support Desk for more information: www.zebra.com/support.
Connect Android Wireless Device to Network
Zebra WFC Voice Client for Android includes support for the following device types:
•Enterprise Mobile devices
•Consumer Smartphone devices (evaluation only).
Connect the Android wireless device to the network. See device instructions for more information. If you need
assistance, contact the Zebra Support at: www.zebra.com/support
.
30
Configuring the Client
Install Workforce Connect Voice Client
There are two ways to install the WFC Voice Client:
•USB tether or web server - This section describes using a USB tether or web server to install the WFC
Voice Client APK manually or using ADB commands.
•Mobile Device Manager (MDM) - For information on installing the WFC Voice Client APK using an MDM,
refer to the Workforce Connect Voice Client Configuration Guide for Mobile Device Managers.
Download and Install Board Support Package (BSP) Operating System
For instructions please refer to www.zebra.com/support and login using your partner login for latest BSP and
integration instructions. If you need assistance, contact Zebra Support at: www.zebra.com/support
Download and Install Android Application Packager (APK) Client
1.From a web browser, go to the Zebra Licensing End User Portal.
To access the Zebra Licensing End User Portal, follow the instructions in the Software Entitlement email from
Zebra. Portal access requires registration at Zebra.com and authorization as a portal user by Zebra Support.
2.From the Zebra Licensing End User Portal, download the latest WFC Voice APK file.
.
Installing the APK Manually
To install the APK manually:
1.Save the APK file to the root directory of the target device using one of the following methods:
•USB tether
•Web server download (if your network supports this option).
2.On the Android device, go to the Apps list and open the file browser.
3.Navigate to the APK file.
4.Run and install the APK file.
5.Check that the WFC Voice Client is available in the Apps Screen.
The WF Connect icon should be visible in the list of available applications.
Installing the APK Using ADB Commands
To install the APK using an Android Debug Bridge (ADB) connection, open a command prompt and send the
following ADB commands to the device:
<apk_file_name> is the name of the WFC Voice APK file.
Create a Shortcut for the Workforce Connect Voice Client
To create a shortcut:
1.In the Apps Screen, press and hold on the WF Connect icon.
31
Configuring the Client
Press and hold WF Connect icon
Drag icon to the Home screen
Figure 21 Apps Screen
2.Drag the WF Connect Icon to the Home screen.
Figure 22 Home Screen
3.Drop icon on Home screen.
Open Workforce Connect Voice Client
To open the WFC Voice Client, use one of the following methods:
•Touch the WF Connect icon on the Home screen.
32
Configuring the Client
Touch on the WF Connect icon on
the Android Home Screen.
Touch on the WF Connect icon on
the Android Apps Screen.
Figure 23 Home Screen
•Touch on the WF Connect icon on the Apps screen.
Figure 24 App Screen
The App Activation screen displays.
Activate Workforce Connect Voice Client
When the WFC Voice Client starts for the first time, the App Activation screen appears. A valid license is required
for each PBX. The WFC Voice Client is activated by using an activation key, Mobile Device Manager (MDM), or
USB tether.
NOTE: When activating a device that does not have direct access to the license source, use a proxy server. See
Configuring a Proxy Server on page 201.
Activate Using an Activation Key
To activate the WFC Voice Client:
33
Configuring the Client
Toggle Button
Clear All Fields
1.Open the WFC Voice Client.
Figure 25 App Activation Screen
2.Use one of the following activation methods:
•Keys or features - Acquires licenses from the default licensing source.
In the keys or features field, enter your activation code(s) separated by commas.
NOTE: The WFC Voice Client version 8.2.729 requires a license source URL when activating using an activation
key. Refer to the Workforce Connect Voice Client 8.2.x Administration Guide for Licensing.
3.To enter a device alias, touch the toggle button and, in the device alias field, enter a name to identify the
device on the license source.
4.Touch Register App.
The About screen appears, displaying currently licensed keys and features.
Figure 26 About Screen
5.Touch OK.
34
Configuring the Client
Activate Using an MDM
Configuring the WFC Voice Client using an MDM requires a deployment package and the WFC Voice Client
configuration file. The configuration file
including licensing information, as key and value pairs. For detailed information on the XML configuration file, see
Settings on page 51.
Define the licensing information using the following XML tags:
•license_key - Contains one or more WFC Voice Client activation keys separated by commas.
•WFC Voice Client version 8.2.730 or later - Leave this field blank.
•license_alias - Identifies the device on the license source. (Optional)
MDM Deployment
During runtime, WFC Voice Client listens for wfc.voice.ACTION_UPDATE_CONFIG intent. When the WFC Voice
Client receives the intent from an MDM, the configuration file uses
configuration parameters. Use a single intent to update multiple configuration parameters by including multiple
element and value pairs.
WFConnect.xmlstores all WFC Voice client configuration parameters,
WFConnect.xml to update the WFC Voice Client
For detailed information on MDM deployment, refer to the Workforce Connect Voice Client 8.x Configuration Guide
for Mobile Device Managers.
Activate Using a USB Tether
Send theWFConnect.xmlconfiguration file to the device using a USB tether, use an Android Debug Bridge (ADB)
connection.
NOTE: It is not recommended to install the WFConnect.xml file using a USB tether because it can cause
permission issues on the device.
1.Install the WFC Voice Client APK. See Download and Install Android Application Packager (APK) Client on
page 31.
2.Copy the WFConnect.xml file in the /sdcard/WFConnect directory.
3.Open a command prompt and send the following adb command to the device:
adb shell am start -a "wfc.voice.ACTION_NEW_CONFIG" --es "profile_uri"
"/WFConnect/WFConnect.xml"
Update License
To update all WFC Voice Client licenses, refer to the Workforce Connect Voice Client 8.2.x Administration Guide
for Licensing.
Configure Workforce Connect Voice Client
The WFC Voice Client is configured using the Graphical User Interface (GUI), an MDM, or a USB Tether.
35
Configuring the Client
Enter Settings password.
NOTE: It is not recommended to install the WFConnect.xml file using a USB tether because it can cause
permission issues on the device.
Configure Using the WFC Voice Client GUI
To configure the WFC Voice Client:
1.Touch the menu button.
Figure 27 WFC Voice Client Menu
2.Touch Settings.
Figure 28 Enter Password Screen
3.Enter the settings password. The default password is: zamboni.
4.Touch Connection Parameters.
Figure 29 Connection Parameters
36
Configuring the Client
MAC Address
Server Address
PBX Type
SIP ID
5.Select a PBX configuration. The default configuration is: PBX#1 Configuration.
For information on configuring additional PBX types, see Configuring Multiple PBX Types on page 56.
6.Enter the following information:
•For Basic CUCM:
i.Touch PBX#1 Type and select Basic CUCM.
ii.In the SIP ID field, enter the Phone Directory Number.
iii. In the User ID field, enter the Digest User (optional).
iv. In the Password field, enter the Digest Password (optional).
v.Enter the Address of the PBX server.
Figure 30 Enter Basic CUCM Parameters
•For Premium CUCM:
vi. Touch PBX#1 Type and select Premium CUCM.
vii. Ensure Device Type is Cisco 8865.
viii. In the User ID field, enter the Digest User (optional).
ix. In the Password field, enter the Digest Password (optional).
x.Enter the MAC Address. See Device Identification on page 41 for more information on MAC
addresses.
xi. Enter the Address of the PBX server.
37
Configuring the Client
MAC Address
Server Address
PBX Type
SIP ID
Figure 31 Enter Premium CUCM Parameters
NOTE: The optional parameters Server Address2 and Server Address 3 are secondary addresses, used if the
primary server address is not reachable.
NOTE: For information on optional configuration settings, see XML Tags on page 174.
7.Touch the back button three times to return to the WFC Voice Client home screen.
Figure 32 Confirmation Message
A confirmation that the Configuration has been saved to WFConnect.xml displays.
Configure Using an MDM
Configuring the WFC Voice Client using an MDM requires a deployment package and the WFC Voice Client
configuration file. The configuration file
WFConnect.xmlstores all WFC Voice client configuration parameters,
38
Configuring the Client
including licensing information, as key and value pairs. For detailed information on the XML configuration file, see
Settings on page 51.
Define the licensing information using the following XML tags:
•license_key - Contains one or more WFC Voice Client activation keys separated by commas.
•WFC Voice Client version 8.2.730 or later - Leave this field blank.
•license_alias - Identifies the device on the license source. (Optional)
MDM Deployment
During runtime, WFC Voice Client listens for wfc.voice.ACTION_UPDATE_CONFIG intent. When the WFC Voice
Client receives the intent from an MDM, the configuration file uses
configuration parameters. Use a single intent to update multiple configuration parameters by including multiple
element and value pairs.
WFConnect.xml to update the WFC Voice Client
For detailed information on MDM deployment, refer to the Workforce Connect Voice Client 8.x Configuration Guide
for Mobile Device Managers.
Configure Using a USB Tether
To send theWFConnect.xmlconfiguration file to the device using a USB tether, use an Android Debug Bridge
(ADB) connection.
NOTE: It is not recommended to install the WFConnect.xml file using a USB tether because it can cause
permission issues on the device.
1.Install the WFC Voice Client APK. See Download and Install Android Application Packager (APK) Client on
page 31.
2.Copy the WFConnect.xml file to the WFConnect directory.
3.Open a command prompt and send the following ADB command to the device:
adb shell am start -a "wfc.voice.ACTION_NEW_CONFIG" --es "profile_uri"
"/WFConnect/WFConnect.xml"
To update a specific parameter in the
send an ADB command to the device in the following format:
$ adb shell am start -a wfc.voice.ACTION_UPDATE_CONFIG --es element value
For a list of possible elements and values, see XML Tags.
WFConnect.xml configuration file using ADB, open a command prompt and
39
Dynamic Configuration
Introduction
The WFC Voice Client configuration file defines the operational environment of the SIP client running on Zebra
mobile android devices. It has various elements that define the network location of the PBX and, for each device,
unique defining operational aspects affecting the user experience. Creating this file manually and distributing this
file for each device on an enterprise-wide scale introduces significant administrative overhead.
Dynamic configuration:
•Reduces the administrative effort preparing the WFC Voice Client for enterprise operation
•Provides a flexible delivery environment for the customized configuration
•Provides a method for shared device use without manually reloading the configuration
•Provides backward compatibility for existing customers.
Rather than manually creating a unique configuration for each device, this approach dynamically configures the
WFC Voice Client using an XML variable file. File delivery can be manual, by an MDM, or automatic through
existing network services.
Overview
The chapter includes:
•Providing a new XML tag that triggers dynamic configuration
•Building a multi-user variable file to build user specific configurations for the WFC Voice Client
•Re-synchronizing the WFC Voice Client with the variable file on a regular basis
•Using DHCP resources to provide auto installation for the file.
Properly configuring these elements allows the WFC Voice Client to register to the PBX.
General Device Use Cases
•A unique user is typically a supervisor or manager with a device with a more advanced feature set that is
not shared with any other user. This extension may be shared with that person’s desk phone.
•A shared device is typically for line workers or department staff that use a phone representing a functional
area, as opposed to a specific person. The device has a basic feature and may also be uniform, sharing
common elements (e.g.; button configurations) across all shared devices.
40
Device Start-Up
There are three stages of device life-cycle in the customer environment that affect how the WFC Voice Client
obtains the suitable runtime configuration:
•Initialized out of the box configuration (no configuration)
•A rebooted device previously configured
•A device reassigned to a new extension / user
Device Identification
The Cisco environment identifies each mobile handset by a unique MAC address. This can be the literal
interpretation of the mobile device MAC address, or a pseudo MAC character string.
•Literal MAC - The WFC Voice Client interrogates and insert the mobile device’s MAC address into the
WFC Voice Client configuration using an Android API. Replacing the mobile device requires the
Administrator to modify the configuration. The replacement device then has the same configuration as the
previous device.
•Pseudo MAC - The 12 character MAC string is a simple unit identifier in the PBX. The device can be
replaced without Administration intervention. The pseudo MAC does not represent the actual device MAC
address. To place a replacement device into service, set the WFC XML configuration set to match the
existing string defined in the PBX.
Dynamic Configuration
41
Profile Configuration
For the WFC Voice Client to connect to a PBX, the Profile section of the WFConnect.xml file must contain XML
tags which the device uses to:
•Establish a link to the PBX
•Identify itself to the PBX
•Retrieve the correct privileges and settings.
NOTE: Any element in the WFC Voice Client configuration file can be replaced with a variable.
Connection Attributes
The sip_userid and sip_userpass provide access to the PBX as shown in the following example:
•An IP address in the sip_remhost field to target the appropriate PBX.
•A literal or pseudo MAC address in the sip_mac field to identify the device to the PBX.
NOTE: If the MAC address is left blank the device will use the device’s physical MAC address.
When using a pseudo MAC address, the PBX device configuration remains static and the MAC address of the
device is changed to match the desired profile. The field can be populated with a 12 character hex string
resembling a MAC address.
42
Dynamic Configuration
Enabling Dynamic Configuration
The var_location tag enables dynamic configuration, and reduces the entire profile section of the
WFConnect.xml file to one line.
NOTE: File location is for demonstration purposes. The actual file location may vary.
When the WFC Voice Client initializes and parses the XML file, this tag instructs the device to retrieve the
wfcvariable.xml file from the stated location. The location can be:
•A local file on the mobile device
•Provisioned by an MDM
•Side loaded manually
Dynamic Configuration
•A URL
Wcfvariable.xml File
This file collects and organizes XML tags to populate the run-time WFConnect.xml file. Tags that are not declared
use default values. The Users tag supports and organizes multiple users. The users section is displayed as a list
on WFC Voice Client sign-in screen. When the display tag for an entry is set to true, users can select a profile from
the list.
When the display tag is set to false, the profname and prof_password tags are used. These tags are used for
user authentication when selecting a hidden profile for a dedicated user. For a shared extension, these tags are
rarely used.
Users can each be a complete and unique configuration, or they can re-use components, such as the following
buttons example.
The previous example shows the wfcvariable.xml variable file resident on the device. The variable file can also
reside on a centrally accessible server that the client can access. This provides service to all devices in the
enterprise and central administrative control.
The var_location element specifies whether the WFC Voice Client looks for the XML file on the device (a local file)
or at a network location, for example:
•Local: file:///WFConnect/wfcvariable.xml
•HTTP: http://10.5.90.10/wfcvariable.xml
•HTTPS: https://10.5.90.10/wfcvariable.xml
•TFTP: tftp://10.5.90.10/wfcvariable.xml
44
Dynamic Configuration
This provides options for deploying the configuration files. For example, an enterprise using an MDM may supply
both the Profile section and the variable file to the device and also have a central location for the variable file.
DHCP Option 150
The WFC Voice Client also supports DHCP Option 150 for retrieving the wfcvariable.xml file. If the var_location
tag is not specified in the WFConnect.xml configuration, the client attempts to download the wfcvariable.xml file
from the TFTP server specified in the Option 150 string.
Configuration Resynchronization
Synchronizing dynamic configuration ensures that devices always have the most current configuration available
from the network server or MDM. For example, when a user logs in to an extension, the configuration files may
change. The new configuration files are available when the user logs off from the current session and the WFC
service re-processes the variable files.
NOTE: The system administrator must ensure that updates are posted to the correct location available to the
Network Services – Option 60 Support in Sunrise products
MDM or Side loaded config file
WFConnect.xml file
The following example displays the standard profile and different ways the voice client is able to retrieve a Dynamic
Workforce Configuration XML file. Options include local XML and TFTP downloaded XML configuration.
Figure 35 XML Files Example
Dynamic Configuration
48
Dynamic Configuration
Testing Remote Dynamic Configuration
A test environment can use any remote server supporting web services.
To set up a lab system:
1.Ensure the server is running IIS to support Web services.
2.Establish a WFC Voice Client website.
3.Create the website and add a virtual folder.
4.Open the Default Documents properties.
Figure 36 Server Manager
5.Set the folder for the WFC Voice Client XML file repository.
49
Dynamic Configuration
Figure 37 Edit Virtual Directory
6.Test the settings to verify the system and default user can access the files.
NOTE: To test accessibility of the files, point your browser to the web site.
7.After determining access to the files, modify the XML files accordingly:
A remote server allows consistency of delivery to the remote device. Logging on and off the device synchronizes
changes to the device. Each login retrieves the existing XML file targeted for that device.
50
Settings
Introduction
This chapter contains information on settings used to configure and customize the WFC Voice Client.
The following sections provide detailed information on:
•Profile Settings - creating, editing, loading and saving a settings profile.
•Connection Parameters - configuring up to four PBX types.
•Miscellaneous Settings - locating help files and editing the settings password.
Exiting WFC Voice Client:
1.Touch the menu button, then Settings. The password dialog box appears.
2.Enter password (default: zamboni).
3.Touch Enter.
4.Touch Stop Service > Yes.
This action can also be initiated using ADB, an MDM, or a third party app. For example, in ADB you can use the
following command:
$ adb shell am broadcast -a wfc.voice.STOP_APP
Reloading WFC Voice Client:
1.Touch the menu button.
2.Touch Reload.
This action can also be initiated using ADB, an MDM, or a third party app. For example, in ADB you can use the
following command:
$ adb shell am broadcast -a wfc.voice.SIGN_OUT
51
Profile Settings
The WFC Voice Client profile is an XML file that contains all the settings for the current WFC Voice Client session.
Create Profile
Create a new profile. A new XML file is created in the WFConnect folder.
To create a new profile:
1.Touch the menu button, then Settings. The password dialog box appears.
2.Enter password (default: zamboni).
3.Touch Enter.
4.Touch the menu button, then Create new profile.
5.Touch Save current profile.
6.Enter a file name for the new profile.
7.Touch Save. The file is saved in the WFConnect folder.
8.Touch the Back button to return to the WFC Voice Client home screen.
Settings
Change Profile Name
To change the name of the current profile:
1.Touch the menu button, then Settings. The password dialog box appears.
2.Enter password (default: zamboni).
3.Touch Enter.
4.Touch Profile name.
5.Enter a file name for the new profile.
6.Touch OK. The file name in the WFConnect folder is updated.
7.Touch the Back button to return to the WFC Voice Client home screen.
Shared Profiles URI
Set the URI of shared profile located on a remote or local server.
To set the URI of a shared profile:
1.Copy the profile from the WFConnect folder using a USB tether.
2.Move the profile to a remote or local server.
Supported protocols are file, http, https, and tftp.
3.From the WFC Voice Client, touch the menu button, then Settings. The password dialog box appears.
4.Enter password (default: zamboni).
5.Touch Enter.
6.Touch Shared Profiles URI.
7.Enter the URI of the shared profile.
8.Touch OK.
9.Touch the Back button to return to the WFC Voice Client home screen.
52
Settings
Load New Profile
Load profiles previously saved to the:
•WFConnect folder
•SD Card
Loading a New Profile Using the GUI
1.Touch the menu button, then Settings. The password dialog box appears.
2.Enter password (default: zamboni).
3.Touch Enter.
4.Scroll to the bottom of the screen.
5.Touch Load new profile. The Select Profile File dialog box appears.
Figure 38 Select Profile Popup
6.Select a profile file name.
7.Touch the Back button or Refresh button to load new profile.
Loading a New Profile Using XML
<WFConnect>
<Profile>
<profname>WFConnect.xml</profname>
</Profile>
Installing the APK Using ADB Commands
To install the APK using an Android Debug Bridge (ADB) connection, open a command prompt and send the
following ADB command to the device:
$ adb shell am start -a wfc.voi ce.ACTION_NEW _CONFIG --es profile_uri < configuration_fi le>
Where
<configuration_file> is the URI of the new XML configuration file.
Save Current Profile
Using the same file name, save the current profile to replace an existing XML file.
To save an existing profile:
1.Touch the menu button, then Settings. The password dialog box appears.
2.Enter password (default: zamboni).
3.Touch Enter.
4.Scroll the bottom of the screen.
5.Touch Save current profile. The current profile name appears.
53
Settings
6.Touch Save. The file is saved in the WFConnect folder.
7.Touch the Back button to return to the WFC Voice Client home screen.
Edit a Profile Using XML
To edit a saved profile using XML, copy the new profile from the WFConnect folder using a USB tether.
54
Connection Parameters
Users can make and receive a call using any configured PBX type. This section describes how to configure up to
three additional PBX types using the WFC Voice Client GUI or WFConnect.xml file.
To configure the default PBX (PBX#1 Configuration) see Configure Workforce Connect Voice Client on page 35.
Figure 39 Connection Parameters
Settings
55
Settings
Configuring Multiple PBX Types
Set the configuration parameters for additional PBX types:
IMPORTANT: When configuring multiple PBXs, ensure the server IP address and credentials are pointing to the
correct PBX call server as indicated by the profile type. For example, the CUCM_BASIC profile must be
configured with the IP address and credentials of a CUCM call manager.
Using the GUI
1.Touch the menu button, then Settings. The
password dialog box appears.
2.Enter the password (default: zamboni).
3.Touch Enter.
4.Touch Advanced Settings > Connection
Parameters.
5.Touch PBX#2 Configuration.
6.Touch PBX#2 Type.
7.Select the PBX type that is the same as the
target PBX call server.
8.Enter the configuration information.
Refer to the Getting Started chapter of the
WFC Voice Client Administrator Guide for
the desired PBX type.
CAUTION: Changing the default audio settings may have adverse results.
Do not modify these settings unless directed to so by Zebra Technical Support.
This section provides detailed information on configuring advanced audio settings. Use the WFC Voice Client GUI
or WFConnect.xml file to customize the Profile section. Both methods are discussed with each Function
description.
To configure audio settings:
1.Touch the menu button, then Settings. The password dialog box appears.
Figure 40 WFC Voice Client Menu
Settings
2.Enter password (default: zamboni).
3.Touch Enter.
Figure 41 WFC Voice Client Settings Menu
4.Touch Advanced Settings > Audio Settings.
57
Figure 42 Advanced Settings / Audio Settings
Settings
58
Audio Codecs Priorities
Set the audio Codecs preferences.
NOTE: Only select audio Codecs available in the PBX.
Settings
Using the GUI
1.In Advanced Settings select Audio
Settings.
2.Select Audio Codecs Priorities.
3.Select the Codec preference (default order
preferred). See Table 1 for descriptions.
4.Touch Back button to return to the WFC
Voice Client home screen.
Table 1 Codecs Priorities
Field TypeDescriptionXML
G.711 u-LawWhen selected, assigns preference priority for
G.711 u-LAW Voice codec negotiations
between PBX and Client.
G.711 A-LawWhen selected, assigns preference priority for
G.711 A-Law Voice codec negotiations between
PBX and Client.
G.729When selected assigns preference priority for
G.729 Voice codec negotiations between PBX
and Client.
Using XML
<WFConnect>
<Profile>
<codec_ulaw_priority>1</codec_ulaw_p
riority>
</Profile>
...
</WFConnect>
<codec_ulaw_priority>1
</codec_ulaw_priority>
<codec_alaw_priority>2
</codec_alaw_priority>
<codec_g729_priority>3
</codec_g729_priority>
G.722When selected assigns preference priority for
G.722 Voice codec negotiations between PBX
and Client.
GSMWhen selected assigns preference priority for
GSM Voice codec negotiations between PBX
and Client.
59
<codec_g722_priority>4
</codec_g722_priority>
<codec_gsm_priority>5
</codec_gsm_priority>
Jitter Buffer
Jitter Initial Delay
Set the Jitter Buffer initial delay settings.
Settings
Using the GUI
1.In Advanced Settings select Audio Settings.
2.Slide the Jitter Initial Delay slider (default 60
msec).
3.Touch Back button to return to the WFC Voice
Client home screen.
Jitter Buffer Max Buffer Size
Set the maximum Jitter Buffer size.
Using the GUI
1.In Advanced Settings select Audio Settings.
2.Slide the Jitter Buffer Size slider (default 250
Use the GUI to configure the User Interface. Settings made in the GUI are saved to the XML file. The GUI settings
and the XML file drives the WFC Voice Client look and functionality. Alternatively edit the XML file,
WFConnect.xml, to make the same GUI settings. The saved WFConnect.xml file can be modified and use to
configure other devices.
The WFConnect.xml file must be stored on the device in the WFCconnect folder. If this file does not exist, the
application uses the default parameter values. The WFC Voice Client XML configuration file has the following
sections which must be present in the file and in the following order:
•Profile section
•Footer section
•Dashboard section
•Call buttons section.
Settings
IMPORTANT: All these sections must be present in the XML file and they must be in the order listed above.
Configuration File Sections
Profile Section
The Profile section contains all the global settings and only requires a few basic items to begin using the WFC
Voice Client on a PBX.
•SIP (Literal or Pseudo) MAC Address <sip_mac>
•SIP Remote Host (PBX Server Address) <sip_remhost>
Unless specified, the Profile section of the WFC Voice Client uses the default settings for Audio Settings, Call
Settings, Miscellaneous Settings, Logging and Optional Services (This is a suggested best practice). Use the WFC
Voice Client GUI or WFConnect.xml file to customize the Profile section. Both methods are discussed with each
Function description.
See XML Example - Profile for a profile section example.
Footer Section
The Footer section defines the buttons, or soft keys, on the WFC Voice Client home screen. The buttons are listed
in the order they appear on the screen. A maximum of six buttons can be added. The Footer always displays until
a call is initiated. While additional items can be defined in the Footer, the following items are strongly
recommended:
•History
•Redial
•Dial
•Contacts
•Voicemail.
Use the WFC Voice Client GUI or WFConnect.xml file to customize the Footer. Both methods are discussed with
each Function description.
64
Settings
NOTE: The footer area does not require a <columns> element as it is always one row of buttons.
IMPORTANT: If a footer section is not required, do not define any buttons between the <Footer> and the
</Footer> tags.
See XML Example - Footer for a footer section example.
Dashboard Section
The Home Screen Dashboard section defines the buttons in the dashboard area of the screen and their layout on
the WFC Voice Client screen. The Dashboard displays functions and features specific to the end user. A maximum
of 12 buttons can be displayed on the screen; additional buttons are accessed by scrolling up and down. Use the
WFC Voice Client GUI or WFConnect.xml file to customize the Footer. Both methods are discussed with each
Function description.
See XML Example - Dashboardfor a dashboard section example.
Call Buttons Section
The Call Buttons section defines the buttons in the call buttons area of the screen and their layout on the WFC
Voice Client screen. In-Call displays the available function and action of call buttons that can be accessed during a
call. While on a call the user may wish to perform one of the following:
•Add Call
•Home
•Hold
•Resume
•Park
•Transfer
•Conference
•Complete
•End Call.
See XML Example - Call Buttons for a call button section example.
Headless Mode
For detailed information on Headless Mode see Headless Mode and WFCVoice Service.
65
Background Logo
Icon Library
To choose a background from the icon library:
Settings
Using the GUI
1.In Advanced Settings select UI Settings >
Background Logo.
2.From the LIBRARY tab, select the new
background. A yellow box appears around
the selected background.
3.Touch the Back button to return to the WFC
Voice Client home screen.
Using XML
<WFConnect>
<Profile>
<background_logo>logo</background_lo
go>
</Profile>
...
</WFConnect>
Custom Background Configuration
The user can create a custom background. To select a custom background:
1.Connect the device to a host computer using a USB cable.
2.From the host computer, copy the icon file to the WFConnect folder on device.
Custom Background Configuration
Using the GUI
1.In Advanced Settings select UI Settings >
Background Logo.
2.From the SDCARD tab, select the new
background. A yellow box appears around
the selected background.
3.Touch the Back button to return to the WFC
Voice Client home screen.
Using XML
<WFConnect>
<Profile>
<background_logo>custom_logo.png</ba
ckground_logo>
</Profile>
...
</WFConnect>
Buttons Padding
Set the horizontal spacing between in-call buttons from 0 pixels to 50 pixels, in 10 pixel increments.
Use the GUI Design Tool to customize the Footer, Dashboard and In-Call screen from within the WFC Voice Client.
Configure each to fit the specific needs of the customer. The appearance of the WFC Voice Client is configured
using the GUI or by directly modifying the WFConnect.xml file. Details on specific XML settings and the construct
of the XML configuration file are discussed in more detail later in this guide.
To begin using the GUI Design Tool, follow the steps below to configure the Footer, Dashboard or In-Call screens:
1.Launch WFC Voice Client.
2.Touch the menu button, then Settings. The password dialog box appears.
Figure 43 WFC Voice Client Menu
3.Enter password (default: zamboni).
4.Touch Enter.
67
Figure 44 WFC Voice Client Settings Menu
5.Touch Advanced Settings > UI Settings.
Figure 45 Advanced Settings / UI Settings
Settings
6.Select Edit Dashboard, Edit Footer or Edit In-Call Button.
Using the UI Settings GUI Design Tool
The following diagram describes the buttons available for each area.
68
Figure 46 GUI Design Tool - Footer
Buttons that will be
available for use in the
selected area:
•Footer
•Dashboard
•In-Call
Touch Add to add a button.
Touch a button to edit. A yellow boarder
appears indicating the button to be
configured.
Touch Up to move the button to the
left in the list.
Touch Delete to remove selected
button.
Touch Down to move the button right in the
list.
Touch Edit to edit the button
configuration
Header Label will change based on
the selected area to configure:
•Footer Design
•Dashboard Design
•In-Call Designer
Touch 3 Columns or 4 Columns
to change the number of
columns.
Settings
The Footer and In-Call views use the layout displayed in Figure 46. The Dashboard view has an additional toggle
button in the bottom center of the screen to change the number of columns on the dashboard (3 or 4).
Figure 47 GUI Design Tool - Dashboard
69
Home Screen Dashboard
Dashboard Buttons
Footer
In-Call Dashboard Buttons (Configurable)
In-Call Footer (Not Configurable)
Figure 48 Home Screen Dashboard
Settings
In-Call Dashboard
Figure 49 In-Call Dashboard
70
Settings
Button Configuration
The following sections describes each button that can be placed on the UI. Each section lists the Designer Tool
procedure and corresponding XML configuration.
Call
Call is the ability to make a telephone call to a specific number or location using a prefix. The administrator
identifies a target by its extension (phone number) and enters this into the Value field along with the prefix. The
user can then use this function to initiate a call to the preset destination.
Figure 50 Sample Button Edit Screen
71
Configuring the Call Button
Settings
Using the GUI
1.In UI Settings select Edit Footer, Edit
Dashboard or Edit In-Call > Add.
2.Select the new button. A yellow box appears
around the selected button.
3.Touch Edit.
4.Select the check box next to Confirm On
Click to enable this (the default is Disabled).
5.Touch Action and select CALL from the
Select Action menu.
6.If the dialed number has a prefix, in the Value
field, enter the prefix number.
7.In the Title field, enter Call.
8.In the Description field, enter a short
description of the button function.
9.Touch Icon and select an icon from the
Select Icon menu. See Icons on page 100.
10. Touch BG to set the background color. See
Button Background Color on page 103.
11. Touch FG to set the foreground text color.
See Button Text Color on page 104.
12. Touch the Back button to return to the WFC
Voice Client home screen.
Using XML
<Footer> or <Dashboard> or <Call Buttons>
...
<Button>
<title>Call</title>
<action>CALL</action>
<value>9</value>
<enabled>true</enabled>
<confirm>false</confirm>
<description>Make a
Dial is the ability to dial a specified extension or number to initiate a telephone call. A caller identifies a target by its
extension (phone number) and originates the call.
Configuring the Dial Button
Using the GUI
1.In Advanced Settings select UI Settings >
Edit Footer, Edit Dashboard or Edit In-Call
> Add.
2.Select the new button. A yellow box appears
around the selected button.
3.Touch Edit.
4.Select the check box next to Confirm On
Click to enable this (the default is Disabled).
5.Touch Action and select DIAL from the
Select Action menu.
6.In the Title field, enter Dial.
7.In the Description field, enter a short
description of the button function.
8.Touch Icon and select an icon from the
Select Icon menu. See Icons on page 100.
9.Touch BG to set the background color. See
Button Background Color on page 103.
10. Touch FG to set the foreground text color.
See Button Text Color on page 104.
11. Touch the Back button to return to the WFC
Voice Client home screen.
Using XML
<Footer> or <Dashboard> or <Call Buttons>
...
<Button>
<title>Dial</title>
<action>DIAL</action>
<value></value>
<enabled>true</enabled>
<confirm>false</confirm>
<description>Dial a number or
Start Application defines a button to launch another application on the device. When the button is pressed WFC
Voice Client minimizes to run in the background and the defined application launches. For example, a button can
be placed in the Footer to open an email application.
Configuring the Start App
Using the GUI
1.In Advanced Settings select UI Settings >
Edit Footer, Edit Dashboard or Edit
In-Call > Add.
2.Select the new button. A yellow box
appears around the selected button.
3.Touch Edit.
4.Select the check box next to Confirm On
Click to enable this (the default is
Disabled).
5.Touch Action and select START_APP.
6.Touch Select App Package and select the
application from the Select App Package
menu.
7.In the Title field, enter the application
name.
8.In the Description field, enter a short
description of the button function.
9.Touch Icon and select an icon from the
Select Icon menu. See Icons on page 100.
10. Touch BG to set the background color. See
Button Background Color on page 103.
11. Touch FG to set the foreground text color.
See Button Text Color on page 104.
12. Touch the Back button to return to the
WFC Voice Client home screen.
Using XML
Opening the music application example is shown in
the following XML.
Log Marker creates a time stamp in the logs. If you experience any issues with WFC Voice Client functionality, the
time stamp focuses troubleshooting of the device to the time the issue occurred for more rapid resolution.
Configuring the Log Marker
Using the GUI
1.In Advanced Settings select UI Settings >
Edit Footer, Edit Dashboard or Edit In-Call
> Add.
2.Select the new button. A yellow box appears
around the selected button.
3.Touch Edit.
4.Select the check box next to Confirm On
Click to enable this (the default is Disabled).
5.Touch Action and select LOG_MARKER
from the Select Action menu.
6.In the Title field, enter Log Marker.
7.In the Description field, enter a short
description of the button function.
8.Touch Icon and select an icon from the
Select Icon menu. See Icons on page 100.
9.Touch BG to set the background color. See
Button Background Color on page 103.
10. Touch FG to set the foreground text color.
See Button Text Color on page 104.
11. Touch the Back button to return to the WFC
Voice Client home screen.
Using XML
<Footer> or <Dashboard> or <Call Buttons>
...
<Button>
<title>Log Marker</title>
<action>LOG_MARKER</action>
<value></value>
<enabled>true</enabled>
<confirm>false</confirm>
<description>Create time
Access the Do Not Disturb (DND) feature directly on the phone. Use a Feature Access Code (FAC) to enable or
disable this feature. Enabling DND suspends all personal calls targeted to the extension, and sends the call
immediately to the defined Coverage Path. DND also removes the extension from consideration during any
Coverage Answer Group, Simultaneous Ringing, and Hunt Group call. This feature is the PBX-based
implementation of an endpoint device Call Ignore feature.
Configuring the DND Button
Using the GUI
1.In Advanced Settings select UI Settings >
Edit Footer, Edit Dashboard or Edit In-Call
> Add.
During an active call the Add Call button can dial a preset number. If there is no number in the Value field, it opens
the dialer. The current call is placed on hold while the new call is initiated. When the new call connects, you can
Transfer, Conference, or End the second call and resume the first call.
IMPORTANT: Only available on the In-Call screen only.
Configuring the Add Call Button
Using the GUI
1.In Advanced Settings select UI Settings >
Edit In-Call > Add.
2.Select the new button. A yellow box appears
around the selected button.
3.Touch Edit.
4.Select the check box next to Confirm On
Click to enable this (the default is Disabled).
5.Touch Action and select ADD_CALL.
6.In the Title field, enter Add Call.
7.In the Description field, enter a short
description of the button function.
8.Touch Icon and select an icon from the
Select Icon menu. See Icons on page 100.
9.Touch BG to set the background color. See
Button Background Color on page 103.
10. Touch FG to set the foreground text color.
See Button Text Color on page 104.
11. Touch the Back button to return to the WFC
Voice Client home screen.
Using XML
<CallButtons>
...
<Button>
<title>Add Call</title>
<action>ADD_CALL</action>
<value></value>
<enabled>true</enabled>
<confirm>false</confirm>
<description>Add a call by
opening the dialer </description>
<bg_color>#FF001425</bg_color>
<fg_color>#FFFFFFFF</fg_color>
<icon>Default</icon>
</Button>
...
</CallButtons>
85
Settings
Home
During an active call the Home button invokes the Dashboard to provide access to Dashboard functions.
IMPORTANT: Only available on the In-Call screen.
Configuring the Home Button
Using the GUI
1.In Advanced Settings select UI Settings >
Edit In-Call > Add.
2.Select the new button. A yellow box appears
around the selected button.
3.Touch Edit.
4.Select the check box next to Confirm On
Click to enable this (the default is Disabled).
5.Touch Action and select HOME.
6.In the Title field, enter Home.
7.In the Description field, enter a short
description of the button function.
8.Touch Icon and select an icon from the
Select Icon menu. See Icons on page 100.
9.Touch BG to set the background color. See
Button Background Color on page 103.
10. Touch FG to set the foreground text color.
See Button Text Color on page 104.
11. Touch the Back button to return to the WFC
Voice Client home screen.
Using XML
<CallButtons>
...
<Button>
<title>Home</title>
<action>HOME</action>
<value></value>
<enabled>true</enabled>
<confirm>false</confirm>
<description>Return to the Home
Call Hold politely suspends an active call while you tend to other business or place an additional call using an
additional Call Appearance. During call hold, you can switch between the active and held calls at any time.
IMPORTANT: Only available on the In-Call screen.
Configuring the Hold Button
Using the GUI
1.In Advanced Settings select UI Settings >
Edit In-Call > Add.
2.Select the new button. A yellow box appears
around the selected button.
3.Touch Edit.
4.Select the check box next to Confirm On
Click to enable this (the default is Disabled).
5.Touch Action and select HOLD.
6.In the Title field, enter Hold.
7.In the Description field, enter a short
description of the button function.
8.Touch Icon and select an icon from the
Select Icon menu. See Icons on page 100.
9.Touch BG to set the background color. See
Button Background Color on page 103.
10. Touch FG to set the foreground text color.
See Button Text Color on page 104.
11. Touch the Back button to return to the WFC
Voice Client home screen.
Using XML
<CallButtons>
...
<Button>
<title>Hold</title>
<action>HOLD</action>
<value></value>
<enabled>false</enabled>
<confirm>false</confirm>
<description>Place call on
Transfer transfers an active call to a third party. While Call Forwarding must be preconfigured, Call Transfer allows
making such call exchanges in real-time with an active call.
IMPORTANT: Only available on the In-Call screen.
Configuring the Transfer Button
Using the GUI
1.In Advanced Settings select UI Settings >
Edit In-Call > Add.
2.Select the new button. A yellow box appears
around the selected button.
3.Touch Edit.
4.Select the check box next to Confirm On
Click to enable this (the default is Disabled).
5.Touch Action and select TRANSFER.
6.In the Title field, enter Transfer.
7.In the Description field, enter a short
description of the button function.
8.Touch Icon and select an icon from the
Select Icon menu. See Icons on page 100.
9.Touch BG to set the background color. See
Button Background Color on page 103.
10. Touch FG to set the foreground text color.
See Button Text Color on page 104.
11. Touch the Back button to return to the WFC
Voice Client home screen.
Using XML
<CallButtons>
...
<Button>
<title>Transfer</title>
<action>TRANSFER</action>
<value></value>
<enabled>false</enabled>
<confirm>false</confirm>
<description>Transfer a call
Conference joins two separate calls for collaboration between each party on the line at the same time. Use a
Feature Access Code (FAC) to enable or disable this feature. See System Feature Settings on page 27.
IMPORTANT: Only available on the In-Call screen.
Configuring the Conference Button
Using the GUI
1.In Advanced Settings select UI Settings >
Edit In-Call > Add.
2.Select the new button. A yellow box appears
around the selected button.
3.Touch Edit.
4.Select the check box next to Confirm On
Click to enable this (the default is Disabled).
5.Touch Action and select CONFERENCE.
6.In the Title field, select Conference.
7.In the Description field, enter a short
description of the button function.
8.Touch Icon and select an icon from the
Select Icon menu. See Icons on page 100.
9.Touch BG to set the background color. See
Button Background Color on page 103.
10. Touch FG to set the foreground text color.
See Button Text Color on page 104.
11. Touch the Back button to return to the WFC
Voice Client home screen.
Using XML
<CallButtons>
...
<Button>
<title>Conf</title>
<action>CONFERENCE</action>
<value></value>
<enabled>false</enabled>
<confirm>false</confirm>
<description>Start a conference
List buttons are configured using XML. The List button contains each sub button before the closing </Button>
element. The List button description appears at the top of the List popup dialog. The sub button description
appears as a comment under the button title, identifying which action is performed.
For example, to create a list with three custom buttons (Bedding, Electronics and Toys):