[Home]

Summary:ASTERISK-15686: Asterisk Crashes after it thinks it gets corrupt SIP message
Reporter:dotnet (dotnet)Labels:
Date Opened:2010-02-24 09:12:12.000-0600Date Closed:2011-06-07 14:01:05
Priority:CriticalRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) trace1.rtfd.zip
Description:I had call from Customer - There phone resgistrations had failed..

I checked the CLI and as soon as I typed SIP SHOW [TAB] the CLI hungup

I restarted asterisk /etc/init.d/asterisk restart and it came back fine.

I checked the asterisk logs and the last entry was

[Feb 24 13:58:22] WARNING[20879] chan_sip.c: Bad request protocol H^? x?? 10044@x.x.x.x:5060 SIP/2.0 (ip x'd)

I have been running 1.4.21 since last September with NEVER a crash. I upgraded (sic) to Asterisk 1.4.29.1 built by root @ carl on a i686 last night because I had a requirement to get dahdi installed on the system.

The call that crashed * went through our SIP proxy (Kamailio) - the SIP messages look fine..

What more information should I give you?  Should I regress to 1.4.21 to provide a stable platform for my customers.

Regards.
Stephen


****** ADDITIONAL INFORMATION ******

Debian 5.01 2.6.26-2-686-bigmem

Asterisk 1.4.29.1

Dahdi_linux 2.2.1

Asterisk Addons 1.4.9

Comments:By: dotnet (dotnet) 2010-02-24 12:02:52.000-0600

Apologies, the category is incorrect, should be chan_sip
By: Clod Patry (junky) 2010-02-24 16:16:17.000-0600

Could you reproduce this easily?

You should include the SIP debug.
When you say "the SIP messages look fine.." do you have it?

Many simultaneous calls?
By: dotnet (dotnet) 2010-02-24 16:43:47.000-0600

I can't see how I could reproduce.

There was only 1 call at this time with 34 endpoints on the server and 1 trunk registration.

I have the SIP trace from the proxy that asterisk sent the call to.

I can upload that if it's any good to you.. Is it possible to upload it as non public?

Thanks
Stephen
By: Clod Patry (junky) 2010-02-24 17:30:39.000-0600

I changed the status to private, so you can upload your sip trace here.
Only developpers and managers will have access to this bug.
By: dotnet (dotnet) 2010-02-24 17:39:44.000-0600

Hi,

The attached from our kamailio proxy..

Regards,
Stephen.
By: Leif Madsen (lmadsen) 2010-02-25 13:25:06.000-0600

Any chance you can attach any traces or information as a text file attachment (not compressed?) A compressed file makes it more difficult for those who want to inspect the information.

For crash issues, please attach a backtrace per the doc/backtrace.txt file in your Asterisk source.
By: Paul Belanger (pabelanger) 2010-04-28 15:33:41

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.

Further information can be found at http://www.asterisk.org/developers/bug-guidelines