Can't make or receive calls using GVoice since this morning
glenviewjeff:
Steve, thanks for the ideas. I don't have access to another network. I'm using Google Wifi directly connected to my own standalone Surfboard modem. As a workaround, I tried connecting a switch to the Surfboard and connecting Google Wifi and the Obitalk to the switch, but the Obitalk apparently never got an IP granted. Comcast said I should be allowed up to three IPs, so my guess is that may be a limitation with the Surfboard only giving out one.
It seems that Anveo and Google Voice now use similar protocols that each fail in my network configuration. (About a year ago back when GV was working perfectly behind my router, I'd tried unsuccessfully to provision Anveo 911, so it makes sense that it still fails.) Are there other VoIP providers that you know of that I can use with my Obitalk that operate under a protocol similar to the old Google Voice before this change broke so many users' connections?
Thanks,
Jeff
Quote from: SteveInWA on May 26, 2018, 08:29:34 pm
Quote from: glenviewjeff on May 26, 2018, 07:58:11 pm
Right, I never suggested it was a google voice issue; I pointed out earlier that the same problem occurs with Anveo service. I only want it to work at my house on the LAN; I'm sure I could hook up an old router and get it to work with DMZ etc. I get it that you're out of suggestions. Thank you for trying to help. Someone else with Google Wifi did claim success.
Quote from: SteveInWA on May 26, 2018, 05:25:21 pm
Any suggestions? Yes, follow my advice in the post you quoted. Go try it somewhere else. The only thing you know now is:
It works when you take your router out of the path.It fails when your router is in the path.It's not a Google Voice issue.[/]
Why not at least try testing it on some other LAN, at some other location? At least that will be another data point implicating your own router (since you said it works when plugged directly into the cable modem). Speaking of which, if you are using a cable company's "residential gateway", which is a combo cable modem, router and WiFi access point, and you plug your own router into that box, then you should put the cable gateway into bridge mode, so that you are not doing multiple NAT. On the other hand, if you are using a cable modem with no gateway features (e.g. a typical "Surfboard" modem), then this doesn't apply.
RFC3261:
Quote from: glenviewjeff on May 28, 2018, 06:48:54 am
Steve, thanks for the ideas. I don't have access to another network. I'm using Google Wifi directly connected to my own standalone Surfboard modem. As a workaround, I tried connecting a switch to the Surfboard and connecting Google Wifi and the Obitalk to the switch, but the Obitalk apparently never got an IP granted.
For your use case, for testing purposes, connect the OBI directly to the cable modem (no switch, direct), power cycle everything (especially the cable modem), and see if the OBi works with the echo test and GV after everything comes back online. If so (and it is mostly likely), then there is something about your network setup which is outside the responsibility of the OBi, and you likely need to take the issue to the various Google WiFi support forums.
It should be noted that in most cases for residential services Comcast only offers 1 dynamic IP address.
VegasTech:
Quote from: drgeoff on May 28, 2018, 02:51:52 am
1. Temporarily remove the router and connect the OBi directly to your modem. That is not the same as having the OBi in the router's DMZ.
I'll give that a try later today. At least that will confirm or rule-out the router as a problem.
Quote from: drgeoff on May 28, 2018, 02:51:52 am
2. The current Motif implementation for GV trunks on Asterisk will not work when GV turns of XMPP. It is not yet known if an alternative will become available.
Yes, that's going to happen in the next few weeks. I suppose it makes sense to stop fooling with it until then. Come to think of it, that's probably what simonics.com is waiting for.
Thanks.
RFC3261:
Quote from: VegasTech on May 27, 2018, 06:48:00 pm
It's possible that it's a router issue, but router issues don't normally come and go.
Actually, they can, depending on the specifics, and especially when using a dynamically changing connection (the AT&T LTE Mobely has the capability to dynamically choose to change connections whenever if feels like it. The target audience for that device was intended to be casual browsing in your vehicle (that some try to use it for their home connection is a contributing reason AT&T has ended the availability of the product/service as it was originally offered (a flat $20/mo unlimited data)).
And one thing to understand that with the AT&T Mobley data connection is that you are typically double nat'ed (someone once claimed triple nat'ed, but I think they had a more complex configuration with their own router too) which can generate all sorts of challenges, compounded by the changing LTE connection.
The only thing I can think of would be to connect an additional router between the Mobley and your clients which uses a connection to a VPN provider so that you can bypass the various AT&T translations and/or blocking and connect everything to that router. It might work. It might not (I am not even sure the VPN connection would reliably stay up).
glenviewjeff:
Oh my goodness; this is a bit ridiculous given that I'd been without phone service for a frustrating two weeks or so since Google Voice made changes and Polycom modified the firmware.
Long story related to my failed attempts at multiple routers before finally moving to Google Wifi mesh, but I had an old router I was still using as a switch (with Wifi disabled) in my office. For some (forgotten) networking reason I had to plug the incoming LAN cable (now connected to the Google WiFi LAN port) into the "Internet" port of my old router, which was of course causing double NAT and probably other VoIP-destroying firewalling.
This now unnecessary connection had worked fine before the Obitalk firmware upgrade, but broke VoIP services subsequently. All it took was moving the ethernet cable over to the LAN side of my router so no additional NAT is being performed. I'd been procrastinating replacing the router with a simple switch, but I should get around to it since it is probably costing me a bit in wasted electricity.
Navigation
[0] Message Index
[#] Next page
[*] Previous page