TELES VoIP Box BRI Series, Reference Manual

Page: 144 / 226

7 System maintenance and soft-
ware update
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 144
The following status and error messages appear in the
proto-
col.log
file when
ALARM
appears in the VoIP port’s subscrib-
er line:
[<port><i>] ERR: Prob-
lem at Port <num>
X A Layer 1 or Layer 2 error occurred on
<num>
.
<i> indicates error type:
A
Layer 1 error
;
Layer 2 error
0
Layer 1&2 operational.
If the error persists, a differentiation is possible
through 'status of the ports'.
If this message appears, status inquiry connections
via remote administration are accepted and NMS
downloads the protocol.log file.
Attention: No Call-
back-Call <num> Ar-
rived
Callback with DTMF: the Callback Provider
<num>
did
not call back within approx. 20 sec.
Direct Line Access with DTMF: the call was accepted
but disconnected again within x sec. (as defined by
MapCallBack-WaitDisc
).
Write error
Access to the disk drive on which the data is to be
stored was not possible because it is set for read-only,
full or because of faulty hardware or software.
[995] Msg-Memory >
75%
X This message appears when message memory is over
75% full.
If this message appears, status inquiry connections
via remote administration are accepted and NMS
downloads the
protocol.log
file.
Table 7.1 Event log messages (continued)
Message NMS Definition
Table 7.2
Protocol.log
status and error messages (page 1 of 4)
Message Definition
System Configuration (a)
config: <num> duplicate profile
Specified line in
pabx.cfg
or
route.cfg
contains du-
plicate profile.
config: <num> invalid
Specified line in
pabx.cfg
or
route.cfg
is invalid.
config: evaluation errcode <num>
Internal error.
Port-Specific Entries
[<port>]Unblock Port
The
<port>
has been unblocked. This can occur via
remote access for all controller types.
[<port>]Block Port
The
<port>
has been blocked. This can occur via re-
mote access for all controller types.