Rainbow Cloud Telephony Backend
Note: The fixes may only apply to issues specific to one or a few trunks.
Main fixes
-
Call cuts
Several use cases where calls were disconnected after a few seconds had been raised, such as transferred call, incoming call to the Welcome service, incoming call during closed hours, lack of ringbacktone after the welcome prompt was played.
The root cause was the use of the Early Media telephonic feature for which renegotiation of codec could fail. -
Group calls
Sometimes, users of a group could not answer an incoming call because the "answer" button was greyed.
The event to release the previous calls was not always emitted to the group members. -
Voice prompts
Change voice prompt language to 'Portuguese' in Equipment information page led to the following error 'Resource not found.
Up to this version, only Brazilian Portuguese voice prompts were downloadable, not the Portuguese ones. -
Call recording
In a hunt group were call recording was enabled there was no ringtone after greeting was played.
An information was missing to enable the ringtone. -
Record
Recording could fail when an incoming call went through an Automated attendant.
The scenarios with recording announcements and pre-announcements is now supported. -
Analytics
The number of calls displayed on the administration page was lower than the number indicated in the group's call logs.
Some CDR were un processed. -
Audio
Forwarding incoming calls to a call center or when leaving a voice message, the call was not heard or cuts off.
A wrongly reject command was sent for these cases. -
Audio
In certain specific cases, users could not hear any sound during calls through a Welcome service and handled by a group, until they put the call on hold and resumed it.
The issue was due to a bad management of codec filtering. -
One-way audio
An incoming call answered on softphone through the Welcome service got one-way audio.
There was exchanges of data at different frequencies between the trunk and Rainbow. -
Incoming call
In specific cases, incoming call could be disconnected when the user put it in hold, altought user remaining connected.
Data in the contact header information needed to identify the correspondant were not accurate. -
Custom voice prompts
Custom voice prompts were not always played for an incoming call on Welcome service in different scenarios.
The voice prompts were not correctely uploaded. -
Supervision
Users were unable to do anything with a call after it was intercepted using a supervision key and transferred back to them.
An event managed by the service controlling calls in network flow was wrongly rejected. -
Voice message
It happened that there were no beep announcing that the users could leave a voice message.
The issue was due to an erroneous message unable to activate the right action.