[Home]

Summary:ASTERISK-30236: app_queue.c: Properly escape commas in MONITOR* variables.
Reporter:Sean Bright (seanbright)Labels:
Date Opened:2022-09-18 16:34:48Date Closed:
Priority:MinorRegression?
Status:In Progress/In ProgressComponents:Applications/app_queue
Versions:GIT 16.28.0 18.14.0 19.6.0 Frequency of
Occurrence		Constant
Related
Issues:
Environment:Attachments:
Description:The contents of the {{MONITOR_FILENAME}} and {{MONITOR_EXEC}} variables are evaluated when a queue member is connected to a caller, allowing information about the member to be included in the filename or post process execution.
   
This is made possible by using {{^\{MEMBERINTERFACE}}} syntax instead of {{$\{MEMBERINTERFACE}}} when assigning a value to {{MONITOR_FILENAME}} so that evaluation does not occur immediately. The {{MONITOR_EXEC}} variable is handled similarly.
   
Because {{MONITOR_FILENAME}} and {{MONITOR_EXEC}} are ultimately passed through the standard dialplan application parsing code, any commas in need to be escaped. This currently happens before variable substitution but should instead be occurring afterwards.

The main consequence of this change is that you can now use dialplan functions with multiple arguments in {{MONITOR_FILENAME}} without the commas being escaped before variable replacement occurs.
Comments:By: Asterisk Team (asteriskteam) 2022-09-18 16:34:53.421-0500

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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

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].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].