[asterisk-bugs] [JIRA] (ASTERISK-29663) messaging: AMI MessageSend does not support same parameters as dialplan application
Brian J. Murrell (JIRA)
noreply at issues.asterisk.org
Tue Sep 21 07:46:33 CDT 2021
[ https://issues.asterisk.org/jira/browse/ASTERISK-29663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256373#comment-256373 ]
Brian J. Murrell commented on ASTERISK-29663:
---------------------------------------------
@jcolp Did you read the explanation I provided in a [previous comment|https://issues.asterisk.org/jira/browse/ASTERISK-29663?focusedCommentId=256367&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-256367]?
The timing of the change to the documentation for {{ManagerAction_MessageSend()}} is the day after the patch for {{Application_MessageSend()}}'s {{to}} argument was landed, and was changed the same day and in the same commit as {{Application_MessageSend()}}.
The documentation change for {{ManagerAction_MessageSend()}}'s {{to}} parameter was explicitly changed from _Ignored_ to the *exact* same text, word for word, as the *newly added* {{to}} parameter of {{Application_MessageSend()}}, not the text for the {{destination}} parameter of {{Application_MessageSend()}}.
This appears to overwhelmingly indicate that the patch landed was intended to change the behaviour of {{ManagerAction_MessageSend()}}'s {{to}} parameter from doing nothing (_Ignored_ per the documentation before the change) to doing the same thing as {{Application_MessageSend()}}'s new {{to}} parameter. Wouldn't you agree?
> messaging: AMI MessageSend does not support same parameters as dialplan application
> -----------------------------------------------------------------------------------
>
> Key: ASTERISK-29663
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-29663
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_pjsip_messaging
> Affects Versions: 18.6.0
> Reporter: Brian J. Murrell
> Assignee: Brian J. Murrell
>
> The patch in https://gerrit.asterisk.org/c/asterisk/+/15828 seems to achieve the desired behaviour of allowing the {{To:}} header to be specified for the recipient. I have successfully used the new third field of {{MessageSend()}} to override the address in the {{To:}} header.
> When I use AMI {{Action: MessageSend}}, setting the {{To:}} field of the action to the same value as I use for the third field of {{MessageSend()}}, the {{To:}} header is not overwritten with the value of the {{To:}} field from the action fields.
> For example, via AMI I send:
> {noformat}
> Action: MessageSend
> ActionID: 22525
> To: pjsip:my_sip_account at example.com
> From: <sip:asterisk at example.com>
> Base64Body: [redacted]
> {noformat}
> But what gets sent in the SIP {{MESSAGE}} is:
> {noformat}
> MESSAGE sip:my_sip_account@[2001:123:aa:123:0:21db:34e6:9b08:176b]:45016;transport=tcp;pn-tok=[redacted];pn-type=firebase;app-id=[redacted];pn-silent=1;pn-timeout=0 SIP/2.0
> Via: SIP/2.0/TCP [2001:123:aa:123::2]:5060;rport;branch=z9hG4bKPj30ad245f-1b2f-40f6-96b9-58e8d3a182b0;alias
> From: <sip:asterisk at example.com>;tag=5db4ff03-6d42-4b96-ab67-149859ec1073
> To: <sip:my_sip_account@[2001:123:aa:123:0:21db:34e6:9b08:176b];pn-tok=[redacted];pn-type=firebase;app-id=[redacted];pn-silent=1;pn-timeout=0>
> Contact: <sip:my_sip_account@[2001:123:aa:123::2]:5060;transport=TCP>
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list