Call Back via Auto Attendant on the OBi Device
roundaway:
ianobi,
I'll try it when getting home from work.
Newbie reading call routing and digitmap stuff and had myself confused. Thanks for the info.
Vegetus:
Hi there!
ModelName: OBi202
HardwareVersion: 1.4
SoftwareVersion: 3.0.1 (Build: 3722)
SP1 Service: GV
SP1 X_InboundCallRoute: {(x.3312094854):aa},{ph1,ph2}
OBiBlueTooth 1 InboundCallRoute: {(x.3312094854):aa},{ph1,ph2}
If I call my GV number from 3312094854, the wired phone rings 3 times and the AA answers the call.
If I call the cellphone connected to the ObI via BT from 3312094854 the wired phone rings BUT the AA won't answer the call.
I want to call the cellphone connected via BT, disconnect the call just before the AA answers and get called back by the ObI202 via BT.
Any way to get the automatic (no AA answer) callback work via BT like {(<**8>(x.3312094854)):aa($1)} ?
Thank you very much for your valuable help.
ianobi:
Vegetus - welcome to the forum.
{(<**8>(x.3312094854)):aa($1)} should work the way you describe. The question here is why does aa not recognise {(x.3312094854):aa} when called via the cellphone.
Make an incoming call via the cellphone and answer the call. While the call is ongoing check in the Expert Config Pages > Status > Call Status. See what Peer Number is shown. Alternatively, after the call is finished look in your OBi web page > Status > Call History.
It looks to me like the CallerID (Peer Number) is not being recieved from the cellphone, or is in some way changed.
Vegetus:
Quote from: ianobi on January 27, 2013, 04:57:50 am
{(<**8>(x.3312094854)):aa($1)} should work the way you describe. The question here is why does aa not recognise {(x.3312094854):aa} when called via the cellphone.
It looks to me like the CallerID (Peer Number) is not being recieved from the cellphone, or is in some way changed.
Yes, the cellphone returns as caller ID +393312094854 (I live in Italy). Now AA answers (I have {(<**8>(+393312094854)):aa($1)},{ph,ph2} in OBiBlueTooth 1 InboundCallRoute).
In Voice Services --> Auto Attendant --> CallbackAnswerDelay I have 10000. I call, AA answers, I choose option 3 and I enter my cellphone number: 3312094854 followed by the pound key.
Then AA dials out but prepends 1 to the number 3312094854 I entered and the call goes out via GT1 not BT.
Someone in USA got few unsolicited calls from me. I'm really sorry for that :-(
Please, help me just one more time and teach me how to fix the dialplan and where can I find examples and tutorials about ObI dialplans and configurations. With Sipura devices there where a lot of web sites and forums with examples and discussions. I'm new to ObI products.
Again, thank you for your help.
ianobi:
The basic problem here is that all the OBi DigitMaps are set up for North American dialling patterns. I live in the UK, so I'm used to these problems!
Quote
Now AA answers (I have {(<**8>(+393312094854)):aa($1)},{ph,ph2} in OBiBlueTooth 1 InboundCallRoute).
If you dial in via your cell phone and hang up before the aa answers, then this rule {(<**8>(+393312094854)):aa($1)} will call you back using the OBiBluebooth > DigitMap.
Quote
I call, AA answers, I choose option 3 and I enter my cellphone number: 3312094854 followed by the pound key.
Then AA dials out but prepends 1 to the number 3312094854 I entered and the call goes out via GT1 not BT.
If you dial in via your cell phone allow aa to answer then use Option 3, aa will call you back using its own Primary Line. At default this is probably set to SP1 Service (GT1). The DigitMap for SP1 is found in Service Providers -> ITSP Profile A -> General -> DigitMap. Its default setting is:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.)
You have input a ten digit number starting with "3". This rule <1>[2-9]xxxxxxxxx will take any ten digit number starting in the range 2 to 9 and will prepend "1" to it. Very useful for North Americans - not useful for the rest of us ;)
At default settings, most OBi DigitMaps have the rule xx. this means "any number of any digits", so whatever you dial will get sent. However, the OBi will wait for ten seconds before sending the digits out to make sure that you have finished dialling. Much better to get a good match for your numbers if you can.
DigitMaps are a big subject. This forum has many good examples - search for posts by user RonR among others. The OBiDeviceAdminGuide has a few good bits in, but lots that is not so good!
Be careful about how you choose to update your OBi see:
http://www.obitalk.com/forum/index.php?topic=92.0
This is a friendly forum - feel free to post questions :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page