| Summary: | ASTERISK-21489: Stasis Core - Refactor PeerStatus events | ||||
| Reporter: | Matt Jordan (mjordan) | Labels: | Asterisk12 | ||
| Date Opened: | 2013-04-17 09:22:41 | Date Closed: | 2013-06-22 07:42:30 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Channels/chan_iax2 Channels/chan_sip/General Core/Channels Core/Stasis | ||
| Versions: | Frequency of Occurrence | ||||
| Related Issues: |
| ||||
| Environment: | Attachments: | ||||
| Description: | {{chan_sip}}, {{chan_iax2}}, and {{chan_skinny}} raise a PeerStatus event. This event is most closely related to the concept of an endpoint, and the lifetime messages of an endpoint in the Stasis cache may subsume the endpoint.
Where the change in state of the endpoint can be captured by an endpoint snapshot, the messages should use snapshot changes. Where it cannot, specific Stasis-Core messages should be raised. The same Stasis-Core messages for PeerStatus need to be relayed by the {{chan_gulp}} related modules as well. | ||||
| Comments: | |||||