Summary: | ASTERISK-21259: Build a pub/sub architecture for the new SIP channel driver | ||||||
Reporter: | Matt Jordan (mjordan) | Labels: | Asterisk12 NewSIP | ||||
Date Opened: | 2013-03-15 08:35:59 | Date Closed: | 2013-05-10 08:11:40 | ||||
Priority: | Major | Regression? | No | ||||
Status: | Closed/Complete | Components: | Channels/chan_pjsip | ||||
Versions: | 12 | Frequency of Occurrence | |||||
Related Issues: |
| ||||||
Environment: | Attachments: | ||||||
Description: | The new SIP work needs the ability to perform SUBSCRIBE/NOTIFY/PUBLISH functionality. As the first stage in that, we need to be able to provide a framework to the rest of Asterisk that let's people:
* Access subscribers and find out what they're subscribed to * Be notified when a subscription is created or changed for a subscriber * Submit notifications for subscribers to the framework on a periodic basis or on an as needed basis. In order to 'plan for the feature', we may want to view the concept of a subscription separately from the concept of an endpoint, such that it's easier to implement RLS in the future. At the end of this task, we should be able to process SUBSCRIBE requests, creating subscriptions, cancelling subscriptions, having appropriate timers, etc. | ||||||
Comments: |