[asterisk-bugs] [Asterisk 0015001]: [patch] CoreShowChannels Response does not honor actionid

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15001 
====================================================================== 
Reported By:                sum
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15001
Category:                   Core/ManagerInterface
Reproducibility:            always
Severity:                   trivial
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.2.0-beta1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-04-29 20:07 CDT
Last Modified:              2009-05-26 15:49 CDT
====================================================================== 
Summary:                    [patch] CoreShowChannels Response does not honor
actionid
Description: 
 Response: Success
Eventlist: start
Message: Channels will follow

Channel: SIP/phone-02-00872080
UniqueID: 1241052557.223
Context: from-local
Extension: 1299
Priority: 3
ChannelState: 6
ChannelStateDesc: Up
Application: MusicOnHold
ApplicationData: 
CallerIDnum: 1201
Duration: 00:00:12
AccountCode: 
BridgedChannel: 
BridgedUniqueID: 

Event: CoreShowChannelsComplete
EventList: Complete
ListItems: 1 


ActionID missing.

====================================================================== 

---------------------------------------------------------------------- 
 (0105461) srt (reporter) - 2009-05-26 15:49
 https://issues.asterisk.org/view.php?id=15001#c105461 
---------------------------------------------------------------------- 
One reason is consistency: All other manager actions that send their
response as a series of events include the action id on all events. This is
a feature that existing libraries use to match the events with the action
they answer.

Another one could be that other messages might appear in between the
events, even multiple concurrent CoreStatusActions could be sent (not sure
if this is relevant or if there is some locking in place). 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-26 15:49 srt            Note Added: 0105461                          
======================================================================