______________________________________________________________________________
Page 100
Version 6.0
______________________________________________________________________________
NovaTec
Mobile Gateway S20
Under „Target“ the routing settings are made. Here it must be guaranteed that the Client can
find the Interface where the Server can be reached. (the
Actual dialled number
plays no
role for the Routing!) The routing can either be over a Trunk group or the routing can be
over a Call numbering plan. It must be guaranteed that the Servernumber is in the Call
numbering plan, if this is not so then Callback is not possible.
The Settings „Dial number Length required“, „Maximum waiting time for next digit when
dialing“ and „Hash (#) as call number termination character“ drive the Call planning on
Callback. Because the actual dialled number is not the number that is sent, but sent
within the Subaddress, User-To-User or Data service Information, The dialling must
follow as a Block dial. I.e. the Client must know when the call number is complete. The
call number is considered as complete if:
·
The number of dialled digits match the number within the settings for „Dial
number Length required“. In the case of Block dial where more digits are
received, these will also be sent, the Number as Block dial will not be shortened.
·
Since the last receipt of a digit corresponding to the „Maximum waiting time for
next digit when dialing“ is exceeded This time would be given in seconds
·
A Hash Sign (#) as call digit is received and the Option „Hash (#) as call number
termination character“ is activated.
·
The Information element „Sending Complete“ is received.
It is naturally very important that the Callback profile must be addressed either in the
call number plan directly or in the LCR – module.
If the call is routed over the LCR module the Hash sign (#) will not be accepted by the LCR
Module and the connection will be terminated with Cause 1 (unknown called number).
