[asterisk-bugs] [Asterisk 0014250]: [patch] Incoming calls matched to the wrong peer

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14250 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14250
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.0 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-01-15 05:58 CST
Last Modified:              2009-01-15 12:33 CST
====================================================================== 
Summary:                    [patch] Incoming calls matched to the wrong peer
Description: 
If there are multiple sip trunks with the same ITSP then an incoming call
is arbitarily matched to the last peer with the same host IP address. This
is not a serious problem because the DID is still correct but it does have
many insidious effects due to the incorrect channel name
====================================================================== 

---------------------------------------------------------------------- 
 (0097944) oej (manager) - 2009-01-15 12:33
 http://bugs.digium.com/view.php?id=14250#c97944 
---------------------------------------------------------------------- 
Ok, that was a new angle - that you can't find the proper peer in manager
actions. You did not say that originally.

I will look at your patch when you have it, but I ask you to understand
that we have to be very careful so we don't break the current architecture
- like it or not. 

Again, don't call IP matching "authentication". It's not. It's just IP
matching and it's very insecure. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-15 12:33 oej            Note Added: 0097944                          
======================================================================