[asterisk-dev] [Code Review] app_queue log membername when state_interface is set for ADDMEMBER and REMOVEMEMBER events.

jamuel reviewboard at asterisk.org
Fri Jun 24 14:40:00 CDT 2011

This is an automatically generated e-mail. To reply, visit:

Review request for Asterisk Developers and leifmadsen.


app_queue logs the events ADDMEMBER and REMOVEMEMBER the agent field set to interface value rather than the membername value when a member is added with a state_interface value set.  However all other member related queue events are logged with the membername when a state_interface is set. It would seem that these ADD/REMOVE MEMBER events should log the agent field in the same manner. 

This patch addresses the original issue reported in https://issues.asterisk.org/jira/browse/ASTERISK-14769 by providing a queues.conf general configuration option log-member-as-agent. Setting log-member-as-agent = yes will cause the membername to be logged in the agent field for ADDMEMBER and REMOVEMEMBER queue events if a state_interface has been set.

The default value (log-member-as-agent = no) does not alter the existing logging for the ADDMEMBER and REMOVEMEMBER events to maintain existing (buggy) behavior for the sake of backwards compatibility. 

This addresses bug https://issues.asterisk.org/jira/browse/ASTERISK-14769.


  http://svn.asterisk.org/svn/asterisk/tags/ 324845 

Diff: https://reviewboard.asterisk.org/r/1286/diff


Tested add, remove, pause, unpause via AMI and CLI and see the correct log output to queue_log.  Also tested with log-member-as-agent omitted to insure backward compatibility for those queues.conf that might not be updated for this new option. 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20110624/077eb836/attachment.htm>

More information about the asterisk-dev mailing list