[Home]

Summary:ASTERISK-16970: queue.log is inconsistently using interface or membername
Reporter:Michael Gaudette (bluefox)Labels:
Date Opened:2010-11-17 03:11:47.000-0600Date Closed:2011-08-18 13:17:52
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Applications/app_queue
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:When logging agent status in the queue.log file, Asterisk uses sometimes the interface and the agent name, making it difficult to use the log to follow an agent's status.

ex:
1289984171|1289984156.113335|5555555555-test|SIP/phone1|ADDMEMBER|
1289984171|NONE|5555555555-test|agent_a|UNPAUSE|
1289984649|1289984632.113336|5555555555-test|SIP/phone1|REMOVEMEMBER|
1289984856|NONE|5555555555-test|agent_a|PAUSE|

ADD and REMOVEMEMBER are using the interface, but PAUSE/UNPAUSE the agent name.

NOTE: I do specify the agent name when ADDing the queue member.


****** STEPS TO REPRODUCE ******

pause, unpause, add or remove a queue member from the dialplan.  Check queue.log and see results.

****** ADDITIONAL INFORMATION ******

Asterisk should show more consistency in this case, and use the agent name only when it was defined so logs are easier to follow and use.

Comments:By: Leif Madsen (lmadsen) 2010-12-06 13:41:41.000-0600

Agreed 100%. I think it is going to be difficult to change this in previous versions due to backwards compatibility and breaking interfaces which may rely on this (or have worked around the issue).

Thanks for the suggestion!

By: Kinsey Moore (kmoore) 2011-08-18 13:17:38.295-0500

This has been taken care of by ASTERISK-14769 and committed.  It is now an option that is off by default.