[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-20-2007 10:23 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-20-07 10:23  
---------------------------------------------------------------------- 
its fine no stress ...

as the the pause status is not stored for realtime users
(persistantmembers off and not dynamicialy added) for a auto pause there is
no write back to set the status a reload will loose this ....

what i sugest is a 2 prong approach 

1)auto pause is tempory for say XX seconds ... (i prefer this approach as
it will allow a call to escalate to a higher penalty caller ... and have
the agent ring next time round) (set autopause to a integer)
2)as is (if autopause set to yes) the user is permanently paused

in both cases esp 2 the DB needs to be updated to reflect this ...

now using a view in pg at least you cannot update it so the table used by
queues should not be a view ... and there should be a way of determining
the loged in/out status from the query ....

hope this makes some sense ... 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-20-07 10:23  irroot         Note Added: 0069095                          
======================================================================