[asterisk-bugs] [Asterisk-GUI 0010151]: AsteriskNOW DID into wrong context

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10151 
====================================================================== 
Reported By:                dmgeurts
Assigned To:                pari
====================================================================== 
Project:                    Asterisk-GUI
Issue ID:                   10151
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.5 
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!): 1127 
Disclaimer on File?:        No 
Request Review:              
====================================================================== 
Date Submitted:             07-07-2007 10:16 CDT
Last Modified:              09-05-2007 08:39 CDT
====================================================================== 
Summary:                    AsteriskNOW DID into wrong context
Description: 
Two accounts from same ITSP, each with a different DID number. When both
accounts are active and registered, only one picks up the call. This
reproducible and consisted. It is always the same trunk/context that the
incoming call is put into.

Disabling either account will result in correct operation, only reachable
on the DID which is registered not the other.

I have no workaround as I can't manage to catch the call using the called
number. Debugging shows 's' and in the wrong context.
====================================================================== 

---------------------------------------------------------------------- 
 bkruse - 09-05-07 08:39  
---------------------------------------------------------------------- 
I believe it is an asterisk issue, but still needs to be resolved.

I know that we are having a similar issue internally and would love to
debug this with you.

I think it is matching off of the IP address its registered, rather than
the DID, which does make sense.

Can explain how you are making it work? and would it be a solution for
everyone? or just for this case.

I will look into it, thanks for the bug report, I believe this is REALLY a
bug, not just a configuration issue, thanks again Siya :]

-bk 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
09-05-07 08:39  bkruse         Note Added: 0069966                          
======================================================================