/
WMS Stable Changelog rel70

WMS Stable Changelog rel70

Jul 03, 2025

Update repository: rel70

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/AQDjSg

Requirements:

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

Note:

  • In WMS 7, location-based multi-factor authentication for Collaboration is enabled by default. For more information, refer to the documentation Security Policy at Wildix.

Note:

  • There is also rel70lts repository, aimed to provide a long-term support upgrade path for users who need extended support cycle. For more information, check out the document WMS Versions Lifecycle and Release Schedule.

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 Collaboration, CDR-View in x-bees

Note: Starting from WMS 7.01.20250528.1 auto-upgrades are mandatory and cannot be disabled. 

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

WMS Stable 7.02.20250625.1 Date: 25.06.2025

Improvement

[WMS-23605] - wms: made some security improvements

WMS Stable 7.02.20250620.2 Date: 20.06.2025

Improvements

[WMS-23525] - wms: updated the logic so that PBX admin is notified via email before S2S, OAuth2 or Simple Token are about to expire or when a new token has been created

Email notifications are sent 7 days before a token expires; when a token has expired and when a new token was created.

[WMS-23635] - wms: extended the expiration date for S2S and OAuth2 tokens that were created before WMS 7.02.20250609.3 till September 1, 2025

Note: PBXs not running the latest version will be forced to upgrade, with schedule starting from September 1, 2025. The schedule will be shared in advance.

WMS Stable Hotfix Date: 20.06.2025

Fix

[WMS-23640] - x-ca: fixed an issue in which it was impossible to install x-caracal in WMS 7.02

WMS Stable 7.02.20250612.3 Date: 12.06.2025

Fix

[WMS-23569] - wms: fixed an issue in which the July 1, 2025 expiration date for S2S, OAuth2 and Simple Tokens was not applied 

WMS Stable 7.02.20250609.3 Date: 11.06.2025

New Feature 

[WMS-23270] - sys: added support for language, voice provider and welcome message selection in Voice Bot Dialplan application, enabling more natural-sounding bots 

To configure Voice Bot settings:

  • Go to WMS -> Dialplan -> Dialplan rules
  • Select the Dialplan procedure used for Voice Bots
  • Under Voice Bot application, configure the following:
    • Select the bot
    • Choose the desired language
    • Select a specific voice
    • Customize the welcome message

Notes:

  • For some languages, it may not be possible to select a specific voice. In such cases, the default voice is used, and the functionality still works correctly
  • For Arabic language (not available in the drop-down menu), use Set application to define the language 

[WMS-23342] - wms: implemented mandatory 2FA for root admin users to improve account protection and reduce the risk of credential-based attacks 

To authenticate, admins must obtain a one-time password (OTP). It can be obtained via:

  • WMP (access via SFPC or directly): go to Customers -> select the specific Company -> under Pbxes, click on the lock icon and copy a code
  • QR code scanning with any compatible authenticator app: go to WMS Settings -> PBX -> Security -> under Admin Two-Factor Authentication, click Show QR code -> scan the QR code using an authenticator app

Documentation: How to get access to PBX with 2FA for root admins

Improvements

[WMS-23130] - x-hop: improved the logic so that Broadcast transcription settings for x-hoppers are applied immediately, rather than within the 15-minute update interval  

[WMS-23505] - wms: disabled the ability to send backups via FTP/SFTP to improve system security  

[WMS-23539] - wms: disabled Basic Auth for root admin users to prevent unauthorized access

  • For PBXs that used Basic Auth within the past month, it will remain enabled after the upgrade
  • To enable it manually, add the following parameter to /rw2/etc/env.custom.ini file: ALLOW_BASIC_AUTH=true 

Fixes

[WMS-22881] - wms: fixed an issue in which WP 5 phones could not register on Hardware PBX due to wrong DNS server set 

[WMS-23126] - dev: fixed an issue in which it wasn’t possible to perform blind transfer to Speed dial button on WP 5 phones  

[WMS-23238] - sys: fixed an issue where triggering the hangup tool on Voice Bot did not terminate the call as expected 

[WMS-23331] - x-hop: fixed an issue with an incoming call to x-hoppers broadcast via smart notifications, in which the call was lost if a broadcast user who already had another call on hold, double-pressed the Push-to-Talk button 

[WMS-23333] - dev: fixed an issue causing incorrect ringback tone on W-AIR handsets due to missing country settings in provisioning 

[WMS-23416] - sys: fixed a rare issue of PBX engine crash 

