TCP/TLS transport

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

 




jay bing schrieb:
> thanks for your replay.
> another quick quiastion:
> about TCP/TLS msg parsing: does the pjsip_transport is responsible for 
> identifing the msg boundries (like u describde) or some upper layer?
> about TLS: does the transport layer responsible for setting the contact 
> header and via or some upper layer?

Sorry, I don't know.
>  
> thanks again,
> jay
> 
> 
>    
> 
> 
> 2009/8/10 Klaus Darilion <klaus.mailinglists at pernau.at 
> <mailto:klaus.mailinglists at pernau.at>>
> 
> 
> 
>     jay bing schrieb:
> 
>         hi
>          does someone familier with any simple paper/presentation about
>         SIP over streaming transport like TCP/TLS
>         please don't refer me to the RFC
>         ...
>          in general, regarding TCP my quastion is how does the transport
>         "know" about the end of each msg, i.e. how streaming is used to
>         send/recieve msg?
>          is there any marker for beginning/end of msg?
> 
> 
>     You just read fromt the socket until double CRLF is received (that's
>     the end of the headers). Then check the value of the content-length
>     header and read that many bytes from the socket.
> 
> 
>         about TLS, is there anything diffrent then regular TCP inside
>         the msg beside the Socket handeling which is done by the basic
>         layer (i.e. openssl of SecureSocket is the symbian case?)
> 
> 
>     not really, except that the contact header and via will have TLS
>     instead of TCP and the application should do some certificate
>     validation (e.g. if the domain in the certificate is the same as the
>     domain in the request URI).
> 
>     regards
>     klaus
> 
>          thanks
>          
> 
>         ------------------------------------------------------------------------
> 
>         _______________________________________________
>         Visit our blog: http://blog.pjsip.org <http://blog.pjsip.org/>
> 
>         pjsip mailing list
>         pjsip at lists.pjsip.org <mailto:pjsip at lists.pjsip.org>
>         http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
> 
> 
>     _______________________________________________
>     Visit our blog: http://blog.pjsip.org <http://blog.pjsip.org/>
> 
>     pjsip mailing list
>     pjsip at lists.pjsip.org <mailto:pjsip at lists.pjsip.org>
>     http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> 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