ZTE-AN-PON-REMOTE-ONU-MIB: View SNMP OID List / Download MIB

The MIB module for the management of PON remote ONU service.

This table includes protocol configuration information of ONU's Ethernet UNI port.

An entry in zxAnPonRmOnuIfProtoConfTable.

This attribute specifies the index of ONU's interface.

Refers to 'zxAnPonRmProtoPktsLimitPrfName'.

Refers to 'zxAnPonRmProtoEnablePrfName'.

PON ONU POTS calling data record table.

An entry in zxAnPonRmPotsCallDataRecordTable.

This attribute indicates the index of UNI in ONU.

VoIP calling record index.

The total number of the call records.

Sequence number of call record.

The time of one call, format is yyyy-mm-dd,HH:MM:SS. For example,2010-12-30,13:06:30.

The duration of one call.

Callee number.

Caller number.

The total number of RTP packets transmitted during the call.

The total number of RTP packets received during the call.

The total number of RTP packets lost during the call.

The total number of RTP packets discarded due to error.

Buffer overflow count.

Buffer empty count.

The average jitter for received packets.

Whether or not the far end participated in RTCP. Enumeration: 'notParticipated': 2, 'participated': 1.

The peak jitter for received packets.

The average jitter buffer depth for received packets.

Whether or not the far end participated in RTCP-XR. Enumeration: 'notParticipated': 2, 'participated': 1.

The peak round-trip delay for a call.

The average round-trip delay for the call.

The average mean opinion score.

EMS can send zxAnPonRmOnuRetrieveCmd to retrieve ONU monitoring metrics which are not defined by ME of OMCI or OAM. Otherwise, EMS can retrieve error messages of excution of zxAnPonRmOnuConfCmd in ONU. The action is divided into two steps. Step one: EMS sends zxAnPonRmOnuRetrieveCmdSessionId and zxAnPonRmOnuRetrieveCmd to OLT. The format of zxAnPonRmOnuRetrieveCmd is: 'command head::[parameter 1]=P1,[parameter 2]=P2, ...[parameter n]=Pn;' the command head represents a configuration function which is defined by EMS and ONU. parameters are followed by '::' and separated by ',', the end of the command must be ';'. Example: GET_WAN_CONF::WANID=1; Step two: The result is saved in zxAnPonRmOnuRetrieveCmdReply. EMS can retrieve result by zxAnPonRmOnuRetrieveCmdSessionId. The format of zxAnPonRmOnuRetrieveCmdReply is: 'command head::[parameter 1]=P1,[parameter 2]=P2, ...[parameter n]=Pn;' the command head represents a configuration function which is defined by EMS and ONU. parameters are followed by '::' and separated by ',', the end of the command must be ';'. Example: GET_WAN_CONF_RESULT::WANID=1,HOST=1,MODE=1,PPPUser=test, PPPPassword=test;

An entry in zxAnPonRmOnuRetrieveCmdTable.

This attribute identifies the session ID. The session ID is generated by EMS and is unique in EMS. Session ID can ensure that reply result does not conflicting.

This attribute identifies commands which declared the information which EMS needs.

This attribute identifies the reply result.

The Maintenance Domain table. Each row in the table represents a different Maintenance Domain. A Maintenance Domain is described in 802.1ag (3.22) as the network or the part of the network for which faults in connectivity are to be managed. The boundary of a Maintenance Domain is defined by a set of DSAPs, each of which can become a point of connectivity to a service instance. This table only used by GPON service.

The Maintenance Domain table entry. The index 'zxAnPonOnuIndex' represents the normal ONU index.

The index to the Maintenance Domain table. Referential integrity is required, i.e., the index needs to be persistent upon a reboot or restart of a device. The index can never be reused for other Maintenance Domain. The index value should keep increasing up to the time that they wrap around. This is to facilitate access control based on OID.

