Beiträge in diesem Abschnitt

VoIP calling: Installation guide [WebRTC Gateway]

Avatar
Baptiste CANDELIER
  • Aktualisiert

Drucken

Folgen

Note1: Troubleshooting articles are only available in English.

Note2:
- This installation guide applies for the OXO Connect Early Adopter phase and OmniPCX Enterprise in General Availability.
- Please consult our Early Adopter Community for details about this Early Adopter step.

What's new: Minimum OmniPCX Enterprise R12.1 version has been updated

 

Available features and restrictions with current Rainbow solution 1.43:

Web/Desktop Client 1.43

  • Supports VoIP through WebRTC Gateway and Nomadic mode to mobile or another phone.
  • Supports OXE/OXO multi-device user having a main desk phone and a REX/VT as secondary.
    • Nota: Pure softphone/mobile users with only one virtual extension (OXE REX or OXO AnyDevice) as main PBX phone, is currently not supported and will be introduced in a next Rainbow Solution version
  • Allows managing single and second call in VoIP mode through WebRTC Gateway (make, answer, release, hold/retrieve, transfer, conference).
  • Allows managing single and second call in nomadic (make, answer, release, hold/retrieve, transfer, conference).
  • Web/Desktop application can now send DTMF while in WebRTC communication through the WebRTC gateway.
  • Allow sharing a screen while in WebRTC communication through the WebRTC gateway.

Android app 1.43

  • Support setting dual ringing to mobile phone.
  • Support PBX single and second call in GSM mode (“nomadic” mode with GSM).
  • Support single and second call in VoIP mode thru WebRTC Gateway.
  • Supports OXE/OXO multi-device user having a main desk phone and a REX(OXE)/AnyDevice(OXO) as secondary.
  • Supports OXE users equipped with only one REX device for GSM mode only (no WebRTC gateway calls).
    • beware that the Web/Desktop app does not yet support this mode, that is therefore currently valid for users only using the mobile app.
  • Allow sending DTMF while in WebRTC communication through the WebRTC gateway.

iOS app 1.43

  • Support setting dual ringing to mobile phone.
  • Supports OXE multi-device user having a main desk phone and a REX as secondary.
    • Nota: Pure softphone/mobile users with only one virtual extension (OXE REX or OXO AnyDevice) as main PBX phone, is currently not supported and will be introduced in a next Rainbow Solution version.
  • Support PBX single call in GSM mode (“nomadic” mode with GSM).
  • Support PBX single call in VoIP mode through WebRTC Gateway

WebRTC Gateway 1.62

  • Available on ALE Business Portal
  • Improve installation experience with a script avoiding manual modification of configuration files (script robustness improved vs 1.61).
  • Nota:
    • Upgrade of OVA to 1.62 is strongly recommended to get full support.
    • WebRTC gateway 1.60 is not compatible with Rainbow Solution 1.43.
  • Component upgrade requires installation of new OVA version
    • Nota: automated update is planned in a next sprint

New numbering configuration:

  • This Rainbow Solution version introduces the Rainbow “long numbering”, where Rainbow users are no more associated to an extension that corresponds to their internal number prefix with Rainbow prefix (BBB), but uses a 17 digits unique extension prefixed by the Rainbow prefix. The OmniPCX Enterprise discrimination rule must be updated according to the TC2462 section 3.2.2.2.
  • Nota: it is advised to restart the whole server with the command sudo reboot to have the users registered with their new 17 digits numbers.

Restrictions:

  • 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).
  • Call log of calls received through WebRTC Gateway displays missed calls.
  • No DTMF on iOS while in a VoIP call through WebRTC Gateway.
  • On OXO, AnyDevice resource creation for a user is not automatically detected by Rainbow. Consequently, after managing AnyDevice resources on PBX side for the Rainbow users, a restart of the Rainbow agent is required from OMC for Rainbow to properly synchronize new multiset configurations. This will be fixed in a next Rainbow Solution version.
  • WebRTC gateway upgrade require reinstallation of new OVA. Automated update is planned in a next Rainbow Solution version.

1 Installation

1.1 Requirements:

  • Rainbow users need to be granted with either a Business or an Enterprise licenses.
  • OXE PBX needs:
    • to run with SW version OXE 12.1 MD2 (M2.300.21.a) & OXE R12.2 (M3.402.13.f).
    • to be granted with REX licenses per targeted Rainbow user
    • to be connected to Rainbow for the Telephony Services
  • OXO PBX needs:
    • to run with SW version OXO Connect R300/045.001
    • to be granted with an AnyDevice Terminal per targeted Rainbow user
    • to be connected to Rainbow for the Telephony Services
  • A Virtual Machine must 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: 2GB
    • vDISK: 20 GB
    • vNIC: 1 GB

1.2 OVA installation:

1.2.1 Software Download

The WebRTC Gateway Software is subject to export control laws and you need to fill-in a form to request the access to the software (detailed instructions are on the ALE Business Portal). Today the software is available under OXE R12.1, OXE 12.2 and soon under OXO Connect R3.0.

1.2.2 Installation:

First deploy the .ova file in your vCenter and start the virtual machine (VM).

