*********************************************************************************
*                                                                               *
* NOTICE:                                                                       *
* This document contains information that is confidential and proprietary to    *
* RADVision LTD.. No part of this publication may be reproduced in any form     *
* whatsoever without written prior approval by RADVision LTD..                  *
*                                                                               * 
* RADVision LTD. reserves the right to revise this publication and make changes *
* without obligation to notify any person of such revisions or changes.         *    
*********************************************************************************

                      Simple Tls Server Readme File
                      ---------------------------------
General
-------
 This sample code gives a complete example of how to:
 
 Initiate the RADVISION SIP Server.
 Register application callbacks.
 Implement application callback.
 Accept incoming register request.
 Proxy an incoming request according to previous registration.
 
 Initiates TLS engines, which are responsible for TLS connection management.
 Initiates a TLS handshake on connected connection.
 Use the "sips:" scheme to conduct secure SIP session.
 
   
 Set the appropriate Record-Route header (or headers) in the outgoing request forwarded 
 down stream from the proxy, using simmetryc Record-Route mechanism, to support 
 the case when a request is received in a non-secure transport but sent in a secured 
 connection, or vice versa.
    
   
 
Usage
-----
This application is using local loop address: 127.0.0.1 as listening addresses
and server domain adress.
All the certificates relate to this address, so if you change it you will need to supply
new corresponding certificates as well.

In this example the Server is waiting for ua to start working.
The ua should send a registration, with Address-of-record with non-secure url and 
binding with a secure url, the binding should be of an address in the local host (x@127.0.0.1:yyyy), 
since the certificate of the uas is for this ip address. 
The server will accept the registration.
The ua then should connect a call to the previous Address-of-record as was registered and 
proxy the request, and the server will send the outgoing request in a secure connection to the uas. 


For working with this sample code:
The Root CA the uac client engine should trust: SipServerCaCert (use SipServerCaCert.pem file).
The Certificate the uas server engine should use: localhost.key-cert.pem  
(both located under RvPackage\SipServerTk\SampleCode\SimpleTlsServer)
Both user agents should be located on the same host as the proxy (the certificates are only for local host,
i.e, 127.0.0.1).