Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated to GIT-16-b0027c6

...

No Format
Action: MessageSend
ActionID: <value>
[Destination:] <value>
[To:] <value>
From: <value>
Body: <value>
Base64Body: <value>
Variable: <value>

...

  • ActionID - ActionID for this transaction. Will be returned.
  • Destination - A To URI for the message. If Destination is provided, the To parameter can also be supplied and may alter the message based on the specified message technology.
    For backwards compatibility, if Destination is not provided, the To parameter must be provided and will be used as the message destination.
  • Technology: PJSIP
    The destination parameter is used to construct the Request URI for an outgoing message. It can be in one of the following formats, all prefixed with the pjsip: message tech.

endpoint - Request URI comes from the endpoint's default aor and contact.
endpoint/aor - Request URI comes from the specific aor/contact.
endpoint@domain - Request URI from the endpoint's default aor and contact. The domain is discarded.

These all use the endpoint to send the message with the specified URI:

endpoint/<sips:host>>
endpoint/<sips:user@host>
endpoint/"display name" <sips:host>
endpoint/"display name" <sips:user@host>
endpoint/sips:host
endpoint/sips:user@host
endpoint/host
endpoint/user@host

These all use the default endpoint to send the message with the specified URI:

<sips:host>
<sips:user@host>
"display name" <sips:host>
"display name" <sips:user@host>
sips:host
sips:user@host

These use the default endpoint to send the message with the specified host:

host
user@host

This form is similar to

...

a dialstring:

PJSIP/user@endpoint

You still need to prefix the destination with the pjsip: message technology prefix. For example: pjsip:PJSIP/8005551212@myprovider. The endpoint contact's URI will have the user inserted into it and will become the Request URI. If the contact URI already has a user specified, it will be replaced.

    • endpoint - Request URI comes from the endpoint's default aor and contact.
    • endpoint/aor - Request URI comes from the specific aor/contact.
    • endpoint@domain - Request URI from the endpoint's default aor and contact. The domain is discarded.
    • endpoint/<sips:host>>
    • endpoint/<sips:user@host>
    • endpoint/"display name" <sips:host>
    • endpoint/"display name" <sips:user@host>
    • endpoint/sips:host
    • endpoint/sips:user@host
    • endpoint/host
    • endpoint/user@host
    • <sips:host>
    • <sips:user@host>
    • "display name" <sips:host>
    • "display name" <sips:user@host>
    • sips:host
    • sips:user@host
    • host
    • user@host
    • PJSIP/user@endpoint
  • Technology: SIP
    Specifying a prefix of sip: will send the message as a SIP MESSAGE request.
  • Technology: XMPP
    Specifying a prefix of xmpp: will send the message as an XMPP chat message.
  • To - A To URI for the message if needed for the message technology being used to send this message. This can be a SIP(S) URI, such as Alice <sip:alice@atlanta.com>, or a string in the format alice@atlanta.com.
    This parameter is required if the Destination parameter is not provided.
  • Technology: PJSIP
    The to parameter is used to specity the To: header in the outgoing SIP MESSAGE. It will override the value specified in MESSAGE(to) which itself will override any to value from an incoming SIP MESSAGE.

...

This documentation was imported from Asterisk Version GIT-16-2c2dc7db0027c6