Snmp Interface Details; Snmp Community Names; Table 16-2: Snmp Predefined Groups - AudioCodes Mediant 1000 User Manual

SIP User's Manual
Table 16-1: Proprietary Traps Description (continues on pages 376 to 377)
Trap
acHTTPDownloadResult
acDChannelStatus
In addition to the listed traps, the device also supports the following standard traps:
dsx1LineStatusChange
dsx3LineStatusChange
coldStart
authenticationFailure
16.7

SNMP Interface Details

This section describes details of the SNMP interface that is required when developing an
Element Manager (EM) for any of the TrunkPack-VoP Series products, or to manage a
device with a MIB browser.
The gateway offers the following SNMP security features:
SNMPv2c community strings
SNMPv3 User-based Security Model (USM) users
SNMP encoded over IPSec (refer to Section
Combinations of the above
Currently, both SNMP and ini file commands and downloads are not encrypted. For ini file
encoding, refer to Section

16.7.1 SNMP Community Names

By default, the device uses a single, read-only community string of 'public' and a single
read-write community string of 'private'.
The following community strings can be defined:
Up to five read-only community strings
Up to five read-write community strings
A single trap community string
Each community string must be associated with one of the following predefined SNMP
groups:
Group
ReadGroup
ReadWriteGroup
TrapGroup
Version 5.0
Sent at the success or failure of HTTP download.
Non-alarm trap sent at the establishment, re-establishment, or
release of LAPD link with its peer connection. The trap is sent
with one of the following textual descriptions:
D-channel synchronized
D-channel not-synchronized
6.1 on page 213.

Table 16-2: SNMP Predefined Groups

Get Access
Yes No
Yes Yes
No No
377
16. SNMP-Based Management
Description
14.1 on page 343)
Set Access
Yes
Yes
Yes
Can Send Traps
December 2006