Summary:	ASTERISK-23705: PJSIP: Add outbound subscriptions and inbound NOTIFY request handling (MWI, Device State)
Reporter:	Matt Jordan (mjordan)	Labels:
Date Opened:	2014-05-01 15:53:00	Date Closed:
Priority:	Major	Regression?
Status:	Open/New	Components:	Resources/res_pjsip Resources/res_pjsip_pubsub
Versions:		Frequency of Occurrence
Related Issues:	must be completed before resolving ASTERISK-27309 Feature Parity with chan_sip is duplicated by ASTERISK-27312 Outbound SUBSCRIBE Support
Environment:		Attachments:
Description:	One of the things that didn't make the cut in PJSIP land initially was the concept of outbound subscriptions. We need to add it. This task consists of two parts: # Adding outbound subscriptions, and managing all the fun that it entails # Understanding inbound NOTIFY requests and raising the appropriate Stasis messages Outbound subscriptions will need a new configuration item. This should be discussed on the -dev list before being implemented, but it _could_ look like this: {noformat} [external_asterisk] type=endpoint outbound_subscription=external_asterisk [external_asterisk] type=outbound_subscription mailbox=1000@context {noformat} This uses a similar nomenclature to outbound registration. We would create a subscription for an event package mapping to 'mailbox' for {{1000@context}}. {{res_pjsip_pubsub}} already contains some APIs for this; these should be extended to support outbound subscriptions. NOTIFY request handling should be handled by the body generators. A body generator should have the ability to take in the body from a NOTIFY request and return back a stasis_message to publish. The virtual table for body generators should be modified to support such a callback, and the various resource modules updated to pass back the appropriate stasis messages.
Comments: