ETSI Core INAP

7.2 Error procedures

This subclause defines the generic error procedures for the core INAP CS1. The error procedure descriptions have been divided in two subclauses, subclause 7.2.2 listing the errors related to INAP operations and subclause 7.2.3 listing the errors related to error conditions in the different FEs which are not directly related to the INAP operations.

7.2.2 Operation related error procedures

The following subclauses define the generic error handling for the operation related errors. The errors are defined as operation errors in Clause 6. The TCAP services which are used for reporting operation errors are described in subclause 7.4.
Errors which have a specific procedure for an operation are described in subclause 7.3 with the detailed procedure of the related operation.

7.2.2.2 Canceled

7.2.2.2.1 General Description

7.2.2.2.1.1 Error description

The Error "Canceled" gives an indication to the SCF that the cancellation, as it was requested by the SCF, of a specific Operation, has been successful. The SCF is only able to cancel certain predefined SCF->SRF Operations.

7.2.2.2.2 Operations SCF->SRF

PlayAnnouncement
PromptAndCollectUserInformation
Procedures at invoking entity (SCF)
A) Sending Cancel

precondition:	SCSM state 4.1	Waiting for Response from the SRF

postcondition:	SCSM state 4.1	Waiting for Response from the SRF

The SCF sends a Cancel after a Play Announcement (PA) or PromptAndCollectUserInformation (P&C) has been sent. The SCF remains in the same state.

B) Receiving Cancelled Error

precondition:	SCSM state any	SL dependent

postcondition:	SCSM state any	SL dependent

After sending a Cancel operation the SL may continue (e.g. sending more PA or P&C or a DisconnectForwardConnection). The Canceled Error can therefore be received in any state. The treatment is SL dependent.
Procedures at responding entity (SRF)
A) Receiving Cancel

precondition:	SRSM state 3	User Interaction

postcondition:	SRSM state 3	User Interaction

The indicated PA or P&C is terminated if it is presently executing or deleted from the buffer. If the indicated PA or P&C is already executed this causes a failure ("CancelFailed")

B) Sending Cancel Error

precondition:	SRSM state 3	User Interaction

postcondition:	SRSM state 3	User Interaction

After returning the "Canceled" Error the SRF stays in the same state. The execution of the indicated PA or P&C is aborted, i.e. the SRF remains connected and the next PA or P&C is executed if available.

7.2.2.3 CancelFailed

7.2.2.3.1 General description

7.2.2.3.1.1 Error description

This Error is returned by Cancel if the cancelling of an Operation, as requested by the SCF, was not successful. Possible failure reasons are:

0	unknownOperation, when the InvokeID of the operation to cancel is not known to SRF (this may also happen in case the operation has already been completed);

1	tooLate, when the invokeID is known but the execution of the operation is in a stadium that it cannot be cancelled anymore. For instance the announcement is finished but the SpecializedResourceReport has not been sent to the SCF yet. The conditions for the occurrence of failure reason "tooLate" may be implementation dependent;

2	operationNotCancellable, when the invokeID points to an Operation that the SCF is not allowed to cancel.

7.2.2.3.1.2 Argument description

PARAMETER SEQUENCE {

	problem	[0] ENUMERATED {

				unknownOperation (0),

				tooLate (1),

				operationNotCancellable (2)},

	operation	[1] InvokeID}

-- The operation failed to be cancelled.

7.2.2.3.2 Operations SCF->SRF

Cancel
Procedures at invoking entity (SCF)
A) Sending Cancel

precondition:	SCSM state 4.1	Waiting for Response from the SRF

postcondition:	SCSM state 4.1	Waiting for Response from the SRF

The SCF sends a Cancel after a Play Announcement (PA) or PromptAndCollectUserInformation (P&C) has been sent. It remains in the same state.
B) Receiving CancelFailed Error

precondition:	SCSM state any	SL dependent

postcondition:	SCSM state any	SL dependent

