To make things easier we will use a basic graph: A company with two headquarters and two affiliates.
In the headquarters there are 2 primary lines available for outgoing calls and receiving calls in passing
selection, and a SIP provider is also available in the headquarters that allows for calling Russia at no cost.
This is the graphic layout that illustrates the example that we will configure.
It is now necessary to know the headquarters’ numbering system:
-
HEADQUARTERS: 81XX where XX are variable numbers between 0 and 9 with a total of 100 extensions
available between 8100 and 8199.
-
AFFILIATE 1: 82XX
-
AFFILIATE 2: 83XX
-
RUSSIAN PREFIX: 0037
-
LOCAL NUMBER: 061238XXX where XXX means 999 numbers in passing selection from 061238000 a
061238999
-
To call with the local number dial 0 (zero) first.
Note
In all affiliates it is necessary to publish the UDP 5036 and UDB 4569 portals (IAX2 protocol) to allow them to
communicate with the station. It is not advisable to have a static IP address for connecting the affiliates while
the static IP address is indispensable for the headquarters.
In this example both the affiliates have the static IP address. If one or more of the affiliates do not have the
static IP address one needs to refer to the relative suggestions.
MASTER STATION (COMPANY HEADQUARTERS STATION)
After correctly installing the two primary cards into the server that is destined to Nblade, activate in the VOIP -
> GLOBAL PARAMETERS menu the support PRI/BRI by selecting (in this case, two primary E1 lines) the
PRI parameter.
While still in GLOBAL PARAMETERS activate the PRI/BRI Auto detects option and restarts the system from
the SISTEMA -> RIAVVIA menu.
Once restarted you will find in the PROVIDER -> PRI/BRI menu the two cards ready to use (if not, you should
check the configuration with your provider - see Provider PRI/BRI
).
Still with the two PRI cards, define the voice REMOVE NUM=1
In the PROVIDER -> SIP/IAX menu, configure the provider that will supply your subscription at zero cost for
Russia (See Provider Sip Iax
).
Still in the PROVIDER -> SIP/IAX menu, configure the two accounts for the slave station in this way:
The protocol is very important, which can be created either by trunking with SIP or with IAX, but for ease we
recommend that it is created with IAX.
The host is the IP address of the affiliates, while the username and password are the same that you
configured for the
remote headquarters.
The context must be in passing selection.
If the remote headquarters does not have a static IP address, you do not need to specify the host but you
need to type in “dynamic”.
Add this new provider and create another identical for the AFFILIATE 2.
At this point we have created the basic structure for enabling the transfer of calls from and to the local lines
(PRI E1), and even to the affiliates.
In the GLOBAL PARAMETERS -> NUMERATION we put 81xx, which identifies the
current station.
(centrale
corrente).
Now we need to create the routing (prefixes) between the various stations. For how to create them, see the
section Prefixes
.
From the PROVIDER -> PREFIXES menu, we can create 4 new rules:
Dialstring Provider
_0XXX. PRI lines
This prefix allows you to call out from the PRI line by dialling ZERO
_82XX AFFILIATE_1
_83XX AFFILIATE_2
These two send the call to the affiliates.
_00037XXX. Provider_SIP_Russian
This prefix makes a direct call with the Russian provider.
We can now configure the permission
inside the
user menu
.
The station is now ready for APPLYING THE MODIFICATIONS and SAVING THE RESCUE POINT.
AFFILIATE STATION 1
The affiliates are much easier to configure.
In the PROVIDER -> SIP/IAX menu, we’ll configure only one account for the headquarters:
Where in the host we indicate the IP address or the DNS name of the master station, the username and
password are the same that you defined in the master station for this affiliate.
If the affiliate does not have a static address you need to type in “YES” in the Register option.
In the GLOBAL PARAMETERS -> NUMERATION we’ll put 82xx which identifies the
current station
.
Now you need to create the routing (prefixes) among the various stations. For how to create them, go to the Prefixes
section.
From the PROVIDER -> PREFIXES menu we’ll create 4 new rules:
Dialstring Provider
_0XXX. STATION_HEADQUARTERS
_81XX STATION_HEADQUARTERS
_83XX STATION_HEADQUARTERS
It is not necessary to configure the Russian prefix because it is already included in the first prefix
_0XXX.
We can now configure the permission
inside the
user menu
.
The station is now ready for APPLYING THE MODIFICATIONS and SAVING THE RESCUE POINT.
AFFLILIATE STATION 2
The affiliates are much easier to configure.
In the PROVIDER -> SIP/IAX menu, we’ll configure only one account for the headquarters:
Where in the host we indicate the IP address or the DNS name of the master station, the username and
password are the same that you defined in the master station for this affiliate.
If the affiliate does not have a static address you need to type in “YES” in the Register option.
In the GLOBAL PARAMETERS -> NUMERATION we’ll put 83xx which identifies the current station.
Now you need to create the routing (prefixes) among the various stations. For how to create them, go to the
section Prefixes
.
From the PROVIDER -> PREFIXES menu we’ll create 4 new rules:
Dialstring Provider
_0XXX. STATION_HEADQUARTERS
_81XX STATION_HEADQUARTERS
_82XX STATION_HEADQUARTERS
It is not necessary to configure the Russian prefix because it is already included in the first prefix
_0XXX.
We can now configure the permission
inside the
user menu
.
The station is now ready for APPLYING THE MODIFICATIONS and SAVING THE RESCUE POINT.
THE SYSTEM CAN NOW FUNCTION.