BIANCA-BRICK-CAPI-MIB

All MIBs › BIANCA-BRICK-CAPI-MIB

Category: Telephony and VoIP, Vendor: bintec

Description: Manages CAPI (Common ISDN API) application connections and ISDN channel usage on bintec BIANCA/BRICK routers.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is BIANCA-BRICK-CAPI-MIB?

BIANCA-BRICK-CAPI-MIB is a legacy BinTec/BiAnca (enterprise OID 272, Brick router family, built on BIANCA-BRICK-PPP-MIB) proprietary MIB reporting registered CAPI (Common ISDN API) application state. Its application table, keyed by number (auto-assigned on CAPI_REGISTER, auto-removed on release), records version, byte order, registered Level-3/message/data-block counts and size, and an info string, while a listen table records per-application controller/service/EAZ/info/CIP masks, and a PLCI (Physical Link Connection Identifier) table records application, controller, and state. As a status MIB it lets an administrator confirm which CAPI applications are registered and their ISDN call state on a legacy BiAnca (BinTec) Brick router. It is deployed on legacy BiAnca (BinTec) Brick router equipment (CAPI/ISDN). Engineers can download the BIANCA-BRICK-CAPI-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in BIANCA-BRICK-CAPI-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Legacy BiAnca (BinTec) Brick router equipment (CAPI/ISDN)

Monitoring Examples

An administrator checks capiApplTable and capiPlciState to confirm which CAPI applications are registered and their ISDN call state on a legacy BiAnca (BinTec) Brick router.

What Can Be Monitored

registered CAPI application state and ISDN call state

Imported Objects

From BIANCA-BRICK-PPP-MIB

BitValue

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter

From SNMPv2-TC

DisplayString

OIDs

