[Home]

Summary:ASTERISK-21368: Add Manager Events for SIP Registry status changing
Reporter:Dmitriy Serov (Demon)Labels:
Date Opened:2013-03-31 06:00:28Date Closed:2013-07-31 19:15:03
Priority:TrivialRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/Registration
Versions:11.3.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) chan_sip.c.diff
Description: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 :(
Comments:By: Dmitriy Serov (Demon) 2013-03-31 06:02:19.319-0500

Patch for trunk (rev 384409)

By: Dmitriy Serov (Demon) 2013-07-15 01:50:19.820-0500

I can't see issue ASTERISK-21372. Why this issue is marked as clone? And is still unresolved.
By: Matt Jordan (mjordan) 2013-07-15 06:44:07.989-0500

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.