Application Context

optional

The application context is a concept in the IN telephony protocols which identifies the type of protocol being used by one party when communicating with another party.

When the first message is sent from the SSF to the SCF, an application context is included to tell the SCF the type of call that is occurring.

In most situations this does not need to be specified for the IN Tester tool. The IN Tester will default to a "CAMEL CAP3" application context.

If this application context is not appropriate, another can be selected.

Options

• CAMEL CAP3 Usually used in mobile networks. The binary value for this is 0x04 00 00 01 15 03 04
• ETSI INAP Usually used in landline networks. The binary value for this is 0x04 00 01 01 01 00 00

---

Acting SSF Type

custom

The IN Tester acts as an SSF in many test scenarios. Some SSF vendors include customisations to INAP and CAMEL messages in their SSF solutions that are utilised by the SCF.

To correctly test the SCF, the IN Tester must act correctly in cases where these customisations are used. When using a specific vendor's SSF, set the value of the "Acting SSF Type" field to the appropriate vendor value to cause the IN Tester to act correctly.

GENBAND

GENBAND provide custom FurnishChargingInformation and ApplyCharging/ApplyChargingReport INAP messages. When GENBAND is selected as the SSF type, the IN Tester will:

• Provide the GENBAND FCI node variant for use.
• Provide the GENBAND AC/ACR ndoe variant for use.
• Expect that any RRBCSM message sent from the SCF to the SSF is split such that leg 1 and leg 2 events are in separate RRBCSM messages.

SINAP

SINAP provide custom FurnishChargingInformation message. When SINAP is selected as the SSF type, the IN Tester will:

• Provide the SINAP FCI node variant for use.

---