After sending a Cancel operation the SL may continue (e.g. sending more PA or P&C or a DisconnectForwardConnection). The CancelFailed Error can therefore be received in any state. The treatment is SL dependent.
Procedures at responding entity (SRF)
A) Receiving Cancel. However, the indicated PA or P&C is not known, or already executed. This causes a failure, CancelFailed.

precondition:	SRSM state 3	User Interaction

postcondition:	SRSM state 3	User Interaction

	or	SRSM state 1	Idle

B) Sending CancelFailed Error

precondition:	SRSM state 3	User Interaction

	or	SRSM state 1	Idle

postcondition:	SRSM state 3	User Interaction

	or	SRSM state 1	Idle

After returning the CancelFailed the SRF stays in the same state.

7.2.2.4 ETCFailed

7.2.2.4.1 General description

7.2.2.4.1.1 Error description

ETCFailed is an error from SSF to SCF, indicating the fact that the establishment of a temporary connection to an assisting SSF or SRF was not successful (e.g. receiving a "Backwards Release" after sending the IAM).

7.2.2.4.2 Operations SCF->SSF

EstablishTemporaryConnection
Procedures at invoking entity (SCF)
A) SCF sends ETC to SSF

precondition:	SCSM state 3.1	Determine Mode

postcondition:	SCSM state 3.2	Waiting for AssistRequestInstructions

B) SCF receives ETCFailed Error from SSF

precondition:	SCSM state 3.2	Waiting for AssistRequestInstructions

postcondition:	SCSM state 2.1	Preparing SSF Instructions

Error handling depends on the SL, e.g. selecting another SRF or continue the processing of the call.
Procedures at responding entity (SSF)
SSF receives ETC from SCF but the establishment of the connection fails, resulting in the returning of the ETCFailed Error to the SCF

precondition:	SSF FSM state c	Waiting for Instructions

postcondition:	SSF FSM state c	Waiting for Instructions

No further Error treatment.

7.2.2.5 ImproperCallerResponse

7.2.2.5.1 General description

7.2.2.5.1.1 Error description

The format of the user input has been checked by the SRF and does not correspond to the required format as it was defined in the initiating P&C Operation.

7.2.2.5.2 Operations SCF->SRF

PromptAndCollectUserInformation
Procedures at invoking entity (SCF)
A) SCF sends P&C to SRF

precondition:	SCSM state 3.1	Determine Mode; P&C will accompany the ConnectToResource

	or 	SCSM state 3.2	Waiting for AssistRequestInstructions; after EstablishTemporaryConnection

	or 	SCSM state 4.1	Waiting for Response from the SRF; if more PAs or P&Cs are active.

postcondition:	SCSM state 4.1	Waiting for Response from the SRF

B) SCF receives ImproperCallerResponse Error from SRF

precondition:	SCSM state 4.1	Waiting for Response from the SRF

postcondition:	SCSM state 4.1	Waiting for Response from the SRF

Error treatment depends on SL. SCF can initiate new User Interaction or forcing a Disconnect (to SSF).
Procedures at responding entity (SRF)
A) SRF receives P&C

precondition:	SRSM state 2	Connected

	or	SRSM state 3	User Interaction

postcondition:	SRSM state 3	User Interaction

B) response from caller is not correct, SRF returns ImproperCallerResponse to SCF

precondition:	SRSM state 3	User Interaction

postcondition:	SRSM state 3	User Interaction

SRF waits for a new Operation from SCF. This may be a new P&C or PA.

7.2.2.6 MissingCustomerRecord

7.2.2.6.1 General description

7.2.2.6.1.1 Error description

The SLP could not be found in the SCF, because the required customer record does not exist, or the requested SLPI, indicated by correlationID in "AssistRequestInstructions" does not exist anymore.

7.2.2.6.2 Operations SSF->SCF

AssistRequestInstructions
InitialDP
Procedures at invoking entity (SSF)
A) Sending Operation

precondition:	SSF FSM state b	Trigger processing

	or	SSF FSM state b' 	Waiting for Instructions; in case of assist/hand-off

postcondition:	SSF FSM state c	Waiting for Instructions

	or	SSF FSM state b' 	Waiting for Instructions; in case of assist/hand-off

