triggering a callback without Obi answering the call
lk96:
thanks for the responses on the trunk group. Will experiment shortly.
However, I just tried a basic experiment to see if I will get a call back and
the Obi doesn't seem to call back. Below is the inbound call route config:
{kkkkkkkkk|mmmmmmmmm):aa},{(nnnnnnnnnnnn):aa(xxxxxxxxxx)},{ph}
where:
kkkkkkkkk is an Obi #
mmmmmmmmm is another Obi #
nnnnnnnnnn: is the 12 digit incoming international phone exactly as captured in the Obi call history
xxxxxxxxxx: is a US based GV # (I didn't want obi to call back a european # that is in roaming). This
# should have been dialed over the primary line (LINE in this case). I also did an experiment
to send that call over SP1 (by prefacing the number with **1).
Do I miss something ?
L.
RonR:
Quote from: lk96 on January 13, 2012, 01:06:46 pm
{(nnnnnnnnnnnn):aa(xxxxxxxxxx)}
The parenthesis around nnnnnnnnnnnn isn't needed (they do no harm).
A call from nnnnnnnnnnnn which is aborted before the Auto Attendant answers should cause the Auto Attendant to initiate a callback to xxxxxxxxxx using the Auto Attendant PrimaryLine. This is assuming that the Auto Attendant DigitMap and OutboundCallRoute match the xxxxxxxxxx number.
You can test the nnnnnnnnnnnn CallerID match by not hanging up and seeing if the Auto Attendant answers.
You can test the Auto Attendant's ability to call xxxxxxxxxx by dialing **0, pressing 2, then entering xxxxxxxxxx#.
lk96:
I figured out why I was not getting the callback: even the 10sec interval was too short.
In fact (and unfortunately) the AA was picking the real call (it will be
a really expensive one). So once I increased this
and kept track of the time I was on the phone while getting the ring back
I did get the call back.
However, it seems that I hit some issue related to the use of trunk groups for the call back:
so I used a syntax like aa(tg1(1nnnnnnnnnn)) to tell the AA to use TG1 to callback the indicated number.
In the configuration of TG1 i replaced the default sp1, sp2 with li1 in order to force
the call out of LINE interface (just as an experiment).
The net result is that I did get the call back but not through the
LINE interface. When I went in the call history, the call was shown that went out through
TG1(1nnnnnnnnnn). But this does not tell me which actual interface was used.
Based on my Obi config I'm fairly certain though that the call went out through SP1
(because the above destination number would not be dialable through SP2 and have
validated that manually).
May be I'm pushing my luck here but ...any ideas ?
Is it possible that you can't have the AA use a TG to call back ?
lk96:
sorry but this was a false alarm. The history did show the call used LINE1 interface.
And when I picked up the *correct" handset to "eavesdrop" on the returned call, I confirmed
that thing worked out fine.
So this is good news that using a TG in the AA callback definition worked as expected.
L.
Stewart:
What services do you have set up on your OBi? Which country SIM(s) do you have? In which countries will you be traveling?
I'm asking this, because there are probably ways to set up the OBi to have two or more callback choices, using local numbers dialed from the EU mobile. I live part time in France and use a prepaid phone there. My OBi is set up so I can dial one Paris number and get a callback via Voxbeam, or dial a different Paris number and get a callback via Orange.
There are also commercial callback services (more expensive than using the OBi, but still fairly reasonable) that can serve as a backup. Take a look at Fonworld and Future-Nine.
Navigation
[0] Message Index
[#] Next page
[*] Previous page