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.
-- Alex -- Sent from my Samsung mobile, and thus lacking in the refinement one might expect from a proper keyboard. Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 Tel: +1-678-954-0670 Web: http://www.evaristesys.com/Peter Lemenkov <lemen...@gmail.com> wrote:2012/9/13 Alex Balashov <abalas...@evaristesys.com>: > You can't get it from rtpproxy. You'd really have to use something like the > dialog or htable modules to keep call state and get that from Kamailio. On the contrary it's possible (using raw UDP reads/writes): work ~: echo "h1u203u03 I\n" | nc -w 1 -u 127.0.0.1 22222 sessions created: 0 active sessions: 0 active streams: 0 work ~: Where * h1u203u03 is randomly chosen token, * 127.0.0.1 is the rtpproxy's control IP, * 22222 is the rtpproxy's control port, * "-u" means that we're using UDP * -w 1 is the timeout in seconds to wait before closing nc. I can't imagine that someone will use nc in performance testing but I think it looks like a good start. -- With best regards, Peter Lemenkov.
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