B) SSF receives Error "MissingCustomerRecord"

precondition:	SSF FSM state c	Waiting for Instructions

	or	SSF FSM state b' 	Waiting for Instructions; in case of assist/hand-off

postcondition:	SSF FSM state a	Idle

	or	SSF FSM state a' 	Idle; in case of assist/hand-off

The CCF routes the call if necessary (e.g. default routing to a terminating announcement).
Procedures at responding entity (SCF)
The SCSM detects that the required SLP does not exist. The SLPI may not exist anymore (e.g. in case of the operation AssistRequestInstructions), or the SLP may have never existed at all (i.e. the customer record in the SCF does not exist, e.g. in case of TDPs a SLP is attempted to be invoked). The Error parameter MissingCustomerRecord is used to inform the invoking entity of this situation. The maintenance functions are informed.

7.2.2.6.3 Operations SRF->SCF

AssistRequestInstructions
Procedures at invoking entity (SRF)
A) Sending Operation

precondition:	SRSM state 2	Connected

postcondition:	SRSM state 2	Connected

B) SRF receives Error "MissingCustomerRecord"

precondition:	SRSM state 2	Connected

postcondition:	SRSM state 1	Idle

SRF initiated Disconnect.
Procedures at responding entity (SCF)
The SCSM detects that the required SLP does not exist (anymore). The establishment of a connection between the SSF and the SRF took too long or the correlationID was invalid. In both cases the requested SLP cannot be found. The Error parameter MissingCustomerRecord is used to inform the invoking entity of this situation. The maintenance functions are informed.

7.2.2.7 MissingParameter

7.2.2.7.1 General description

7.2.2.7.1.1 Error description

There is an Error in the received Operation argument. The responding entity cannot start to process the requested Operation because the argument is incorrect: an expected optional parameter which is essential for the application is not included in the Operation argument.

7.2.2.7.2 Operations SCF->SSF

Non Call Associated
ActivateServiceFiltering

Call Associated/Non Call Processing

ApplyCharging	CallInformationRequest

FurnishChargingInformation	RequestNotificationChargingEvent

RequestReportBCSMEvent	ResetTimer

SendChargingInformation

Call Associated/Call Processing

Connect	ConnectToResource

EstablishTemporaryConnection	InitiateCallAttempt

CollectInformation
Procedures at invoking entity (SCF)
A) Sending Operation

precondition:	SCSM	any state in which the above operations can be transferred.

postcondition:	SCSM	any state as result of the transfer of any of the above operations

B) SCF receives Error "MissingParameter"

precondition:	SCSM	any state as result of the transfer of any of the above operations.

postcondition:	SCSM	transition to the initial state (i.e. before sending the erroneous operation).

The SL and maintenance functions are informed. Further treatment of the call is dependent on SL.
Procedures at responding entity (SSF)

precondition:	(1) SSF FSM	appropriate state.

		(2) SSF FSM	Operation received, appropriate event occurred.

postcondition:	(1) SSF FSM	transition to the same state.

The SSF FSM detects the error in the received operation. The Error parameter is returned to inform the SCF of this situation.

7.2.2.7.3 Operations SSF->SCF

AssistRequestInstructions
InitialDP
ApplyChargingReport
Procedures at invoking entity (SSF)
A) Sending Operation

precondition:	SSF FSM	any state in which the above operations can be transferred.

postcondition:	SSF FSM	any state as result of the transfer of any of the above operations

B) SSF receives Error "MissingParameter"
precondition: SSF FSM any state as result of the transfer of any of the above operations.

postcondition:	SSF FSM state a	Idle

After receiving this Error, the SSF FSM returns to the state Idle, the CCF routes the call if necessary (default routing to a terminating announcement). If the call is already established (i.e. mid-call trigger or ApplyChargingReport), the CCF may maintain the call or disconnect it. The choice between these two options is network operator specific. In case of an assisting SSF, the temporary connection is released by the assisting SSF.
Procedures at responding entity (SCF)

