| Index |
| Unique index of the basic or primary rate interface. |
| Description |
| Textual description of the basic rate interface including its slot and number (e.g. bri2-0 means slot 2, unit 0). Length: 0 to 255 |
| Layer1State |
| The ISDN physical layer state according to I.430 f1(1) = inactive; f2(2) = sensing; f3(3) = deactivated; f4(4) = awaiting signal; f5(5) = identifying input; f6(6) = synchronized; f7(7) = activated; f8(8) = lost framing; g1(9) = deactive; g2(10) = pending activation; g3(11) = active; g4(12) = pending deactivation Enumerations: - f1 (1)
- f2 (2)
- f3 (3)
- f4 (4)
- f5 (5)
- f6 (6)
- f7 (7)
- f8 (8)
- g1 (9)
- g2 (10)
- g3 (11)
- g4 (12)
|
| BchannelControl |
| B-channels are controlled by a call control protocol in the D-channel. Otherwise they may be used as permanent links. Enumerations: - uncontrolled (1)
- controlled (2)
|
| ActivationRequest |
| When this object is set to 'activate' the BRICK will start an activation sequence of ISDN-Layer1 of the basic rate interface. Enumerations: - nooperation (1)
- activate (2)
|
| Mode |
| Specifies the mode of the interface. TE or NT Mode will be set for ISDN interfaces without PABX control. For PRI both NT (network termination) and TE (terminal equipment) modes are supported. If hardware is detected to be in a different state than contained in configuration (and it isn't programmable concerning mode but only changable by means of jumpers), isdnIfOperState becomes failed. Enumerations: - te (1)
- nt (2)
- pabx-terminal (3)
- pabx-trunk (4)
- pabx-tie (5)
|
| TimerT3 |
| Value of Timer T3 in milliseconds.T3 is started whenever ISDNLayer-1 is activated (i.e. Activation Request is started). |
| UsePowerDetector |
| Use the PS1 Power Detector to control the layer 1 automaton.This object is only valid for basic rate interfaces. Enumerations: |
| NumberOfChannels |
| Number of Channels including the D channel, that are available on this ISDN Interface (3 = BRI, 31 = PRI). Range: 1 to 31 |
| Timeouts |
| Number of timeouts of T3 during lifetime of the system. |
| Activates |
| Number of successful activation cycles during lifetime of the system. |
| Deactivates |
| Number of deactivations during lifetime of the system. |
| AutoconfigState |
| Start auto configuration on this ISDN Interface. Auto configuration is a mechanism to automatically detect the attributes of an ISDN interface. This can be done at boot time (if isdnIfAutoConfig is set to 'on') or by manually setting this field to 'start'. Refer to Chapter 3 on Features and Methods. Enumerations: - start (1)
- running (2)
- done (3)
|
| Autoconfig |
| Start Autoconfiguration on this ISDN interface at bootup. Enumerations: |
| LicenseUsage |
| Shows which license type is currently used for this ISDN interface. Enumerations: - none (1)
- missing (2)
- pri (3)
- g703 (4)
- bri (5)
|
| BriIfType |
| For some basic rate ISDN hardware it is possible to switch line interface type between S and U interface by using dedicated header modules. As this hardware property may also influence configuration on higher protocol layers, it is reflected here as well as made permanent when a configuration gets saved. For primary rate interfaces (PRI) this variable has no meaning. Enumerations: |
| AdminState |
| This variable allows for taking an ISDN interface out of/in service w/o having to touch the configuration. Besides, it is possible to initiate a reconfiguration for that interface in case a mismatch in configuration parameters (hardware vs. software) was detected. Inconsistencies with the need of reconfiguration are differing - isdnIfMode (te/nt), and/or - isdnIfBriIfType (s/u) In case of mismatch, contents of mentioned variabled might be wrong and this circumstance is reflected in variable isdnIfOperState. State reconfig may then be used in order to cause an update of these variable as appropriate which ... - will be signalled to higher protocol layers, and - can result in extensive reconfiguration steps The latter may also cover clean-ups undoable by system so this decision is left to the user. Default value is down. Enumerations: - down (1)
- up (2)
- reconfig (3)
|
| OperState |
| The operational state of an interface is indicated via this variable. Possible values are: - down(1), - running(2), - fail(3), - stopped(4), - stopping(5), - starting(6) The latter two states being of transitional type, mainly for hot-plug type hardware, and won't be normally seen by user. State fail is used to reflect inconsistencies between hardware state and configuration concerning interface mode (isdnIfMode) and, for basic rate interfaces, type (isdnIfBriType). Enumerations: - down (1)
- running (2)
- fail (3)
- stopped (4)
- stopping (5)
- starting (6)
|
| Slips |
| Slip conditions detected since startup. Flags that the frequency of receive clock is different than frequency of internal system clock. |