This feature allows to increase the call capabilities on a single OXE by connecting several WebRTC gateways and also enables applicative High Availability (HA).
- Works with OXE from R12.4 MD4, R100 and higher
- Is not applicable to OCO/OCE
Topology
► Principles based on OXE ARS mechanisms
- One SIP trunk per WebRTC gateway.
► Overflow on the following SIP trunk when:
- Maximum number of simultaneous streams defined on the SIP trunk is reached
- The WebRTC gateway doesn’t respond
- The SIP trunk fails down
- The WAN access is unavailable for the WebRTC gateway.
► Maximum number of streams corresponds to the capacity of the WebRTC gateway.
► The number of the WebRTC gateway depends on the number of SIP trunk supported by the OXE (see OXE feature list).
Note: More about WebRTC gateway topologies, flows, use cases and sizing can be found in the Technical Business Engine document TBE067 available on MyPortal
Rainbow Configuration
- Main configuration is done on PBX side to manage the sip trunks to the WebRTC gateways, consult TC2462 for detailed configuration.
- On Rainbow side, you'll need only to create as many WebRTC gateways as needed.
On the Equipment configuration, tab "Connection" click on "Add a new WebRTC gateway"
Each new WebRTC gateway will have a new Gateway ID
If first WebRTC gateway ID is PBXa1b1-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-c1d1 then you have
- PBXa1b1-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-c1d1-1 for the second one
- PBXa1b1-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-c1d1-2 for the 3rd
- PBXa1b1-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-c1d1-3 for the 4th
- and so on
It is this Gateway ID that has to be used to configure each additional WebRTC gateway.
Note: All WebRTC gateways have the same configuration Except PBXID which is the corresponding Gateway ID available on the Rainbow admin page and the IP address and Hostname which are unique for each WebRTC gateway.