*********************************************************************************
*                                                                               *
* 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.         *    
*********************************************************************************

                      Advanced 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.
 
 Use a user made verification callback and inspect the certificate.
 Override the stack decision on post connection assertions.
 note that in this sample we use a deliberately mis-issued certificate 
  
 
    
 
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 secure url (sips:)
and binding with a secure url (sips:), and the server will accept the registration.
The ua client then should connect a call to the previous Address-of-record as was registered.
When establishing tls connection from the ua to the server, the server decision is not to establish the 
connection, but the application override this decision using the post connection assertion callback.
Afterwards the proxy forward the request in a secured connection to the ua server.


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: wrongHost.key-cert.pem 
(all located under RvPackage\SipServerTk\SampleCode\AdvancedTlsServer)

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).




