[sr-dev] WebSocket (RFC 6455) and draft-ibc-sipcore-sip-websocket on Kamailio

[Daniel-Constantin Mierla]

Hello,

On 6/15/12 10:40 AM, Iñaki Baz Castillo wrote:
> 2012/6/15 Daniel-Constantin Mierla <miconda at gmail.com>:
>> I will be here to guide whenever needed to navigate through the transport
>> layers.
> Hi Daniel, thanks a lot. Some initial questions:
>
> - What about the TLS layer? WebSocket session is established via an
> HTTP GET request on top of TCP ot TCP-TLS. Web browsers usually don't
> present a certificate during TLS handshake so probably we don't want
> to obtain client certificate. But, is already possible to use the
> Kamailio HTTP stack on top of TLS?
yes, you can do http over tcp or tls in kamailio.

>
>
> - About the relationship between the TCP/WS connection and SIP message
> fields (to properly route incoming requests):
>
> I'm pretty sure the proper solution here is Outbound. I've implemented
> it in my proxy and works great (forget mangling the Contact URI or
> creating "alias" in Kamailio that could be overridn by other users and
> so...). Is there a chance to investigate adding Outbound to Kamailio?
> I've lot of experience with the spec and can help here.
Which RFC are you talking about? There was work done for 
registrar/usrloc in 3.3 to handle as per RFC5626 (as well as RFC5627 GRUU).

But overall, the selection of outgoing connection has an algorithm based 
on port/ip/proto, like it is for old tcp/tls. This time I assume the 
double record routing will have one with WS/WSS and the other will be 
UDP/TCP/TLS or, if needed, we can add another WS/WSS.

Cheers,
Daniel


-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-dev/attachments/20120615/f7e74be7/attachment.htm>