[WMS-23421] - sys: fixed an issue of PBX engine restarts in case of Hardware/ Virtual PBX, with Cloud Analytics disabled 

[WMS-23457] - sys: fixed an issue causing increased memory consumption in PBX engine 

[WMS-23515] - wms: added expiration date to S2S, OAuth2 and Simple Tokens to provide better security 

The expiration date for all existing tokens is set to July 1, 2025. To continue using your token after this date, you need to regenerate it:

  • Go to WMS Settings -> PBX -> Integrations -> Applications
  • Select the desired token
  • Regenerate the token and set a new expiration date

WMS Stable 7.01.20250605.1 Date: 05.06.2026

Improvement

[WMS-23498] - sys: made some security improvements 

WMS Stable 7.01.20250603.1 Date: 03.06.2025

Improvement

[WMS-23477] - sys: made some security improvements 

WMS Stable 7.01.20250528.1 Date: 29.05.2025

Improvement

[WMS-23334] - wms: introduced new repository rel70lts as a long-term support upgrade path, offering a more stable and predictable release schedule for users who need extended support cycles

  • Added the drop-down menu with possibility to choose the necessary repository in WMS -> Tools and Utilities -> Upgrade -> Upgrade repository field.
  • Also, with this update, auto-upgrades are now mandatory and cannot be disabled.

Documentation: WMS Versions Lifecycle and Release Schedule

WMS Stable 7.01.20250512.1 Date: 23.05.2025

Fix

[WMS-23387] - classound: fixed an issue in which CLASSOUND received the PBX address instead of the MAC address of the device in case of a call from WP 5 phone in some rare cases

WMS Stable 7.01.20250512.1 Date: 13.05.2025

New Features

