Overview
To increase call capacity and ensure high availability in OXE networks, the WebRTC Gateway Scalability feature allows multiple WebRTC gateways to be connected to a single OXE. This setup enables overflow handling and load distribution across gateways.
Note: Works with OXE from R12.4 MD4, R100 and higher. Is not applicable to OCO/OCE.
An alternative method—Dynamic Overflow—uses gateway-side call rejection to trigger overflow, offering a more flexible option for episodic peak loads
Scalability Principles
This feature relies on standard OXE ARS mechanisms, with one SIP trunk per WebRTC gateway. Overflow occurs when:
- The maximum number of simultaneous streams on a SIP trunk is reached
- The WebRTC gateway does not respond
- The SIP trunk fails
- WAN access to the gateway is unavailable
The maximum stream count reflects the gateway’s capacity, and the number of gateways is limited by the SIP trunk support of the OXE system.
Topology
Configuration Highlights
- OXE Side: SIP trunks must be configured for each WebRTC gateway. Refer to TC2462 for detailed setup.
-
Rainbow Side: Create as many WebRTC gateways as needed. Each gateway receives a unique Gateway ID (e.g.,
PBXa1b1-xxxx-xxxx-xxxx-c1d1,PBXa1b1-xxxx-xxxx-xxxx-c1d1-1, etc.).
- All gateways share the same configuration, except for their PBX ID, IP address, and hostname, which must be unique.
Use Case Guidance
WebRTC Gateway Scalability is ideal for steady-state deployments where overflow is expected regularly. It allows OXE to manage call routing directly, without relying on gateway-side rejection. This makes it well-suited for larger or multi-site environments where predictable load balancing is required.
For episodic or peak-load scenarios, consider the alternative Dynamic Overflow feature, which handles overflow at the gateway level.
Note: More about WebRTC gateway topologies, flows, use cases and sizing can be found in the Technical Business Engine document TBE067 available on MyPortal.