[asterisk-bugs] [Asterisk 0013257]: crash if hangup during sip_read

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13257 
====================================================================== 
Reported By:                travishein
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   13257
Category:                   Channels/chan_sip/General
Reproducibility:            unable to reproduce
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.20 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-08-07 21:26 CDT
Last Modified:              2008-08-20 10:15 CDT
====================================================================== 
Summary:                    crash if hangup during sip_read
Description: 
This one might be similar to http://bugs.digium.com/view.php?id=13256, although
this time it appears to crash
from within the sip_read. It is almost as if the application that was
invoked from the realtime_exec entered a state of waiting for an input from
the user, but the user hung up during this waiting period, so when the
system starts looking for the response after the wait period, in this case
the channel had closed,

At least that's my view from the outside impression, the last line printed
to teh console was:

WARNING[6784]: rtp.c:1140 ast_rtp_read: RTP Read error: Socket operation
on non-socket.  Hanging up.

currently on 1.4.20rc2
====================================================================== 

---------------------------------------------------------------------- 
 (0091582) putnopvut (administrator) - 2008-08-20 10:15
 http://bugs.digium.com/view.php?id=13257#c91582 
---------------------------------------------------------------------- 
Actually I was mistaken about the socket(2) lack of error handling. It
appears that if the recvfrom(2) was called on a file descriptor which was
not a socket, it either means a memory corruption of the rtp structure or
that the kernel is not handling file descriptors properly.

I'll still add the error-handling to sip_read, and I believe I'll close
this bug after the fact, too. If this occurs again, it would be helpful to
run Asterisk under valgrind to see if there is some corruption of the rtp
structure. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-08-20 10:15 putnopvut      Note Added: 0091582                          
======================================================================