[asterisk-bugs] [Asterisk 0010424]: Allow realtime members on non realtime queues/A member with priorty < 0 is logged out

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10424 
====================================================================== 
Reported By:                irroot
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   10424
Category:                   Applications/app_queue
Reproducibility:            N/A
Severity:                   trivial
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.10  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             08-10-2007 02:18 CDT
Last Modified:              08-13-2007 12:42 CDT
====================================================================== 
Summary:                    Allow realtime members on non realtime queues/A
member with priorty < 0 is logged out
Description: 

hi there some trivial patches extending on the recent changes (adding
update_realtime_members) it seems to make logic sence to allow realtime
agents on non realtime queues (ive been doing this for over a year
already).

ive also been setting the priorty field in SQL to a negitive value as
opposed to deleteing the agent to log them off and then back to there
existing value to log them on again.
====================================================================== 

---------------------------------------------------------------------- 
 irroot - 08-13-07 12:42  
---------------------------------------------------------------------- 
yeah sure im doing that but there is one place it is lacking ...

when a member is auto paused it should be writen back as this happens
inside the app it should be updated inside the app.

this seems to be the only change made inside the app that should be writen
back IMHO.

the behavior is not what is expected in this case when there is a reload. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-13-07 12:42  irroot         Note Added: 0068789                          
======================================================================