[WebRTC Gateway] Early adopter OXO Connect - VoIP calling

Completed

Comments

26 comments

  • Official comment
    Avatar
    Baptiste CANDELIER

    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.

  • Avatar
    Brian BIRD

    I have sent the email. Very interested in being an early adopter, although more so with the OXO platform :)

  • Avatar
    Rubén RÍO

    Hello,

    Would you specify what are the "REX licenses"?
    I've never hear about them before.

    Regards,

  • Avatar
    Tom KOPPERS

    REX stands for Remote Extension licenses in the OXE. You need a REX license if you want to use the Rainbow as softphone without an other device.

  • Avatar
    Christopher RIEGLER

    "REX" means "Remote Extension". This is a license on the PBX and can be checked for instance on the OXE with the spadmin CLI command.

  • Avatar
    Rubén RÍO

    Thanks, I know remote extension, but never heard before this acronym.
    Regards!

  • Avatar
    Antonio TESSARI

    When will this feauture be available on the OXO platform? I have little interest in OXE pbx!

  • Avatar
    Baptiste CANDELIER

    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

  • Avatar
    Baptiste CANDELIER

    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 section
     
    You'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
  • Avatar
    Pascal KICK

    Hi,

    after Installation I have no

    /etc/otlitemediapillargateway/config.js ?!?

     

    and "invaild HOSTNAME setting" see Screenshot

    but the hostname "rainbow-mpgw and the DNS entry is set

     

     

     

  • Avatar
    Baptiste CANDELIER

    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

  • Avatar
    Antonio TESSARI

    In the presentation of new Alcatel-Lucent OXO Connect R3.0 is introduced a Rainbow WebRTC gateway to establish VoIP calls from/to Rainbow devices.

    Any information about the project? They run like the "brother" OXE

    thank's

  • Avatar
    Dany JENNEVÉ

    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)

  • Avatar
    Brian BIRD

    Fantastic news Dany...we are ready!

  • Avatar
    Rogerio GAUZE

    Hi, the webRTC gateway works on V-Motion?

  • Avatar
    Paul HOGG

    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

     

  • Avatar
    Paul HOGG

    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

     

     

  • Avatar
    Quentin GRABENSTAETTER

    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

  • Avatar
    Jim VERTÉ

    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 Modification

    Answer is always : "ERROR: aborting, Valeu PBX_DOMAIN, RAINBOW_DOMAIN, RAINBOW_HOST or PBXID not set"

     

    How to continu ?

    Regards

    Jim

     

  • Avatar
    Jim VERTÉ

    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-mpgw

     

    You MUST reboot the server before configuration STEP 2.

    Bpatist, maybe make an update of the instal guide ?

     

    Jim

  • Avatar
    Jorge Alberto Rivera

    Someone know if  the Gateway for OXO  is ready with the last release for production, and the issues correction for end user experience?  , I need download  the stable version of the  VM, 

  • Avatar
    Baptiste CANDELIER

    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
  • Avatar
    Baptiste CANDELIER

    Hi Jim,

    Thanks for your feedback, the issue you have described will not occur with latest WebRTC gateway 1.66. With this version both configuration steps can be executed without reboot of the server. 

    Regards,

    Baptiste

     

  • Avatar
    David LAMORSKI

    Hi,

    Have connected WebRTC-GW 1.66 and OXO, VoIP calls are working good. But I can not see the calling number while Rainbow App is in background or the iPhone is idle. Instead of the number "MediaPillars" is shown.

  • Avatar
    Koen CNAEPKENS

    Hi Baptiste,

    Have you got any idea when the WebRTC gateway will become generally available? 

    Kind regards

  • Avatar
    Baptiste CANDELIER

    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

Post is closed for comments.