Navigation :

MAP Inbound Register

Overview

The MAP Register operation informs the test application that this script instance is expecting to receive a particular inbound MAP message in the near future.

In general, the test application will be running many scripts simultaneously. When an inbound MAP request is received for a new TCAP transaction, the test application needs this mechanism in order to determine which of the currently running scripts should receive the inbound operation.

This message is typically used by the IN Tester when it is simulating the role of an HLR.

Direction: INBOUND
From: N/A
To: N/A

Attributes

The operation attributes are as follows.

Attribute	Type	Description
`type`	String	`map.hlr_from_scp.Register`
`label`	String	An optional label for this node if it is to be the target of a `branch` operation.
`arguments`	Object	[Required] A structure specifying how to expected inbound MAP transaction will be matched. Expressions may be supplied within this structure.
`.opcode`	`71`	[Required] The MAP operation code. Currently the only supported operation code is `71` for `AnyTimeInterrogrationRequest`.
`.msisdn_digits`	String	The expected inbound MSISDN Digits to register. This field is supported for operation code `71`.
`.imsi_digits`	String	The expected inbound IMSI Digits to register. This field is supported for operation code `71`.

Example

This is an example entry within the operations array:

{
    "type": "map.hlr_from_scp.Register",
    "arguments": {
        "opcode": "71",
        "msisdn_digits": "{$v->{logical}}"
    }
}