Hi Guys,

I have been suggested by the opensips developers to raise that issue to your
attention.

My SIP network topology is as follow:
1) origination IP
2) opensips proxy
3) opensips running in b2b mode
4) termination IP

I am running opensips trunk version currently with RTPproxy version 1.2.0. I
have been running the latest RTPproxy version before but switched back to
1.2.0 mostly because the logging wasn't working good with the latest
version. The issue I'm going to report have been noticed with both latest
version and 1.2.0.

So, on the opensips proxy (that is point 2 from the call flow), I am running
the following configuration:

###################################
*route[1] {
   ....
**     if (is_method("INVITE")) {
                xlog("[PROXY]($rm - $rr)----- INVITE FROM ROUTE[1] ..
sending to B2B \n");
                rewritehostport("<MY_IP>:5061");
                if (rtpproxy_offer("eo","**<MY_IP>**"))
                    t_on_reply("1");
        }
        else if (method == "BYE" || method == "CANCEL") {
                unforce_rtp_proxy();
        }*
   .....
*}
*
*onreply_route[1] {
        if (!(status=~"183" || status=~"200")) {
                drop;
        }

        rtpproxy_answer("FA");
}
*###################################


So, when restarting the opensips, I have that initial lines:
Feb 11 12:52:48 sms /root/opensips-1.6.4-tls/opensips[21754]:
INFO:nathelper:rtpp_test: rtp proxy <udp:*<MY_IP>*:22332> found, support for
it enabled
 Feb 11 12:52:48 sms /root/opensips-1.6.4-tls/opensips[21753]:
INFO:nathelper:rtpp_test: rtp proxy <udp:*<MY_IP>*:22332> found, support for
it enabled

So far so good.
Now, when I'm placing a call:
Feb 11 12:53:05 sms /root/opensips-1.6.4-tls/opensips[21746]:
DBG:nathelper:force_rtp_proxy: Forcing body:#012[v=0#015#012o=-
229796569696953 1 IN IP4 <TERMINATION_IP>#015#012s=-#015#012c=IN IP4
<TERMINATION_IP>
#015#012t=0 0#015#012m=audio 18338 RTP/AVP 0 101#015#012a=rtpmap:0
PCMU/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101 0-16]
Feb 11 12:53:05 sms /root/opensips-1.6.4-tls/opensips[21746]:
DBG:core:parse_to_param: tag=as612bc040
Feb 11 12:53:05 sms /root/opensips-1.6.4-tls/opensips[21746]:
DBG:core:parse_to: end of header reached, state=29
Feb 11 12:53:05 sms /root/opensips-1.6.4-tls/opensips[21746]:
DBG:core:parse_to: display={011359883327749}, ruri={sip:359883327749@
<ORIGINATION_IP>}
Feb 11 12:53:05 sms rtpproxy[21731]: DBUG:handle_command: received command
"21746_6 LA 4512c49c3cd0db1b410744fe0ced15bf@<ORIGINATION_IP>
<TERMINATION_IP> 18338 as612bc040;1 B2B.599.537;1"
*Feb 11 12:53:05 sms kernel: [7145167.526106] rtpproxy[21731]: segfault at 0
ip 00000000004053e9 sp 00007fff71948b00 error 4 in rtpproxy[400000+e000]*


I managed to avoid that rtpproxy crash by changing the following :
*     if (rtpproxy_offer("eo","**<MY_IP>**"))*
to:
*     if (rtpproxy_offer(**))


*The opensips guys suggested to bring that to your attention as the rtpproxy
should not crash that easy.
Please let me know if I can help with anything more.

Thank you.
-- Kamen*



*
_______________________________________________
Devel mailing list
[email protected]
http://lists.rtpproxy.org/mailman/listinfo/devel

Reply via email to