All MIBs › NMS-1705
Last Updated: 2006-04-11
Category: Telephony/VoIP
Description: Manages NMS Communications 1705 platform card configuration and telephony interface parameters.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is NMS-1705?
NMS-1705 is a vendor-specific SNMP module from NMS Communications for its 1705 telephony platform card, used in voice/media processing systems. The module description available is generic boilerplate (referencing NAT) rather than a true description, and only a single top-level object identifier (nms1705Objects) was provided as a sample object, indicating this entry mostly reflects the module's registration root rather than detailed runtime objects. In general, a card-management MIB of this kind would expose configuration and status for telephony interface parameters and card-level operational health, such as card presence/state and channel status. Its likely monitoring value, where implemented, would be hardware status of the platform card (e.g. card up/down, channel utilization) within a larger telephony chassis. It would depend on a parent chassis/shelf MIB from NMS Communications for slot and chassis context, and would be deployed in telecom/media-gateway environments using NMS Communications 1705 platform cards. Engineers can download the NMS-1705 file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in NMS-1705. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- NMS Communications 1705 telephony platform card
Monitoring Examples
Only the top-level nms1705Objects identifier was available as a sample object, so a concrete polling scenario cannot be honestly constructed from this data; in general, an administrator would expect this branch to expose card and telephony-channel status objects for the 1705 platform card within a media-processing chassis.
Imported Objects
From NMS-SMI
| nmsMgmt | OBJECT-IDENTITY |
From RFC-1212
| OBJECT-TYPE |
From RFC1155-SMI
| IpAddress |
From RFC1213-MIB
| DisplayString |
OIDs
RFC description
Defines managed objects for NAT gateway configuration on terminal server lines.
Start monitoring NMS Communications 1705 telephony platform card with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.