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

noreply at bugs.digium.com noreply at bugs.digium.com
Wed Oct 24 17:55:03 CDT 2007


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:55 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 - 10-24-07 17:55  
---------------------------------------------------------------------- 
kwallace, I don't think they're related as one is an authentication error
where one extention is expected and another is found (sorry for the bad
explanation). The issue in this ticket is about ITSP's not extensions.

insecure=very shows up as insecure=port,invite on my trunks, in fact
changing "very" into just "port" breaks the operation of my did's. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-24-07 17:55  dmgeurts       Note Added: 0072484                          
======================================================================




More information about the asterisk-bugs mailing list