PROJECT PURPOSE:
----------------

This project contains the Session Initiation Protocal (SIP) test suite, standardized by the ETSI. 

The goal of this project is to generate C++ code and build an executable from the TTCN-3 test suite.

The executable can be used to test a real SIP implementation.

As a result of the execution, a debug file is generated with all necessary information to easily see 
what happened during execution.

PROJECT CONTENTS:
-----------------

The project contains the following files:
  - Eight TTCN-3 files
    Downloaded from the TTCN-3 website, which are the standardized test suite.
    
  - params.ttcnpar																								
    Some parameters (called module parameters) can be configured before the execution
    of the test suite. In this file, all these parameters are present. Some of them have
    been predefined in the TTCN-3 code, some others are not and a default value has been set.
    In every case, the user can change the value of these parameters to adapt the test to its target.
    It is important to understand that these values are not used during the generation of the C++ code
    or during the build of the executable, but during the execution of the test suite.
  
  - ExternalFunctions.c
    This file contains the definition of several external functions required by the test suite.
    The contents of these functions can be edited if required, however their signature should not be changed.
    
  - RTDS_TTCN_SUT_interface.c and RTDS_TTCN_SUT_interface.h				
    This two files define the interface between the test suite and the system to test.
  
  - License
    Licenses of external libraries required to build the interface.

																																
INSTRUCTIONS:
-------------

To generate an executable from this test suite, select SIP_MainModule.ttcn in the project and click on the build button. 
In the new opened window, select a code generation profile for your platform. 
There are two profiles per platform, the difference is the verbosity of the debug file.
For example, for linux 32 bit, the profile linux32 will generate an executable with an extented verbosity:
	- testcase started time,
	- function and altstep calls,
	- message reception and timer time out
	- precise information in case of matching error,
The profile linux32_simple will generate an executable with very basic information in the debug file (testcase name and verdict result).

After this, an executable for your platform is generated and can be used to test a real SIP implementation.
	
