Step 1.
The SIP INVITE request is sent from the UE to S-CSCF#1 by the procedures of the originating flow. This message should contain the initial media description offer in the SDP.
Step 2.
S-CSCF#1 invokes whatever service logic is appropriate for this session attempt.
Step 3.
S-CSCF#1 performs an analysis of the destination address, and determines the network operator to whom the subscriber belongs. For S-S#1, this flow is an inter-operator message to the I-CSCF entry point for the terminating user. S-CSCF#1 forwards the INVITE request directly to I-CSCF#2, the well-known entry point into the terminating user's network
Step 4.
I-CSCF#2 (at the border of the terminating user's network) shall query the HSS for current location information.
Step 5.
HSS responds with the address of the current Serving-CSCF for the terminating user.
Step 6.
I-CSCF#2 forwards the INVITE request to the S-CSCF (S-CSCF#2) that will handle the session termination.
Step 7.
S-CSCF#2 invokes whatever service logic is appropriate for this session setup attempt
Step 8.
The sequence continues with the message flows determined by the termination procedure.
Step 9.
The media stream capabilities of the destination are returned along the signalling path, as per the termination procedure.
Step 10.
S-CSCF#2 forwards the SDP to I-CSCF#2
Step 11.
I-CSCF#2 forwards the SDP to S-CSCF#1.
Step 12.
S-CSCF#1 forwards the SDP to the originator, as per the originating procedure.
Step 13.
The originator decides on the offered set of media streams, confirms receipt of the Offer Response with a Response Confirmation, and forwards this information to S-CSCF#1 by the origination procedures. The Response Confirmation may also contain SDP. This may be the same SDP as in the Offer Response received in Step 12 or a subset.
Step 14-15.
S-CSCF#1 forwards the offered SDP to S-CSCF#2.
Step 16.
S-CSCF#2 forwards the offered SDP to the terminating endpoint, as per the termination procedure
Step 17-20.
The terminating end point acknowledges the offer with answered SDP and passes through the session path to the originating end point.
Step 21-24.
Originating end point acknowledges successful resource reservation and the message is forwarded to the terminating end point.
Step 25-28.
Terminating end point acknowledges the response and this message is sent to the originating end point through the established session path.
Step 29-32.
Terminating end point then generates ringing and this message is sent to the originating end point through the established session path.
Step 33-36.
Terminating end point then sends 200 OK via the established session path to the originating end point.
Step 37-40.
Originating end point acknowledges the establishment of the session and sends to the terminating end point via the established session path.