Recently bought an Obi200 and am using it with the AT&T Arris gateway. All the ports are forwarded correctly, I believe as seen below, but the Obi setup still can't detect my phone. The **9 test also works and I can hear myself.
(https://i.imgur.com/FDBZhr1.png)
Quote from: Ryutso on December 08, 2020, 11:31:16 AM
Recently bought an Obi200 and am using it with the AT&T Arris gateway. All the ports are forwarded correctly, I believe as seen below, but the Obi setup still can't detect my phone. The **9 test also works and I can hear myself.
(https://i.imgur.com/FDBZhr1.png)
It is rarely necessary to set up any port forwarding on home routers/gateways for OBis to work.
If you had spent 5 minutes glancing at even the titles of recent topics here that would have been of more benefit to you.
drgeeoff
As is often the case with anything OBi it is NOT clear how to get the server to answer up to configure the OBi device.
I SEARCHED the forum and found NOTHING about the problem AND looked at the most recent postings.
You will notice that one of those posts, by me, tries to help a new user and describes this problem
and the workaround rather than telling him to go read.
I used to get that on Linux forums all the time which is why Linux never grew to replace Winblows in the consumer market.
If you leave the "I want to configure Google Voice on this device." it may not work. It didn't for me earlier today.
I added the device without a GV #, then added my 2 GVs AFTER the device showed in the Dashboard.
This was never a problem before (I began using GV on a 110 years ago and a 212 immediately after the 110 stopped working with the 110) but as is common when trying to make it "easier" for people it doesn't work correctly OR is described incorrectly.
It MAY for a user with no GV # on a newly purchased device, but that is just a supposition.
It's caused by OBi's bad programming or their incomplete description which should say something like
"Users with new, unconfigured devices leave the configure Google Voice on this device" box checked.
All others uncheck the box."
Ryutso's problem is probably the one I describe above.
Simple cure. Eliminate the automation.
Quote from: DownSouth on December 08, 2020, 08:12:17 PM
drgeeoff
As is often the case with anything OBi it is NOT clear how to get the server to answer up to configure the OBi device.
I SEARCHED the forum and found NOTHING about the problem AND looked at the most recent postings.
You will notice that one of those posts, by me, tries to help a new user and describes this problem
and the workaround rather than telling him to go read.
I used to get that on Linux forums all the time which is why Linux never grew to replace Winblows in the consumer market.
If you leave the "I want to configure Google Voice on this device." it may not work. It didn't for me earlier today.
I added the device without a GV #, then added my 2 GVs AFTER the device showed in the Dashboard.
This was never a problem before (I began using GV on a 110 years ago and a 212 immediately after the 110 stopped working with the 110) but as is common when trying to make it "easier" for people it doesn't work correctly OR is described incorrectly.
It MAY for a user with no GV # on a newly purchased device, but that is just a supposition.
It's caused by OBi's bad programming or their incomplete description which should say something like
"Users with new, unconfigured devices leave the configure Google Voice on this device" box checked.
All others uncheck the box."
Ryutso's problem is probably the one I describe above.
Simple cure. Eliminate the automation.
1. Lots of posts over the last few weeks. Some examples:
http://www.obitalk.com/forum/index.php?topic=17663.0
http://www.obitalk.com/forum/index.php?topic=17699.0
http://www.obitalk.com/forum/index.php?topic=17672.0
http://www.obitalk.com/forum/index.php?topic=17641.0
http://www.obitalk.com/forum/index.php?topic=17630.0
http://www.obitalk.com/forum/index.php?topic=17613.0
http://www.obitalk.com/forum/index.php?topic=17644.0
2. The problem is that the Obihai server gubbins has gone into "flakey" mode and Obihai support don't have the know-how or the motivation to fix it.
Quote from: DownSouth on December 08, 2020, 08:12:17 PM
If you leave the "I want to configure Google Voice on this device." it may not work. It didn't for me earlier today.
I added the device without a GV #, then added my 2 GVs AFTER the device showed in the Dashboard.
This was never a problem before (I began using GV on a 110 years ago and a 212 immediately after the 110 stopped working with the 110) but as is common when trying to make it "easier" for people it doesn't work correctly OR is described incorrectly.
I appreciate the attempt, but sadly unchecking that box also failed. Looks like the backend registration process really is fucked.