Volte Call Drop For Training_0307

  • Uploaded by: shaikh
  • 0
  • 0
  • January 2021
  • PDF

This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA


Overview

Download & View Volte Call Drop For Training_0307 as PDF for free.

More details

  • Words: 751
  • Pages: 15
Loading documents preview...
CLOT Issue Analyzing (VoLTE Call Drop)

7.Mar, 2015 Joohyun,Kim

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 “Bye” message ‐ 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

© SAMSUNG Electronics Co., Ltd. Confidential and Proprietary

1

Case Study-1(VoLTE Call Drop) ■

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 didn’t receive the “183 session progress

500 Server Internal Error

Case Study-2(VoLTE Call Drop) ■ 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 “Bye” message

500 Server Internal Error 15 minutes period

Case Study-3(VoLTE Call Drop) ■ Call Drop was caused by end by user •

Call drop was caused by end By user — This is not KPI fail about this case

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

© SAMSUNG Electronics Co., Ltd. Confidential and Proprietary

5

Case Study-4(Drop-Bye)  CLUSTER TN-EROD-0037_VOL-ISSUE LOG(VoL) •

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

© SAMSUNG Electronics Co., Ltd. Confidential and Proprietary

6

Case Study-4(Drop-Bye)  CLUSTER TN-EROD-0037_VOL-ISSUE LOG(VoL) •

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

© SAMSUNG Electronics Co., Ltd. Confidential and Proprietary

7

Summary_Case Study-5(BR-RNCH-0258) 

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

© SAMSUNG Electronics Co., Ltd. Confidential and Proprietary

Issue CLOT(BR-RNCH-0258) 

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

© SAMSUNG Electronics Co., Ltd. Confidential and Proprietary

Issue CLOT(BR-RNCH-0258) 

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

© SAMSUNG Electronics Co., Ltd. Confidential and Proprietary

Issue CLOT(BR-RNCH-0258) 

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

© SAMSUNG Electronics Co., Ltd. Confidential and Proprietary

Issue CLOT(BR-RNCH-0258) 

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

© SAMSUNG Electronics Co., Ltd. Confidential and Proprietary

Appendix(SIP Response Table) 

Server error Code 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

© SAMSUNG Electronics Co., Ltd. Confidential and Proprietary

13

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.

Related Documents

Volte Analysis.pdf
January 2021 1
Drop Box
January 2021 2
Call Data
March 2021 0

More Documents from "jto 09"