TELES VoIPBox BRI, Справочное руководство

Страница: 201 / 280

7 Signaling and routing features
VoIPBox BRI Version 18.0.002 Page 201
Before adding call forking functionality to your
route.cfg,
check whether the necessary mapping of a destination num-
ber to a port followed by the new destination number exists:
For routing to a VoIP port, the following syntax is used:
The parameters
<destinationNumber>
and
<newDestinationNumber>
do not need to be identical.
To activate call forking, add the following entries behind the
mappings:
Assign the port folowed by the new destination number to the
parameter
GlobalIn<int>
. You can define up to 32 different
GlobalIn
configurations.
GlobalIn<int>=<port><newDestinationNumber>
where int
>= 1
For VoIP, the following syntax is used:
GlobalIn<int>=<voipPort><voipProfile>:<newDestinationN
umber>
where int >= 1
Assign the numbers which you want to call simultaneously to
the
GlobalOut<int>
parameter. The integer value is used to
map
GlobalIn
to
GlobalOut.
You can define up to 32 different
GlobalOut
configurations
GlobalOut<int>=<destinationNumber1>
<destinationNumber2>
where int >= 1
Be aware that for both destination numbers the
MapAll
pa-
rameter needs to be set. This must be done before the fork-
ing.
In this example two mappings exist: calls to the destination
number 543211234 are mapped to the port 10 and the new
destination number 543211234. Calls to the destination num-
ber 01721234554 are mapped to the port 20 and the new des-
MapAll<destinationNumber>=<port><newDestinationNumber>
MapAll<destinationNumber>=<voipPort><voipProfile>:<newDestinationNumber>