MobiLink IP
CALL CONTROL
MobilinkIP_Usermanual-sw1.2.21_revGen.doc
Page 119 of 188
The Web interface for Incoming Calls features the button More (when you edit a row, it shows up in
the extreme right, besides Exit).
The pages for Local Users/Mobile Users, allow only
certain
mobile numbers to register to the PBX
But here, in the section for Incoming Calls, all the mobile phones that call to the modules of MobiLink
IP will be registered to the PBX (instead of registering only the numbers that you have inserted in the
table!)
6.7.5. Definition of DCR
Dynamic call routing is
the process of automatically re-routing a call based on specific criteria, instead
of using a static, pre-defined routing table
.
The feature Dynamic Call routing was designed primary to fix the ID issue that arises for calls made
through mobile gateways; from your desk, you ring someone in the filed, but this mobile user cannot
call you back!
From First, the called party cannot see the real phone number (extension) of the calling party; instead
he just sees the number of the SIM card for the GSM module used. When the call is not accepted, or
the called party was busy, when the called party tries to ring back to the number that shows up in
„missed calls”, he will reach only the respective GSM module of the MobiLink-IP gateway and he
cannot be connected to the PBX or to the human operator.
He does not have information about the
real number
of the calling party, he does not know from what
local extension he was called.
To overcome this problem, outgoing calls made through the mobile modules of the MobiLink IP are
stored in the Dynamic CLIP table as they are made.
When the destination rings back, he will be connected automatically to the source of the call. See
below an example:
At 14:00:44, the extension 246 rings, via interface mobile3, the phone number 072xxxxxxx – row 6 is
an outgoing call.
The, at 14:01:55, the user in the field, with phone number 072xxxxxxx calls back.
Row 7 shows an incoming call. His call is automatically connected to the extension 246, who was the
source of the first call. But in the field DNIS you see only a zero, not the value “246”. Why?
Because it is a dynamic list! The value of the destination is stored only
temporary
, then it is deleted
or replaced with a new value. This way, when the user in the field calls back the first time, he will be
connected to the source extension, but when he calls back a second time or later, this value has been
erased, so now he will be connected to the extension that was specified in the filed “Target”!
Also, when the mobile user out in the field has not yet been called by anybody from MobiLink IP, the
DCR feature has not value to operate upon, so when he rings, the remote mobile user will be
connected to the extension you have set in the field “Target”.
