Auto attendant not working, won't answer

<< < (4/4)

rastoma:
Quote from: azrobert on July 14, 2014, 09:26:51 pm

Quote


This probably won't work but try it anyway:
{14805551212:aa},{ph}



No, tried that, didn't work :(

rastoma:
Quote from: HDFLucky on July 15, 2014, 09:16:18 am

If you are making all changes within the Expert menu (IOW, not making some changes directly via the local ip),

Yes, I have tried multiple ways.  Doing all changes in Export mode in the dashboard.  Going back to defaults and then doing all changes directly via the local IP.  Nothing works except for {aa}.  Either in expert mode or via local IP, {aa} works every time for all incoming calls.

Quote from: HDFLucky on July 15, 2014, 09:16:18 am

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. ;)


Well, I did click on Reset Configuration under System Management when logged directly into the device.  That caused me to have to delete SP2 in the Dashboard and setup ring.to again.  I have not used the physical reset  button on the device itself.

I sent ring.to a support email late last night asking how to check call logs in my ring.to account and someone replied not long ago.  Unfortunately the feature to check call logs for SIP clients has not been implemented yet but will soon.  He stated they have not tested Obi's AA.  He asked me for the settings I have been trying and he's going to set one up on his end to see what happens.  I'll let you know what he finds out.

rastoma:
I wish I had tried this yesterday instead of wasting a lot of time on getting AA to work while subscribed to ring.to

And thank you very much to hdflucky and azrobert for all your time and help.

So what I did was delete my Obi device from the dashboard.  Reset the Obi100 using the reset button on the bottom of the unit to make sure everything is back to factory default settings.  I readded my device.  Setup anveo911 and ring.to again.  This time I put ring.to on SP1 just for the heck of it to see if it would make a difference.  Nope.  No difference.  {aa} still worked to make AA answer all calls, but no way to get it to answer on just one specified number.

So.... deleted ring.to configuration again.  Configured a previously never used Google Voice number on SP1.  Clicked on trusted caller in the Dashboard, entered my cell number.  And voila!!!  AA answers on just my number now like it's supposed to.

Now I just wait to hear back from ring.to to see how/why my Obi device receives CID correctly showing my cell number when I call my ring.to number, but Obi AA won't answer like it should.

rastoma:
Got another reply back from a tech/CSR at ring.to.  BIGGGG thumbs up to ring.to thus far.  I know it's just one support ticket.  But so far I'm impressed at their desire to help me with something that's not really a feature of their own service.

Brad (don't know his last name to give him proper kudos) was able to duplicate this issue on his end.  So it's definitely related to how ring.to is sending CID (I'm assuming it has to be CID related as that is what triggers AA I think).  

Anyway, he's pushing this to the engineering team at ring.to.  He said it will likely be the end of next week before they will be able to start debugging it.  Which is OK.  I do need the feature as it worked before.  And I know their main task is ensuring the core functions... ie sending/receiving calls comes first.  But knowing Brad's quick responses thus far I do feel at ease and believe they will get this sorted.  And I can still get the same functionality using THEIR AA, though I can't press a key to have the call go through anyway in case I need to reach someone on that phone, or have the system do a call back.

All in all, I'm very pleased with ring.to thus far.  Call quality is great and their support thus far is great.  I'm really glad they and Obi teamed up.  I wish I could change this topic to add ring.to in the subject line in case others are having this issue... AND so more people will see my great experience with ring.to thus far.

Navigation

[0] Message Index

[*] Previous page