[asterisk-bugs] [JIRA] (ASTERISK-22556) [patch] MailboxCount & ExtensionState commands - request multiple mailboxes/extensions

[Joshua Colp (JIRA)]

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

Joshua Colp updated ASTERISK-22556:
-----------------------------------

    Summary: [patch] MailboxCount & ExtensionState commands - request multiple mailboxes/extensions  (was: MailboxCount & ExtensionState commands - request multiple mailboxes/extensions)

> [patch] MailboxCount & ExtensionState commands - request multiple mailboxes/extensions
> --------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-22556
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22556
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Core/ManagerInterface/NewFeature
>    Affects Versions: 1.8.23.1, 13.18.4
>            Reporter: Mike Ser
>         Attachments: managerPatch3
>
>
> We use asterisk gui & initial loading can take forever with large installations (100+ extensions,) as each extension requires two AMI requests to send and receive the ExtensionState & MailboxStatus commands.  I have modified these commands in manager.c to accept a comma delimited list of extensions and build a reply for the entire list.  
> I also have made modifications to asterisk gui to take advantage of this feature and load all the ExtensionState's and MailboxStatus' with a single command which executes very quickly, which I will be glad to submit if these changes are accepted.
> In addition the asterisk gui can now refresh the extension status very well, where in the past it required a separate javascipt setInterval for each extension, which for large installations performed so poorly that we had commented it out.
> I don't see where on this form I can attach the code changes.  I did fill out a license agreement.  Perhaps it hasn't been approved?  It's actually a trivial change IMHO.  



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