Code : STM#340-3 Samsung Electronics Co., Ltd. How to Trace ? Distribution EnglishED01

© Samsung Electronics Co., Ltd. 2 Objectives After successful completion of the course the trainees should be able to execute the following activities.

© Samsung Electronics Co., Ltd. 3 OpenTSP Trace Mode None / Type 1 / Type 2 Set to Type 2 How to change the Trace Mode of OpenTSP By Control Panel By Config Tool

© Samsung Electronics Co., Ltd. 4 Trace Tool DBGView.exe TB20.exe / OfficeServ Call Source Insight / Edit Tool

© Samsung Electronics Co., Ltd. 5 DBGView.exe Common Debug Tool for Samsung CTI S/W(OpenTSP/Call/Operator/Etc) See the Doc File(HowToUseDBGView.doc)

© Samsung Electronics Co., Ltd. 6 Tapi Browser TAPI based Call Control Tool You can use most of tapi functions with this tool on OpenTSP See the Doc File (HowToUseTB.doc)

© Samsung Electronics Co., Ltd. 7 Other Tools Tapi Sampler OpenTSP Self Test Tool. Text Editor Tool You can use text editor for analyzing the trace log file. Recommend you to use tools that have the more powerful edit features like source insight

© Samsung Electronics Co., Ltd. 8 How to make trace log file Change the OpenTSP Trace Type Run DBGView.exe Set the option value of DBGView Time / History Depth / Log To File etc Start Capturing of Trace Log Test the error case or Wait until detecting error case by using application or physical device Stop Capturing and save it(or Stop Log to File etc) Analyze this captured trace file

© Samsung Electronics Co., Ltd. 9 Lab 3 : Make a Trace Log File including the follwing cases OpenTSP StartUp Procedure MakeCall / Answer Call / Drop Call OpenTSP Shutdown Procedure Make a Trace Log File for another case By using Phone, Try to make a call for other cases. (Transfer, Hold, Retrieve, Conference, Forward, DND, Callback etc)

© Samsung Electronics Co., Ltd. 10 Basic Structure of Trace Log By internal threads of OpenTSP, each trace log message is displayed for representing its own functional result.

© Samsung Electronics Co., Ltd. 11 Trace Log Sample See the sample file. (CommonEvent.doc)

© Samsung Electronics Co., Ltd. 12 How To Analyze Error Case Describe the more detailed situation of error case Find “When, Which Line, What is problem ?” –When – It is very important data because this data can be used for finding the error point from the trace log file. –Which Line – can be used for tracing of error situation –What’s problem ? – can be used for finding the error effect Divide an error situation into the following 4 cases (possibility). Is it Application Side Error ? –This error is just only detected at 3 rd party application and at other software like TB20, this error is not detected. –Does it follow the TAPI and OpenTSP specification for processing its own function ? Is it TSP Side Error ? –This error is common to all cti softwares(3 rd party, TB20, Call etc) –TSP crashed or unexpected error detected. –Call State Mismatch detected between Application and Physical Device. –Stuck call generated. Is it Switch Side Error or Environment Error ? –there is no response from switch / Link –CTI Link goes down unexpectedly. Unknown case

© Samsung Electronics Co., Ltd. 13 Entering the trace log file Make the trace log file more simple Use more powerful edit tool like “source insight” than “Windows Text Editor” Abstract the OpenTSP log from the exising log file.(based on ProcessID or DeviceID or etc) Abstract the core log case including the error situation Try to find out where is the wrong point Trace each log case by using the device no, call state Compare the error case with the expected case or the normal case

© Samsung Electronics Co., Ltd. 14 Lab 4 : Analyze Log File. Case 1 : Event Missing by Switch Voice Record Off Event is not delivered. See Sample Log File (2-VoiceRecording) Case 2 : TSP Error Case Call State Mismatch between application and real phone. See Sample Log File (3-Mismatch)

Samsung Electronics Co., Ltd.