languageThis article has been translated in other language.
Rainbow Cloud Telephony Backend
Main fixes
- Hang up
It could happen that an incoming call was hung up by the caller, the call kept ringing on all extensions.
The cancellation information took too much time in spreading. - Hold
Users could be randomly unable to put incoming calls on hold.
The event that managed the change of state between the client application and the cloud telephony component remained in ringing state, which prevented calls from being transferred. - Hold
Some users could not put incoming calls on hold.
This use case was due to a lack of a specific event that wrongly tagged the second call as 'simple call'. - Overflow
The overflow to a voice mail was not always working when the user called a group.
In such a case, an event was wrongly transmitted with encryption, which was refused by the voice mail. - Transfer
In some cases it was not possible to transfer an incoming call to an internal destination.
A specific codec was not supported from end to end. It's fixed by an operation in our infrastructure. - Transfer
Attendant could not transfer a call after a pickup through a supervision key.
The identifier of the caller was not following the routing.