The type (and thereby format) of the Maintenance Domain Name. A value that represents a type (and thereby the format) of a zxAnPonRmOnuCfmMdName. The value can be one of the following: none(1) No format specified, usually because there is not (yet) a Maintenance Domain Name. In this case, a zero length OCTET STRING for the Domain Name field is acceptable. dnsLikeName(2) Domain Name like string, globally unique text string derived from a DNS name. macAddrAndUint(3) MAC address + 2-octet (unsigned) integer. charString(4) RFC2579 DisplayString, except that the character codes 0-31 (decimal) are not used. iccBased(5) ITU carrier code followed by locally assigned UMC code, 13 bytes with trailing nulls as needed. Enumeration: 'iccBased': 5, 'none': 1, 'macAddressAndUint': 3, 'charString': 4, 'dnsLikeName': 2.

The Maintenance Domain name. The type/format of this object is determined by the value of the zxAnPonRmOnuCfmMdFormat object. Each Maintenance Domain has unique name amongst all those used or available to a service provider or operator. It facilitates easy identification of administrative responsibility for each Maintenance Domain. Clause 3.24 defines a Maintenance Domain name as the identifier, unique over the domain for which CFM is to protect against accidental concatenation of Service Instances, of a particular Maintenance Domain.

The Maintenance Domain Level. Integer identifying the Maintenance Domain Level (MD Level). Higher numbers correspond to higher Maintenance Domains, those with the greatest physical reach, with the highest values for customer's CFM packets. Lower numbers correspond to lower Maintenance Domains, those with more limited physical reach, with the lowest values for CFM PDUs protecting single bridges or physical links.

Indicates if the Management Entity can create MHFs. Enumerated value indicating whether the management entity can create MHFs (MIP Half Function) for this Maintenance Domain. The valid values are: defMHFnone(1) No MHFs can be created for this VID. defMHFdefault(2) MHFs can be created on this VID on any Bridge port through which this VID can pass. defMHFexplicit(3) MHFs can be created for this VID only on Bridge ports through which this VID can pass, and only if a MEP is created at some lower MD Level. Enumeration: 'defMHFnone': 1, 'defMHFexplicit': 3, 'defMHFdefault': 2.

Enumerated value indicating what, if anything, is to be included in the Sender ID TLV (21.5.3) transmitted by MPs configured in this Maintenance Domain. Since, in this variable, there is no encompassing Maintenance Domain, the value sendIdDefer takes the meaning of sendIdChassisManage. The valid values are: sendIdNone(1) The Sender ID TLV is not to be sent. sendIdChassis(2) The Chassis ID Length, Chassis ID Subtype, and Chassis ID fields of the Sender ID TLV are to be sent. sendIdManage(3) The Management Address Length and Management Address of the Sender ID TLV are to be sent. sendIdChassisManage(4) The Chassis ID Length, Chassis ID Subtype, Chassis ID, Management Address Length and Management Address fields are all to be sent. Enumeration: 'sendIdManage': 3, 'sendIdNone': 1, 'sendIdChassis': 2, 'sendIdChassisManage': 4.

The status of the row. The writable columns in a row can not be changed if the row is active. All columns must have a valid value before a row can be activated.

This managed entity models an IEEE 802.1 service defined on a bridge port. A maintenance association (MA) is a set of endpoints on opposite sides of a network, all existing at a defined maintenance level. This table only used by GPON service.

It is entry in the zxAnPonRmOnuCfmMaTable.

This attribute uniquely identifies an instance of MA.

