[asterisk-bugs] [Asterisk 0017598]: AGI manager command is not consistent with other commands
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Jul 7 09:45:52 CDT 2010
The following issue requires your FEEDBACK.
======================================================================
https://issues.asterisk.org/view.php?id=17598
======================================================================
Reported By: rrb3942
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17598
Category: Resources/res_agi
Reproducibility: always
Severity: minor
Priority: normal
Status: feedback
Asterisk Version: SVN
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-07-07 09:37 CDT
Last Modified: 2010-07-07 09:45 CDT
======================================================================
Summary: AGI manager command is not consistent with other
commands
Description:
There are a few issues with the AGI manager command.
1. Does not appear to use ActionIDs at all (Very Bad).
2. Uses a CommandID, but this is only used in some of it's response
events. This should be replaced with the ActionID used with the command.
3. The message or response line in the initial acknowledgement should
should indicate that the results will follow.
4. Response Events require you to have 'agi' events enabled in order to
receive them. They are also sent to everyone listening to those events.
This could cause CommandID/ActionID collision.
5. The command should end with a 'Complete' event.
======================================================================
----------------------------------------------------------------------
(0124305) lmadsen (administrator) - 2010-07-07 09:45
https://issues.asterisk.org/view.php?id=17598#c124305
----------------------------------------------------------------------
This kind of borders on the level of feature request. While it may not be
consistent, it's not really considered a bug.
Are you able to provide a patch to implement the functionality you
describe?
Issue History
Date Modified Username Field Change
======================================================================
2010-07-07 09:45 lmadsen Note Added: 0124305
2010-07-07 09:45 lmadsen Status new => feedback
======================================================================
More information about the asterisk-bugs
mailing list