[asterisk-bugs] [Asterisk 0015849]: Recent change to peer_iphash_cb breaks peer matching

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15849 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   15849
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            have not tried
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-09-08 04:05 CDT
Last Modified:              2009-09-08 09:56 CDT
====================================================================== 
Summary:                    Recent change to peer_iphash_cb breaks peer matching
Description: 
A change has been made to the chan_sip.c function peer_iphash_cb to remove
hashing on the port number. It is not clear why this change was made but it
may be indirectly related to a tcp/tls matching issue. However the change
breaks udp peer matching. 


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

---------------------------------------------------------------------- 
 (0110312) dvossel (administrator) - 2009-09-08 09:56
 https://issues.asterisk.org/view.php?id=15849#c110312 
---------------------------------------------------------------------- 
"...Depending whether insecure=port is configured this will either lead to
calls from trunk2 and trunk3 failing to match at all or ..."

With 'insecure=port' disabled, no change in behavior should be present. 
Can you please verify this?  With what settings are calls from trunk2 and
trunk3 failing to match at all? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-08 09:56 dvossel        Note Added: 0110312                          
======================================================================