STUN changes in pjsip 1.4

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Aug 25, 2009 at 4:52 PM, Klaus
Darilion<klaus.mailinglists at pernau.at> wrote:
>
>
> Benny Prijono schrieb:
>>
>> Ah, yes, good point! It was http://trac.pjsip.org/repos/ticket/866
>>
>> Basically, in pre-1.4, STUN used to be one single point of failure
>> thing, if your STUN server is down the library will refuse to be
>> started. With that ticket, we added support for multiple STUN servers,
>> and the library checks for STUN server usability before picking one
>> up. The checking uses STUN facility in PJNATH, which is mostly new
>> STUN, though I thought it should be backward compatible with old STUN
>> (at least it worked with Vovida STUN in
>> http://www.sf.net/projects/stun)
>
> Are you sure? I use latest version too.
>

I works in several locations that I tested (including from open
Internet). I use 0.96_Aug13 version.

>>
>> You can use stun.pjsip.org.
>
> Same problem.
>

In that case I'm not convinced the problem is in the code. Maybe some
NAT filtering?

Cheers
 Benny

> klaus
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>



[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux