The capiInfoTable contains the last 10 CAPI info codes
and their message identifiers for where the error occured.
The most recent message is at inx 09 with older messages
rolling off the top of the table, i.e. inx 00.
Creating entries: Entries are created automatically by
the system once a CAPI info code is received by a
registered application.
Deleting entries: Entries are removed automatically
by the system.
Parsed from file mibcapi.mib.txt
Company: None
Module: BIANCA-BRICK-CAPI-MIB
The capiInfoTable contains the last 10 CAPI info codes
and their message identifiers for where the error occured.
The most recent message is at inx 09 with older messages
rolling off the top of the table, i.e. inx 00.
Creating entries: Entries are created automatically by
the system once a CAPI info code is received by a
registered application.
Deleting entries: Entries are removed automatically
by the system.
Parsed from file BIANCA-BRICK-CAPI-MIB.mib
Module: BIANCA-BRICK-CAPI-MIB
Vendor: BinTec Communications GmbH
Module: BIANCA-BRICK-CAPI-MIB
[Automatically extracted from oidview.com]
capiInfoTable OBJECT-TYPE SYNTAX SEQUENCE OF CapiInfoEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The capiInfoTable contains the last 10 CAPI info codes and their message identifiers for where the error occured. The most recent message is at inx 09 with older messages rolling off the top of the table, i.e. inx 00. Creating entries: Entries are created automatically by the system once a CAPI info code is received by a registered application. Deleting entries: Entries are removed automatically by the system." ::= { capi 5 }
capiInfoTable OBJECT-TYPE SYNTAX SEQUENCE OF CapiInfoEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The capiInfoTable contains the last 10 CAPI info codes and their message identifiers for where the error occured. The most recent message is at inx 09 with older messages rolling off the top of the table, i.e. inx 00. Creating entries: Entries are created automatically by the system once a CAPI info code is received by a registered application. Deleting entries: Entries are removed automatically by the system." ::= { capi 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.272.4.7.5.1 | capiInfoEntry | 7 | 7 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.272.4.7.1 | capiApplTable | 1 | 9 | The capiApplTable contains information for all currently registered CAPI 1.1 and CAPI 2.0 applications, and their respective CAPI… |
| 1.3.6.1.4.1.272.4.7.2 | capiListenTable | 1 | 8 | The capiListenTable contains the listen settings for each CAPI application. Creating entries: Entries can only be created by the s… |
| 1.3.6.1.4.1.272.4.7.3 | capiPlciTable | 1 | 17 | The capiPlciTable contains information for each currently connected CAPI application (i.e. has a Physical Link Connection Identif… |
| 1.3.6.1.4.1.272.4.7.4 | capiNcciTable | 1 | 5 | The capiNcciTable contains information for each CAPI NCCI (network control connection identifier). An NCCI describes a logical co… |
| 1.3.6.1.4.1.272.4.7.6 | capiConfigTable | 1 | 12 | The capiConfigTable contains configuration information for each ISDN stack. Setting these fields is optional, and is not required… |
| 1.3.6.1.4.1.272.4.7.7 | capiMultiControllerTable | 1 | 4 | This table contains mappings between controller numbers used by CAPI applications and the ISDN stacks available on the BRICK (i.e… |
| 1.3.6.1.4.1.272.4.7.8 | capiUserTable | 1 | 4 | The capiUserTable contains information about the capi users. CAPI users must authenticate to the system by means of user name and… |