A value that represents a type (and thereby the format) of a zxAnPonOnuCfmMaName. The value can be one of the following: primaryVid(1) Primary VLAN ID. 12 bits represented in a 2-octet integer: - 4 least significant bits of the first byte contains the 4 most significant bits of the 12 bits primary VID - second byte contains the 8 least significant bits of the primary VID 0 1 2 3 4 5 6 7 8 +-+-+-+-+-+-+-+-+ |0 0 0 0| (MSB) | +-+-+-+-+-+-+-+-+ | VID LSB | +-+-+-+-+-+-+-+-+ charString(2) RFC2579 DisplayString, except that the character codes 0-31 (decimal) are not used. (1..45) octets unsignedInt16 (3) 2-octet integer/big endian rfc2865VpnId(4) RFC 2685 VPN ID 3 octet VPN authority Organizationally Unique Identifier followed by 4 octet VPN index identifying VPN according to the OUI: 0 1 2 3 4 5 6 7 8 +-+-+-+-+-+-+-+-+ | VPN OUI (MSB) | +-+-+-+-+-+-+-+-+ | VPN OUI | +-+-+-+-+-+-+-+-+ | VPN OUI (LSB) | +-+-+-+-+-+-+-+-+ |VPN Index (MSB)| +-+-+-+-+-+-+-+-+ | VPN Index | +-+-+-+-+-+-+-+-+ | VPN Index | +-+-+-+-+-+-+-+-+ |VPN Index (LSB)| +-+-+-+-+-+-+-+-+ To support future extensions, the zxAnPonOnuCfmMaFormat textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations MUST ensure that zxAnPonOnuCfmMaFormat objects and any dependent objects (e.g., zxAnPonOnuCfmMaName objects) are consistent. An inconsistentValue error MUST be generated if an attempt to change an zxAnPonOnuCfmMaFormat object would, for example, lead to an undefined zxAnPonOnuCfmMaName value. In particular, zxAnPonOnuCfmMaFormat/zxAnPonOnuCfmMaName pairs MUST be changed together if the nameType changes. The Maintenance Domain name and Maintenance Association name, when put together into the CCM PDU, MUST total 48 octets or less. If the zxAnPonRmOnuCfmMdFormat object contains none(1), then the zxAnPonOnuCfmMaName object MUST be 45 octets or less in length. Otherwise, the length of the zxAnPonRmOnuCfmMdName object plus the length of the zxAnPonOnuCfmMaName object, added together, MUST total less than or equal to 44 octets. Enumeration: 'unsignedInt16': 3, 'rfc2865VpnId': 4, 'primaryVid': 1, 'charString': 2.

Denotes a generic Maintenance Association Name. It is the part of the Maintenance Association Identifier which is unique within the Maintenance Domain Name and is appended to the Maintenance Domain Name to form the Maintenance Association Identifier (MAID). The value is always interpreted within the context of a zxAnPonOnuCfmMaFormat value. The value of a zxAnPonOnuCfmMaName object MUST always be consistent with the value of the associated zxAnPonOnuCfmMaFormat object. Attempts to set an zxAnPonOnuCfmMaName object to a value inconsistent with the associated zxAnPonOnuCfmMaFormat MUST fail with an inconsistentValue error.

Indicates the interval at which CCMs are sent by a MEP. The possible values are: intervalInvalid(1) No CCMs are sent (disabled). interval300Hz(2) CCMs are sent every 3 1/3 milliseconds (300Hz). interval10ms(3) CCMs are sent every 10 milliseconds. interval100ms(4) CCMs are sent every 100 milliseconds. interval1s(5) CCMs are sent every 1 second. interval10s(6) CCMs are sent every 10 seconds. interval1min(7) CCMs are sent every minute. interval10min(8) CCMs are sent every 10 minutes. Enumeration: 'interval10s': 6, 'interval10min': 8, 'interval1s': 5, 'interval10ms': 3, 'interval100ms': 4, 'interval300Hz': 2, 'intervalInvalid': 1, 'interval1min': 7.

This attribute is a list of up to 12 VLAN IDs with which this MA is associated. The first entry is understood to be the primary VLAN. eg: 100,15-16 means that the primary VLAN is 100, MA is associated with VLAN 15,16,100. A null value indicates the MA is not associated with any VLANs.

This attribute determines whether the bridge creates a MHF or not, under circumstances defined in IEEE 802.1ag clause 22.2.3. defMHFnone(1), No MHFs can be created for this VID. defMHFdefault(2), MHFs can be created on this VID on any Bridge port through which this VID can pass. defMHFexplicit(3), MHFs can be created for this VID only on Bridge ports through which this VID can pass, and only if a MEP is created at some lower MD Level. defMHFdefer(4), The creation of MHFs is determined by the corresponding Maintenance Domain variable (zxAnPonRmOnuCfmMdMhfCreation). Enumeration: 'defMHFnone': 1, 'defMHFdefer': 4, 'defMHFexplicit': 3, 'defMHFdefault': 2.

