SIP FLOW

UE MME/SAE/PGW S-CSCF
Registration
Attach, Default Bearer setup, NAS Authentication, Integrity
Protection

1. UE Attaches to the network, the PGW assignes IP address

Activate EPS Bearer (QCI5) and DRB
and identifies P-CSCF to the terminal.
2. Terminal sets the IMEI and IMS communication identifier Activate EPS Bearer Accept (QCI5) and DRB

ICSI value Store P-CSCF IP

Address
3. UE sends Registration Request Message to IMS “S-
Extract user public
CSCF” (via P-CSCF) in REGISTER message identity from ISIM

4. S-CSCF performs registration procedures with HSS and Allocate client and
1
server ports
acquires user authentication information
5. IMS”S-CSCF” sends 401 Unauthorized message to UE REGISTER
Registration procedures
6. UE calculates the response and sends it to IMS”S- 2 with HSS

CSCF” in REGISTER message

401 Unauthorized:
7. After the authentication has succeeded the S-CSCF
downloads and stores service control information from Verify AUTN &

HSS
calculate RES
3
8. IMS”S-CSCF”sends 200 ok message to UE notifies the REGISTER

terminal about completed registration

Download service control
information from HSS

4
200 OK,

For internal use

2 ©2013 Nokia Solutions and Networks. All rights reserved.
 UE to UE VoLTE call flow MO IMS Network MT
Initiate call

INVITE

100 Trying
‘INVITE’ message indicates that a client is being invited to
participate in a call session. 183 Session Progress
INVITE
‘100 Trying’ message indicating that the call setup is in 200 OK
100 Trying
progress.
‘183 Session Progress’ response is used to convey 1 180 Ringing
Ringing

Information about the progress of the call that is not 200 OK (invite)
Answer

otherwise classified
ACK

2 EPS Bearer Activation for QCI1 and Audio Video Path

Setup

200 OK (invite)
ACK

3 EPS Bearer Activation for QCI1 and Audio Video Path

Setup

Voice or Video Session

BYE

200 OK
BYE

200 OK

For internal use

3 ©2013 Nokia Solutions and Networks. All rights reserved.
 Originating UE IMS Network Terminating UE
VoLTE call flow in NSN Smart Lab Initiate call
1
(using precondition mechanism) INVITE

100 Trying
2 OPTIONS
3
1. MO UE generates an INVITE request, which is sent to 200 OK

the IMS. 4 INVITE

100 Trying

2. The P-CSCF acknowledges the INVITE to the MO UE 183 Session Progress

with "100 Trying” message indicating that the call setup EPS Bearer Activation for QCI1 and Audio Video Path
Setup
is in progress. 183 Session Progress

PRACK
3. The SIP method OPTIONS allows a IMS to query EPS Bearer Activation for QCI1 and Audio Video Path
another UA or a proxy server as to its capabilities. This Setup

allows a client to discover information about the PRACK

supported methods, content types, extensions, codecs, 200 OK 200 OK

etc. UPDATE UPDATE

200 OK 200 OK

4. At MT UE the INVITE message contains: Session Ringing

Description Protocol (SDP) parameters: declaration for 180 Ringing 180 Ringing

using precondition, type of media, codec to use and the

200 OK 200 OK
protocol for transporting the media.
ACK ACK
For internal use
4 01/06/2024 Voice orreserved.
©2013 Nokia Solutions and Networks. All rights Video Session
 Originating UE IMS Network Terminating UE
xxNETWORK UE to UE VoLTE call Initiate call

– Originating INVITE INVITE

‘INVITE’ message indicates that a client is being invited to

participate in a call session.

The UE may initiate a session without the precondition

mechanism if the originating UE does not require local
resource reservation (UE has not indicated support or
requirement for preconditions in this call example).

- Preconditions require that the participant reserve network

resources (QoS) before continuing with the session.

For internal use

5 01/06/2024 ©2013 Nokia Solutions and Networks. All rights reserved.
 Originating UE IMS Network Terminating UE
xxNETWORK UE to UE VoLTE call Initiate call

-TRYING INVITE

100 Trying

The P-CSCF acknowledges the ‘INVITE’ to the UE with ‘100

Trying’ message indicating that the call setup is in progress.
This message is always sent by IMS to the client, i.e. it is
never forwarded upstream.

IETF: This response indicates that the request has been

received by the next-hop server and that some unspecified
action is being taken on behalf of this call (for example, a
database is being consulted). This response, like all other
provisional responses, stops retransmissions of an INVITE by a
UAC. The 100 (Trying) response is different from other
provisional responses, in that it is never forwarded upstream by
a stateful proxy.

