[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:              10-24-2007 17:45 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.
====================================================================== 

---------------------------------------------------------------------- 
 kwallace - 10-24-07 17:45  
---------------------------------------------------------------------- 
Is this related to bug # 0009044 ?
(observation based on notes in both bugs, especially mariusmuja2 0070492
and cstadlmann 0063398)

I've observed this symptom (matching 0010151 description) on an Asterisk
1.4-based system (not AsteriskNOW), and saw that "insecure=port" (mentioned
in bug # 0009044) or "insecure=port,invite" (equivalent to "insecure=very")
does not make the symptom go away.  Used the same work-around as in
dmgeurts 0069949. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-24-07 17:45  kwallace       Note Added: 0072482                          
======================================================================