Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated to GIT-18-40bdfff

...

Send a text message. The body of the message that will be sent is what is currently set to MESSAGE(body). This may he come from an incoming message. The technology chosen for sending the message is determined based on a prefix to the to destination parameter.

This application sets the following channel variables:

...

Syntax

No Format
MessageSend(todestination,[from,[to]])
Arguments
  • to destination - A To URI for the message.

...

  • Technology: XMPP
    Specifying a prefix of xmpp: will send the message as an XMPP chat message.
  • from - A From 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, or simply a username such as alice.. This will override a from specified using the MESSAGE dialplan function or the from that may have been on an incoming message.
  • Technology: PJSIP
    The from parameter can be a configured endpoint or in the form of "display-name" <URI>.
  • 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
  • Technology: SIP
    Ignored
  • Technology: XMPP
    Ignored

See Also

Import Version

This documentation was imported from Asterisk Version GIT-18-40bdfff