For internal use

6 01/06/2024 ©2013 Nokia Solutions and Networks. All rights reserved.
 Originating UE IMS Network Terminating UE
xxNETWORK UE to UE VoLTE call Initiate call

- Session Progress INVITE

100 Trying
The ‘183 Session Progress’ response is used to convey
information about the progress of the call that is not 183 Session Progress

otherwise classified. The Reason-Phrase, header fields, or

message body MAY be used to convey more details about
the call progress.

After ‘183 Session Progress’ message is received the IMS

signalling (QCI 5) bearer may carry RTP audio packets, e.g.
voice announcement or music, to notify originating UE.

In case of precondition mechanism, P-CSCF would send ‘183

Session Progress’ to originating UE which then compares the
terminating UE capabilities with its own and determines the
codec to be used.

Precondition mechanism is not used in this example, i.e.

xxNETWORK IMS sends only one option (AMR-WB16000) and
requests the resources reserved accordingly. It does not request
to confirm when resources are reserved.
For internal use
7 01/06/2024 ©2013 Nokia Solutions and Networks. All rights reserved.
 Originating UE IMS Network Terminating UE
xxNETWORK UE to UE VoLTE call Initiate call

- Terminating INVITE INVITE

100 Trying
The P-CSCF updates the Via and Route-Record headers and
183 Session Progress
forwards the request to the Called UE. INVITE

Secure port is included in the Via address specification. The

message also includes the media authorization token which is
passed to the SAEGW in the PDP context activation request.

For internal use

8 01/06/2024 ©2013 Nokia Solutions and Networks. All rights reserved.
 Originating UE IMS Network Terminating UE
xxNETWORK UE to UE VoLTE call Initiate call

- Terminating TRYING INVITE

100 Trying
When the P-CSCF receives an initial INVITE request destined
for the UE, it will have a list of Record-Route header fields. 183 Session Progress
INVITE
Prior to forwarding the initial INVITE request, the P-CSCF
100 Trying
shall respond to all INVITE requests with a ‘100 Trying’
provisional response.

It should be noted that according to the specifications the

”100 Trying” message should only be sent by the P-CSCF to
an originating UE. However, the SIP client of terminating UE
(Samsung S4) is also sending the ”100 Trying” message to
the IMS in this call example.

Please note that the SIP client of LG G2 did not send ‘100
Trying’ message although both UEs have the same
Qualcomm chipset (MSM8974).

For internal use

9 01/06/2024 ©2013 Nokia Solutions and Networks. All rights reserved.
 Originating UE IMS Network Terminating UE
xxNETWORK UE to UE VoLTE call Initiate call

180 RINGING INVITE

100 Trying

‘180 Ringing’ message is trying to alert what the target UE

is received the ‘INVITE’ message. This response may be 183 Session Progress

used to initiate local ringback. INVITE

100 Trying
Please note that 180 Ringing’ message is NOT forwarded Ringing
by IMS to the originating UE in this example. However, 180 Ringing

NSN IMS is always forwarding ‘180 Ringing’ message.

PRACK and UPDATE messages are omitted as session

is NOT using precondition mechanism due to the support
is not indicated in UE originating ‘INVITE’ message.

If the terminating UE does not support the precondition

mechanism it will ignore any precondition information
received from the originating UE (TS 24.229 chapter
6.1.3).

‘ For internal use

10 01/06/2024 ©2013 Nokia Solutions and Networks. All rights reserved.
 Originating UE IMS Network Terminating UE
xxNETWORK UE to UE VoLTE call Initiate call

200 OK (INVITE) INVITE

100 Trying

Terminating UE sends ‘200 OK’ as the call is answered.

183 Session Progress

EPS bearer for QCI1 is activated once a terminating UE INVITE

has received ACK from IMS and thus, this completes the 100 Trying
INVITE/200 OK/ACK three-way handshake used to Ringing
establish SIP sessions at B-party. 180 Ringing

Answer
200 OK

ACK

EPS Bearer Activation for QCI1 and Audio Video Path

Setup

For internal use

11 01/06/2024 ©2013 Nokia Solutions and Networks. All rights reserved.
 Originating UE IMS Network Terminating UE
xxNETWORK UE to UE VoLTE call Initiate call

200 OK (invite) INVITE

100 Trying

Once originating UE receives 200 OK, it sends ACK to

