| Summary: | ASTERISK-23865: Abstract PJSIP-specific elements away from the pubsub API | ||
| Reporter: | Mark Michelson (mmichelson) | Labels: | |
| Date Opened: | 2014-06-12 11:58:06 | Date Closed: | 2014-06-25 16:00:29 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_pjsip_pubsub |
| Versions: | 12.3.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | In pursuit of incorporating resource list subscriptions into Asterisk, an initial housecleaning step is needed. Currently, SIP notifiers make the assumption that the ast_sip_subscription structure that they operate on is tied directly to a pjsip_evsub structure underneath. However, once resource lists come into play, a notifier may actually be working on a "virtual" ast_sip_subscription that does not have a direct link to a pjsip_evsub.
The idea behind this task is to abstract away direct links between the notifiers and PJSIP. The only PJSIP structures that may remain in the notifier code are PJLIB objects (such as pj_str_t) and certain PJSIP objects that do not necessarily tie directory to a subscription or dialog (pjsip_evsub_state, pjsip_body). A plan has been outlined on the wiki at https://wiki.asterisk.org/wiki/display/AST/PJSIP+Subscription+Abstraction+Plan . Use this as a guideline for changes to the API. If it turns out that some of the suggested changes do not make sense, feel free to do something else. | ||
| Comments: | |||