[asterisk-bugs] [Asterisk 0016543]: sin_family not set to AF_INET when running trunk on Solaris nevada

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16543 
====================================================================== 
Reported By:                crjw
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16543
Category:                   Core/RTP
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Target Version:             1.4.30
Asterisk Version:           SVN 
JIRA:                       SWP-628 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 237213M 
Request Review:              
====================================================================== 
Date Submitted:             2010-01-05 00:19 CST
Last Modified:              2010-01-08 11:44 CST
====================================================================== 
Summary:                    sin_family not set to AF_INET when running trunk on
Solaris nevada
Description: 
Dialing from any phone fails because sin_family is set to 0 instead of 2
for the RTP traffic.
Asterisk logs the following error:
"res_rtp_asterisk.c:437 ast_rtp_new: Oh dear... we couldn't allocate a
port for RTP instance '827de88'"

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

---------------------------------------------------------------------- 
 (0116314) crjw (reporter) - 2010-01-08 11:44
 https://issues.asterisk.org/view.php?id=16543#c116314 
---------------------------------------------------------------------- 
"Target Version" field for this bug was updated to 1.4.30 by lmadsen
today.
I find this odd since the problem was reported against the trunk.

I never experienced the problem in 1.4 or 1.6 versions.
I believe that the problem was introduced into the trunk on April 2/2009
along with the new RTP engine code. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-08 11:44 crjw           Note Added: 0116314                          
======================================================================