<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
<div class="moz-cite-prefix">On 6/15/12 10:40 AM, Iñaki Baz Castillo
wrote:<br>
</div>
<blockquote
cite="mid:CALiegfmCoO13R1K1hXiK5f+NmWkppxsPQNOF86JJjXy2us-CeA@mail.gmail.com"
type="cite">
<pre wrap="">2012/6/15 Daniel-Constantin Mierla <a class="moz-txt-link-rfc2396E" href="mailto:miconda@gmail.com"><miconda@gmail.com></a>:
</pre>
<blockquote type="cite">
<pre wrap="">I will be here to guide whenever needed to navigate through the transport
layers.
</pre>
</blockquote>
<pre wrap="">
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?</pre>
</blockquote>
yes, you can do http over tcp or tls in kamailio.<br>
<br>
<blockquote
cite="mid:CALiegfmCoO13R1K1hXiK5f+NmWkppxsPQNOF86JJjXy2us-CeA@mail.gmail.com"
type="cite">
<pre wrap="">
- 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.</pre>
</blockquote>
Which RFC are you talking about? There was work done for
registrar/usrloc in 3.3 to handle as per
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
RFC5626 (as well as
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
RFC5627 GRUU).<br>
<br>
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.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<blockquote
cite="mid:CALiegfmCoO13R1K1hXiK5f+NmWkppxsPQNOF86JJjXy2us-CeA@mail.gmail.com"
type="cite">
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla - <a class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a>
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a>
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - <a class="moz-txt-link-freetext" href="http://asipto.com/u/katu">http://asipto.com/u/katu</a>
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - <a class="moz-txt-link-freetext" href="http://asipto.com/u/kpw">http://asipto.com/u/kpw</a></pre>
</body>
</html>