IN Scenario Pack 2.0.0 :: IN Scenario Pack Guide

The IN Scenario Pack adds support for the following IN protocols to the OpenCloud Scenario Simulator:

ETSI-INAP-CS1
CAP-v1
CAP-v2
CAP-v3
CAP-v4
MAP

This document describes how to install and run the examples included with the Scenario Pack.

Installation

The minimum required Scenario Simulator version for this release of the IN Scenario Pack is 2.3.1.2.

If the Scenario Simulator installation contains an existing version of the IN Scenario Pack this must be removed before installing this version.

$ rm protocols/in-scenario-pack-x.y.z.jar
$ rm -rf in-examples/

Similarly, if any optional extension IN Scenario Packs have been installed, these must also be removed:

$ rm protocols/optional-extension-scenario-pack-x.y.z.jar
$ rm -rf optional-extension-examples/

It is not necessary to remove other Scenario Packs, for example HTTP, SIP or Diameter.

Extract the new IN Scenario Pack in the <scenario-simulator> root directory:

$ unzip in-scenario-pack.zip

Finally, any optional extension IN Scenario Packs (with the same version) may be extracted in the same manner:

$ unzip optional-extension-scenario-pack.zip

Examples

The IN scenario pack is bundled with example configuration and scenario files.

The examples may be found in the <scenario_simulator>/in-examples directory.

There are examples using two endpoints (in the 2sims directory) and three endpoints (in the 3sims directory).

Configuration

Example configuration files are included in the <*sims>/config/ directory.

The config/loopback/ directory contains an example loopback configuration for connecting three simulator instances, all using the tcap simulator
The config/signalware/ directory contains an example configuration for connecting to three signalware backends.

Running the examples

To start up simulator instances for scenarios that use 2 endpoints, run these commands in separate terminals:

  $ ./scenario-simulator.sh -f in-examples/2sims/config/loopback/setup-sim1.commands -l endpoint1.log -f in-examples/2sims/config/setup-examples-sim1.commands -e 'wait-until-operational'
  $ ./scenario-simulator.sh -f in-examples/2sims/config/loopback/setup-sim2.commands -l endpoint2.log -f in-examples/2sims/config/setup-examples-sim2.commands -e 'wait-until-operational'

To start up simulator instances for scenarios that use 3 endpoints, run these commands in separate terminals:

  $ ./scenario-simulator.sh -f in-examples/3sims/config/loopback/setup-sim1.commands -l endpoint1.log -f in-examples/3sims/config/setup-examples-sim1.commands -e 'wait-until-operational'
  $ ./scenario-simulator.sh -f in-examples/3sims/config/loopback/setup-sim2.commands -l endpoint2.log -f in-examples/3sims/config/setup-examples-sim2.commands -e 'wait-until-operational'
  $ ./scenario-simulator.sh -f in-examples/3sims/config/loopback/setup-sim3.commands -l endpoint3.log -f in-examples/3sims/config/setup-examples-sim3.commands -e 'wait-until-operational'

IN Examples with 2 endpoints

Example 1. CAPv3-Demo-ContinueRequest.scen

This Scenario is for use with the CGIN demo service. It sends an InitialDP with a callingPartyNumber ending in 1, and expects the service to reply with a Continue.

Requires SSP-Loadgen and SCP-Rhino endpoints
Load scenario on both endpoints: load-scenario in-examples/2sims/scenarios/CAPv3-Demo-ContinueRequest.scen
Run session from "SSP-Loadgen" endpoint: run-session CAPv3-Demo-ContinueRequest

Example 2. CAPv3-Demo-ReleaseCallRequest.scen

This Scenario is for use with the CGIN demo service. It sends an InitialDP with a callingPartyNumber ending in 0, and expects the service to reply with a ReleaseCall.

Requires SSP-Loadgen and SCP-Rhino endpoints
Load scenario on both endpoints: load-scenario in-examples/2sims/scenarios/CAPv3-Demo-ReleaseCallRequest.scen
Run session from "SSP-Loadgen" endpoint: run-session CAPv3-Demo-ReleaseCallRequest

Example 3. INAP-SSP-SCP.scen

A scenario for testing a VPN service under load using INAP.

Requires SSP-Loadgen and SCP-Rhino endpoints
Load scenario on both endpoints: load-scenario in-examples/2sims/scenarios/INAP-SSP-SCP.scen
Run session from "SSP-Loadgen" endpoint: run-session INAP-SSP-SCP

Example 4. CAPv2-Relay.scen

A MSC-SCP relay scenario. Between the MSC and SCP is a relay service (not represented in this scenario) that removes a "987" prefix if present in the CalledPartyNumber of the IDP.

Requires MSC and SCP endpoints
Load scenario on both endpoints: load-scenario in-examples/2sims/scenarios/CAPv2-Relay.scen
Run session from "MSC" endpoint: run-session CAPv2-Relay

IN Examples with 3 endpoints

Example 5. INAP-SSP-SCP-HLR.scen

A scenario for testing a VPN service under load using INAP. This example sends AnyTimeInterrogation requests to an HLR as part of the callflow.

Requires SSP-Loadgen, SCP-Rhino and HLR endpoints
Load scenario on all endpoints: load-scenario in-examples/3sims/scenarios/INAP-SSP-SCP-HLR.scen
Run session from "SSP-Loadgen" endpoint: run-session INAP-SSP-SCP-HLR

Example 6. MAP-MT-SMS-DeliveryAbsentSubscriber.scen

This scenario provides an example call flow between an SMSC, HLR, and MSC. It is intended to demonstrate the spontaneous creation of an SMS from the SMSC (either as the result of a queued message or otherwise).

Requires HLR, SMSC and MSC endpoints
Load scenario on all endpoints: load-scenario in-examples/3sims/scenarios/MAP-MT-SMS-DeliveryAbsentSubscriber.scen
Run session from "SMSC" endpoint: run-session MAP-MT-SMS-DeliveryAbsentSubscriber

Example 7. MAP-MT-SMS-DeliveryPresentSubscriber.scen

Requires HLR, SMSC and MSC endpoints
Load scenario on all endpoints: load-scenario in-examples/3sims/scenarios/MAP-MT-SMS-DeliveryPresentSubscriber.scen
Run session from "SMSC" endpoint: run-session MAP-MT-SMS-DeliveryPresentSubscriber