News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Auto Call back without AA answering - Question?

Started by larrybob, December 21, 2011, 09:56:34 PM

Previous topic - Next topic

larrybob

 I would  like to use auto callback. Where aa calls back the incoming number if the caller hangs up before AA answers.

the admin guide recommended the following
To the line port  INBOUND CALL ROUTE
{(<**1>(x.12121559801|4089913313)):aa($1)} for auto call back if 12121559801or 4089913313 calls and hangs up


This would use sp1 .  To use the PTSN LINE I WOULD USE **8 INSTEAD.
{(<**8>(x.12121559801|4089913313)):aa($1)}

Is the <**8> needed if the PTSN line is the primary line for AA? or can it be left out?
Will this work the same way ?
{(x.12121559801|4089913313):aa($1)}

If i want to reach the AA and not hang up... do i need to add a second rule?

{(<**8>(x.12121559801|4089913313)):aa($1)},{(x.12121559801|4089913313:aa}

which is correct choice  1),2), or 3)
1){(<**8>(x.12121559801|4089913313)):aa($1)},{(x.12121559801|4089913313:aa},{ph}
2){(x.12121559801|4089913313):aa($1)},{(x.12121559801|4089913313:aa},{ph}
3){(x.12121559801|4089913313):aa($1)},{ph}

Thanks Larry


Finally, I noticed that to make this change, I had to uncheck OBI talk. Now  the circle of callers no longer updates the line port  INBOUND CALL ROUTE . It seems that if you want auto callback the use the circle of callers must be deactivated?

RonR

#1
Quote from: larrybob on December 21, 2011, 09:56:34 PM
the admin guide recommended the following

The OBi Device Administration Guide is incomplete, unclear, and confusing.

An Auto Attendant rule is simply:

{[caller-id:]aa[(callback-number)]}

caller-id and callback-number are optional.

If caller-id is present, only matching callers are sent to the Auto Attendant.

caller-id may be a literal string or a DigitMap expression.

If callback-number is not present, the Auto Attendant answers after AnswerDelay milliseconds.

If callback-number is present, the Auto Attendant answers after CallbackAnswerDelay milliseconds.  If the caller hangs up before the Auto Attendant answers, the Auto Attendant initiates a call to callback-number.

callback-number may be a literal string or $1.  If $1 is used, the caller's CallerID (optionally modified by a caller-id DigitMap expression) will be used if the Auto Attendant initiates a callback.

In all cases, the Auto Attendant initiates a callback using its DigitMap, OutboundCallRoute, and PrimaryLine.    If a DigitMap expression is used for caller-id, service route access codes (**n) may be used to override the PrrimaryLine.

Common examples of Auto Attendant callback usage might be:

{12341234567:aa($1)}

Calls from 12341234567 will be answered by the Auto Attendant after CallbackAnswerDelay milliseconds.  If the caller hangs up before the Auto Attendant answers, the Auto Attendant will initiate a call to 12341234567 using its DigitMap, OutboundCallRoute, and PrimaryLine.

{(<**8>(12341111111|12342222222)):aa($1)}

Calls from 12341111111 or 12342222222 will be answered by the Auto Attendant after CallbackAnswerDelay milliseconds.  If the caller hangs up before the Auto Attendant answers, the Auto Attendant will initiate a callback to the caller using its DigitMap and OutboundCallRoute.  **8 will be prepended to the caller's number, causing the LINE Port to be used instead of the PrimaryLine.

{(1234555xxxx):aa($1)}

Calls from 1234555---- will be answered by the Auto Attendant after CallbackAnswerDelay milliseconds.  If the caller hangs up before the Auto Attendant answers, the Auto Attendant will initiate a callback to the caller using its DigitMap, OutboundCallRoute, and PrimaryLine.

{aa($1)}

All incoming calls will be answered by the Auto Attendant after CallbackAnswerDelay milliseconds.  If the caller hangs up before the Auto Attendant answers, the Auto Attendant will initiate a callback to the caller using its DigitMap, OutboundCallRoute, and PrimaryLine.

NOTE:  There is a bug in the Auto Attendant.  If the Auto Attendant initiates a callback and the called party selects option 3 (enter a callback number), everything will proceed normally and as expected, but no callback will be made and no error will be reported.

Quote from: larrybob on December 21, 2011, 09:56:34 PM
It seems that if you want auto callback the use the circle of callers must be deactivated?

If you're using the OBiTALK Web Portal and you make any changes to InboundCallRoutes, it becomes your responsibility to do the 'Circle-of-Trust' (CallerID matching) in your InboundCallRoute rules.

larrybob

#2
Then setting the PTSN line as the primary line for the AA, Choice 3) would be what would be correct to use?

so if obitalk created this :
{(x.12121559801|4089913313:aa},{ph} for cirlcle,of numbers

then changing to this:
{(x.12121559801|4089913313:aa($1)},{ph} should add the automatic call back to all the numbers in the circle.

( I could add all the trusted numbers in obitalk, then go in to the expert configuration, uncheck obitalk and default, and change aa to aa($1).


Larry

RonR

#3
Circle-of-Trust is nothing more than CallerID matching in an InboundCallRoute rule.  If you make 12341234567 a trusted number, the OBiTALK Web Portal simply makes an InboundCallRoute rule to the Auto Attendant:

...{12341234567:aa}...

If you make 12347654321 a trusted number in addition to 12341234567, the OBiTALK Web Portal simply changes the InboundCallRoute rule to:

...{(12341234567|12347654321):aa}...

If you take control of any OBi setting through the OBiTALK Web Portal (such as an InboundCallRoute), you are on your own with that setting and the OBiTALK Web Portal will not add anything back into it or touch it in any way from that point on.


Auto Attendant Option 3 has nothing whatsover to do with InboundCallRoute rules.  Option 3 collects a callback number by having the caller enter it, hangs up, and places a call to that number using the Auto Attendant DigitMap, OutboundCallRoute, and PrimaryLine.

An InboundCallRoute rule employing aa($1) has nothing whatsoever to do with Auto Attendant Option 3.  The aa($1) rule collects a callback number from the incoming caller's CallerID and then places a call to that number using the Auto Attendant DigitMap, OutboundCallRoute, and PrimaryLine.

If you have 5 trusted callers that you want to be routed to the Auto Attendant with the option of being called back if they hang up before the Auto Attendant answers, simply make the following InboundCallRoute rule and don't bother with the OBiTALK Web Portal Cirle-of-Trust:

InboundCallRoute : {(12341111111|12342222222|12343333333|12344444444|123455555555):aa($1)}

You can make it even nicer to maintain by using the following InboundCallRoute rule instead:

InboundCallRoute : {(Maac):aa($1)}

and putting all your trusted Auto Attendant Callback numbers in a User Defined DigitMap:

User Settings -> User Defined Digit Maps -> User Defined Digit MapX
Label : aac
DigitMap : (12341111111|12342222222|12343333333|12344444444|123455555555)

larrybob

I changed my notation to choice 3) instead of option 3) . I was referring to possibilities to pick from in my original post. Not the choices of the Auto attendant.

Larry...