]> git.ipfire.org Git - thirdparty/asterisk.git/commit
message & stasis/messaging: make text message variables work in ARI
authorKevin Harwell <kharwell@digium.com>
Mon, 24 Feb 2020 23:16:33 +0000 (17:16 -0600)
committerKevin Harwell <kharwell@digium.com>
Mon, 2 Mar 2020 18:11:50 +0000 (12:11 -0600)
commitfc1d93cf97e6d059584b1feb5d075d22ead31669
tree7b1b293acad43da67d2f255b91b35030f6ce82f6
parentd86cd96c872c803af4edfa9c73de082ffb64a755
message & stasis/messaging: make text message variables work in ARI

When a text message was received any associated variable was not written to
the ARI TextMessageReceived event. This occurred because Asterisk only wrote
out "send" variables. However, even those "send" variables would fail ARI
validation due to a TextMessageVariable formatting bug.

Since it seems the TextMessageReceived event has never been able to include
actual variables it was decided to remove the TextMessageVariable object type
from ARI, and simply return a JSON object of key/value pairs for variables.
This aligns more with how the ARI sendMessage handles variables, and other
places in ARI.

That being the case, and since this is technically an API breaking change (no
one should really be affected since things never really worked) the ARI version
was updated to reflect that.

ASTERISK-28755 #close

Change-Id: Ia6051c01a53b30cf7edef84c27df4ed4479b8b6f
doc/UPGRADE-staging/ari_messaging.txt [new file with mode: 0644]
include/asterisk/message.h
main/message.c
res/ari/ari_model_validators.c
res/ari/ari_model_validators.h
res/stasis/messaging.c
rest-api/api-docs/endpoints.json
rest-api/resources.json