[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:                oej
====================================================================== 
Project:                    Asterisk
Issue ID:                   14250
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
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-28 03:49 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
====================================================================== 

---------------------------------------------------------------------- 
 (0098946) oej (manager) - 2009-01-28 03:49
 http://bugs.digium.com/view.php?id=14250#c98946 
---------------------------------------------------------------------- 
I don't see where we are not compliant with RFC3261. It's our
implementation that is a mess, on the wire we do everything right. We
register a contact and route the call based on the INVITE request URI. No
problem with that.

The whole user/peer/friend implementation was a poor design from start,
inherited from chan_iax with some patches that made it worse and this is
something I've gradually changed for many years. Now is the time to move
forward and make good designs instead of patching and making it even worse.
We can't have two parallell architectures. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-28 03:49 oej            Note Added: 0098946                          
======================================================================