Orig P-CSCF Interfaces (Caller and Called are IMS Subscribers)

Calling UE IMS Network Called UE

EventStudio System Designer 4.0
Caller User Visited IMS 1 Home IMS 1 Home IMS 2 Called User
Equipment Equipment
15-Dec-07 08:21 (Page 1)
Caller Orig P-CSCF Orig S-CSCF Term I-CSCF Term S-CSCF Term P-CSCF Called
IMS Routing of Initial SIP INVITE
INVITE The SIP phone sends the invite to
INVITE called@hims2.net SIP/2.0,
called@hims2.net. The message contains
P-Preferred-Identity: Route entries for the terminal and the S-CSCF
<caller@hims1.net>,
Via: <Calling UE IP> :Port,
address that was extracted from the
Route: <P-CSCF address>, Service-Route header in the registration "200
Route: <S-CSCF address>,
Contact: <Calling UE IP> :Port,
OK" message. Security ports setup for IPSec
SDP: <Caller Supported Codec List> SA establishment are used. "To" and "From"
headers are also included in the message.
These headers do not play a role in call
processing.
Make sure that INVITE was received over the The INVITE was sent using the registration
IPSec Security Association time SA so the P-CSCF accepts the request.
Make sure that the preferred public identity is P-CSCF verifies that the preferred public
currently registered identity specified in the INVITE is currently
registered.
The S-CSCF address for the user was obtained
at the time of registration (Service-Route
header in the "200 OK" response to the
REGISTER message.)
Use DNS to translate from scscf1.hims1.net to The originating P-CSCF queries the DNS to
'Orig S-CSCF' IP address obtain the IP address of the S-CSCF in the
called subscriber's home network. The
S-CSCF address for the user was obtained at
the time of registration (Service-Route header
in the "200 OK" response to the REGISTER
message).
INVITE The P-CSCF replaces the preferred identity
INVITE called@hims2.net SIP/2.0,
header with the asserted identity header and
P-Asserted-Identity: forwards the message to the S-CSCF in the
<caller@hims1.net>,
Via: <Orig P-CSCF> <Calling-UE>,
home network. It adds a Record-Route header
Record-Route: <Orig P-CSCF>, with its own address.
Route: <Orig S-CSCF>,
Contact: <Calling UE IP> :Port,
SDP: <Caller Supported Codec List>

100 Trying The P-CSCF just acknowledges the INVITE to

the UE. The "100 Trying" message indicates
that the call setup is in progress.
100 Trying The S-CSCF acknowledges the INVITE that
was received from P-CSCF.
IMS Routing of First Response to the SIP Invite
183 Session Progress
Via: <Orig P-CSCF> <Calling-UE>,
Record-Route: <Term S-CSCF> <Orig
S-CSCF> <Orig P-CSCF>,
SDP: <Codecs supported by Caller
and Called>

Obtain a media authorization token from the The originating P-CSCF requests the Policy
PDF Decision Function (PDF) to generate a media
authorization token. The token will be included
Orig P-CSCF Interfaces (Caller and Called are IMS Subscribers)
Calling UE IMS Network Called UE
EventStudio System Designer 4.0
Caller User Visited IMS 1 Home IMS 1 Home IMS 2 Called User
Equipment Equipment
15-Dec-07 08:21 (Page 2)
Caller Orig P-CSCF Orig S-CSCF Term I-CSCF Term S-CSCF Term P-CSCF Called
in the "183 Session Progress" sent to the
originating UE.
183 Session Progress Just like other nodes, the Orig P-CSCF
Via: <Calling-UE>,
removes its own entry from the Via header.
Record-Route: <Term S-CSCF>;port The P-CSCF also updates the Record-Route
<Orig S-CSCF> <Orig P-CSCF>,
SDP: <Codecs supported by Caller
header to include the protected port number in
and Called>, its entry. This forces the terminal to send all
P-Media-Authorization responses using the protected IPSec SA. The
message also includes the media authorization
token. This token will have to be passed to the
GGSN in the PDP context activation request.
PDP Context Activation and Audio/Video Path Setup
PRACK PRACK The Caller now sends a PRACK to inform the
SDP: <Selected Codec>, SDP: <Selected Codec>,
called subscriber about the selected Codec.
<Local-QOS: none> <Local-QOS: none> The message also indicates that currently the
resources needed for meeting the quality of
service requiements of the session are not
available.
200 OK 200 OK The called subscriber acknowledges the
SDP: <Selected Codec>, SDP: <Selected Codec>,
PRACK. The message also indicates that
<Local-QOS: none> <Local-QOS: none> quality of service for the session is not met for
the called subscriber.
UPDATE UPDATE Since the caller PDP context has been
SDP: <Local-QOS: SDP: <Local-QOS:
activated, notify the called end that the caller
sendrecv> sendrecv> can now meet the quality of service in the
send and receive direction.
200 OK 200 OK The caller replies back to the called user. Note
SDP: <Local-QOS: none> SDP: <Local-QOS: none>
that the Local QoS is still set to none as the
called PDP context activation has not been
completed.
180 Ringing 180 Ringing Inform the caller that the called subscriber is
being rung. This serves as an implicit
indication to the caller that the QoS at the
called side has also been met.
PRACK PRACK The caller acknowledges the ringing message.

200 OK 200 OK The called subscriber acknowledges the

PRACK.
200 OK 200 OK Notify the caller that that the call has been
answered.
ACK ACK The caller acknowledges the "200 OK"
message. The call is now ready to enter
conversation mode.