How to get aa to pick up incoming call?
RonR:
Quote from: QBZappy on October 26, 2011, 08:33:33 am
You may want to modify it to be more flexible by changing it to:
{(x.2222222222|x.3333333333):aa},{ph}
Have you ever seen the CallerID from a particular phone vary from one call to the next? In my experience, it's very consistent.
jazzy:
Ron, That's exactly why I need to place (2) numbers on the inbound call route.
My work number CID on the Obi history changes between 2 different numbers,
(but the Area Code and Local prefix don't change, just the last 4 digits)
You think that could be the problem why my aa doesn't pick up?
RonR:
I was referring to the leading '1' being present or absent.
You should be able to have virtually any number of CallerID's in an 'aa' rule and as long as one of them matches, the call will go to the Auto Attendant:
{(12222222222|13333333333|14444444444|15555555555|16666666666|17777777777):aa},{ph}
Calls from any of those six numbers should go the Auto Attendant.
jazzy:
Ron, The leading '1' is present in the CID history on my Obi, but the call from work
rings the attached phone. 'aa' did not pick up. I have the default setting of 4000, for the answer delay.
Might that be the problem? How long is 4000, about 4 secs?
BTW, my SP is Google Voice, but that shouldn't make a difference in the aa, right?
RonR:
jazzy,
There's nothing complicated or tricky about sending calls to the Auto Attendant. You should not have to change any other settings. Assuming your Google Voice account is configured on SP1 and you want calls that arrive on that trunk with a CallerID of 12222222222 or 13333333333 to be routed to the Auto Attendant, then set:
Voice Services -> SP1 Service -> X_InboundCallroute : {(12222222222|13333333333):aa},{ph}
If neither of those numbers get routed to the Auto Attendant, double-check the Call History to make sure the number in the InboundCallRoute matches exactly. Try changing the InboundCallRoute rule to a cell phone number or a friend's number and see if that call goes to the Auto Attendant.
If you're absolutely sure you have the correct CallerID in the InboundCallRoute rule, you might try the following steps:
1. System Management -> Device Update -> Backup Configuration (Use OBi Version : checked)
2. System Management -> Device Update -> Reset Configuration
3. System Management -> Device Update -> Restore Configuration
4. Re-enter all passwords (they're not saved in a backup file).
Navigation
[0] Message Index
[#] Next page
[*] Previous page