You are here: CSP Developers Guide: Common Channel Signaling > 6 SCCP/TCAP > SCCP/TCAP Parameter Information
SCCP/TCAP Parameter Information
Overview
This section contains information on SCCP and TCAP parameters inserted into the SCCP and TCAP ICBs. Note special instructions for the parameters described below.
Description of Parameters
Called Party Address (CDPA)
The CDPA in the primitive request is used if specified. If DPC is not included in the CDPA, the MTP DPC or adjacent translator must be provided.
The following sequence is used for deriving the DPC:
Use DPC in CDPA if provided; otherwise,
If CDPA routes on DPC/SSN, then use the MTP DPC in the primitive or in the SSN default table. If CDPA routes on Global Title, then use the first adjacent translator as the DPC.
Important! As an SSP, Global Title Translation (GTT) is not provided.
Calling Party Address (CGPA)
The CGPA in the primitive request is used if provided; otherwise,
If a TCAP primitive, the CGPA stored for this dialog is used.
If configured for this SSN, the CGPA in the SSN default table is used.
Component Present
This indicates whether or not components are present. If components are present, then only syntactically valid and opportune components are delivered to the destination TC-USER.
Dialog ID
This parameter appears in the dialog handling and component handling primitives. to associate components with a dialog. The same dialog ID must be used within the same dialog. In a Unidirectional primitive, the same dialog ID assures that all components with the identical dialog ID are blocked together in the same Unidirectional message destined for the same destination address.
For structured dialogs, the dialog ID is used to identify all components belonging to the same dialog from the beginning of the dialog to its end. The dialog ID maps onto the transaction IDs exchanged in the messages between a pair of nodes.
Error Code
Use the NATIONAL-ERR-CODE parameter type (0x47) if a national error code is used, or the PRIVATE-ERR-CODE tag (0x48) if a private error code is used.
Last Component
Used in primitives of the Indication type to designate the last component of a message. Note that indication of the last part of the result of an operation is via the name of the primitive.
In the case of multiple components received within a TCAP message, a TC-transaction indication primitive followed by several TC-component indication primitives are sent to the TC-USER. The Last Component parameter in the TC-component primitive specifies if this component is the last component in the message.
This should not be confused with the Last/Not Last primitive type, which indicates the last or not last part of an operation or result of an operation.
Operation
Use the GLOBAL-OPER-CODE parameter type (0x2C) if a national operation code is used, or a LOCAL-OPER-CODE tag (0x2D) if a private operation code is used.
Parameter (ITU only)
Use the PARAMETER-SEQ parameter type (0x4A) to send a sequence of parameters or the PARAMETER-SET tag (0x4B) to send a parameter set.
Problem Code (ITU only)
Use PROBLEM-TYPE-CODE parameter type.
Quality of Service
The QOS in the primitive request is used if specified, otherwise:
The QOS in the SSN default table is used if it is configured for the subsystem, otherwise;
The following default configuration is used:
Return Option = Do Not Return on Error
Sequence Option = Sequence Not Guaranteed
Message Priority (ANSI)=0x00
Termination
Indicates which scenario is chosen by the TC-USER for the end of the dialog (prearranged or basic).
Timeout (ITU only)
The timeout value is in 10 ms units.
This section contains information on ITU SCCP and TCAP parameters inserted into the SCCP and TCAP ICBs.
ITU SCCP Parameter IDs
0x66 |
CGPA (Calling Party Address) |
0x67 |
CGPA (Calling Party Address) Element |
0x68 |
CDPA (Called Party Address) |
0x69 |
CDPA (Called Party Address) Element |
0x6A |
QOS (Quality of Service) |
0x6B |
User Data |
0x6C |
CDPA (Called Party Address) DPC |
0x6D |
Return Reason |
0x6E |
SSN (Subsystem Number) |
0x6F |
SPC (Signaling Point Code) |
0x70 |
SSN (Subsystem Number) Status |
0x71 |
SCCP Signaling Point Status |
0x72 |
Remote SCCP Status |
0x73 |
MTP OPC |
0x74 |
MTP DPC |
ITU TCAP Parameter IDs
0x0F |
Abort Reason |
0x11 |
P-Abort Cause |
0x1F |
Invoke ID |
0x20 |
Link ID |
0x28 |
Invoke Class |
0x29 |
Invoke Timeout |
0x2A |
Problem Type Code |
0x2E |
Parameter |
0x2C |
Global Operation Code |
0x2D |
Local Operation Code |
0x30 |
Last Component |
0x37 |
Protocol Version |
0x38 |
Application Context Name |
0x39 |
User Info |
0x3A |
Termination Option |
0x43 |
Dialog_AS_ID |
0x44 |
Unidialog_AS_ID |
0x45 |
Component Present |
0x47 |
Global Error Code |
0x48 |
Local Error Code |
0x6D |
Return Reason |
This section contains information on ANSI SCCP and TCAP parameters inserted into the SCCP and TCAP ICBs.
ANSI SCCP Parameter IDs
0x66 |
CGPA (Calling Party Address) |
0x67 |
CGPA (Calling Party Address) Element |
0x68 |
CDPA (Called Party Address) |
0x69 |
CDPA (Called Party Address) Element |
0x6A |
QOS (Quality of Service) |
0x6B |
User Data |
0x6C |
CDPA (Called Party Address) DPC |
0x6D |
Return Reason |
0x6E |
SSN (Subsystem Number) |
0x6F |
SPC (Signaling Point Code) |
0x70 |
SSN (Subsystem Number) Status |
0x71 |
SCCP Signaling Point Status |
0x73 |
MTP OPC |
0x74 |
MTP DPC |
ANSI TCAP Parameter IDs
0x0F |
User Abort Info |
0x11P |
Abort Cause |
0x1F |
Invoke ID |
0x20 |
Correlation ID |
0x2A |
Problem Type Code |
0x2C |
National Operation Code |
0x2D |
Local Operation Code |
0x30 |
Last Component |
0x3A |
Termination Option |
0x45 |
Component Present |
0x47 |
National Error Code |
0x48 |
Private Error Code |
0x4A |
Parameter Sequence |
0x4B |
Parameter Set |
0x6D |
Return Reason |
The following table illustrates the parameter format for parameters inserted into the SCCP and TCAP ICBs.
Byte |
Field |
---|---|
Data[0] |
Parameter 1 ID |
Data[1] |
|
Data[2] |
Parameter Length |
Data[3] |
|
Data[4+] |
Parameter-specific Fields |
Parameter Data
This section shows the specific data for each parameter.
Abort Reason
Byte |
Value(s) |
---|---|
Data[4] Reason |
0x00 = User-defined 0x01 = Application Context Name Not Supported (ITU Only) 0x02 - Dialog Refused |
Calling Party Address (CGPA)
Byte |
Value(s) |
---|---|
Data[4+] Calling Party Address |
Conforms to ANSI or ITU specification. |
Calling Party Address (CGPA) Element
Byte |
Value(s) |
---|---|
Data[4] Routing Indication |
0x00 = Route on GT |
Data[5] National/International Flag
|
0x00 = Coded International |
Data[6] Subsystem Number |
|
Data[710] Point Code |
|
Data[11] Global Title Indicator |
|
Data[12] Global Title Length |
Variable |
: |
: |
Data[N] Global Title |
|
Note:
1. Subsystem Number is 0x00 if unknown or not provided.
2. The Point Code is 0xFFFFFFFF if unknown or not provided.
3. The Calling Party Address is constructed with the elements provided and converted to ANSI or ITU format according to the appropriate specification.
4. The National/International flag applies only to indication. In a request, SCCP codes the CGPA according to the SCCP SCLC Component SCLC Configuration Byte 1.
5. "Global Title Indicator" in Data[11] corresponds to the "Global Title Indicator" in the SCCP message CGPA.
Called Party Address (CDPA) Element
Byte |
Value(s) |
---|---|
Data[4] Routing Indication |
0x00 = Route on GT |
Data[5] National/International Flag |
0x00 = Coded International |
Data[6] Subsystem Number |
|
Data[710] Point Code |
|
Data[11] Global Title Indicator |
|
Data[12] Global Title Length |
(Variable) |
: |
: |
Data[N] Global Title |
|
Note
1. Subsystem Number is 0x00 if unknown or not provided.
2. The Point Code is 0xFFFFFFFF if unknown or not provided.
3. The Called Party Address is constructed with the elements provided and converted to ANSI or ITU format according to the appropriate specification.
4. The National/International flag applies only to indication. In a request, SCCP codes the CDPA according to the SCCP PPL SCLC Component Config Byte 1.
5. "Global Title Indicator" in Data[11] corresponds to the "Global Title Indicator" of the SCCP message CDPA.
Class
Byte |
Value(s) |
---|---|
Data[4] Class |
Class Number (14) |
Component Present
Byte |
Value(s) |
---|---|
Data[4] |
0x00 Not Present |
Dialog_AS_ID
The values for the Dialog_AS_ID parameter are automatically stored in the CSP, consistent with ITU TCAP specifications. They cannot be modified by the host if you use the ITU White Book.
Byte |
Value(s) |
---|---|
Data[4] Status |
0x01 = Signaling Point Inaccessible |
Error Code
Byte |
Value(s) |
---|---|
Data[4] Code |
Global or Local Error Code |
Last Component
Byte |
Value(s) |
---|---|
Data[4] |
0x00 Last Component |
Operation
Byte |
Value(s) |
---|---|
Data[4] Code |
Global or Local Operation Code |
P Abort Cause (ITU)
Byte |
Value(s) |
---|---|
Data[4] Cause |
0x00 = Unrecognized Message Type |
P Abort Cause (ANSI)
Byte |
Value(s) |
---|---|
Data[4] Cause |
0x01 = Unrecognized Package Type |
Problem Type Code (ITU)
Byte |
Value(s) |
---|---|
Data[4] Problem Type |
0x01 = General |
Data[5] Problem Code |
General |
Problem Type Code (ANSI)
Byte |
Value(s) |
---|---|
Data[4] Problem Type |
0x01=General |
Data[5] Problem Code |
All Types 0x00=Not Used General 0x01=Unrecognized Component Type Invoke 0x01=Duplicate Invoke ID Return Result 0x01=Unrecognized Correlation ID Return Error 0x01=Unrecognized Correlation ID Transaction Portion 0x01=Unrecognized Package Type |
Protocol Version
The values for the Protocol Version parameter are automatically stored, consistent with ITU TCAP specifications. They cannot be modified by the host if you use the ITU White Book.
Quality of Service (QOS)
Byte |
Value(s) |
---|---|
Data[4] Return Option |
0x00=Discard on Error 0x01=Return on Error |
Data[5] Sequence Control Parameter |
0x00=Sequence not Guaranteed For other than zero, this value is used for sequence control.** |
Data[6] Message Priority* |
(ANSI Only) |
*Refer to ANSI MTP Specification T1-111.5 for the information on selecting message priority.
**For the outgoing messages, the sequence is guaranteed for the messages with the same sequence control value. They will reach the destination in the same order as they were sent out. For the incoming messages, this value simply means the sequence is guaranteed (SCCP class 1 services are used in this case).
Remote SCCP Status
Byte |
Value(s) |
---|---|
Data[4] Status |
0x01=Remote SCCP Available |
Return Reason (ITU)
Byte |
Value(s) |
---|---|
Data[4] Cause |
0x00 No Translation for an Address of Such Nature *Only applicable to XUDTS message. |
Return Reason (ANSI)
Byte |
Value(s) |
---|---|
Data[4] Cause |
0x00 No Translation for an Address of Such Nature *=Only applicable to XUDT and XUDTS messages. |
SCCP Signaling Point Status
Byte |
Value(s) |
---|---|
Data[4] Status |
0x01=SCCP DPC Prohibited |
Subsystem Status
Byte |
Value(s) |
---|---|
Data[4] Status |
0x00=Prohibit |
Termination Option
Byte |
Value(s) |
---|---|
Data[4] Option |
0x01=Pre-arranged End |
Unidialog_AS_ID
The values for the Unidialog_AS_ID parameter are automatically stored, consistent with ITU TCAP specifications. They should not be modified by the host if you use the ITU White Book.
Application Context Name
MTP DPC
Correlation ID
Invoke ID
Linked ID
Parameters
Parameter Sequence
Parameter Set
Signaling Point Code (SPC)
Subsystem Number
Timeout
User Data
User Information