[asterisk-bugs] [Asterisk 0010424]: Allow realtime members on non realtime queues/A member with priorty < 0 is logged out
noreply at bugs.digium.com
noreply at bugs.digium.com
Fri Aug 10 09:59:53 CDT 2007
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-10-2007 09:59 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-10-07 09:59
----------------------------------------------------------------------
I guess I can kinda see where you're going with the setting the priority
field to a negative value in the database, but to do this I just have a
table with my members and create a view in the database, then point the
queue_members in extconfig.conf to the view. The view then only lists the
members that have the 'logged_on' flag set in the primary table.
I think that functionality could be confusing to people, so I'd rather see
it live outside in the database, and not in Asterisk.
The realtime members being used in a non-realtime queue I would agree with
though (didn't realize that didn't work)
Issue History
Date Modified Username Field Change
======================================================================
08-10-07 09:59 blitzrage Note Added: 0068721
======================================================================
More information about the asterisk-bugs
mailing list