Summary: | ASTERISK-26687: log_member_name_as_agent is missed in 13.8-cert4 | ||
Reporter: | Alex (AlexRS) | Labels: | log_member_name_as_agent |
Date Opened: | 2017-01-03 02:11:25.000-0600 | Date Closed: | 2017-01-03 02:41:07.000-0600 |
Priority: | Major | Regression? | |
Status: | Closed/Complete | Components: | Applications/app_queue |
Versions: | 13.8.0 | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | Centos 7 asterisk 13.8-cert4 | Attachments: | |
Description: | log_member_name_as_agent doesn work. In log I get (100 - extension, Alex - extension name):
1483430588|MANAGER|help|Local/100@sip/n|ADDMEMBER| 1483430591|Tv-1483430590.0|help|Alex|CONNECT|0|Tv-1483430591.1|0 ADDMEMBER and REMOVEMEMBER write extension number. CONNECT, COMPLETECALLER, etc - extension name. Resulting statistics are collected incorrectly, i.e there are both 'Alex' and '100' agents persists. I cant found somethig aboute removing this options in README or CHANGES PS root@asterisk:/usr/src/asterisk/asterisk-certified-13.8-cert4# grep -si log_member_name_as_agent apps/app_queue.* root@asterisk:/usr/src/asterisk/asterisk-certified-13.8-cert4# PPS. Sorry for my English( | ||
Comments: | By: Asterisk Team (asteriskteam) 2017-01-03 02:11:25.781-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Alex (AlexRS) 2017-01-03 02:41:07.362-0600 Sorry, in was log_membername_as_agent |