Does PJSIP implement the *new* STUN RFC 5389

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

 



2011/10/18 Benny Prijono <bennylp at teluu.com>:
> On Mon, Oct 17, 2011 at 11:39 PM, I?aki Baz Castillo <ibc at aliax.net> wrote:
>> Hi, since PJSIP implements RFC 5626 (Outbound) I assume it has
>> upgraded its STUN implementation from the old RFC 3489 to the new RFC
>> 5389, am I right?
>>
>
> We don't need STUN for outbound since we only implement TCP outbound,
> but yeah we use RFC 5389 heavily for ICE/TURN in pjnath.

Hi Benny, why don't you implement UDP Outbound? it has no mistery for
the client, it just does the same as in case of TCP (adding ;ob to
Contact URI for non-REGISTER and ;reg-id Contact header param for
REGISTER). And then instead of sending double CRLF for NAT keep-alive,
the SIP UDP client must send STUN Binding Requests (RFC 5389) to the
SIP UDP port of the proxy/server. That's all :)

PS: I've a SIP proxy implementing Outbound for SIP UDP/TCP/TLS
clients. Ask me if you want to test.


-- 
I?aki Baz Castillo
<ibc at aliax.net>



[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