Note: The .ova has been created with a QWERTY keyboard, you may need to change it:

Login with followin crendentials:
User=kb
Password=kb

The wizard to change the keyboard will be automatically started, just follow the instructions on the screen to change your keyboard.

You may also access to the same menu by using following commands:

# dpkg-reconfigure keyboard-configuration
# service keyboard-setup restart

For the configuration login with following credentials on the console:

User=rainbow
Password=Rainbow123

Make sure to change the default rainbow login password.

For root commands you must use “sudo”

1.3 WebRTC Gateway configuration (as of version 1.61)

When logged using rainbow account, the configuration is made using the commands mpnetwork [options...] and mpconfig [options...]

mphelp //displays the list of mpXXXXX commands//

mpstart|mpstop|mprestart //start, stop or restart gateway//

1.3.1 First Installation:

You need first to configure the Network settings then the WebRTC gateway settings.

By default the Rainbow WebRTC Gateway starts using a DHCP based network setting.

Login with the rainbow account to make the configuration

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"

optional you can add following options

--HOSTDOMAIN="mycompany.com"
--PROXY="user:pass@10.2.3.252:8000/"

You'll find the some details in chapter Configuration Modification

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

1.3.1.3 Step 3 - Reboot the server

Then you need to reboot the server with the command sudo reboot

1.3.1.4 Config files

Once you have executed both scripts mpnetwork and mpconfig you can check the configuration in following file /etc/rainbow-mp.cfg.

IP="10.2.3.4"
NETMASK="255.255.255.0"
GATEWAY="10.2.3.254"
HOSTNAME="rainbow-mpgw"
HOSTDOMAIN="mycompany.com"
DNS="10.2.3.253"
NTP="10.2.3.253"
LOGLEVEL="info"
JANUSLOGLEVEL="4"
PROXY=""
TURN_SERVER="turn-eu1.openrainbow.com"
TURN_PORT="3478"
PBXID="PBXa1b1-2wxy-3c3d-6789-4e4f-g556-7h89-10i9"
PBX_DOMAIN="10.2.3.5"
RAINBOW_DOMAIN="openrainbow.com"
RAINBOW_HOST="openrainbow.com"

This is a summary of the parameters that will be used to configure the VM and the 3 services of the WebRTC gateway

/etc/janus/janus.cfg
/etc/otlitemediapillargateway/config.js
/etc/kamailio/kamctlrc

1.3.2 Configuration modification:

Once the 1st installation has been performed you can modify each parameter individually.

1.3.2.1 Network settings

In case you need to update the configuration each command can be executed separately

mpnetwork --IP="10.2.3.4" //your new ip address of the VM//
mpnetwork --NETMASK="255.255.255.0"
mpnetwork --GATEWAY="10.2.3.254" //your gateway//
mpnetwork --DNS="10.2.3.253" //your DNS//
mpnetwork --NTP="10.2.3.253"
mpnetwork --HOSTNAME="rainbow-mpgw"

optional

mpnetwork --HOSTDOMAIN="mycompany.com"
mpnetwork --PROXY="user:pass@10.2.3.252:8000/"

you may also use

mpnetwork --FQDN="rainbow-mpgw.mycompany.com"

After the modification reboot the server with the command sudo reboot

1.3.2.2 WebRTC Gateway settings:

In case you need to update the configuration each command can be executed separately

mpconfig --PBX_DOMAIN="10.2.3.5" //your OXE/OXO ip address//
mpconfig --PBXID="PBXxxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx" //your OXE/OXO pbxid in Rainbow//

Note: PBX_DOMAIN can be an FQDN (in this case the DNS used by the WebRTC Gateway must resolve this FQDN)

optional

mpconfig --PROXY="user:pass@10.2.3.252:8000/"
mpconfig --RAINBOW_DOMAIN="domain.yy.zz"
mpconfig --RAINBOW_HOST="host.uu.vv"
mpconfig --TURN_SERVER="turn-CC.openrainbow.com"
mpconfig --TURN_PORT="3478"

TURN server configuration replace CC with:

na1 for TURN server located in America
as1 for TURN server located in Asia
oc1 for TURN server located in Oceania
eu1 for TURN server located in France (default value if not modified)
eu2 for TURN server located in Germany
eu3 for TURN server located in UK

After the modification reboot the server with the command sudo reboot

1.3.2.3 Change network settings to DHCP

run the command:

mpnetwork --IP=dhcp

optional you can add a proxy

mpnetwork --PROXY="user:pass@10.1.2.252:8000/"

After the modification reboot the server with the command sudo reboot

2 OXE configuration:

Please consult TC2462 for the OXE configuration.

3 Rainbow Configuration:

For the OXE/OXO connected to the WebRTC Gateway you'll have to select the option "Activate the WebRTC gateway"

 

Note: To have this option on an OXO Connect, the administrator of the Rainbow company needs to be granted with an Early Adopter licence on his account.

4 Troubleshooting:

for troubleshooting please read the troubleshooting guide

 

 

 

Verwandte Beiträge

Kommentare

0 Kommentare

Zu diesem Beitrag können keine Kommentare hinterlassen werden.