Page tree

Enabling SNMP

By default, the phone will not accept SNMP requests. This is necessary because SNMP might introduce unwanted security threats. To enable SNMP, you must specify which IP addresses may send SNMP requests to the phone. This can be done via Web Interface > Advanced > Network > SNMP Section

Two formats are allowed for the settings:

  • SNMP port - you may specify a different port than 161 for SNMP. Because the phone only runs one SNMP server on the device, changing the port should usually not be necessary. 
  • The IP address (e.g. “”) of the SNMP manager or the subnet address (address/subnet* e.g. allows accesses from hosts to can be specified. You may use several entries separated by space. For example, “” will allow accesses from the two listed IP addresses.

*The subnet indicates how many bits of the address are significant.

Reading Information

The phone only supports the GET request of SNMP. SET or other requests are not supported. For configuration and advances usage of the phone, please use the web server of the phone. The table on this page shows the available object identifiers (OID) on the phones.

The statistics covers data send and received on all interfaces of the phone. This includes all VLAN interfaces and the standard interface, but not the loopback device. The traffic of the built-in switch which by-passes the phone is not measured.

The number of calls is incremented whenever the phone writes a log into the local call statistics dictionary (for redial, missed calls, etc.).

The number of registrations can be used for sanity-checking of the phones. If the number goes down to zero, the phone has a problem and the SNMP manager should generate an alarm.

OIDNameUnitDescription BytesIntegerThe total number of bytes received PacketsIntegerThe total number of packets received BytesIntegerThe total number of bytes sent PacketsIntegerThe total number of packets sent status of registration x (1..12) (works with v6.5 or newer) & U-Boot VersionStringThe currently used firmware & uboot version (for example, “snom 360-SIP 3.60d 113-m”) number of registrations on the phone number of successful and unsuccessful calls free memory on the phone running time of the phone load averageString

The CPU load average of last 1min., 5min. and 15min. (> V8.2.6) about memory: used, free, cached, lid (phone lowlevel app.), lcs (phone highlevel app.) (> V8.2.6) UptimeStringThe running time of the phone highlevel application (> V8.2.6) incoming and outgoing messages (> V8.2.6) connections (> V8.2.6) number of timeouts running (> V8.2.6) subscriptions (> V8.2.6)

The serial number (starting from V10). Note: It's impossible to retrieve the serial number from the phones. Instead the MAC address is returned.

SNMP Test Tools

There is a SNMP Test Suite available at

Basic GET requests can be run in order to check the functionality:

snmpget -v1 -c public 10.91.x.x:161
SNMPv2-SMI::mib-2.7526.2.4 = STRING: "snomD765-SIP 2010.12-00001-gd311851f1"

snmpget -v1 -c public 10.91.x.x:161
SNMPv2-SMI::mib- = STRING: "0004139403F6"

snmpget -v1 -c public 10.91.x.x
SNMPv2-SMI::mib-2.7526.2.1.1 = INTEGER: 348150

snmpget -v1 -c public 10.91.x.x
SNMPv2-SMI::mib-2.7526.2.1.2 = INTEGER: 3707

snmpget -v1 -c public 10.91.x.x
SNMPv2-SMI::mib-2.7526.2.3.6 = INTEGER: 1

snmpget -v1 -c public 10.91.x.x
SNMPv2-SMI::mib-2.7526.2.3.8 = INTEGER: 0