<br><div class="gmail_quote">On Wed, May 11, 2011 at 8:51 AM, Vlad Paiu <span dir="ltr"><<a href="mailto:vladpaiu@opensips.org">vladpaiu@opensips.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div text="#000000" bgcolor="#ffffff">
Hello Brett,<br>
<br>
A well formed MI command should end with two '\n\n' characters. When
you do<div class="im"><br>
echo -e ":address_dump:my_fifo\n\n"<br>
<br></div>
,your MI command ends with three '\n', because echo adds an extra \n at
the end, unless you use the -n parameter.<br>
<br>
So what happens is that OpenSIPS successfully processes your
address_dump MI command, and then reads the third \n.<br>
It treats it as an empty MI command, and attempts to block and read the
second \n signaling the end of the MI command, and there it gets stuck.<br><br></div></blockquote><div><br></div><div>Vlad,</div><div>Thanks for this explaination, that makes a *lot* of sense. However, I feel like sending "crap" to the fifo shouldn't break it, right? At least, it should eventually clear itself out or reset itself without requiring a restart. Right? If I had sent it just one more carriage return, do you think it would clear it out?</div>
<div><br>-Brett</div><div> </div></div>