From 2438636a31f3b8da2a72b577399ef8ba9d40098c Mon Sep 17 00:00:00 2001 From: Matthew Jordan Date: Sat, 28 Sep 2013 22:56:29 +0000 Subject: [PATCH] res_pjsip_notify: Add documentation We forgot to add documentation for res_pjsip_notify, which would prevent it from being loaded. Whoops. This patch also updates res_pjsip_notify to use pjsip_notify.conf, which now has its own sample file in the configs directory as well. Review: https://reviewboard.asterisk.org/r/2835/ git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/12@400121 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- configs/pjsip_notify.conf.sample | 57 ++++++++++++++++++++++++++++++++ res/res_pjsip_notify.c | 42 ++++++++++++++++++++++- 2 files changed, 98 insertions(+), 1 deletion(-) create mode 100644 configs/pjsip_notify.conf.sample diff --git a/configs/pjsip_notify.conf.sample b/configs/pjsip_notify.conf.sample new file mode 100644 index 0000000000..8224ee1ff4 --- /dev/null +++ b/configs/pjsip_notify.conf.sample @@ -0,0 +1,57 @@ +; rfc3842 +; put empty "Content=>" at the end to have CRLF after last body line + +[clear-mwi] +Event=>message-summary +Content-type=>application/simple-message-summary +Content=>Messages-Waiting: no +Content=>Message-Account: sip:asterisk@127.0.0.1 +Content=>Voice-Message: 0/0 (0/0) +Content=> + +; Aastra + +[aastra-check-cfg] +Event=>check-sync + +[aastra-xml] +Event=>aastra-xml + +; Digium + +[digium-check-cfg] +Event=>check-sync + +; Linksys + +[linksys-cold-restart] +Event=>reboot_now + +[linksys-warm-restart] +Event=>restart_now + +; Polycom + +[polycom-check-cfg] +Event=>check-sync + +; Sipura + +[sipura-check-cfg] +Event=>resync + +[sipura-get-report] +Event=>report + +; snom + +[snom-check-cfg] +Event=>check-sync\;reboot=false + +[snom-reboot] +Event=>check-sync\;reboot=true + +; Cisco + +[cisco-check-cfg] +Event=>check-sync diff --git a/res/res_pjsip_notify.c b/res/res_pjsip_notify.c index c90a91b15d..8e9b202616 100644 --- a/res/res_pjsip_notify.c +++ b/res/res_pjsip_notify.c @@ -50,6 +50,46 @@ Parameters will be placed into the notify as SIP headers. + + Module that supports sending NOTIFY requests to endpoints from external sources + + + Unused, but reserved. + + + Configuration of a NOTIFY request. + + Each key-value pair in a notify + configuration section defines either a SIP header to send + in the request or a line of content in the request message + body. A key of Content is treated + as part of the message body and is appended in sequential + order; any other header is treated as part of the SIP + request. + + + A key/value pair to add to a NOTIFY request. + + If the key is Content, + it will be treated as part of the message body. Otherwise, + it will be added as a header in the NOTIFY request. + The following headers are reserved and cannot be + specified: + + + + + + + + + + + + + + + ***/ #define CONTENT_TYPE_SIZE 64 @@ -59,7 +99,7 @@ * \internal * \brief The configuration file containing NOTIFY payload types to send. */ -static const char notify_config[] = "sip_notify.conf"; +static const char notify_config[] = "pjsip_notify.conf"; struct notify_option_item { const char *name;