The Embedded Web Server's 'Message Log' (Integral Syslog); Control Protocol Reports; Tpncp Error Report; Mgcp/Megaco Error Conditions - AudioCodes Mediant 2000 User Manual
Mgcp, megaco, tpncp voip mediant media gateways
Hide thumbs
Also See for Mediant 2000:
- User manual (702 pages) ,
- Installation manual (44 pages) ,
- Hardware installation manual (30 pages)
Table of Contents
Advertisement
SyslogServerIP=10.2.0.136
EnableSyslog =1
SyslogServerPort =601
9.2
The Embedded Web Server's 'Message Log'
(Integral Syslog)
The Message Log screen in the Embedded Web Server GUI, similar to a Syslog
server only integral to the web server, displays debug messages useful for debugging.
For detailed information, refer to ''Message Log'' on page 252. The Message Log
screen is not recommended for logging of errors and warnings because errors can
appear over a prolonged period of time, e.g., a device can display an error after
running for a week, and it is not recommended to prolong a 'Message Log' session.
For logging of errors and warnings, refer to ''Syslog'' on page 271.
9.3
Control Protocol Reports
9.3.1
TPNCP Error Report
When working with the AudioCodes proprietary TPNCP (TrunkPack Network Control
Protocol), the TP-1610 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.3.2
MGCP/MEGACO Error Conditions
When working with MGCP/MEGACO, the device reports error conditions via the Call
Manager (or via a Call Manager of the customer's choice) using the standard
MGCP/MEGACO facilities, through the network interface. For more information on
MGCP/MEGACO error conditions, refer to the IETF Website at:
www.ietf.org/rfc/..
Refer to RFC 3435/3661 for MGCP and RFC 3015 for MEGACO.
9.3.3
SNMP Traps
TP-1610 boards support 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
available on the board.
9.4
TP-1610 Self-Test
The TP-1610 self-test capabilities are used to identify faulty hardware components on
startup and during run time.
User's Manual
165
for more details on all SNMP traps
274
Mediant 2000
Document # LTRT-69805
Advertisement
Table of Contents
