Files
asterisk/include/asterisk/res_pjsip_pubsub.h
Mark Michelson a27abd02e6 Decouple subscription handling from NOTIFY/PUBLISH body generation.
When the PJSIP pubsub framework was created, subscription handlers were required
to state what event they handled along with what body types they knew how to
generate. While this serves well when implementing a base RFC, it has problems
when trying to extend the body to support non-standard or proprietary body
elements. The code also was NOTIFY-specific, meaning that when the time comes
that we start writing code to send out PUBLISH requests with MWI or presence
bodies, we would likely find ourselves duplicating code that had previously been
written.

This changeset introduces the concept of body generators and body supplements. A
body generator is responsible for allocating a native structure for a given body
type, providing the primary body content, converting the native structure to a
string, and deallocating resources. A body supplement takes the primary body
content (the native structure, not a string) generated by the body generator and
adds nonstandard elements to the body. With these elements living in their own
module, it becomes easy to extend our support for body types and to re-use
resources when sending a PUBLISH request.

Body generators and body supplements register themselves with the pubsub core,
similar to how subscription and publish handlers had done. Now, subscription
handlers do not need to know what type of body content they generate, but they
still need to inform the pubsub core about what the default body type for a
given event package is. The pubsub core keeps track of what body generators and
body supplements have been registered. When a SUBSCRIBE arrives, the pubsub core
will check that there is a subscription handler for the event in the SUBSCRIBE,
then it will check that there is a body generator that can provide the content
specified in the Accept header(s).

Because of the nature of body generators and supplements, it means
res_pjsip_exten_state and res_pjsip_mwi have been completely gutted. They no
longer worry about body types, instead calling
ast_sip_pubsub_generate_body_content() when they need to generate a NOTIFY body.

Review: https://reviewboard.asterisk.org/r/3150


git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/12@407016 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2014-01-31 22:11:18 +00:00

712 lines
24 KiB
C

