Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info

Update repository: rel60

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

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

...

Starting from March 11, WMS 
Note

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

Warning

WMS Stable 6.05.20240306.

...

  • March 11: upgrade available for the PBXs related* to the Estonia, Finland, Denmark, Sweden, the Netherlands, India, Australia, Germany, Austria, Switzerland, Spain
  • March 12: United States, Canada, Latin America
  • March 13: the UK
  • March 14: France, Belgium
  • March 15: Italy
  • March 16 (at night): weekly auto-upgrade available for all the countries listed above 
  • March 28 (at night): monthly auto-upgrade available for all the countries

*Note: PBX is considered as "related to a certain country", based on the Wildix sales manager assigned to the Partner, and not based on the physical location of the system or the customer.

WMS Release Candidate 6.05.20240306.4 Hotfix Date: 06.03.2024

Fixes

...

Hotfix Date: 06.03.2024

Fixes

[WMS-19461] - col: fixed an issue in which after logout from Collaboration user status didn’t change to Away in some cases if Web Push was enabled

[WMS-19483] - wms: improved the logic of Company Data Storage to avoid an issue of potential data loss which could occur in some rare cases during initial feature activation 

WMS

...

Stable 6.05.20240301.1 Date: 01.03.2024

Warning

Important: This version will be available only for PBXs related to the countries according to the schedule (see above)!

Fixes

[WMS-19246] - col: fixed an issue in which Web device was unavailable in Collaboration in some cases

...

[WMS-19424] - col: fixed an issue in which it wasn’t possible to answer an incoming call in Collaboration in case of G729 codec and starting from Google Chrome version 122

WMS Stable 6.05.20240209.1 Hotfix Date: 09.02.2024

Fix

[WMS-19060] - dev: made some improvements for provisioning of WP R5 phones

WMS Stable 6.05.20240207.1 Hotfix Date: 07.02.2024

Fix

[WMS-18578] - col: fixed an issue in which agent became unavailable after hanging up a call with Sennheiser IMPACT 5000 series headset

[WMS-19228] - sys: fixed an issue in which it was impossible to provision some WP phones due to MAC addresses not in range 


WMS Stable 6.05.20240202.1 Hotfix Date: 02.02.2024

Fixes

[WMS-18990] - sys: fixed a rare issue in which there was no audio during a call after upgrade

[WMS-18994] - sys: improved the logic of clearing voicemail box of a hotel room upon check in/ out, to ensure custom statuses are also removed after checkout

WMS Stable 6.05.20240129.1 Hotfix Date: 30.01.2024

Fix

[WMS-19091] - sys: fixed an issue of high load on PBX with a big amount of call recordings after upgrade

WMS Stable 6.05.20240119.1 Date: 24.01.2024

WarningImportant: This version will be available only for PBXs related to the countries according to the schedule (see above)!



New Features

[WMS-16922] - wda: added possibility to sync user presence status from Collaboration / x-bees to Microsoft Teams  

Notes:

  • Cloud Analytics should be activated in WMS -> PBX -> Features
  • Any other calendar integrations (Google Calendar or Microsoft 365) should be deactivated, otherwise Microsoft Teams presence sync won't work

Important: If you have previously activated Microsoft Teams Presence, you need to reactivate it for 2-way presence sync

How-to:

  1. Go to WMS -> PBX -> Integrations -> Cloud integrations
  2. Click Microsoft Teams Presence
  3. Click Install
  4. Log in to your Microsoft account

Once your user status is changed in Collaboration/ x-bees, it is automatically aligned in Microsoft Teams

Documentation: teams4Wildix - integration of Microsoft Teams with Wildix PBX - Documentation

[WMS-17696] - dev: added support for new WP R5 phones (Start R5, WelcomeConsole R5, WorkForce R5, and ForcePro R5)

  • Added Wildix BLF icons on the new phones, different icons for different kinds of BLF keys (e.g. Prefix, Speed dial, DTMF, etc.)
  • Implemented support for BLF Contact center
  • Added new icons for the connected WP R5 devices in the user's list in WMS 
  • Added WP R5 phones to the device selection list 
  • Introduced AES 256 encryption for both signalling and media
  • Improved call management dialog (except for Start phone), which allows to easily switch between active calls

Documentation: Wildix VoIP Phones 5 User GuideVoIP Phones Datasheet - Start, WorkForce, ForcePro, WelcomeConsole, Vision, SuperVision 

