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.
Add information on configuring multiple PBXs, WiFi Preferred, importing contacts.
2
ChangeDateDescription
-04 Rev A3/2018Add information on TCP/UDP port usage.
-05 Rev A5/2019Updating features for most recent release of the client.
-06 Rev A7/2019Updates to custom ringtone and audio prompt file formats. Update to Home Screen
Dashboard section.
-07 Rev A6/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.
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
•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.
12
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
.
13
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.
14
Configuring the Client
Press and hold WF Connect icon
Drag icon to the Home screen
Figure 1 Apps Screen
2.Drag the WF Connect Icon to the Home screen.
Figure 2 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.
15
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 3 Home Screen
•Touch on the WF Connect icon on the Apps screen.
Figure 4 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 169.
Activate Using an Activation Key
To activate the WFC Voice Client:
16
Configuring the Client
Toggle Button
Clear All Fields
1.Open the WFC Voice Client.
Figure 5 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 6 About Screen
5.Touch OK.
17
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 38.
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 14.
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.
18
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 7 WFC Voice Client Menu
2.Touch Settings.
Figure 8 Enter Password Screen
3.Enter the settings password. The default password is: zamboni.
4.Touch Connection Parameters.
Figure 9 Connection Parameters
19
Configuring the Client
User ID
Password
Server Address
PBX Type
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 43.
6.Touch the PBX Type field and select Asterisk.
7.Enter the User ID.
8.Enter the Password.
9.Enter the Address of the PBX server.
Figure 10 Enter Parameters
NOTE: For information on optional configuration settings, see XML Tags on page 144.
10. Touch the back button three times to return to the WFC Voice Client home screen.
Figure 11 Confirmation Message
A confirmation that the Configuration has been saved to WFConnect.xml displays.
20
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 38.
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 14.
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
21
Configuring the PBX
Introduction
This chapter describes the steps you need to take to configure the PBX.
You will perform the following steps to configure the Asterisk:
•Enable Supported Audio Codecs
•Enable TCP As Signaling Transport Protocol
•Adding an Extension
•Check the configuration of the mobile device.
Enable Supported Audio Codecs
To enable supported Audio Codecs:
1.Login to Asterisk PBX as administrator.
2.Select Settings > Asterisk SIP Settings.
IMPORTANT: Client supported Audio Codecs are G.711 u-Law, G.711 A-Law, G.722, GSM, and G.729.
22
Figure 12 Audio Codecs Screen
3.Click Submit.
Configuring the PBX
Enable TCP As Signaling Transport Protocol
To enable TCP as signaling transport protocol:
1.Go to the Command Line Interface (CLI) and enter the following:
2.Click Submit. The Add Extension screen will appear.
3.Enter the user extension, display name and password.
Figure 14 Add Extension Screen
4.Click Submit. Additional device options appear.
5.Enable TCP or UDP as transport protocol.
24
Figure 15 Device Options Screen
Configuring the PBX
In order to register WFC with Asterisk, the admin/user needs to configure the application with the UserID and
password that has been configured at the voice gateway. Also, unless the application receives the Asterisk’s IP
address during the DHCP DORA exchange, the admin/user needs to add the voice gateway as “server address” in
the WFC Voice Settings.
25
Check Device Settings
At the device there are only 3 fields the administrator must set:
•User ID
•Password
•Server Address.
Figure 16 Device Settings
Configuring the PBX
26
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.
27
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 system identifies each mobile device by a unique user ID and password. The user’s credentials are mapped to
a specific feature set in the PBX. This requires that the user credentials are loaded into the WFC Voice Client XML
and passed to the PBX at registration time.
Dynamic Configuration
28
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:
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.