Here is an example of the data Asterisk sends over for the channel data. In the dialplan field, there is an app_name and an app_data field that is not included in the DialplanCEP. This is useful information to know for Stasis. If Asterisk sends the call to Stasis, the app_name would be "Stasis" and the app_data would be the stasis application's identifier, which is Application used for the ARI connection. The app_data can also include additional parameters that should be passed from Asterisk to the ARI/Stasis application. These would be separated by a space (forming a string array).
Here is an example of the data Asterisk sends over for the channel data. In the dialplan field, there is an app_name and an app_data field that is not included in the DialplanCEP. This is useful information to know for Stasis. If Asterisk sends the call to Stasis, the app_name would be "Stasis" and the app_data would be the stasis application's identifier, which is Application used for the ARI connection. The app_data can also include additional parameters that should be passed from Asterisk to the ARI/Stasis application. These would be separated by a space (forming a string array).
{ "id":"1675093673.34", "name":"Local/10000@IS-00000004;1", "state":"Up", "protocol_id":"", "caller":{"name":"LocalTest","number":"9000"}, "connected":{"name":"LocalTest","number":"9000"}, "accountcode":"", "dialplan":{"context":"IS","exten":"createcall","priority":23,"app_name":"AGI","app_data":"agi:async"}, "creationtime":"2023-01-30T09:47:53.350-0600", "language":"en" }
I just submitted a Pull Request for code that adds this support.