2N Netstar, Manual

Page: 255 / 282

255
Figure 6: Part of Configuration of External Extension with Number Used for Routing
The port over which the call will be made determines the setup of routing "Without
port" in the "Routing" tag in the extension properties (or, as the case may be, the type
of the extension when using a mass configuration by the fall–down structure).
Figure
shows a suitable solution of routing of an outgoing call of the external extension. 3
Inclusion of a bundle of GSM ports in the routing "Without port" reduces the probability
of rejection of a call at the respective external extension when one GSM port is busy at
the moment.
One of the possible settings of the bundle is shown in . The selected cyclic Figure 7
allocation strategy means that at the first attempt to call one of the external
extensions, which has this bundle set in the routing "Without port", it will be routed to
the first row of the bundle, i.e., to port GSM 1. At the second call to port GSM 2,
subsequently to port GSM 3, and at the next making of a call again to port GSM 1. In
the event that the specific port is busy at the moment of routing, it will automatically
go to the next row. This is ensured by checking the "Next row if is called busy" option.
In case all the ports are busy, the call can be routed ot the default destination used as
a back-up route.
The By credit option is another suitable strategy for this case. This strategy is intended
for credit-monitored bundles with virtual ports. An incoming call is routed to the virtual
port of the bundle with the currently highest count of free minutes. If there are more
rows with the same count of free minutes, the sequence of rows in the bundle is
respected. If a row object is busy or unavailable, the call is routed to the next row, or
terminated.