[asterisk-bugs] [Asterisk 0012363]: Asterisk crash and receive lot of 'Bad request protocol' error

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12363 
====================================================================== 
Reported By:                jvandal
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12363
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.19 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-03-2008 11:55 CDT
Last Modified:              04-03-2008 13:21 CDT
====================================================================== 
Summary:                    Asterisk crash and receive lot of 'Bad request
protocol' error
Description: 
Hi,

I have a server that have been updated to Asterisk 1.4.19 and since
yesterday, it crashed about each hour.

Not sure if this can be related, but I see this warning on CLI, not sure
if this can be related, but 1st time I see this, using a Mediatrix 2102
ATA.
 
[Apr  3 12:55:03] WARNING[7832]: chan_sip.c:6772
determine_firstline_parts: Bad request protocol Method Not Allowed
[Apr  3 12:56:35] WARNING[7832]: chan_sip.c:6772
determine_firstline_parts: Bad request protocol OK
[Apr  3 12:56:35] WARNING[7832]: chan_sip.c:6772
determine_firstline_parts: Bad request protocol OK

====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 04-03-08 13:21  
---------------------------------------------------------------------- 
Regarding the "Bad request protocol" messages, what this means is that
chan_sip thinks that the first line of the SIP request sent does not
contain the string "SIP/2.0" after the request type.

What seems odd from the output you have given is that it appears that
chan_sip thinks that it has received a request when it has actually
received a response. Those "OK's" are most likely part of a "200 OK"
response. A SIP debug of the packets that cause the problem would be
helpful in determining why this is happening.

As for the crash, I would suggest that p->callid is NULL, but this is
unlikely since stringfield parameters should never be NULL. Instead, I
would bet that this is an issue of memory corruption. The best way to fix
such issues is to run Asterisk under valgrind as described in
doc/valgrind.txt 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-03-08 13:21  putnopvut      Note Added: 0085008                          
======================================================================