[Serusers] nathelper fix_nated_* question
Maxim Sobolev
sobomax at portaone.com
Thu Apr 22 22:25:03 CEST 2004
Yes, and you should be indicating session direction when calling
force_rtp_proxy() using its arguments ('ie', 'ei', 'ee', 'ii').
-Maxim
Andy Pyles wrote:
> Hi Maxim,
>
> so just to be clear, bridge mode needs to be enabled on the command line
> for rtpproxy correct?
>
> Is -l the option for bridge mode?
>
> i.e.: `rtpproxy -l 192.168.0.1/1.2.3.4'
>
> Andy
> On Thu, 22 Apr 2004, Maxim Sobolev wrote:
>
>
>>Looks like what you really want is rtpproxy/nathelper in bridge mode.
>>Please check sample configuration files available in the trunk as well
>>as comments at the beginning of nathelper.c.
>>
>>-Maxim
>>
>>Andy Pyles wrote:
>>
>>>In the overly simplified version below, assuming I have 2 ip's:
>>>
>>>192.168.0.1 , and 1.2.3.4 How do I specify which IP will be replaced?
>>>
>>>In this particular case I want it to always replace with 1.2.3.4 on
>>>packets
>>>going out, and 192.168.0.1 on the way in. From my example it's always
>>>replacing it with the internal ip.
>>>
>>>For example the following would be nice:
>>>EIP=1.2.3.4
>>>IIP=192.168.0.1
>>>
>>>fix_nated_contact(EIP);
>>>fix_nated_sdp(EIP);
>>>etc.
>>>
>>>
>>>if (method == "INVITE") {
>>>
>>> fix_nated_contact();
>>> fix_nated_sdp("3")
>>> if (force_rtp_proxy("FAEE"))
>>> t_on_reply("1");
>>>
>>>}
>>>
>>>onreply_route[1] {
>>> if (!(status=~"183" || status=~"200"))
>>> break;
>>> fix_nated_contact();
>>> fix_nated_sdp("3");
>>> force_rtp_proxy("FA");
>>>}
>>>
>>>_______________________________________________
>>>Serusers mailing list
>>>serusers at lists.iptel.org
>>>http://lists.iptel.org/mailman/listinfo/serusers
>>>
>>>
>>>
>>
>>
>
>
>
More information about the sr-users
mailing list