Polycom MGC Administrator, Руководство администратора

Страница: 505 / 584

MGC Administrator’s Guide
A-9
Fault Category - Exceptions
A severe system error, or exception, is an error that prevents the current task
from being executed. When the system detects such an error, it automatically
locks (or suspends) the task that caused the error. The effect of this suspension
depends on the type of the task. An error in a main or critical task will cause
the system to restart itself.
An error in a conference task will lock the conference. In this case, all
conference related operations will be blocked, including terminate, add
participant, remove participant etc. From the participants’ point of view, the
conference will go on but will stay in its current state, for example no video
switching will take place. However all other On Going Conferences will not
be affected. The operator can wait for these conferences to end, and then
restart the system manually. Similar behavior will take place when the error is
caused by a
participant task .
The system indicates the detection of a severe error by logging a fault
message. The message is displayed as follows:
This message can be viewed in the Fault Messages window. If such a fault
occurs, it is very important that you write down the fault message description
as well as the sequence of operations that led to it, and transfer it to the system
service engineer so that the problem can be fixed.
Table A-5: Fault Log Message
Time Category Level Code
06:23 pm june 15 exception major
EXCEPTION
_
HANDLER
_
MESSAGE
Description
EXCEPTION: error=0x0 error_address=0x1c0e74
TaskID=0x370000 tskname=
CONF interpt_num=0