What is the BETA program
Reminder (LOI extract):
"the Beta program allows delivering early versions to a set of selected companies. This particularly aims at allowing partners to discover evolutions in advance an get better prepared to roll-out by their end-customers, and for ALE to collect feedback during this beta phase. It is therefore mainly targeted at partners, who are “permanent” beta users, and may exceptionally be allocated to End-customer Beta Testers in case early delivery of some specific evolutions is a critical business need."
How to subscribe to the BETA program
- As a Business Partner make your request per email to support@openrainbow.com
- Add [BETA REQUEST] in the title
- Following information are needed:
- Your company name as defined in Rainbow.
- Name, e-mail address and role in the company of the person who will sign the letter of intent (LOI)
- Email addresses of iOS users who will need access to the Beta version
- Email addresses of Android users who will need access to the Beta version
- The person indicated to sign the LOI will receive a signature request by email through Docusign.
- Once the document has been signed, we allocate the Beta licenses to the company.
Note: by default, the Beta program entitles you to 5 Beta user licenses.
What we expect from you
Note: you can consult the article Current Beta Program to know which version and feature are currently available for the Beta program.
- Feedback about the Features/Versions
- in our dedicated community.
- by replying to the surveys that we send to you.
- Reporting issues
- if a malfunction is identified.
- a regression of a feature working with the production version.
Support Process
Open a support ticket
- send an email to support@openrainbow.com or open directly a ticket on MyPortal
- Title should contain [BETA]
- on MyPortal, select the version "Beta" in the Rainbow version field
Troubleshooting
A few reminders about log recovery :
- The easiest way for the end user to recovery the Rainbow client logs is to use the Report a problem feature.
- For Rainbow client logs consult the dedicated article.
- In addition to Rainbow client logs, for web client the Browser log can be very helpful.
- For WebRTC gateway logs (mpcollect --all) and SIP traces (mpndump on) consult the dedicated article.
Report a malfunction/bug :
If the issue is reproduced provide use a step by step description to reproduced the problem. Please feel free to add screenshots or videos to help us understand the problem.
In case of issues about calls do not forget to give us all details about the users configuration:
- PBX type/version
- Device (Deskphone, REX, Anydevice)
- WebRTC gateway version
- Routing setting (Computer mode/Office Phone)
- Exact date and time of the call.
All information about the caller and called party
- email of the Rainbow account
- caller number / called number
- destination type, internal/external, mobile/ land line
In addition to this information please provide all involved Rainbow client logs and the WebRTC gateway logs in case of VoIP calls (Computer mode).