<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
you should enable core dumping - that should be via running 'ulimit
-c unlimited' before you start rtpproxy.<br>
<br>
If you get the coredump, then grab the backtrace with gdb, it should
show where rtpproxy crashed. With that info, maybe we can spot a fix
for it.<br>
<br>
Hopefully rtpproxy package is with debug symbols, if not, the look
for a rtpproxy-dbg package and install it if found.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div class="moz-cite-prefix">On 20/12/13 18:59, Jr Richardson wrote:<br>
</div>
<blockquote
cite="mid:CA+U74VOaZ4twZMxsqTHHRPN3CqPdANiqX+Jcc=Rwx5ymH=G=mA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Hi All,</div>
<div> </div>
<div>root@sip-router3-ve206:/etc/kamailio# kamailio -V<br>
version: kamailio 4.1.0 (x86_64/linux) 350d2e</div>
<div> </div>
<div>Doing some testing, can't seem to get rtpproxy to not
segfault. I've loaded version from deb-squeeze pkg, from
source <a moz-do-not-send="true"
href="http://b2bua.org/chrome/site/rtpproxy-1.2.1.tar.gz">http://b2bua.org/chrome/site/rtpproxy-1.2.1.tar.gz</a>
and from <a class="moz-txt-link-freetext" href="git://">git://</a><a moz-do-not-send="true"
href="http://sippy.git.sourceforge.net/gitroot/sippy/rtpproxy">sippy.git.sourceforge.net/gitroot/sippy/rtpproxy</a>
(which should be the latest) but all versions segfault as soon
as a call sets up.</div>
<div> </div>
<div>I've configured each versions control socket for both udp
or unix, kamailio starts and sees the rtpproxy fine with no
errors, but when a call hits, rtpproxy segfaults.</div>
<div> </div>
<div>I've run rtpproxy in the forground with degug and get this
response (IP's washed x.x.x):</div>
<div>------------------</div>
<div>DBUG:handle_command: received command "7505_12 USIEc0,101
<a class="moz-txt-link-abbreviated" href="mailto:0adb2f8449b8c9026f993a0a7db9ab5d@x.x.x.76">0adb2f8449b8c9026f993a0a7db9ab5d@x.x.x.76</a> x.x.x.76 23388
as33dd7c98;1"<br>
INFO:handle_command: new session
<a class="moz-txt-link-abbreviated" href="mailto:0adb2f8449b8c9026f993a0a7db9ab5d@x.x.x.76">0adb2f8449b8c9026f993a0a7db9ab5d@x.x.x.76</a>, tag as33dd7c98;1
requested, type strong<br>
Segmentation fault</div>
<div>------------------</div>
<div> </div>
<div>root@sip-router3-ve206:/etc/kamailio# more
/etc/default/rtpproxy <br>
# Defaults for rtpproxy</div>
<div># The control socket.<br>
CONTROL_SOCK="unix:/var/run/rtpproxy/rtpproxy.sock"<br>
# To listen on an UDP socket, uncomment this line:<br>
#CONTROL_SOCK="udp:<a moz-do-not-send="true"
href="http://127.0.0.1:7722">127.0.0.1:7722</a>"</div>
<div># Additional options that are passed to the daemon.<br>
EXTRA_OPTS="-l x.x.x.20"</div>
<div> </div>
<div>kamailio.cfg:</div>
<div>loadmodule "rtpproxy.so"</div>
<div>modparam("rtpproxy", "rtpproxy_sock", "udp:<a
moz-do-not-send="true" href="http://127.0.0.1:7722">127.0.0.1:7722</a>")</div>
<div>
</div>
<div>inside route[]</div>
<div><br>
add_path_received();<br>
rtpproxy_manage("cwei");<br>
record_route();</div>
<div> </div>
<div>Any guidance on further identifying the issue?</div>
<div> </div>
<div>Thanks.</div>
<div> </div>
<div>JR<br>
-- <br>
JR Richardson<br>
Engineering for the Masses
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla - <a class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a>
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a></pre>
</body>
</html>