XYLO-CALLMGMT-MIB :: callHistDisconnectReason

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › XYLO-CALLMGMT-MIB › callHistDisconnectReason

callHistDisconnectReason

Module: XYLO-CALLMGMT-MIB

OID (symbolic): XYLO-CALLMGMT-MIB::callHistDisconnectReason

OID (numeric): 1.3.6.1.4.1.15.2.16.2.4.1.24

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: Call disconnect reasons: unknown telDisc got telephone disconnect (hangup) dialFailed wanmgrErr internal error, shouldn't happen reset WAN/channel reset admErrornext general internal mechanism to end call admModDown DSR or DCD went down pppTerm PPP protocol disconnect inactivity inactivity timer ran out hangupCmd CLI command 'hangup' lastJob CLI last-job maxLogon max logon timer ran out slaveNormal normal slave termination slaveError abnormal slave termination noCarrier modem failed to establish a connection cliInactivity cli_inactivity timer ran out portReset port was reset cliAuthFail CLI authorization failed slaveAuthFail slave port authorization failed pppPapFail PPP PAP failed pppChapFail PPP CHAP failed modemReset internal modem was reset deadModemReset internal modem was reset because it was not responding

What is callHistDisconnectReason?

The system-level reason this call was disconnected, from a long enumeration including telDisc(2) (far-end hangup), noCarrier(15), pppChapFail(21), inactivity(9), and dozens of other specific PPP/system failure codes. Admins mine this field across many historical records to find recurring disconnect causes, e.g. a spike in pppChapFail(21) pointing to a credentials problem with a particular dial-up client population.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.15.2.16.2.4.1.24
snmpwalk -v2c -c public <target> XYLO-CALLMGMT-MIB::callHistDisconnectReason

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.15.2.16.2.4.1.24.1
snmpget -v2c -c public <target> XYLO-CALLMGMT-MIB::callHistDisconnectReason.1

Start monitoring Xylogics Remote Annex communication/access servers (active-call/modem-call-statistics status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the XYLO-CALLMGMT-MIB::callHistDisconnectReason OID value, configure state conditions and alerts, and monitor any Xylogics Remote Annex communication/access servers (active-call/modem-call-statistics status) from a single console.

OID Breakdown

Upper-level ancestors (9 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.15xylogicsANNEX-MIB
1.3.6.1.4.1.15.2annexANNEX-MIB
1.3.6.1.4.1.15.2.16callmgmtXYLO-MIB-SMI
Numeric OIDNameModule
1.3.6.1.4.1.15.2.16.2callHistXYLO-CALLMGMT-MIB
1.3.6.1.4.1.15.2.16.2.4callHistTableXYLO-CALLMGMT-MIB
1.3.6.1.4.1.15.2.16.2.4.1callHistEntryXYLO-CALLMGMT-MIB
1.3.6.1.4.1.15.2.16.2.4.1.24callHistDisconnectReasonXYLO-CALLMGMT-MIB