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.
i
ChangeDateDescription
-04 Rev A12/2017Add information on configuring multiple PBXs, WiFi Preferred, importing contacts.
-05 Rev A3/2018Add 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.
ii
Table of Contents
Copyright ............................................................................................................................................ i
Terms of Use ..................................................................................................................................... i
Revision History ................................................................................................................................. i
Configuring a Proxy Server ........................................................................................................... 165
Network Ports and Protocols
Network Ports and Protocols ........................................................................................................ 166
7
About This Guide
Introduction
This manual describes how to install, configure and use Workforce Connect Voice Client on an Avaya IP Office
network.
NOTE: Screens and windows pictured in this guide are samples and can differ from actual screens.
PBX Integration Statement
Avaya IPO configuration references contained within this document is based on Avaya IP Office version 9.0.
Generally Avaya configuration elements are maintained in subsequent releases, however cannot be guaranteed.
Reader is advised to consult Avaya IP Office configuration guide for releases above 9.0 and use in conjunction with
this documentation.
NOTE: Workforce Connect Voice Client requires a minimum Avaya IP Office version 9.0.
8
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 Avaya IP Office.
•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.
About This Guide
•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.
•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.
9
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
•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.
About This Guide
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
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.
10
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
.
1
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.
2
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.
3
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 165.
Activate Using an Activation Key
To activate the WFC Voice Client:
4
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.
5
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 26.
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 2.
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.
6
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
7
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 31.
6.Touch the PBX Type field and select Avaya IP Office.
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 140.
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.
8
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 26.
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 2.
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
9
Configuring the PBX
Introduction
This chapter describes the steps you need to take to configure Avaya IP Office.
Perform the following steps to configure Avaya IP Office:
•Verify that the Avaya IP Office software is at version of 9.1 or above.
•Collect necessary information
•Add User
•Set Extension number
•Set Caller ID
•Set Supervisor Password
•Check the configuration of the mobile device.
Collect Necessary Information
Assemble the following information before you begin to configure the Avaya IP Office PBX and the mobile device:
•User ID (extension #) and Password
•Extension Number
•Supervisor Password
•Server Address
Open the Avaya IP Office Web Manager
1.Open the Avaya IP Office web interface.
2.Click Call Management.
3.Click View All.
10
Figure 12 IP Office Web Interface
Add New SIP User
To add a new SIP user, click Add User.
Figure 13 Add User Button
Configuring the PBX
IMPORTANT: If you do not have Administrative rights, contact Zebra Help Desk at: 1.800.653.5350.
Add User Credentials
Add User credentials by following these steps:
1.Enter the following items:
Name
Password
Extension.
2.Click OK.
11
Figure 14 Add User Credentials
Configuring the PBX
Setup Extension (If not already configured)
If the extension has not been previously created, AIPO opens a window that allows the administrator to create an
extension matching the number that he has just set in the user configuration.
1.Click SIP Extension to add a SIP extension.
Figure 15 Select Extension Dialog Box
2.Click OK.
12
Edit User Properties
In order for the phone to register to the PBX the administrator has to add a Supervisor password for the user.
1.Click Edit to edit the user properties. The following screen appears.
Figure 16 Edit User Settings
2.Click the Telephony tab.
Figure 17 Telephony Tab
Configuring the PBX
3.Click Supervisor Settings.
4.Enter Login Code (Supervisor Password).
Figure 18 Enter Login Code
5.Click Save.
13
Check Device Settings
At the device there are only 3 fields the administrator must set:
•User ID
•Password
•Server address.
Figure 19 Device Settings
Configuring the PBX
14
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.
15
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
16
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: