Skip to main content
👋 You have been redirected to the new Help Center! Don't forget to change your shortcuts. More about migration

Does the knowledge base help you find what you're looking for?

Thanks for your opinion

Shared WebRTC Gateway

Related to

Baptiste CANDELIER
  • Updated

Shared WebRTC Gateway Principles

  • By default all OXE PBXs of a company belong to the same PBX group. This notion of PBX group is hidden from BP administration.
  • The shared WebRTC Gateway principle relies on the capability for the Rainbow administrator to configure the WebRTC Gateway of one of the nodes as default route within a PBX group.
  • This shared WebRTC Gateway is then used by all OXE nodes of this group, that don’t have their own WebRTC Gateway.

mceclip0.png

For the example above:

  • On the Rainbow administration side, only Node3 has a WebRTC gateway declared, set as the default route. Node1 and Node2 do not have a WebRTC gateway declared

Node3 configuration
mceclip1.png

Node1 & Node2 configuration
mceclip2.png

  • On OXE configuration side, Node3 has a SIP trunk toward its WebRTC gateway. Node1 and Node2 also have the same SIP trunk configuration pointing to the same WebRTC gateway.

WebRTC gateway capacity

The WebRTC gateway capacity remains unchanged (refer to presales document TBE067), and must not be exceeded when mutualizing telephony traffic of several OXE through one shared WebRTC gateway.

  • If the load of a shared WebRTC gateway gets too high, a dedicated WebRTC gateway can be added to the node that have the highest traffic.
  • It is possible to have several PBX with a WebRTC gateway in the same group, but only one WebRTC gateway can be default within a group.

From example let's say Node1 has high traffic and need a dedicated WebRTC gateway. Node1 will exclusively use the WebRTC gateway declared on it, Node2 & 3 will use the shared WebRTC gateway.

mceclip0.png

Note:
Shared WebRTC gateway principle is not compatible with scalable WebRTC gateway configuration. However, within a group, high load nodes can be deployed with a dedicated scalable WebRTC gateway, while low traffic nodes can share a WebRTC gateway.
mceclip2.png

Rainbow PBX group management

PBX groups is a hidden notion in Rainbow that represents PBX with homogeneous numbering plan in the same company. It allows Rainbow to optimize calls by forcing internal numbering.

By default in a Rainbow company, there is one group for all OXEs

Creation of several groups within a company is possible via a Support Request, in case there is a need to have OXE groups each with a Shared WebRTC Gateway, for capacity or geography reasons. Required information is the list of PBX Ids and the expected group names.

Important:
Rainbow will use public numbers when dialing a user belonging to another group, Therefore, the OXE configuration must be properly set up that dialed extensions are translated into internal extensions when OXE nodes actually share a homogeneous numbering plan.

Troubleshooting

A few reminders about log recovery :

  • The easiest way for the end user to recovery the Rainbow client logs is to use the Report a problem feature.
  • For Rainbow client logs consult the dedicated article.
  • In addition to Rainbow client logs, for web client the Browser log can be very helpful.
  • For WebRTC gateway logs (mpcollect --all) and SIP traces (mpndump on) consult the dedicated article.
Was this article helpful?
0 out of 0 found this helpful

Related articles