User Access To Diagnostic Information; Diagnostic Call (V3R1) - Unify OpenStage 60 Administration Manual

3.26.3

User Access to Diagnostic Information

If this option is enabled, extended phone data is also displayed to the user. To view the data,
the user must click on the "Diagnostic information" link in the user menu.
The Diagnostic Information can also be viewed by the user on the local phone by
>
selecting User > Diagnostic information.
Administration via WBM
Diagnostics > Diagnostic information > User access
User access
;
User Access
Reset
Submit
3.26.4

Diagnostic Call (V3R1)

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 Open-
Scape 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 prob-
lem 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 ei-
ther be sent after a successful end of diagnostic scenario or trace file is full.
For enabling tracing on all involved solution components, a call must be recognized to be a "di-
agnostic" 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 dialled 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.
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
Administration
Diagnostics
263