All MIBs › TEL2N-MIB
Organization: 2N TELEKOMUNIKACE a.s.
Last Updated: 2015-05-01
Category: Vendor-Specific Device Management, VoIP and Telephony
Description: Manages 2N TELEKOMUNIKACE IP door intercom devices, access control events, and call state.
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 TEL2N-MIB?
TEL2N-MIB is a vendor-specific MIB from 2N TELEKOMUNIKACE covering the company's Helios IP intercom product line, exposing device identity and SIP registration state for IP door-entry/intercom units. Under the heliosip subtree it reports hipProductName, hipHwVersion, hipSerial, hipVersion, and hipBootVersion for hardware/firmware identification, and a hipSipTable indexed by hipIndex tracks each configured SIP account's hipPhoneNumber, hipState (down, goingup, up, goingdown), hipRegistrationAt (registrar IP), and hipRegistrationTime. This makes it a compact device-identity-and-SIP-registration MIB rather than a call-detail or access-control MIB, useful for confirming an intercom unit is registered with its SIP proxy/PBX and identifying which registrar it last registered against. It is deployed on 2N Helios IP intercom hardware at building entrances and gates, typically alongside a SIP PBX or intercom management platform. Facilities/telecom teams poll the TEL2N-MIB MIB to confirm door intercom SIP accounts remain registered and reachable.
IPNetwork Monitor allows you to monitor SNMP objects defined in TEL2N-MIB. 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
- 2N TELEKOMUNIKACE Helios IP door intercom devices
Monitoring Examples
An operator polls hipState across hipSipTable for every intercom unit at a site; a hipState stuck at down or goingup for longer than the expected registration retry interval would indicate the intercom has lost SIP registration and can no longer receive or place calls.
What Can Be Monitored
- device product name/hardware/firmware version
- serial number
- per-account SIP registration state
- SIP registrar IP address
- SIP registration timestamp
Imported Objects
From SNMPv2-SMI
| Integer32 | |
| IpAddress | |
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| TimeTicks | |
| enterprises |
How to Use in IPNetwork Monitor
Example using hipState OID:
OIDs
RFC description
Manages 2N Telekomunikace IP intercom devices including Helios IP product models with SIP account status.
Start monitoring 2N TELEKOMUNIKACE Helios IP door intercom device (SIP registration/hardware identity 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.