When a company uses more than one PBXs (e.g. Head office and branches or subsidiaries) it is possible to add each PBX into the same Rainbow company. But there are some configuration rules that must be followed and may require some action from the Rainbow Customer Care team to set up the correct configuration.
General information
The PBX numbering plan must be homogeneous and the PBX must be configured to allow and route calls from one PBX to another based on the internal numbers of the users. These conditions and the configuration done on Rainbow side will guarantee the best user experience.
Rainbow PBX management principles
System Group
From a Rainbow admin point a view a PBX is attached to a Rainbow Company, but from a technical point of view, in the Rainbow database, a PBX is (can be) linked to a system group in this company. The belonging to a system group mainly defines how Rainbow will make a call from one PBX to another PBX of the same company.
- For OXE, at PBX creation a default system group is created and each additional OXE PBX in this company will be put in this system group.
- For OXO Connect, at PBX creation no system group is created. Each additional OXO Connect PBX will therefore also be added to the company without link to a system group.
Role of a system group
PBX in the same company and same system group:
Calling a user that is on another PBX of the same system group will be made automatically with the internal number, even if the call button displays the DDI of the user. The PCG (server in front of the PBX on Rainbow cloud side) chooses to send to the PBX the internal number of the called party based on the belonging of the destination PBX to the same system group.
PBX in the same company but not in a system group or same system group:
In this case, if the called party has a DDI number, the internal number of the destination will not be used automatically and therefore the DDI number will be send to the PBX to make the call. So depending of the PBX configuration the call might result in an external outgoing call on the public trunk.
If the called party has only an internal phone number, then this number will be sent to the PBX and if no specific configuration is made on PBX side the call will not be established.
Company with several OXO Connect
As stated above no system group is created when an OXO is created/added to a company.
Now if you have a company with several OXO that are in network with homogenous numbering plan you'll have to contact the Rainbow Customer Care Team so that we create the system group and add the concerned PBXs to this group.
Company with several OmniPCX Enterprise
A OmniPCX Enterprise PBX is automatically created in a system group (default system group of the company). Any additional OXE will be added to this system group and therefore it is mandatory to have a homogenous numbering plan and the PBXs must be configured to allow calls from one PBX to another based on the internal numbers of the users.
Mixing PBX types and having several system groups
It is possible to have different PBX types in the same company.
As indicated previously if you have for example a OXO and a OXE in the company only the OXE will be in a system group. Now if these PBXs are in network with a homogenous numbering plan you'll have to contact the Rainbow Customer Care Team so that we add the OXO to the same system group as the OXE.
It's also possible in the same company to have some PBXs in one system group and some PBXs either in another system group or not attached to a system group. Calls from/to PBXs from different system groups (or no in a system group) will always use DDI calls on public trunk.