This attribute determines the content of the sender ID TLV included in CFM messages transmitted by MP controlled by this MA. sendIdNone(1), The Sender ID TLV is not to be sent. sendIdChassis(2), The Chassis ID Length, Chassis ID Subtype, and Chassis ID fields of the Sender ID TLV are to be sent. sendIdManage(3), The Management Address Length and Management Address of the Sender ID TLV are to be sent. sendIdChassisManage(4), The Chassis ID Length, Chassis ID Subtype, Chassis ID, Management Address Length and Management Address fields are all to be sent. sendIdDefer(5), The contents of the Sender ID TLV are determined by the corresponding Maintenance Domain variable (zxAnPonRmOnuCfmMdMhfIdPermission). Enumeration: 'sendIdManage': 3, 'sendIdDefer': 5, 'sendIdNone': 1, 'sendIdChassis': 2, 'sendIdChassisManage': 4.

This attribute indicates the operation of the entry.

This managed entity models a maintenance association end point (MEP) as defined primarily in IEEE 802.1ag and secondarily in ITU-T Y.1731. This table only used by GPON service.

It is entry in the zxAnPonRmOnuCfmMepTable.

This attribute specifies the MEP's own identity in the MA.

This attribute specifies the associated Ethernet port.

If set to true, the MEP will generate CCM messages. Enumeration: 'disabled': 2, 'enabled': 1.

This attribute specifies that wether to enable Y.1731 server MEP function. Enumeration: 'disabled': 2, 'enabled': 1.

The direction in which the MEP faces on the Bridge port. Indicates the direction in which the Maintenance association (MEP or MIP) faces on the bridge port: down(1) Sends Continuity Check Messages away from the MAC Relay Entity. up(2) Sends Continuity Check Messages towards the MAC Relay Entity. Enumeration: 'down': 1, 'up': 2.

An integer indicating the Primary VID of the MEP, always one of the VIDs assigned to the MEP's MA. The value 0 indicates that either the Primary VID is that of the MEP's MA, or that the MEP's MA is associated with no VID.

Administrative state of the MEP, unlock indicates that the MEP is to function normally, and lock indicates that it is to cease functioning. Enumeration: 'lock': 2, 'unlock': 1.

The priority value for CCMs and LTMs transmitted by the MEP. Default Value is the highest priority value allowed to pass through the bridge port for any of this MEPs VIDs. The management entity can obtain the default value for this variable from the priority regeneration table by extracting the highest priority value in this table on this MEPs bridge port. (1 is lowest, then 2, then 0, then 3-7).

This attribute comprises 8 bytes to be included in LTMs. They allow received LTRs to be directed to the correct originator. The attribute includes the originator MAC address and a locally-defined identifier. If this field is 0 (default), the ONT uses the MEP's MAC address, with 0 as the locally-defined identifier.

This attribute lists up to 12 expected peer MEPs for CCMs, [IEEE 802.1ag] allows for multipoint networks, and therefore a list of peer MEPs. This attribute allows for up to 12 peers for a given MEP, though G-PON applications are expected to need only a single peer. Missing or unexpected messages trigger alarm declaration after a soak interval. it should be set to null if unused peer MEP. e.g., 1,3-5 means the used peer MEPs are 1,3,4,5.

This attribute enable generation of Ethernet AIS. Enumeration: 'disabled': 2, 'enabled': 1.

This attribute specifies ethernet AIS transmission period. Enumeration: 'time1min': 2, 'time1s': 1.

This attribute specifies priority of transmitted ETH AIS frames.

This attribute specifies the maintenance level at which the client MEP exists.

This attribute specifies the lowest priority alarm that is allowed to generate a fault alarm. mode1, All defects generate alarms after suitable soaking, including AIS and RDICCM. mode2, Alarm generated only by one of: MACstatus, RemoteCCM, ErrorCCM, XconCCM. mode3, Alarm generated only by one of: RemoteCCM, ErrorCCM, XconCCM mode4, Alarm generated only by one of: ErrorCCM, XconCCM. mode5, Alarm generated only by: XconCCM. mode6, No alarms are to be reported. Enumeration: 'mode6': 6, 'mode4': 4, 'mode5': 5, 'mode2': 2, 'mode3': 3, 'mode1': 1.

This attribute defines the defect soak time that must elapse before the MEP declares an alarm.

This attribute defines the defect-free soak time that must elapse before the MEP clears an alarm.

This attribute indicates the operation of the entry.

The table lists PPPoE test entry. the entry indicates the test.

An entry in the zxAnPonRmOnuPppoeTestTable.

