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 A2/2017Initial release.
-02 Rev A6/2017Update features supported in Basic CME and Premium CME.
-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 Hunt Group 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.
-08 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.
Configuring the PBX ..................................................................................................................... 192
Configuring the Workforce Connect Voice Client .......................................................................... 194
Using Hunt Groups ....................................................................................................................... 195
Join Group ............................................................................................................................... 195
Unjoin Group ........................................................................................................................... 197
10
About This Guide
Introduction
This manual describes how to install, configure and use Workforce Connect Voice Client on an Cisco CME
network.
NOTE: Screens and windows pictured in this guide are samples and can differ from actual screens.
Chapter Descriptions
Topics covered in this guide are as follows:
•Configuring the Client, describes the steps you need to take prior to beginning to configure the device.
•Configuring the PBX, describes the steps you need to take to configure Cisco CME.
•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.
•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.
•Network Ports and Protocols, provides an overview of the ports and protocols the WFC Voice Client uses
on supported Zebra devices.
•Hunt Groups, describes how to configure the Hunt Groups feature.
11
PBX Integration Statement
Cisco CME configuration references contained within this document is based on Cisco CME version 9.1. Generally
Cisco configuration elements are maintained in subsequent releases, however cannot be guaranteed. Reader is
advised to consult Cisco CME configuration guide for releases above 9.1 and use in conjunction with this
documentation.
NOTE: Workforce Connect Voice Client requires a minimum Cisco CME version of 9.1.
Notational Conventions
The followingconventions are used in this document:
•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
About This Guide
•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 Workforce Connect Voice Client.
For the latest version of this guide and all guides, go to: www.zebra.com/support
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
.
12
About This Guide
•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.
13
Configuring the PBX
Introduction
This chapter describes the steps you need to take to configure Cisco CME.
You will perform the following steps to configure Cisco CME:
•Verify that the CME PBX software is at version of 9.1 or above.
Assemble the following information before you begin to configure the Cisco CME PBX and the mobile device:
•The type of phone that is being emulated by each mobile device.
•The radio MAC address of each mobile device.
•The extension number that is assigned to each mobile device.
Open the Cisco CME Command Line Interface
1.Open the Cisco CME command line interface by establishing one of the following connections:
•Telnet
•SSH
•Console session.
2.Login using your credentials. (You must have Admin rights to perform this action.)
3.Enter Enable Mode and issue the "config t" command.
14
Configuring the PBX
IMPORTANT: If you do not have Administrative rights, contact the Support help Desk at: 1.800.653.5350.
Add Directory Numbers
To add Directory Numbers on the CME:
Figure 1 Add Directory Number - CLI
Issue the following commands on the CLI:
config t
Enter configuration commands, one per line. End with CNTL/Z.
voice register dn 25
number 1111
Add New Phone
Figure 2 Add New Phone - CLI
15
Configuring the PBX
Add New Phone for Basic CME
Issue the following commands on the CLI:
config t
Enter configuration commands, one per line. End with CNTL/Z.
voice register pool 25
id mac AAA1.BBB1.CCC1
number 1 dn 25
username XXXX password XXXX
NOTE: Basic CME does not include advanced WFC Voice Client features. For information on features available
in Basic CME and Premium CME, see Using the Client on page 123.
Add New Phone for Premium CME
Issue the following commands on the CLI:
config t
Enter configuration commands, one per line. End with CNTL/Z.
voice register pool 25
id mac AAA1.BBB1.CCC1
type 8865
number 1 dn 25
username XXXX password XXXX
Commit Changes
To commit any DN and Pool changes on the CME:
Figure 3 Commit Changes - CLI
Issue the following commands on the CLI:
config t
Enter configuration commands, one per line. End with CNTL/Z.
(config)#voice register global
(config-register-global)#no create profile (not mandatory but recommended)
(config-register-global)#create profile
16
Configuring the PBX
Assign Multiple Lines per Device
Many features can be configured on the WFCVC by configuring them on the CME.
Assign various lines per device (up to 6 lines per device by referring to the DNs in the pool configuration using the
number X dn X command.
Figure 4 Assign Multiple Lines
Customizing Line Labels and Caller ID
Many features can be configured on the WFCVC by configuring them on the CME.
Modifying the Label and the Name in the DN configurations modifies the message next to the Line Number and the
Name that is presented to the call target when the device initiates a call from a specific line.
17
Figure 5 Line Label and Caller ID
Device A Home
Screen
Device B Incoming Call screen
when device A initiates a call from
line 1113
Configuring the PBX
Customize the WFCVC Status Bar Message
Option A: The Status Bar Reflects the Pool Description
The Status Bar message will vary according to the configuration of the Pool Description and the Line's Label.
Figure 6 Status Bar Reflects the Pool Description
18
Configuring the PBX
Option B: The Status Bar Reflects the Line Label
The Status Bar message will vary according to the configuration of the Pool Description and the Line's Label.
Figure 7 Status Bar Reflects the Line Label
Option C: The Status Bar Reflects the Line Number
The Status Bar message will vary according to the configuration of the Pool Description and the Line's Label.
Figure 8 Status Bar Reflects the Line Number
19
Configuring the PBX
Pushing Buttons from CME
In order to push buttons to the WFCVC, create a template with the desired buttons, and apply the template to the
device configuration.
Figure 9 Pushing Buttons from CME
The DHCP server provides network configuration parameters directly to DHCP clients. DHCP relay passes DHCP
requests received on one interface to an external DHCP server located behind a different interface.
Cisco IP Phones download their configuration from a TFTP server. When a Cisco IP Phone starts, if it does not
have both the IP address and TFTP server IP address preconfigured, it sends a request with option 150 to the
DHCP server to obtain this information. A maximum of two TFTP servers can be identified using option 150.
For more information on configuring the CME, review the Cisco Best Practices Guide. If you need assistance,
contact Zebra Support at: www.zebra.com/support
.
20
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
.
21
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.
22
Configuring the Client
Press and hold WF Connect icon
Drag icon to the Home screen
Figure 10 Apps Screen
2.Drag the WF Connect Icon to the Home screen.
Figure 11 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.
23
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 12 Home Screen
•Touch on the WF Connect icon on the Apps screen.
Figure 13 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 190.
Activate Using an Activation Key
To activate the WFC Voice Client:
24
Configuring the Client
Toggle Button
Clear All Fields
1.Open the WFC Voice Client.
Figure 14 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 15 About Screen
5.Touch OK.
25
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 41.
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 22.
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.
26
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 16 WFC Voice Client Menu
2.Touch Settings.
Figure 17 Enter Password Screen
3.Enter the settings password. The default password is: zamboni.
4.Touch Connection Parameters.
Figure 18 Connection Parameters
27
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 46.
6.Touch the PBX Type field and select Basic CME or Premium CME.
7.Enter SIP ID (Basic CME only).
8.Enter the MAC Address. See Device Identification on page 31 for more information on MAC addresses.
9.Enter the Address of the PBX server.
Figure 19 Enter Parameters
NOTE: For information on optional configuration settings, see XML Tags on page 163.
10. Touch the back button three times to return to the WFC Voice Client home screen.
Figure 20 Confirmation Message
A confirmation that the Configuration has been saved to WFConnect.xml displays.
28
Configuring the Client
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
including licensing information, as key and value pairs. For detailed information on the XML configuration file, see
Settings on page 41.
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.
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 22.
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
29
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.
30
Loading...
+ 168 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.