BIANCA-BRICK-CAPI-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for BIANCA-BRICK-CAPI-MIB.
79
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
79 total| Object Name |
|---|
org OBJECT IDENTIFIER .1.3 |
RFC1155-SMI Unknown .1.3 |
dod OBJECT IDENTIFIER .1.3.6 |
internet OBJECT IDENTIFIER .1.3.6.1 |
private OBJECT IDENTIFIER .1.3.6.1.4 |
enterprises OBJECT IDENTIFIER .1.3.6.1.4.1 |
bintec OBJECT IDENTIFIER .1.3.6.1.4.1.272 |
bibo OBJECT IDENTIFIER .1.3.6.1.4.1.272.4 |
capi OBJECT IDENTIFIER .1.3.6.1.4.1.272.4.7 |
capiApplTableThe 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. SEQUENCE OF CapiApplEntry .1.3.6.1.4.1.272.4.7.1 |
capiApplEntry CapiApplEntry .1.3.6.1.4.1.272.4.7.1.1 |
capiApplNumberIdentification number of the registered application.ro INTEGER .1.3.6.1.4.1.272.4.7.1.1.1 |
capiApplVersionThe version number of the registered application.ro Enumeration .1.3.6.1.4.1.272.4.7.1.1.2 |
capiApplByteOrderThe byte order used by the application.ro Enumeration .1.3.6.1.4.1.272.4.7.1.1.3 |
capiApplRegLevel3CntCAPI_REGISTER: The number of level 3 connections
this application accepts.ro INTEGER .1.3.6.1.4.1.272.4.7.1.1.4 |
capiApplRegMsgCntCAPI_REGISTER: The number of registered CAPI
messages this application accepts.ro INTEGER .1.3.6.1.4.1.272.4.7.1.1.5 |
capiApplRegDblkCntCAPI_REGISTER: The number of registered B3 data
blocks this application accepts.ro INTEGER .1.3.6.1.4.1.272.4.7.1.1.6 |
capiApplRegDblkSizeCAPI_REGISTER: The size of registered B3 data
blocks this application accepts.ro INTEGER .1.3.6.1.4.1.272.4.7.1.1.7 |
capiApplInfoStrInformation string of CAPI instance: IP address and TCP port
of connecting system and user name if any.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.272.4.7.1.1.8 |
capiListenTableThe 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. SEQUENCE OF CapiListenEntry .1.3.6.1.4.1.272.4.7.2 |
capiListenEntry CapiListenEntry .1.3.6.1.4.1.272.4.7.2.1 |
capiListenApplicationThe application-number (capiApplNumber).ro INTEGER .1.3.6.1.4.1.272.4.7.2.1.1 |
capiListenControllerThe ISDN controller number. This value refers to the
isdnStkNumber.ro HexValue .1.3.6.1.4.1.272.4.7.2.1.2 |
capiListenServiceMaskThe bit mask of CAPI 1.1 listen services. Specifies
which 1TR6 services to listen for (CAPI 1.1 only).ro HexValue .1.3.6.1.4.1.272.4.7.2.1.3 |
capiListenEazMaskThe bit mask of CAPI 1.1 listen-EAZs (CAPI 1.1 only).ro HexValue .1.3.6.1.4.1.272.4.7.2.1.4 |
capiListenInfoMaskThe 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.ro HexValue .1.3.6.1.4.1.272.4.7.2.1.5 |
capiListenCipMaskThe 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.ro HexValue .1.3.6.1.4.1.272.4.7.2.1.6 |
capiListenCipMask2The bit mask of CAPI 2.0 listen CIPMask.ro HexValue .1.3.6.1.4.1.272.4.7.2.1.7 |
capiPlciTableThe 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. SEQUENCE OF CapiPlciEntry .1.3.6.1.4.1.272.4.7.3 |
capiPlciEntry CapiPlciEntry .1.3.6.1.4.1.272.4.7.3.1 |
capiPlciNumberThe PLCI (physical link connection identifier) of the
application.ro HexValue .1.3.6.1.4.1.272.4.7.3.1.1 |
capiPlciApplicationThe application-number (capiApplNumber).ro INTEGER .1.3.6.1.4.1.272.4.7.3.1.2 |
capiPlciControllerThe ISDN controller number. This value refers to the
isdnStkNumber.ro HexValue .1.3.6.1.4.1.272.4.7.3.1.3 |
capiPlciStateThe current link state as described in the CAPI state
diagram.ro Enumeration .1.3.6.1.4.1.272.4.7.3.1.4 |
capiPlciSelectB2ProtoThe current B2 protocol setting (CAPI 1.1 applications
only).ro Enumeration .1.3.6.1.4.1.272.4.7.3.1.5 |
capiPlciSelectB2DlpdCurrent B2 protocol descriptor. DLPD = data link
protocol descriptor (CAPI 1.1 applications only).ro OCTET STRING .1.3.6.1.4.1.272.4.7.3.1.6 |
capiPlciSelectB3ProtoCurrent B3 protocol setting (CAPI 1.1 applications
only).ro Enumeration .1.3.6.1.4.1.272.4.7.3.1.7 |
capiPlciSelectB3NcpdThe current B3 Ncpd setting. NCPD = network control
protocol descriptor (CAPI 1.1 applications only).ro OCTET STRING .1.3.6.1.4.1.272.4.7.3.1.8 |
capiPlciB1ProtoCurrent CAPI 2.0 B1 protocol setting.ro Enumeration .1.3.6.1.4.1.272.4.7.3.1.9 |
capiPlciB1ConfigCurrent CAPI 2.0 B1 protocol configuration setting.ro OCTET STRING .1.3.6.1.4.1.272.4.7.3.1.10 |
capiPlciB2ProtoCurrent CAPI 2.0 B2 protocol setting.ro Enumeration .1.3.6.1.4.1.272.4.7.3.1.11 |
capiPlciB2ConfigCurrent CAPI 2.0 B2 protocol configuration setting.ro OCTET STRING .1.3.6.1.4.1.272.4.7.3.1.12 |
capiPlciB3ProtoCurrent CAPI 2.0 B3 protocol setting.ro Enumeration .1.3.6.1.4.1.272.4.7.3.1.13 |
capiPlciB3ConfigCurrent CAPI 2.0 B3 protocol configuration setting.ro OCTET STRING .1.3.6.1.4.1.272.4.7.3.1.14 |
capiPlciCipValueThe current CIPValue setting.ro INTEGER .1.3.6.1.4.1.272.4.7.3.1.15 |
capiPlciInfoMaskThe current InfoMask setting.ro HexValue .1.3.6.1.4.1.272.4.7.3.1.16 |
capiNcciTableThe 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. SEQUENCE OF CapiNcciEntry .1.3.6.1.4.1.272.4.7.4 |
capiNcciEntry CapiNcciEntry .1.3.6.1.4.1.272.4.7.4.1 |
capiNcciNumberThe NCCI number assigned by the system.ro HexValue .1.3.6.1.4.1.272.4.7.4.1.1 |
capiNcciApplicationThe application number (capiApplNumber).ro INTEGER .1.3.6.1.4.1.272.4.7.4.1.2 |
capiNcciPlciThe CAPI PLCI number (capiPlciNumber).ro HexValue .1.3.6.1.4.1.272.4.7.4.1.3 |
capiNcciStateThe current state of the NCCI, as described in the
CAPI state diagram.ro Enumeration .1.3.6.1.4.1.272.4.7.4.1.4 |
capiInfoTableThe 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. SEQUENCE OF CapiInfoEntry .1.3.6.1.4.1.272.4.7.5 |
capiInfoEntry CapiInfoEntry .1.3.6.1.4.1.272.4.7.5.1 |
capiInfoApplicationThe application number (capiApplNumber).ro INTEGER .1.3.6.1.4.1.272.4.7.5.1.1 |
capiInfoPlciThe CAPI PLCI number (capiPlciNumber).ro HexValue .1.3.6.1.4.1.272.4.7.5.1.2 |
capiInfoNcciThe NCCI number (capiNcciNumber).ro HexValue .1.3.6.1.4.1.272.4.7.5.1.3 |
capiInfoC1CommandThe CAPI 1.1 command where the info occurred.ro Enumeration .1.3.6.1.4.1.272.4.7.5.1.4 |
capiInfoC2CommandThe CAPI 2.0 command where the info occurred.ro Enumeration .1.3.6.1.4.1.272.4.7.5.1.5 |
capiInfoSubCommandThe CAPI 1.1/2.0 subcommand.ro Enumeration .1.3.6.1.4.1.272.4.7.5.1.6 |
capiInfoNumberThe 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.ro HexValue .1.3.6.1.4.1.272.4.7.5.1.7 |
capiConfigTableThe 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. SEQUENCE OF CapiConfigEntry .1.3.6.1.4.1.272.4.7.6 |
capiConfigEntry CapiConfigEntry .1.3.6.1.4.1.272.4.7.6.1 |
capiConfigStkNumberThe isdnStkNumber this configuration belongs to.ro INTEGER .1.3.6.1.4.1.272.4.7.6.1.1 |
capiConfigFaxG3RcvSpeedThe 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.rw Enumeration .1.3.6.1.4.1.272.4.7.6.1.2 |
capiConfigFaxG3ECMSpecifies whether ECM (error correction mode)
should be used for G3 facsimile transmissions.rw Enumeration .1.3.6.1.4.1.272.4.7.6.1.3 |
capiConfigFaxG3HeaderSpecifies 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.rw Enumeration .1.3.6.1.4.1.272.4.7.6.1.4 |
capiConfigVoiceCodingSwitches the bit order for voice-data.rw Enumeration .1.3.6.1.4.1.272.4.7.6.1.5 |
capiConfigSendAlertingFor CAPI 1.1 this specifies when the CAPI server
should send alert messages for incoming calls.rw Enumeration .1.3.6.1.4.1.272.4.7.6.1.6 |
capiConfigV42bisSpecifies 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.rw Enumeration .1.3.6.1.4.1.272.4.7.6.1.7 |
capiConfigModemDefaultSpecifies the modem profile of the mdmProfileTable
which contains the default modem parameters to use
for modem connections.rw Enumeration .1.3.6.1.4.1.272.4.7.6.1.8 |
capiConfigFaxModulationSet 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 capabilityrw Enumeration .1.3.6.1.4.1.272.4.7.6.1.9 |
capiConfigFax12000Enable or disable the 12000Bps Mode for fax transmission.
A lot of fax receivers have problems with this tranmission
mode. Default value is offrw Enumeration .1.3.6.1.4.1.272.4.7.6.1.10 |
capiConfigFaxTXLevelSet the transmit level to -x dB db0 = 0dB, db3 = -3dB.
In Germany -6dB (db6) is normally used for facsimile
transmission.rw Enumeration .1.3.6.1.4.1.272.4.7.6.1.11 |
capiMultiControllerTableThis 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. SEQUENCE OF CapiMultiControllerEntry .1.3.6.1.4.1.272.4.7.7 |
capiMultiControllerEntry CapiMultiControllerEntry .1.3.6.1.4.1.272.4.7.7.1 |
capiControllerNumberThe controller number requested by the CAPI application.rw INTEGER .1.3.6.1.4.1.272.4.7.7.1.1 |
capiControllerStkMaskThis 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.rw BitValue .1.3.6.1.4.1.272.4.7.7.1.2 |
capiControllerVersionSpecifies which CAPI applications (CAPI version 1.1, or 2.0)
this entry applies to.
Set this field to `delete' to delete this entry.rw Enumeration .1.3.6.1.4.1.272.4.7.7.1.3 |