diff options
| author | Matthew Jordan <mjordan@digium.com> | 2012-07-19 22:17:13 +0000 |
|---|---|---|
| committer | Matthew Jordan <mjordan@digium.com> | 2012-07-19 22:17:13 +0000 |
| commit | 86ff5585fd4de538c65bcbdce54cd9ef74b4e784 (patch) | |
| tree | ec6bdea2bbe0e590e472ef43d47fd51bd15d39d6 /channels | |
| parent | f80278792480fe432a32608773f172576dc84839 (diff) | |
Add the ability to specify technology specific documentation
A number of applications/AMI commands in Asterisk have specific behavioral
differences depending on the resource or channel technology those
applications are executed on. For example, the MessageSend application/
command is technology agnostic, but how the channel drivers that support
that functionality behave is dependant on the protocols and channel
driver implementation. Prior to this patch, those details were either
documented in the application/command documentation itself, or were left
undocumented.
This patch adds a new element to the documentation schema, <info/>. An info
node is essentially a piece of technology specific reference information that
can be included by any top level XML documentation node. For example, the
MessageSend application can now include XMPP/SIP specific information, where
that technology specific information can be defined in chan_motif/res_xmpp/
chan_sip. Likewise, that information can also be included in the MessageSend
AMI command.
Review: https://reviewboard.asterisk.org/r/2049
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@370278 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'channels')
| -rw-r--r-- | channels/chan_sip.c | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/channels/chan_sip.c b/channels/chan_sip.c index eadf9b961..9d57ad5bd 100644 --- a/channels/chan_sip.c +++ b/channels/chan_sip.c @@ -572,6 +572,14 @@ ASTERISK_FILE_VERSION(__FILE__, "$Revision$") via multiple <literal>Variable: name=value</literal> sequences.</para> </description> </manager> + <info name="SIPMessageFromInfo" language="en_US" tech="SIP"> + <para>The <literal>from</literal> parameter can be a configured peer name + or in the form of "display-name" <URI>.</para> + </info> + <info name="SIPMessageToInfo" language="en_US" tech="SIP"> + <para>Specifying a prefix of <literal>sip:</literal> will send the + message as a SIP MESSAGE request.</para> + </info> ***/ static int min_expiry = DEFAULT_MIN_EXPIRY; /*!< Minimum accepted registration time */ |