/
WMS Beta Changelog rel70beta

WMS Beta Changelog rel70beta

Update repository: rel70beta

In case of automatic upgrade, make sure to specify the current repository.

Other changelogs: https://www.wildix.com/new-releases-and-updates/

Link for sharing: https://wildix.atlassian.net/wiki/x/AYCVQ

Note: Upgrade to WMS 7 is currently limited. The criteria of limited availability: only Partners who have in-house x-bees or sold at least one x-bees or x-hoppers are eligible for upgrade. 

Requirements:

  • Min. supported version from which upgrade is possible: WMS 6.09.20250121.1

Note: CDR-View is no longer available in WMS 7.

Its functionality is substituted by Cloud Analytics (CDR-View 2.0) in Collaboration and CDR-View 2.0 Liveboard in x-bees.

Check out documentation for more details: Cloud Analytics (CDR-View 2.0) in CollaborationCDR-View in x-bees

Important: In WMS 7, the option to allow TLS 1.0, TLS 1.1 in is no longer available. This means a number of old devices are not supported after upgrade to WMS 7. See the list of devices below:

  • W02FXS r1/ r2, W04FXS r1/ r2, W24FXS r1/ r2
  • W04FXO r1/ r2
  • WP400, WP410 r1, WP480 r1/ r2, WP490 r1/ r2
  • WP500, WP600
  • WP600A, WP600ACG

API admin user authentication:

It is recommended to use PHP HTTP client library for S2S authentication: https://github.com/Wildix/s2s-client-php

API documentation: https://<pbx_host>/api/v1/doc/#section/Authentication

Note: Automatic upgrades are performed from the repository used for manual upgrade. Weekly automatic upgrade is enabled by default. 

WMS Beta 7.01.20250312.1 Date: 14.03.2025

Fix

[WMS-22787] - x-hop: fixed an issue with voice authentication and failed attempts to record voice footprint, in which audio prompts notifying about the reason of failure (e.g. too noisy environment or not enough speech) were not played 

WMS Beta 7.01.20250307.1 Date: 11.03.2025

Improvement

[WMS-22677] - sys: updated TURN server logic, so that local IP addresses are included in the TURN server’s allowed list, to avoid a rare issue when there was no media during a call in Collaboration on Hardware / Virtual PBX after update to WMS 6.08.20241029.2 

Fixes

[WMS-22544] - col: fixed a rare no audio issue during some calls in Collaboration on Virtual PBX after update to WMS 6.08 

[WMS-22648] - x-hop: fixed an issue in which Talk time in x-hoppers analytics report could be slightly higher than the actual talk time in some cases 

[WMS-22728] - col: fixed an unexpected call drop issue after opening Collaboration Web Phone settings 

[WMS-22747] - col: fixed an issue where Collaboration Web Phone could not be used due to an invalid token, preventing users from making and receiving calls 

[WMS-22753] - col: fixed an issue when it was impossible to open CDR-View after upgrade to WMS 6.10 

WMS Beta 7.01.20250228.1 Date: 28.02.2025

Fix

[WMS-22595] - sys: fixed an issue on Hardware/ Virtual PBXs, in which Diagnostics Hub autotrace files filled up internal disk space causing memory issue after upgrade to WMS 6.09.20250107.2 Note: With this update, old autotrace data will be deleted.

Also, made an improvement so that when creating Diagnostics Hub reports, there is now a notification informing if the report was created successfully.

WMS Beta 7.01.20250227.1 Date: 27.02.2025

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:

  • Smart Notifications set up on the PBX
  • Voice Bot, to allow shop assistants to reply via the headset

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.

Improvement

[WMS-20727] - col: updated the logic so that Echo Cancellation in Collaboration is disabled automatically when Wildix MonoLED/ DuoLED, MonoLED-BT/ DuoLED-BT headsets are used

Fix

[WMS-22451] - x-ca: fixed an issue of incorrect Session Time in Agent Availability report in x-caracal, in case agents were members of multiple call groups  

WMS Beta 7.01.20250221.3 Date: 25.02.2025

Improvement

[WMS-22437] - dev: released W-AIR firmware v.750b101 (Base stations), v. 750b100 (handsets and headsets) which include some fixes and improvements:

  • Increased W-AIR headsets battery life, extending talk time from 7 hours to 13 hours
  • Fixed an issue in which W-AIR headsets continued to blink green when fully charged
  • Resolved an issue in which W-AIR Base Sync Plus didn’t accept passwords in some cases (e.g. if the password had 2 sequential characters)
  • Fixed an issue when DND and Call Forward indications were not displayed on the handset display after upgrade to firmware v. 730b100
  • Fixed an occasional issue in which it wasn’t possible to access Central Directory on handsets registered to some Base stations unless the Base station was rebooted (additional fix)

Note: Also, disabled automatic update of W-AIR devices on PBXs with x-hoppers license, adding the logic of a separate update of W-AIR devices used in x-hoppers systems.

Fixes

[WMS-21744] - wms: fixed an issue in case of using Collaboration Native app within Citrix as a web phone, in which audio settings were set to default after logging out and logging back in to Citrix Note: For the fix to be applied, after the upgrade users need to go to Collaboration Settings -> Web Phone -> choose the necessary device for Speakers / Ringing / Microphone options and click Save.

[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  

WMS Beta 7.01.20250219.1 Date: 20.02.2025

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: https://docs.wildix.com/api-reference/rest/wms/pbx/#/operations/addSmartNotification 


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-22349] - wms: removed the option to allow TLS 1.0, TLS 1.1 in WMS -> PBX -> Security settings 

Note: The following devices will no longer be supported after the upgrade:

  • W02FXS r1/ r2, W04FXS r1/ r2, W24FXS r1/ r2
  • W04FXO r1/ r2
  • WP400, WP410 r1, WP480 r1/ r2, WP490 r1/ r2
  • WP500, WP600
  • WP600A, WP600ACG

[WMS-22351] - col: removed the link to old CDR-View from the More options menu in Collaboration   

[WMS-22387] - col: made UI/UX improvements by adding notifications in case of network problems during a call so that user is informed of the issue   

[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 https://x-hoppers.atlassian.net/wiki/x/AwAU

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: https://x-hoppers.atlassian.net/wiki/x/AwAU 


Fix

[WMS-17445] - sys: fixed an issue in which Text-to-speech failed if the input text contained more than 800 characters