News:

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

Main Menu

How to get aa to pick up incoming call?

Started by jazzy, October 26, 2011, 07:24:46 AM

Previous topic - Next topic

jazzy

I'm trying to get the aa to pick up when I call from work.

I've set up the incoming route on SP2 like this:

Voice Services -> SP2 Service -> X_InboundCallRoute : {(12222222222|13333333333):aa},{ph}
where the 2's=work number A and the 3's=work number B

When I call from work, the attached phone rings, and I don't get the aa options.
Was trying to get option 2, to make an outgoing call using SP2 from my Obi,
when I call from my work number.

Dale

does the work phone send the leading 1 in the caller id ?

jazzy

Yes, the incoming call from work has the leading '1'
in the caller ID .  Verified it in History.

QBZappy

Quote from: jazzy on October 26, 2011, 07:24:46 AM
Voice Services -> SP2 Service -> X_InboundCallRoute : {(12222222222|13333333333):aa},{ph}
where the 2's=work number A and the 3's=work number B

Have a look at the OBi CID. Make sure that the number in the InboundCallRoute is the same as what you see in the call history.

You may want to modify it to be more flexible by changing it to:
{(x.2222222222|x.3333333333):aa},{ph}
Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.

jazzy

I'm quite sure the number I placed in the Inbound call route, is the same
as what showed up in the Obi CID history.  I'll have to double check
when I get home later this evening.  Other than that, are there any other
settings that I'm missing in the Obi, to get the aa to answer so I
can get the aa choices?

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).

jazzy

Ron, I had one of the extensions incorrect in
the inbound call route, so 'aa' works fine now.
Thanks!

Is there a way to have all extensions at my work to roll to
the 'aa'?  1222222xxxx  ( where xxxx are any 4 digits )

RonR

Quote from: jazzy on October 27, 2011, 04:18:08 PM
Is there a way to have all extensions at my work to roll to
the 'aa'?  1222222xxxx  ( where xxxx are any 4 digits )

As long as you own all the xxxx digit numbers.  If not, anyone else in that range will have access to your Auto Attendant.

jazzy

So I'd put this in the Inbound call route?

Voice Services -> SP1 Service -> X_InboundCallroute : {1222222xxxx:aa},{ph}