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 what IP addressed may send SNMP requests to the phone. This can be done via Web Interface > 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. “192.168.4.5”) of the SNMP manager or the subnet address (address/subnet* e.g. 192.168.5.0/24 allows accesses from hosts 192.168.5.0 to 192.168.5.255) can be specified. You may use several entries separated by space. For example, “192.168.5.6 192.168.5.7” will allow accesses from the two listed IP addresses.
*The subnet indicates how many bits of the address are significant.
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.
|220.127.116.11.2.1.7518.104.22.168||Rx Bytes||Integer||The total number of bytes received|
|22.214.171.124.2.1.75126.96.36.199||Rx Packets||Integer||The total number of packets received|
|188.8.131.52.2.1.75184.108.40.206||Tx Bytes||Integer||The total number of bytes sent|
|220.127.116.11.2.1.7518.104.22.168||Tx Packets||Integer||The total number of packets sent|
|22.214.171.124.2.1.7526.2.3.x||Registration||Integer||Registration status of registration x (1..12) (works with v6.5 or newer)|
|126.96.36.199.2.1.7526.2.4||Firmware & U-Boot Version||String||The currently used firmware & uboot version (for example, “snom 360-SIP 3.60d 113-m”)|
|188.8.131.52.2.1.7526.2.5||Registrations||Integer||The number of registrations on the phone|
|184.108.40.206.2.1.7526.2.6||Calls||Integer||The number of successful and unsuccessful calls|
|220.127.116.11.2.1.7526.2.7||Memfree||Integer||The free memory on the phone|
|18.104.22.168.2.1.7526.2.8||Uptime||String||The running time of the phone|
|22.214.171.124.2.1.7526.2.9||CPU load average||String|
The CPU load average of last 1min., 5min. and 15min. (> V8.2.6)
|126.96.36.199.2.1.7526.2.10||Meminfo||String||Info about memory: used, free, cached, lid (phone lowlevel app.), lcs (phone highlevel app.) (> V8.2.6)|
|188.8.131.52.2.1.7526.2.11||LCS Uptime||String||The running time of the phone highlevel application (> V8.2.6)|
|184.108.40.206.2.1.7526.2.12||Packets||String||The incoming and outgoing messages (> V8.2.6)|
|220.127.116.11.2.1.7526.2.13||Connections||String||The connections (> V8.2.6)|
|18.104.22.168.2.1.7526.2.14||Timeouts||String||The number of timeouts running (> V8.2.6)|
|22.214.171.124.2.1.7526.2.15||Subscriptions||String||The 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 http://www.net-snmp.org/.
Basic GET requests can be run in order to check the functionality: