Changes between Version 6 and Version 14 of Ticket #1032


Ignore:
Timestamp:
Mar 22, 2010 12:14:08 PM (15 years ago)
Author:
nanang
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1032

    • Property Status changed from new to closed
    • Property Resolution changed from to fixed
    • Property Summary changed from TLS certificate verification (thanks Rohit Agrawal, Klaus Darilion, and Pierre-Luc Bacon for the suggestions) to TLS certificate verification and callback to notify TCP/TLS transport state (thanks Rohit Agrawal, Klaus Darilion, and Pierre-Luc Bacon for the suggestions)

  • Ticket #1032 – Description

    v6 v14  
    1818 - Verification in SIP TLS transport: 
    1919   - Add destination host name into {{{pjsip_tx_data}}}. The TLS transport will use it to get the server name for TLS verification. 
    20    - Introduce a new SIP transport callback to notify transport states, i.e: connected, disconnected, TLS verification error, or combination of them, see below for more detail. 
     20   - Introduce a new SIP transport callback to notify transport states, i.e: connected, disconnected. 
    2121   - Add a verification step, i.e: domain name verification, then include its result to verification status of SSL socket info. 
    22    - If {{{verify_server/client}}} is set, TLS transport will disconnect the transport and notify the application via the new callback, with event type 'disconnected + TLS verification error', whenever there is any TLS verification error. 
    23    - If {{{verify_server/client}}} is not set, TLS transport will just notify the application via the new callback, with event type 'connected + TLS verification error', whenever there is any TLS verification error, the return value of the callback will be used to decide whether transport should be shutdown. In case there is no verification error, the application will be notified via the new callback with event type 'connected'. 
     22   - If {{{verify_server/client}}} is set and there is TLS verification error, TLS transport will disconnect the transport and notify the application via the new callback with event type 'disconnected', application can examine disconnection status code and TLS verification result via transport state info. 
     23   - If {{{verify_server/client}}} is not set and there is TLS verification error, TLS transport will notify the application via the new callback with event type 'connected', application can examine TLS verification result via transport state info.