Hi Anca,<br><br>Ok, I managed it work your way.<br><br>The key was not in the rtpproxy_answer but the rtpproxy_offer :)<br><br>Once again thanks to you and Ovidiu for your great help !<br><br>
So just for the record if someone else face the same issue: segfault in the rtpproxy on the onreply_route: don't look only the rtpproxy_answer but also play with the rtpproxy_offer<br><br><br><br><br><br><div class="gmail_quote">
On 11 February 2011 18:30, Anca Vamanu <span dir="ltr"><<a href="mailto:anca@opensips.org">anca@opensips.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"><div class="im">
On 02/11/2011 03:31 PM, Kamen Petrov wrote:
</div><div class="im"><blockquote type="cite"><i>onreply_route[1] {<br>
if (!(status=~"183" || status=~"200")) {<br>
drop;<br>
}<br>
<br>
rtpproxy_answer("FA");<br>
</i></blockquote>
</div><p>Maybe you could try to use other flags, or renounce at one at a
time to see which one results in segmentation fault. You should
also report this to the rtpproxy list. <br>
</p>
<br>
<pre cols="72">--
Anca Vamanu
OpenSIPS Developer</pre>
</div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br>