[WebRTC Gateway] Early adopter OXO Connect - VoIP calling
Completed
What is the VoIP calling feature?
The VoIP calling brings new possibilities for a Rainbow user connected to a PBX. They now may call any PBX or PSTN user from their Rainbow client (on PC or Mobile). They may additionally answer calls made to their PBX number, from internal phones or from PSTN, on their Rainbow clients.
What are the pre-requisite to get the VoIP calling feature?
To enjoy the VoIP calling feature:
- Rainbow users need to be granted with either a Business or an Enterprise licenses.
- OXO Connect PBX needs:
- to run with SW version OXO Connect 300/054.001
- to be granted with an AnyDevice Terminal per targeted Rainbow user
- to be connected to Rainbow for the Telephony Services
- IP Trunk licences for the SIP trunk
- For OXO Connect you can host the Rainbow WebRTC Gateway on a standalone PC. Read the dedicated installation guide for more details.
- A Virtual Machine can also be set-up to host Rainbow WebRTC Gateway. The VM software is delivered by ALE and requires a VMWARE 6.0 or later environment. The VM has to meet the following minimum requirements that may still change:
- vCPU: 2
- CPU reservation in MHz: 4800
- vRAM: 2 GB
- vDISK: 4 GB
- vNIC: 1 GB
How to leave some feedback?
Our users’ feedback matters a lot to us as it paves the way toward the best choice possible for new optimized features. We thank You for that.
Where can I give some feedback?
Send an email to support@openrainbow.com. Please consult our troubleshooting guide before sending your email providing the WebRTC gateway and Rainbow client logs.
How do I sign up?
For OminPCX Enterprise, the functionality is in general availability since mid of July, so it is no longer necessary to register for Early Adopter. WebRTC gateway for OXO Connect & OXO Connect Evolution will be available for general availability on Monday, October 15..
If you're interested in becoming an Early Adopter, simply send an email with the following subject: [WebRTC Gateway] I’m interested to be part of the Early adopter phase to support@openrainbow.com. Please indicate the name of the Company in Rainbow on which you want to connect the WebRTC gateway.
We plan to progressively open this feature to customers. So, please be patient if you have signed up and it takes some time to hear from us.
-
Official comment
Hi,
I'm pleased to announce that WebRTC gateway for OXO Connect & OXO Connect Evolution will be available for general availability on Monday, October 15.
This General Availability applies only for OXO Connect & OXO Connect Evolution as "stand-alone" PBX. Do not install the WebRTC gateway on a PBX that is networked with another PBX. More details on the topologies will be published soon.
REMINDER: Due to a future control on the server side that requires an identifier introduced in this WebRTC gateway version 1.67, existing WebRTC gateways whose version < 1.67 must be upgraded to this new version before October 28.
Best Regards,
Customer Care team.Comment actions -
The first version of the WebRTC GateWay for OXO Connect R3.0 is planned to be released before August 3rd in the Early Adopter program. It will run as an ISO software to be installed on a Mini-PC (Intel NUC NUC5CPYH + Ram + Disk or an equivalent pre-packaged version such as Terra 3000 Micro PC)
-
Hi,
WebRTC Gateway 1.67 is available on ALE Business Portal since October, 8th.Due to a future control on the server side that requires an identifier introduced in this WebRTC gateway version 1.67, existing WebRTC gateways whose version < 1.67 must be upgraded to this new version before October 28.Please consult our Installation Guide and Troubleshooting Guide for details about this version and the associated Rainbow solution 1.47.Note: the minimum OXO Connect/OXO Connect Evolution version is R300/054.001.Regards,Baptiste -
Hi,
I’m pleased to announce that we have started the Early Adopter phase. Some of you have already been contacted and are installing the WebRTC Gateway. More Early Adopters will be added in the next days, stay tuned.
Please check below the available features and restriction with current Rainbow solution 1.41:
Available Features:
- WebRTC Calling to PSTN and Nomadic with one Web/Desktop client only.
- Only OXE multi-device user (Deskphone + REX) is supported.
- Support of single and second call with WebRTC Gateway (make, answer, release, hold/retrieve, transfer, conference)
- Support of single and second call in nomadic (make, answer, release, hold/retrieve, transfer, conference)
- iOS and Android of 1.41 support setting PBX dual ringing to mobile phone. Their routing is reflected on desktop (activating dual ring to mobile from mobile shows dual ring on web), and desktop routing reflected on mobiles
Restrictions in this delivery:
- Nomadic with OXE only works with external extensions. Activating nomadic mode to a local OXE extension is possible but does not work (can be programmed but calls fail and also sometimes cannot be released).
- Update of user’s multi-device config in PBX (e.g. adding REX/VT or creating new user) is not automatically reflected on PCG side. A restart of the Rainbow PBX Agent is required to force full resync.An installation & troubleshooting guide is available on our Help Center.
Baptiste
-
Hi,
Since June 16 some fixes for Rainbow solution 1.43 have been , associated WebRTC Gateway 1.62 is now available on ALE Business Portal.For OmniPCX Enterprise, the functionality is now in general availability, so it is no longer necessary to register for Early Adopter to be able to install and use a WebRTC gateway. This has been announced in our Rainbow News sectionYou'll have a description of the available features and restrictions for this version in our Installation Guide.For OmniPCX Enterprise you can still refer to this Installation guide, just disregard the remarks concerning Early Adopter.Baptiste -
Hi Pascal,
I've just updated the Installation Guide because I didn't know that the first time the "mp" commands are executed you'll need to pass some mandatory options:
mpnetwork --IP="10.2.3.4" --NETMASK="255.255.255.0" --GATEWAY="10.2.3.254" --DNS="10.2.3.253"
IP, Netmask, Gateway and DNS are mandatory the 1st time
mpconfig --PBX_DOMAIN="10.2.3.5" --PBXID="PBXa1b1-2wxy-3c3d-6789-4e4f-g556-7h89-10i9"
PBX_Domain and PBXID are mandatory the 1st time.
and do not forget to restart the server "sudo reboot" once the configuration is done.
Regards,
Baptiste
-
HI all im looking to buy a Intel NUC , could you point me in the direction where you purchased this from to cover the above specification. Or a good alternative ?
i guess this has to be cost effective for the SMB market.
thank you
vCPU: 2
CPU reservation in MHz: 4800
vRAM: 2GB
vDISK: 20 GB
vNIC: 1 GB -
hi
Could you confirm I now have access to the webrtc sw and my rainbow account/company ‘ select telecom’ has the facility to apply the early phase integration ?
I filled in the correct form but my rainbow account is not showing access to the facility and I cannot download sw from my BP account.
can you help
thank you
-
Hello everybody,
Our validation team testing WebRTC Gateway for OXO found last technical issues impacting the user experience. Consequently early adoption is postponed to September. We are measuring the stability level every day to provide the best Early Adoption experience to our partners.
Stay tuned, we will give you news as soon as we have information about the release date !
Thanks for your understanding,
Quentin -
Dear,
i'm trying to install a webrtc gateway on a vmware 6.0 infrastructure.
I'm following the guide but the installation is always failing on the 2de step - config :
1.3.1.2 Step 2 - Configure the WebRTC Gateway:
The 1st time you have to tun the command with the mandatory options PBX_DOMAIN and
PBXID as shown below:
mpconfig --PBX_DOMAIN="10.2.3.5" --PBXID="PBXa1b1-2wxy-
3c3d-6789-4e4f-g556-7h89-10i9"
You'll find the some details in chapter Configuration ModificationAnswer is always : "ERROR: aborting, Valeu PBX_DOMAIN, RAINBOW_DOMAIN, RAINBOW_HOST or PBXID not set"
How to continu ?
Regards
Jim
-
found the solution - after config step 1
1.3.1.1 Step 1 - Network configuration
The 1st time you have to run the command mpnetwork with the mandatory options IP,
NETMASK, GATEWAY and DNS as shown below:
mpnetwork --IP="10.2.3.4" --NETMASK="255.255.255.0"
--GATEWAY="10.2.3.254" --DNS="10.2.3.253"
You can also run for this 1st step the mpnetwork command with all options by adding
NTP and HOSTNAME
mpnetwork --IP="10.2.3.4" --NETMASK="255.255.255.0"
--GATEWAY="10.2.3.254" --DNS="10.2.3.253" --NTP="10.2.3.253"
--HOSTNAME="rainbow-mpgwYou MUST reboot the server before configuration STEP 2.
Bpatist, maybe make an update of the instal guide ?
Jim
-
Hi,
I’m happy to announce that we have started the Early Adopter phase with OXO Connect and OXO Connect Evolution.For those who have registered for the Early Adopter phase you will receive information by email within the day about adding Early Adopter subscriptions to your company. You will need to assign an Early Adopter license to your administration accounts to enable the WebRTC gateway on OXO Connect systems.
An installation & troubleshooting guide is available on our Help Center.Baptiste
Post is closed for comments.
Comments
25 comments