[asterisk-bugs] [Asterisk 0016965]: [patch] DBGet response does not end with a 'Complete' event
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Mar 5 12:44:31 CST 2010
The following issue has been UPDATED.
======================================================================
https://issues.asterisk.org/view.php?id=16965
======================================================================
Reported By: rrb3942
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 16965
Category: Core/ManagerInterface
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Asterisk Version: 1.4.29.1
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-03-04 14:45 CST
Last Modified: 2010-03-05 12:44 CST
======================================================================
Summary: [patch] DBGet response does not end with a
'Complete' event
Description:
DBGet returns its response as an event, but it does not send a 'Complete'
event.
For example take this Action -
Action: DBGet
Family: Foo
Key: bar
ActionID: 1
How it responds now -
Response: Success
Message: Result will follow
ActionID: 1
Event: DBGetResponse
Family: Foo
Key: bar
Value: sip123
ActionID: 1
How it should respond -
Response: Success
Message: Result will follow
ActionID: 1
Event: DBGetResponse
Family: Foo
Key: bar
Value: sip123
ActionID: 1
Event: DBGetComplete
ActionID: 1
This will bring DBGet in line with how other manager actions behave when
responding with events.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2010-03-05 12:44 rrb3942 Summary DBGet response does not
end with a 'Complete' event => [patch] DBGet response does not end with a
'Complete' event
======================================================================
More information about the asterisk-bugs
mailing list