[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 14:42:17 CDT 2009


The following issue has been UPDATED. 
====================================================================== 
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:                     closed
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 216186 
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-09-03 16:25 CDT
Last Modified:              2009-09-17 14:42 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?



====================================================================== 

---------------------------------------------------------------------- 
 (0110886) lmadsen (administrator) - 2009-09-17 14:42
 https://issues.asterisk.org/view.php?id=15829#c110886 
---------------------------------------------------------------------- 
This is actually a feature request without a patch provided (which are not
handed on the issue tracker).

Additionally, it was pointed out that if this change was made to general
Asterisk, we would break existing implementations that require this
functionality.

If you need this functionality for your own system, there are many
qualified consultants who could implement this on the asterisk-biz mailing
list. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-17 14:42 lmadsen        Note Added: 0110886                          
2009-09-17 14:42 lmadsen        Status                   new => closed       
2009-09-17 14:42 lmadsen        Resolution               open => no change
required
======================================================================




More information about the asterisk-bugs mailing list