| 00:54.34 | *** join/#asterisk-dev acidfu_ (~acidfoo@24-212-247-227.cable.teksavvy.com) |
| 02:09.10 | *** join/#asterisk-dev leedm777 (~textual@50-81-28-152.client.mchsi.com) |
| 05:02.32 | *** join/#asterisk-dev bof22 (~Thunderbi@185.13.183.107) |
| 05:45.40 | *** join/#asterisk-dev jkroon (~jkroon@2c0f:f720:1:0:fcb3:e235:8b0a:1f6b) |
| 06:03.03 | *** join/#asterisk-dev CELYA_ (~Thunderbi@LStLambert-657-1-90-73.w80-13.abo.wanadoo.fr) |
| 06:40.41 | *** join/#asterisk-dev CELYA_ (~Thunderbi@LStLambert-657-1-90-73.w80-13.abo.wanadoo.fr) |
| 06:56.44 | *** join/#asterisk-dev jkroon (~jkroon@uls-154-73-35-201.wall.uls.co.za) |
| 07:01.14 | *** join/#asterisk-dev bof22 (~Thunderbi@185.13.183.107) |
| 07:17.22 | *** join/#asterisk-dev tzafrir (~tzafrir@local.xorcom.com) |
| 07:17.22 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 07:26.09 | *** join/#asterisk-dev hehol (~hehol@gatekeeper.loca.net) |
| 07:26.45 | *** join/#asterisk-dev pchero_work (~pchero@109.70.54.56) |
| 11:14.00 | *** join/#asterisk-dev Marquis42 (~Marquis42@d14-69-130-192.try.wideopenwest.com) |
| 11:39.30 | *** join/#asterisk-dev acidfu_ (~acidfoo@24-212-247-227.cable.teksavvy.com) |
| 12:00.16 | *** join/#asterisk-dev leedm777 (~textual@50-81-28-152.client.mchsi.com) |
| 13:13.27 | *** join/#asterisk-dev leedm777 (textual@nat/digium/x-tyqqcpmsxenjgbry) |
| 13:43.55 | *** join/#asterisk-dev leedm777 (textual@nat/digium/x-grrhkkajagywnptf) |
| 14:05.09 | *** join/#asterisk-dev kharwell (kharwell@nat/digium/x-luxrneesvjkikudm) |
| 14:24.16 | *** join/#asterisk-dev putnopvut (putnopvut@asterisk/master-of-queues/mmichelson) |
| 14:24.16 | *** mode/#asterisk-dev [+o putnopvut] by ChanServ |
| 14:31.02 | *** join/#asterisk-dev cresl1n (Adium@asterisk/libpri-and-libss7-expert/Cresl1n) |
| 14:31.02 | *** mode/#asterisk-dev [+o cresl1n] by ChanServ |
| 14:37.08 | cresl1n | waves |
| 14:39.02 | cresl1n | nudges file |
| 14:39.08 | file | hello hello hello |
| 14:39.23 | file | welcome back |
| 14:39.42 | *** join/#asterisk-dev leedm777 (textual@nat/digium/x-lzwtdtxcsztqarsy) |
| 14:58.44 | *** join/#asterisk-dev rmudgett (rmudgett@nat/digium/x-emieszigwnhtvflb) |
| 14:59.20 | *** join/#asterisk-dev CELYA_ (~Thunderbi@LStLambert-657-1-90-73.w80-13.abo.wanadoo.fr) |
| 16:32.34 | *** join/#asterisk-dev jkroon (~jkroon@2c0f:f720:1:0:fcb3:e235:8b0a:1f6b) |
| 17:07.17 | tm1000 | So in Asterisk 14 "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." |
| 17:07.20 | tm1000 | But I am not seeing that |
| 17:07.52 | tm1000 | for instance. If I run command "database show". The last line I get it "Output: 1997 results found." |
| 17:12.46 | file | that seems... right? |
| 17:18.07 | tm1000 | file: shouldn't it end with "--END COMMAND--" which is what is documented? |
| 17:18.15 | file | no |
| 17:18.20 | tm1000 | Re: https://wiki.asterisk.org/wiki/display/AST/Upgrading+to+Asterisk+14 |
| 17:18.20 | file | it used to |
| 17:18.48 | tm1000 | Ok. So how can I know when a command ends (furthermore the docs are wrong?) file |
| 17:18.55 | file | it says "instead of" |
| 17:19.00 | tm1000 | yeah it does opps |
| 17:19.25 | tm1000 | hmmm so it's really difficult to figure out when a command ends. |
| 17:19.57 | file | does not know as AMI isn't something he knows well |
| 17:20.14 | *** join/#asterisk-dev tzafrir (~tzafrir@bzq-179-40-173.cust.bezeqint.net) |
| 17:20.14 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 17:35.11 | X-Rob | Hmm. That's gunna suck. file -- any way to have that reverted, or at least signal SOMEHOW that the command output is finished? |
| 17:35.24 | file | if you create an issue we can look at it |
| 17:36.14 | X-Rob | wanders off to create a ticket |
| 17:36.23 | file | how do you know something is normally over? |
| 17:39.22 | file | https://gerrit.asterisk.org/#/c/139/ is the change |
| 17:40.56 | file | and starpy has support for it, I believe it just knows the response is complete when it gets a line of \r\n |
| 17:41.53 | tm1000 | file: yes I am just discovering this. |
| 17:44.53 | X-Rob | That seems... unreliable. |
| 17:45.17 | file | but isn't that how AMI fundamentally works, how else do you know when a response is complete or not? |
| 17:45.26 | X-Rob | You wait for --END COMMAND-- |
| 17:45.37 | file | I mean in general |
| 17:46.00 | X-Rob | I was just thinking what else could randomly send \r\n to ami |
| 17:46.06 | X-Rob | but I guess probably nothing |
| 17:47.32 | file | An action or event is terminated by an additional '\r\n' character. |
| 17:47.43 | file | so that's how you know it is over, just like any other message |
| 17:48.34 | X-Rob | Hmm. There's no longer an Action ID in the response? I'm just looking at the code |
| 17:48.58 | file | I don't believe that would have changed |
| 17:49.17 | file | if it did yeah that'd be a bug |
| 17:49.51 | file | it used to have to do it itself because it was special and couldn't use the common code |
| 17:50.00 | file | but it uses the common code because it's no longer 'special' |
| 17:51.36 | X-Rob | Yeah, ignore that |
| 17:51.43 | X-Rob | it was actually unused anyway |
| 17:54.02 | file | so does that... solve... stuff... |
| 17:55.04 | tm1000 | file: I think it'll be fine |
| 17:56.18 | file | X-Rob, et toi? |
| 18:12.55 | X-Rob | file: ack, leave the bug closed |
| 18:25.52 | coreyfarrell | X-Rob: previously if CLI produced a blank line that would result in "\r\n\r\n" being sent over AMI. now each line of CLI output uses an "Output: " header so "\r\n\r\n" cannot be in the middle of the output. |
| 18:31.03 | tm1000 | coreyfarrell: yeah. It's better this way. Just my script has to support Asterisk 11,12,13,14. It's so old that it was never looking for just "\r\n" by itself. I noticed it was sending that right at the moment file mentioned it and once he mentioned it I just wrote the code. So it all works now. |
| 18:31.30 | tm1000 | "its so old" it was just looking for "END COMMAND" so not so old. but anyways |
| 18:45.58 | *** join/#asterisk-dev snuff-work (~snuff-wor@203.87.61.22) |
| 18:45.58 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 19:30.34 | *** join/#asterisk-dev newtonr (~newtonr@173-21-146-94.client.mchsi.com) |
| 19:30.34 | *** mode/#asterisk-dev [+o newtonr] by ChanServ |
| 19:42.35 | *** join/#asterisk-dev snuff-work (~snuff-wor@203.87.61.22) |
| 19:42.35 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 20:00.15 | *** join/#asterisk-dev newtonr (~newtonr@173-21-146-94.client.mchsi.com) |
| 20:00.15 | *** mode/#asterisk-dev [+o newtonr] by ChanServ |
| 20:17.52 | *** join/#asterisk-dev babak (uid19622@gateway/web/irccloud.com/x-efmsfiijuxzmytio) |
| 21:39.00 | tm1000 | anyone know if https://issues.asterisk.org/jira/browse/ASTERISK-26242 is fixed???? It's linked to an internal ticket and DPMA is now at 3.1.0 |
| 21:40.27 | file | should be fixed in 3.1 I think |
| 23:00.08 | *** part/#asterisk-dev kharwell (kharwell@nat/digium/x-luxrneesvjkikudm) |
| 23:08.32 | *** join/#asterisk-dev snuff-work (~snuff-wor@203.87.61.22) |
| 23:08.32 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 23:40.31 | *** join/#asterisk-dev acidfu_ (~acidfoo@24-212-247-227.cable.teksavvy.com) |