6 Jun
2007
6 Jun
'07
3:35 p.m.
On 06/06/2007 07:29 PM, Klaus Darilion wrote:
Alexander Bergolth wrote:
Yes, I did already read it but I still didn't get the clue yet. :(
In my configuration, there is no internal and external net, both IP
addresses are in the same subnet using public IP addresses.
What I'd like to achieve:
The openser/rtpproxy server has some IP addresses and receives and sends
SIP traffic on all of those interfaces.
rtpproxy should simply use that local IP address for its RTP connection
to the client from which the SIP traffic from the client came in.
I've tried to use force_rtp_proxy("", "$Ri") but that leads to
the
SDP-line "c=$Ri". Maybe the nathelper-module doesn't support
pseudo-variables?
Cheers,
--leo
--
e-mail ::: Alexander.Bergolth (at) wu-wien.ac.at
fax ::: +43-1-31336-906050
location ::: Computer Center | Vienna University of Economics | Austria
I'm experiencing problems using openser and
rtpproxy on a multihomed box
(IP addresses are 137.208.89.45 and 137.208.89.65).
The client (firewalled) contacts the server via the first IP address
(137.208.89.45) but rtpproxy sometimes uses it's second IP
(137.208.89.65) in the "c=" SDP-information. (See below.)
However it _sends_ RTP packets from the _first_ IP address. Those
packets will never pass through the firewall, of course, since the
clients outgoing RTP traffic is sent to another IP address than the
incoming traffic is hitting the firewall from.
Is there a way to tell rtpproxy to use the same IP-address both for the
c= SDP header and as source address?
I guess you need the bridge mode of rtp proxy. Take a look at the "flags":
http://openser.org/docs/modules/devel/nathelper#AEN296