[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:                     confirmed
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-23 08:36 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
====================================================================== 

---------------------------------------------------------------------- 
 (0098545) Nick_Lewis (reporter) - 2009-01-23 08:36
 http://bugs.digium.com/view.php?id=14250#c98545 
---------------------------------------------------------------------- 
Re "You still mix namespaces":

You have chosen to interpret the AOR in the request line of an INVITE from
a UAC as an "extension" and you have chosen to interpret the Contact in the
request line of an INVITE from a UAS also as an "extension". This
interpretation receives no support from RFC3261. They may both be request
lines in INVITES but the one from a UAS contains different objects to the
one from a UAC. The AOR from a UAC and the Contact from a UAS do not need
to be interpreted in the same way as each other and can be mapped to
different asterisk namespaces without abusing any architectural principles. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-23 08:36 Nick_Lewis     Note Added: 0098545                          
======================================================================