[asterisk-bugs] [Asterisk 0014340]: Calls are not matched to correct peer when using callbackextension parameter

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14340 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14340
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1-beta4 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-01-27 04:03 CST
Last Modified:              2009-01-28 13:18 CST
====================================================================== 
Summary:                    Calls are not matched to correct peer when using
callbackextension parameter
Description: 
If there are a number of peers with different callbackextension parameters
the incoming calls are not matched to the right peers

for example with two peers as follows
[trunk1]
host=sip.myitsp.com
callbackextension=9991
...
[trunk2]
host=sip.myitsp.com
callbackextension=9992
...

incoming calls to 9991 and to 9992 are both matched to the peer for 9992
====================================================================== 

---------------------------------------------------------------------- 
 (0098972) oej (manager) - 2009-01-28 13:18
 http://bugs.digium.com/view.php?id=14340#c98972 
---------------------------------------------------------------------- 
This is the same issue as reported in the other bug report. It's the same
mechanism as a register= line, Nick. Nothing else. We still need new code. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-28 13:18 oej            Note Added: 0098972                          
======================================================================