Cisco is no longer supporting SNMP for many products, such as the C40, and C60 codecs.
Please upgrade the interface for monitoring nodes to include this option.
See the below response from Cisco of why they are moving to XML API.
Cisco solutions has decided to move away from SNMP and use XML queries.
One of the biggest reasons is that a lot of codecs are behind firewalls and through the public internet, some not secured through VPNs, since the codec communications use encryption. SNMP is used for LAN based management and only used for WAN management when there is a secure network between two sites. No one sends SNMP across the public internet, not even SNMPv3 traffic. It is just not counted as being a truly secure protocol.
SNMP is a connection-less protocol, which has vast implications for wide-area network implementations. Think of a typical enterprise TelePresence implementation where there are SOHO sites on the internet behind firewalls with private networks.
a) How do SOHO devices send traps to an SNMP manager inside the corporate network? They can't.
b) A public address with a NAT to the SNMP manager would be required for SOHO devices to send traps.
c) Because it is connectionless, the SNMP manager cannot send a message to the SOHO device, even as a reply to a trap.
Cisco has chosen to use XML over HTTP or HTTPS because they are connection-oriented, and communications can be returned to the SOHO device, as a reply, through a firewall and NAT. This gives us the ability to have rich communication, exceeding the capability of SNMP, that works even over the Internet, and this can be done in a more secure manner.
For management, Cisco does have Prime Collaboration Manager for both Cisco Voice (UC) and Video (TelePresence). It uses XML to gather information from Codecs, VCS, and Bridges.