[Freeswitch-users] Longtime working user's phone now disconnecting
sdevoy at bizfocused.com
Thu Jan 14 19:00:19 MSK 2016
Thank you Larry and Daniel.
I really appreciate the explanation of the underlying problem and the fix for it.
From: freeswitch-users-bounces at lists.freeswitch.org [mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of Larry Morley
Sent: Tuesday, January 12, 2016 2:13 PM
To: FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org>
Subject: Re: [Freeswitch-users] Longtime working user's phone now disconnecting
As previously noted, this is slightly off topic. That said, I felt I'd be remiss if I didn't add a note to this thread.
We had customers experience the same problem - and others apparently stemming from the same root cause - particularly with this ISP. And, it turned out they had experienced the same problems with their phone service when they were receiving it from the company before us.
The cause of that problem, along with others such as users receiving calls from their own extensions several times an hour, 24x7, were ultimately determined to be the result of Comcast having an incompatible SIP ALG enabled on the CPE: a SIP ALG that's properly implemented and properly working shouldn't cause any issues. Also, the users that experienced the worst variants of these problems had a SIP ALG, and apparently other ALGs for other protocols, enabled on their own routers.
Calling Comcast technical support and requesting that they change the "cable router" settings, then power cycling the CPE and the local routers as necessary, invariably solved the problem(s) we'd been experiencing.
Note that in the course of fixing these issues, we discovered that, according to the current DOCSIS specifications, by design, end users aren't supposed to be able to modify much with respect to DOCSIS "cable modem" settings. That's why we decided to go the ISP tech support route first.
We haven't seen a recurrence of any of the problems noted initially since we made the changes noted, well over six months ago.
Hopefully this is of use to someone.
On Jan 10, 2016 3:49 AM, "Daniel Corbe" <dcorbe at hammerfiber.com<mailto:dcorbe at hammerfiber.com>> wrote:
> On Jan 9, 2016, at 11:24 PM, Sean Devoy <sdevoy at bizfocused.com<mailto:sdevoy at bizfocused.com>> wrote:
> I don’t know what else happens when that is set, but I know it makes my extension re-register every 30 seconds (which seems excessive to me). I think that is probably just masking the underlying problem where the Comcast router is dropping the NAT connection after some time period. I am thrilled to have it working, but there must be a cleaner fix. Is there at least a way to extend that 30 second time to 60, 90, 120?
This is slightly off-topic; however, it really is your Comcast-supplied CPE causing this particular issue. You’re better off buying an inexpensive cable modem that only runs in bridge mode and using a router that you have more direct configuration control over. The person that maintained this before you obviously took note of how stupidly aggressive the default timers are on their CPE.
Professional FreeSWITCH Consulting Services:
consulting at freeswitch.org<mailto:consulting at freeswitch.org>
Official FreeSWITCH Sites
FreeSWITCH-users mailing list
FreeSWITCH-users at lists.freeswitch.org<mailto:FreeSWITCH-users at lists.freeswitch.org>
-------------- next part --------------
An HTML attachment was scrubbed...
Join us at ClueCon 2016 Aug 8-12, 2016
More information about the FreeSWITCH-users