[asterisk-bugs] [Asterisk 0013255]: bad contact port keeps carriers from taking calls

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13255 
====================================================================== 
Reported By:                falves11
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13255
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 135851 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-08-07 13:50 CDT
Last Modified:              2008-08-12 18:46 CDT
====================================================================== 
Summary:                    bad contact port keeps carriers from taking calls
Description: 
Attached is a packet capture of a test call. Please take not that the port
in both the From and the Contact headers is 0, which is why the calls are
being rejected.


======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0011843 Moved Temporarily Contact Transport inf...
====================================================================== 

---------------------------------------------------------------------- 
 (0091355) qwell (administrator) - 2008-08-12 18:46
 http://bugs.digium.com/view.php?id=13255#c91355 
---------------------------------------------------------------------- 
I have some thoughts on this - I'll look into it tomorrow.

I think it may be an integer overflow in create_addr (and various other
places) relating to int being signed.  The sscanf that was added there may
have triggered an existing bug. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-08-12 18:46 qwell          Note Added: 0091355                          
======================================================================