Automatic call back digitmap question for Anonymous calls

<< < (2/2)

pc44:
Update <- ;D

It seems as though the following should work:

{(x.):aa(**25551231234)}

...where 5551231234 is whatever specific number you want to use.  The **2 that comes before your desired number is optional, in the event that you want to route the callback through SP2.

The good news is that I tested this using an anonymous call block, and the AA still performed the callback to the desired, target number.  The only problem is that I am unfamiliar with the AA and also do not have sufficient landlines available right now with which to do more testing.  For reference, I read this from the OBi Device Admin Guide's AA Callback Service:
Quote

A rule can be added to the InboundCallRoute parameter to have the AA call back the caller’s or any other number, if the caller hangs up before the AA answers. The rule should indicate that “aa(callback-number)” is the target destination of the call, where callback-number is the number that the AA should call back if the caller hangs up before the AA answers the call.

Hope it helps,
pc44

QBZappy:
Quote from: pc44 on June 24, 2012, 08:29:55 am

It seems as though the following should work:

{(x.):aa(**25551231234)}


I could reproduce the CBack with a static number, however the (x.) didn't do anything for me. It worked when I replaced it with my cell number eg:
{(5145551212):aa(**25551231234)}

This still leaves me without the ability of receiving a CBack call without proper CID being picked up. This may just be a small detail in the inbound rule. It seems that the $1 variable can be hard coded by the user. To block my CID using my cell I need to press #31# + number. Result on the receiving phone is "Private number". What did your CID show in the call history when you did *67?

pc44:
Quote from: QBZappy on June 24, 2012, 10:05:49 pm

I could reproduce the CBack with a static number, however the (x.) didn't do anything for me. It worked when I replaced it with my cell number eg:
{(5145551212):aa(**25551231234)}

This still leaves me without the ability of receiving a CBack call without proper CID being picked up. This may just be a small detail in the inbound rule. It seems that the $1 variable can be hard coded by the user. To block my CID using my cell I need to press #31# + number. Result on the receiving phone is "Private number". What did your CID show in the call history when you did *67?


Good question.  I'm looking at the call history, and this is what I am finding for my *67 call to the OBI:
Quote

Call 18   06/24/2012    10:54:23   
Terminal ID   GoogleVoice4   AA1
Peer Name      
Peer Number      
Direction   Inbound   Inbound
10:54:23   Ringing   
10:54:31   End Call

Peer number and peer name were just blank.  Maybe we need to modify the (x.) to something else to account for the Private Number scenario.  Maybe (x.|@?) would allow for the alphanumeric "Private number," but there must be a cleaner way to write that.

pc44

QBZappy:
pc44,

Call Back (Set up with a static CBack number)
{(x.|@?):aa(5145551212)}
Note to force over a specific SP we can use the optional **1/2/8 for OBi110  eg **25145551212

I tested this and it worked in both of the following cases:
1) OBi call history Peer Name & Peer Number both blank
2) OBi call history Peer Name & Peer Number both populated with name and number

This should force all incoming calls to the OBi to CBack to a preset number irregardless of what CID is picked up or if CID is blank. Users can call in, and hang up after the first ring avoiding long distance charges.

A side note to this is that you can also trigger a CBack in this manner by using GTalk using a computer. The OBi call history shows the name of the GTalk incoming caller. I guess this is a not too obvious web Call Back feature of the OBi.

pc44:
QBZappy,

Thanks for testing and confirming this on your end!  It's great to know that it works.

Quote from: QBZappy on June 25, 2012, 10:50:49 am

A side note to this is that you can also trigger a CBack in this manner by using GTalk using a computer. The OBi call history shows the name of the GTalk incoming caller. I guess this is a not too obvious web Call Back feature of the OBi.

I had not even thought of that side note.  That's a nice alternate method for triggering AA callback.

Nice work,
pc44

Navigation

[0] Message Index

[*] Previous page