OID symbolic	OID numeric	Type	Access	Description
bibo	1.3.6.1.4.1.272.4
bintec	1.3.6.1.4.1.272
capi	1.3.6.1.4.1.272.4.7
INT capiApplByteOrder	1.3.6.1.4.1.272.4.7.1.1.3	INTEGER	read-only	The byte order used by the application.
capiApplEntry	1.3.6.1.4.1.272.4.7.1.1		not-accessible
STR capiApplInfoStr	1.3.6.1.4.1.272.4.7.1.1.8	DisplayString	read-only	Information string of CAPI instance: IP address and TCP port of connecting system and user name if any.
INT capiApplNumber	1.3.6.1.4.1.272.4.7.1.1.1	INTEGER	read-only	Identification number of the registered application.
INT capiApplRegDblkCnt	1.3.6.1.4.1.272.4.7.1.1.6	INTEGER	read-only	CAPI_REGISTER: The number of registered B3 data blocks this application accepts.
INT capiApplRegDblkSize	1.3.6.1.4.1.272.4.7.1.1.7	INTEGER	read-only	CAPI_REGISTER: The size of registered B3 data blocks this application accepts.
INT capiApplRegLevel3Cnt	1.3.6.1.4.1.272.4.7.1.1.4	INTEGER	read-only	CAPI_REGISTER: The number of level 3 connections this application accepts.
INT capiApplRegMsgCnt	1.3.6.1.4.1.272.4.7.1.1.5	INTEGER	read-only	CAPI_REGISTER: The number of registered CAPI messages this application accepts.
capiApplTable	1.3.6.1.4.1.272.4.7.1		not-accessible	The capiApplTable contains information for all currently registered CAPI 1.1 and CAPI 2.0 applications, and their respective CAPI_REGISTER information. Creating entries: Entries are created automatically by the system. After receiving an appropriate CAPI_REGISTER call, the system 'registers' the application, and assigns it a unique capiApplNumber. Deleting entries: Once an application releases, entries are automatically removed by the system.
INT capiApplVersion	1.3.6.1.4.1.272.4.7.1.1.2	INTEGER	read-only	The version number of the registered application.
capiConfigEntry	1.3.6.1.4.1.272.4.7.6.1		not-accessible
INT capiConfigFax12000	1.3.6.1.4.1.272.4.7.6.1.10	INTEGER	read-write	Enable or disable the 12000Bps Mode for fax transmission. A lot of fax receivers have problems with this tranmission mode. Default value is off
INT capiConfigFaxG3ECM	1.3.6.1.4.1.272.4.7.6.1.3	INTEGER	read-write	Specifies whether ECM (error correction mode) should be used for G3 facsimile transmissions.
INT capiConfigFaxG3Header	1.3.6.1.4.1.272.4.7.6.1.4	INTEGER	read-write	Specifies whether the header-line and logo ('BIANCA/FAX'), should appear on outgoing facsimiles. The value 'logo_header' allows the header-line and the logo to be printed on the top of each page.
INT capiConfigFaxG3RcvSpeed	1.3.6.1.4.1.272.4.7.6.1.2	INTEGER	read-write	The G3 facsimile receive speed. For CM-EBRI this should be set to maximum. Set this field to `delete' to remove this entry. The entry can be deleted only if there is no entry with it's capiConfigStkNumber in the isdnStkTable.
INT capiConfigFaxModulation	1.3.6.1.4.1.272.4.7.6.1.9	INTEGER	read-write	Set the default transmission protocol for fax. - v17 max. 14400 Bps new standard - v33 max. 14000 Bps early standard - v29 max. 9600 Bps fax standard - v17s v17 with Swiss capability - v33s v33 with Swiss capability
INT capiConfigFaxTXLevel	1.3.6.1.4.1.272.4.7.6.1.11	INTEGER	read-write	Set the transmit level to -x dB db0 = 0dB, db3 = -3dB. In Germany -6dB (db6) is normally used for facsimile transmission.
INT capiConfigModemDefault	1.3.6.1.4.1.272.4.7.6.1.8	INTEGER	read-write	Specifies the modem profile of the mdmProfileTable which contains the default modem parameters to use for modem connections.
INT capiConfigSendAlerting	1.3.6.1.4.1.272.4.7.6.1.6	INTEGER	read-write	For CAPI 1.1 this specifies when the CAPI server should send alert messages for incoming calls.
INT capiConfigStkNumber	1.3.6.1.4.1.272.4.7.6.1.1	INTEGER	read-only	The isdnStkNumber this configuration belongs to.
capiConfigTable	1.3.6.1.4.1.272.4.7.6		not-accessible	The capiConfigTable contains configuration information for each ISDN stack. Setting these fields is optional, and is not required. Creating entries: Entries are created automatically by the system when a new ISDN stack is initialised in the isdnStkTable. Deleting entries: An entry can be removed by assigning the value `delete' to its capiConfigFaxG3RcvSpeed object. It can be removed only if there is no entry with it's capiConfigStkNumber in the isdnStkTable.
INT capiConfigV42bis	1.3.6.1.4.1.272.4.7.6.1.7	INTEGER	read-write	Specifies whether V.42bis data compression should be used. If data compression is activated here,the receiving or sending side is first queried whether it supports data compression. The BRICK supports V.42bis data compression using up to 2 B-channels.
INT capiConfigVoiceCoding	1.3.6.1.4.1.272.4.7.6.1.5	INTEGER	read-write	Switches the bit order for voice-data.
INT capiControllerNumber	1.3.6.1.4.1.272.4.7.7.1.1	INTEGER	read-write	The controller number requested by the CAPI application.
BIT capiControllerStkMask	1.3.6.1.4.1.272.4.7.7.1.2	BitValue	read-write	This binary number defines the ISDN stack(s) to use for the specified CAPI 1.1 or CAPI 2.0 applications. For example; `Number=1 StkMask=0b1111 Version=capi20' means: allow CAPI 2.0 applications requesting ISDN controller 1 to use the ISDN stacks with IsdnStkNumber 0 - 3 on the BRICK.
INT capiControllerVersion	1.3.6.1.4.1.272.4.7.7.1.3	INTEGER	read-write	Specifies which CAPI applications (CAPI version 1.1, or 2.0) this entry applies to. Set this field to `delete' to delete this entry.
INT capiInfoApplication	1.3.6.1.4.1.272.4.7.5.1.1	INTEGER	read-only	The application number (capiApplNumber).
INT capiInfoC1Command	1.3.6.1.4.1.272.4.7.5.1.4	INTEGER	read-only	The CAPI 1.1 command where the info occurred.
INT capiInfoC2Command	1.3.6.1.4.1.272.4.7.5.1.5	INTEGER	read-only	The CAPI 2.0 command where the info occurred.
capiInfoEntry	1.3.6.1.4.1.272.4.7.5.1		not-accessible
HEX capiInfoNcci	1.3.6.1.4.1.272.4.7.5.1.3	HexValue	read-only	The NCCI number (capiNcciNumber).
HEX capiInfoNumber	1.3.6.1.4.1.272.4.7.5.1.7	HexValue	read-only	The info value as specified in the CAPI 1.1/2.0 specification. See Appendix A for a listing of CAPI 1.1 and CAPI 2.0 info values.
HEX capiInfoPlci	1.3.6.1.4.1.272.4.7.5.1.2	HexValue	read-only	The CAPI PLCI number (capiPlciNumber).
INT capiInfoSubCommand	1.3.6.1.4.1.272.4.7.5.1.6	INTEGER	read-only	The CAPI 1.1/2.0 subcommand.
capiInfoTable	1.3.6.1.4.1.272.4.7.5		not-accessible	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.
INT capiListenApplication	1.3.6.1.4.1.272.4.7.2.1.1	INTEGER	read-only	The application-number (capiApplNumber).
HEX capiListenCipMask	1.3.6.1.4.1.272.4.7.2.1.6	HexValue	read-only	The bit mask of CAPI 2.0 listen CIPMask. The purpose of the CIPMask parameter is to select basic classes of incoming calls. CAPI 2.0 applications only.
HEX capiListenCipMask2	1.3.6.1.4.1.272.4.7.2.1.7	HexValue	read-only	The bit mask of CAPI 2.0 listen CIPMask.
HEX capiListenController	1.3.6.1.4.1.272.4.7.2.1.2	HexValue	read-only	The ISDN controller number. This value refers to the isdnStkNumber.
HEX capiListenEazMask	1.3.6.1.4.1.272.4.7.2.1.4	HexValue	read-only	The bit mask of CAPI 1.1 listen-EAZs (CAPI 1.1 only).
capiListenEntry	1.3.6.1.4.1.272.4.7.2.1		not-accessible
HEX capiListenInfoMask	1.3.6.1.4.1.272.4.7.2.1.5	HexValue	read-only	The bit mask of the CAPI 1.1/2.0 listen InfoMask setting. The purpose of infomask is to specify the type of information for a physical connection or controller which will be provided by CAPI.
HEX capiListenServiceMask	1.3.6.1.4.1.272.4.7.2.1.3	HexValue	read-only	The bit mask of CAPI 1.1 listen services. Specifies which 1TR6 services to listen for (CAPI 1.1 only).
capiListenTable	1.3.6.1.4.1.272.4.7.2		not-accessible	The capiListenTable contains the listen settings for each CAPI application. Creating entries: Entries can only be created by the system and is performed automatically upon receiving a CAPI_LISTEN_REQ message. Deleting entries: Entries are automatically removed by the system once the application releases.
capiMultiControllerEntry	1.3.6.1.4.1.272.4.7.7.1		not-accessible
capiMultiControllerTable	1.3.6.1.4.1.272.4.7.7		not-accessible	This table contains mappings between controller numbers used by CAPI applications and the ISDN stacks available on the BRICK (i.e., the Number field of the isdnStkTable). The Version field specifies whether an entry applies to CAPI 1.1 or CAPI 2.0 applications. If a CAPI 1.1 entry is not defined, CAPI 1.1 applications can only use isdnStkNumber N if N is the controller number requested by the application. If a CAPI 2.0 entry is not defined, CAPI 2.0 applications can only use isdnStkNumber N-1 if N is the controller number requested by the application. Creating entries: Entries are created by assigning a value to the capiControllerNumber object. Deleting entries: An entry can be removed by assigning the value `delete' to its capiControllerVersion object.
INT capiNcciApplication	1.3.6.1.4.1.272.4.7.4.1.2	INTEGER	read-only	The application number (capiApplNumber).
capiNcciEntry	1.3.6.1.4.1.272.4.7.4.1		not-accessible
HEX capiNcciNumber	1.3.6.1.4.1.272.4.7.4.1.1	HexValue	read-only	The NCCI number assigned by the system.
HEX capiNcciPlci	1.3.6.1.4.1.272.4.7.4.1.3	HexValue	read-only	The CAPI PLCI number (capiPlciNumber).
INT capiNcciState	1.3.6.1.4.1.272.4.7.4.1.4	INTEGER	read-only	The current state of the NCCI, as described in the CAPI state diagram.
capiNcciTable	1.3.6.1.4.1.272.4.7.4		not-accessible	The capiNcciTable contains information for each CAPI NCCI (network control connection identifier). An NCCI describes a logical connection on level 3. Several NCCIs operating on the same PLCI may exist. Creating entries: As soon as a CAPI_CONNECT_B3_REQ (or CAPI_CONNECT_B3_IND) message is received, the system creates an entry by assigning the application a unique capiNcciNumber. Deleting entries: Entries are automatically deleted by the system once a CAPI_DISCONNECT_B3_RESP message is received.
INT capiPlciApplication	1.3.6.1.4.1.272.4.7.3.1.2	INTEGER	read-only	The application-number (capiApplNumber).
OCT capiPlciB1Config	1.3.6.1.4.1.272.4.7.3.1.10	OCTET STRING	read-only	Current CAPI 2.0 B1 protocol configuration setting.
INT capiPlciB1Proto	1.3.6.1.4.1.272.4.7.3.1.9	INTEGER	read-only	Current CAPI 2.0 B1 protocol setting.
OCT capiPlciB2Config	1.3.6.1.4.1.272.4.7.3.1.12	OCTET STRING	read-only	Current CAPI 2.0 B2 protocol configuration setting.
INT capiPlciB2Proto	1.3.6.1.4.1.272.4.7.3.1.11	INTEGER	read-only	Current CAPI 2.0 B2 protocol setting.
OCT capiPlciB3Config	1.3.6.1.4.1.272.4.7.3.1.14	OCTET STRING	read-only	Current CAPI 2.0 B3 protocol configuration setting.
INT capiPlciB3Proto	1.3.6.1.4.1.272.4.7.3.1.13	INTEGER	read-only	Current CAPI 2.0 B3 protocol setting.
INT capiPlciCipValue	1.3.6.1.4.1.272.4.7.3.1.15	INTEGER	read-only	The current CIPValue setting.
HEX capiPlciController	1.3.6.1.4.1.272.4.7.3.1.3	HexValue	read-only	The ISDN controller number. This value refers to the isdnStkNumber.
capiPlciEntry	1.3.6.1.4.1.272.4.7.3.1		not-accessible
HEX capiPlciInfoMask	1.3.6.1.4.1.272.4.7.3.1.16	HexValue	read-only	The current InfoMask setting.
HEX capiPlciNumber	1.3.6.1.4.1.272.4.7.3.1.1	HexValue	read-only	The PLCI (physical link connection identifier) of the application.
OCT capiPlciSelectB2Dlpd	1.3.6.1.4.1.272.4.7.3.1.6	OCTET STRING	read-only	Current B2 protocol descriptor. DLPD = data link protocol descriptor (CAPI 1.1 applications only).
INT capiPlciSelectB2Proto	1.3.6.1.4.1.272.4.7.3.1.5	INTEGER	read-only	The current B2 protocol setting (CAPI 1.1 applications only).
OCT capiPlciSelectB3Ncpd	1.3.6.1.4.1.272.4.7.3.1.8	OCTET STRING	read-only	The current B3 Ncpd setting. NCPD = network control protocol descriptor (CAPI 1.1 applications only).
INT capiPlciSelectB3Proto	1.3.6.1.4.1.272.4.7.3.1.7	INTEGER	read-only	Current B3 protocol setting (CAPI 1.1 applications only).
INT capiPlciState	1.3.6.1.4.1.272.4.7.3.1.4	INTEGER	read-only	The current link state as described in the CAPI state diagram.
capiPlciTable	1.3.6.1.4.1.272.4.7.3		not-accessible	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.
dod	1.3.6
enterprises	1.3.6.1.4.1
internet	1.3.6.1
org	1.3
private	1.3.6.1.4

RFC description

BinTec BIANCA/BRICK CAPI subsystem management MIB. Monitors and manages CAPI 1.1 and CAPI 2.0 application registration and status.

Start monitoring bintec BIANCA/BRICK ISDN/VPN routers (legacy) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download BIANCA-BRICK-CAPI-MIB

What Is BIANCA-BRICK-CAPI-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description