[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.

[WMS-21887] - x-hop: added the Dial by name feature for Voice Agents which allows to dial colleagues by pronouncing their name / extension when speaking with a Voice Agent

How-to:

  1. In Voice bot settings add the Transfer tool 

  2. Choose the option Directory in the Destination field

  3. In the Description field, enter instructions for the transfer, e.g. “Transfer the call if user asks. Transfer only to the users who are in the Directory”

For detailed instructions, check out the documentation How to configure Voice Agents

[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-16279] - sys: removed the 1-minute limit for voicemail audio transcriptions

  • With the update, the length of voicemails that can be transcribed is unlimited.
  • The pre-recorded part of the voicemail announcement (e.g. "Hello, welcome to the voicemail of…I am not available at the moment...") is not transcribed.

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

[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

[WMS-21685] - x-hop: added possibility to configure dynamic detection of the speaker's language for transcription, to cover cases when user may speak multiple languages in the broadcast 

How-to:

  1. Add the -tl parameter with the necessary languages 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:
    vi /etc/systemd/system/pbx-data-engine.service.d/override.conf
    [Service]
    ExecStart=
    ExecStart=/usr/sbin/pbx_data_engine.py --daemon -tl "en,it"
    Where “en,it” are the languages, which you can substitute with the preferred ones.
  2. Reload systemd and restart the service to apply the changes

Note:

  • The following languages are supported: en, en-us, it, fr, de, es, es-us, pt, nl, de-ch. It is recommended to use maximum three languages for the best recognition results.
  • In case only one language is indicated, the setting is ignored.
  • In case the language of the user indicated in WMS -> Users is not included in the language list inside the -tl parameter, language detection is not applied.
  • Only one dialect per language is allowed (e.g., “en”, cannot be set together with “en-us”). In case of setting different dialogs of the same language, the dynamic language detection is not applied.

Limitations:

  • Short phrases (e.g. which last less than 3 seconds) may not be recognized and transcribed using the user language in WMS.
  • In case of a long phrase, if the user switches to another language in the middle of the phrase, the phrase is transcribed in the first language, that was recognized at the beginning of the phrase.

[WMS-22015] - wms: improved the logic so that depending on the license type on the PBX, the invitation button in WMS -> Users page is displayed as “Invite to x-hoppers"/ “Invite to Collaboration 7"/ “Invite to x-bees” 

[WMS-22002] - x-hop: simplified the logic of creating and managing x-hoppers broadcasts for easier and more intuitive setup 

  1. Added the dedicated Dialplan application named Broadcast. Now, instead of using Conference app with Conference ID, you need to add a Broadcast application and choose the necessary broadcast.
  2. Broadcast creation will become available on Friday morning, 21.03.2025. Once the changes are available, you’ll need to:
    • Go to WMS -> Broadcasts -> Broadcast tab and check if there are the necessary broadcasts or add them
    • Go to the Dialplan and add Broadcast application to the *Wairhotline* and *wair* sections (instead of the Conference app).

To check your broadcasts or create a new one:

  1. Go to WMS -> Broadcasts -> tab Broadcast
  2. Click Add to add a broadcast and fill out the following details:
    • Broadcast name: enter name of the channel
    • PBX: select the appropriate PBX, in case there are multiple PBXs
    • Members: the list of users that need to be added to the channel
    • Transcription: enable the checkbox in case you wish to record and transcribe broadcast conversations
    • Default broadcast: enable the checkbox if you wish to make this broadcast the default one for your store
    • Avatar (optional): choose picture for the broadcast channel
    • Click Save. The dedicated group conversation is automatically created in x-hoppers.

For detailed instructions, see the updated documentation: https://x-hoppers.atlassian.net/wiki/x/AQAt

There are also some changes on the QR Code tab:

  • Added the column Broadcast with the broadcast name the quick response is linked to
  • When adding a quick response, in the Broadcast field you need to choose the broadcast that was created before (instead of entering broadcast ID manually)

Note: You also need to reconfigure / re-add QR codes, choosing the necessary broadcast name in the Broadcast field.

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

[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-22531] - x-hop: improved voice authentication accuracy by using extension recording in addition to the key phrase recording for during authentication process 

x-hoppers_auth Dialplan was updated. For more details and to get the updated Dialplan, check the documentation: https://x-hoppers.atlassian.net/wiki/x/AwAU

[WMS-22605] - sys: added possibility to transcribe calls for customers with UC licenses 

  • Transcription of calls can be enabled by adding the following variable in WMS -> Dialplan -> General settings -> Set dialplan variables: TRANSCRIBE_RECORDED_CALLS=yes
  • Transcription of calls is supported only for UC-Business and UC-Premium licenses
  • UC-Premium license includes 3 hours of transcriptions per month. UC-Business does not include any transcription hours – in this case, transcription hours included in the relevant CDS bundle will be used.

Documentation: AI+Data Boost Bundles Overview

[WMS-22640] - dev: improved the logic so that when missed call notification pop-up is disabled on WP 5 phones, the configuration is not reset after device reboot/ check sync 

[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 

[WMS-22703] - wda: added global dialplan variable which allows Dial the phone application to ignore user’s “call forward all” settings  

How-to:

  • To enable, add the following variable to WMS -> Dialplan -> General settings -> Set dialplan variables: SKIP_FORWARD_ALL=yes
  • By default, the option is disabled. When enabled, when executing Dial the phone application, the called user's settings Call forward all are ignored.

[WMS-22716] - dev: enabled SDES-SRTP by default for W-PA / W-PA 2 Public Announcer 

[WMS-22844] - sys: improved the quality of Voice AI Agents making them sound more human-like 

[WMS-22884] - wms: extended the list of fields which can be imported from Google with the fields Google Voice and Other

How-to:

  • When importing users from Google in WMS, you can add the values phoneGoogleVoice and phoneOther in the Mobile Number and Home fields correspondingly in the mapping section.

[WMS-22893] - wms: added confirmation dialog when attempting to delete W-AIR slot in WMS -> Devices -> W-AIR Devices  

[WMS-23048] - x-hop: extended smart notifications feature with possibility to deliver Call group calls to x-hoppers broadcast

[WMS-23094] - col: updated the logic so that location-based multi-factor authentication for Collaboration is enabled by default 

  • Location-based MFA requires users to confirm their IP address via email, if the IP address appears to be from an unfamiliar location

[WMS-23185] - wms: added possibility to disable access to Collaboration on WMS 7

How-to:

  1. Go to WMS -> PBX -> Features
  2. Disable the checkbox Allow Collaboration

When the checkbox is disabled and user tries to log in to Collaboration, there is a notification that Collaboration access is disabled and user is suggested to use Collaboration 7 instead.

By default, the option is enabled. 

[WMS-23196] - sys: added support for new Vodafone R6 SIP Trunk  

[XBS-5191] - xbs: added possibility to add call tags during a call in x-bees/ Collaboration 7/ x-hoppers

How-to:

  1. Click Manage tags button on the call dialog
  2. Choose the necessary tag

Also, added support for TAGS variable in Popup URL.

Tags can be set up in WMS -> PBX -> Call and chat history -> Settings -> Tags field or via Dialplan application Set -> Tags. 

Fixes

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

[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-20480] - x-ca: resolved an issue in which x-caracal call details API was not working 

[WMS-20643] - sys: fixed an issue when checking old voicemail details in which incorrect date of the incoming voicemail was announced in German language 

[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-22315] - sys: fixed an issue in which PBX engine crashed in some rare cases if transcriptions were used sys: fixed an issue in which PBX engine crashed in some rare cases if transcriptions were used

[WMS-22435] - col: fixed performance and audio issues which occurred in some cases when noise suppression was enabled

[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-22544] - col: fixed a rare no audio issue during some calls in Collaboration on Virtual PBX after update to WMS 6.08

[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-22632] - wms: fixed an issue in which trunk settings were ignored and trunk registration used UDP transport protocol even if TCP was set 

[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-22701] - сol: fixed a rare issue in which a wrong device was used instead of the selected one during the first call after logging in to Collaboration  

[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-22752] - sys: fixed visualization issue in Cloud Analytics where Voice Bot calls were incorrectly labeled as missed and outbound, and displayed the Bot ID instead of its number

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

[WMS-22779] - dev: fixed an issue in which Cancel key was not translated in some cases on WP 5 phones 

[WMS-22784] - sys: fixed an issue in which scheduled backups to SFTP stopped working after upgrade to WMS 6.10 

[WMS-22785] - wms: fixed an issue in which incomplete autotrace archive from Diagnostics Hub was sent to CDS and it wasn’t possible to open the archive

[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-22865] - wms: fixed an issue with Diagnostics Hub in which Callweaver logging was automatically restarted after PBX reboot, even if Callweaver logging was previously disabled 

[WMS-22868] - wms: allowed using a slash character (/) in SMS messages sent via the “Curl SMS send” option, which gives possibility to send clickable URLs  

[WMS-22888] - dev: fixed an issue in which missed call notification was displayed on WP phones after performing semi-attended transfer using BLF key

[WMS-22890] - dev: fixed an issue in which there was no media in the call with W-PA / W-PA 2 Public Announcer after recent upgrade 

[WMS-22897] - wms: fixed an issue in which Broadcast application in Dialplan was saved with incorrect status for Play Battery Level checkbox  

[WMS-22905] - x-ca: fixed an issue when it was impossible to open x-caracal in case of a Virtual/ Hardware PBX with a custom database set in WMS -> PBX -> Integrations -> Analytics -> x-caracal  

[WMS-22910] - sys: fixed an issue when it was impossible to login to Call groups via Collaboration on a Virtual PBX in case there wasn’t direct Internet connection and Proxy was enabled 

[WMS-22938] - wms: fixed an issue when it wasn’t possible to download some files in Diagnostics Hub 

[WMS-22943] - wms: fixed an issue where the real-time transcription button was not displayed during x-bees calls after upgrading subscription plans from Collaboration to x-bees

[WMS-22945] - x-ca: fixed an issue in which Session time in x-caracal was calculated incorrectly in some cases after upgrade to WMS 6.10.20250307.2 

[WMS-22959] - ca: fixed an issue with Agents Stats report in Cloud Analytics (CDR-View 2.0) in which external user phone number was displayed in Agents column in case of a conference call with internal agents and an external user 

[WMS-23055] - wms: fixed an issue in which PBX could not be rebooted due to an error with Diagnostics Hub script execution 

[WMS-23073] - x-ca: fixed an issue of incorrect pause time and wrapup time in x-caracal reports in some cases

[WMS-23082] - x-hop: fixed a rare issue in which headset was not added to the broadcast automatically and it couldn’t be resolved by placing the headset on the charger and picking it up again 

[WMS-23204] - sys: fixed an issue where Paging did not work due to incorrectly added Multicast addresses

[WMS-23254] - wms: fixed an issue in which it was impossible to open CDR-View 1.0 after recent update  

Firmwares

New W-AIR LifeSaver firmware v 760b200, ForcePro 5 v. 2.12.16.67, Start 5 v. 2.12.5.41, WelcomeConsole 5 v. 2.12.16.54, WorkForce 5 v. 2.12.16.62, W-AIR firmware v.750b101 (Base stations) and v. 750b100 (handsets and headsets)

[WMS-23210] - dev: fixed an issue in which W-AIR LifeSaver couldn't receive incoming calls in the idle state 

[WPR5-91] - dev: resolved an issue in which it was impossible to use MonoLED/ DuoLED headsets with WP 5 phones due to low microphone level

[WPR5-92] - dev: fixed an issue in which search by letters in Phonebook didn’t work in some languages

[WPR5-97] - dev: fixed an issue in which WP 5 Phones returned to the home screen when voicemail was played

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

  • 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.