IMS to complete SIP session establishment and 183 Session Progress

subsequently EPS bearer for QCI1 is activated - voice INVITE

communication starts. 100 Trying

Ringing
180 Ringing

Answer
200 OK

ACK

EPS Bearer Activation for QCI1 and Audio Video Path

Setup

200 OK

ACK

EPS Bearer Activation for QCI1 and Audio Video Path

Setup

Voice or Video Session

For internal use

12 01/06/2024 ©2013 Nokia Solutions and Networks. All rights reserved.
 Originating UE IMS Network Terminating UE
xxNETWORK UE to UE VoLTE call
Initiate call

Voice Session starts – RTP header contains the INVITE

information to terminating UE on which codec is used.

100 Trying
In this case it is AMR-WB (100) which corresponds to
AMR-WB16000 (23.85 kbps) 183 Session Progress

INVITE
xxNETWORK - Wireshark 1.8.4
Real-Time Transport Protocol 100 Trying
[Stream setup by SDP (frame 55)]
[Setup frame: 55] Ringing
[Setup Method: SDP] 180 Ringing
10.. .... = Version: RFC 1889 Version (2)
..0. .... = Padding: False Answer
...0 .... = Extension: False 200 OK
.... 0000 = Contributing source identifiers count: 0
1... .... = Marker: True ACK
Payload type: AMR-WB (100)
Sequence number: 245 EPS Bearer Activation for QCI1 and Audio Video Path
[Extended sequence number: 65781] Setup
Timestamp: 14068
Synchronization Source identifier: 0x0000f500 (62720) 200 OK
Adaptive Multi-Rate
Payload decoded as RFC 3267 ACK
1111 .... = CMR: No mode request (15)
EPS Bearer Activation for QCI1 and Audio Video Path
.... 0000 = Reserved: 0
Setup
Payload Table of Contents
0... .... = F bit: Last frame in this payload
.100 0... = FT bits: AMR-WB 23.85 kbit/s (8) Voice or Video Session
.... .1.. = Q bit: Ok

For internal use

13 01/06/2024 ©2013 Nokia Solutions and Networks. All rights reserved.
 •SIP FAILURE
•ERROR CODE

For internal use

14 01/06/2024 ©2013 Nokia Solutions and Networks. All rights reserved.
 • 1- 480”Temp unavailable/IMS not support” this issue mainly due to Missed pages
• In mobility and dense urban environments, the usual case is that the MT UE frequently misses the first and second page,
and finally the MT UE responds to the third page ,Since there is no response from the MT UE within 12 s (operator
configured) of the SIP invite message, the IMS network will send a SIP 480 (unreachable) to the MO UE.

• 2- 481”call transaction doesn’t request” this issue mainly due to BGF timer expire
• BGF monitors packets flow in both direction UL& DL if packet flow stop and BGF timer expire send release message.

• 3- 486”Busy here” this issue mainly due to MT out of connection.

• 4- 487”Request terminated” this issue mainly due to

• 1-bad coverage which lead to UE make INTERRAT-HO or TAU before QCI1 establish.
• 2-cancel message sends by MO or MT during call setup

• 5- 488”not acceptable here” this issue mainly due to

• invite message sent contain no codec or no common codec

• 6- 500”server internal error” this issue mainly due to

• PRAK message lost or subscriber data is not correct.

• 7- 502”Bad Gateway” this issue mainly due to

• server or gateway received invalid response from down stream server.

• 8- 503”service unavailable” this issue mainly due to

• eNB . Made ubnormal realse to UE due to lost or enb RLF timer expire
For internal use
•
15 01/06/2024 ©2013 Nokia Solutions and Networks. All rights reserved.
 •CALL SETUP TIME

For internal use

16 01/06/2024 ©2013 Nokia Solutions and Networks. All rights reserved.
 VoLTE Call Setup Time
Originating UE IMS Network
Terminating UE
Initiate call
INVITE 119 ms

100 Trying

606 ms

183 Session Progress

1527 ms

73 ms INVITE

100 Trying
60 ms
Ringing
3060 ms 180 Ringing
1275 ms (* call script delay)
Answer
152 ms 200 OK (invite)

MO= 3.9 sec ACK

EPS Bearer Activation for QCI1 and Audio Video Path Setup

200 OK (invite) 65 ms
ACK

EPS Bearer Activation for QCI1 and Audio Video Path Setup
MT=1.5 sec

Voice or Video Session

For internal use

17 ©2013 Nokia Solutions and Networks. All rights reserved.