The capiPlciTable contains information for each currently
connected CAPI application (i.e. has a Physical Link
Connection Identifier associated with it).
Creating entries: Entries can only be made by the
system. Upon receiving a CAPI_CONNECT_REQ (or
CAPI_CONNECT_IND) message, the system assigns a
unique PLCI (capiPlciNumber) and an entry is made.
Deleting entries: Entries are automatically deleted by
the system once a CAPI_DISCONNECT_RESP message
is received.
Parsed from file mibcapi.mib.txt
Company: None
Module: BIANCA-BRICK-CAPI-MIB
The capiPlciTable contains information for each currently
connected CAPI application (i.e. has a Physical Link
Connection Identifier associated with it).
Creating entries: Entries can only be made by the
system. Upon receiving a CAPI_CONNECT_REQ (or
CAPI_CONNECT_IND) message, the system assigns a
unique PLCI (capiPlciNumber) and an entry is made.
Deleting entries: Entries are automatically deleted by
the system once a CAPI_DISCONNECT_RESP message
is received.
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]
capiPlciTable OBJECT-TYPE SYNTAX SEQUENCE OF CapiPlciEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The capiPlciTable contains information for each currently connected CAPI application (i.e. has a Physical Link Connection Identifier associated with it). Creating entries: Entries can only be made by the system. Upon receiving a CAPI_CONNECT_REQ (or CAPI_CONNECT_IND) message, the system assigns a unique PLCI (capiPlciNumber) and an entry is made. Deleting entries: Entries are automatically deleted by the system once a CAPI_DISCONNECT_RESP message is received." ::= { capi 3 }
capiPlciTable OBJECT-TYPE SYNTAX SEQUENCE OF CapiPlciEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The capiPlciTable contains information for each currently connected CAPI application (i.e. has a Physical Link Connection Identifier associated with it). Creating entries: Entries can only be made by the system. Upon receiving a CAPI_CONNECT_REQ (or CAPI_CONNECT_IND) message, the system assigns a unique PLCI (capiPlciNumber) and an entry is made. Deleting entries: Entries are automatically deleted by the system once a CAPI_DISCONNECT_RESP message is received." ::= { capi 3 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.272.4.7.3.1 | capiPlciEntry | 16 | 16 | 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.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.5 | capiInfoTable | 1 | 8 | The capiInfoTable contains the last 10 CAPI info codes and their message identifiers for where the error occured. The most recent… |
| 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… |