Skip to end of metadata
Go to start of metadata

MessageSend

Synopsis

Send an out of call message to an endpoint.

Description

Syntax

Action: MessageSend
ActionID: <value>
To: <value>
From: <value>
Body: <value>
Base64Body: <value>
Variable: <value>
Arguments
  • ActionID - ActionID for this transaction. Will be returned.
  • To - The URI the message is to be sent to.
  • 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.
  • Technology: SIP
    Ignored
  • Technology: XMPP
    Ignored
  • From - A From URI for the message if needed for the message technology being used to send this message.
  • Technology: PJSIP
    The from parameter 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.
  • Body - The message body text. This must not contain any newlines as that conflicts with the AMI protocol.
  • Base64Body - Text bodies requiring the use of newlines have to be base64 encoded in this field. Base64Body will be decoded before being sent out. Base64Body takes precedence over Body.
  • Variable - Message variable to set, multiple Variable: headers are allowed. The header value is a comma separated list of name=value pairs.

See Also

Import Version

This documentation was imported from Asterisk Version GIT-18-a40e58a

  • No labels