Zebra Workforce Connect: Voice Client Workforce Connect Voice Client 8.2.x Administration Guide for Licensing

WORKFORCE CONNECT
Voice Client 8.2.x
Administration Guide
for Licensing
MN-003137-05 Rev. A
Workforce Connect Voice Client 8.2.x Administration Guide for Licensing

Copyright

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.
2
Workforce Connect Voice Client 8.2.x Administration Guide for Licensing

Introduction

The Workforce Connect Voice (WFC Voice) provides PBX features for select Zebra mobile computers. These features improve the effectiveness of communications within an organization, providing enterprise voice communications across multiple media types on unified mobile devices.

Activation ID

To use WFC Voice on your devices, the devices must be licensed. Licensing requires an activation ID(s) and a connection to a licensing server.
The activation ID is a 32-digit code which must be entered into the client via one of the following methods:
Deployment via Mobile Device Manager (MDM) - Create a WFC Voice configuration file with one or more
Activation IDs. Activation IDs are entered in the
Manual Entry - Enter one or more comma separated activation codes.
<license_key> element and separated by commas.

License Scheme

WFC Voice requires Activation IDs for the following components:
PBX Standard (e.g. CUCM-Standard, CME-Standard, AURA, IPO, Mitel, etc.) and associated software version.
One activation ID is required per standard PBX.
PBX Premium (e.g. CUCM-Premium, CME-Premium) and associated software version – OPTIONAL Entitlement.
Two activation IDs are required per premium PBX – one for the appropriate software version, and one for the device license.
The Zebra Licensing server generates an Activation ID based on each order. When purchasing additional blocks of Entitlements after an initial purchase, Activation IDs are received for each order.
Upgrading to new software releases (e.g. X.Y to X.Y+1 or X.Y to X+1.Y) requires new Activation IDs.
NOTE WFC Voice can accept multiple Activation IDs.
3
Workforce Connect Voice Client 8.2.x Administration Guide for Licensing

Activation Using an MDM

Deploying WFC Voice using an MDM requires a deployment package and an XML configuration file. The configuration file stores all WFC Voice configuration parameters as key and value pairs.

WFC Voice XML Configuration File

Two XML tags are used to define licensing information in the XML file:
license_key: Contains one or more WFC Voice activation keys.
license_source: URL of a license source server.

WFC Voice Version 8.2.729

The following example shows license_key and license_source configuration parameters in the WFC Voice XML configuration file.
NOTE In WFC Voice versions 8.2.729 the license_source parameter must be defined.
<Profile> ... <license_source>https://zebra-licensing.flexnetoperations.com/flexnet/deviceservices</license_sour
ce> <license_key>xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx, yyyy-yyyy-yyyy-yyyy-yyyy-yyyy-yyyy-yyyy,
additional activation ids</license_key>

WFC Voice Version 8.2.730 and Later

The following example shows the license_key configuration parameter in the WFC Voice XML configuration file.
NOTE In WFC Voice versions 8.2.730 and later, if the license_source parameter is not defined, WFC Voice uses
the default licensing source.
<Profile> ... <license_key>xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx, yyyy-yyyy-yyyy-yyyy-yyyy-yyyy-yyyy-yyyy,
additional activation ids</license_key> ... </Profile>
4
Workforce Connect Voice Client 8.2.x Administration Guide for Licensing

Deploying the Configuration File

Version 8.2.729
1. Push new configuration file containing thelicense_key and license_source parameter. The XML file name must be
pushed as
2. Install application using an MDM, such as AirWatch or MobiControl.
Ensure to grant all runtime permissions to the application.
3. After installation, use an MDM to:
Whitelist the application.
Example command:
adbshelldumpsysdeviceidlewhitelist+com.symbol.wfc.voice
Allow the application to display system popup notifications for incoming calls.
Example command:
appopssetcom.symbol.wfc.voiceSYSTEM_ALERT_WINDOWallow
/sdcard/WFConnect/WFConnect.xml on device.
IMPORTANT Do not send the wfc.voice.ACTION_NEW_CONFIG intent yet.
4. Reboot device or start the application.
5
Loading...
+ 11 hidden pages