From sobomax at sippysoft.com  Mon Feb  2 22:05:55 2009
From: sobomax at sippysoft.com (Maxim Sobolev)
Date: Mon, 02 Feb 2009 22:05:55 -0800
Subject: [RTPproxy Users] Kamilio integration with rtpproxy
In-Reply-To: <492FBD74.9060201@sippysoft.com>
References: <b245e6760811200939gce214d3qc4253f2de9de3abc@mail.gmail.com>	<4925BA7F.1050209@sippysoft.com>	<b245e6760811210131iebc316br31a17068039810e9@mail.gmail.com>	<49272369.5020003@sippysoft.com>	<b245e6760811240122w4dc8f3fv5cd7662b5430fc5b@mail.gmail.com>	<492A80C2.7080105@pernau.at>	<b245e6760811250355lbe96364tcf88de22fdb6ffc@mail.gmail.com>	<492BEA9D.4020104@sippysoft.com>
	<b245e6760811250547u2b3f319ek3da7ac7588b786e1@mail.gmail.com>
	<492FBD74.9060201@sippysoft.com>
Message-ID: <4987DEC3.4010608@sippysoft.com>

Joan,

I am not sure if the problem is still relevant or not, but it appears to 
be caused by the bug in GCC 4.3.2 compiler in the default -O2 
optimization mode. I have just bumped into this issue on one of 
customer's system myself. The problem can be worked around either by 
compiling the RTPproxy with -O0 instead or by upgrading the compiler 
suite. Particularly, on Ubuntu upgrading from "gcc version 4.3.2 (Ubuntu 
4.3.2-1ubuntu11)" to "gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu12)" has 
solved the issue for me.

Regards,
-- 
Maksym Sobolyev
Sippy Software, Inc.
Internet Telephony (VoIP) Experts
T/F: +1-646-651-1110
Web: http://www.sippysoft.com
MSN: sales at sippysoft.com
Skype: SippySoft

From aseques at gmail.com  Tue Feb  3 03:16:29 2009
From: aseques at gmail.com (Joan)
Date: Tue, 3 Feb 2009 12:16:29 +0100
Subject: [RTPproxy Users] Kamilio integration with rtpproxy
In-Reply-To: <4987DEC3.4010608@sippysoft.com>
References: <b245e6760811200939gce214d3qc4253f2de9de3abc@mail.gmail.com>
	<b245e6760811210131iebc316br31a17068039810e9@mail.gmail.com>
	<49272369.5020003@sippysoft.com>
	<b245e6760811240122w4dc8f3fv5cd7662b5430fc5b@mail.gmail.com>
	<492A80C2.7080105@pernau.at>
	<b245e6760811250355lbe96364tcf88de22fdb6ffc@mail.gmail.com>
	<492BEA9D.4020104@sippysoft.com>
	<b245e6760811250547u2b3f319ek3da7ac7588b786e1@mail.gmail.com>
	<492FBD74.9060201@sippysoft.com> <4987DEC3.4010608@sippysoft.com>
Message-ID: <b245e6760902030316k248277cfuaeb35bc9d05feea4@mail.gmail.com>

