[asterisk-bugs] [JIRA] (ASTERISK-24049) Asterisk Manager Interface: A number of list type responses aren't using astman_send_listack

[Richard Mudgett (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-24049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on ASTERISK-24049 started by Richard Mudgett.

> Asterisk Manager Interface: A number of list type responses aren't using astman_send_listack
> --------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-24049
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24049
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/ManagerInterface
>    Affects Versions: 1.8.29.0, 11.11.0, 12.4.0
>            Reporter: Jonathan Rose
>            Assignee: Richard Mudgett
>
> The following manager commands issue lists without using the astman_send_listack command (instead just using astman_send_ack) and this means they generally aren't informing the recipient they will be receiving a list in the proper manner.  It's not something that is hard to program around or anything, but it's inconsistent and unnecessary.
> BridgeList
> BridgeInfo
> BridgeTechnologyList
> DAHDIShowChannels
> PRIShowSpans
> ParkedCalls (both 1.8-11 and 12+)
> Parkinglots (both 1.8-11 and 12+ -- actually, 1.8 might not having Parkinglots command... it looks like it only unregisters it without ever registering it in the first place)
> QueueSummary
> QueueStatus
> Another thing worth noting is that every call to astman_send_listack uses 'start' for the value of the listflag. It looks like once upon a time, the idea was for 'cancel' and 'complete' to also be sent via astman_send_listack, but I don't really know what circumstances would call for that and most of the time an event is just issued to indicate that an action is finished sending lists such as 'ParkedCallsComplete'. I'm not sure if this needs to be addressed for any reason... it just seems topical since this issue relates to unifying the behavior of manager event lists.



--
This message was sent by Atlassian JIRA
(v6.2#6252)