Control Protocol Reports; Tpncp Error Report; Megaco Error Conditions; Solutions To Possible Problems - AudioCodes Mediant 1000 User Manual

User's Manual
9.4

Control Protocol Reports

9.4.1

TPNCP Error Report

When working with the AudioCodes proprietary TPNCP (TrunkPack Network Control
Protocol), the Mediant 1000 reports all events using a TPNCP log event report mechanism
(using error/debug events), through the network interface. For a list of events, refer to the
section, "Board Originated Error Codes," in the "VoPLib API Reference Manual", Document
#: LTRT-844xx.
Examples of using the Log Event Report Mechanism are also shown in the "VoPLib API
Reference Manual", Document #: LTRT-844xx.
9.4.2

MEGACO Error Conditions

When working with MEGACO, the Mediant 1000 reports error conditions via the Call
Manager (or via a Call Manager of the customer's choice) using the standard MEGACO
facilities, through the network interface. For more information on MEGACO error
conditions, refer to the IETF web site at URL
for MEGACO.
9.4.3 SNMP Traps
Mediant 1000 supports various SNMP traps via the SNMP Agent running on the board.
Among these traps are Trunk MIB traps, acBoardStarted and acResetingBoard traps.
Refer to "Using SNMP" on page
board.
9.5

Solutions to Possible Problems

9.5.1

Possible Common Problems

Solutions to possible common problems are described in the table below.
Problem Possible Cause
Software does not
No
function in the device
communica
tion
Network problem
Network definitions
Version 4.6
117

Table 9-1: Solutions to Possible Common Problems

Solutions
Try to "ping" the board/module. If ping fails, check for
network problems/definitions and try to reset the
board/module
Check the cables.
Check if the default gateway can reach the IP of the
board/module.
Check if the board/module got the correct IP.
9. Diagnostics & Troubleshooting
http://www.ietf.org/rfc/
for more details on all SNMP traps available on the
191
and refer to RFC 3015
August 2005