languageThis article has been translated in other language.
Android application - version 1.161.3
Main fix
- Messages
User could get the notification 'in progress' while receive certains messages, or didn't receive any notification at all.
The issue was caused by a poor management of the network availability at the start of the app by Samsung with Android 16 and further OS versions. It has been fixed on Rainbow side. - Ringing state
Android device kept ringing and remained stuck after the call rejection from a Desktop app.
This issue happened when 2 specific parallel actions in backend occurred at the same time.
Web application - version 2.161.18
Main fixes
- Analytics
In the 'Applications' section of the Analytics, the total number of used major versions was not correct.
Right values are displayed now. - Azure
The wrong company could be displayed in front of users in search Azure results.
The issue occurred for several companies belonging to an organization. - Busy
Users could be stuck in busy after P2P calls, further calls not appearing in the call log.
Receiving incoming calls during an outgoing call could lead to a bad treatment of events and block further telephony actions. - Busylight
The Kuando Busylight stopped working after the Rainbow release 161.
The Kuando busy light has been disabled by since v161: it's now needed to enable it manually from Settings - Notifications. - Card display
Card display was not working for users with an Essential license. - Forward
There was an issue with the call forwarding in certain cases where the status was badly reflected on hybrid users.
The event broadcast to notify the forward state was sent erroneously to other users. - HDS - CCD agent
Some users could remain in 'connection in progress' even if the call was picked up already from an external agent.
A loop occurred when the CCD started negotiation to be connected, so further negotiation steps never happened. - Permissions
It happened that some users lost their profile.
A field was missing when users hadn't got a customized one. - Routines
Routine tables could disappear randomly.
It happened when a supervised user activated one of their routines. - Webinar
Switching the device, speaker could lose audio/video.
An event was misinterpreted during the switch.
