[asterisk-bugs] [JIRA] (ASTERISK-21368) Add Manager Events for SIP Registry status changing

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-21368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207960#comment-207960 ] 

Matt Jordan commented on ASTERISK-21368:
----------------------------------------

ASTERISK-21372 is an internal issue used only for time tracking and planning purposes. Any actual updates done to this issue will be done on this issue (ASTERISK-21368).

And yes this is unresolved, because no one from the developer community has taken on the patch and it is still in the queue to be worked.

If you'd like to speed up the response times for this issue:

Since this is an improvement, the patch should be written against trunk. In trunk, however, channel drivers no longer access AMI directly, they access it over the Stasis message bus. The Registry events were changed to be publications over said message bus. A patch that pushes the messages over the bus written for trunk would get worked faster - as it is, there is a higher engineering effort with the patch in its current state as we'll have to rewrite it for trunk.
                
> Add Manager Events for SIP Registry status changing
> ---------------------------------------------------
>
>                 Key: ASTERISK-21368
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21368
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Channels/chan_sip/Registration
>    Affects Versions: 11.3.0
>            Reporter: Dmitriy Serov
>            Severity: Trivial
>         Attachments: chan_sip.c.diff
>
>
> There are no some manager events notification of changing peer State to REG_STATE_NOAUTH and REG_STATE_REJECTED.
> For example: Owner of external peer can change password and our asterisk will not feel something wrong :(

--
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