TCAP Op - Abort
Overview
The TCAP Abort operation represents the receipt or sending of a TCAP Abort.
- Direction: OUTBOUND/INBOUND
- From: IN Tester or SCP
- To: SCP or IN Tester
Attributes
The operation attributes are as follows.
Attribute | Type | Description |
---|---|---|
type
|
String |
tcap.hlr_to_scp.Abort or tcap.ssp_to_scp.Abort or tcap.srf_to_scp.Abort or tcap.hlr_from_scp.Abort or tcap.ssp_from_scp.Abort or tcap.srf_from_scp.Abort
|
label
|
String |
An optional label for this node if it is to be the target of a branch operation.
|
arguments
|
Object | [Required] The structure of the TCAP AbortArg we expect to receive or send. Expressions may be supplied within this structure. |
Example
This is an example entry within the operations
array:
{
"type": "tcap.hlr_to_scp.Abort",
"arguments": {
"p_cause": 4
}
}
Arguments
The following arguments are supported.
Argument | Type | Notes |
---|---|---|
p_cause
|
Integer |
An optional p-abortCause value to send or expect.This represents a protocol-level error from the constants defined in Q.773. At most only one of protocol-level cause or user-level data should be present, never both. |
u_source
|
0 / 1
|
An optional u-abortCause .. abort-source value to send or expect.The source is either 0 (user) or 1 (provider) as defined in Q.773.At most only one of protocol-level cause or user-level data should be present, never both. |
u_info_0_octets
|
Binary |
An optional u-abortCause .. user-information [0 ].encoding .octet-aligned value to send or expect.This is arbitrary, unstructured binary content. At most only one of protocol-level cause or user-level data should be present, never both. |