Google Voice Hangs at "Configuring...."
sfbphone:
first time user, OBi200 wont connect to GV
for awhile status was going from "configuring" then "Registration Not Required"
now status goes to "configuring" then "Connecting to 64.9.240.172" but stalls there
do i need to just wait for them to finish the changes this week?
SteveInWA:
Quote from: sfbphone on June 21, 2018, 12:39:50 pm
first time user, OBi200 wont connect to GV
for awhile status was going from "configuring" then "Registration Not Required"
now status goes to "configuring" then "Connecting to 64.9.240.172" but stalls there
do i need to just wait for them to finish the changes this week?
I wish I had a firm root cause for that symptom. I had the same issue during the early beta test of the new firmware, and it just went away. A few others reported the same symptoms. What firmware build number is your OBi 200 running now? Pick up the attached telephone and key in ***0 then 1# to hear it read out. We just need the last four digits.
sfbphone:
3.2.2.5859
SteveInWA:
Thanks. So, your device has already been updated with the new firmware in support of Google Voice.
Have you tried deleting the device off of your OBiTALK dashboard, resetting it*, then adding it back and reconfiguring it? This may solve the issue.
*after deleting it from the OBiTALK dashboard, wait a few minutes, then unplug the Ethernet and power cords, leaving the telephone cord plugged in. Plug in just the power cord and wait for it to boot up. Pick up the phone and press ***8 then 1 to restore it to factory defaults. Let the device sit for several minutes, while the LEDs blink through the various steps in the reset process. Then, unplug it from power again, and then plug in the Ethernet cord and the power cord again. After it boots up, repeat the **5xxxx procedure to add it back to your OBiTALK dashboard and to configure Google Voice. When you configure GV, look closely at the various windows and dialog boxes that appear. Make darn sure that the Gmail address shown, when it asks you to grant OBiTALK access to your Google VoIP service is the correct address.
It may take several power-cycles and some waiting after you do all of this, for it to end up showing "Connected" status. Be patient and let it sit a while after completing the Google Voice configuration step.
RFC3261:
Quote from: SteveInWA on June 21, 2018, 02:19:57 pm
I wish I had a firm root cause for that symptom.
I do not really have any additional clue, but my WAG (when I first converted and saw this) was that the repeated connection attempts due to all the reboots, firmware updates, resets, etc. caused GV to put my device into the deferred connection bin (which is a very common approach to repeated connection attempts when doing anomaly and attack detection; a few initial minor infractions are ignored until you reach some threshold, and then are sent to the penalty box to wait until you have cooled off).
Navigation
[0] Message Index
[#] Next page
[*] Previous page