Longtime working user's phone now disconnecting
Hi, I have an emotional user who now claims her phone fails at least once a week and everyone else's must be, but no one has ever reported it! My very favorite kind of complaint - entirely founded in emotion, myth and misunderstanding. In any case, I called her. I spent 4:11 listening to her complain, but not be able to sight a single instance I could research. Then <CLICK> the connection was lost. She claims she did not hang up, the line went dead. Perhaps there is an actual problem after all. I will add at least one of the errors she reported would lead me to believe there is a hardware (or power) issue on her desk phone (Cisco SPA540). I did look on the phone after the dropped call and the phone did NOT reboot and said it was still registered from 45 minutes earlier. Just FYI: The problems are reported to have started when COMCAST replaced their DSL and they got new external IP addresses. The phones are NATed. Can someone tell me what [BREAK], [NORMAL CLEARING], then "port ending bridge by request from write function" means? Just for background, this was an internal ext to ext dial in separate "domains" on my FS server. NO IVR involved. Here is a log excerpt: 12:32:12.178673 [DEBUG] sofia_glue.c:3429 sofia/external/220@redacted.com Setting audio receive payload in Re-INVITE to 0 12:36:23.318530 [DEBUG] switch_core_session.c:1016 Send signal sofia/external/sip:10@redacted_too:port [BREAK] 12:36:23.338532 [NOTICE] sofia.c:737 Hangup sofia/external/sip:10@redacted_too:port [CS_EXCHANGE_MEDIA] [NORMAL_CLEARING] 12:36:23.338532 [DEBUG] switch_ivr_bridge.c:569 sofia/external/sip:10@redacted_too:port ending bridge by request from write function 12:36:23.338532 [DEBUG] switch_channel.c:3187 Send signal sofia/external/sip:10@redacted_too:port [KILL] 12:36:23.338532 [DEBUG] switch_core_session.c:1351 Send signal sofia/external/sip:10@redacted_too:port [BREAK] 12:36:23.338532 [DEBUG] switch_ivr_bridge.c:645 BRIDGE THREAD DONE [sofia/external/220@redacted.com] 12:36:23.338532 [DEBUG] switch_ivr_bridge.c:675 Send signal sofia/external/sip:10@redacted_too:port [BREAK] 12:36:23.338532 [DEBUG] switch_ivr_bridge.c:645 BRIDGE THREAD DONE [sofia/external/sip:10@redacted_too:port] 12:36:23.338532 [DEBUG] switch_ivr_bridge.c:675 Send signal sofia/external/220@redacted.com [BREAK] Any ideas where I should look next or even what the problem is? NOTHING has changed on the server for months and months. The FS version is rather out of date, but has been stable for a long time. Thanks in advance. Sean
You probably want to go a little higher up in the excerpt and even better if the sip trace was enabled as well. ending bridge by request from write function just means one of the legs is hungup and is no longer accepting writes so the bridge ends. You are missing the place where the leg hangs up, most likely from some sip transaction. Look for lines with "Hangup" in them. On Tue, Jan 5, 2016 at 12:16 PM, Sean Devoy <sdevoy@bizfocused.com> wrote:
Hi,
I have an emotional user who now claims her phone fails at least once a week and everyone else’s must be, but no one has ever reported it! My very favorite kind of complaint – entirely founded in emotion, myth and misunderstanding.
In any case, I called her. I spent 4:11 listening to her complain, but not be able to sight a single instance I could research. Then <CLICK> the connection was lost. She claims she did not hang up, the line went dead. Perhaps there is an actual problem after all.
I will add at least one of the errors she reported would lead me to believe there is a hardware (or power) issue on her desk phone (Cisco SPA540). I did look on the phone after the dropped call and the phone did NOT reboot and said it was still registered from 45 minutes earlier.
Just FYI: The problems are reported to have started when COMCAST replaced their DSL and they got new external IP addresses. The phones are NATed.
Can someone tell me what [BREAK], [NORMAL CLEARING], then “port ending bridge by request from write function” means?
Just for background, this was an internal ext to ext dial in separate “domains” on my FS server. NO IVR involved.
Here is a log excerpt:
12:32:12.178673 [DEBUG] sofia_glue.c:3429 sofia/external/220@redacted.com Setting audio receive payload in Re-INVITE to 0
12:36:23.318530 [DEBUG] switch_core_session.c:1016 Send signal sofia/external/sip:10@redacted_too:port [BREAK]
12:36:23.338532 [NOTICE] sofia.c:737 Hangup sofia/external/sip:10@redacted_too:port [CS_EXCHANGE_MEDIA] [NORMAL_CLEARING]
12:36:23.338532 [DEBUG] switch_ivr_bridge.c:569 sofia/external/sip:10@redacted_too:port ending bridge by request from write function
12:36:23.338532 [DEBUG] switch_channel.c:3187 Send signal sofia/external/sip:10@redacted_too:port [KILL]
12:36:23.338532 [DEBUG] switch_core_session.c:1351 Send signal sofia/external/sip:10@redacted_too:port [BREAK]
12:36:23.338532 [DEBUG] switch_ivr_bridge.c:645 BRIDGE THREAD DONE [sofia/external/220@redacted.com]
12:36:23.338532 [DEBUG] switch_ivr_bridge.c:675 Send signal sofia/external/sip:10@redacted_too:port [BREAK]
12:36:23.338532 [DEBUG] switch_ivr_bridge.c:645 BRIDGE THREAD DONE [sofia/external/sip:10@redacted_too:port]
12:36:23.338532 [DEBUG] switch_ivr_bridge.c:675 Send signal sofia/external/ 220@redacted.com [BREAK]
Any ideas where I should look next or even what the problem is?
NOTHING has changed on the server for months and months. The FS version is rather out of date, but has been stable for a long time.
Thanks in advance.
Sean
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Anthony Minessale II ♬ @anthmfs ♬ @FreeSWITCH ♬ ☞ http://freeswitch.org/ ☞ http://cluecon.com/ ☞ http://twitter.com/FreeSWITCH ☞ irc.freenode.net #freeswitch ☞ *http://freeswitch.org/g+ <http://freeswitch.org/g+>* ClueCon Weekly Development Call ☎ sip:888@conference.freeswitch.org ☎ +19193869900 https://www.youtube.com/watch?v=9XXgW34t40s https://www.youtube.com/watch?v=NLaDpGQuZDA
Thank you for the reply Anthony. It appears you are correct OF COURSE! I dug in deeper to the setup (and dialplan, etc) for that user’s extension. I found a difference from the working models that I should have seen before even posting, sorry. The extension did not have <variable name="sip-force-contact" value="NDLB-connectile-dysfunction"/> And all the working extensions do have it. I added it. 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? Can you direct me to a good resource to help me understand this parameter better? Thank you again, Sean From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Anthony Minessale Sent: Thursday, January 07, 2016 12:40 PM To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> Subject: Re: [Freeswitch-users] Longtime working user's phone now disconnecting You probably want to go a little higher up in the excerpt and even better if the sip trace was enabled as well. ending bridge by request from write function just means one of the legs is hungup and is no longer accepting writes so the bridge ends. You are missing the place where the leg hangs up, most likely from some sip transaction. Look for lines with "Hangup" in them. On Tue, Jan 5, 2016 at 12:16 PM, Sean Devoy <sdevoy@bizfocused.com<mailto:sdevoy@bizfocused.com>> wrote: Hi, I have an emotional user who now claims her phone fails at least once a week and everyone else’s must be, but no one has ever reported it! My very favorite kind of complaint – entirely founded in emotion, myth and misunderstanding. In any case, I called her. I spent 4:11 listening to her complain, but not be able to sight a single instance I could research. Then <CLICK> the connection was lost. She claims she did not hang up, the line went dead. Perhaps there is an actual problem after all. I will add at least one of the errors she reported would lead me to believe there is a hardware (or power) issue on her desk phone (Cisco SPA540). I did look on the phone after the dropped call and the phone did NOT reboot and said it was still registered from 45 minutes earlier. Just FYI: The problems are reported to have started when COMCAST replaced their DSL and they got new external IP addresses. The phones are NATed. Can someone tell me what [BREAK], [NORMAL CLEARING], then “port ending bridge by request from write function” means? Just for background, this was an internal ext to ext dial in separate “domains” on my FS server. NO IVR involved. Here is a log excerpt: 12:32:12.178673 [DEBUG] sofia_glue.c:3429 sofia/external/220@redacted.com<mailto:220@redacted.com> Setting audio receive payload in Re-INVITE to 0 12:36:23.318530 [DEBUG] switch_core_session.c:1016 Send signal sofia/external/sip:10@redacted_too:port [BREAK] 12:36:23.338532 [NOTICE] sofia.c:737 Hangup sofia/external/sip:10@redacted_too:port [CS_EXCHANGE_MEDIA] [NORMAL_CLEARING] 12:36:23.338532 [DEBUG] switch_ivr_bridge.c:569 sofia/external/sip:10@redacted_too:port ending bridge by request from write function 12:36:23.338532 [DEBUG] switch_channel.c:3187 Send signal sofia/external/sip:10@redacted_too:port [KILL] 12:36:23.338532 [DEBUG] switch_core_session.c:1351 Send signal sofia/external/sip:10@redacted_too:port [BREAK] 12:36:23.338532 [DEBUG] switch_ivr_bridge.c:645 BRIDGE THREAD DONE [sofia/external/220@redacted.com<mailto:220@redacted.com>] 12:36:23.338532 [DEBUG] switch_ivr_bridge.c:675 Send signal sofia/external/sip:10@redacted_too:port [BREAK] 12:36:23.338532 [DEBUG] switch_ivr_bridge.c:645 BRIDGE THREAD DONE [sofia/external/sip:10@redacted_too:port] 12:36:23.338532 [DEBUG] switch_ivr_bridge.c:675 Send signal sofia/external/220@redacted.com<mailto:220@redacted.com> [BREAK] Any ideas where I should look next or even what the problem is? NOTHING has changed on the server for months and months. The FS version is rather out of date, but has been stable for a long time. Thanks in advance. Sean _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org<mailto:FreeSWITCH-users@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org -- Anthony Minessale II ♬ @anthmfs ♬ @FreeSWITCH ♬ ☞ http://freeswitch.org/ ☞ http://cluecon.com/ ☞ http://twitter.com/FreeSWITCH ☞ irc.freenode.net<http://irc.freenode.net> #freeswitch ☞ http://freeswitch.org/g+ ClueCon Weekly Development Call ☎ sip:888@conference.freeswitch.org<mailto:sip%3A888@conference.freeswitch.org> ☎ +19193869900 https://www.youtube.com/watch?v=9XXgW34t40s https://www.youtube.com/watch?v=NLaDpGQuZDA
On Jan 9, 2016, at 11:24 PM, Sean Devoy <sdevoy@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.
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. Sincerely, Larry Morley On Jan 10, 2016 3:49 AM, "Daniel Corbe" <dcorbe@hammerfiber.com> wrote:
On Jan 9, 2016, at 11:24 PM, Sean Devoy <sdevoy@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@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Thank you Larry and Daniel. I really appreciate the explanation of the underlying problem and the fix for it. Sean From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Larry Morley Sent: Tuesday, January 12, 2016 2:13 PM To: FreeSWITCH Users Help <freeswitch-users@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. Sincerely, Larry Morley On Jan 10, 2016 3:49 AM, "Daniel Corbe" <dcorbe@hammerfiber.com<mailto:dcorbe@hammerfiber.com>> wrote:
On Jan 9, 2016, at 11:24 PM, Sean Devoy <sdevoy@bizfocused.com<mailto:sdevoy@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@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org<mailto:FreeSWITCH-users@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (4)
-
Anthony Minessale
-
Daniel Corbe
-
Larry Morley
-
Sean Devoy