Hi all,
i try to register at the rtpproxy mailinglist, but its still pending. Maybe someone here had the same issue. In my multihomed setup (with mhomed=1 in kamailio.cfg) i had segfaults from rtpproxy if i called rtpproxy_manage with params.
Notice that i must run rtpproxy as root to get core files.
Any hints? Maybe my kamailio config isnt right?
ulimit -c unlimited ; /usr/local/bin/rtpproxy -u root -s /home/sys/bin/rtpproxy.sock -l <PUBLIC-IP> 172.20.100.74 -d DBUG:LOG_LOCAL5
Apr 10 15:13:40 kamailio1 rtpproxy[19728]: DBUG:handle_command: received command "V" Apr 10 15:13:40 kamailio1 rtpproxy[19728]: DBUG:doreply: sending reply "20040107#012" Apr 10 15:13:40 kamailio1 rtpproxy[19728]: DBUG:handle_command: received command "VF 20050322" Apr 10 15:13:40 kamailio1 rtpproxy[19728]: DBUG:doreply: sending reply "1#012" Apr 10 15:13:40 kamailio1 rtpproxy[19728]: DBUG:handle_command: received command "VF 20071116" Apr 10 15:13:40 kamailio1 rtpproxy[19728]: DBUG:doreply: sending reply "1#012" Apr 10 15:13:40 kamailio1 rtpproxy[19728]: DBUG:handle_command: received command "VF 20081102" Apr 10 15:13:40 kamailio1 rtpproxy[19728]: DBUG:doreply: sending reply "1#012" Apr 10 15:13:40 kamailio1 rtpproxy[19728]: DBUG:handle_command: received command "UEIc107,0,8,101 NTgxNzRkMmJmYzFlYjg2NTdiN2Q3MzJkYjkzMzI3Yjk. 217.XXX.XXX.XX 49814 00671612;1" Apr 10 15:13:40 kamailio1 rtpproxy[19728]: INFO:handle_command: new session NTgxNzRkMmJmYzFlYjg2NTdiN2Q3MzJkYjkzMzI3Yjk., tag 00671612;1 requested, type strong Apr 10 15:13:40 kamailio1 rtpproxy[19728]: INFO:handle_command: new session on a port 36156 created, tag 00671612;1 Apr 10 15:13:40 kamailio1 rtpproxy[19728]: INFO:handle_command: pre-filling caller's address with 217.XXX.XX.XX:49814 Apr 10 15:13:40 kamailio1 rtpproxy[19728]: DBUG:doreply: sending reply "36156 212.XX.XX.XXX#012" (gdb) bt #0 0x0804ccb8 in ishostseq (ia1=0x99c54c8, ia2=0x0) at rtpp_util.c:55 #1 0x080514ba in handle_command (cf=0xbffb9d8c, controlfd=5, dtime=1334063620.8220949) at rtpp_command.c:761 #2 0x0804afb7 in process_commands (argc=9, argv=0xbffda634) at main.c:752 #3 main (argc=9, argv=0xbffda634) at main.c:856 (gdb) p ia1->sa_family $1 = 2 (gdb) p ia2->sa_family Cannot access memory at address 0x0
# RTPProxy control route[NATMANAGE] { #!ifdef WITH_NAT xlog("NATMANAGE M=$rm RURI=$ru F=$fu T=$tu IP=$si ID=$ci\n"); if (is_request()) { if(has_totag()) { if(check_route_param("nat=yes")) { setbflag(FLB_NATB); } } }
if (isbflagset(FLB_NATB)) return;
if (dst_ip == PUBLIC_IP ) { xlog("rtpproxy_manage extern zu intern\n"); rtpproxy_manage("OCFEI","172.20.10.74");
} else { xlog("rtpproxy_manage intern zu extern\n"); rtpproxy_manage("OCFIE","PUBLIC_IP"); }
if (is_request()) { if (!has_totag()) { add_rr_param(";nat=yes"); } } if (is_reply()) { if(isbflagset(FLB_NATB)) { fix_nated_contact(); } } #!endif return; }
Hello,
is 3.2.2 from packages or tarball? If yes, can you try with latest git branch 3.2? Hints to install are here:
http://www.kamailio.org/wiki/install/3.2.x/git
Even rtpproxy should not crash in any case and a fix has to be done there, I just want to see if it is an effect of an issue fixed in rtpproxy module of kamailio.
Cheers, Daniel
On 4/10/12 3:37 PM, Karsten Horsmann wrote:
Hi all,
i try to register at the rtpproxy mailinglist, but its still pending. Maybe someone here had the same issue. In my multihomed setup (with mhomed=1 in kamailio.cfg) i had segfaults from rtpproxy if i called rtpproxy_manage with params.
Notice that i must run rtpproxy as root to get core files.
Any hints? Maybe my kamailio config isnt right?
ulimit -c unlimited ; /usr/local/bin/rtpproxy -u root -s /home/sys/bin/rtpproxy.sock -l<PUBLIC-IP> 172.20.100.74 -d DBUG:LOG_LOCAL5
Apr 10 15:13:40 kamailio1 rtpproxy[19728]: DBUG:handle_command: received command "V" Apr 10 15:13:40 kamailio1 rtpproxy[19728]: DBUG:doreply: sending reply "20040107#012" Apr 10 15:13:40 kamailio1 rtpproxy[19728]: DBUG:handle_command: received command "VF 20050322" Apr 10 15:13:40 kamailio1 rtpproxy[19728]: DBUG:doreply: sending reply "1#012" Apr 10 15:13:40 kamailio1 rtpproxy[19728]: DBUG:handle_command: received command "VF 20071116" Apr 10 15:13:40 kamailio1 rtpproxy[19728]: DBUG:doreply: sending reply "1#012" Apr 10 15:13:40 kamailio1 rtpproxy[19728]: DBUG:handle_command: received command "VF 20081102" Apr 10 15:13:40 kamailio1 rtpproxy[19728]: DBUG:doreply: sending reply "1#012" Apr 10 15:13:40 kamailio1 rtpproxy[19728]: DBUG:handle_command: received command "UEIc107,0,8,101 NTgxNzRkMmJmYzFlYjg2NTdiN2Q3MzJkYjkzMzI3Yjk. 217.XXX.XXX.XX 49814 00671612;1" Apr 10 15:13:40 kamailio1 rtpproxy[19728]: INFO:handle_command: new session NTgxNzRkMmJmYzFlYjg2NTdiN2Q3MzJkYjkzMzI3Yjk., tag 00671612;1 requested, type strong Apr 10 15:13:40 kamailio1 rtpproxy[19728]: INFO:handle_command: new session on a port 36156 created, tag 00671612;1 Apr 10 15:13:40 kamailio1 rtpproxy[19728]: INFO:handle_command: pre-filling caller's address with 217.XXX.XX.XX:49814 Apr 10 15:13:40 kamailio1 rtpproxy[19728]: DBUG:doreply: sending reply "36156 212.XX.XX.XXX#012" (gdb) bt #0 0x0804ccb8 in ishostseq (ia1=0x99c54c8, ia2=0x0) at rtpp_util.c:55 #1 0x080514ba in handle_command (cf=0xbffb9d8c, controlfd=5, dtime=1334063620.8220949) at rtpp_command.c:761 #2 0x0804afb7 in process_commands (argc=9, argv=0xbffda634) at main.c:752 #3 main (argc=9, argv=0xbffda634) at main.c:856 (gdb) p ia1->sa_family $1 = 2 (gdb) p ia2->sa_family Cannot access memory at address 0x0
# RTPProxy control route[NATMANAGE] { #!ifdef WITH_NAT xlog("NATMANAGE M=$rm RURI=$ru F=$fu T=$tu IP=$si ID=$ci\n"); if (is_request()) { if(has_totag()) { if(check_route_param("nat=yes")) { setbflag(FLB_NATB); } } }
if (isbflagset(FLB_NATB)) return; if (dst_ip == PUBLIC_IP ) { xlog("rtpproxy_manage extern zu intern\n"); rtpproxy_manage("OCFEI","172.20.10.74"); } else { xlog("rtpproxy_manage intern zu extern\n"); rtpproxy_manage("OCFIE","PUBLIC_IP"); } if (is_request()) { if (!has_totag()) { add_rr_param(";nat=yes"); } } if (is_reply()) { if(isbflagset(FLB_NATB)) { fix_nated_contact(); } }
#!endif return; }
Hello Daniel,
it´s kamailio 3.2.2 from tarball. I will try the git version today and report the result here.
Thanks.
Regards Karsten
2012/4/10 Daniel-Constantin Mierla miconda@gmail.com:
Hello,
is 3.2.2 from packages or tarball? If yes, can you try with latest git branch 3.2? Hints to install are here:
http://www.kamailio.org/wiki/install/3.2.x/git
Even rtpproxy should not crash in any case and a fix has to be done there, I just want to see if it is an effect of an issue fixed in rtpproxy module of kamailio.
Cheers, Daniel
Hi Daniel,
i compiled kamailio from git with this checkout params:
git clone --depth 1 git://git.sip-router.org/sip-router kamailio cd kamailio git checkout -b 3.2 origin/3.2
and its still the same issue. rtpproxy segfaults if i call rtpproxy_manage with params.
Whats next to do?
is 3.2.2 from packages or tarball? If yes, can you try with latest git branch 3.2? Hints to install are here:
http://www.kamailio.org/wiki/install/3.2.x/git
Even rtpproxy should not crash in any case and a fix has to be done there, I just want to see if it is an effect of an issue fixed in rtpproxy module of kamailio.
Hello,
On 4/11/12 9:21 AM, Karsten Horsmann wrote:
Hi Daniel,
i compiled kamailio from git with this checkout params:
git clone --depth 1 git://git.sip-router.org/sip-router kamailio cd kamailio git checkout -b 3.2 origin/3.2
and its still the same issue. rtpproxy segfaults if i call rtpproxy_manage with params.
thanks for testing it.
Whats next to do?
One should look over the code of rtpproxy, find the reason of crash and fix it.
I am using rtpproxy in bridge mode and haven't experienced any issue -- my way is pretty much like in this tutorial:
http://kb.asipto.com/kamailio:kamailio-mixed-ipv4-ipv6
There are different parameters given to rtpproxy_manage(), maybe you can play a bit with the parameter value and see if a particular flag there is the cause of the issue.
Cheers, Daniel
is 3.2.2 from packages or tarball? If yes, can you try with latest git branch 3.2? Hints to install are here:
http://www.kamailio.org/wiki/install/3.2.x/git
Even rtpproxy should not crash in any case and a fix has to be done there, I just want to see if it is an effect of an issue fixed in rtpproxy module of kamailio.
Hi Daniel,
i tried that way and two others. Its still the same issue.
Without params the rtpproxy is still there otherwise it segfaults .....
Cannot be the only person who use 3.2.2 and rtpproxy in bridging mode.... any working examples???
Your Tutorial is 3.2.0 btw....
One should look over the code of rtpproxy, find the reason of crash and fix it.
I am using rtpproxy in bridge mode and haven't experienced any issue -- my way is pretty much like in this tutorial:
http://kb.asipto.com/kamailio:kamailio-mixed-ipv4-ipv6
There are different parameters given to rtpproxy_manage(), maybe you can play a bit with the parameter value and see if a particular flag there is the cause of the issue.
Cheers, Daniel
Hi, I am using the 3.2.2 version with RTPproxy in bridging mode - the only time I was having segmentation fault (with any version) was when I started RTPproxy in bridging mode(in my mind) but it wasn't and I was missing a "/" in-between the PublicIP and the Private IP - Which, when I read your email, is missing in your command as well. Give it a try and see if your RTPproxy fails again !
Regards, Sammy.
On Wed, Apr 11, 2012 at 5:11 PM, Karsten Horsmann khorsmann@gmail.comwrote:
Hi Daniel,
i tried that way and two others. Its still the same issue.
Without params the rtpproxy is still there otherwise it segfaults .....
Cannot be the only person who use 3.2.2 and rtpproxy in bridging mode.... any working examples???
Your Tutorial is 3.2.0 btw....
One should look over the code of rtpproxy, find the reason of crash and
fix
it.
I am using rtpproxy in bridge mode and haven't experienced any issue --
my
way is pretty much like in this tutorial:
http://kb.asipto.com/kamailio:kamailio-mixed-ipv4-ipv6
There are different parameters given to rtpproxy_manage(), maybe you can play a bit with the parameter value and see if a particular flag there is the cause of the issue.
Cheers, Daniel
-- Mit freundlichen Grüßen *Karsten Horsmann*
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
Hi SamyGo,
thanks for the hint! It works with rtpproxy -l internal.ip/external.ip with the slash between it.
Strange - on older posts i read the opposite to get bridging working....
Thats wonderful :) , I read some older posts too but AFAIR there were these threads and someone else mentioned the correct way of running rtpproxy in bridging mode in the ends. So maybe you picked wrong post and followed.
Anyways have fun.
Regards, Sammy.
On Thu, Apr 12, 2012 at 2:17 PM, Karsten Horsmann khorsmann@gmail.comwrote:
Hi SamyGo,
thanks for the hint! It works with rtpproxy -l internal.ip/external.ip with the slash between it.
Strange - on older posts i read the opposite to get bridging working....
-- Mit freundlichen Grüßen *Karsten Horsmann*
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