
INSTALLATION MANUAL
7.7.6
General Routing Considerations
Here are shown some general routing consideration for the calls made via Voxell LCR via its
three ports.
7.7.6.1
GSM port
The settings for routing are:
-
IN and OUT, which allow the respective calls,
-
DISA, that makes use of dialing in by using DTMF,
-
Direction, assigns the mobile module to a trunk,
-
Target type, where you select either FXS or FXO,
-
Target, where you enter the number of the
destination of the call coming in via mobile module.
incoming calls
-
if you have checked DISA – this is relevant only when the ports FXS and FXO are present.
-
dial the number you want using DTMF, it will be analyzed and outputted towards the
FXO, or a call is made to the FXS
-
when DISA is checked, the call is directed to the port number you have filled in the
target field, such as the local extension “283”;
-
if the Target Type is FXO, then the FXO interface is engaged and the number you have
entered in the field Target is sent in DTMF mode. The call from GSM will be answered,
because there is no information about the beginning of the conversation from the FXO
interface
-
when the Target Type is FXS instead of FXO, a call will be generated to FXS and the call
coming in from GSM is answered when the FXS subscriber picks up the phone.
outgoing calls
-
the mobile module has associated a direction name (by default trunk 0); if the number
dialed over FXO (in DISA mode) or over FXS directly corresponds to the direction
associated with the mobile module, the call will be made via this GSM module. If the
number corresponds to another direction, it will be routed to the respective interface,
and if it corresponds to no real interface (Trunk 3), the call will be rejected, the caller
will hear busy tone!
-
GSM in mode DISA - it waits for the reception of the whole numbering from the mobile
network (either the number of digits specified in the Routing table is reached or a “#”
character is encountered) and then it is sent to the FXO interface.
page 45 / 60