precondition:	(1) SCSM	appropriate state.

	(2) SCSM	Operation received, appropriate event occurred.

postcondition:	(1) SCSM state 1	Idle; in case of InitialDP or ApplyChargingReport.

	or	(2) SCSM state 2.1	Preparing SSF Instructions; in case of AssistRequestInstructions.

The SCSM detects the erroneous situation. The Error parameter is used to inform the SSF of this situation. The SL and maintenance functions are informed.

7.2.2.7.4 Operations SCF->SRF

PlayAnnouncement
PromptAndCollectUserInformation
Procedures at invoking entity (SCF)
A) Sending Operation

precondition:		SCSM state 3.1	Determine Mode; P&C or PA will accompany the ConnectToResource

	or 	SCSM state 3.2	Waiting for AssistRequestInstructions; after EstablishTemporaryConnection

	or 	SCSM state 4.1	Waiting for Response from the SRF; if more PAs or P&Cs are outstanding.

postcondition:	SCSM state 4.1	Waiting for Response from the SRF

B) Receiving Error

precondition:	SCSM state 4.1	Waiting for Response from the SRF

postcondition:	SCSM state 4.1	Waiting for Response from the SRF

Error treatment depends on SL. SCF can initiate new User Interaction or force Disconnect (to SSF).
Procedures at responding entity (SRF)

precondition:	SRSM state 2	Connected

	or SRSM state 3	User Interaction

postcondition:	SRSM state 3	User Interaction

The SRSM detects that a required parameter is not present in the Operation argument. The Error parameter MissingParameter is used to inform the SCF of this situation. The SCF should take the appropriate actions to treat this error.

7.2.2.7.5 Operations SRF->SCF

AssistRequestInstructions
Procedures at invoking entity (SRF)
A) Sending Operation

precondition:	SRSM state 2	Connected

postcondition:	SRSM state 2	Connected

B) Receiving Error

precondition:	SRSM state 2	Connected

postcondition:	SRSM state 1	Idle

Procedures at responding entity (SCF)

precondition:	SCSM state 3.2	Waiting for ARI

postcondition:	SCSM state 2.1 	Preparing SSF instructions

The SCSM detects the error in the received operation. The Error parameter is used to inform the SRF of this situation. The SL and maintenance functions are informed. The SCF might try another SRF, route the call or release the call (SL dependent).

7.2.2.9 ParameterOutOfRange

7.2.2.9.1 General description

7.2.2.9.1.1 Error description

The responding entity cannot start the processing of the requested Operation because an Error in a parameter of the Operation argument is detected: a parameter value is out of range.
All errors, which can be detected by the ASN.1 decoder, already may be detected during the decoding of the TCAP message and indicated by the TC error indication "MistypedParameter".

7.2.2.9.2 Operations SCF->SSF

Non Call Associated
ActivateServiceFiltering

Call Associated/Non Call Processing
ApplyCharging
CallInformationRequest
SendChargingInformation
Refer to subclause 7.2.2.7 for the appropriate error procedures.

7.2.2.9.3 Operations SSF->SCF

ApplyChargingReport
Refer to subclause 7.2.2.7 for the appropriate error procedures.

7.2.2.11 RequestedInfoError

7.2.2.11.1 General description

7.2.2.11.1.1 Error description

The RequestedInfoError is an immediate response to the CallInformationRequest operation, indicating that the requested information is not known to the SSF or is not available.

7.2.2.11.1.2 Argument description

