Skip to content

MessageSend.md: Update manual to section #172

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gtjoseph merged 1 commit into from
Jan 21, 2026
+2 −2
Merged

MessageSend.md: Update manual to section #172

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...sterisk_18_Documentation/API_Documentation/Dialplan_Applications/MessageSend.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,7 @@ The 'from' parameter can be a configured peer name or in the form of "display-na
* __Technology: XMPP__<br>
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.<br>

* `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.<br>
* `to` - A To URI for the message if needed for the message technology being used to send this message. This should be a SIP(S) URI, such as 'Alice <sip: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.<br>

* __Technology: PJSIP__<br>
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.<br>
Expand Down
2 changes: 1 addition & 1 deletion ...erisk_18.9_Documentation/API_Documentation/Dialplan_Applications/MessageSend.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,7 @@ The 'from' parameter can be a configured peer name or in the form of "display-na
* __Technology: XMPP__<br>
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.<br>

* `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.<br>
* `to` - A To URI for the message if needed for the message technology being used to send this message. This should be a SIP(S) URI, such as 'Alice <sip: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.<br>

* __Technology: PJSIP__<br>
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.<br>
Expand Down