Avaya Communication Manager controlled maintenance
MG-DS1 (DS1 Interface Media Module)
188
Maintenance of the Avaya G350 Media Gateway
June 2004
Echo Cancellation
If the MM710 firmware detects a serious echo canceller hardware error, it notifies maintenance software.
When the maintenance subsystem receives notification of the echo cancellation error, it executes this
Loss Of Signal Alarm Inquiry test.
This test, in addition to querying for a loss of signal condition and CSU errors, also queries MM710 to
confirm the echo canceller error. A minor alarm is raised if the error is confirmed. The trunks of the board
remain in-service since the board is still functional except for the echo cancellation capability.
If a loss of signal condition co-exists with CSU and/or echo canceller errors, the loss of signal condition
takes priority, and the board and all trunks on the board are put in the out-of-service state. Errors are
logged, however, for each error type.
When the maintenance subsystem receives notification that the echo canceller hardware error condition
no longer exists, the maintenance subsystem restores the board and all trunks to their previous service
state, if the alarm can be cleared (no other CSU errors or loss of signal conditions exist).
NOTE:
The DSU functionality is not available in this release of Communication Manager.
Table 109: TEST #138 Loss of Signal Alarm Inquiry Test 1 of 3
Error
Code
Test
Result
Description/ Recommendation
ABORT
Internal
system
error
Retry the command at 1-minute intervals for a maximum of 5 times.
2000
ABORT
Response to the test was not received within the allowable time period. This
may be due to hyperactivity. Error Type 1538 in the error log indicates
hyperactivity. The hyperactive Media Module is out of service and one or more
of the following symptoms may be exhibited.
The MG-DS1 tests (such as Test #138 and Test #139) are aborting with error
code 2000.
The tests run on the ports of this Media Module are returning a no board result.
A
busyout
or a
release
command has no affect on the test results.
A
list config
command shows that the Media Module and the ports are
properly installed.
When hyperactivity occurs, the Media Module is isolated from the system, and
all of the trunks for this Media Module are placed into the out of service state.
The system will try to restore the Media Module within 15 minutes. When no
faults are detected for 15 minutes, the MG-DS1 (MM710) interface Media
Module is restored to normal operation. All of the trunks for the Media Module
are then returned to the in service state. Hyperactivity is often caused by the
associated facility. In such a case, faults (such as slips, misframes, or blue
alarms) would be entered in the error log. In addition, many hardware errors
would be logged against the associated trunk circuits. If the facility is OK and
the error occurs again after 15 minutes, replace the Media Module.
1 of 3
Содержание Media Gateway G350
Страница 1: ...Maintenance of the Avaya G350 Media Gateway 555 245 105 Issue 3 June 2004 ...
Страница 16: ...About this book Sending us comments 16 Maintenance of the Avaya G350 Media Gateway June 2004 ...
Страница 48: ...G350 component maintenance IP telephones 48 Maintenance of the Avaya G350 Media Gateway June 2004 ...
Страница 284: ...Monitoring Extended keepalive 284 Maintenance of the Avaya G350 Media Gateway June 2004 ...
Страница 306: ...G350 traps G350 traps and resolutions 306 Maintenance of the Avaya G350 Media Gateway June 2004 ...
Страница 326: ...Media Server alarms S8300 alarms UPS 326 Maintenance of the Avaya G350 Media Gateway June 2004 ...