[asterisk-bugs] [Asterisk 0014752]: Chan_Sip route to an incorrect DID

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14752 
====================================================================== 
Reported By:                alex70
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14752
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.1.0-rc3 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!): 184149 
Request Review:              
====================================================================== 
Date Submitted:             2009-03-25 12:32 CDT
Last Modified:              2009-03-26 05:28 CDT
====================================================================== 
Summary:                    Chan_Sip route to an incorrect DID
Description: 
I have 2 voip numbers configured correctly. I can make outbound call from
both of them but I can receive only from the first one. Seems that DID2
context in users.conf route to DID1 in extensions.conf finding no match.

  
====================================================================== 

---------------------------------------------------------------------- 
 (0102218) alex70 (reporter) - 2009-03-26 05:28
 http://bugs.digium.com/view.php?id=14752#c102218 
---------------------------------------------------------------------- 
Looking on various posts on internet I have found this behaviour is well
known but not resolved yet. 

It seems to occur when two accounts are registered with the same server,
or at least the same IP address. 

The work around is to use the same context for both accounts.

Anyway I think it will be good to fix this problem as even the asterisk
gui is not able to handle this situation. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-26 05:28 alex70         Note Added: 0102218                          
======================================================================