[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:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   12363
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
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-25-2008 08:22 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

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

---------------------------------------------------------------------- 
 jvandal - 04-25-08 08:22  
---------------------------------------------------------------------- 
About corrupted packet, the server will start crash in 1-2 hours after
receive some corrupt packet like :

#
U 192.111.226.42:5060 -> 172.16.186.49:5060
NOTIFY sip:t8885555583 at 172.16.186.49:5060 SIP/2.0.
Via: SIP/2.0/UDP 192.111.226.42:5060;branch=z9hG4bK4c6b082f;rport.
From: "asterisk" <sip:asterisk at 192.111.226.42>;tag=as2a2e0574.
To: <sip:t8885555583 at 172.16.186.49:5060>.
Contact: <sip:asterisk at 192.111.226.42>.
Call-ID: 088aaa476d295a7245440d90181c8942 at 192.111.226.42.
CSeq: 102 NOTIFY.
User-Agent: Asterisk PBX.
Max-Forwards: 70.
Event: message-summary.
Content-Type: application/simple-message-summary.
Content-Length: 96.
.
Messages-Waiting: yes.
Message-Account: sip:asterisk at 192.111.226.42.
Voice-Message: 10/6 (0/0).

#
U 172.16.186.49:5060 -> 192.111.226.42:5060
SI5004P/2.0 200 OK.
Call-ID: 088aaa476d295a7245440d90181c8942 at 192.111.226.42.
CSeq: 102 NOTIFY.
From: "asterisk" <sip:asterisk at 192.111.226.42>;tag=as2a2e0574.
To: <sip:t8885555583 at 172.16.186.49:5060>;tag=ba02a167407dad8.
Via: SIP/2.0/UDP 192.111.226.42:5060;branch=z9hG4bK4c6b082f;rport.
Content-Length: 4.
User-Agent: MxSipApp/5.0.23.141 MxSF/v3.2.2.4.
.


On valgrind output, some line on chan_sip.c refer to MWI, this can also be
related ? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-25-08 08:22  jvandal        Note Added: 0086005                          
======================================================================