Versions Compared

Key

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

...

  • destination - A To URI for the message.
  • Technology: PJSIP
    Specifying a prefix of pjsip: will send the message as a SIP MESSAGE request. 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, an error is returned.

    • 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: PJSIP
    The from parameter can be a configured endpoint or in the form of "display-name" <URI>.is used to specity the From: header in the outgoing SIP MESSAGE. It will override the value specified in MESSAGE(from) which itself will override any from value from an incoming SIP MESSAGE.
  • Technology: SIP
    The from parameter can be a configured peer name or in the form of "display-name" <URI>.
  • Technology: XMPP
    Specifying a prefix of xmpp: will specify the account defined in xmpp.conf to send the message from. Note that this field is required for XMPP messages.
  • 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 will override a to specified using the MESSAGE dialplan function or the to that may have been on an incoming message.
  • Technology: PJSIP
    Ignored 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.
  • Technology: SIP
    Ignored
  • Technology: XMPP
    Ignored

...

This documentation was imported from Asterisk Version GIT-16-63c25d32c2dc7d