Here’s what the R-IM-SSF does when it gets messages from the IN:

IN message Action 
 InitialDP

Initial trigger for an IN-initiated call. See [1 Initial Triggering via the IN] for a detailed description of how the R-IM-SSF uses the information contained in the InitialDP and provisioned state to contact a SIP-AS.

 
 EventReportBCSM

An EventReportBCSM event causes the R-IM-SSF to send a message on the SIP dialog corresponding to the same call leg for which the event was reported. The actual SIP message sent depends on the reported event:

event message

abandon

CANCEL request for the INVITE, to the SIP-AS Any incoming SIP dialogs representing call legs (rather than user interaction requests) will also be terminated with a 487 Request Terminated final response

alerting

180 Alerting provisional response

busy

486 Busy Here final response

no answer

408 Request Timeout final response

not reachable

408 Request Timeout final response

route select failure

404 Not Found final response

answer

200 OK response

disconnect

BYE request

If the event report corresponds to a leg terminating event: then once the SIP dialog has been confirmed terminated in the R-IM-SSF by receipt of an ACK (for a final response) or 200 OK (for a BYE), then the R-IM-SSF will release the leg or call (as described when a CANCEL or BYE is received) if the call has not already been released.

 
 AssistRequestInstructions

Indicates the initiation of an SRF assisting dialog. A 200 OK response is sent by the R-IM-SSF on the SIP dialog that initiated the user interaction session.

 
 SpecializedResourceReport

Indicates the end of an announcement. A DisconnectForwardConnection request is sent by the R-IM-SSF on the IN dialog; and, if relevant, the SRF assisting dialog will be closed. A BYE request is also sent by the R-IM-SSF on the SIP dialog that initiated the user interaction.

 
 HoldResult +
ReconnectResult

The call leg was successfully held or resumed. A 200 OK response is sent by the R-IM-SSF on the corresponding SIP dialog.

 
 ReleaseCallPartyConnectionResult

The call leg was successfully disconnected. The corresponding SIP dialog has already terminated at this point, so no further action is necessary.

 
 OpenRefuse

This event only occurs for SIP network initiated calls in the case where the IN dialog created by the R-IM-SSF is not accepted by the MSC. A 503 Service Unavailable final response is sent on the SIP dialog that initiated the call.

 
 UserAbort +
ProviderAbort

  • When received for an IN-initiated call, depending on the current call state, a CANCEL or BYE is sent by the R-IM-SSF on the outgoing SIP dialog to the SIP-AS, and a 500 Internal Server Error final response or BYE is sent on any incoming SIP dialog from the SIP-AS.

  • When received for a SIP network initiated call, depending on the current call state, a 503 Service Unavailable final response or BYE request is sent by the R-IM-SSF on each incoming SIP dialog from the SIP-AS.

  • When received for an SRF assisting dialog, a BYE request is sent in the R-IM-SSF to the SIP-AS on the SIP dialog that initiated the user interaction session.

 
 OperationError

  • If a user error response relating to a ConnectToResource operation, a BYE request is sent by the R-IM-SSF on the SIP dialog that initiated the user interaction session. If user interaction was being performed using an assisting dialog, the assisting dialog is aborted and a DisconnectForwardConnection request is sent by the R-IM-SSF on the main IN dialog.

  • If a user error response indicating a PlayAnnouncement request has been cancelled, a DisconnectForwardConnection request is sent by the R-IM-SSF on the IN dialog; and, if relevant, the SRF assisting dialog will be closed. Announcement cancellation occurs because the SIP-AS terminated the SIP dialog initiating the user interaction session before the announcement had completed, so no further action is needed on this dialog.

  • If an error response relating to an InitiateCallAttempt operation, establishment of the new call leg failed and a 503 Service Unavailable final response is sent by the R-IM-SSF on the corresponding SIP dialog.

  • If an error response relating to a HoldCallPartyConnection or Reconnect operation, the a 500 Internal Server Error final response to the re-INVITE is sent by the R-IM-SSF on the corresponding SIP dialog.

  • If any other case, the R-IM-SSF aborts the call, and acts the same as if it received an abort message.
Previous page Next page