8.19.33  
Maintenance | OpenStage Phones: Trace 
 
Use Trace to configure appropriate trace settings and transfer them to the
to be traced.telephone you want to trace. Trace data (trace profiles) can be downloaded from the telephone to the PC for logging and analysis (e.g. troubleshooting) after the trace routine.
The Trace function is only available on OpenStage 60 TDM and OpenStage 80 TDM telephones.
To access the Trace dialog, click the Trace button on the OpenStage Phones tab. Select the OpenStage TDM telephone you want to trace in the OpenStage drop-down list. Use the Selection table to define the Trace ID and, in the same line, the Trace Level required for the Trace ID. Then the flags and parameters in the Error Trace and Core Dump Configuration area can be activated (e.g. Delete Core Dump) and defined (e.g. trace duration Timeout (Minutes)). Use the PC -> Phone button to transfer the trace settings from the PC to the OpenStage TDM telephone you want to trace. You can now start tracing the stationary OpenStage TDM telephone, for example, with a call. When the trace finishes on the OpenStage TDM telephone, go to File Name and select the PC folder where you want to transfer the OpenStage TDM telephone's trace data for analysis (troubleshooting, for instance) on the PC. Use the Phone -> PC button to transfer the trace data to the PC folder. You can then forward the trace data to Administration/Development for analysis.

8.19.33.1  
Trace Area 

OpenStage  
This displays all active OpenStage TDM terminals. Open the drop-down list and select the OpenStage TDM telephone whose trace data (trace profiles) you want to transfer to the PC for analysis (troubleshooting, for instance) after the trace routine.

File Name  
Click Browse and select the PC folder (for example, C:\temp\OPERA\trace99.tar) where the OpenStage TDM telephone's trace profile (for example, binary data) should be transferred for analysis (troubleshooting, for instance).
Phone -> PC button:
Use this button to transfer an OpenStage TDM telephone trace to the PC folder that you selected under File Name.

8.19.33.2  
Trace-Process Area 
You can specify the components ( Trace-ID ) and Trace-Level for the trace process in the table here, transfer the trace settings from the PC to the selected OpenStage TDM telephone and perform the error trace and core dump configuration.

Selection  
The Selection table consists of the columns Trace-ID and Trace-Level. The software components for tracing a selected OpenStage TDM telephone can be chosen in the Trace-ID column. You can select the trace level (0 through 6) of the relevant software component for the trace routine in the Trace-Level column.
The following are descriptions of the software components listed in the Trace-ID column:

Trace-ID  
Meaning  
Administration  
This option is used to change and set user and administrator menu parameters in the telephone database.  
Application Framework  
All telephone applications (such as "Call View" and "Call Log") or the internal phonebook operate within the Application Framework. This component is responsible for switching between different applications and activating a required application.  
Application Menu  
Features options for starting and stopping applications.  
Bluetooth Service  
Is a service for managing Bluetooth connections between external Bluetooth devices and the telephone. Bluetooth is only available on HiPath OpenStage 60/80 telephones.  
Call Log  
Lets you display the telephone's "call history".  
Call View  
Lets you show calls on the display.  
Certificate Management  
Lets you verify and exchange security certificates.  
Communications  
Is involved in transferring call-specific information and signaling data to and from the CSTA service.  
Component Registrar  
Lets you register data associated with different telephone types (such as HFA/SIP telephones).  
CSTA Service  
Is a service for all possible CSTA messages. CSTA messages are used by all services in the telephone as "Common Call Progression" and "Control Protocol".  
Data Access Service  
Is a service that allows other services to access data in a telephone database.  
Desktop  
Is responsible for the display's individual views.  
These are mainly the status bar on top of the display and the FPK label.  
Digit Analysis Service  
Is a service for the analysis and modification of data streams that are sent and received via the telephone (for example, phone number conversion from canonical format into non-canonical format).  
Directory Service  
Is a service for comparing data such as the phone numbers of incoming and outgoing calls with entries in the internal phonebook.  
DLS Client Management  
Supports interaction with the DLS (Deployment and Licensing Service).  
Health Service  
The Health Service lets you:  
 •   monitor the telephone for diagnostic purposes
 •   provide a "logging interface" for other services in the telephone.
