AA not working with Ring.to service
rastoma:
I have an Obi100. Ring.to setup on SP1. Anveo 911 on SP2.
Incoming and outgoing calls work fine. Well fine after I have to reboot the device every couple of days and remove and re-add the ring.to account information in my Obihai control panel.
Anyway, had this about a year now (signed up within a few days of the free Ring.to deal), and since day 1, AA has never worked.
I was told it was a Ring.to issue and that since everything was so new then they were working on it.
But if the Obi device sees the call and rings the phone, then shouldn't the AA answer no matter the service provider?
Yes I have my number(s) as trusted callers. I've tried full 10 and 11 digits (with a 1 and without). I've tried 7 digits with 'Match' checked. I've tried from my home phone (which is Nettalk currently), and from two cell phones. All with every combination of the above. AA will not answer.
I was using GV before Ring.to and switched since Ring.to was free and there was concern that Google would stop working at some point. But even with GV the AA never answered either.
Everything else I guess is working as it's supposed to though I have done no other customizations. Can the device be defective with JUST AA?
drgeoff:
It is very unlikely that just the AA part of your OBi is faulty. It is only a bit of software.
You do realise that AA has to be enabled and configured? By default, incoming calls only ring the phone(s) and do not go to the AA.
rolandh:
This works for me on my OBi 202 using RingTo on one of it's SP slots. My understanding is that it's the OBi, itself, that determines where to send the call (auto attendant vs. phone port) based on matching the inbound Caller ID with the appropriate rule in the relevant InboundCallRoute. All the portal is doing when you add a trusted caller is writing the rule. If I'm correct, I don't believe the service provider matters.
rastoma:
Quote from: drgeoff on March 21, 2015, 12:10:44 pm
You do realise that AA has to be enabled and configured? By default, incoming calls only ring the phone(s) and do not go to the AA.
I have everything set at default, and most all settings are check marked 'OBiTALK Settings'.
Under Voice Service, then AA, there is a check mark on ENABLE. That check mark is there by default. DigitMap, OutboundCallRoute, PrimaryLine, AnswerDelay, CallbackAnswerDelay and NumberOnNoInput all have values there. It's this way even after doing a hard reset (using reset button on bottom of unit and it was reset completely and correctly). The Obi device was removed from Obitalk. Then readded and SP1 and SP2 set up again. And by default AA is enabled.
So I'm confused as to what has to be enabled and configured? What am I overlooking?
azrobert:
Look at the OBi100 Call History to see the format of the CallerID.
Is the CallerID 10 or 11 digits?
To access Call History:
Log directly into the OBi using the local interface.
Key the IP address of the OBi into a Web Browser.
Hit Enter
The UserID and default Password are both "admin".
Click Status on the left column.
Then click Call History.
The CallerID is to the right of Peer Number.
Continue using the Local Interface and go to:
Voice Services -> SP1 Service
Please post the contents of X_InboundCallRoute
For security reasons, modify any phone numbers.
Navigation
[0] Message Index
[#] Next page