ZTE-AN-PON-REMOTE-ONU-MIB :: zxAnPonRmCallerTestSipFailReason

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › ZTE-AN-PON-REMOTE-ONU-MIB › zxAnPonRmCallerTestSipFailReason

zxAnPonRmCallerTestSipFailReason

Module: ZTE-AN-PON-REMOTE-ONU-MIB

OID (symbolic): ZTE-AN-PON-REMOTE-ONU-MIB::zxAnPonRmCallerTestSipFailReason

OID (numeric): 1.3.6.1.4.1.3902.1082.500.3.2.9.6.1.5

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The failed reason of SIP test. This field should be filled when the value of zxAnPonRmCallerTestFailReason is 'sipTestFailed'.

dialToneTestFailure(1) - Dial tone test failure. inviteOkButNoBearerData(2) - No bearer traffic was received even though the test call was successful. callTimeoutNo200Ok(3) - The test call never completed although provisional response were received for the INVITE request. noResponseToInvite(4) - No response was received to the INVITE request and attempts to retry the INVITE timed out without a response. errorCodeAndReasonPhrase(5) - The softswitch returned an error to the INVITE request. callCancelledByServer(6) - The softswitch sent a CANCEL for the INVITE transaction. callCancelledByOnt(7) - The call was cancelled by the ONT. lineNotConfigured(8) - The POTS line is not fully configured, probably due to missing SIP provisioning data. lineNotInValidState(9)- The POTS line is in the wrong status to perform the test. lineNotRegistered(10) - The POTS line is not registered with the softswitch. notchFiltersRequired(11) - The notch filter settings in the configuration profile analog data were missing.

What is zxAnPonRmCallerTestSipFailReason?

Reports why the SIP signaling for the caller-side voice test failed, such as a dial-tone test failure, no bearer data despite an apparently successful call, a call timeout with no 200 OK, no response to the INVITE, an explicit SIP error code, a server- or ONT-initiated cancel, or a misconfigured/unregistered line. It's only populated when zxAnPonRmCallerTestFailReason indicates a SIP-level test failure.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3902.1082.500.3.2.9.6.1.5
snmpwalk -v2c -c public <target> ZTE-AN-PON-REMOTE-ONU-MIB::zxAnPonRmCallerTestSipFailReason

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.3902.1082.500.3.2.9.6.1.5.1
snmpget -v2c -c public <target> ZTE-AN-PON-REMOTE-ONU-MIB::zxAnPonRmCallerTestSipFailReason.1

Start monitoring ZTE ZXA10 GPON/EPON OLTs and ONUs with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ZTE-AN-PON-REMOTE-ONU-MIB::zxAnPonRmCallerTestSipFailReason OID value, configure state conditions and alerts, and monitor any ZTE ZXA10 GPON/EPON OLTs and ONUs 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.3902zteDPI-MIB
1.3.6.1.4.1.3902.1082zxAccessNodeZTE-AN-SMI
1.3.6.1.4.1.3902.1082.500zxAnPonZTE-AN-SMI
Numeric OIDNameModule
1.3.6.1.4.1.3902.1082.500.3zxAnPonRemoteOnuMibZTE-AN-PON-REMOTE-ONU-MIB
1.3.6.1.4.1.3902.1082.500.3.2zxAnPonRmOnuObjectsZTE-AN-PON-REMOTE-ONU-MIB
1.3.6.1.4.1.3902.1082.500.3.2.9zxAnPonRmOnuOamObjectsZTE-AN-PON-REMOTE-ONU-MIB
1.3.6.1.4.1.3902.1082.500.3.2.9.6zxAnPonRmOnuVoipCallerTestTableZTE-AN-PON-REMOTE-ONU-MIB
1.3.6.1.4.1.3902.1082.500.3.2.9.6.1zxAnPonRmOnuVoipCallerTestEntryZTE-AN-PON-REMOTE-ONU-MIB
1.3.6.1.4.1.3902.1082.500.3.2.9.6.1.5zxAnPonRmCallerTestSipFailReasonZTE-AN-PON-REMOTE-ONU-MIB