[Home]

Summary:ASTERISK-29069: chan_sip: FRACK on incoming handling of REGISTER
Reporter:Don Hunter (vmPhone)Labels:
Date Opened:2020-09-04 10:24:51Date Closed:
Priority:MajorRegression?
Status:Open/NewComponents:Channels/chan_sip/Registration
Versions:13.34.0 16.15.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) backtrace.5SEP2020.txt
( 1) backtrace.txt
Description:For some time now, every day or two, Asterisk gets the following... then crashes (restarts).

astobj2.c: FRACK!, Failed assertion bad magic number 0x0 for object 0x17eeac88 (0)

Comments:By: Asterisk Team (asteriskteam) 2020-09-04 10:24:52.799-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.

By: Don Hunter (vmPhone) 2020-09-04 10:25:58.119-0500

Backtrace attached

By: Sean Bright (seanbright) 2020-09-05 07:45:25.172-0500

Do you know in which version of Asterisk this problem began occurring?

By: Don Hunter (vmPhone) 2020-09-05 10:50:30.904-0500

Sorry, no... but it has been the last several.
I can say the issue has been ongoing for the past year,but getting much more frequent.

We started using TLS about a year ago, and if I was to point a finger, I would say that is when the issue started.

By: Benjamin Keith Ford (bford) 2020-09-08 09:52:57.116-0500

Hey [~vmPhone], can you provide any additional information on how Asterisk is being used? Some logs[1] would also be good to have, just so we can see if there's anything obvious that stands out. The logs need to be from a session leading up to the FRACK.

[1]" https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

By: Don Hunter (vmPhone) 2020-09-08 10:25:45.876-0500

Attached find a new backtrace from Saturday's crash.

By: Don Hunter (vmPhone) 2020-09-08 10:27:36.337-0500

Benjamin,

I have a full log (vvv) available for the Sept 5 crash just posted.  
Due to the confidential nature of the details in the log, I do not want to make public.

Where can I provide you details to obtain the file, so it remains secure (confidential)?

By: Benjamin Keith Ford (bford) 2020-09-08 10:40:40.803-0500

The chan_sip channel driver is in 'extended' support status and is supported only by community members.  Your issue is in the queue. Your patience is appreciated as a community developer may work the issue when time and resources become available.

Asterisk is an open source project and community members work the issues on a voluntary basis. You are welcome to develop your own patches and submit them to the project.[1]

If you are not a programmer and you are in a hurry to see a patch provided then you might try rallying support on the Asterisk users mailing list or forums.[2] Another alternative is offering a bug bounty on the asterisk-dev mailing list.[3] Often a little incentive can go a long way.

[1]: https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process
[2]: http://www.asterisk.org/community/discuss
[3]: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Bug+Bounties

If a community member does work this issue, you may have to send the info to them to make progress. Just a word of caution since this is outside of Sangoma.

By: Don Hunter (vmPhone) 2020-09-08 10:42:06.245-0500

We have a very busy system... full file on verbose 3 is up to a gig daily.
Unfortunately, the crashes are unpredictable, occurring every 1 to 3 days apart.
Verbose 5 would produce an unmanageable log file.

If you need a verbose 3 log, from the last crash on Sep 5, we have one.
If you need a verbose 5, I will have to enable and wait for the next crash.

By: Don Hunter (vmPhone) 2020-09-08 11:44:54.483-0500

With crashes every day or two... we really need to get this fixed.
We will offer a bounty, in hopes for a quick resolve.

By: Sean Bright (seanbright) 2020-09-08 12:18:04.427-0500

Can you send unredacted backtraces to asteriskteam@digium.com with ASTERISK-29069 in the subject?

By: Don Hunter (vmPhone) 2020-09-15 11:10:56.916-0500

From what I have researched, this is a known (and very old) issue with Asterisk and Chan_SIP.
If we move from Chan_SIP to PJSIP, will this issue go away?

By: Joshua C. Colp (jcolp) 2020-09-15 11:14:20.025-0500

The code is completely different, and there have been no reports of this in PJSIP.