8.6.2 Behaviour of the gsmSSF in the process gsmSSF

03.783GPPCcustomized Applications for Mobile network Enhanced Logic (CAMEL) Phase 2Release 1998Stage 2TS

The following paragraphs give details on the behaviour of the gsmSSF in the process gsmSSF.

8.6.2.1 Actions of the gsmSSF on receipt of CAP_Request_Report_BCSM_Event (at the state Waiting_For_Instructions)

The gsmSSF arms the requested EDP, if the arming rules are fulfilled and returns to state Waiting_For_Instructions.

The gsmSCF may request the monitoring for any one or more Answer, Busy, No Answer, Abandon, Route Select Failure and Disconnect Event of a party in the call.

8.6.2.2 Actions of the gsmSSF on receipt of CAP_Continue (at the state Waiting_For_Instructions)

An Int_Continue is sent to request the GMSC/MSC to continue call set-up as originally requested.

8.6.2.3 Actions of the gsmSSF on receipt of CAP_Release_Call (at the state Monitoring)

When a control relationship exists between the gsmSCF and gsmSSF (at least one EDP-R is armed), the gsmSCF may spontaneously instruct the gsmSSF to release the call at any time using the Release Call IF. The Release Call IF shall not be sent from the gsmSCF if only monitor relationship exists between the gsmSSF and the gsmSCF.

8.6.2.4 Actions of the gsmSSF on receipt of Int_DP_T_Busy or Int_DP_T_No_Answer including the parameter CF (at the state Monitoring)

If the handling of Int_DP_T_Busy or Int_DP_T_No_Answer including the parameter CF leads to the gsmSSF sending a CAP_Event_Report_BCSM to the gsmSCF, the gsmSSF shall include the parameter Call Forwarded as the Event Specific Information BCSM.