Can't make or receive calls using GVoice since this morning
SteveInWA:
::)
RFC3261:
Quote from: glenviewjeff on May 28, 2018, 12:08:04 pm
Oh my ...
Thank you for the follow up. All too many individuals just disappear after things start working for them without follow up(*), so we never know the details of the issue(s), or what changed to get it all working again. Multiple levels of nat can, in some cases, work, and in others not so much.
(*) Especially if the root cause is a self-inflicted hole in the foot.
drgeoff:
I have had a double NATed OBi100 for more than 4 years - the ITSP in Japan gives the router a 10.x.x.x address and the router (an ancient D-Link DIR300 running DD-WRT) gives the OBi100 a 192.168.1.x address Never had GV configured on it as its only real use is over the Obitalk network for calls with or through my OBi110 here in the UK. However I have at various times configured several different SIP providers on it, including sipgate.co.uk, pbxes.org and my own FreePBX on my local LAN. Never had an issue that was caused by the double NAT.
However, this thread does appear to have revealed the same or similar problem as in https://www.obitalk.com/forum/index.php?topic=13991.0
RFC3261:
Quote from: drgeoff on May 28, 2018, 12:51:23 pm
Never had an issue that was caused by the double NAT.
Yep, details always matter. So does your router, and the CGN solution your provider offers. STUN and UPnP all can introduce interesting issues as they try to determine how to traverse NAT and/or open ports. And some things try to guess RFC1918 addresses break with providers that use different netblocks that are not RFC1918, but are used like private addresses (and some apps have no clue that 100.64/10 was assigned specifically for CGN solutions).
The only good news is that there is no reason to use NAT with IPv6. The bad news is support of IPv6 SIP is often non-existent.
VegasTech:
In general, I'm going to wait until Google makes changes in the next few weeks and see how it works then. But I did make an additional change to restore incoming calls.
What I did to receive calls reliably was to create a free line at callcentric.com and then forward Google Voice calls to the callcentric number. That works reliably because the connections to callcentric use the sip protocol, which works fine on my Obi200. I'm still making outbound calls with Google Voice, since I can restore Google Voice service temporarily by rebooting the Obi200 from my computer. It's not perfect, but it makes me functional again.
In using the callcentric did for incoming calls be careful to not allow outgoing calls. If you do that you'll get stuck paying 2 cents/minute for outgoing service. Since I already had a PBX server (FreePBX/Asterisk) setup and running, I created a callcentric trunk and incoming route, but no outgoing route. That leaves no possibility for outgoing calls through callcentric. I have the Obi200 connecting to my PBX server as a generic sip device to receive calls on SP2. If I had it to do over again I would probably put callcentric on SP1 and Google Voice on SP2 so I don't get the double ring on incoming calls, but since it's only temporary I'll leave it alone.
As an additional experiment I've ordered an ObiWIFI dongle so I can connect to the AT&T Mobley directly. That's obviously going to be an improvement because the Mobley also uses nat. So I'm currently using two layers of nat, first through the Mobley and then again through the AC1900 router, which is clumsy. I'll post back later this week on whether connecting directly to the Mobley helped.
SteveInWA has been a terrific resource in the past. I'm sorry to see that he's not taking this issue seriously. But maybe it's a moot point with the upcoming changes in Google Voice connectivity. It could be an entirely new game a few weeks from now.
Navigation
[0] Message Index
[#] Next page
[*] Previous page