The VLAN of interface which will be used in testing datagram. 0 means that test will use the PVID of interface. Non-zero value must be within the tagged VLAN list of interface. If ONU can not find the VLAN in the tagged VLAN list of interface, test will fail.

The user name.max size is 64 for epon, 25 for gpon

The password.max size is 32 for EPON, 25 for GPON

The protocol that is used to anthenticate user. Enumeration: 'pap': 3, 'auto': 1, 'chap': 2.

The object is used to start or stop test. start(1) - Start the test. stop(2) - Stop the test. Enumeration: 'start': 1, 'stop': 2.

The status of test. Agent need keep this parameter updated so that manager can get the latest status of test by polling. notStarted(1) - test is not started inProgress(2) - test is in progress success(3) - test is completed successfully failed(4) - test failed. Enumeration: 'failed': 4, 'inProgress': 2, 'notStarted': 1, 'success': 3.

The failed reason of test. none(1) - no error unknownError(2) - unknown error hardwareNotSupport(3) - Hardware does not support the test. notFindVlan(4) - Specified VLAN is not existed. padiTimeOut(5) - PADI request timed out. padrTimeOut(6) - PADR request timed out. lcpNegotiationFail(7) - LCP negotiation failed. userAuthFail(8) - User name or password is invalid. ipNegotiationFail(9) - IP negotiation failed. Enumeration: 'none': 1, 'padrTimeOut': 6, 'lcpNegotiationFail': 7, 'userAuthFail': 8, 'vlanNotExist': 4, 'hardwareNotSupport': 3, 'unknownError': 2, 'ipNegotiationFail': 9, 'padiTimeOut': 5.

The table lists IPoE test entry. the entry indicates the test.

An entry in the zxAnPonRmOnuIpoeTestTable.

IPoE test authentication mode. option60String(1) - authenticate using zxAnPonRmIpoeTestOption60String. usernameAndPassword(2) - authenticate using zxAnPonRmIpoeTestUsername and zxAnPonRmIpoeTestPassword. Enumeration: 'option60String': 1, 'usernameAndPassword': 2.

The user name. This object is valid when zxAnPonRmIpoeTestAuthMode is usernameAndPassword(2).

The password. Max size is 16 for epon and gpon. This object is valid when zxAnPonRmIpoeTestAuthMode is usernameAndPassword(2).

The IPoE test client MAC address.

The option60 for IPoE test. This object is valid when zxAnPonRmIpoeTestAuthMode is option60String(1).

The VLAN id of interface which will be used in testing datagram. 0 means that test will use the PVID of interface. Non-zero value must be within the tagged VLAN list of interface. If ONU can not find the VLAN in the tagged VLAN list of interface, test will fail.

The IPoE test timed out.

Client IP address type.

The IP address that is distributed by BAS when IPoE test is completed successfully.

The gateway IP address type.

The gateway IP address.

The all times for IPoE test ping gateway.

The successful times for IPoE test ping gateway.

The maximum delay for IPoE test ping gateway.

The minimum delay for IPoE test ping gateway.

The average delay for IPoE test ping gateway .

The object is used to start or stop test. start(1) - Start the test. stop(2) - Stop the test. Enumeration: 'start': 1, 'stop': 2.

The status of test. Agent need keep this parameter updated so that manager can get the latest status of test by polling. notStarted(1) - test is not started inProgress(2) - test is in progress success(3) - test is completed successfully failed(4) - test failed Enumeration: 'failed': 4, 'inProgress': 2, 'notStarted': 1, 'success': 3.

The failed reason of test. none(1) - no error ipoeDiscoverTimeOut(2) - IPoE discover timed out. ipoeRequestTimeOut(3) - IPoE request timed out. ipoeAuthFailed(4) - IPoE authentication failed. ipoeUnavailable(5) - IPoE unavailable. ipoeTestTimeOut(6) - IPoE test timed out. unknownError(7) - unknown error vlanNotExist(8) - Specified VLAN is not existed. Enumeration: 'none': 1, 'vlanNotExist': 8, 'ipoeAuthFailed': 4, 'unknownError': 7, 'ipoeUnavailable': 5, 'ipoeDiscoverTimeOut': 2, 'ipoeRequestTimeOut': 3, 'ipoeTestTimeOut': 6.

