How to set up Voice Authentication for x-hoppers
This guide explains how to configure voice authentication for assigning x-hoppers headsets to users.
Created: June 2024
Updated: December 2024
Permalink: https://x-hoppers.atlassian.net/wiki/x/AwAU
Introduction
x-hoppers allows you to configure the logic of assigning headsets to users via:
Simple user sign in (dial-by-name), so that staff can take the headset from the charger, pronounce their names and automatically get assigned to the headset
Voice authentication (pre-saved voice footprint), when the system compares the voice of the user with user voices (voice footprints) previously saved in the system and in case of a match, allows authentication, which eliminates the risk of user logging in under a different name
Requirements
x-hoppers system on WMS 6.07 and higher
Simple user sign in: SalesFloorHopper and higher
Voice authentication: SalesFloorHopper + AI and higher
Configuration
Simple user sign in authentication
By default, the feature is disabled. To enable it:
Add the parameter --xhop_voice_login true to the /etc/systemd/system/pbx-data-engine.service.d/override.conf file. The parameter should be added to the line "ExecStart=/usr/sbin/pbx_data_engine.py --daemon -cr" (-cr is used in case of recording in-store conversations):
vi /etc/systemd/system/pbx-data-engine.service.d/override.conf [Service] ExecStart= ExecStart=/usr/sbin/pbx_data_engine.py --daemon -cr --xhop_voice_login true
Optionally, you can enable simple user sign in for users of specific Departments only. For this, add “department” value after --xhop_voice_login and indicate the list of departments in the environment variable XHOP_VOICE_AUTH_DEPS_LIST separated by comma:
vi /etc/systemd/system/pbx-data-engine.service.d/override.conf [Service] ExecStart= ExecStart=/usr/sbin/pbx_data_engine.py --daemon -cr --xhop_voice_login department Environment='XHOP_VOICE_AUTH_DEPS_LIST=Sales,Support'
Make sure to reload systemd and restart the service to apply the changes:
systemctl daemon-reload systemctl restart pbx-data-engine
Note: Reloading systemd is required each time you make any changes to the /etc/systemd/system/pbx-data-engine.service.d/override.conf file.
When enabled, each time the headset is placed into the charger, user gets unassigned and gets Service license type in the system. When a user lifts the headset from the charger:
The user is asked to say their name
The user should pronounce the name and surname
The system looks for the user and assigns the headset to the user
Important: For the feature to start working on the headsets, follow one of the following procedures:
After enabling the feature, when using the headsets for the first time, users need to lift the headsets from the charger -> place into the charger -> lift from the charger again
Alternatively, before performing the upgrade and activating the feature, unassign headsets via x-hoppers admin (Devices -> choose device and click Assign to user -> in the Extension field, choose “unknown”). Then, when users lift the headsets from the charger, they need to press the Push-to-talk button first
Voice footprint authentication
When this feature is enabled, during user voice authentication the system compares the voice of the user with user voices previously saved in the system and in case of a match, allows authentication.
To enable the feature, follow the instructions below:
Download the following Dialplan and upload it on your PBX in the tab Dialplan rules:
Add the following variable to x-hoppers admin -> Dialplan -> General Settings -> Set dialplan variables field and click Save:
Once enabled, upon lifting the headset, users are prompted to say the phrase “with x-hoppers, my voice is my password“ to access broadcasts. If the voice authentication attempt fails, they are prompted to provide their extension and name. In case voice footprint is missing, users are suggested to record it. There are 3 attempts with 3 retries each to record the footprint. The system matches the pronunciation with user records and assigns the headset. Each time the headset is placed into the charger, it gets unassigned and gets Service license type.
Configure virtual users
It is possible to configure dummy (virtual) users for assigning a headset in case a user could not be verified by voice after 3 attempts. To set a list of dummy users for assigning a headset in case of voice authentication failure:
Create the file with the following name:
In this file, add the list of dummy user extensions, for example:
When dummy users are configured, and a user fails to complete voice authentication, the headset gets automatically assigned to an available dummy user.
Customization
It is possible to customize prompts pronounced during voice authentication. For this, add the following variable(s) to x-hoppers admin -> Dialplan -> General Settings -> Set dialplan variables field:
To set your custom prompt instead of the default voice footprint message “After the beep please say with x-hoppers: my voice is my password“:
To set a custom prompt instead of “Please say your first and last name to use the device“. For example, as long as it is possible to login via extension number, you can change the prompt to “Say your extension”:
To skip the playback message “Please hold to use the device, or say cancel to search again“:
By default, the value is yes.
To set a custom x-hoppers message instead of the default “Thank you”, pronounced at the end of voice authentication, when a user needs to wait till the headset joins the conference:
By default, during voice authentication, a message with information about battery level of x-hoppers headsets is played to users. To customize the default message “Battery level is. Make sure the headset is charged”:
Where "%s" stands for battery level and can be used to pronounce the battery level information in the needed place.
To disable battery level announcement: