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

---------------------------------------------------------------------- 
 (0098942) Nick_Lewis (reporter) - 2009-01-28 03:02
 http://bugs.digium.com/view.php?id=14250#c98942 
---------------------------------------------------------------------- 
The contact in the request line of a trunk INVITE must actually contact the
peer. A match needs to be made between the contact info and something in
the peer. If the peername cannot be used because the contact is set to
callbackextension then the match must be with the callbackextension. 

All trunk peer definitions will need to contain a callbackextension
parameter for invite matching purposes irrespective of whether they use
integrated registration or use a registration string in the common section.
The existence of a callbackextension parameter cannot imply integrated
registration so a register=yes/no parameter is required to set integrated
registration. 

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