[asterisk-bugs] [JIRA] (ASTERISK-23154) Manager: ExtensionStatus event does not present information in a human readable way

Digium Subversion (JIRA) noreply at issues.asterisk.org
Mon Jan 27 15:11:03 CST 2014


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

Digium Subversion closed ASTERISK-23154.
----------------------------------------

    Resolution: Fixed
    
> Manager: ExtensionStatus event does not present information in a human readable way
> -----------------------------------------------------------------------------------
>
>                 Key: ASTERISK-23154
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23154
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Core/ManagerInterface
>    Affects Versions: SVN, 1.8.26.0, 11.8.0, 12.1.0
>            Reporter: Jonathan Rose
>            Assignee: Kevin Harwell
>
> ExtensionStatus displays the extension status purely as a number which is set based on a field of the ast_state_cb_info struct called 'exten_state'.
> exten_state isn't really a state value. The enumerator has a few values that operate as states, those being:
> AST_EXTENSION_REMOVED
> AST_EXTENSION_DEACTIVATED
> AST_EXTENSION_NOT_INUSE
> AST_EXTENSION_INUSE
> But after that things start to get a little weird.  The extension state value that I noticed in particular was 16 which would be:
> AST_EXTENSION_INUSE | AST_EXTENSION_ONHOLD
> and allegedly it would be possible to hit other combinations such as NOT_INUSE | UNAVAILABLE
> Obviously changing the value of the Status field in the event is off the table, but a new value should be added to present this information
> in a human readable way, possibly simply by providing a function that turns an extension state into a comma separated list of the items in
> the enumerator.
> Another part of this task could be adding documentation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list