Google Outbound Not Working After Years
Michael_Reeder:
Looking at the other symyst thread:
I don't get played a recorded message on outbound calls - it just hangs up after one ring and I get dial tone.
My SP2 Configurations (where I use Google Voice) say "Connected" on all three devices whether or not outbound calling is working.
Yes - I can log into and out of the Google account through a web browser. As previously mentioned, I have deleted and reconnected my GV accounts to both Obi202 routers.
Looks like I have tried the rest of the suggestions there, including SteveInWA Google Voice primer...
I've logged onto the webpage of my #2 Obi100 home device (since I'm there right now) and am looking around for anything maybe useful...
Under call history I see what looks like a successful call with "Call Connected" and the same start and end time for the call. This is for a failed call that just hung up on me.
Under call history I also see a 3 second call that might have been a successful call on 4/30/17. On 5/1/17 is a "call connected" with NO time elapsed that likely failed.
If I go under "Voice Services", "SIP Credentials" I see old wrong "AuthUserName" and "AuthPassword" information from a different VoIP phone provider I used to use. From discussion in another thread I don't believe this matters at all as Google Voice uses a different authentication mechanism through the Obitalk panel. Sure enough - when I go into the same area on my WORKING Obi202 device, the old wrong info is there. So I don't think this matters at all...
I'm out of ideas again.
-- Michael
sjmyst:
Michael,
From what another user on my other thread says, it sounds like you're right about the user/pass on the device. Seems to use different authentication now.
BTW, my stuff just started magically working.
You can read about it more in my other thread. But, basically I just needed to take a break. So, I left with it broken, and came back to it working.
We did have a storm and a power outage. So, the device did get a power reset. I can't imagine that helping. Especially since I had rebooted the device MANY times before that. But, it was probably the first time I physically removed power. So, there you go...
The only thing I can think is that either my activity to delete my device on OBiTalk and recreated it EVENTUALLY worked (maybe something needed to be distributed?). Or, maybe nothing was really wrong (nothing had really changed), and somebody kicked something at OBiHAI or GV to make things work again.
Hopefully things started working for your also. Best of luck!
Let me know if you want me to try anything to compare to my situation. But, it really sounds like you've got something else going on there.
Regards,
sjmyst
sjmyst:
Re-reading your symptoms made me think about the Echo Test feature. I'm not sure if it will give you anything more than what you already know. But, here's a link just in case it might help:
https://www.obitalk.com/forum/index.php?topic=537.0
Regards,
sjmyst
Michael_Reeder:
sjmyst,
Thanks for your thoughts and ideas. Glad your phones are working.
No luck - my stuff is still broken this morning.
Just played around with echo test. My broken #1 Obi202 is able to complete the echo test just fine.
-- Michael
drgeoff:
It is known (and accepted as not a bug) that although you can have multiple OBi20x devices working on the same GV number, having an OBi1x0 device in the mix can result in not all devices working. Exactly what happens can depend on the order in which devices power up and contact the GV server.
https://www.obitalk.com/forum/index.php?topic=11143.msg73648#msg73648
You mention working fine for some years. In the summer of 2014 Google changed the authorisation protocol. You can no longer configure GV by entering your GV username and password in either the Obitalk portal or the devices's web server. Are you definitely using the new procedure on all the OBis?
Navigation
[0] Message Index
[#] Next page
[*] Previous page