16 Oct
2009
16 Oct
'09
3:27 a.m.
Klaus Darilion wrote:
Alex Balashov wrote:
That's what I thought too. It does not call any kernel IP forwarding
APIs.
But it seems to make a difference!
--
Alex Balashov - Principal
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Alex Balashov wrote:
That's strange, rtpproxy is in usermaode, thus the ip_forward setting
should not cause any influence. Daniel-Constantin Mierla wrote:
An additional note: if I turn OFF /proc/sys/net/ipv4/ip_forward and
then start the proxy in bridging mode, the following happens when it
is invoked:
DBUG:handle_command: received command "8725_4 UAIEc0,101
5f1690462d84b3814915b05f65c626bd(a)208.52.173.7 208.52.173.7 11832
as214288b6;1"
INFO:handle_command: new session
5f1690462d84b3814915b05f65c626bd(a)208.52.173.7, tag as214288b6;1
requested, type strong
Segmentation fault
In other words, it seems to require ip_forward to be on in order to
not crash, but when it is on, no packets are exchanged between the
interfaces. IIRC, I use:
if(dst_ip==private_ip)
force_rtp_proxy("ocfaei");
else
force_rtp_proxy("ocfaie");
rtpproxy started with: -l external_ip/private_ip
Probably is rtpproxy 1.1 -- cannot check right now.
I just tried this and it works, from the point of view of SDP. We
were already able to obtain this result.
The problem is that the actual rtpproxy does not seem to forward the
packets that come into one interface toward the other, so no media is
exchanged.