[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:37 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
====================================================================== 

---------------------------------------------------------------------- 
 (0098945) Nick_Lewis (reporter) - 2009-01-28 03:37
 http://bugs.digium.com/view.php?id=14250#c98945 
---------------------------------------------------------------------- 
Ok - it is a feature request to better comply with RFC3261. (Only if
compliance with RFC3261 is claimed is it a bug). I accept that to "do it
all" is a lot of work but to amend my patch to match on callbackextension
instead of peername is relatively straightforward. I think it would be of
benefit but I understand that  you may rather I hold off. 

I think your proposal is fantastic but it may be possible to do the same
thing with
[peername]
type=peer
register=yes 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-28 03:37 Nick_Lewis     Note Added: 0098945                          
======================================================================