PARAMETER ENUMERATED {

	unknownRequestedInfo(1),

	requestedInfoNotAvailable(2)

7.2.2.11.2 Operations SCF->SSF

CallInformationRequest
Refer to subclause 7.2.2.7 for the appropriate error procedures.

7.2.2.14 SystemFailure

7.2.2.14.1 General description

7.2.2.14.1.1 Error description

This error is returned by a PE if it was not able to fulfil a specific task as requested by an operation, and recovery is not expected to be completed within the current call instance.

7.2.2.14.1.2 Argument description

PARAMETER

	UnavailableNetworkResource

UnavailableNetworkResource ::= ENUMERATED {

	unavailableResources (0),

	componentFailure (1),

	basicCallProcessingException (2),

	resourceStatusFailure (3),

	endUserFailure (4)}

7.2.2.14.2 Operations SCF->SSF

Non Call Associated
ActivateServiceFiltering

Call Associated/Non Call Processing

ApplyCharging	CallInformationRequest

RequestNotificationChargingEvent	RequestReportBCSMEvent

SendChargingInformation

Call Associated/Call Processing

CollectInformation	Connect

ConnectToResource	DisconnectForwardConnection

EstablishTemporaryConnection	InitiateCallAttempt

Refer to subclause 7.2.2.7 for the appropriate error procedures.

7.2.2.14.3 Operations SSF->SCF

InitialDP
ApplyChargingReport
Refer to subclause 7.2.2.7 for the appropriate error procedures.

7.2.2.14.4 Operations SCF->SRF

PlayAnnouncement
PromptAndCollectUserInformation
Refer to subclause 7.2.2.7 for the appropriate error procedures.

7.2.2.15 TaskRefused

7.2.2.15.1 General introduction

7.2.2.15.1.1 Error description

This Error is returned by a PE if it was not able to fulfil a specific task as requested by an operation, and recovery is expected to be completed within the current call instance.

7.2.2.15.1.2 Argument description

PARAMETER ENUMERATED {

	generic(0),

	unobtainable (1),

	congestion (2)

7.2.2.15.2 Operations SCF->SSF

Non Call Associated
ActivateServiceFiltering

Call Associated/Non Call Processing

ApplyCharging	CallInformationRequest

FurnishChargingInformation	RequestNotificationChargingEvent

RequestReportBCSMEvent	ResetTimer

SendChargingInformation

Call Associated/Call Processing

CollectInformation	Connect

ConnectToResource	DisconnectForwardConnection

EstablishTemporaryConnection	InitiateCallAttempt

Refer to subclause 7.2.2.7 for the appropriate error procedures.

7.2.2.15.3 Operations SSF->SCF

AssistRequestInstructions
InitialDP
ApplyChargingReport
Refer to subclause 7.2.2.7 for the appropriate error procedures.

7.2.2.15.4 Operations SCF->SRF

PromptAndCollectUserInformation
Refer to subclause 7.2.2.7 for the appropriate error procedures.

7.2.2.15.5 Operations SRF->SCF

AssistRequestInstructions
Refer to subclause 7.2.2.7 for the appropriate error procedures.

7.2.2.16 UnavailableResource

7.2.2.16.1 General description

7.2.2.16.1.1 Error description

The SRF is not able to perform its function (i.e. play a certain announcement and/or collect specific user information), and cannot be replaced. A reattempt is not possible.

7.2.2.16.2 Operations SCF->SRF

PlayAnnouncement
PromptAndCollectUserInformation
Procedures at invoking entity (SCF)
A) SCF sends PA or P&C to SRF

precondition:	SCSM state 3.1	Determine Mode; PA or P&C will accompany the ConnectToResource

	or	SCSM state 3.2	Waiting for AssistRequestInstructions; after EstablishTemporaryConnection

	or	SCSM state 4.1	Waiting for Response from the SRF; if more PAs or P&Cs are outstanding.

postcondition:	SCSM state 4.1	Waiting for Response from the SRF

B) SCF receives UnavailableResource Error from SRF

precondition:	SCSM state 4.1	Waiting for Response from the SRF

postcondition:	SCSM state 4.1	Waiting for Response from the SRF

If the chosen resource cannot perform its function the further treatment is service dependent.

EXAMPLE:	-	request SSF to connect to alternative SRF;	
-	service processing without PA or P&C (if possible);	
-	terminate service processing.

Procedures at responding entity (SRF)
A) SRF receiving PA or P&C

precondition:	SRSM state 2	Connected; if initial PA or P&C

	or	SRSM state 3	User Interaction; if not initial PA or P&C

B) SRF is not able to perform its function (and cannot be replaced). SRF sends UnavailableResource.