2009/2/3 Maxim Sobolev <sobomax at sippysoft.com>:
> Joan,
>
> I am not sure if the problem is still relevant or not, but it appears to
> be caused by the bug in GCC 4.3.2 compiler in the default -O2
> optimization mode. I have just bumped into this issue on one of
> customer's system myself. The problem can be worked around either by
> compiling the RTPproxy with -O0 instead or by upgrading the compiler
> suite. Particularly, on Ubuntu upgrading from "gcc version 4.3.2 (Ubuntu
> 4.3.2-1ubuntu11)" to "gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu12)" has
> solved the issue for me.
>
So bad, at the end I ended up using mediaproxy instead, since that
worked almost out of the box altought the performance is probably not
the same.
I might give a shot again in the future to rtpproxy tought.
In this conflict between kamailio / opensips, mediaproxy is clearly
going with opensips (even sharing the mailing lists), and It seems to
me that opensips (at the moment) is succeeding more on the community
gathering stuff, and evolving rather fast (there are some interesting
new modules)
Might I ask if you're going to keep contributing to opensips too? I've
seen a couple of patches from you a couple of months ago, but haven't
tested them. And I would be interested on a long term basis (who
doesn't :P)

From sobomax at sippysoft.com  Tue Feb  3 03:23:08 2009
From: sobomax at sippysoft.com (Maxim Sobolev)
Date: Tue, 03 Feb 2009 03:23:08 -0800
Subject: [RTPproxy Users] Kamilio integration with rtpproxy
In-Reply-To: <b245e6760902030316k248277cfuaeb35bc9d05feea4@mail.gmail.com>
References: <b245e6760811200939gce214d3qc4253f2de9de3abc@mail.gmail.com>	<b245e6760811210131iebc316br31a17068039810e9@mail.gmail.com>	<49272369.5020003@sippysoft.com>	<b245e6760811240122w4dc8f3fv5cd7662b5430fc5b@mail.gmail.com>	<492A80C2.7080105@pernau.at>	<b245e6760811250355lbe96364tcf88de22fdb6ffc@mail.gmail.com>	<492BEA9D.4020104@sippysoft.com>	<b245e6760811250547u2b3f319ek3da7ac7588b786e1@mail.gmail.com>	<492FBD74.9060201@sippysoft.com>
	<4987DEC3.4010608@sippysoft.com>
	<b245e6760902030316k248277cfuaeb35bc9d05feea4@mail.gmail.com>
Message-ID: <4988291C.70106@sippysoft.com>

Joan wrote:
> Might I ask if you're going to keep contributing to opensips too? I've
> seen a couple of patches from you a couple of months ago, but haven't
> tested them. And I would be interested on a long term basis (who
> doesn't :P)

Yes, absolutely. Right now, nathelper in both OpenSIPS and SER support 
the same set of RTPproxy features and we are likely to support both in 
the foreseeable future.

Regards,
-- 
Maksym Sobolyev
Sippy Software, Inc.
Internet Telephony (VoIP) Experts
T/F: +1-646-651-1110
Web: http://www.sippysoft.com
MSN: sales at sippysoft.com
Skype: SippySoft

From khansfriend at gmail.com  Tue Feb 10 20:59:47 2009
From: khansfriend at gmail.com (Khan)
Date: Tue, 10 Feb 2009 22:59:47 -0600
Subject: [RTPproxy Users] RTPproxy is not running
Message-ID: <d0992c780902102059u1b21aff5j7a30eb378173eb8e@mail.gmail.com>

Hello everyone,

I am new to VoIP technology, I had a successful opensips running before
installing rtpproxy and making changes in opensips.cfg file.

###
modparam("nathelper", "natping_interval", 60)
modparam("nathelper", "ping_nated_only", 1)
modparam("nathelper", "rtpproxy_sock", "udp:127.0.0.1:8899")
modparam("nathelper", "force_socket", "udp:localhost:8899")

modparam("nathelper", "rtpproxy_disable_tout", 60)
modparam("nathelper", "rtpproxy_tout", 1)
modparam("nathelper", "rtpproxy_retr", 5)
modparam("nathelper", "sipping_method", "OPTIONS")
modparam("nathelper", "received_avp", "$avp(i:801)")
###

I ran rtpproxy manually as follows:

root# rtpproxy -f -l 192.168.1.2  -s udp:localhost:8899 &

I tried to see if rtpproxy is  running using following command

# ps -ef |grep rtp
root     11570  5786  0 22:35 pts/0    00:00:00 rtpproxy -s udp:127.0.0.1
8899 -f -l 192.168.1.2
root     11583  5786  0 22:40 pts/0    00:00:00 grep rtp

this is what i see,  Im not sure if its running or not i see rtpproxy.pid in
/var/run directory but no rtpproxy.sock file.

but when i make call, i get error of 407 proxy authentication faiure and get
the following dump:

# NAT-Reply - S=183 D=Session Progress
F=sip:16336380000 at voipbiznet.com<sip%3A16336380000 at voipbiznet.com>T=
sip:16336380005 at voipbiznet.com
<sip%3A16336380005 at voipbiznet.com>IP=192.168.1.101
ID=4346894F676048F0918F8B9D9C398F470xc0a80164

root at voipbiznet:/home/amjad# NAT-Reply - S=183 D=Session Progress F=
sip:16336380000 at voipbiznet.com <sip%3A16336380000 at voipbiznet.com> T=
sip:16336380005 at voipbiznet.com
<sip%3A16336380005 at voipbiznet.com>IP=192.168.1.101
ID=4346894F676048F0918F8B9D9C398F470xc0a80164
New request - M=REGISTER RURI=sip:192.168.1.2
F=sip:16336380005 at 192.168.1.2<sip%3A16336380005 at 192.168.1.2>T=
sip:16336380005 at 192.168.1.2 <sip%3A16336380005 at 192.168.1.2> IP=192.168.1.101
ID=7594792B0BEB4755AEC8DF5B0AE9F5DF0xc0a80165
Register authentication failed - M=REGISTER RURI=sip:192.168.1.2 F=
sip:16336380005 at 192.168.1.2 <sip%3A16336380005 at 192.168.1.2> T=
sip:16336380005 at 192.168.1.2 <sip%3A16336380005 at 192.168.1.2> IP=192.168.1.101
ID=7594792B0BEB4755AEC8DF5B0AE9F5DF0xc0a80165
New request - M=REGISTER RURI=sip:192.168.1.2
F=sip:16336380005 at 192.168.1.2<sip%3A16336380005 at 192.168.1.2>T=
sip:16336380005 at 192.168.1.2 <sip%3A16336380005 at 192.168.1.2> IP=192.168.1.101
ID=7594792B0BEB4755AEC8DF5B0AE9F5DF0xc0a80165
Registration successful - M=REGISTER RURI=sip:192.168.1.2 F=
sip:16336380005 at 192.168.1.2 <sip%3A16336380005 at 192.168.1.2> T=
sip:16336380005 at 192.168.1.2 <sip%3A16336380005 at 192.168.1.2> IP=192.168.1.101
ID=7594792B0BEB4755AEC8DF5B0AE9F5DF0xc0a80165
NAT-Reply - S=183 D=Session Progress
F=sip:16336380000 at voipbiznet.com<sip%3A16336380000 at voipbiznet.com>T=
sip:16336380005 at voipbiznet.com
<sip%3A16336380005 at voipbiznet.com>IP=192.168.1.101
ID=4346894F676048F0918F8B9D9C398F470xc0a80164

root at voipbiznet:/home/amjad# NAT-Reply - S=200 D=OK F=
sip:16336380000 at voipbiznet.com <sip%3A16336380000 at voipbiznet.com> T=
sip:16336380005 at voipbiznet.com
<sip%3A16336380005 at voipbiznet.com>IP=192.168.1.101
ID=4346894F676048F0918F8B9D9C398F470xc0a80164
Feb 10 22:43:51 [6837] ERROR:nathelper:force_rtp_proxy2_f: incorrect port 0
in reply from rtp proxy
NAT-Reply - S=200 D=OK
F=sip:16336380000 at voipbiznet.com<sip%3A16336380000 at voipbiznet.com>T=
sip:16336380005 at voipbiznet.com
<sip%3A16336380005 at voipbiznet.com>IP=192.168.1.101
ID=4346894F676048F0918F8B9D9C398F470xc0a80164
Feb 10 22:43:51 [6840] ERROR:nathelper:force_rtp_proxy2_f: incorrect port 0
in reply from rtp proxy
NAT-Reply - S=200 D=OK
F=sip:16336380000 at voipbiznet.com<sip%3A16336380000 at voipbiznet.com>T=
sip:16336380005 at voipbiznet.com
<sip%3A16336380005 at voipbiznet.com>IP=192.168.1.101
ID=4346894F676048F0918F8B9D9C398F470xc0a80164
Feb 10 22:43:52 [6842] ERROR:nathelper:force_rtp_proxy2_f: incorrect port 0
in reply from rtp proxy
NAT-Reply - S=200 D=OK
F=sip:16336380000 at voipbiznet.com<sip%3A16336380000 at voipbiznet.com>T=
sip:16336380005 at voipbiznet.com
<sip%3A16336380005 at voipbiznet.com>IP=192.168.1.101
ID=4346894F676048F0918F8B9D9C398F470xc0a80164
Feb 10 22:43:54 [6844] ERROR:nathelper:force_rtp_proxy2_f: incorrect port 0
in reply from rtp proxy


I need to know what am I doing wrong here? Please help!!!


Khan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rtpproxy.org/pipermail/users/attachments/20090210/0e00e1c7/attachment.html 

From sobomax at sippysoft.com  Wed Feb 25 00:41:05 2009
From: sobomax at sippysoft.com (Maxim Sobolev)
Date: Wed, 25 Feb 2009 00:41:05 -0800
Subject: [RTPproxy Users] RTPproxy is not running
In-Reply-To: <d0992c780902102059u1b21aff5j7a30eb378173eb8e@mail.gmail.com>
References: <d0992c780902102059u1b21aff5j7a30eb378173eb8e@mail.gmail.com>
Message-ID: <49A50421.2060809@sippysoft.com>

Khan,

Most likely there is some logical mistake in your routing script. The 
'0' reply from RTPproxy means that there is no such session in there. 
Possible cause of this is not invoking force_rtp_proxy on INVITE, I can 
only see 200 OK and 183 Session Progress in your log.

Khan wrote:
> Hello everyone,
> 
> I am new to VoIP technology, iI had a successful opensips running before 
> installing rtpproxy and making changes in opensips.cfg file.
> 
> ###
> modparam("nathelper", "natping_interval", 60)
> modparam("nathelper", "ping_nated_only", 1)
> modparam("nathelper", "rtpproxy_sock", "udp:127.0.0.1:8899 
> <http://127.0.0.1:8899>")
> modparam("nathelper", "force_socket", "udp:localhost:8899")
> 
> modparam("nathelper", "rtpproxy_disable_tout", 60)
> modparam("nathelper", "rtpproxy_tout", 1)
> modparam("nathelper", "rtpproxy_retr", 5)
> modparam("nathelper", "sipping_method", "OPTIONS")
> modparam("nathelper", "received_avp", "$avp(i:801)")
> ###
> 
> I ran rtpproxy manually as follows:
> 
> root# rtpproxy -f -l 192.168.1.2  -s udp:localhost:8899 &
> 
> I tried to see if rtpproxy is  running using following command
> 
> # ps -ef |grep rtp
> root     11570  5786  0 22:35 pts/0    00:00:00 rtpproxy -s 
> udp:127.0.0.1 8899 -f -l 192.168.1.2
> root     11583  5786  0 22:40 pts/0    00:00:00 grep rtp
> 
> this is what i see,  Im not sure if its running or not i see 
> rtpproxy.pid in /var/run directory but no rtpproxy.sock file.
> 
> but when i make call, i get error of 407 proxy authentication faiure and 
> get the following dump:
> 
> # NAT-Reply - S=183 D=Session Progress F=sip:16336380000 at voipbiznet.com 
> <mailto:sip%3A16336380000 at voipbiznet.com> 
> T=sip:16336380005 at voipbiznet.com 
> <mailto:sip%3A16336380005 at voipbiznet.com> IP=192.168.1.101 
> ID=4346894F676048F0918F8B9D9C398F470xc0a80164
> 
> root at voipbiznet:/home/amjad# NAT-Reply - S=183 D=Session Progress 
> F=sip:16336380000 at voipbiznet.com 
> <mailto:sip%3A16336380000 at voipbiznet.com> 
> T=sip:16336380005 at voipbiznet.com 
> <mailto:sip%3A16336380005 at voipbiznet.com> IP=192.168.1.101 
> ID=4346894F676048F0918F8B9D9C398F470xc0a80164
> New request - M=REGISTER RURI=sip:192.168.1.2 
> F=sip:16336380005 at 192.168.1.2 <mailto:sip%3A16336380005 at 192.168.1.2> 
> T=sip:16336380005 at 192.168.1.2 <mailto:sip%3A16336380005 at 192.168.1.2> 
> IP=192.168.1.101 ID=7594792B0BEB4755AEC8DF5B0AE9F5DF0xc0a80165
> Register authentication failed - M=REGISTER RURI=sip:192.168.1.2 
> F=sip:16336380005 at 192.168.1.2 <mailto:sip%3A16336380005 at 192.168.1.2> 
> T=sip:16336380005 at 192.168.1.2 <mailto:sip%3A16336380005 at 192.168.1.2> 
> IP=192.168.1.101 ID=7594792B0BEB4755AEC8DF5B0AE9F5DF0xc0a80165
> New request - M=REGISTER RURI=sip:192.168.1.2 
> F=sip:16336380005 at 192.168.1.2 <mailto:sip%3A16336380005 at 192.168.1.2> 
> T=sip:16336380005 at 192.168.1.2 <mailto:sip%3A16336380005 at 192.168.1.2> 
> IP=192.168.1.101 ID=7594792B0BEB4755AEC8DF5B0AE9F5DF0xc0a80165
> Registration successful - M=REGISTER RURI=sip:192.168.1.2 
> F=sip:16336380005 at 192.168.1.2 <mailto:sip%3A16336380005 at 192.168.1.2> 
> T=sip:16336380005 at 192.168.1.2 <mailto:sip%3A16336380005 at 192.168.1.2> 
> IP=192.168.1.101 ID=7594792B0BEB4755AEC8DF5B0AE9F5DF0xc0a80165
> NAT-Reply - S=183 D=Session Progress F=sip:16336380000 at voipbiznet.com 
> <mailto:sip%3A16336380000 at voipbiznet.com> 
> T=sip:16336380005 at voipbiznet.com 
> <mailto:sip%3A16336380005 at voipbiznet.com> IP=192.168.1.101 
> ID=4346894F676048F0918F8B9D9C398F470xc0a80164
> 
> root at voipbiznet:/home/amjad# NAT-Reply - S=200 D=OK 
> F=sip:16336380000 at voipbiznet.com 
> <mailto:sip%3A16336380000 at voipbiznet.com> 
> T=sip:16336380005 at voipbiznet.com 
> <mailto:sip%3A16336380005 at voipbiznet.com> IP=192.168.1.101 
> ID=4346894F676048F0918F8B9D9C398F470xc0a80164
> Feb 10 22:43:51 [6837] ERROR:nathelper:force_rtp_proxy2_f: incorrect 
> port 0 in reply from rtp proxy
> NAT-Reply - S=200 D=OK F=sip:16336380000 at voipbiznet.com 
> <mailto:sip%3A16336380000 at voipbiznet.com> 
> T=sip:16336380005 at voipbiznet.com 
> <mailto:sip%3A16336380005 at voipbiznet.com> IP=192.168.1.101 
> ID=4346894F676048F0918F8B9D9C398F470xc0a80164
> Feb 10 22:43:51 [6840] ERROR:nathelper:force_rtp_proxy2_f: incorrect 
> port 0 in reply from rtp proxy
> NAT-Reply - S=200 D=OK F=sip:16336380000 at voipbiznet.com 
> <mailto:sip%3A16336380000 at voipbiznet.com> 
> T=sip:16336380005 at voipbiznet.com 
> <mailto:sip%3A16336380005 at voipbiznet.com> IP=192.168.1.101 
> ID=4346894F676048F0918F8B9D9C398F470xc0a80164
> Feb 10 22:43:52 [6842] ERROR:nathelper:force_rtp_proxy2_f: incorrect 
> port 0 in reply from rtp proxy
> NAT-Reply - S=200 D=OK F=sip:16336380000 at voipbiznet.com 
> <mailto:sip%3A16336380000 at voipbiznet.com> 
> T=sip:16336380005 at voipbiznet.com 
> <mailto:sip%3A16336380005 at voipbiznet.com> IP=192.168.1.101 
> ID=4346894F676048F0918F8B9D9C398F470xc0a80164
> Feb 10 22:43:54 [6844] ERROR:nathelper:force_rtp_proxy2_f: incorrect 
> port 0 in reply from rtp proxy
> 
> 
> I need to know what am I doing wrong here? Please help!!!

Regards,
-- 
Maksym Sobolyev
Sippy Software, Inc.
Internet Telephony (VoIP) Experts
T/F: +1-646-651-1110
Web: http://www.sippysoft.com
MSN: sales at sippysoft.com
Skype: SippySoft