Help  
Provides the Help function.  
Instrumentation Service  
Is a service for exchanging telephone data for remote-control, testing, and monitoring purposes using the "Husim Phone Tester".  
Java  
Every Java application running on the telephone also operates in the "Java Sandbox", controlled by the Java Service.  
Journal Service  
Is a service for storing and accessing the "call history" information that is used by the "Call Log" application.  
Media Control Service  
Is a service for controlling "media streams" (voice, tones, ringer melodies, and so on) on the telephone.  
Media Processing Service  
Software layer between the "Media Control", "Tone Generation", and "Voice Engine" services. The "Media Processing Service" regulates changeover between audio devices, such as the handset and loudspeaker, for example.  
Mobility Service  
Is a service for logging on to different telephones and configuring these telephones based on the user's individual profile.  
OBEX Service  
This service enables the telephone's Bluetooth access. Bluetooth is only available on HiPath OpenStage 60/80 telephones.  
OpenStage Client Management  
This tool enables other services within the telephone to operate the database.  
Password Management Service  
Is a service for checking the passwords used in the telephone.  
Physical Interface Service  
Is a service for telephone application via the keyboard, mode keys (e.g. to start applications), programmable function keys, the clickwheel, and the slider.  
Phonebook  
Is responsible for the telephone's internal phonebook application.  
POT Service  
Is a service that performs basic telephony if the "Call View" application fails.  
Service Framework  
Environment where other telephone services operate. This service controls how services are started and stopped.  
Service Registry  
Is a service for recording all services that currently operate within the telephone.  
Sidecar Service  
Is a service for interaction between the telephone and all additional key modules possible.  
SIP Call Control  
Contains the call model for the telephone and is linked to telephony and call processing.  
SIP Messages  
SIP messages that are exchanged by the telephone.  
SIP Signalling  
Is involved in SIP display creation and record analysis and communicates directly with the SIP memory.  
Team Service  
Is a service that mainly involves the key functions.  
Tone Generation Service  
Is a service for creating tones on the telephone.  
Transport Service  
This service offers an IP (LAN) interface from the telephone to the "external environment".  
Vcard Parser Service  
This service manages the conversion and identification of VCard information when sending or receiving VCards via Bluetooth.  
Voice engine  
Provides a switching mechanism for "Voice Streams" within the telephone. It is therefore also involved in QDC, Music On Hold, and Voice Instrumentation.  
Web Server Service  
This service lets the telephone access the web.  

Trace-Level column  
The following trace levels can be selected in a drop-down list for the selected trace ID:

Trace level  
0  
OFF  
1  
FATAL  
2  
ERROR  
3  
WARNING  
4  
LOG  
5  
TRACE  
6  
DEBUG  

Transferring trace profiles  
Use the PC -> Phone button to transfer the trace settings from the PC to the OpenStage TDM telephone you want to trace.

8.19.33.3  
Error Trace and Core Dump Configuration Area 
The phone reset that was caused by an error generates a core dump in addition to the trace. Core dump behavior is defined here. When uploading the trace, the trace and, where applicable, the core dump are zipped together and transferred as a single tar file (.tar).

automatic delete before start  
If this flag is set, the existing trace file is automatically deleted every time you start a trace routine and a new empty trace file is created.

delete core dump  
If this flag is activated, the stored data that was written to a trace file is deleted. By default, this flag is not set.

activate core dump  
If this flag is activated, the trace data is saved.

max. core size [MB]  
You can select the maximum core size (in MB) in the drop-down list.
The following settings are available:
Unlimited, 1 MB, 5 MB, 10 MB, 15 MB, 25 MB, 50 MB, 75 MB, 100 MB.

File size  
The trace file size is entered here. Once the maximum file size is reached, the data is deleted and a new trace file is generated. The new trace data is then written to the new trace file.
Trace file size (in bytes): 65,536 to 4,194,304

Timeout [Minutes]  
The duration of the trace operation (trace time in minutes) is entered here.
Trace time (in minutes): 0 to 15

See also:  
   -   Section 8.19.31 "Maintenance | OpenStage Phones: Event Log"
   -   Section 8.19.32 "Maintenance | OpenStage Phones: SW distribution"
   -   Section 8.19.40 "Transfer | SW Transfer"
   -   Section 9.2.5 "Terminal hw sw version"
   -   Section 9.8.1 "Flags"

HiPath 3000/5000 V9, Manager E, Administrator Documentation, Issue 7   up Top
Disclaimer & Copyright   ID: P31003H3590M1000176A9   2012-06-25