| Summary: | ASTERISK-21250: AddQueueMember does not write membername to the queue log | ||
| Reporter: | Alex Epshteyn (aepshteyn) | Labels: | |
| Date Opened: | 2013-03-14 14:10:02 | Date Closed: | 2013-03-14 16:26:15 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Applications/app_queue |
| Versions: | 1.8.20.1 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | When membername is specified it is not written to the log. Noticed that this was fixed/changed in Asterisk 11 where there is also an option
log_membername_as_agent here is a relevant snippet from 11.2.1 6788 if (ast_strlen_zero(args.membername) || !log_membername_as_agent) { 6789 ast_queue_log(args.queuename, ast_channel_uniqueid(chan), args.interface, "ADDMEMBER", "%s", ""); 6790 } else { 6791 ast_queue_log(args.queuename, ast_channel_uniqueid(chan), args.membername, "ADDMEMBER", "%s", ""); 6792 } | ||
| Comments: | By: Matt Jordan (mjordan) 2013-03-14 16:26:15.100-0500 This was an improvement that was done for [Asterisk 11|https://wiki.asterisk.org/wiki/display/AST/New+in+11]: {noformat} Added new option log_member_name_as_agent, which will cause the membername to be logged in the agent field for ADDMEMBER and REMOVEMEMBER queue events if a state_interface has been set. {noformat} As it was technically a change in behavior/new feature, it was not a candidate for backporting to Asterisk 1.8. By: Alex Epshteyn (aepshteyn) 2013-03-14 23:50:02.758-0500 My understanding was that membername in AddQueueMember command is for the purpose of reporting membername instead of the interface, and that it applies to the log. Is that incorrect? | ||