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.