[WMS-18658] - x-hop: added possibility to enable the logic of assigning x-hoppers headsets to users via speech-to-text, by taking the headset from the charger and pronouncing the user name  

The feature is disabled by default. To enable, add the following parameter to the /etc/systemd/system/pbx-data-engine.service.d/override.conf file:

--xhop_voice_login true

When enabled, each time the headset is placed into the charger, it gets unassigned. When a user lifts the headset from the charger:
1. The user is asked to say their name
2. The user should pronounce the name and surname
3. 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:
a) 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.
b) Alternatively, before performing the upgrade and activating the feature, unassign headsets via WMS (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 Call button first.  

Improvements

...

[WP-291] - dev: added the display of extension and user name in SNMP responses on WelcomeConsole and WP480GR3 phones, in case of enabled SNMP on the devices

WMS Stable 6.04.20240104.1 Hotfix Date: 05.01.2024

Fix

[WMS-18872] wizy: fixed an issue when it was impossible to connect to a conference on Wizyconf Station due to the lack of an authorization session on PBX

WMS Stable 6.04.20231221.1 Hotfix Date: 22.12.2023

Fix

[WMS-18817] - dev: rolled back W-AIR LifeSaver firmware from 670b1 to 650b201due to some issues found, in which:

  • Handset language settings could not be saved. 
  • After enabling No movement alarm, when there was an incoming call, the handset stopped ringing too quick, before the call was answered. 
  • Man down alarm was not triggered in some cases, when No movement alarm was enabled and pre-alarm delay was set to a value different from 0.

WMS Stable 6.04.20231220.3 Date: 21.12.2023

Improvements


[WMS-18549] - col: made updates to ensure smooth work of Collaboration conferences when Google Chrome ends support of third-party cookies  

[WMS-18552] - col: in the view of Google Chrome upcoming plans to end support of third-party cookies, updated the logic to avoid issues with Collaboration authorization inside MS Teams  

Fixes

[WMS-18210] - wms: fixed an issue in which settings for user import from Zoho were lost after closing the Import window

[WMS-18327] - dev: fixed an issue in which some old WP phones could not download custom ring tone and caller image in some cases if custom secure port was configured on the Hardware/ Virtual PBX, after upgrade to WMS 6.04.20231020.1 

[WMS-18498] - col: fixed an issue in which Microsoft 365 Single Sign-On didn’t work if user tried to log into Collaboration inside MS Teams

[WMS-18547] - int: fixed an issue in which Hold button didn’t work in Salesforce integration in case x-bees Web was selected as an active device 

[WMS-18597] - sys: fixed an issue when after opening a new voicemail or missed call notification, another entry on the voicemail list was removed in some cases  

[WMS-18600] - wms: fixed an issue in which user preferences were ignored by a call transferred from Call group on another PBX in WMS Network (e.g. the call was not sent to the voicemail after the timeout was reached) 

[WMS-18604] - wms: fixed an issue with attended transfer via call group, in which caller name was not updated after the transfer was completed 

[WMS-18722] - col: fixed an issue in which after logging in to Collaboration with a different user and performing a call via Collaboration extension, the extension tried to perform the call from the previous user 

Limitations:

  • Collaboration Chrome extension does not currently work with Collaboration in case of a cross domain iFrame (for example in Microsoft Teams)
  • Users have to refresh Collaboration before logging in if Collaboration is used in cross domain iFrame (for example in Microsoft Teams)

WMS Stable Hotfix Date: 13.11.2023

Fix

[WMS-18199] - wms: fixed an issue in which there was no call recording attached in email notification if the selected call recording format was mp3, after upgrade to WMS 6.04.20231004.1

WMS Stable Hotfix Date: 02.11.2023

Fix

[WMS-17995] - col: fixed an issue in which PDF file of the sent fax was missing in call history after upgrade to WMS 6.03.20230828.1

WMS Stable Hotfix Date: 30.10.2023

Fix

[WMS-18292] - sys: fixed an issue when calls were not delivered to agents due to PBX engine thinking there was another call (reverted the fix of the ticket [WMS-17499] - sys: fixed an issue in which call group agents received more than one call at a time even though call waiting was disabled)

WMS Stable 6.04.20231020.1 Hotfix Date: 23.10.2023

Fixes

[WMS-18083] - sys: fixed an issue in which dynamic call group members were lost after applying backup 

...

  • Rolled back Start, WorkForce, and WelcomeConsole firmwares due to found regression with Low volume on MonoLED/ DuoLED-BT headsets

WMS Stable 6.04.20231012.1 Date: 12.10.2023

New Features

...

[WMS-18211] - sys: fixed an issue of PBX engine crash in some rare cases

WMS Stable Hotfix 6.03.20230911.4 Date: 11.09.2023 

Fix

Released the changes from [WMS-17486], [WMS-17519], [WMS-17537], that were lost after release of WMS version 6.03.20230828.1

WMS Stable Hotfix 6.03.20230828.1 Date: 28.08.2023 

Fix

[WMS-17626] - wms: fixed an issue in which fax delivery status report sent to email didn’t contain PDF file of the sent fax, after upgrade to WMS 6.03

[WMS-17838] - wms: fixed an issue in which some email notifications about received fax were delivered without an attachment after upgrade to WMS 6.03

Stable 6.03.20230816.1 Date: 16.08.2023 

Improvement

...

Stable Hotfix Date: 21.07.2023

Fix

[WMS-17598] - ios/android: fixed an issue in which Collaboration app on mobile was not ringing during an incoming call, if the call was made to a call group and the app was in a sleep state

Stable Hotfix Date: 18.07.2023

Fix

[WMS-17583] - dev: fixed an issue when it was not possible to update W-AIR headset firmware

WMS Stable Hotfix 6.03.20230712.2 Date: 13.07.2023

Fixes

[WMS-17486] - col: fixed an issue in which it was not possible to select Web as an active device in Collaboration in case of teams4Wildix (Mode 2) integration, after WMS upgrade to 6.03.20230626.2

...

WMS Stable Hotfix 6.03.20230709.1 Date: 10.07.2023

Fix

[WMS-17536] - sys: fixed an issue in which calls were not distributed to call group members after a certain period of time (WMS-13025 was reverted)

Stable 6.03.20230630.3 Date: 04 July 2023

Improvements

...

  • “Man down” alarm on W-AIR LifeSaver was not triggered if “No movement” alarm was enabled at the same time and the pre-alarm delay was set to a value other than 0.
  • W-AIR LifeSaver handset stopped ringing too fast before the incoming call was answered if “No movement” alarm was enabled and the handset was motionless for some time before the call.
  • “No movement” alarm randomly stopped working until the W-AIR LifeSaver handset was rebooted.
  • Fixed an issue in which language settings on W-AIR handsets changed to English after handset reboot, after upgrade to firmware v. 0650b2

WMS Stable 6.02.20230328.2 Hotfix Date: 30 March 2023

...

WMS Stable Hotfix Date: 24 March 2023

Fixes

[WMS-16621] - wms: fixed an issue in which “403 Forbidden” error was displayed when opening a terminal on Hardware PBX after upgrade to WMS 6.02.20230306.1

[WMS-16647] - wms: fixed an issue in which error message was displayed when adding a new ACL group on Client PBX in WMS Network

...

[WMS-16066] - dev: rolled back W-AIR firmware v. 0530b9 due to found issue in which W-AIR base stations randomly started to have huge network latency until rebooted, which resulted in such an issue as bad audio during calls

WMS Stable 6.01.20230123.2 Date: 23 January 2023

Improvements

...

WMS Stable Hotfix Date: 19 December 2022

Updated package: 6.01.20221122.1

Fix

[WMS-15910] - sys: fixed a vulnerability issue with Server-side request forgery (SSRF) via the component ZohoClient.php in the WMS

  • Note: WMS 6.01 PBXs automatically received this fix so upgrade to this version is not required.

WMS Stable Version 6.01.20221122.1 Date: 28.11.2022

Improvements

[WMS-14150] - dev: improved provisioning logic to handle upgrades of mixed W-AIR networks, which include both new (SyncPlus and Small Business R2) bases and bases that are end of life (W-AIR and Small Business R1)

[WMS-14430] - sys: added support of Basque language on WP phones   

[WMS-14797] - x-ca: added display of user presence status message in x-caracal Realtime and Agent reports 

[WMS-14867] - sys: improved security of how web passwords are stored

Note: Web password is encrypted when:

  • old backup is applied 
  • users are uploaded from CSV file
  • an old user on a running system has unencrypted password

[WMS-15545] - sys: added sound package with system sounds in Basque language 

The package is available in WMS -> Settings -> PBX -> Language and region -> Sounds packages

[WMS-15598] - sys: added a new provisioning parameter for x-hoppers headsets that allows controlling silent charging setting

Requirements:

  • W-AIR firmware starting from v 650b2
  • Activated x-hoppers

How-to:

Add the following parameter with one of the values to the [wildixair] section of /rw2/etc/provision.conf file:

WairSilentcharging = on | off | deactivated

  • on: only LED indication while charging
  • off: normal mode with LED indication and audio while charging
  • deactivated: headset is disconnected and can’t receive calls while charging

By default, silent charging is set to On. 

[WMS-15659] - wms: added a new API endpoint that allows to set presence for multiple users at once 

PUT /api/v1/pbx/presence/ - lets to set status (dnd/away), status message, and till what time the status is set for the specified extensions

Note: Available only for administrators

API documentation can be accessed via PBX and by the link:

https://www.wildix.com/wp-content/wms-api/

Fixes

[WMS-13043] - wms: added possibility to sync presence status between PBXs in WMS Network

[WMS-14649] - col: fixed an issue in which it wasn’t possible to see incoming video stream from 2N intercom during an outgoing call, after upgrade to Chrome 103

[WMS-15266] - sys: fixed an issue in which auto upgrade of Hardware PBXs could not be started due to lack of space at /var/log/ directory

[WMS-15640] - wms: fixed an issue with presence sync between PBXs in WMS Network when using Microsoft 365 calendar integration

[WMS-15673] - wms: fixed an issue in which pop-up messages were not visualised in WMS if admin used French language and the WMS network was not aligned with licences on the PBX

[WMS-15686] - sys: fixed an issue in which emails with 2FA code were not sent after PBX upgrade to WMS 6.01

[WMS-15710] - wms: fixed an issue in which SIP Proxy didn’t start after reboot, after upgrade to WMS 6.01  

New Firmware

New W-AIR firmware v 650b2 

Warning

Important: Starting from the current version, all further W-AIR firmwares will be released only for W-AIR Sync Plus and W-AIR Small Business R2 bases.

[WMS-15276] - dev: retail mode is now automatically enabled on x-hoppers headsets if x-hoppers is activated on a PBX

The following settings are pre-configured:

  • Retail Mode: On
  • Audio feedback: Voice
  • Silent charging: On
  • Silent mode: Off

Documentation: https://wildix.atlassian.net/wiki/x/QB-OAQ.

WMS Stable Version 6.01.20221019.4 Date: 24.10.2022

New Features

[WMS-12489] - wms: added possibility to choose which user data (personal data, voicemails, etc.) has to be deleted  

How-to:

  1. Go to WMS -> Users
  2. Choose user or a group of users -> click delete (-)
  3. Select data to be deleted -> click Ok

The list of options you can choose from:

  • Personal data (avatar, mobile phone, email, new passwords)
  • Voicemails
  • Voicemail greetings
  • Calls (history, records, faxes)
  • Chat history
  • Phonebooks
  • Call group member
  • Missed call manager
  • Paging group member
  • Applications (s2s, simple token)
  • Unassign devices

If you want to delete user and all their data, tick off the option “User with all data”

Notes:

  • Updated API endpoint DELETE /PBX/Colleagues/{id}/ with the new parameters
  • Removed API endpoint for multiple user deletion DELETE /PBX/Colleagues/{ids}/

API documentation can be accessed via PBX and by the link:https://www.wildix.com/wp-content/wms-api/

[WMS-13627] - sys: added possibility to set up backend for storing chat and call history (CDR) on Cloud PBXs  

How-to:

  1. Go to WMS -> Settings -> PBX -> Call and chat history
  2. Configure backend: proceed to MySQL/ MSSQL/ Sqlite tab -> enter the necessary data -> click Save
  3. Go to Settings tab -> select the configured backend in the CDR-backend field -> click Save

DocumentationWMS Settings Menu - Admin Guide.

[WMS-14162] - dev: added possibility to modify sound volume (RX and TX gain levels) on FXS r3 media gateways via custom provisioning settings

How-to:

  • Add the following parameters to [wildixfxs2] section in /rw2/etc/provision.conf file:
    RXgain= -10-10
    TXgain= -10-10
    By default, RX gain is -2 dB, TX gain is 0 dB.

DocumentationProvisioning Custom Settings

...

  • To extend the limit of voicemails (by default, the maximum number is 100), change the value of following parameter in the /etc/callweaver/voicemail-custom.conf file:
    maxmsg=200
    Where 200 is the desired number of allowed voicemails.
    Note: Maximum value is 9999

DocumentationCustom config parameters List

[WMS-14242] - sys: added an option to allow calls from users that have the same public IP address as a static trunk 

...