The table lists callee test entry. The entry indicates a test.

An entry in the zxAnPonRmOnuVoipCalleeTestTable.

The duration of test. Agent should stop test following regular on-hook procedure, if the test hasn't completed after duration yet.

The max ring time of test.

This object indicates the current status of port. idle(1) - The state of port is idle. ringing(2) - The state of port is ringing. offHook(3) - The state of port is off-hook. connected(4) - Voice data path is established. The port can receive and send voice data. busyTone(5) - The port is playing busy tone. onHook(6) - The state of port is on-hook. Enumeration: 'ringing': 2, 'onHook': 6, 'idle': 1, 'busyTone': 5, 'connected': 4, 'offHook': 3.

The object is used to start or stop test. start(1) - Start the test. stop(2) - Stop the test. Agent should stop test following regular on-hook procedure. Enumeration: 'start': 1, 'stop': 2.

The status of test. Agent need keep this parameter updated so that manager can get the latest status of test by polling. notStarted(1) - Test is not started. inProgress(2) - Test is in progress. success(3) - Test is successful. It means that the voice path of call is well, while the on-hook operation is successful. failed(4) - Test failed. Enumeration: 'failed': 4, 'inProgress': 2, 'notStarted': 1, 'success': 3.

The failed reason of test. other(1) - Other reason. noRing(2) - No ringing. noUpstreamVoice(3) - No upstream voice. noDownstreamVoice(4) - No downstream voice. noBidirectionVoice(5) - No upstream and downstream voice. Enumeration: 'noUpstreamVoice': 3, 'other': 1, 'noDownstreamVoice': 4, 'noRing': 2, 'noBidirectionVoice': 5.

The failed detail. This field should be filled when the value of zxAnPonRmCalleeTestFailReason is 'other'.

The table lists caller test entry. The entry indicates a test.

An entry in the zxAnPonRmOnuVoipCallerTestTable.

The time-out of test. Agent should stop test following regular on-hook procedure, if the test hasn't completed after time-out yet.

The number that user dials. The max size is 64 for EPON ,20 for GPON.

This object indicates the current status of port. idle(1) - The state of port is idle. offHook(2) - The state of port is off-hook. dialTone(3) - The port is playing dial tone. receiveNumber(4) - The port is receiving number. receiveEnd(5) - Receiving number ended. ringBackTone(6) - The port is playing ring back tone. connected(7) - Voice data path is established. The port can receive and send voice data. busyTone(8) - The port is playing busy tone. onHook(9) - The state of port is on-hook. Enumeration: 'receiveNumber': 4, 'dialTone': 3, 'onHook': 9, 'receiveEnd': 5, 'idle': 1, 'busyTone': 8, 'connected': 7, 'offHook': 2, 'ringBackTone': 6.

Specifies how long it takes to set up bearer traffic RTP packets for the POTS line being tested in tenths of a second.The delay measure timer starts when the INVITE is generated for a call origination to the phone number specified by the PHONENO parameter in the DGN-SIPDIALTONE TL1 command. The SIP application at the ONU starts listening for RTP packets. If RTP packets are detected, the delay measure timer is stopped and the timer value is recorded for later reporting. Range for measure post dial delay is 0.0 to 6553.5 in tenths of seconds.

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. Enumeration: 'callCancelledByOnt': 7, 'noResponseToInvite': 4, 'callCancelledByServer': 6, 'lineNotInValidState': 9, 'inviteOkButNoBearerData': 2, 'notchFiltersRequired': 11, 'errorCodeAndReasonPhrase': 5, 'lineNotRegistered': 10, 'callTimeoutNo200Ok': 3, 'dialToneTestFailure': 1, 'lineNotConfigured': 8.