precondition:	SRSM state 3	User Interaction

postcondition:	SRSM state 3	User Interaction

7.2.2.17 UnexpectedComponentSequence

7.2.2.17.1 General description

7.2.2.17.1.1 Error description

The responding entity cannot start the processing of the requested operation because a SACF or MACF rule is violated, or the operation could not be processed in the current state of the FSM.

7.2.2.17.2 Operations SCF->SSF

Non Call Associated
ActivateServiceFiltering

Call Associated/Non Call Processing

ApplyCharging	CallInformationRequest

FurnishChargingInformation	RequestNotificationChargingEvent

RequestReportBCSMEvent	ResetTimer

SendChargingInformation

Call Associated/Call Processing

CollectInformation	Connect

ConnectToResource	Continue

DisconnectForwardConnection	EstablishTemporaryConnection

InitiateCallAttempt

In this case the SSF detects the erroneous situation, sends the UnexpectedComponentSequence error and remains in the same state. In the SCF the SL and maintenance functions are informed and the SL decides about error treatment.

7.2.2.17.3 Operations SSF->SCF

ApplyChargingReport
AssistRequestInstructions
InitialDP
In case of assisting SSF an error occurs in case an AssistRequestInstructions is sent while a relationship between SCF and assisting SSF has already been established. In that case the SCF returns the error parameter. SL and maintenance are informed. On receiving the error the assisting SSF moves to Idle and the temporary connection is released.
In case the operation is sent by an "initiating" SSF in the context of an existing relationship, the SCF returns the error parameter. SL and maintenance are informed. On receiving the error the SSF moves to Idle.

7.2.2.17.4 Operations SCF->SRF (only applicable for direct SCF-SRF case)

PlayAnnouncement
PromptAndCollectUserInformation
In this case the SRF detects the erroneous situation, sends the UnexpectedComponentSequence error and remains in the same state. In the SCF the SL and maintenance functions are informed and the SL decides about error treatment. Possible error treatment is to send the DisconnectForwardConnection operation to the SSF.

7.2.2.17.5 Operations SRF->SCF

AssistRequestInstructions
In this case an error occurs if the SRF has already an established relationship with the SCF and for some reason sends a AssistRequestInstructions. The SCF detects the erroneous situation, informs SL and maintenance functions and returns the error parameter. On receiving the parameter the SRF moves to idle and releases the temporary connection.

7.2.2.18 UnexpectedDataValue

7.2.2.18.1 General description

7.2.2.18.1.1 Error description

The responding entity cannot complete the processing of the requested Operation because a parameter has an unexpected data value.
Note that this error does not overlap with "ParameterOutOfRange"

EXAMPLE:	startTime DateAndTime ::= -- value indicating January 32 1993, 12:15:01

	The responding entity does not expect this value and responds with "UnexpectedDataValue".

7.2.2.18.2 Operations SCF->SSF

Call Associated/Non Call Processing

ApplyCharging	FurnishChargingInformation

RequestNotificationChargingEvent	RequestReportBCSMEvent

ResetTimer

Call Associated/Call Processing

CollectInformation	Connect

ConnectToResource	EstablishTemporaryConnection

InitiateCallAttempt
Refer to subclause 7.2.2.7 for the appropriate error procedures.

7.2.2.18.3 Operations SSF->SCF

AssistRequestInstructions
InitialDP
ApplyChargingReport
Refer to subclause 7.2.2.7 for the appropriate error procedures.

7.2.2.18.4 Operations SCF->SRF

PlayAnnouncement
PromptAndCollectUserInformation
Refer to subclause 7.2.2.7 for the appropriate error procedures.

7.2.2.18.5 Operations SRF->SCF

AssistRequestInstructions
Refer to subclause 7.2.2.7 for the appropriate error procedures.

7.2.2.19 UnexpectedParameter

7.2.2.19.1 General description

7.2.2.19.1.1 Error description

There is an error in the received Operation argument. A valid but unexpected parameter was present in the Operation argument. The presence of this parameter is not consistent with the presence of the other parameters. The responding entity cannot start to process the Operation.

