Zebra Workforce Connect: Voice Client Workforce Connect Voice Client 9x (versions earlier than 9.0.20306) Administration Guide for Licensing
WORKFORCE CONNECT
Voice Client
Versions Earlier than 9.0.20306
Administration Guide
for Licensing
MN-003586-05EN Rev. A
Copyright
Workforce Connect Voice Client 9.x Administration Guide for Licensing
ZEBRA and the stylized Zebra head are trademarks of Zebra Technologies Corporation, registered in
many jurisdictions worldwide. All other trademarks are the property of their respective owners. ©2019
Zebra Technologies Corporation and/or its affiliates. All rights reserved.
COPYRIGHTS & TRADEMARKS: For complete copyright and trademark information, go to
zebra.com/copyright
.
WARRANTY: For complete warranty information, go to zebra.com/warranty
END USER LICENSE AGREEMENT: For complete EULA information, go to 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 9.x Administration Guide for Licensing
Introduction
NOTE: This guide only applies to versions of WFC Voice earlier then 9.0.20306.
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 the 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 WFC Voice 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
commas.
• Manual Entry - Enter one or more comma separated activation codes.
<license_key> element and separated by
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. Depending on
your entitlement, you may receive one or two activation IDs for each premium PBX. If you were
provided two activation IDs, BOTH must be used to enable premium services.
The Zebra Licensing server generates one or more Activation IDs based on each order. By default, when
purchasing additional blocks of Entitlements after an initial purchase, new Activation IDs are received for
each order. To associate a new order with the Activation IDs from a previous order, include the Activation
IDs on your purchase order.
NOTE: WFC Voice can accept multiple Activation IDs.
WFC Voice version 9.x is licensed on a subscription basis. The expiration date displayed in WFC Voice
may include a 30 day grace period, allowing the client to continue operating 30 days past the actual
expiration date. Refer to your software entitlement email for the actual expiration date. To view the
expiration date in the WFC Voice application, which may include the grace period, go to About > View
Keys & Licenses.
NOTE: If the license for WFC Voice is renewed inside the 30 day grace period, make sure to update the
license(s) on the client. See Updating Licenses Using an MDM on page 5 or Updating Licenses Manually
on page 6.
3
Workforce Connect Voice Client 9.x Administration Guide for Licensing
Upgrading from WFC Voice Version 8.2.x
Upgrading WFC Voice version 8.2.x to version 9.x requires new Activation IDs, which are provided with the
purchase of WFC Voice version 9.x.
To update the Activation IDs in WFC Voice, use one of the following methods:
• Replace the 8.2.x Activation IDs with the 9.x Activation IDs in the XML configuration file. See Activation
Using an MDM on page 4.
• Enter the new Activation IDs in the activation screen. See Activation Using Manual Entry on page 5.
NOTE: It is not necessary to delete 8.2.x licenses before upgrading to 9.x.
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 (optional).
When
license_source is not defined, WFC Voice uses the default license source. Do not change the
license_source parameter unless instructed to by Zebra Support.
The following example shows
Voice XML configuration file. The default
<Profile>
...
<license_source>https://zebra-licensing.flexnetoperations.com/flexnet/deviceservices</lic
ense_source>
<license_key>xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx,
yyyy-yyyy-yyyy-yyyy-yyyy-yyyy-yyyy-yyyy, additional activation ids</license_key>
NOTE: Add "-uat" after "zebra-licensing" in the license source, when licensing within the development
environment.
license_key and license_source configuration parameters in the WFC
license_source parameter is shown.
4
Workforce Connect Voice Client 9.x Administration Guide for Licensing
Activation Using Manual Entry
When WFC Voice is initialized on the device, the user is prompted to enter the activation ID.
Figure 1 App Activation Screen
1. In the keys or features field, enter your activation code(s) separated by commas. Alternately, you may
scan in your activation codes as follows:
a. Using a tool to generate a bar/QR code (e.g. www.barcodesinc.com/generator/qr
activation code(s), separating by commas.
b. Generate the code.
c. While in the WFC Voice activation screen, scan in the code. It will populate directly into the
keys/features field.
2. Touch to left of Register App and in the device alias field, enter a name to identify the device on
the license source (optional).
3. Touch Register App.
NOTE: When licensing within the development environment, follow the steps below to switch to the UAT,
before selecting Register App::
a. Click on the arrows to expand the parameters,
b. Long press on the license source field,
c. Add "-uat" after "zebra-licensing".
Updating Licenses Using an MDM
), enter in your
To update all WFC Voice licenses using an MDM, send the wfc.voice.ACTION_UPDATE_CONFIG start
activity intent with the
Example command:
adb shell am start -a wfc.voice.ACTION_UPDATE_CONFIG --es license_key
1234-1234-1234-1234-1234-1234-1234
license_key parameter.
5
Loading...