Asterisk 16 Manager –END COMMAND–
Hello!
Just upgraded asterisk from 13 to 16 and found that php-agi library is not compatible.
It waits for –END COMMAND–
after command is completed,
but, as I see from tcpdump, now asterisk does not send such string after command is completed.
Could you tell me, is it possible to get previous behaviour ?
Or what now manager sends as command completed ?
Thank you!
—
4 thoughts on - Asterisk 16 Manager –END COMMAND–
It is not possible to return the old behavior, and the new behavior is in the UPGRADE notes for 14 (UPGRADE-14.txt) as that is when it happened:
AMI:
– The Command action now sends the output from the CLI command as a series
of Output headers for each line instead of as a block of text with the
–END COMMAND– delimiter to match the output from other actions.
Commands that fail to execute (no such command, invalid syntax etc.) now
return an Error response instead of Success.
—
Joshua C. Colp Digium – A Sangoma Company | Senior Software Developer
445 Jan Davis Drive NW – Huntsville, AL 35806 – US
Check us out at: http://www.digium.com & http://www.asterisk.org
—
12.10.2018 14:10, Joshua C. Colp пишет:
14 was not LTS, you know…
—
When upgrading it’s important to check all the UPGRADE notes for the intermediate versions as well, as there may be things which impact you.
We try not to, and this was certainly a case where the feedback that happened afterwards was taken into account for any future changes.
—
Joshua C. Colp Digium – A Sangoma Company | Senior Software Developer
445 Jan Davis Drive NW – Huntsville, AL 35806 – US
Check us out at: http://www.digium.com & http://www.asterisk.org
—
The old AMI protocol was so broken, so it was hardly possible to make any compatible client implementation. Whatever you do, it would break on some corner cases. This change fixed a little bit of this mess.
And if some client library is not properly updated for major Asterisk releases, then that is not Asterisk to blame.
Jacek
—