Dmitry Melekhov
2018-Oct-12 06:35 UTC
[asterisk-users] 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!
On Fri, Oct 12, 2018, at 3:35 AM, Dmitry Melekhov wrote:> 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 ?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: www.digium.com & www.asterisk.org
Dmitry Melekhov
2018-Oct-12 10:22 UTC
[asterisk-users] asterisk 16 manager --END COMMAND--
12.10.2018 14:10, Joshua C. Colp пишет:> On Fri, Oct 12, 2018, at 3:35 AM, Dmitry Melekhov wrote: >> 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 ? > 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:14 was not LTS, you know...> > 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. >Very pity that you break compatibility...