Release notes for 2025-06-06

Rainbow Cloud Telephony Backend

Main fixes

• Analytics
  An error message prevent an administrator to show selected Groups in the Communication page.
  The role of the admin was mistakenly considered as not having the right to access this data.
• Analytics
  The export of the audio analysis statistics didn't work.
  The feature has been enhanced and allows now to export more than 1000 entries without impacting the web client performances. 
• Analytics
  HUB CloudPBX configuration tabs were no more available in the dashboard.
  A side effect of new roles introduction led to this inconsistency.
• csv
  Some partners couldn't import devices by using the csv file.
  The mass provisioning for devices didn't filter correctly the data.
• Dect base station
  A secondary base station was not fully displayed in the administration page.
  A bad information was returned to this page. It's fixed.
• Myriad S device
  Creation of a Myriad S device or viewing devices in the communication page could generate an error 500.
  Synchronization with some new data was not automatically done.
• M5 devices
  Outgoing calls were no longer possible from a M5 device.
  It has been fixed.
• Ringback tone
  Bad ring back tones could be played in specific countries.
  The right ones are now available in these companies.

Rainbow Hybrid Telephony Backend

Main fixes

• Azure AD
  Indirect Reseller administrators couldn't perform the synchronization between Azure AD and Rainbow.
  The authorization was not well managed for an Indirect Reseller when acting at the End Customer level. 
• Supervised calls
  iPhones got notifications of supervised calls although the 'notification of supervised calls' parameter was disabled.
  The setting was treated with a wrong variable.

Rainbow Hybrid & Hub Backend

Main fixes

• Call display
  When joining a webinar, the user got an unexpected call from a bubble "" on his iPhone.
  Information provided by the webinar was badly transferred from a backend component.
• Channels
  Some posts were missing in channels when user had a look at the global page of the channels.
  It was a regression due to a development around the support of the future ability of adding comments to channels.
• csv
  Sometimes a mass provisioning csv file could not be imported, with an error "Invalid record length".
  Specific characters were blocking the import. They are now taken as other characters.
• Recording
  Recording of webinar could sometimes be produced without audio.
  When record was made with 'sharing' option only, the application did not consider the 'audio+video' media type. Every record in webinar takes now audio & video into account.