volte call drop for training_0307

7/26/2019 VoLTE Call Drop for Training_0307

1/15

CLOT Issue Analyzing

(VoLTE Call Drop)

7.Mar, 2015

Joohyun,Kim


2/15

Summary-Case Study-1/2/3

Cluster_AP-TNDR-0236-C2(VoL)

Key VoLTE Drop

Call drop was caused by Mobile to Server test scenario(known issue) By server setting, every 15 minutes, UE could have call drop by no-RTP

This is not KPI fail, but UE should have Byemessage

If there are call drop for VoLTE call attach in VoL UE, this is call drop(Refer to Next Slide)

Call Drop was caused by end by user

This is not KPI fail

Call Drop was caused by 500 Server internal error

Server Internal Error 5xx responses are failure responses given when a server itself has

erred

AP-TDNR-0236-C2 Call drop summary

1 SAMSUNG Electronics Co., Ltd. Confidential and Proprietary


3/15

Cause of Failure(Code 500 error)

For VoLTE Attach , Call drop happened by SIP Fail cause Code 500

Code 500 : Server Internal Error 5xx responses are failure responses given when a server itself has erred

UE didnt receive the 183 session progress

Case Study-1(VoLTE Call Drop)

500 Server Internal Error


4/15

Call drop by serve call scenario

Call drop was caused by Mobile to Server test scenario(known issue)

By server setting, every 15minute, UE could have call drop by no-RTP

This case is not KPI fail , but UE, UE should send the Byemessage


500 Server Internal Error

15 minutes period


5/15

Call Drop was caused by end by user

Call drop was caused by end By user

This is not KPI fail about this case



6/15

Summary_Case Study-4(Drop-Bye)

CLUSTER TN-EROD-0037_VOL-ISSUE LOG(VoL)

Why there are happened like Drop-Bye

Call drop was caused by User disconnected call by screen or ear phone button. It is not KPI Fail

Below is the event situation by tester

1st : User disconnected call by screen or ear phone button

2nd : User stopped Smart DM



7/15

Case Study-4(Drop-Bye)


Why there are happened like end by user

Call drop was caused by end by user from user stopped smart DM. It is not KPI Fail

Below is the event situation by tester

1st : User stopped Smart DM

2ND : Smart DM Automatically disconnected call


End By User


8/15

Case Study-4(Drop-Bye)


During the test, there was some other call from other UE

Event through, test UE is MO but MO UE received Rx-invite Msg form other UE It is strange situation



9/15

Summary_Case Study-5(BR-RNCH-0258)

SAMSUNG Electronics Co., Ltd. Confidential and Proprietary

After sending the 100 Trying Message, UE receive the SIP 200 OK lately

During the issue time, signal is good and RLC Layer is normal

In abnormal case, time between 100 trying and QCI 1 Bearer with 183 session progress is

more than 20000ms

In this event time is only depend on IMS core side


10/15

Issue CLOT(BR-RNCH-0258)

In abnormal case, time between 100 trying and QCI 1 Bearer with 183 session progress is more

than 20000ms



11/15


During the issue time, signal is good and RLC Layer is normal



12/15


During the issue time, There is only depend on IMS core side



13/15

Issue CLOT(BR-RNCH-0258) During the issue time, There is only depend on IMS core side



14/15

Server error Code

Appendix(SIP Response Table)


Error Code Contents

500 Internal Server Error

501 Not Implemented

502 Bad Gateway

503 Service Unavailable

504 Server Timeout

505 SIP Version Not Supported

513 Message Too Large


15/15

Copyright and Confidentiality

Copyright 2014 SAMSUNG Electronics Co., Ltd. SAMSUNG Electronics reserves the right to make changes to the specifications

of the products detailed in this document at any time without notice and obligation to notify any person of such changes.

Information in this document is proprietary to SAMSUNG Electronics Co., Ltd. No information contained here may be copied,

translated, transcribed or duplicated by any form without the prior written consent of SAMSUNG Electronics.

volte call drop for training_0307

Documents