The Reject component

Reject Component               Mandatory indication

Component Type Tag             Mandatory                1 0 1 0 0 1 0 0
Component length (Note)

Invoke ID Tag a)               Mandatory
Invoke ID length
Invoke ID

Problem Code Tag               Mandatory
Problem Code length
Problem Code

a)      If the invoke ID is not available, Universal Null (see Table 12) with Length = 0 should be used.
NOTE - The component length is coded to indicate the number of octets contained in the component (excluding the component type tag and the component length octets).

8)      Problem Code
        The Problem Code consists of one of the four elements - General Problem, Invoke Problem, Return Result Problem or Return Error Problem. The tags for these elements are coded as shown in Table 16. Their values are shown in Tables 17 to 20.
Coding of Problem Type Tags

     Problem type

     General Problem     1 0 0 0 0 0 0 0
     Invoke              1 0 0 0 0 0 0 1
     Return Result       1 0 0 0 0 0 1 0
     Return error        1 0 0 0 0 0 1 1

Coding of General Problem

a)      Components are equivalent to ROSE Application Protocol Data Units (APDU).

Table 18/Q.763 - Coding of Invoke Problem

a)      Invoke parameter is equivalent to ROSE Invoke argument.
b)      ROSE uses "Initiator releasing" as only the initiator of the underlying association may release it. In ISUP, either entity may release the association.
c)      ROSE refers to a linked operation as a child operation.
Table 19/Q.763 - Coding of Return Result Problem

Unrecognized Invoke ID
Return Result Unexpected
Mistyped Parameter

Table 20/Q.763 - Coding of Return Error Problem

Unrecognized Invoke ID
Return Error Unexpected
Unrecognized Error
Unexpected Error
Mistyped Parameter