News:

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

Main Menu

auto attendant not pickup

Started by cpyby, August 17, 2011, 08:55:58 PM

Previous topic - Next topic

cpyby

I have a google account that the Trusted Caller doesn't ring the AA.  I have 3 obi110 in the US that AA pickup instantly but the 4th obi110 outside US just ring normal.  I tried putting GV on SP2, same problem. 

I then used a different GV account on the same obi, both SP1 and SP2, AA work instantly.  I switched back to the original GV account, no AA.  I even tried manually put X_InboundCallRoute to just AA only (no ph), still no AA pickup.

At first I thought it might be my password so i changed the email password, AA still fail.  Could this be somehow tie to the way I have my google account?  My google email end with 2 digits.

RonR

#1
Calls are routed to the Auto Attendant by having an aa rule on that trunk's InboundCallRoute:

Voice Services -> SP1 Service -> X_InboundCallRoute : aa  (or {aa})

will cause all calls arriving via SP1 to be routed to the Auto Attendant.

Voice Services -> SP1 Service -> X_InboundCallRoute : {(1?(2345550001|2345550002|2345550003)):aa},{ph}

will cause calls arriving via SP1 from 2345550001, 2345550002, and 2345550003 to be routed to the Auto Attendant, with all other calls being routed to the PHONE Port.

cpyby

Thanks RonR. 

Been trying to fix the problem in the last few days.  Just right when I go to sleep thinking about caller ID, I went to check google setting.  Indeed google is using google voice number instead of passing caller's number.  I make the change to pass caller's number and AA work perfectly.

baby007

#3
Hi, I am having the same problem. I tried to set "aa" in the InboundCallRule but auto attendant still not pickup. Please help
Edit: I am setting a landline connected to obi so that auto attendant will pick up all incoming calls from that phone

RonR

#4
Please post the contents of the InboundCallRoute from the OBi itself by logging in at the IP address returned by dialing ***1 (username/password = admin/admin).  Identify which one it is (SP1/SP2/LINE/etc.).

Please describe exactly what you're trying to accomplish.

RonR

Quote from: baby007 on April 24, 2012, 07:41:17 PM
Edit: I am setting a landline connected to obi so that auto attendant will pick up all incoming calls from that phone

Physical Interfaces -> LINE Port -> InboundCallRoute : aa

should send all incoming calls on the LINE Port to the Auto Attendant.

baby007

#6
Perfect. I knew I did something wrong. Big mistake, was trying to set aa in Voice Service.
In case I change my mind, could I set aa to pickup all incoming calls but a specific number?

RonR

Quote from: baby007 on April 24, 2012, 08:00:24 PM
In case I change my mind, could I set aa to pickup all incoming calls but a specific number?

Sure:

InboundCallRoute : {12341234567:ph},{aa}

Calls from 12341234567 will ring the PHONE Port.  All others will go to the Auto Attendant.

baby007

Nice. Originally, I want obi to block advertising calls so I set aa to pickup all calls. But then I realize what if its not a robot - call, then the person calling me can press 1 to continue. can you suggest me something to work on this?

RonR

Blocking nuisance calls is a difficult prolem.  If the calls are anonymous (no CallerID), you can block aonoymous calls.  If the calls come from a relatively small number of known/consistent CallerID's, you can block just those CallerID's.

baby007

its ok, so how I can block those numbers manually?
Can I just block those numbers and let the rest bypass the aa (not listening to aa) ?
Thanks Ron

RonR

InboundCallRoute : {?:},{(12345550001|12345550002|12345550003):},{ph}

This will block anonymous calls and calls from 12345550001, 12345550002, and 12345550003.  All other calls will ring the PHONE Port.

baby007

Thanks so much Ron.
Loving the assistance here