/
x-hoppers Changelog (WMS 7)

x-hoppers Changelog (WMS 7)

Owned by Tatiana Bieliakova
Last updated: Feb 28, 2025 by Ksenia Babych
2 min read

x-hoppers Changelog: new features and improvements for x-hoppers, available with WMS 7.

Created: February 2025

WMS 7 changelog: https://wildix.atlassian.net/wiki/x/AYCVQ

Update repository: rel70beta

Permalink: https://x-hoppers.atlassian.net/wiki/x/AwD-CQ

x-hoppers Date: 27.02.2025

Note: The changes are available in WMS Beta 7.01.20250227.1.

New Feature

[WMS-19775] - x-hop: added the logic to automatically play messages that were sent to x-hoppers users in one-on-one chats, through the headset when user is in the broadcast 

Requirements:

How-to:

  • When there is a direct message and in case user is in the broadcast, the message is automatically played in the headset. The audio starts with: “Message from {sender’s name}”. After playing the message, the user is prompted to use Voice bot to reply to the message.

Current limitations:

  • Messages that were played via x-hoppers headset are not marked as seen in x-hoppers chat.

  • In case broadcast is on hold, the private message stays in queue max. 30 min until user returns to the broadcast. 

x-hoppers Date: 25.02.2025

Note: The changes are available in WMS Beta 7.01.20250221.3.

Fix

[WMS-22486] - x-hop: fixed an issue in which x-hoppers headset was removed from the broadcast in about 10 minutes after being registered to another Base Station  

x-hoppers Date: 20.02.2025

Note: The changes are available in WMS Beta 7.01.20250219.1.

New Feature

[WMS-21972] - sys: extended x-hoppers Smart Notifications API with possibility to play a private message to a user connected to the broadcast 

  • For private messages, include the relevant user’s extension in the extension value of the API endpoint.

  • In case there is a public message announced in the broadcast, the private message is played to the user after the current public message finishes. The consequent public messages continue to be played in the broadcast while the user listens to the private message.

  • In case the user is not in the broadcast (e.g. has an incoming call, muted the broadcast or is using AI assistant), the private message is played when the user returns to the broadcast.

API documentation: PBX API | Wildix Developer Docs  

Improvements

[WMS-20693] - xhop: improved the logic of Push-to-talk feature, so that it is enabled by default on PBX with x-hoppers license 

  • With the update, it is no longer needed to modify the override.conf file to enable the feature.

Documentation will be updated soon: https://x-hoppers.atlassian.net/wiki/x/AYAx    

[WMS-22441] - x-hop: improved voice authentication by adding possibility to allow guest users to sign into x-hoppers headset 

Note: For the feature to work, virtual users should be configured (see details in the “Configure virtual users” section of the guide How to set up Voice Authentication for x-hoppers) 

How-to:

  • Add the following variable to WMS -> Dialplan -> General Settings -> Set dialplan variables field:
    XHOPPERS_VA_GENERIC_USER_ACCESS_KEYPHRASE=<custom word/phrase>
    Where “custom word/phrase” is the word /phrase that a guest user should pronounce to be logged into x-hoppers headset.

  • Once the system detects the word/ phrase, the user hears the default audio prompt "Guest login key phrase recognised" and is automatically logged in as a virtual user. 

If you wish to change the default audio prompt to a custom one, add the following variable to WMS -> Dialplan -> General Settings -> Set dialplan variables 
XHOPPERS_VA_GENERIC_USER_ACCESS_PROMPT=your custom prompt

Documentation will be updated soon: How to set up Voice Authentication for x-hoppers  

Related content