[asterisk-bugs] [Asterisk 0012958]: Queue members as SIP/XXXX do not update status correctly

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12958 
====================================================================== 
Reported By:                evandro
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12958
Category:                   Applications/app_queue
Reproducibility:            sometimes
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.19 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-06-30 13:07 CDT
Last Modified:              2008-11-12 13:39 CST
====================================================================== 
Summary:                    Queue members as SIP/XXXX do not update status
correctly
Description: 
I have queue members logged in as SIP/XXXX with Addqueuemember(01|SIP/XXX),
and when there are many calls on the queue, the status of this members
delay to update, making that calls do not send to the members, unless i
remove and add members in the queue again

When have a few numbers of calls, the system work normally

anyone can help?
====================================================================== 

---------------------------------------------------------------------- 
 (0094809) putnopvut (administrator) - 2008-11-12 13:39
 http://bugs.digium.com/view.php?id=12958#c94809 
---------------------------------------------------------------------- 
blitzrage: yes, I was thinking that that would solve thiagarcia's
particular case. lazytt's is something different though, and is most likely
a local-channel specific thing.

If the /n doesn't work any more, then I would suspect there's been some
sort of change to local channel device state handling, and I should perhaps
try to figure out what that change is. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-12 13:39 putnopvut      Note Added: 0094809                          
======================================================================