In addition to the call flows described above, the following call flows describe some of the cases where CSI interworking can occur within the network on the terminating side.
Figure A.5 below shows a call flow for adding an IMS session (e.g. MSRP session) to an existing voice call. In this case the voice call was established with IMS origination, and the interworking is performed in the network. The addition of the IMS session is from the terminal that performed the IMS origination.
The S CSCF 2 of the originating network sends the RE INVITE message for the MSRP to the S CSCF 1 of the terminating network, in accordance with the already established sessions.
Figure A.6 shows a call flow for adding an IMS session (e.g. MSRP session) to an existing voice call. In this case the voice call was established with CSI origination, and the interworking is performed in the network. The addition of the IMS session is from the terminal that performed the CSI origination.
The flow below assumes that the CSI interworking was performed in the originating network.
The CSI AS1 generates a RE INVITE message within the existing dialogue towards UE2. This is returned to the S CSCF1. The RE INVITE contains the SDP for the original media (e.g. the audio) and the added media (e.g. MSRP).
Finally, the user plane for the MSRP is created. Note that the MSRP media could go through the CSI AS.
Figure A.7 shows a call flow for adding a voice call to an existing IMS session (e.g. MSRP session). In this case the original IMS session was established with CSI origination, and the interworking is performed in the network. The addition of the IMS session is from the terminal that performed the CSI origination.
The flow below assumes that the CSI interworking is performed in the originating network.
The gsmSCF invokes the CSI interworking Application's CAMEL Service that determines that the call needs to be interworked to IMS for CSI; thus, the CAMEL Service interworks the call to the IMS by allocating an IMRN and returning it to the gsmSCF; otherwise it responds with a CAP Continue.
The gsmSCF responds with a CAP Connect message containing the Original Called party ID and Destination Routing Address. Destination Routing Address contains the IMRN to route the call to the CSAF. Handling of Destination Routing Address and Original Called party ID is as defined in TS 23.078.
The MGCF initiates an INVITE towards the I CSCF in the home IMS of the originating CSI user. The calling party number and/or original called number are included in the INVITE if they are received from the PSTN call setup signalling (e.g. ISUP).
The I CSCF routes the INVITE based on one of the following standard procedures specified in "PSI based Application Server termination direct" and "PSI based Application Server termination - indirect" procedures in TS 23.228.
If, when the INVITE arrives at the CSI Interworking Application, it is processed by the CSAF of the CSI Interworking Application that may use the IMRN to retrieve the original called party number and the calling party number from the CAMEL Service. The CSAF uses the original called number and the calling party number to setup the outgoing call leg to party B in accordance with the AS origination procedure defined in clause 5.6.5 of TS 23.228.
The CSI AS forwards the RE INVITE to the IMS Core B. The CS part of the CSI session is now interworked to IMS Core B.
The rest of the call is established as per normal SIP signalling with interworking towards the CS domain. The voice call is considered to be established.