Application Server Responses Sample Clauses
Application Server Responses. Where the Application Server acts as a proxy or B2BUA then the session will continue with an INVITE being sent back from the Application Server to the S-CSC (or SB/SCIM). The actions taken on responses to the INVITE sent to the Application Server are described below.
Application Server Responses. If the REGISTER is received and accepted by the Application Server / SCIM then it MUST return a 200 OK response. The 200 OK response will include the same value in the Expires header as that received in the the REGISTER. Should no response be received from the Application Server or an error response be returned to the REGISTER then the action of the S-CSC will be dependent upon the default handling defined in the initial filter criteria. If there is no defined default handling or the default handling is SESSION_CONTINUED then no further action is required. If the default handling is defined as SESSION_TERMINATED then the S-CSC will initiate a de-registration for all currently registered public user identities for the user. Where the Registration is propagated through the SB/SCIM then the SB/SCIM acts in the following way for Application Server Registration failures. ⮚ If no default handling is defined or the default handling defined in the SCIM service profile indicates SESSION_CONTINUED then no action is taken. ⮚ If the default handling defined in the SCIM service profile indicates SESSION_TERMINATED then the SB/SCIM will return an error response to the S-CSC (the same response returned by the failing Application Server, or 408 Request Timeout in the event of the Application Server returning no response) and perform a de-registration against any Application Servers for which the Registration has already been performed. This is shown in the Figure 8 below.