The WebRTC v3 gateway implements 2 major changes, updating the linux version (Debian 12 Bookworm) and a completely reworked user registration on the WebRTC gateway reducing the number of threads and memory consumption. These changes have already been tested internally on several versions and different topologies, but we can't test all the types of installation used by customers. We therefore need your help to confirm that this version works properly with WM brands, PC models or topologies that we couldn't cover in our tests.
How to subscribe to the Early Adopter Program
- To subscribe as a BP use following link :
I want to subscribe or open a support ticket on MyPortal or by sending a mail to support@openrainbow.com (Title should be [EA WRG3] I want to subscribe to the WebRTC gateway v3 Early Adopter Phase and please provide following information:
- Request is for (Company Name as defined in Rainbow)
- PBX ID
- Current installed WebRTC gateway version
- Installation type (PC / Virtual Machine)
- VM/PC brand/model or version
- Topology (1 PBX - 1 WebRTC gateway; shared WebRTC gateway; 1 PBX - 2 or more WebRTC gateway)
- To subscribe as an End Customer, please contact your ALE reseller to ask them to open the ticket for you.
What is new in this WebRTC gateway v3.x ?
As mentioned in the introduction the WebRTC v3 gateway implements 2 major changes, updating the linux version (Debian 12 Bookworm) and a completely reworked user registration on the WebRTC gateway reducing the number of threads and memory consumption.
Of course, we have also made a number of corrections and general improvements as:
- Fixed DTMF issue with payload type 96.
- In some cases, calls were not notified has been corrected.
- A number of robustness improvements (library updates, logs management, etc...).
How this EA program works
Selection criteria for Early Adopters
As explained we need your help to confirm that this version works properly with WM brands, PC models or topologies that we couldn't cover in our tests.
Following your request, we will examine the following elements to decide whether or not to open access to the WebRTC gateway v3 software (either via a download link or by activating the remote upgrade for this version).
- Type of installation
- Topology
- Number of users
- Usage (e.g. number of calls)
As one of the evolutions is a modification of user registration on the WebRTC gateway, we will first open up access to customers with a small number of users and then proceed in several phases in order to also address customers with a large number of users.
So don't worry if you don't get a positive response for the first phase, we'll certainly consider your application for one of the next phases.
What we expect from you
All we ask is that you install the new version and that you or your customer carry on with your day-to-day work as usual.
And in case you encounter a problem, report it to us with as much information as possible and all needed logs (see Troubleshooting chapter below).
- As a BP you can either open a ticket on MyPortal or by sending a mail to support@openrainbow.com (Title should contain [EA WRG3]).
- As an End Customer please contact your Rainbow reseller.
- And if you just have a question or a comment about this version to share with us, you can also post a message in our Early Adopter Community. Post title should then contain [EA WRG3]
Troubleshooting
A few reminders about log recovery :
- For Rainbow client logs consult the dedicated article.
- In addition to Rainbow client logs, for web client the Browser logs can be very helpful.
- Another easy way for the end user to recovery the Rainbow client logs is to use the Report a problem feature.
- For WebRTC gateway logs (mpcollect --log) and SIP traces (mpndump on) consult the dedicated article