Can't call out using Google Voice - dead air

<< < (2/2)

PeterG:
No good info from logs.  :(
For some other reason I can't upload a screen capture of the log window, but it shows GTT outgoing call to the correct number, GTALK init session and then GTALK sess state changed from 0 to 2 and nothing relevant beyond that.

I see nothing interesting in my router logs either, noting only that there is an established connection from the Obi's IP to a Google IP.

I ***8 reset and will try a full reset reinstall tomorrow. :'(

PeterG:
To close out my problem:
As I originally posted, I connected my OBI200, updated the firmware and connected to Google Voice, received incoming calls but was not able to place outgoing calls.
As a last resort, I finally decided to delete the device from my account, do a full hard factory reset, and re-configure from scratch.
This, in fact, fixed the problem and I'm able to dial out via either of my connected Google Voice accounts!

rsyslogdfan2020:
I may not have found this post had I not gone through the pain of enabling syslog. (It was exacerbated by the fact I am not on windows.) Your solution worked for me as well. Thank you!

It appears whatever was done to the auto update pathway, didn't allow for an Obi that sat in a drawer for a spell. :'( I wonder how many people just assumed theirs was trash?

After deleting the device from obitalk.com and using the reset in the `Device Update` menu, I was greeted with a new firmware with different branding.

For the curious, getting syslogs for me looked like:
Code:

sudo rsyslogd -f /usr/local/etc/rsyslog.conf -i /usr/local/var/run/rsyslogd.pid
/usr/local/etc/rsyslog.conf:
Code:

module(load="imudp") # udp logs
input(type="imudp" port="514")
*.* /tmp/syslog.log

then:
Code:

tail -f /tmp/syslog.log

Navigation

[0] Message Index

[*] Previous page