| 1 | Introduction |
| 1.1 | Purpose |
| 1.2 | History |
| 1.3 | Terms |
2 | Compliance |
| 2.1 | Concepts |
| 2.2 | GR-1299-CORE, Issue 10, November 2004 |
Reference List | |
1 Introduction
1.1 Purpose
The purpose of this document is to describe how the AIN message library complies with the AIN protocol specification GR-1299-CORE.
1.2 History
|
Revision |
Date |
Author |
Comment |
|
A |
2008-03-05 |
XTSDANI |
First approved revision. |
1.3 Terms
| AIN | Advanced Intelligent Network | |
| LNP | Local Number Portability | |
| SCP | Service Control Point | |
| SS7 | Signaling System Number 7 | |
| SSP | Service Switching Point | |
2 Compliance
2.1 Concepts
The following abbreviations are used throughout this document:
| C (=Compliant) | The implementation fully complies with the protocol specification. | |
| N (=Not Compliant) | The feature described in the protocol specification is not implemented or is implemented in a completely different way. A comment is added in the latter case. | |
| P (=Partially Compliant) | The implementation complies functionally with the protocol specification with some variations. A comment is added describing the deviation. | |
| - | There is nothing to implement in the referred section of the protocol specification (always placed in column C). | |
| N/A | The requirements in the referred section of the protocol specification are outside the scope of AIN Message Library (always placed in column C). The requirements may be of interest to an application that is using AIN Message Library. | |
2.2 GR-1299-CORE, Issue 10, November 2004
Following is a table where it is stated to what degree AIN Message Library complies with the requirements in each section of GR-1299-CORE (Reference [1]). GR-1299-CORE frequently refers to GR-1298-CORE, Reference [2].
|
References |
C |
N |
P |
Comments |
|---|---|---|---|---|
|
1. Introduction |
- |
|||
|
1.1 Purpose and Scope |
- |
|||
|
1.2 Relationship to Other Telcordia AIN GRs and IN Standards |
- |
|||
|
1.3 Definitions |
- |
|||
|
1.4 Conventions |
- |
|||
|
1.5 Requirements Terminology |
- |
|||
|
1.6 Requirement Labeling Conventions |
- |
|||
|
1.6.1 Numbering of Requirement and Related Objects |
- |
|||
|
1.6.2 Requirement, Conditional Requirement, and Objective Object Identification |
- |
|||
|
1.7 Document Organization |
- |
|||
|
1.8 Major Changes from GR-1299-CORE, Issue 9 |
- |
|||
|
2. Notation and Protocol Description |
- |
|||
|
2.1 Abstract Syntax and Transfer Syntax Notation |
X |
|||
|
2.2 TCAP |
- |
|||
|
2.2.1 General TCAP Package Structure |
- |
|||
|
2.2.2 Package Type and Transaction ID Requirements |
N/A |
|||
|
2.2.3 Component Type and Component ID Requirements |
N/A |
|||
|
2.2.4 Description of TCAP in ASN.1 |
X |
Missing Mandatory Parameter is detected, but reported with Problem Code Badly Structured Component Portion. | ||
|
3. Normal Procedures |
- |
|||
|
3.1 Definitions |
- |
|||
|
3.1.1 Switch Call Related Message |
- |
|||
|
3.1.1.1 Switch Request Message |
- |
|||
|
3.1.1.2 Switch Response Message |
- |
|||
|
3.1.1.3 Switch Notification Message |
- |
|||
|
3.1.2 SCP/Adjunct Call Related Message |
- |
|||
|
3.1.2.1 SCP/Adjunct Response Message |
- |
|||
|
3.1.2.2 SCP/Adjunct Event Message |
- |
|||
|
3.1.3 SCP/Adjunct Non-Call Related Message |
- |
|||
|
3.1.4 Switch Non-Call Related Message |
- |
|||
|
3.1.5 Multiple-Component Package |
- |
|||
|
3.1.6 Transactions |
- |
|||
|
3.1.6.1 Transaction Already Exists |
- |
|||
|
3.1.6.2 Transaction Does Not Already Exist |
- |
|||
|
3.1.6.3 Call Related Transaction |
- |
|||
|
3.1.6.4 Non-Call Related Transaction |
- |
|||
|
3.2 SCP/Adjunct-to-SSP Messages |
- |
|||
|
3.2.1 SCP/Adjunct Call Related Messages |
- |
|||
|
3.2.1.1 Transaction Level Procedures |
N/A |
|||
|
3.2.1.2 Component Level Procedures |
N/A |
|||
|
3.2.2 SCP/Adjunct Non-Call Related Messages |
- |
|||
|
3.2.2.1 Transaction Level Procedures |
N/A |
|||
|
3.2.2.2 Component Level Procedures |
N/A |
|||
|
3.3 SSP-to-SCP/Adjunct Messages |
- |
|||
|
3.3.1 Switch Call Related Messages |
- |
|||
|
3.3.1.1 Transaction Level Procedures |
N/A |
|||
|
3.3.1.2 Component Level Procedures |
N/A |
|||
|
3.3.2 Switch Non-Call Related Messages |
- |
|||
|
3.3.2.1 Transaction Level Procedures |
N/A |
|||
|
3.3.2.2 Component Level Procedures |
N/A |
|||
|
3.4 Dialogue Portion Requirements |
N/A |
|||
|
3.4.1 Switch-Initiated Transactions |
- |
|||
|
3.4.1.1 Switch Establishes the Transaction |
N/A |
|||
|
3.4.1.2 SCP/Adjunct Responds to the Query |
N/A |
|||
|
3.4.1.3 Switch Reaction to SCP/Adjunct Reply |
N/A |
|||
|
3.4.2 Switch Unidirectional Packages |
- |
|||
|
3.4.2.1 Switch Sends Unidirectional Package |
N/A |
|||
|
3.4.2.2 SCP/Adjunct Receives Unidirectional Package |
N/A |
|||
|
3.4.3 SCP/Adjunct Initiated Transactions |
- |
|||
|
3.4.3.1 SCP/Adjunct Establishes the Transaction |
N/A |
|||
|
3.4.3.2 Switch Responds to Query |
N/A |
|||
|
3.4.4 SCP/Adjunct Unidirectional Packages |
- |
|||
|
3.4.4.1 SCP/Adjunct Sends Unidirectional Package |
N/A |
|||
|
3.4.4.2 Switch Receives Unidirectional Package |
N/A |
|||
|
3.5 Summary Information |
- |
|||
|
4. Abnormal Procedures |
- |
|||
|
4.1 Definitions |
- |
|||
|
4.2 Protocol Errors |
- |
|||
|
4.2.1 Detectable Protocol Errors |
N/A |
|||
|
4.2.1.1 Fatal Transaction Portion Protocol Errors |
N/A |
|||
|
4.2.1.2 Fatal Component Portion Protocol Errors |
X |
The following protocol errors are detected in some cases:
Missing Mandatory Parameter is detected, but reported with Problem Code Badly Structured Component Portion. The rest of the protocol errors are outside the scope of AIN Message Library, and should be handled by the application. | ||
|
4.2.1.3 Fatal Dialogue Portion Protocol Errors |
N/A |
|||
|
4.2.1.4 Non-Fatal Protocol Errors |
X |
The Unrecognized Identifier non-fatal protocol error are handled according to Alternative 2 (CR4-9, CR4-10 and CR4-11). During decoding of parameters, all unrecognized identifiers are ignored and the decoding continues with the next parameter or field. Missing Mandatory Field conditions are not handled. | ||
|
4.2.2 Reporting Protocol Errors at the Transaction Level |
- |
|||
|
4.2.2.1 Fatal Transaction Portion Protocol Errors |
N/A |
|||
|
4.2.2.2 Fatal Component Portion Protocol Errors |
N/A |
|||
|
4.2.2.3 Fatal Dialogue Portion Protocol Errors |
N/A |
|||
|
4.2.3 Reporting Protocol Errors at the Component Level |
- |
|||
|
4.2.3.1 Fatal Protocol Errors |
N/A |
|||
|
4.2.3.2 Non-Fatal Protocol Errors |
N/A |
|||
|
4.3 Application Errors |
- |
|||
|
4.3.1 Description of Application Errors |
- |
|||
|
4.3.2 Detectable Application Errors |
- |
|||
|
4.3.2.1 Fatal Application Errors |
X |
Erroneous Data Value is detected in decoding of ChargePartyStationType, Carrier, AlternateCarrier, SecondAlternateCarrier and TranslationType. This type of application error should be handled by the application as well. Unexpected Parameter Sequence is not detected. The rest of the application errors are outside the scope of AIN Message Library, and should be handled by the application. | ||
|
4.3.2.2 Non-Fatal Application Errors |
X |
Erroneous Data Value is detected in decoding of ChargePartyStationType, Carrier, AlternateCarrier, SecondAlternateCarrier and TranslationType. This type of application error should be handled by the application as well. The rest of the application errors are outside the scope of AIN Message Library, and should be handled by the application. | ||
|
4.3.3 Reporting Application Errors |
- |
|||
|
4.3.3.1 Fatal Application Errors Without Fatal Dialogue Portion Application Error |
N/A |
|||
|
4.3.3.2 Fatal Dialogue Portion Application Errors |
N/A |
|||
|
4.3.3.3 Non-Fatal Application Errors |
N/A |
|||
|
4.4 Failures |
- |
|||
|
4.4.1 Detectable Failures |
N/A |
|||
|
4.4.2 Reporting Failures |
- |
|||
|
4.4.2.1 Transaction Level Procedures |
N/A |
|||
|
4.4.2.2 Component Level Procedures |
N/A |
|||
|
4.5 Caller Abandon |
N/A |
|||
|
4.6 Summary Information |
- |
|||
|
5. Messages |
X |
The ExtensionParameter is not supported, it is ignored if present in a decoded message. There are some requirements in this section that are outside the scope of AIN Message Library, and should be handled by the application. | ||
|
5.1 Message Cross-Reference List |
- |
|||
|
5.2 Call Related Messages |
- |
|||
|
5.2.1 Switch Call Related Messages |
- |
|||
|
5.2.1.1 Call_Info_From_Resource |
X |
|||
|
5.2.1.2 Close |
X |
Partly supported for SSP. An invoke component containing the CloseCause parameter can be encoded. | ||
|
5.2.1.3 CTR_Clear |
X |
|||
|
5.2.1.4 Failure_Outcome |
X |
|||
|
5.2.1.5 Info_Analyzed |
X |
Partly supported for SSP. An invoke component containing the following parameters can be encoded:
| ||
|
5.2.1.6 Info_Collected |
X |
|||
|
5.2.1.7 Network_Busy |
X |
|||
|
5.2.1.8 O_Abandon |
X |
|||
|
5.2.1.9 O_Answer |
X |
|||
|
5.2.1.10 O_Called_Party_Busy |
X |
|||
|
5.2.1.11 O_Disconnect |
X |
|||
|
5.2.1.12 O_DTMF_Entered |
X |
|||
|
5.2.1.13 O_Mid_Call |
X |
|||
|
5.2.1.14 O_No_Answer |
X |
|||
|
5.2.1.15 O_Suspended |
X |
|||
|
5.2.1.16 O_Term_Seized |
X |
|||
|
5.2.1.17 Origination_Attempt |
X |
|||
|
5.2.1.18 Resource_Clear |
X |
|||
|
5.2.1.19 Set_Timer_Reply |
X |
|||
|
5.2.1.20 Success_Outcome |
X |
|||
|
5.2.1.21 T_Answer |
X |
|||
|
5.2.1.22 T_Busy |
X |
|||
|
5.2.1.23 T_Disconnect |
X |
|||
|
5.2.1.24 T_DTMF_Entered |
X |
|||
|
5.2.1.25 T_Mid_Call |
X |
|||
|
5.2.1.26 T_No_Answer |
X |
|||
|
5.2.1.27 Termination_Attempt |
X |
|||
|
5.2.1.28 Term_Resource_Available |
X |
|||
|
5.2.1.29 Timeout |
X |
|||
|
5.2.2 SCP/Adjunct Call Related Messages |
- |
|||
|
5.2.2.1 Acknowledge |
X |
|||
|
5.2.2.2 Analyze_Route |
X |
Partly supported for SSP. An invoke component can be decoded, the following parameters can be extracted:
| ||
|
5.2.2.3 Authorize_Termination |
X |
|||
|
5.2.2.4 Call_Info_To_Resource |
X |
|||
|
5.2.2.5 Cancel_Resource_Event |
X |
|||
|
5.2.2.6 Collect_Information |
X |
Partly supported for SSP. The operation code can be decoded. No parameters can be decoded. | ||
|
5.2.2.7 Connect_To_Resource |
X |
|||
|
5.2.2.8 Continue |
X |
Partly supported for SSP. The operation code can be decoded. No parameters can be decoded. | ||
|
5.2.2.9 Create_Call |
X |
|||
|
5.2.2.10 Disconnect |
X |
Partly supported for SSP. The operation code can be decoded. No parameters can be decoded. | ||
|
5.2.2.11 Disconnect_Leg |
X |
|||
|
5.2.2.12 Forward_Call |
X |
|||
|
5.2.2.13 Merge_Call |
X |
|||
|
5.2.2.14 Move_Leg |
X |
|||
|
5.2.2.15 Offer_Call |
X |
|||
|
5.2.2.16 Originate_Call |
X |
|||
|
5.2.2.17 Reconnect |
X |
|||
|
5.2.2.18 Send_To_Resource |
X |
Partly supported for SSP. An invoke component can be decoded, the following parameters can be extracted:
| ||
|
5.2.2.19 Set_Timer |
X |
|||
|
5.2.2.20 Split_Leg |
X |
|||
|
5.3 Non-Call Related Messages |
- |
|||
|
5.3.1 ACG |
X |
Partly supported for SSP. An invoke component can be decoded, the following parameters can be extracted:
| ||
|
5.3.2 ACG_Global_Ctrl_Restore |
X |
Partly supported for SSP. An invoke component can be decoded, the ACGGlobalOverride parameter can be extracted. A return result component containing no parameters (just the SEQUENCE tag) can be encoded. | ||
|
5.3.3 ACG_Global_Ctrl_Restore_Success |
X |
See 5.3.2 ACG_Global_Ctrl_Restore, return result component. | ||
|
5.3.4 ACG_Overflow |
X |
|||
|
5.3.5 Activity_Test |
X |
|||
|
5.3.6 Activity_Test_Reply |
X |
|||
|
5.3.7 Call_Type_Request |
X |
|||
|
5.3.8 Call_Type_Response |
X |
|||
|
5.3.9 Control_Request |
X |
|||
|
5.3.10 Echo_Reply |
X |
|||
|
5.3.11 Echo_Request |
X |
|||
|
5.3.12 Furnish_AMA_Information |
X |
|||
|
5.3.13 Monitor_For_Change |
X |
|||
|
5.3.14 Monitor_Success |
X |
|||
|
5.3.15 NCA_Data |
X |
|||
|
5.3.16 NCA_Request |
X |
|||
|
5.3.17 NCA_Response |
X |
|||
|
5.3.18 Query_Request |
X |
|||
|
5.3.19 Query_Response |
X |
|||
|
5.3.20 Request_Report_BCM_Event |
X |
Partly supported for SSP. The operation code can be decoded. No parameters can be decoded. | ||
|
5.3.21 Send_Notification |
X |
Partly supported for SSP. An invoke component can be decoded, the EchoData parameter can be extracted. | ||
|
5.3.22 Status_Reported |
X |
|||
|
5.3.23 Termination_Notification |
X |
Partly supported for SSP. An invoke component containing the following parameters can be encoded:
| ||
|
5.3.24 Update |
X |
|||
|
5.3.25 Update_Data |
X |
|||
|
5.3.26 Update_Request |
X |
|||
|
5.3.27 Update_Success |
X |
|||
|
5.4 Abnormal Messages |
- |
|||
|
5.4.1 Application Errors |
- |
|||
|
5.4.1.1 Application_Error |
X |
A return error component containing the ApplicationErrorString parameter (ErrorCause part) can be encoded. A return error component can be decoded, the ErrorCause part of the ApplicationErrorString parameter can be extracted. The error code can not be encoded or decoded. | ||
|
5.4.1.2 Report_Error |
X |
An invoke component containing the ApplicationErrorString parameter (ErrorCause part) can be encoded. An invoke component can be decoded, the ErrorCause part of the ApplicationErrorString parameter can be extracted. | ||
|
5.4.1.3 Failure_Report |
X |
A return error component containing the FailureCause parameter can be encoded. A return error component can be decoded, the FailureCause parameter can be extracted. The error code can not be encoded or decoded. | ||
|
5.4.2 Protocol Errors |
X |
General Problem Codes incorrectComponentPortion and badlyStructuredComponentPortion are used when these protocol errors are detected. Missing Mandatory Parameter is detected, but reported with General Problem Code badlyStructuredComponentPortion. The rest of the Problem Codes are outside the scope of AIN Message Library. | ||
|
5.5 Message Tables |
- |
|||
|
6. Parameters and Formats |
X |
R6-1: Values marked as spare or reserved are permitted and do not result in Erroneous Data Value. R6-1: Values omitted (not assigned any meaning) are not detected as Erroneous Data Value (examples include ACGGlobalOverride, ErrorCause, FailureCause, GapDuration, GapInterval). The rest of the requirements in this section are outside the scope of AIN Message Library, and should be handled by the application. | ||
|
6.1 AccessCode |
X |
|||
|
6.2 ACGEncountered |
X |
Can be encoded in the Info_Analyzed invoke component. | ||
|
6.3 ACGGlobalOverride |
X |
Can be decoded in the ACG_Global_Ctrl_Restore invoke component. | ||
|
6.4 AdministrableObject |
X |
|||
|
6.4.1 TriggerItemAssignment |
X |
|||
|
6.4.2 SSPUserResource |
X |
|||
|
6.4.3 SrhrGroup |
X |
|||
|
6.4.4 NetworkTestDesignator |
X |
|||
|
6.4.5 OperationsMonitoringAssignment |
X |
|||
|
6.5 ActResult |
X |
|||
|
6.6 AINDigits |
X |
This format type is used by several parameters that include digits as part of their contents. | ||
|
6.7 AlternateBillingIndicator |
X |
|||
|
6.8 AlternateCarrier |
X |
Can be decoded in the Analyze_Route invoke component. | ||
|
6.9 AlternateDialingPlanInd |
X |
|||
|
6.10 AlternateTrunkGroup |
X |
Can be decoded in the Analyze_Route invoke component. | ||
|
6.11 AMAAlternateBillingNumber |
X |
Can be decoded in the Analyze_Route invoke component. | ||
|
6.12 AMABAFModules |
X |
|||
|
6.13 AMABillingFeature |
X |
|||
|
6.14 AMABusinessCustomerID |
X |
Can be decoded in the Analyze_Route invoke component. | ||
|
6.15 AMADigitsDialedWC |
X |
Can be decoded in the Analyze_Route invoke component. | ||
|
6.16 AMALineNumber |
X |
Can be decoded in the Analyze_Route invoke component. | ||
|
6.17 AMAMeasure |
X |
|||
|
6.18 AMAMeasurement |
X |
|||
|
6.19 AMAServiceProviderID |
X |
Can be decoded in the Analyze_Route invoke component. | ||
|
6.20 AMASetHexABIndicator |
X |
|||
|
6.21 AMASequenceNumber |
X |
Can be decoded in the Analyze_Route invoke component. | ||
|
6.22 AMAslpID |
X |
Can be decoded in the Analyze_Route invoke component. | ||
|
6.23 Amp1 |
X |
|||
|
6.24 Amp2 |
X |
|||
|
6.25 AnswerIndicator |
X |
|||
|
6.26 ApplicationErrorString |
X |
Can be encoded and decoded in the Application_Error return error component and in the Report_Error invoke component. The optional fields FailedMessage and UserID can not be encoded or extracted from decoding. | ||
|
6.27 ApplicationIndicator |
X |
|||
|
6.28 ApplyRestrictions |
X |
|||
|
6.29 BCMType |
X |
|||
|
6.30 BearerCapability |
X |
Can be encoded in the Info_Analyzed invoke component. The values not used for AIN can not be encoded. | ||
|
6.31 BillingIndicator |
X |
|||
|
6.32 BusinessGroup |
X |
|||
|
6.33 BusyCause |
X |
|||
|
6.34 BusyType |
X |
|||
|
6.35 CalledPartyID |
X |
Can be encoded in the Info_Analyzed invoke component and decoded in the Analyze_Route invoke component. | ||
|
6.36 CalledPartyStationType |
X |
|||
|
6.37 CallingGeodeticLocation |
X |
|||
|
6.38 CallingPartyBGID |
X |
|||
|
6.39 CallingPartyID |
X |
Can be encoded in the Info_Analyzed invoke component. | ||
|
6.40 CallType |
X |
|||
|
6.41 Carrier |
X |
Can be encoded in the Info_Analyzed invoke component and decoded in the Analyze_Route invoke component. | ||
|
6.42 CarrierFormat |
X |
This format type is used by the Carrier, AlternateCarrier and SecondAlternateCarrier parameters. It is supported where these parameters are supported. | ||
|
6.43 CarrierUsage |
X |
|||
|
6.44 CcID |
X |
|||
|
6.45 ChargeNumber |
X |
Can be encoded in the Info_Analyzed invoke component. | ||
|
6.46 ChargePartyStationType |
X |
Can be encoded in the Info_Analyzed invoke component and decoded in the Analyze_Route invoke component. | ||
|
6.47 ClearCause |
X |
|||
|
6.48 ClearCauseData |
X |
|||
|
6.49 CloseCause |
X |
Can be encoded in the Close invoke component. | ||
|
6.50 CollectedAddressInfo |
X |
|||
|
6.51 CollectedDigits |
X |
|||
|
6.52 CongestionLevel |
X |
|||
|
6.53 ConnectTime |
X |
Can be encoded in the Termination_Notification invoke component. | ||
|
6.54 ControlCauseIndicator |
X |
Can be decoded in the ACG invoke component. | ||
|
6.55 ControlEncountered |
X |
|||
|
6.56 ControllingLegTreatment |
X |
|||
|
6.57 CsID |
X |
|||
|
6.58 CTRConnection |
X |
|||
|
6.59 DestinationAddress |
X |
Can be decoded in the Send_To_Resource invoke component. | ||
|
6.60 DisconnectCause |
X |
|||
|
6.61 DisconnectFlag |
X |
Can be decoded in the Send_To_Resource invoke component. | ||
|
6.62 DisplayText |
X |
|||
|
6.63 DPConverter |
X |
|||
|
6.64 DTMFDigitsDetected |
X |
|||
|
6.65 EchoData |
X |
Can be decoded in the Send_Notification invoke component and encoded in the Termination_Notification invoke component. | ||
|
6.66 EditListType |
X |
|||
|
6.67 EDPNotification |
X |
|||
|
6.68 EDPRequest |
X |
|||
|
6.69 EnvelopContent |
X |
|||
|
6.70 EnvelopeEncodingAuthority |
X |
|||
|
6.71 ErrorCause |
X |
|||
|
6.72 ExtendedRinging |
X |
|||
|
6.73 ExtensionParameter |
X |
|||
|
6.74 FacilityGID |
X |
|||
|
6.75 FacilityMemberID |
X |
|||
|
6.76 FacilityStatus |
X |
|||
|
6.77 FailedMessage |
X |
|||
|
6.78 FailureCause |
X |
Can be encoded and decoded in the Failure_Report return error component. | ||
|
6.79 FailureCauseData |
X |
|||
|
6.80 FeatureActivatorID |
X |
|||
|
6.81 ForwardCallIndicator |
X |
|||
|
6.82 GapDuration |
X |
Can be decoded in the ACG invoke component. | ||
|
6.83 GapInterval |
X |
Can be decoded in the ACG invoke component. | ||
|
6.84 GenericAddress |
X |
|||
|
6.85 GenericAddressList |
X |
|||
|
6.86 GenericDigits |
X |
|||
|
6.87 GenericDigitsList |
X |
|||
|
6.88 GenericName |
X |
|||
|
6.89 GlobalTitleAddress |
X |
Can be decoded in the ACG invoke component. Supported with size constraint OCTET STRING (SIZE(5)). | ||
|
6.90 InfoProvided |
X |
|||
|
6.91 IPReturnBlock |
X |
|||
|
6.92 JurisdictionInformation |
X |
Can be encoded in the Info_Analyzed invoke component. | ||
|
6.93 LampTreatment |
X |
|||
|
6.94 Lata |
X |
Can be encoded in the Info_Analyzed invoke component. | ||
|
6.95 LegID |
X |
|||
|
6.96 MonitorTime |
X |
|||
|
6.97 NetworkSpecificFacilities |
X |
|||
|
6.98 NotificationDuration |
X |
|||
|
6.99 NotificationIndicator |
X |
|||
|
6.100 ODTMFDigitsString |
X |
|||
|
6.101 ODTMFNumberOfDigits |
X |
|||
|
6.102 ONoAnswerTimer |
X |
|||
|
6.103 OriginalCalledPartyID |
X |
|||
|
6.104 OSIIndicator |
X |
|||
|
6.105 OutpulseNumber |
X |
|||
|
6.106 OverflowBillingIndicator |
X |
|||
|
6.107 PartyID |
X |
|||
|
6.108 PartyOnHold |
X |
|||
|
6.109 PassiveLegTreatment |
X |
|||
|
6.110 PointInCall |
X |
|||
|
6.111 Prefix |
X |
|||
|
6.112 PrimaryBillingIndicator |
X |
|||
|
6.113 PrimaryTrunkGroup |
X |
Can be decoded in the Analyze_Route invoke component. | ||
|
6.114 ProvideInfo |
X |
|||
|
6.115 RedirectingPartyID |
X |
|||
|
6.116 RedirectionInformation |
X |
|||
|
6.117 ResourceType |
X |
Can be decoded in the Send_To_Resource invoke component. | ||
|
6.118 ResultCause |
X |
|||
|
6.119 RTPReroutingNumber |
X |
|||
|
6.120 RTPServiceIndicator |
X |
|||
|
6.121 Sap |
X |
|||
|
6.122 SecondAlternateBillingIndicator |
X |
|||
|
6.123 SecondAlternateCarrier |
X |
Can be decoded in the Analyze_Route invoke component. | ||
|
6.124 SecondAlternateTrunkGroup |
X |
Can be decoded in the Analyze_Route invoke component. | ||
|
6.125 SecurityEnvelope |
X |
|||
|
6.126 ServiceContext |
X |
|||
|
6.127 ServiceProviderID |
X |
|||
|
6.128 SignalingPointCode |
X |
|||
|
6.129 Spid |
X |
This format type is supported for UserID parameter, see 6.151. | ||
|
6.130 SrhrGroupID |
X |
|||
|
6.131 SSPResponseMessageTimerT1 |
X |
|||
|
6.132 StatusCause |
X |
|||
|
6.133 STRConnection |
X |
|||
|
6.134 StrParameterBlock |
X |
Can be decoded in the Send_To_Resource invoke component. StrParameterBlock is divided into sub-fields. Extraction of the individual sub-fields is not supported. | ||
|
6.134.1 Play Announcements |
X |
Extraction of this sub-field is not supported. See 6.134. | ||
|
6.134.2 Play Announcements and Collect Digits |
X |
Extraction of this sub-field is not supported. See 6.134. | ||
|
6.134.3 Flex Parameter Block |
X |
Extraction of this sub-field is not supported. See 6.134. | ||
|
6.135 SubsystemNumber |
X |
|||
|
6.136 Tcm |
X |
|||
|
6.137 TDTMFDigitsString |
X |
|||
|
6.138 TDTMFNumberOfDigits |
X |
|||
|
6.139 TerminateOnNoAnswer |
X |
|||
|
6.140 TerminationIndicator |
X |
Can be encoded in the Termination_Notification invoke component. | ||
|
6.141 TimeoutTimer |
X |
|||
|
6.142 TimerUpdated |
X |
|||
|
6.143 TNoAnswerTimer |
X |
|||
|
6.144 TransID |
X |
|||
|
6.145 TranslationType |
X |
Can be decoded in the ACG invoke component. | ||
|
6.146 TriggerCriteriaFlag |
X |
|||
|
6.147 TriggerCriteriaType |
X |
Can be encoded in the Info_Analyzed invoke component. Only values used for Local Number Portability and Toll-free queries are supported:
| ||
|
6.148 TriggerInformation |
X |
|||
|
6.149 TSTRCTimer |
X |
|||
|
6.150 UpdateFailure |
X |
|||
|
6.150.1 TTNoAnswerTimerFailure |
X |
|||
|
6.150.2 TONoAnswerTimerFailure |
X |
|||
|
6.150.3 TriggerItemAssignmentFailure |
X |
|||
|
6.150.4 PotentialUseFailure |
X |
|||
|
6.150.5 UpdateGroupsFailure |
X |
|||
|
6.150.6 DPConverterFailure |
X |
|||
|
6.150.7 CancelInterdigitTimerFailure |
X |
|||
|
6.151 UserID |
X |
Can be encoded in the Info_Analyzed invoke component. | ||
|
6.152 VerticalServiceCode |
X |
|||
|
6.153 WakeUpDuration |
X |
|||
|
7. SCCP Procedures |
- |
|||
|
7.1 SCCP Model |
- |
|||
|
7.2 General SCCP |
- |
|||
|
7.2.1 Receipt of (Extended) Unitdata Messages |
N/A |
|||
|
7.2.2 Message Return on Error |
N/A |
|||
|
7.2.3 Segmentation |
N/A |
|||
|
7.3 SCCP Parameter Population |
N/A |
|||
|
7.3.1 SSP Initial Message |
N/A |
|||
|
7.3.2 SSP Subsequent Message |
N/A |
|||
|
7.3.3 SCP Initial Message |
N/A |
|||
|
7.3.4 SCP Subsequent Message |
N/A |

Contents