[ previous ] [ next ] [ threads ]
 To :  Yate mailing list <yate@v...>
 From :  Tusar <tusarbd@g...>
 Subject :  Re: [yate] YATE [SIP --> H323] NAT problem
 Date :  Tue, 20 Oct 2009 17:38:56 +0700
Hi,

Does this means .. If I disable "rtp_forward" then only from Private IP will
be RTP proxied and from Public IP, RTP will be directed directly ?

Or is there any parameter for selective range of IP will be PROXIED and
other will not. Like ..
RTP_Proxy = 192.168.0.0/16,172.16.0.0/16 .
So [192.168.0.0/16,172.16.0.0/16] will be forcefully PROXIED.

My intention is to keep free resources from RTP for YATE. So that YATE can
handle more number of calls.

Thankyou very much .

Best Regards,
//Tusar\


On Tue, Oct 20, 2009 at 5:01 PM, Diana Cionoiu  wrote:

> Hello Tusar,
>
> If you want Yate to act like an SBC and get you out in the Internet you
> shouldn't use rtp_forward.
> When you use rtp_forward you depend on the other end to handle the NAT
> problems.
>
> Diana
>
>
> Tusar wrote:
>
>> Hi,
>>
>> I am trying to implement YATE's automatic NAT for SIP --> H323 but somehow
>> it is failing .
>> From Public IP both way voice is OK but from Private IP we can NOT hear
>> anything .
>>
>>
>> ysipchan.conf
>> =============
>> [general]
>> registrar=enable
>> options=enable
>> prack=enable
>> info=enable
>> fork=disable
>> progress=enable
>> *nat=enable*
>> forward_sdp=enable
>> refresh_nosdp=enable
>>
>> [codecs]
>> default=off
>> g723=yes
>> g729=yes
>>
>>
>> h323chan.conf
>> =============
>> [general]
>> external_rtp=yes
>> fallback_rtp=yes
>> forward_rtp=yes
>>
>> [codecs]
>> default=no
>> g723=on
>> g729=on
>>
>> [ep]
>> faststart=on
>> h245tunneling=true
>> h245insetup=false
>>
>>
>> regexroute.conf
>> ===============
>> [default]
>> ${rtp_forward}possible=;rtp_forward=yes
>> ${formats}^\([^,]*\)=;formats=
>> .*=h323/@6...:1720; xsip_auth_bye=false
>>
>> If I disable [;;; ${rtp_forward}possible=;rtp_forward=yes]  then I can
>> hear both party but at this time Public IP is also getting proxied .
>>
>>
>> Can anyone give some hints to solve this problem ?
>>
>> Best Regards,
>> //Tusar\
>>
>>
>



Hi,

Does this means .. If I disable "rtp_forward" then only from Private IP will be RTP proxied and from Public IP, RTP will be directed directly ?

Or is there any parameter for selective range of IP will be PROXIED and other will not. Like ..
RTP_Proxy = 192.168.0.0/16,172.16.0.0/16 .
So [192.168.0.0/16,172.16.0.0/16] will be forcefully PROXIED.

My intention is to keep free resources from RTP for YATE. So that YATE can handle more number of calls.

Thankyou very much .

Best Regards,
//Tusar\


On Tue, Oct 20, 2009 at 5:01 PM, Diana Cionoiu <diana-liste@n...> wrote:
Hello Tusar,

If you want Yate to act like an SBC and get you out in the Internet you shouldn't use rtp_forward.
When you use rtp_forward you depend on the other end to handle the NAT problems.

Diana


Tusar wrote:
Hi,

I am trying to implement YATE's automatic NAT for SIP --> H323 but somehow it is failing .
From Public IP both way voice is OK but from Private IP we can NOT hear anything .


ysipchan.conf
=============
[general]
registrar=enable
options=enable
prack=enable
info=enable
fork=disable
progress=enable
*nat=enable*
forward_sdp=enable
refresh_nosdp=enable

[codecs]
default=off
g723=yes
g729=yes


h323chan.conf
=============
[general]
external_rtp=yes
fallback_rtp=yes
forward_rtp=yes

[codecs]
default=no
g723=on
g729=on

[ep]
faststart=on
h245tunneling=true
h245insetup=false


regexroute.conf
===============
[default]
${rtp_forward}possible=;rtp_forward=yes
${formats}^\([^,]*\)=;formats=
.*=h323/@6...:1720; xsip_auth_bye=false

If I disable [;;; ${rtp_forward}possible=;rtp_forward=yes]  then I can hear both party but at this time Public IP is also getting proxied .


Can anyone give some hints to solve this problem ?

Best Regards,
//Tusar\