<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div>Really? Interesting, I had no idea. I thought the rtpproxy control protocol was binary and did not lend itself easily to interaction in this manner. Thanks for the tip. </div><div><br></div><div><br></div><div><br></div><div><br></div><div><div style="font-size:75%;color:#575757">-- Alex<br><br>--<br>Sent from my Samsung mobile, and thus lacking in the refinement one might expect from a proper keyboard. <br><br>Alex Balashov - Principal<br>Evariste Systems LLC<br>235 E Ponce de Leon Ave<br>Suite 106<br>Decatur, GA 30030<br>Tel: +1-678-954-0670<br>Web: http://www.evaristesys.com/</div></div> <br>Peter Lemenkov <lemenkov@gmail.com> wrote:<br>2012/9/13 Alex Balashov <abalashov@evaristesys.com>:<br>> You can't get it from rtpproxy. You'd really have to use something like the<br>> dialog or htable modules to keep call state and get that from Kamailio.<br><br>On the contrary it's possible (using raw UDP reads/writes):<br><br>work ~: echo "h1u203u03 I\n" | nc -w 1 -u 127.0.0.1 22222<br> sessions created: 0<br>active sessions: 0<br>active streams: 0<br>work ~:<br><br>Where<br><br>* h1u203u03 is randomly chosen token,<br>* 127.0.0.1 is the rtpproxy's control IP,<br>* 22222 is the rtpproxy's control port,<br>* "-u" means that we're using UDP<br>* -w 1 is the timeout in seconds to wait before closing nc.<br><br>I can't imagine that someone will use nc in performance testing but I<br>think it looks like a good start.<br><br>-- <br>With best regards, Peter Lemenkov.<br></body>