[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 02:26 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
====================================================================== 

---------------------------------------------------------------------- 
 (0098518) oej (manager) - 2009-01-23 02:26
 http://bugs.digium.com/view.php?id=14250#c98518 
---------------------------------------------------------------------- 
This patch is not approved as it breaks a lot of the architecture, not only
mixing the extension namespace and the peer namespace. We can't do that. 
And we can't change the internal workings and break the current
architecture, which a lot of people have configurations that rely on.

I do however agree that there is a problem that needs to be solved at some
point with the matching of SIP trunks coming in, regardless if we register
or not. We need to match on the domain of the sender and implement a new
type of object (not a user or a peer) that matches on domains. That way we
can match one providers cluster of servers -regardless of IP. If we want to
restrict IP access, we can use ACLs. I would happily start coding on that,
provided I can find funding somewhere.

That has to be seen as a feature request though. The problem with peer
matching on registrations is well-known and there are several working
workarounds published on the net. I do realize that these doesn't really
work well with AMI clients, which puts more pressure on finding a good
solution. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-23 02:26 oej            Note Added: 0098518                          
======================================================================