/*
* Asterisk -- An open source telephony toolkit.
*
* Copyright (C) 2013, Digium, Inc.
*
* Mark Michelson <mmichelson@digium.com>
*
* See http://www.asterisk.org for more information about
* the Asterisk project. Please do not directly contact
* any of the maintainers of this project for assistance;
* the project provides a web site, mailing lists and IRC
* channels for your use.
*
* This program is free software, distributed under the terms of
* the GNU General Public License Version 2. See the LICENSE file
* at the top of the source tree.
*/
#ifndef _RES_PJSIP_PUBSUB_H
#define _RES_PJSIP_PUBSUB_H
#include "asterisk/linkedlists.h"
/* Forward declarations */
struct pjsip_rx_data;
struct pjsip_tx_data;
struct pjsip_evsub;
struct ast_sip_endpoint;
struct ast_datastore;
struct ast_datastore_info;
/*!
* \brief Opaque structure representing a publication
*/
struct ast_sip_publication;
/*!
* \brief Callbacks that publication handlers will define
*/
struct ast_sip_publish_handler {
/*! \brief The name of the event this handler deals with */
const char *event_name;
/*! \brief Publications */
struct ao2_container *publications;
/*!
* \brief Called when a PUBLISH to establish a new publication arrives.
*
* \param endpoint The endpoint from whom the PUBLISH arrived
* \param rdata The PUBLISH request
* \retval NULL PUBLISH was not accepted
* \retval non-NULL New publication
*
* \note The callback is expected to send a response for the PUBLISH in success cases.
*/
struct ast_sip_publication *(*new_publication)(struct ast_sip_endpoint *endpoint, pjsip_rx_data *rdata);
/*!
* \brief Called when a PUBLISH for an existing publication arrives.
*
* This PUBLISH may be intending to change state or it may be simply renewing
* the publication since the publication is nearing expiration. The callback
* is expected to send a response to the PUBLISH.
*
* \param pub The publication on which the PUBLISH arrived
* \param rdata The PUBLISH request
* \retval 0 Publication was accepted
* \retval non-zero Publication was denied
*
* \note The callback is expected to send a response for the PUBLISH.
*/
int (*publish_refresh)(struct ast_sip_publication *pub, pjsip_rx_data *rdata);
/*!
* \brief Called when a publication has reached its expiration.
*/
void (*publish_expire)(struct ast_sip_publication *pub);
/*!
* \brief Called when a PUBLISH arrives to terminate a publication.
*
* \param pub The publication that is terminating
* \param rdata The PUBLISH request terminating the publication
*
* \note The callback is expected to send a response for the PUBLISH.
*/
void (*publish_termination)(struct ast_sip_publication *pub, pjsip_rx_data *rdata);
AST_LIST_ENTRY(ast_sip_publish_handler) next;
};
/*!
* \brief Create a new publication
*
* Publication handlers should call this when a PUBLISH arrives to establish a new publication.
*
* \param endpoint The endpoint from whom the PUBLISHes arrive
* \param rdata The PUBLISH that established the publication
* \retval NULL Failed to create a publication
* \retval non-NULL The newly-created publication
*/
struct ast_sip_publication *ast_sip_create_publication(struct ast_sip_endpoint *endpoint, pjsip_rx_data *rdata);
/*!
* \brief Given a publication, get the associated endpoint
*
* \param pub The publication
* \retval NULL Failure
* \retval non-NULL The associated endpoint
*/
struct ast_sip_endpoint *ast_sip_publication_get_endpoint(struct ast_sip_publication *pub);
/*!
* \brief Create a response to an inbound PUBLISH
*
* The created response must be sent using ast_sip_publication_send_response
*
* \param pub The publication
* \param status code The status code to place in the response
* \param rdata The request to which the response is being made
* \param[out] tdata The created response
*/
int ast_sip_publication_create_response(struct ast_sip_publication *pub, int status_code, pjsip_rx_data *rdata,
pjsip_tx_data **tdata);
/*!
* \brief Send a response for an inbound PUBLISH
*
* \param pub The publication
* \param rdata The request to which the response was made
* \param tdata The response to the request
*/
pj_status_t ast_sip_publication_send_response(struct ast_sip_publication *pub, pjsip_rx_data *rdata,
pjsip_tx_data *tdata);
/*!
* \brief Register a publish handler
*
* \retval 0 Handler was registered successfully
* \retval non-zero Handler was not registered successfully
*/
int ast_sip_register_publish_handler(struct ast_sip_publish_handler *handler);
/*!
* \brief Unregister a publish handler
*/
void ast_sip_unregister_publish_handler(struct ast_sip_publish_handler *handler);
/*!
* \brief Add a datastore to a SIP publication
*
* Note that SIP uses reference counted datastores. The datastore passed into this function
* must have been allocated using ao2_alloc() or there will be serious problems.
*
* \param publication The publication to add the datastore to
* \param datastore The datastore to be added to the subscription
* \retval 0 Success
* \retval -1 Failure
*/
int ast_sip_publication_add_datastore(struct ast_sip_publication *publication, struct ast_datastore *datastore);
/*!
* \brief Retrieve a publication datastore
*
* The datastore retrieved will have its reference count incremented. When the caller is done
* with the datastore, the reference counted needs to be decremented using ao2_ref().
*
* \param publication The publication from which to retrieve the datastore
* \param name The name of the datastore to retrieve
* \retval NULL Failed to find the specified datastore
* \retval non-NULL The specified datastore
*/
struct ast_datastore *ast_sip_publication_get_datastore(struct ast_sip_publication *publication, const char *name);
/*!
* \brief Remove a publication datastore from the publication
*
* This operation may cause the datastore's free() callback to be called if the reference
* count reaches zero.
*
* \param publication The publication to remove the datastore from
* \param name The name of the datastore to remove
*/
void ast_sip_publication_remove_datastore(struct ast_sip_publication *publication, const char *name);
/*!
* \brief Opaque structure representing an RFC 3265 SIP subscription
*/
struct ast_sip_subscription;
/*!
* \brief Role for the subscription that is being created
*/
enum ast_sip_subscription_role {
/* Sending SUBSCRIBEs, receiving NOTIFYs */
AST_SIP_SUBSCRIBER,
/* Sending NOTIFYs, receiving SUBSCRIBEs */
AST_SIP_NOTIFIER,
};
/*!
* \brief Data for responses to SUBSCRIBEs and NOTIFIEs
*
* Some of PJSIP's evsub callbacks expect us to provide them
* with data so that they can craft a response rather than have
* us create our own response.
*
* Filling in the structure is optional, since the framework
* will automatically respond with a 200 OK response if we do
* not provide it with any additional data.
*/
struct ast_sip_subscription_response_data {
/*! Status code of the response */
int status_code;
/*! Optional status text */
const char *status_text;
/*! Optional additional headers to add to the response */
struct ast_variable *headers;
/*! Optional body to add to the response */
struct ast_sip_body *body;
};
#define AST_SIP_MAX_ACCEPT 32
struct ast_sip_subscription_handler {
/*! The name of the event this handler deals with */
const char *event_name;
/*! The types of body this handler accepts.
*
* \note This option has no bearing when the handler is used in the
* notifier role. When in a subscriber role, this header is used to
* populate the Accept: header of an outbound SUBSCRIBE request
*/
const char *accept[AST_SIP_MAX_ACCEPT];
/*!
* \brief Default body type defined for the event package this handler handles.
*
* Typically, a SUBSCRIBE request will contain one or more Accept headers that tell
* what format they expect the body of NOTIFY requests to use. However, every event
* package is required to define a default body format type to be used if a SUBSCRIBE
* request for the event contains no Accept header.
*/
const char *default_accept;
/*!
* \brief Called when a subscription is to be destroyed
*
* This is a subscriber and notifier callback.
*
* The handler is not expected to send any sort of requests or responses
* during this callback. The handler MUST, however, begin the destruction
* process for the subscription during this callback.
*/
void (*subscription_shutdown)(struct ast_sip_subscription *subscription);
/*!
* \brief Called when a SUBSCRIBE arrives in order to create a new subscription
*
* This is a notifier callback.
*
* If the notifier wishes to accept the subscription, then it can create
* a new ast_sip_subscription to do so.
*
* If the notifier chooses to create a new subscription, then it must accept
* the incoming subscription using pjsip_evsub_accept() and it must also
* send an initial NOTIFY with the current subscription state.
*
* \param endpoint The endpoint from which we received the SUBSCRIBE
* \param rdata The SUBSCRIBE request
* \retval NULL The SUBSCRIBE has not been accepted
* \retval non-NULL The newly-created subscription
*/
struct ast_sip_subscription *(*new_subscribe)(struct ast_sip_endpoint *endpoint,
pjsip_rx_data *rdata);
/*!
* \brief Called when an endpoint renews a subscription.
*
* This is a notifier callback.
*
* Because of the way that the PJSIP evsub framework works, it will automatically
* send a response to the SUBSCRIBE. However, the subscription handler must send
* a NOTIFY with the current subscription state when this callback is called.
*
* The response_data that is passed into this callback is used to craft what should
* be in the response to the incoming SUBSCRIBE. It is initialized with a 200 status
* code and all other parameters are empty.
*
* \param sub The subscription that is being renewed
* \param rdata The SUBSCRIBE request in question
* \param[out] response_data Data pertaining to the SIP response that should be
* sent to the SUBSCRIBE
*/
void (*resubscribe)(struct ast_sip_subscription *sub,
pjsip_rx_data *rdata, struct ast_sip_subscription_response_data *response_data);
/*!
* \brief Called when a subscription times out.
*
* This is a notifier callback
*
* This indicates that the subscription has timed out. The subscription handler is
* expected to send a NOTIFY that terminates the subscription.
*
* \param sub The subscription that has timed out
*/
void (*subscription_timeout)(struct ast_sip_subscription *sub);
/*!
* \brief Called when a subscription is terminated via a SUBSCRIBE or NOTIFY request
*
* This is a notifier and subscriber callback.
*
* The PJSIP subscription framework will automatically send the response to the
* request. If a notifier receives this callback, then the subscription handler
* is expected to send a final NOTIFY to terminate the subscription.
*
* \param sub The subscription being terminated
* \param rdata The request that terminated the subscription
*/
void (*subscription_terminated)(struct ast_sip_subscription *sub, pjsip_rx_data *rdata);
/*!
* \brief Called when a subscription handler's outbound NOTIFY receives a response
*
* This is a notifier callback.
*
* \param sub The subscription
* \param rdata The NOTIFY response
*/
void (*notify_response)(struct ast_sip_subscription *sub, pjsip_rx_data *rdata);
/*!
* \brief Called when a subscription handler receives an inbound NOTIFY
*
* This is a subscriber callback.
*
* Because of the way that the PJSIP evsub framework works, it will automatically
* send a response to the NOTIFY. By default this will be a 200 OK response, but
* this callback can change details of the response by returning response data
* to use.
*
* The response_data that is passed into this callback is used to craft what should
* be in the response to the incoming SUBSCRIBE. It is initialized with a 200 status
* code and all other parameters are empty.
*
* \param sub The subscription
* \param rdata The NOTIFY request
* \param[out] response_data Data pertaining to the SIP response that should be
* sent to the SUBSCRIBE
*/
void (*notify_request)(struct ast_sip_subscription *sub,
pjsip_rx_data *rdata, struct ast_sip_subscription_response_data *response_data);
/*!
* \brief Called when it is time for a subscriber to resubscribe
*
* This is a subscriber callback.
*
* The subscriber can reresh the subscription using the pjsip_evsub_initiate()
* function.
*
* \param sub The subscription to refresh
* \retval 0 Success
* \retval non-zero Failure
*/
int (*refresh_subscription)(struct ast_sip_subscription *sub);
/*!
* \brief Converts the subscriber to AMI
*
* This is a subscriber callback.
*
* \param sub The subscription
* \param buf The string to write AMI data
*/
void (*to_ami)(struct ast_sip_subscription *sub, struct ast_str **buf);
AST_LIST_ENTRY(ast_sip_subscription_handler) next;
};
/*!
* \brief Create a new ast_sip_subscription structure
*
* In most cases the pubsub core will create a general purpose subscription
* within PJSIP. However, PJSIP provides enhanced support for the following
* event packages:
*
* presence
* message-summary
*
* If either of these events are handled by the subscription handler, then
* the special-purpose event subscriptions will be created within PJSIP,
* and it will be expected that your subscription handler make use of the
* special PJSIP APIs.
*
* \param handler The subsription handler for this subscription
* \param role Whether we are acting as subscriber or notifier for this subscription
* \param endpoint The endpoint involved in this subscription
* \param rdata If acting as a notifier, the SUBSCRIBE request that triggered subscription creation
*/
struct ast_sip_subscription *ast_sip_create_subscription(const struct ast_sip_subscription_handler *handler,
enum ast_sip_subscription_role role, struct ast_sip_endpoint *endpoint, pjsip_rx_data *rdata);
/*!
* \brief Get the endpoint that is associated with this subscription
*
* This function will increase the reference count of the endpoint. Be sure to
* release the reference to it when you are finished with the endpoint.
*
* \retval NULL Could not get endpoint
* \retval non-NULL The endpoint
*/
struct ast_sip_endpoint *ast_sip_subscription_get_endpoint(struct ast_sip_subscription *sub);
/*!
* \brief Get the serializer for the subscription
*
* Tasks that originate outside of a SIP servant thread should get the serializer
* and push the task to the serializer.
*
* \param sub The subscription
* \retval NULL Failure
* \retval non-NULL The subscription's serializer
*/
struct ast_taskprocessor *ast_sip_subscription_get_serializer(struct ast_sip_subscription *sub);
/*!
* \brief Get the underlying PJSIP evsub structure
*
* This is useful when wishing to call PJSIP's API calls in order to
* create SUBSCRIBEs, NOTIFIES, etc. as well as get subscription state
*
* This function, as well as all methods called on the pjsip_evsub should
* be done in a SIP servant thread.
*
* \param sub The subscription
* \retval NULL Failure
* \retval non-NULL The underlying pjsip_evsub
*/
pjsip_evsub *ast_sip_subscription_get_evsub(struct ast_sip_subscription *sub);
/*!
* \brief Get the underlying PJSIP dialog structure
*
* Call this function when information needs to be retrieved from the
* underlying pjsip dialog.
*
* This function, as well as all methods called on the pjsip_evsub should
* be done in a SIP servant thread.
*
* \param sub The subscription
* \retval NULL Failure
* \retval non-NULL The underlying pjsip_dialog
*/
pjsip_dialog *ast_sip_subscription_get_dlg(struct ast_sip_subscription *sub);
/*!
* \brief Send a request created via a PJSIP evsub method
*
* Callers of this function should take care to do so within a SIP servant
* thread.
*
* \param sub The subscription on which to send the request
* \param tdata The request to send
* \retval 0 Success
* \retval non-zero Failure
*/
int ast_sip_subscription_send_request(struct ast_sip_subscription *sub, pjsip_tx_data *tdata);
/*!
* \brief Alternative for ast_datastore_alloc()
*
* There are two major differences between this and ast_datastore_alloc()
* 1) This allocates a refcounted object
* 2) This will fill in a uid if one is not provided
*
* DO NOT call ast_datastore_free() on a datastore allocated in this
* way since that function will attempt to free the datastore rather
* than play nicely with its refcount.
*
* \param info Callbacks for datastore
* \param uid Identifier for datastore
* \retval NULL Failed to allocate datastore
* \retval non-NULL Newly allocated datastore
*/
struct ast_datastore *ast_sip_subscription_alloc_datastore(const struct ast_datastore_info *info, const char *uid);
/*!
* \brief Add a datastore to a SIP subscription
*
* Note that SIP uses reference counted datastores. The datastore passed into this function
* must have been allocated using ao2_alloc() or there will be serious problems.
*
* \param subscription The ssubscription to add the datastore to
* \param datastore The datastore to be added to the subscription
* \retval 0 Success
* \retval -1 Failure
*/
int ast_sip_subscription_add_datastore(struct ast_sip_subscription *subscription, struct ast_datastore *datastore);
/*!
* \brief Retrieve a subscription datastore
*
* The datastore retrieved will have its reference count incremented. When the caller is done
* with the datastore, the reference counted needs to be decremented using ao2_ref().
*
* \param subscription The subscription from which to retrieve the datastore
* \param name The name of the datastore to retrieve
* \retval NULL Failed to find the specified datastore
* \retval non-NULL The specified datastore
*/
struct ast_datastore *ast_sip_subscription_get_datastore(struct ast_sip_subscription *subscription, const char *name);
/*!
* \brief Remove a subscription datastore from the subscription
*
* This operation may cause the datastore's free() callback to be called if the reference
* count reaches zero.
*
* \param subscription The subscription to remove the datastore from
* \param name The name of the datastore to remove
*/
void ast_sip_subscription_remove_datastore(struct ast_sip_subscription *subscription, const char *name);
/*!
* \brief Register a subscription handler
*
* \retval 0 Handler was registered successfully
* \retval non-zero Handler was not registered successfully
*/
int ast_sip_register_subscription_handler(struct ast_sip_subscription_handler *handler);
/*!
* \brief Unregister a subscription handler
*/
void ast_sip_unregister_subscription_handler(struct ast_sip_subscription_handler *handler);
/*!
* \brief Pubsub body generator
*
* A body generator is responsible for taking Asterisk content
* and converting it into a body format to be placed in an outbound
* SIP NOTIFY or PUBLISH request.
*/
struct ast_sip_pubsub_body_generator {
/*!
* \brief Content type
* In "plain/text", "plain" is the type
*/
const char *type;
/*!
* \brief Content subtype
* In "plain/text", "text" is the subtype
*/
const char *subtype;
/*!
* \brief allocate body structure.
*
* Body generators will have this method called when a NOTIFY
* or PUBLISH body needs to be created. The type returned depends on
* the type of content being produced for the body. The data parameter
* is provided by the subscription handler and will vary between different
* event types.
*
* \param data The subscription data provided by the event handler
* \retval non-NULL The allocated body
* \retval NULL Failure
*/
void *(*allocate_body)(void *data);
/*!
* \brief Add content to the body of a SIP request
*
* The body of the request has already been allocated by the body generator's
* allocate_body callback.
*
* \param body The body of the SIP request. The type is determined by the
* content type.
* \param data The subscription data used to populate the body. The type is
* determined by the content type.
*/
int (*generate_body_content)(void *body, void *data);
/*!
* \brief Convert the body to a string.
*
* \param body The request body.
* \param str The converted string form of the request body
*/
void (*to_string)(void *body, struct ast_str **str);
/*!
* \brief Deallocate resources created for the body
*
* Optional callback to destroy resources allocated for the
* message body.
*
* \param body Body to be destroyed
*/
void (*destroy_body)(void *body);
AST_LIST_ENTRY(ast_sip_pubsub_body_generator) list;
};
/*!
* \brief Body supplement
*
* Body supplements provide additions to bodies not already
* provided by body generators. This may include proprietary
* extensions, optional content, or other nonstandard fare.
*/
struct ast_sip_pubsub_body_supplement {
/*!
* \brief Content type
* In "plain/text", "plain" is the type
*/
const char *type;
/*!
* \brief Content subtype
* In "plain/text", "text" is the subtype
*/
const char *subtype;
/*!
* \brief Add additional content to a SIP request body.
*
* A body generator will have already allocated a body and populated
* it with base data for the event. The supplement's duty is, if desired,
* to extend the body to have optional data beyond what a base RFC specifies.
*
* \param body The body of the SIP request. The type is determined by the
* body generator that allocated the body.
* \param data The subscription data used to populate the body. The type is
* determined by the content type.
*/
int (*supplement_body)(void *body, void *data);
AST_LIST_ENTRY(ast_sip_pubsub_body_supplement) list;
};
/*!
* \since 13.0.0
* \brief Generate body content for a PUBLISH or NOTIFY
*
* This function takes a pre-allocated body and calls into registered body
* generators in order to fill in the body with appropriate details.
* The primary body generator will be called first, followed by the
* supplementary body generators
*
* \param content_type The content type of the body
* \param content_subtype The content subtype of the body
* \param data The data associated with body generation.
* \param[out] str The string representation of the generated body
* \retval 0 Success
* \retval non-zero Failure
*/
int ast_sip_pubsub_generate_body_content(const char *content_type,
const char *content_subtype, void *data, struct ast_str **str);
/*!
* \since 13.0.0
* \brief Register a body generator with the pubsub core.
*
* This may fail if an attempt is made to register a primary body supplement
* for a given content type if a primary body supplement for that content type
* has already been registered.
*
* \param generator Body generator to register
* \retval 0 Success
* \retval -1 Failure
*/
int ast_sip_pubsub_register_body_generator(struct ast_sip_pubsub_body_generator *generator);
/*!
* \since 13.0.0
* \brief Unregister a body generator with the pubsub core.
*
* \param generator Body generator to unregister
*/
void ast_sip_pubsub_unregister_body_generator(struct ast_sip_pubsub_body_generator *generator);
/*!
* \since 13.0.0
* \brief Register a body generator with the pubsub core.
*
* This may fail if an attempt is made to register a primary body supplement
* for a given content type if a primary body supplement for that content type
* has already been registered.
*
* \param generator Body generator to register
* \retval 0 Success
* \retval -1 Failure
*/
int ast_sip_pubsub_register_body_supplement(struct ast_sip_pubsub_body_supplement *supplement);
/*!
* \since 13.0.0
* \brief Unregister a body generator with the pubsub core.
*
* \param generator Body generator to unregister
*/
void ast_sip_pubsub_unregister_body_supplement(struct ast_sip_pubsub_body_supplement *supplement);
/*!
* \since 13.0.0
* \brief Get the body type used for this subscription
*/
const char *ast_sip_subscription_get_body_type(struct ast_sip_subscription *sub);
/*!
* \since 13.0.0
* \brief Get the body subtype used for this subscription
*/
const char *ast_sip_subscription_get_body_subtype(struct ast_sip_subscription *sub);
#endif /* RES_PJSIP_PUBSUB_H */