7.2.2.19.2 Operations SCF->SSF

Non Call Associated
ActivateServiceFiltering

Call Associated/Non Call Processing

ApplyCharging	CallInformationRequest

FurnishChargingInformation	RequestNotificationChargingEvent

RequestReportBCSMEvent	ResetTimer

SendChargingInformation

Call Associated/Call Processing

CollectInformation	Connect

ConnectToResource	EstablishTemporaryConnection

InitiateCallAttempt

Refer to subclause 7.2.2.7 for the appropriate error procedures.

7.2.2.19.3 Operations SSF->SCF

AssistRequestInstructions
InitialDP
ApplyChargingReport
Refer to subclause 7.2.2.7 for the appropriate error procedures.

7.2.2.19.4 Operations SCF->SRF

PlayAnnouncement
PromptAndCollectUserInformation
Refer to subclause 7.2.2.7 for the appropriate error procedures.

7.2.2.19.5 Operations SRF->SCF

AssistRequestInstructions
Refer to subclause 7.2.2.7 for the appropriate error procedures.

7.2.2.20 UnknownLegID

7.2.2.20.1 General description

7.2.2.20.1.1 Error description

This error is used to indicate to the SCF that a specific leg, indicated by the LegID">LegID parameter value in the operation, is unknown to the SSF.

7.2.2.20.2 Operations SCF->SSF

Call Associated/Non Call Processing
SendChargingInformation
Refer to subclause 7.2.2.7 for the appropriate error procedures.

7.2.3 Entity related error procedures

The following subclauses define the error handling for the entity related errors. Since the error situations are not originated by the reception of an operation, the invoking entity is denoted here as the entity at which the error situation is detected. The responding entity is the entity which receives the error report.
The TCAP services used for reporting errors are described in subclause 7.4.

7.2.3.1 Expiration of TSSF

7.2.3.1.1 General description

7.2.3.1.1.1 Error description

A timeout occurred in the SSF on the response from the SCF.

7.2.3.1.2 Procedures SSF->SCF

Procedure at the invoking entity (SSF)
Timeout occurs in SSF on TSSF

precondition:	SSF FSM state c	Waiting for instructions

	or	SSF FSM state d	Waiting for end of User Interaction

	or	SSF FSM state e	Waiting for end of Temporary connection

postcondition:	SSF FSM state a	Idle

The SSF FSM aborts the dialogue and moves to the Idle state, the CCF routes the call if necessary (e.g. default routing to a terminating announcement). The abort is reported to the maintenance functions.
Procedure at the responding entity (SCF)
SCF receives a dialogue abort

precondition:	Any state

postcondition:	SCSM state 1	Idle; if the abort is related to a SSF dialogue

	or	SCSM state 2	Preparing SSF instructions; if the abort is related to an assisting SSF dialogue

The SCF releases all allocated resources and reports the abort to the maintenance functions, if the abort is received on a SSF dialogue. The SCF releases all resources related to the dialogue, reports the abort to the maintenance functions and returns to state preparing SSF instructions, if the abort is received on an assisting SSF dialogue.

7.2.3.2 Expiration of TSRF

7.2.3.2.1 General Description

7.2.3.2.1.1 Error description

A timeout occurred in the SRF on the response from the SCF. This procedure concerns only the direct SCF-SRF case.

7.2.3.2.2 Procedures SRF->SCF

Procedure at the invoking entity (SRF)
Timeout occurs in SRF on TSRF

precondition:	SRSM state 2	Connected

	or	SRSM state 3	User Interaction

postcondition:	SRSM state 1	Idle

The SRF aborts the dialogue and moves to the Idle state, all allocated resources are de-allocated. The abort is reported to the maintenance functions.
Procedure at the responding entity (SCF)
SCF receives a dialogue abort

precondition:	SCSM state 4	User Interaction

postcondition:	SCSM state 2	Preparing SSF instructions

The SCF releases all resources related to the dialogue, reports the abort to the maintenance functions and returns to state preparing SSF instructions.

INAP Contents Page