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

---------------------------------------------------------------------- 
 blitzrage - 08-13-07 12:31  
---------------------------------------------------------------------- 
Do you mean like a SQL query to check the database? Because you could
utilize func_odbc for that purpose. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-13-07 12:31  blitzrage      Note Added: 0068786                          
======================================================================