[asterisk-bugs] [Asterisk 0014256]: [patch] SIP Channel name is not unique

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14256 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   14256
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-16 04:31 CST
Last Modified:              2009-01-27 04:20 CST
====================================================================== 
Summary:                    [patch] SIP Channel name is not unique
Description: 
The name of the asterisk channel that is created on an incoming sip call is
not unique

There can be two trunks with different ITSP but same username e.g.
[trunk1]
username=nicklewis
host=sip.myitsp1.com

[trunk2]
username=nicklewis
host=sip.myitsp2.net

The sip channel name of the asterisk channel that is created when a call
comes into these trunks is "SIP/nicklewis" in both cases. The sip channel
should be named after the peername instead e.g. "SIP/trunk1" and
"SIP/trunk2" 
====================================================================== 

---------------------------------------------------------------------- 
 (0098831) oej (manager) - 2009-01-27 04:20
 http://bugs.digium.com/view.php?id=14256#c98831 
---------------------------------------------------------------------- 
OK then. Since it's not really a security issue, I don't think we'll change
1.2. But 1.4 and later needs to be fixed. Will discuss with file on how to
push this forward, since this is assigned to him by him. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-27 04:20 oej            Note Added: 0098831                          
======================================================================