Hi Bogdan,
The rtpproxy was configured to use both addresses.
The tricky part was the proper usage of force_rtp_proxy().
Here's my working setup:
- start rtpproxy: rtpproxy -l <internal_IP>/<external_IP>
forcing rtp from internal to external: force_rtp_proxy("ie")
forcing rtp from external to internal: force_rtp_proxy("ei")
If there are other SIP proxy server in between endpoint, the "r" flag
is crucial.
regards,
-ovi
On 6/8/06, Bogdan-Andrei Iancu <[EMAIL PROTECTED]> wrote:
Hi Ovidiu,
when starting the rtpproxy, have you configured both addresses?
regards,
bogdan
Ovidiu Sas wrote:
> Can anyone shed some light on how openser should poke rtpproxy in
> order to get the proper IP address when a bridged rtp session is
> established?
>
>
> thx,
> -ovi
>
> On 6/5/06, Ovidiu Sas <[EMAIL PROTECTED]> wrote:
>
>> Hi all,
>>
>>
>> I'm trying to get openser to act as an SBC using the mediaproxy
>> module and
>> the rtpproxy (built from the cvs).
>> openser is configured to run in a multihomed mode.
>> I'm starting rtpproxy in debug mode: rtpproxy -f -l
>> 10.110.1.174/10.111.5.15
>> The rtpproxy is binding to both IPs.
>>
>> When an INVITE is received on the 10.110 interface, I call
>> force_rtp_proxy().
>> Regrdless of the "i" or "e" parameter that I pass to the
>> force_rtp_proxy(),
>> the rtpproxy is replying with the same IP.
>>
>> output from rtpproxy if force_rtp_proxy("i"):
>>
>> received command "UI [EMAIL PROTECTED] 10.110.48.7 10046
>> 60e4ff4a-soma;1"
>> new session [EMAIL PROTECTED], tag 60e4ff4a-soma;1
>> requested,
>> type strong
>> new session on a port 35000 created, tag 60e4ff4a-soma;1
>> pre-filling caller's address with 10.110.48.7:10046
>> sending reply "35000 10.110.1.174
>> "
>>
>>
>> output from rtpproxy if force_rtp_proxy("e"):
>>
>> received command "UE [EMAIL PROTECTED] 10.110.48.7 10012
>> 1f713156-soma;1"
>> new session [EMAIL PROTECTED], tag 1f713156-soma;1
>> requested,
>> type strong
>> new session on a port 35002 created, tag 1f713156-soma;1
>> pre-filling caller's address with 10.110.48.7:10012
>> sending reply "35002 10.110.1.174
>> "
>>
>> The IP address sent out in the outgoing INVITE is 10.110.1.174
>> instead of
>> 10.111.5.15.
>>
>>
>> Is this the expected behaviour from the rtpproxy?
>> Do I need to pass other params to the force_rtp_proxy() function?
>>
>>
>> Regards,
>> -ovi
>>
>
> _______________________________________________
> Users mailing list
> Users@openser.org
> http://openser.org/cgi-bin/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users@openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
