Howto:SBC scaling for large number of channels: Difference between revisions
No edit summary |
No edit summary |
||
| Line 46: | Line 46: | ||
==Configuration Example== | ==Configuration Example== | ||
'''The following example shows how a configuration can be done, maybe it’s a little bit different in your scenario. Depending on the SIP Provider and the needed Number Mappings or Routes, there can be a lot of alternative Configurations''' | |||
===Configuring the Customers regular PBX=== | ===Configuring the Customers regular PBX=== | ||
'''1. Create a Trunk Object in the regular PBX''' | |||
Of Course, in the regular PBX (where usually the Users are registered), a Trunk Object must be existing with the Number for External calls. | |||
[[Image: RealPBX_1TrunkObject.jpg]] | [[Image: RealPBX_1TrunkObject.jpg]] | ||
===Configuring the Registration Gateway=== | ===Configuring the Registration Gateway=== | ||
'''2. Enable the PBX on the Register-GW''' | |||
On the same GW where the SBC (SIP Interface to Provider) is configured, a PBX must be created. Any System or PBX Name can be chosen because it’s normally an isolated PBX. But two Port Licenses are needed for the two Gateway registrations. | |||
[[Image: RegisterGW_1MasterPBX.jpg]] | [[Image: RegisterGW_1MasterPBX.jpg]] | ||
'''3. Create two Gateway Objects''' | |||
On this PBX two Gateway Objects must be created. Defaults settings can be used, but each Gateway Object must have a Number. | |||
In this example we have chosen the Prefix "1" for calls to the SIP Provider and the Prefix "2" for calls to the internal PBX. | |||
[[Image: RegisterGW_2PBX-GatewayObjects.jpg]] | [[Image: RegisterGW_2PBX-GatewayObjects.jpg]] | ||
'''4. Configure SIP Interface''' | |||
At the SIP Interface to the Provider, nothing special must be configured, please use the Provider specific setting from the Profiles or from the Provider Documentation. | |||
Only Media Relay must be set to "off" and the internal registration goes to the PBX on its own Gateway. | |||
[[Image: RegisterGW_3SIP-Interface.jpg]] | [[Image: RegisterGW_3SIP-Interface.jpg]] | ||
[[Image: RegisterGW_4Routing.jpg]] | '''4. Modification of the Routes''' | ||
Following modification must be done in the Routes | |||
* The '''"2"''' (Prefix of the second Gateway Object in the PBX) '''must be added''' before each called Number that goes to the PBX. | |||
* If there is a default Tone Mapping, it can be disabled or deleted. | |||
* The '''"1"''' (Prefix of the first GW Object in the PBX) '''must be cut''' before each called Number that comes from the PBX. | |||
[[Image: RegisterGW_4Routing.jpg]] | |||
=== Configuring the SBC Relay Gateways=== | === Configuring the SBC Relay Gateways=== | ||
Revision as of 14:10, 2 September 2016
Applies To
This information applies to
- SBC functionality on Gateways or IPVA with v12r1 or later
More Information
Preamble
With the innovaphone SBC, we provide approximately 100 - 200 concurrent Channels per Gateway or IPVA. In bigger Scenarios where a few hundred (or more) Channels are required, several Gateways can be joined to a "Load Balancing Scenario" to provide a large number of Channels.
Also, in most scenarios an additional and dedicated SBC as SIP -Gateway to the Provider is needed (with or w/o registrations), because the most part of SIP Providers accept only one counterpart.
This document describes the principles how to configure such a "Load Balancing Scenario" with reference to an example.
Be aware that this is just an example to explain how it works; maybe it’s a little bit different in your scenarios depending on the SIP Provider!
Function Principle
The Limitation of the concurrent Channels per Gateway is based on the Media Relay Feature. If this Feature is enabled (and it’s mandatory for the SBC), the Channels are limited.
To bypass this limit, the idea is:
- to have a dedicated Gateway without Media-Relay. This acts only as Registration Gateway to the SIP Provider. Without Media Relay this Gateway can handle a very large number of calls. We call it "Register-GW" in this document.
- to use as many Gateways as needed for Media Relay. All calls should be evenly distributed on this Gateway to have a "Load Balance Scenario". We call them "Relay-GWs" in this document.
Register-GW
- On the "Register-GW" we need a PBX because only with the PBX we have an evenly distribution to several Gateways. Therefore the PBX must be enabled (Master) on this Gateway, but we need only two Gateway Objects in it. The first is for the registration from the Provider- SIP-Interface (on the same GW) and the second is for all registrations from the "Relay-GWs". No other object is needed.
- The SIP-Interface to the Provider is similar to the SBC of the "Common Scenario". It has two registrations, one to the SIP Provider and another to the internal PBX. Only Media relay is disabled.
- The default Routes between SIP Provider and PBX must be adapted.
Relay-GWs
The "Relay-GWs" are serving the Media Relay Part in this scenario. On each "Relay-GW" there are two registrations and simple routes between it.
- One registration to the "Register-GW"- PBX with Media Relay and the same SDP settings like the SIP Interface to the Provider.
- One registration to the real PBX w/o Media Relay with default settings.
Configuration Example
The following example shows how a configuration can be done, maybe it’s a little bit different in your scenario. Depending on the SIP Provider and the needed Number Mappings or Routes, there can be a lot of alternative Configurations
Configuring the Customers regular PBX
1. Create a Trunk Object in the regular PBX
Of Course, in the regular PBX (where usually the Users are registered), a Trunk Object must be existing with the Number for External calls.
Configuring the Registration Gateway
2. Enable the PBX on the Register-GW
On the same GW where the SBC (SIP Interface to Provider) is configured, a PBX must be created. Any System or PBX Name can be chosen because it’s normally an isolated PBX. But two Port Licenses are needed for the two Gateway registrations.
3. Create two Gateway Objects
On this PBX two Gateway Objects must be created. Defaults settings can be used, but each Gateway Object must have a Number.
In this example we have chosen the Prefix "1" for calls to the SIP Provider and the Prefix "2" for calls to the internal PBX.
4. Configure SIP Interface
At the SIP Interface to the Provider, nothing special must be configured, please use the Provider specific setting from the Profiles or from the Provider Documentation.
Only Media Relay must be set to "off" and the internal registration goes to the PBX on its own Gateway.
4. Modification of the Routes
Following modification must be done in the Routes
- The "2" (Prefix of the second Gateway Object in the PBX) must be added before each called Number that goes to the PBX.
- If there is a default Tone Mapping, it can be disabled or deleted.
- The "1" (Prefix of the first GW Object in the PBX) must be cut before each called Number that comes from the PBX.
Configuring the SBC Relay Gateways
