[asterisk-bugs] [Asterisk 0015829]: queue_log is incosistent for member information - 2 events use member location where the rest use member name
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Sep 17 17:28:41 CDT 2009
The following issue has been REOPENED.
======================================================================
https://issues.asterisk.org/view.php?id=15829
======================================================================
Reported By: somedood
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 15829
Category: Applications/app_queue
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Asterisk Version: SVN
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 216186
Request Review:
======================================================================
Date Submitted: 2009-09-03 16:25 CDT
Last Modified: 2009-09-17 17:28 CDT
======================================================================
Summary: queue_log is incosistent for member information - 2
events use member location where the rest use member name
Description:
In 1.6 queue members can now have names, and queue_log records the name
(when available, otherwise defaults to location) for member related events
except for "ADDMEMBER" and "REMOVEMEMBER". These events record the agent
location instead.
With our queue member setup the location is dynamic depending on where
they logged in from, but the name will be static for a member. With the
current queue_log we can't tell when an agent has logged in, but can tell
when they've handled calls. Can ADDMEMBER and REMOVEMEMBER be changed to
the same behavior as the other member-related events?
======================================================================
----------------------------------------------------------------------
(0110909) somedood (reporter) - 2009-09-17 17:28
https://issues.asterisk.org/view.php?id=15829#c110909
----------------------------------------------------------------------
Would it make a difference if I submitted a patch to fix the problem?
We have a workaround setup on our system, but I'm concerned that others
that use queue member names without using the agent channel will have the
exact same problem. Can I submit a patch and have the changes included in
a changelog/readme or something?
Issue History
Date Modified Username Field Change
======================================================================
2009-09-17 17:28 somedood Note Added: 0110909
2009-09-17 17:28 somedood Status closed => new
2009-09-17 17:28 somedood Resolution no change required =>
reopened
======================================================================
More information about the asterisk-bugs
mailing list