Diagnostic Call - Siemens A31003-D3000-M100-01-76A9 Administrator User Manual

Administration
Diagnostics

3.23.4 Diagnostic Call

196
Administration via WBM
Diagnostics > Diagnostic information > User access
Related Topics
The feature "Rapid Status Diagnostic Call" will provide the possibility to place a
diagnostic call, for example by the user, which starts call related tracing on the
phone and on involved OpenScape Voice and collect these traces at OpenScape
Voice Trace Manager (OSVTM). With all these traces available, a call can be
followed throughout the voice system and a possible problem can be detected
faster. As all traces from all involved components are available at the first level
support, the analysis of a possible problem can be started immediately.
A so-called diagnostic scenario will enable traces on all involved SIP components
of the OSC Voice solution and store all traces at a central server. A tool will help
service, to follow a call through the traces and determine the point of problem.
The approach is to use a SIP Header ([1]) to indicate, whether a call is a
diagnostic call or not. Presence of this header will mean that related call is a
diagnostic call. Absence of this field means a non-diagnostic call. This header will
either switch on traces in the solution component or be ignored if it isn't supported.
If the call is recognized as a diagnostic call, the traces will be sent to DLS as a
first step and then DLS will forward them to OSVTM. Collected traces will either
be sent after a successful end of diagnostic scenario or if trace file is full.
For enabling tracing on all involved solution components, a call must be recog-
nized to be a "diagnostic" call. Therefore, a special SIP header will be added to
the signalling messages. All components which are able to support such a call will
then switch on traces and send the traces to DLS server (which will forward them
to a pre-defined OSVTM server).
A dial-prefix has been chosen, as the dialed number should be identical to a
number, where the user identified a possible problem. This prefix will be filtered
before placing a call, so that the SIP messages will be similar to the ones for the
problematic destination.
The SIP header "X-Siemens-Trace-ID" has been chosen, as this is a special SIP
field created for this feature. Existence of the diagnostic call, start and finish of a
diagnostic call can be determined via this field [1].
Trace id will be unique throughout the system and the following format will be
used to generate trace id:
TraceId: <UNIX_Timestamp>_<Last 6 bytes of MAC Address>
If related calls (diagnostic or not) are established following the start of the
diagnostic call, then it turns to be a diagnostic scenario. Related calls become
diagnostic (if they are not already) and traces are collected until the last diagnostic
call ends plus a predefined timer. This timer guarantees capturing related infor-
mation regarding to a problematic scenario.
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
A31003-D3000-M100-01-76A9, 02-2013