switched from OBi110 to 200 - autoattendant not working for trusted callers
azrobert:
Try deleting all the Trusted Caller entries then add the rule using OBi Expert.
I create a file using Windows Snipping Tool then use the file as an attachment to a post.
MikeGJ:
tried that - deleted trusted callers, SP1 X_inboundcallroute says ph (as expected); replaced that with {(@.7201234567|@.7207654321):aa},{ph}
and saved, then dialed from first number - call did not ring house line, was ringing on cell then went to VM.
Edited value changing @ back to x, saved and dialed again - went to AA!! But then same thing happened -try a second time from that number and it also didnt ring house line, ringing on cell then went to VM as well. 3rd and 4th tries also go to VM!! Tried x.1720etc and also goes to VM - will now not ring the house line. revert back to Obitalk settings - value goes to back to ph (since no trusted callers) and now calls from my cell go through and ring.
Cant figure out why AA picks up only sometimes and only after making changes, and why @. in the inbound rule should then send the call from the number that matches the rule to VM instead!
drgeoff:
Quote from: MikeGJ on June 02, 2018, 11:25:36 am
If I could figure out how to embed an image I'd show you my call history (clicking on the insert image just puts this code in the text - I dont know what to insert to load an image!) showing the times AA picks up.
Click the "Additional Options" immediately below the text entry box. Click the "Choose file" button and navigate to the folder on your computer that contains the image file. Select the file and click OK or Open or whatever is appropriate for the OS your are using.
In Windows, you grab a screen image by pressing CTRL and Print Screen keys. Paste that from the buffer into an image editing program. Crop as required and then save into a folder for the steps in the above paragraph.
MikeGJ:
thanks for pointing out the additional options - I'd only seen buttons above!
Here's a screen capture of my call history for today showing that the obi always recognizes my cell phone number as 1720xxxxxxx5 but doesnt always use AA1 to deal with calls from it. This has been while I've been playing around with the expert to try and get autoattendant consistently working.
Summary - calls are not routing to the AA with default trusted caller number stored as ten digit i.e. 720-xxx-xxxx; SP1 X_inboundcallroute shows {(x.720------5|x.720------4):aa},{ph}
calling in with cell (first trusted caller ending in 5) results in GV ringing house line
editing value replacing x. with @. stops ohone ringing and sends call to GV VM
resetting value to OBitalk settings (check box; values is as shown above) and saving SOMETIMES results in the NEXT call from cell going to AA; BUT subsequent calls either go straight through and ring or dont ring and go to VM.
Call history showing incoming calls going to AA are ONLY after trying something that didnt work and then resetting to OBitalk values.
I am completely flummoxed.
SteveInWA:
Quote from: MikeGJ on June 02, 2018, 10:16:04 am
thanks for your response - I'd seen another post in day-to-day use regarding the autoattendant not picking up http://www.obitalk.com/forum/index.php?topic=13969.0
and they mentioned something about GV changing its callerID format - they suggested changing x.1 to +1 in the X_InboundCallRoute.
I tried your suggestion of changing x. to @. but all that did was stop my cell ringing the house line instead eventually going to VM.
The referenced thread demonstrated that the solution is to enter +1yourgooglevoicenumber. You instead are trying to use x or @. Why? Just follow the instructions. Take out the x. and replace it with +1 and try again.
This begs the bigger question, why do you want to use the auto-attendant with Google Voice? What is your goal? If you want to call another number from a phone that is linked to your Google Voice account, using Google Voice as the service, you do not need to use trusted callers, or even an OBiTALK device, for that matter. The feature is built into Google Voice, via its own IVR.
Navigation
[0] Message Index
[#] Next page
[*] Previous page