Simulators for the backend processes used for SS7 connectivity, to permit testing of IN services without using an SS7 network
How do I get it ...
Please register/login to download from DevPortal
( Log in | Sign up )
The backend simulators are useful for connecting an IN service to an IN simulator for testing purposes, without the need for an SS7 network. They simulate the backend processes used to provide a bridge between the IN resource adaptors and the SS7 network.
The real backend processes are documented in the Signalware Integration Guide.
In a typical usage scenario, a single instance of the backend simulator would be started, then both a Rhino cluster and an IN simulator would connect to it, allowing the simulator and the Rhino cluster to communicate, e.g.:
[IN Scriptable Simulator] <-> [CAP backend process] <-> [Rhino with INAP RA and INAP service]
The use of a simulator is transparent to the resource adaptor or simulator. The RA connects to the backend on the configured TCP port (in the same way as it connects to a real backend process), and sends and receives messages in exactly the same way as if it were connected to an SS7 network.
There are four backend simulators available, for CAP, INAP, MAP, and IS41.
Starting the simulators
The jar files for each simulator are located in the in/incc/lib/ directory of the IN connectivity pack, with the following names:
The backend simulator can be started as follows:
java -jar <jarfile> -c <configuration-file>
For example to start the CAP simulator:
java -jar in/incc/lib/cap-backend-simulator.jar -c sample-configuration-file.xml
A sample configuration file can be obtained by running the jar as above but with the -g option.
Command line arguments
The command line args can be obtained by invoking the -h option, or with no arguments.
Filename of XML configuration file.
This specifies the SCCP address type to use. The default is C7.
This is an integer value in the range 0-32767.
It is used as part of dialog identifiers, so if an RA connects to multiple
backend simulators, each simulator must be given a unique application-id.
If unspecified, a value derived from the current time is used, changing
every 1/10th of a second and unique every 54m 36.8s.
Limit the maximum number of dialogs that can be allocated at any one time.
By default the maximum is effectively unlimited.
-h Print this help message (all other arguments are ignored).
-g Output a sample XML configuration file (all other arguments are ignored).