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

---------------------------------------------------------------------- 
 dmgeurts - 09-05-07 02:16  
---------------------------------------------------------------------- 
bkruse,

Indeed it is. I wonder if it's more an issue with Asterisk rather than the
gui...

However my workaround does work now, which is to match the dialed number
on the 'wrong' DID context so the calls are forwarded to the right
extension. Though for more complex dial plans this would not be ideal
(though I suppose one could forward to a context rather than an extension). 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
09-05-07 02:16  dmgeurts       Note Added: 0069949                          
======================================================================