Auto attendant not working, won't answer
rastoma:
Quote from: azrobert on July 14, 2014, 08:26:32 pm
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......".
The AA I get when I forward my ring.to number to my cell and then call that same number from the cell is an AA from ring.to. It says to enter the number you would like to call from your 'ring.to' number. Basically it performs the same function I'm trying to do with the Obi AA. I need to return calls using my voip number as the caller ID. It just bugs me when something that should work doesn't :)
Quote
Try X_InboundCallRoute: {(@.4805551212@.):aa},{ph}
I'm guessing here. Maybe there is a blank before or after the callerid. @ will match almost everything.
Unfortunately that didn't work either (yes I substituted my 10 digit phone number). So far {aa} is the only option that will make the Obi AA answer but of course I don't need every caller to reach the AA :)
I submitted a ticket to ring.to. Since it's still fairly recent that they have offered service a preferred provider through Obitalk, I asked them has there been any other reports of ring.to users having trouble with the Obi AA. Call log does show my cell number correctly (with a 1 in the front so it's 11 digits). Obi is seeing my number so it just doesn't make any sense that it's not triggering AA.
HDFLucky:
The ! just indicates that you have something other than the OBi default stored - perfectly normal.
As to why axrobert's suggestion did not work… at the risk of asking a dumb question, are you sure you modified the X_InboundCallRoute for sp2, and you remembered to click Submit, and waited for the box to reboot before testing?
azrobert:
Quote
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.
No, this is not normal. The phone should not ring.
This probably won't work but try it anyway:
{14805551212:aa},{ph}
rastoma:
Quote from: HDFLucky on July 14, 2014, 09:22:33 pm
As to why axrobert's suggestion did not work… at the risk of asking a dumb question, are you sure you modified the X_InboundCallRoute for sp2, and you remembered to click Submit, and waited for the box to reboot before testing?
No dumb question here, because this is crazy :) And I appreciate all the effort both of you are making.
Yes I have double checked that I am using the X_InboundCallRoute for SP2. I scroll to the bottom and click on Submit. Now I have not rebooted the box when trying these. Does clicking submit reboot the box or am I supposed to reboot manually? The {aa} worked without me clicking on reboot afterward so I have only been clicking Submit thus far.
HDFLucky:
This is a challenging one all right! I don't if your 100 is different, and it's probably moot at this point, but here's how it works in my OBi202 using Expert mode:
10 seconds after clicking Submit, power light starts flashing6 seconds after power is back on solid, the phone lights flash 3 times3 seconds after the phone lights are back on solid, reboot is complete and dial tone restored
In any event, power cycling (i.e., pull the plug for ~10 seconds) accomplishes the same thing. If you are making all changes within the Expert menu (IOW, not making some changes directly via the local ip), then I'm out of ideas… but at least my post will bring your thread to the top, where it will be seen by the heavy hitters on here :)
I don't remember who wrote it, but it was someone whose opinion here I respect, that these units can sometimes get into a state that simply can't be explained by the settings (which look totally correct, as they do in this case). But deleting everything, factory resetting, and then putting everything back fixes it. I'm not expert enough to say we are at that point, but I think we're getting close. ;)
Navigation
[0] Message Index
[#] Next page
[*] Previous page