[asterisk-bugs] [JIRA] (ASTERISK-25662) Malformed AGI 520 Usage response
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Wed Jan 6 08:23:33 CST 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-25662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=228851#comment-228851 ]
Asterisk Team commented on ASTERISK-25662:
------------------------------------------
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].
> Malformed AGI 520 Usage response
> --------------------------------
>
> Key: ASTERISK-25662
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-25662
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_agi
> Affects Versions: 11.21.0, 13.6.0
> Reporter: Tony Mountifield
> Severity: Minor
>
> In res_agi.c, there are the following three lines:
> {code}
> ast_agi_send(agi->fd, chan, "520-Invalid command syntax. Proper usage follows:\n");
> ast_agi_send(agi->fd, chan, "%s", c->usage);
> ast_agi_send(agi->fd, chan, "520 End of proper usage.\n");
> {code}
> However, the value of {{c->usage}} generated from the XML appears to lack a terminating newline. This means that the {{520 End of proper usage.}} will not appear at the beginning of a line and this will therefore confuse a parser of AGI responses.
> Suggest the middle line be changed as follows:
> {code}
> ast_agi_send(agi->fd, chan, "%s\n", c->usage);
> {code}
> This bug has probably existed ever since the original change to XML help. Obviously, it only occurs when an AGI client sends a malformed command.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list