The error code of SIP test. This field should be filled when the value of zxAnPonRmCallerTestSipFailReason is 'errorCodeAndReasonPhrase'. unauthorized(1) - 401 Unauthorized. forbidden(2) - 403 Forbidden. notFound(3) - 404 Not found. proxyAuthenticationRequired(4) - 407 Proxy authentication required. requestTimeout(5) - 408 Request timeout. temporarilyUnavailable(6) - 480 Temporarily unavailable. addressIncomplete(7) - 484 Address incomplete. busyHere(8) - 486 Busy here. requestTerminated(9) - 487 Request terminated. notAcceptableHere(10) - 488 Not acceptable here. serverInternalError(11) - 500 Server internal error. serviceUnavailable(12) - 503 Service unavailable. serverTimeout(13) - 504 Server time-out. Enumeration: 'notFound': 3, 'unauthorized': 1, 'busyHere': 8, 'forbidden': 2, 'requestTerminated': 9, 'temporarilyUnavailable': 6, 'proxyAuthenticationRequired': 4, 'addressIncomplete': 7, 'serverInternalError': 11, 'notAcceptableHere': 10, 'serviceUnavailable': 12, 'requestTimeout': 5, 'serverTimeout': 13.

The object is used to start or stop test. start(1) - Start the test. stop(2) - Stop the test. Agent should stop test following regular on-hook procedure. Enumeration: 'start': 1, 'stop': 2.

The status of test. Agent need keep this parameter updated so that manager can get the latest status of test by polling. notStarted(1) - Test is not started. inProgress(2) - Test is in progress. success(3) - Test is successful. It means that the voice path of call is well, while the on-hook operation is successful. failed(4) - Test failed. notForced(5) - Test is not attempted because the POTS line is busy. Enumeration: 'failed': 4, 'inProgress': 2, 'notStarted': 1, 'notForced': 5, 'success': 3.

The failed reason of test. other(1) - Other reason. noDialTone(2) - No dial tone. noRingBack(3) - No ring back tone. noAnswer(4) - No answer. noUpstreamVoice(5) - No upstream voice. noDownstreamVoice(6) - No downstream voice. noBidirectionVoice(7) - No upstream and downstream voice. sipTestFailed(8) - SIP test failed. Enumeration: 'noRingBack': 3, 'noAnswer': 4, 'noUpstreamVoice': 5, 'noDownstreamVoice': 6, 'noDialTone': 2, 'other': 1, 'sipTestFailed': 8, 'noBidirectionVoice': 7.

The failed detail. This field should be filled when the value of zxAnOnuVoipCallerTestFailReason is 'other'.

ONU optical transceivers table.

ONU optical transceivers entry.

ONU optical transceivers speed mode. The following values are valid for GPON: gpon(1): GPON, xgpon(2): XG-PON, xgspon(3): XGS-PON, unknown(255): unknown. The following values are valid for EPON: oneG(11): EPON, oneGAndTenGEpon(12): 1G/10G-EPON, tenGAnd10GEpon(13): 10G/10G-EPON, unknown(255): unknown. Enumeration: 'xgpon': 2, 'unknown': 255, 'gpon': 1, 'tenGAnd10GEpon': 13, 'oneGAndTenGEpon': 12, 'xgspon': 3, 'epon': 11.

ONU optical transceivers ODN type. The following values are valid for GPON: classBplusAndCplus(1): Class B+/C+, n1AndN2aAndE1AndE2a(2): N1/N2a/E1/E2a, n2bAndE2b(3): N2b/E2b, n1AndN2AndE1(4): N1/N2/E1. The following values are valid for EPON: px20(51): PX20, px20plus(52): PX20+, prx30(53): PRX30, pr30(54): PR30, prx40(55): PRX40, pr40(56): PR40, unknown(255): unknown. Enumeration: 'pr40': 56, 'px20plus': 52, 'pr30': 54, 'n1AndN2aAndE1AndE2a': 2, 'n1AndN2AndE1': 4, 'unknown': 255, 'px20': 51, 'n2bAndE2b': 3, 'classBplusAndCplus': 1, 'prx30': 53, 'prx40': 55.

ONU optical transceivers applicable device type. Enumeration: 'unknown': 255, 'on': 1.

ONU optical transceivers encapsulation type. sfpAndsfpplus(1): SFP/SFP+, xfp(2): XFP, unknown(255): unknown. Enumeration: 'xfp': 2, 'sfpAndsfpplus': 1, 'unknown': 255.

ONU optical transceivers transmitted wavelength.

ONU optical transceivers received wavelength.

ONU optical transceivers vendor name.

ONU optical transceivers vendor part number.

ONU optical transceivers vendor serial number.