Google Voice on Obi200 Connect Failed: No Response
drgeoff:
Quote from: mike1971 on June 03, 2019, 02:57:12 pm
Google had a major outage with cloud services yesterday that effected alot of google systems, including voice. Should be better now.
https://www.theregister.co.uk/2019/06/04/google_outage_botched_server/
ShazamInForum:
Meridius,
Dial **9 222 222 222 Echo Test and tell us if echo test failed or successful. Also, lower your router firewall settings to low or disable it and try adding/authenticating your Google Voice service again.
And ports to open in your router: https://www.obitalk.com/info/faq/Troubleshooting-sec/ports-to-keep-open-on-my-router
Good luck!
drgeoff:
Quote from: ShazamInForum on June 04, 2019, 02:16:56 pm
And ports to open in your router: https://www.obitalk.com/info/faq/Troubleshooting-sec/ports-to-keep-open-on-my-router
Most of that is totally irrelevant. Not a single one of the dozens of home routers I have examined has any user controls for opening ports. Port forwarding, yes. But port forwarding is not port opening. Also port forwarding is applicable to incoming packets. All but one of the "open" ports in the Obihai FAQ are for outgoing packets.
Meridius:
oh man, I finally got it running. Was router issue. The new firmware update to 5921EX changed how obi200 works with my router (was previously on 5898EX).
since obitalk automatically updates to new firmware when adding devices, I got messed over.
I had to disable SIP ALG and open up ports by port forwarding these (5060, 5061, 6800, 5222, 5223, 10000-11000, 16600-16998, 19305) to the IP addresses of the obi200s. after rebooting, everything works.
during registration of the obi devices with google and anveo, I had to also plug in directly into the ports of the router; these devices with the new firmware don't like to be connected to switches when they work with my router.
was frustrating experience, but I think I blame Netgear for this since I tested these new firmware out on older Netgear router and experienced no problems with registration.
drgeoff:
Quote from: Meridius on June 04, 2019, 06:26:02 pm
oh man, I finally got it running. Was router issue. The new firmware update to 5921EX changed how obi200 works with my router (was previously on 5898EX).
since obitalk automatically updates to new firmware when adding devices, I got messed over.
I had to disable SIP ALG and open up ports by port forwarding these (5060, 5061, 6800, 5222, 5223, 10000-11000, 16600-16998, 19305) to the IP addresses of the obi200s. after rebooting, everything works.
during registration of the obi devices with google and anveo, I had to also plug in directly into the ports of the router; these devices with the new firmware don't like to be connected to switches when they work with my router.
was frustrating experience, but I think I blame Netgear for this since I tested these new firmware out on older Netgear router and experienced no problems with registration.
Most probably SIP ALG was the only showstopper and the firmware version and ports were not contributing to the failures.
Navigation
[0] Message Index
[#] Next page
[*] Previous page