The number you dialed, has not received a response from the service provider?
A_Friend:
Quote from: B0b. on August 20, 2018, 04:41:53 am
I am not asking if the hotspot is causing the calls to not go through. I am asking why the hotspot is causing the calls to not go through with the OBi.
I posted the question here to try different settings to try to get the OBi to work with the hotspot, not hear "tough luck".
Forgive me if I continue with my speculations...
There's another thread, where the poster is experiencing a related problem. His cable-connected Obi phone is dropping its GV connection, but not its other SIP carriers' connections. The GV connection absolutely will not reconnect until he reboots the Obi, and then it's fine. My speculation there is two-fold. One, his cable company has been doing work on the system this last week during off-hours (like mid-day), which causes a brief interruption of service. This results in GV losing registration, but his other SIP connections either survive that, or reconnect automatically as soon as internet is available again. And... Two, it's the Obi Firmware -- it's not handling a reconnect/re-registration for GV because the engineers never planned on it having to, and the business with the Auth token is very different (and a bit complicated) from how other SIP registrations are done.
SteveInWA might be right, that there's nothing you can change that will delay the de-registration or keep the connection alive. Or maybe not. Who knows until you kibbitz around a bit and see? And you're right that it's clearly something to do with the Obi.
My theory is that the firmware needs an update so it can handle re-registering dropped GV connections without needing a reboot.
B0b.:
Quote from: A_Friend on August 20, 2018, 06:10:47 am
Quote from: B0b. on August 20, 2018, 04:41:53 am
I am not asking if the hotspot is causing the calls to not go through. I am asking why the hotspot is causing the calls to not go through with the OBi.
I posted the question here to try different settings to try to get the OBi to work with the hotspot, not hear "tough luck".
Forgive me if I continue with my speculations...
There's another thread, where the poster is experiencing a related problem. His cable-connected Obi phone is dropping its GV connection, but not its other SIP carriers' connections. The GV connection absolutely will not reconnect until he reboots the Obi, and then it's fine. My speculation there is two-fold. One, his cable company has been doing work on the system this last week during off-hours (like mid-day), which causes a brief interruption of service. This results in GV losing registration, but his other SIP connections either survive that, or reconnect automatically as soon as internet is available again. And... Two, it's the Obi Firmware -- it's not handling a reconnect/re-registration for GV because the engineers never planned on it having to, and the business with the Auth token is very different (and a bit complicated) from how other SIP registrations are done.
SteveInWA might be right, that there's nothing you can change that will delay the de-registration or keep the connection alive. Or maybe not. Who knows until you kibbitz around a bit and see? And you're right that it's clearly something to do with the Obi.
My theory is that the firmware needs an update so it can handle re-registering dropped GV connections without needing a reboot.
I think you are right. Thank you for your help and reply.
SteveInWA:
No, the firmware does not need an update. OBiTALK devices will automatically re-establish both their connection to the network, and to any service provider that can handle the re-connections, including Google Voice.
However, if the device goes offline over and over again in a short period of time, the service provider may temporarily block/ban the connection attempts.
This is not speculation, as your "friendly" speculator keeps speculating. This is a proven fact, based on my hundreds of hours spent beta testing Google Voice on OBiTALK devices, and helping thousands of users with the service.
As I believe I mentioned earlier, Google Voice has specific, non-default keep-alive settings, as long as you use the OBiTALK portal to create the SP configuration:
Via OBiTALK Expert mode: Voice Services-->SPx-->X_CustomKeepAliveMsg = %0d%0a%0d%0a
SteveInWA:
Ok, since I am such a swell guy, and you have been given so much BS advice about your issue, I discussed this with a friend who is using an LTE modem with Google Voice on his OBi. As I pointed out earlier, your hotspot is periodically dropping the connections. Why? Because it's designed to save power, and to save LTE bandwidth.
By contrast, if you switch to a fixed-location, AC-powered, always-on LTE modem, your connection won't drop, as proven by my friend's testing.
This is what he's using: https://www.netgear.com/home/products/mobile-broadband/lte-modems/LB1120.aspx
LTN1:
Quote from: SteveInWA on August 21, 2018, 08:27:23 am
Ok, since I am such a swell guy, and you have been given so much BS advice about your issue, I discussed this with a friend who is using an LTE modem with Google Voice on his OBi. As I pointed out earlier, your hotspot is periodically dropping the connections. Why? Because it's designed to save power, and to save LTE bandwidth.
By contrast, if you switch to a fixed-location, AC-powered, always-on LTE modem, your connection won't drop, as proven by my friend's testing.
This is what he's using: https://www.netgear.com/home/products/mobile-broadband/lte-modems/LB1120.aspx
Very kind of you, Steve, to contribute to an OP who seemingly would rather have people pull answers out of their asses that lead nowhere. While he may not care for more accurate answers, I do have a follow up question on these types of LTE modems. Isn't there likely a configuration in each modem where you can bypass the power saving mode and keep it awake all the time? Of course, none of this has to do with the OBi but it would be interesting to know. For example, on my cable modem (SBG6580), I used to have wireless internet dropping all the time until I went to the WMM QoS parameters and turned off WMM Support, No-Acknowledgement and Power Save Support.
Navigation
[0] Message Index
[#] Next page
[*] Previous page