Auto attendant not working, won't answer
azrobert:
Check the call history again and make sure the callerid (Peer Number) is correct.
This is probably a dumb question, but is the call coming in on SP2?
Terminal ID in the call history will be SP2.
For a test to see if the Auto Attendant is working change the SP2 InboundCallRoute to {aa}
rastoma:
Quote from: HDFLucky on July 14, 2014, 07:42:06 pm
Hmm, have you used OBi Expert mode to make changes to DigitMap or OutboundCallRoute in Voice Service > Auto Attendant? If so, post what you have now.
I haven't touched any other settings anywhere. I even reset the obi box (100) to default, deleted my ring.to account in obitalk dashboard, and added it back again. I just did that last night and since then the only option touched any where is the suggested info in X_InboundCallRoute. Well, I first tried trusted caller option and then tried the custom entry in advanced settings.
I just figured out how to get it to answer but I wish I could get it work as it should. I logged into my ring.to account and forwarded calls to the cell phone that I wanted to use to access AA. So now when I call the ring.to number from my cell, AA immediately answers and asks me to enter a phone number to dial. So I entered the wife's cell number and the ring.to number does show up on the CID which is what I ultimately was needing to do.
Doesn't AA give other options too or by default does it just immediately ask what number I want to call?
Again, it would be nice to know why a trusted caller (or even when using expert settings), doesn't reach the AA. I would really like to be able to access the dashboard if I'm out of town and change or add a trusted caller.
Thank you for your time in helping... if I can provide other details from my account still (even though everything is default otherwise), please let me know and I will get you the information.
rastoma:
Quote from: azrobert on July 14, 2014, 07:45:25 pm
Check the call history again and make sure the callerid (Peer Number) is correct.
This is probably a dumb question, but is the call coming in on SP2?
Terminal ID in the call history will be SP2.
For a test to see if the Auto Attendant is working change the SP2 InboundCallRoute to {aa}
I checked the call history by logging into the device directly using my local IP. It does show terminal ID is SP2 which is correct; ring.to is on SP2 and anveo911 is on SP1.
I entered {aa} as instructed. AA did answer!!! YEAH!!! :) And it's a different AA than I get when calling from my cell phone while the number is forwarded to the same cell. I guess ring.to has their own AA that I didn't know about. It's a female voice that just says to enter phone number to call.
With {aa}, I got a male voice that gave 3 options, 1 to continue with call... and I already forgot 2 and 3 LOL.
But what was interesting, the destination phone rang one time (not a ring that I hear on the phone I'm using, but it actually rang on the destination phone), and then AA answered. Is that normal? I thought AA would answer immediately before ringing the phone.
So.. hope I'm not confusing you.... but yes AA works with {aa}... how can it not work with a specific number?
rastoma:
There are you red ! next X_ServProvProfile, X_RingProfile, X_CodecProfile and X_InboundCallRoute.
It shows a red ! whether I have check mark next to use Obitalk settings or not. Is that normal?
azrobert:
The OBi AA always gives you three options, so I think you are getting a different AA when you forward the call. This sounds more like GV. GV has a female voice and the prompt is something like "You have no new calls. Enter 2 to make a new call......".
Try X_InboundCallRoute: {(@.4805551212@.):aa},{ph}
I'm guessing here. Maybe there is a blank before or after the callerid. @ will match almost everything.
Navigation
[0] Message Index
[#] Next page
[*] Previous page