[ previous ] [ next ] [ threads ]
 To :  Torsten Schlabach <tschlabach@g...>
 From :  Diana Cionoiu <diana-liste@v...>
 Subject :  Re: [yate] STUN
 Date :  Wed, 16 Aug 2006 17:10:00 +0300
Hello Torsten,

Actually STUN is not the only way to pass NAT. Most of the SIP severs 
actually has no problem with Yate behind NAT. Especially if are another 
Yate servers. You can find more about that issue and how is handled in 
Yate at:
Actually STUN can be a pain in a lot of cases, so we decided for a while 
to not implement it.

Diana Cionoiu

P.S. Yes, we will provide guidance for anyone that will write STUN, 
because it can be disabled after all if is in the way.

Torsten Schlabach wrote:

> Hi,
> > I'm sorry but YateClient dosen't support STUN right now.
> What a pitty. This renders it next to useless for 90% of the people I 
> know. Do you have any plans to support STUN? Do you think it would be 
> a lot of work doing so? I might be interested in helping out if 
> someone would provide some guidance to the source.
> Regards,
> Torsten
> Diana Cionoiu schrieb:
>> Hello Torsten,
>> I'm sorry but YateClient dosen't support STUN right now.
>> Regards,
>> Diana
>> Torsten Schlabach wrote:
>>> Hi!
>>> Sorry if that has been asked before, but I haven't seen anything in 
>>> the archives.
>>> I tried to use the Yate Client to connect to a 3rd party SIP 
>>> account. But this obviously fails because I cannot configure the 
>>> STUN server needed.
>>> Does the Yate client support STUN at all, maybe through a config file?
>>> Regards,
>>> Torsten