| 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 |
...
| Note |
|---|
Note: Automatic upgrades are performed from the repository used for manual upgrade. Weekly automatic upgrade is enabled by default. |
...
WMS Release Candidate 6.05.20240119.1 Date: 24.01.2024
| Warning |
|---|
Important: 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:
- Go to WMS -> PBX -> Integrations -> Cloud integrations
- Click Microsoft Teams Presence
- Click Install
- 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-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
[WMS-17660] - sys: made updates to ensure more accurate and complete data in the MOS (the Mean Opinion Score) column in Cloud Analytics (CDR-View2.0)
[WMS-18076] - wms: added possibility to export and import timetables
How-to:
- To export a timetable, go to WMS -> Dialplan -> Timetable / Switch, choose the timetable(s) you want to export and click Export.
- To import a timetable, click Import -> choose the file with the timetable and load it. In case the imported timetable has the same name as the existing one, the existing timetable is overwritten with the imported timetable.
[WMS-18225] - wms: added a new API endpoint that provides possibility to download recordings in case of using Cloud storage New API endpoint:
GET /pbx/recordings/
The API endpoint returns the list of recordings, in the descending order from the newest to oldest.
Note:
- Available for root admin only.
- In case of WMS Network, the API endpoint returns recordings across the entire WMS Network, rather than a specific PBX.
API documentation can be accessed via PBX and by the link:
https://www.wildix.com/wp-content/wms-api/
[WMS-18237] - wms: made improvements to the WMS -> PBX -> Integrations section by renaming the tab Calendars / x-bees into Cloud integrations
[WMS-18328] - sys: updated the logic so that Company data storage is activated by default for Cloud PBXs
- With the update, all backups and recordings are automatically uploaded to data storage. Local copies of call recordings are available on the local disk of PBX for 7 days.
- For detailed information about Company Data Storage Procedure, please refer to the following documentation: Company Data Storage Flow
[WMS-18357] - dev: moved all devices’ firmwares from PBX to CDN (content distribution network), which allows to free up space on the PBX
When the PBX gets a firmware, local cache is created. If there are multiple devices of the same model, the firmware is downloaded only once.
[WMS-18373] - col: added notification about CDR-View going end of life on December 31 2024 and prompting to use the new version, CDR-View 2.0, which is displayed when opening CDR-View or refreshing the page
[WMS-18396] - wms: added possibility to remove user avatar when deleting user data
How-to:
- Go to WMS -> Users
- Choose user or a group of users and click Delete (-)
- Select Remove user avatar and click Delete
[WMS-18545] - wms: added possibility to use SFTP for scheduled backups
How-to:
- Go to WMS -> Tool and utilities -> Backup system -> Scheduled backups tab
- In the Protocol field, choose SFTP
- Complete the necessary fields and click Save
Note: Support for backups to FTP will be removed by January 01, 2025. Customers using FTP need to reconfigure the settings using SFTP by the mentioned date.
[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
[WMS-18814] - dev: increased the number of DECT handsets that can be connected to a single W-AIR Network to 500 handsets
Fixes
[WMS-17127] - sys: fixed an issue of high CPU usage by tproxyd service in some cases
[WMS-17874] - sys: fixed an issue when user presence status could not be changed due to a duplicate entry found for the same user in PBX engine
[WMS-18015] - wms: added a new parameter that allows to avoid an issue in which there was no media after answering a call on some latest iOS versions, in case the phone was locked and it was an API call by an external CRM, or a call from Collaboration with Any selected as a device
How-to:
Add the following parameter to /rw2/etc/env.custom.ini file:
ORIGINATE_VIA_ANY_DEVICE_TRANSFER=false
[WMS-18039] - wms: fixed an issue in which Bellcore SFK Caller ID type was not saved correctly in FXO settings in WMS (Caller ID type is available for FXO gateways pre 2020)
[WMS-18236] - wms: fixed an issue in which it was not possible to update a user by exporting CSV, editing the CSV file and importing the CSV again with the updated user data, after upgrade to WMS 6
[WMS-18282] - wms: fixed an issue in which changes of preferences for multiple users who were Call group members led to incorrect presence status in Call groups
[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-18333] - sys: fixed an issue where the user status didn't change to offline after logging out from Collaboration connected in a remote desktop environment
[WMS-18348] - sys: fixed an issue when a call group agent received more than one call at a time even though call waiting was disabled
[WMS-18387] - wms: fixed an issue in which there was no record of a call in CDR database with MySQL as backend if the name of the caller/ callee contained a character like č
[WMS-18403] - dev: fixed an issue with setting custom secure port on a remote Hardware / Virtual PBX with HTTP protocol used (parameter HTTPForceUse set to “yes”), which could lead to such issues as failure to download firmware on Wildix devices, access history and phonebooks
[WMS-18455] - sys: fixed an issue in which it was impossible to delete calls from Collaboration history in case of a PBX with MSSQL as backend
[WMS-18492] - x-ca: fixed an issue in which x-caracal interface was not displayed after initial x-caracal activation
[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-18531] - wms: fixed an issue when incoming calls from a third party trunk, that were forwarded to CLASSOUND via Dialplan, failed if the trunk didn't normalize the dialled number
[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-18565] - wda: fixed an issue in which Service tag was missing for conversations created after performing an outgoing call from x-bees to an external number
[WMS-18566] - sys: fixed a rare issue in which a recording was sent to a wrong email in some cases after upgrade to WMS 6.03.20230630.3
[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-18609] - wms: fixed an issue in which Trunk function key in Collaboration and WMS incorrectly displayed ports of gateways with more than one trunk
Note: Also, updated names of the ports displayed in Trunk function key, so that they correspond to the names used on Trunks page in WMS
[WMS-18777] - wms: fixed an issue in which the header indicated in WMS-> System -> FAX/SMS server -> Standard SMS header was not added to SMS text message if mail2sms was used, after upgrade to WMS 6
[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-18883] - sys: fixed an issue in which some unread voicemails were lost in case missed call notification was present in the same voicemail box
New Firmwares
New Firmwares: WelcomeConsole firmware v. 68.145.2.78, Start firmware v 150.145.2.22, WP480GR3 firmware 63.145.10.42
[WP-189] - dev: added possibility to disable Web GUI on WelcomeConsole phones after provisioning
How-to:
- Add the following parameter to the [wildixp2] section of /rw2/etc/provision.conf file:
WebLoginActive = no
By default, Web GUI is enabled.
[WP-262] - dev: fixed an issue of a distorted audio during a call with an agent using WelcomeConsole and EPOS Sennheiser headset with the latest firmware
[WP-269] - dev: fixed an issue in which on some EPOS Sennheiser headsets connected to WelcomeConsole it was impossible to change volume during a call
[WP-270] - dev: fixed an issue in which it wasn’t possible to pick up a second incoming call with multi-function button on DuoLED-BT headset with firmware 0x59EE, if the headset was connected to WelcomeConsole
[WP-271] - dev: fixed an issue with calls being terminated on Start phones due to launched DHCP renewal process
[WP-288] - dev: improved security on WelcomeConsole and Start phones by disabling TLS 1.0 and TLS 1.1
TLS 1.2 is enabled by default
[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:
- Go to WMS -> Users
- Choose user or a group of users -> click delete (-)
- 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:
- Go to WMS -> Settings -> PBX -> Call and chat history
- Configure backend: proceed to MySQL/ MSSQL/ Sqlite tab -> enter the necessary data -> click Save
- Go to Settings tab -> select the configured backend in the CDR-backend field -> click Save
Documentation: WMS 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.
Documentation: Provisioning 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
Documentation: Custom 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
...