pc44,
larrybob,
I don't think it works that way."$1" is hard coded to represent a number to call back. $1 is used to expand either the CID picked up by the OBi or a number provided by the user after pressing option 3 of the AA. The OBi stores that number (variable) temporarily to make the CBack. I understand from the user guide that there a two ways to initiate a call back:
Method 1) {(<**1>(14089913313|12121559801)):aa($1)}
Scenario - Call in hang up before OBi picks up and the Obi will call back either of the two numbers above if it is recognized in the CID.
This scenario may not work for the OP since CID is not reliable. Hence the problem.
Method 2) Involves selecting Option 3 after the AA picks up.
Scenario - Call in deliberately hit the AA and drop a CBack number (manually or perhaps by speed dial).
I think that you are correct in assuming all calls are to be directed to the AA in order to give the OP a chance to initiate the CBack by pressing Option # 3 + a CBack number. I suspect that a number setup in the speed dial may be a more efficient way of initaing this CBack if it is to be routine. This may work.
Mcallback should be modified to include "x." in the far right end of the line, since you want this rule to be picked up last as a failsafe in order to pick up all CIDs.
{(<**2>(x.)):aa($1)}
Note that all calls will hit the AA. OP should make that number really private and set up the AA PIN.
Since using Option 1 the caller must hangup before the OBi answers, it should not cost anything to try other than cell aire time. It may pick up the CID and CBack. If not try the other method. That should be reliable since it is the user providing the number to CBack.