Also, this is how I am running the rtpproxy:<br>23414 ? Ss 0:00 /usr/local/bin/rtpproxy -s udp:184.106.168.144 22332 -u root root -p /var/run/rtpproxy/rtpproxy.pid -F -l 184.106.168.144<br><br>And here is the nathelper config for both opensips and b2b:<br>
modparam("nathelper", "rtpproxy_sock", "udp:<a href="http://184.106.168.144:22332">184.106.168.144:22332</a>")<br>modparam("nathelper", "force_socket", "udp:<a href="http://184.106.168.144:22332">184.106.168.144:22332</a>")<br>
modparam("nathelper", "rtpproxy_retr", 2)<br>modparam("nathelper", "received_avp", "$avp(i:42)")<br>modparam("nathelper", "ping_nated_only", 1)<br>modparam("nathelper", "rtpproxy_autobridge", 1)<br>
modparam("nathelper", "sipping_bflag", 8)<br>modparam("nathelper", "sipping_from", "<a href="mailto:sip%3Apinger@platform.worldtalkinc.com">sip:pinger@platform.worldtalkinc.com</a>")<br>
modparam("nathelper", "sipping_method", "INFO")<br><br clear="all"><br><br>Does anything of that seems suspicious to you ?<br><br><br><br><br><div class="gmail_quote">On 11 February 2011 16:42, Kamen Petrov <span dir="ltr"><<a href="mailto:kamen.petrov@gmail.com">kamen.petrov@gmail.com</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;">Anca:<div class="im"><br><i>> There was a problem with the db schema for the b2b_logic table -
lots of wrong NOT NULL constraints there. I have just fixed it.
Please take the new schema from svn and replace the table.</i><br></div>
-- Seems to be fine now, thank you.<div class="im"><br><br><i>> Are you using the newest version of rtpproxy?</i><br></div>-- I am running 1.2.0 right now. I have been running 1.2.1 before but with the same success. I moved back to 1.2.0 mainly because the debug does not work with 1.2.1 and I can't see what happens in the background.<br>
<br>Ovidiu:<div class="im"><br><i>> Then please remove the old core file and make sure that you have the latest source on both servers.</i><br></div>-- I removed the old core file, tested a new call and got into the same issue (as described before: segfault on the rtpproxy). A new core haven't been generated. Both servers uses the same opensips setup with different config files (loaded with: "<b>-f <file></b>")<br>
<br><br>On theory, I should have rtpproxy_offer on the "route" and rtpproxy_answer on the "onreply_route" right ? Since that is the case when I have segfault on the rtpproxy.<br>If I remove the rtpproxy_answer form the onreply_route, there is no segfault, but there is no audio as well.<br>
<br>Please advise.<br>Your help guys is highly appreciated !<br clear="all">--------------------------------------------<br><font color="#888888">Kamen Petrov</font><div><div></div><div class="h5"><br>
<br><br><div class="gmail_quote">On 11 February 2011 16:30, Ovidiu Sas <span dir="ltr"><<a href="mailto:osas@voipembedded.com" target="_blank">osas@voipembedded.com</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;">
Then please remove the old core file and make sure that you have the<br>
latest source on both servers.<br>
<div><div></div><div><br>
On Fri, Feb 11, 2011 at 9:27 AM, Kamen Petrov <<a href="mailto:kamen.petrov@gmail.com" target="_blank">kamen.petrov@gmail.com</a>> wrote:<br>
> The last core i have is:<br>
> -rw------- 1 root root 43188224 Feb 10 11:49 /core<br>
><br>
> I did the attached tests 1 or 2 hours ago and the system time now is "Fri<br>
> Feb 11 14:29:14 UTC 2011".<br>
><br>
> I guess there is no new core :(<br>
><br>
><br>
> On 11 February 2011 16:23, Ovidiu Sas <<a href="mailto:osas@voipembedded.com" target="_blank">osas@voipembedded.com</a>> wrote:<br>
>><br>
>> Please get a gdb trace from the core file.<br>
>><br>
>> Thanks,<br>
>> Ovidiu<br>
>><br>
>> On Fri, Feb 11, 2011 at 8:31 AM, Kamen Petrov <<a href="mailto:kamen.petrov@gmail.com" target="_blank">kamen.petrov@gmail.com</a>><br>
>> wrote:<br>
>> >> Ok guys,<br>
>> >><br>
>> >> Few issues still (after updating from trunk).<br>
>> >><br>
>> >> As suggested, I removed the engage_rtp_proxy from the b2b opensips<br>
>> >> instance.<br>
>> >><br>
>> >> I noticed the following debug from the opensips:<br>
>> >> Feb 11 12:49:06 sms /root/opensips-1.6.4-tls/opensips[21621]:<br>
>> >> ERROR:db_postgres:db_postgres_store_result: 0x7b9360 - invalid query,<br>
>> >> execution aborted<br>
>> >> Feb 11 12:49:06 sms /root/opensips-1.6.4-tls/opensips[21621]:<br>
>> >> ERROR:db_postgres:db_postgres_store_result: 0x7b9360: PGRES_FATAL_ERROR<br>
>> >> Feb 11 12:49:06 sms /root/opensips-1.6.4-tls/opensips[21621]:<br>
>> >> ERROR:db_postgres:db_postgres_store_result: 0x7b9360: ERROR: null<br>
>> >> value in<br>
>> >> column "e3_sid" violates not-null constraint#012<br>
>> >><br>
>> >> Looking on the postgres log, here is the failed SQL statement:<br>
>> >> 2011-02-11 12:49:06 UTC ERROR: null value in column "e3_sid" violates<br>
>> >> not-null constraint<br>
>> >> 2011-02-11 12:49:06 UTC STATEMENT: insert into b2b_logic<br>
>> >><br>
>> >> (si_key,scenario,sparam0,sparam1,sparam2,sparam3,sparam4,sdp,sstate,next_sstate,e1_type,e1_sid,e1_to,e1_from,e1_key,e2_type,e2_sid,e2_to,e2_from,e2_key<br>
>> >> ) values<br>
>> >><br>
>> >> ('545.0','','','','','','','',-3,0,0,'','<a href="http://sip:17864776626@190.124.220.12:5060" target="_blank">sip:17864776626@190.124.220.12:5060</a>','<a href="mailto:sip%3A359883327749@69.25.128.234" target="_blank">sip:359883327749@69.25.128.234</a>','B2B.608.661',1,'','<a href="http://sip:17864776626@190.124.220.12:5060" target="_blank">sip:17864776626@190.124.220.12:5060</a>','<a href="mailto:sip%3A359883327749@69.25.128.234" target="_blank">sip:359883327749@69.25.128.234</a>','B2B.545.4207959')<br>
>> >><br>
>> >> I am using the default b2b postgres tables.<br>
>> >><br>
>> >> So next, I have the following config on the rtpproxy opensips (not the<br>
>> >> b2b<br>
>> >> one):<br>
>> >> #####################################################<br>
>> >> route[1] {<br>
>> >> fix_nated_contact();<br>
>> >><br>
>> >> if (is_method("INVITE")) {<br>
>> >> rewritehostport("<a href="http://184.106.168.144:5061" target="_blank">184.106.168.144:5061</a>");<br>
>> >> if (rtpproxy_offer("eo","184.106.168.144"))<br>
>> >> t_on_reply("1");<br>
>> >> }<br>
>> >> else if (method == "BYE" || method == "CANCEL") {<br>
>> >> unforce_rtp_proxy();<br>
>> >> }<br>
>> >> ..<br>
>> >> }<br>
>> >><br>
>> >> onreply_route[1] {<br>
>> >> if (!(status=~"183" || status=~"200")) {<br>
>> >> drop;<br>
>> >> }<br>
>> >><br>
>> >> rtpproxy_answer("FA");<br>
>> >><br>
>> >> }<br>
>> >> #####################################################<br>
>> >><br>
>> >> As result, when I initiate a call, I get the following on the syslog:<br>
>> >><br>
>> >> Feb 11 12:52:48 sms /root/opensips-1.6.4-tls/opensips[21754]:<br>
>> >> INFO:nathelper:rtpp_test: rtp proxy <udp:<a href="http://184.106.168.144:22332" target="_blank">184.106.168.144:22332</a>> found,<br>
>> >> support for it enabled<br>
>> >> Feb 11 12:52:48 sms /root/opensips-1.6.4-tls/opensips[21753]:<br>
>> >> INFO:nathelper:rtpp_test: rtp proxy <udp:<a href="http://184.106.168.144:22332" target="_blank">184.106.168.144:22332</a>> found,<br>
>> >> support for it enabled<br>
>> >> ....<br>
>> >> Feb 11 12:53:05 sms /root/opensips-1.6.4-tls/opensips[21746]:<br>
>> >> DBG:nathelper:force_rtp_proxy: Forcing body:#012[v=0#015#012o=-<br>
>> >> 229796569696953 1 IN IP4 190.124.220.12#015#012s=-#015#012c=IN IP4<br>
>> >> 190.124.220.12<br>
>> >> #015#012t=0 0#015#012m=audio 18338 RTP/AVP 0 101#015#012a=rtpmap:0<br>
>> >> PCMU/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101<br>
>> >> 0-16]<br>
>> >> Feb 11 12:53:05 sms /root/opensips-1.6.4-tls/opensips[21746]:<br>
>> >> DBG:core:parse_to: display={011359883327749},<br>
>> >> ruri={<a href="mailto:sip%3A359883327749@69.25.128.233" target="_blank">sip:359883327749@69.25.128.233</a>}<br>
>> >> Feb 11 12:53:05 sms rtpproxy[21731]: DBUG:handle_command: received<br>
>> >> command<br>
>> >> "21746_6 LA <a href="mailto:4512c49c3cd0db1b410744fe0ced15bf@69.25.128.233" target="_blank">4512c49c3cd0db1b410744fe0ced15bf@69.25.128.233</a><br>
>> >> 190.124.220.12<br>
>> >> 18338 as612bc040;1 B2B.599.537;1"<br>
>> >> Feb 11 12:53:05 sms kernel: [7145167.526106] rtpproxy[21731]: segfault<br>
>> >> at<br>
>> >> 0 ip 00000000004053e9 sp 00007fff71948b00 error 4 in<br>
>> >> rtpproxy[400000+e000]<br>
>> >> ....<br>
>> >> ....<br>
>> >> Feb 11 12:53:05 sms /root/opensips-1.6.4-tls/opensips[21748]:<br>
>> >> DBG:tm:t_reply_matching: hash 23820 label 1987919557 branch 0<br>
>> >> Feb 11 12:53:05 sms /root/opensips-1.6.4-tls/opensips[21748]:<br>
>> >> DBG:tm:t_reply_matching: REF_UNSAFE:[0x7fc0f89b4f10] after is 2<br>
>> >> Feb 11 12:53:05 sms /root/opensips-1.6.4-tls/opensips[21748]:<br>
>> >> DBG:tm:t_reply_matching: reply matched (T=0x7fc0f89b4f10)!<br>
>> >> Feb 11 12:53:05 sms /root/opensips-1.6.4-tls/opensips[21748]:<br>
>> >> DBG:tm:t_check: end=0x7fc0f89b4f10<br>
>> >> Feb 11 12:53:05 sms /root/opensips-1.6.4-tls/opensips[21748]:<br>
>> >> DBG:tm:reply_received: org. status uas=100, uac[0]=0 local=0<br>
>> >> is_invite=1)<br>
>> >> Feb 11 12:53:06 sms /root/opensips-1.6.4-tls/opensips[21746]:<br>
>> >> ERROR:nathelper:send_rtpp_command: timeout waiting reply from a RTP<br>
>> >> proxy<br>
>> >> Feb 11 12:53:06 sms /root/opensips-1.6.4-tls/opensips[21746]:<br>
>> >> ERROR:nathelper:send_rtpp_command: proxy <udp:<a href="http://184.106.168.144:22332" target="_blank">184.106.168.144:22332</a>><br>
>> >> does<br>
>> >> not respond, disable it<br>
>> >> Feb 11 12:53:06 sms /root/opensips-1.6.4-tls/opensips[21746]:<br>
>> >> ERROR:nathelper:send_rtpp_command: can't send command to a RTP proxy<br>
>> >> Connection refused<br>
>> >> ........................ repeating over 100<br>
>> >> times................................<br>
>> >><br>
>> >> Obviously the RTPproxy dies.<br>
>> >> What I noticed is, when i remove<br>
>> >> rtpproxy_answer("FA");<br>
>> >> from the onreply_route, the RTPproxy does not dies.<br>
>> >><br>
>> >> Any ideas what I am doing wrong ?<br>
>> >><br>
>> >> Thank you.<br>
>> >> -- Kamen<br>
>> ><br>
>> > _______________________________________________<br>
>> > Users mailing list<br>
>> > <a href="mailto:Users@lists.opensips.org" target="_blank">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>
>> ><br>
>><br>
>> _______________________________________________<br>
>> Users mailing list<br>
>> <a href="mailto:Users@lists.opensips.org" target="_blank">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>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org" target="_blank">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>
><br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">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>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>