Summary:	ASTERISK-30079: Randomly extension gets unregistered
Reporter:	Ahmad Hassan (ahassan)	Labels:
Date Opened:	2022-05-24 04:08:51	Date Closed:	2022-05-24 04:08:53
Priority:	Critical	Regression?
Status:	Closed/Complete	Components:	Core/Configuration
Versions:	13.24.0	Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	my asterisk 13.24 is on public IP , some remote clients complain that randomly their extension get unregistered , i have open the Full log and find something like following patteren . can anyone please help on this how to trace the actual reason of this issue. 36424556:[May 23 11:18:15] NOTICE[84831] chan_sip.c: Peer '1001' is now Reachable. (47ms / 2000ms) 36432145:[May 23 11:21:35] NOTICE[84831] chan_sip.c: Peer '1060' is now UNREACHABLE!  Last qualify: 45 36432461:[May 23 11:21:39] NOTICE[84831] chan_sip.c: Peer '1001' is now UNREACHABLE!  Last qualify: 48 36435123:[May 23 11:22:11] NOTICE[84831] chan_sip.c: Peer '1070' is now UNREACHABLE!  Last qualify: 44 36438397:[May 23 11:23:28] VERBOSE[84831] chan_sip.c: Registered SIP '1001' at 208.180.137.9:29307 36438501:[May 23 11:23:28] NOTICE[84831] chan_sip.c: Peer '1001' is now Reachable. (255ms / 2000ms) 36439725:[May 23 11:23:32] VERBOSE[84831] chan_sip.c: Registered SIP '1060' at 208.180.137.9:5060 36439774:[May 23 11:23:33] NOTICE[84831] chan_sip.c: Peer '1060' is now Reachable. (91ms / 2000ms) 36474708:[May 23 11:32:14] VERBOSE[84831] chan_sip.c: Registered SIP '1070' at 208.180.137.9:23756 36474709:[May 23 11:32:14] NOTICE[84831] chan_sip.c: Peer '1070' is now Reachable. (45ms / 2000ms) 36492149:[May 23 11:37:12] NOTICE[84831] chan_sip.c: Peer '1070' is now UNREACHABLE!  Last qualify: 44 36501151:[May 23 11:42:02] VERBOSE[84831] chan_sip.c: Registered SIP '1070' at 208.180.137.9:23756 36501152:[May 23 11:42:02] NOTICE[84831] chan_sip.c: Peer '1070' is now Reachable. (42ms / 2000ms) 36513963:[May 23 11:47:16] NOTICE[84831] chan_sip.c: Peer '1070' is now UNREACHABLE!  Last qualify: 45 36541292:[May 23 11:52:04] VERBOSE[84831] chan_sip.c: Registered SIP '1070' at 208.180.137.9:23756 36541307:[May 23 11:52:04] NOTICE[84831] chan_sip.c: Peer '1070' is now Reachable. (43ms / 2000ms) 36571220:[May 23 12:02:18] NOTICE[84831] chan_sip.c: Peer '1070' is now UNREACHABLE!  Last qualify: 46 36575904:[May 23 12:04:23] VERBOSE[84831] chan_sip.c: Registered SIP '1070' at 208.180.137.9:23756 36575905:[May 23 12:04:23] NOTICE[84831] chan_sip.c: Peer '1070' is now Reachable. (44ms / 2000ms) 36580175:[May 23 12:06:28] NOTICE[84831] chan_sip.c: Peer '1060' is now UNREACHABLE!  Last qualify: 44 36581772:[May 23 12:06:42] NOTICE[84831] chan_sip.c: Peer '1001' is now UNREACHABLE!  Last qualify: 57 36582665:[May 23 12:07:17] NOTICE[84831] chan_sip.c: Peer '1070' is now UNREACHABLE!  Last qualify: 45 36592162:[May 23 12:08:20] VERBOSE[84831] chan_sip.c: Registered SIP '1060' at 208.180.137.9:5060 36592231:[May 23 12:08:20] NOTICE[84831] chan_sip.c: Peer '1060' is now Reachable. (43ms / 2000ms) 36593532:[May 23 12:08:32] VERBOSE[84831] chan_sip.c: Registered SIP '1001' at 208.180.137.9:29307 36593533:[May 23 12:08:32] NOTICE[84831] chan_sip.c: Peer '1001' is now Reachable. (45ms / 2000ms) 36596194:[May 23 12:09:30] VERBOSE[84831] chan_sip.c: Registered SIP '1070' at 208.180.137.9:23756 36596195:[May 23 12:09:30] NOTICE[84831] chan_sip.c: Peer '1070' is now Reachable. (43ms / 2000ms) 36602252:[May 23 12:11:44] NOTICE[84831] chan_sip.c: Peer '1060' is now UNREACHABLE!  Last qualify: 49 36603947:[May 23 12:12:24] NOTICE[84831] chan_sip.c: Peer '1070' is now UNREACHABLE!  Last qualify: 191
Comments:	By: Asterisk Team (asteriskteam) 2022-05-24 04:08:53.248-0500 Per the Asterisk versions page [1], the maintenance (bug fix) support for the Asterisk branch you are using has ended. For continued maintenance support please move to a supported branch of Asterisk. After testing with a supported branch, if you find this problem has not been resolved, please open a new issue against the latest version of that Asterisk branch. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions By: Asterisk Team (asteriskteam) 2022-05-24 04:08:54.367-0500 We appreciate the difficulties you are facing, however information request type issues would be better served in a different forum. The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors. If this issue is actually a bug please use the Bug issue type instead. Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines By: Asterisk Team (asteriskteam) 2022-05-24 04:08:54.675-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].