Stops Working After 3 Hours

<< < (2/5) > >>

NoelB:
I have not worked out how quote from a previous post yet but I use Keep Alives . They are sip pkts sent to the voip provider which keep your router nat session refreshed . With a setting of 60 secs mine are actually sent every 120 secs for some reason but most nat sessions remain alive for a couple of minutes so 120 secs is fine. Registers actually do the same thing if set at this frequency but some voip providers will not accept register less than 300 secs to limit server activity.If the router nat session closes incoming pkts will be rejected unless you use port forwarding or dmz which are both security hazards.

Veghead:
No luck so far.

I tried enabling X_KeepAliveEnable and set X_KeepAliveExpires to 60. That didn't work, so I tried setting X_KeepAliveExpires to 30. No luck there either.

Same problem as before. Rebooting the Obihai temporarily solves the problem.

I'm using an SMC combo gateway/router/cable modem provided by Comcast. I believe it's the SMC8014. Unfortunately, I'm stuck with that specific router as part of my business class service.

Should I open a support ticket with OBI at this point?

Mango:
Did you get the chance to try the tests I suggested in my previous post?

Also, please confirm that **9 222-222-222 normally works (when the device is not having the problem).

Codesmith:
Various people have stated that there is a 3 hour limit to all google voice calls.  I can't find anything official or authoritative on this however.

But every Google Voice call I've made cuts out at exactly 3 hours.  (I have a female friend that occasionally engages in long talks).

drgeoff:
Quote from: Codesmith on October 26, 2014, 01:32:08 am

Various people have stated that there is a 3 hour limit to all google voice calls.  I can't find anything official or authoritative on this however.

But every Google Voice call I've made cuts out at exactly 3 hours.  (I have a female friend that occasionally engages in long talks).



A 3 hour cut-off on a call in progres is a different  issue and not the same problem as the one being trouble-shooted here.

I agree with the suggestions from the other posters above.

Navigation

[0] Message Index

[#] Next page

[*] Previous page