The allowed dial direction is either incoming(1),
outgoing(2), or both(3) calls. No call is ever set up when set
to incoming(1). Incoming calls will not be identified
when set to outoing(2). Furthermore, once PPP
authentication succeeds and there is at least one incoming
number defined but for which none matches, the call will
not be accepted for security reasons.
Parsed from file mibppp.mib.txt
Company: None
Module: BIANCA-BRICK-PPP-MIB
The allowed dial direction is either incoming(1),
outgoing(2), or both(3) calls. No call is ever set up when set
to incoming(1). Incoming calls will not be identified
when set to outoing(2). Furthermore, once PPP
authentication succeeds and there is at least one incoming
number defined but for which none matches, the call will
not be accepted for security reasons.
Parsed from file BIANCA-BRICK-PPP-MIB.mib
Module: BIANCA-BRICK-PPP-MIB
Vendor: BinTec Communications GmbH
Module: BIANCA-BRICK-PPP-MIB
[Automatically extracted from oidview.com]
biboDialDirection OBJECT-TYPE SYNTAX INTEGER { incoming(1), outgoing(2), both(3) } ACCESS read-write STATUS mandatory DESCRIPTION "The allowed dial direction is either incoming(1), outgoing(2), or both(3) calls. No call is ever set up when set to incoming(1). Incoming calls will not be identified when set to outoing(2). Furthermore, once PPP authentication succeeds and there is at least one incoming number defined but for which none matches, the call will not be accepted for security reasons." ::= { biboDialEntry 3 }
biboDialDirection OBJECT-TYPE SYNTAX INTEGER { incoming(1), outgoing(2), both(3) } ACCESS read-write STATUS mandatory DESCRIPTION "The allowed dial direction is either incoming(1), outgoing(2), or both(3) calls. No call is ever set up when set to incoming(1). Incoming calls will not be identified when set to outoing(2). Furthermore, once PPP authentication succeeds and there is at least one incoming number defined but for which none matches, the call will not be accepted for security reasons." ::= { biboDialEntry 3 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.272.4.4.1.1.1 | biboDialIfIndex | 0 | 0 | The correlating PPP interface index. |
| 1.3.6.1.4.1.272.4.4.1.1.2 | biboDialType | 0 | 0 | The dialup type can be set to plain isdn(1), isdn-spv(2) semi-permanent links used by the German 1TR6 D-channel protocol, or to d… |
| 1.3.6.1.4.1.272.4.4.1.1.4 | biboDialNumber | 0 | 0 | The defined dialing number. Used for either dialing or comparing to incoming calls or both, depending on the content of the biboD… |
| 1.3.6.1.4.1.272.4.4.1.1.5 | biboDialSubaddress | 0 | 0 | The defined dial subaddress, if any. Also, see the biboDialNumber field. |
| 1.3.6.1.4.1.272.4.4.1.1.6 | biboDialClosedUserGroup | 0 | 0 | The defined closed user group, if any. Also, see the biboDialNumber field. |
| 1.3.6.1.4.1.272.4.4.1.1.7 | biboDialStkMask | 0 | 0 | The defined stack mask. Each value of IsdnStkNumber represents a bit in this bitmask. A mask of 0 disables dialup completely, whi… |
| 1.3.6.1.4.1.272.4.4.1.1.8 | biboDialScreening | 0 | 0 | The screening indicator of the biboDialNumber. The biboDialScreening field can be used to gauge the `trustworthiness' of the bibo… |
| 1.3.6.1.4.1.272.4.4.1.1.9 | biboDialCallingSubaddress | 0 | 0 | The defined calling dial subaddress, if any. Also, see the biboDialNumber field. |
| 1.3.6.1.4.1.272.4.4.1.1.10 | biboDialTypeOfCallingSubAdd | 0 | 0 | The type of calling party subaddress. |
| 1.3.6.1.4.1.272.4.4.1.1.11 | biboDialTypeOfCalledSubAdd | 0 | 0 | The type of called party subaddress. |
| 1.3.6.1.4.1.272.4.4.1.1.12 | biboDialLocalNumber | 0 | 0 | The defined local dialing number. Used for either dialing or comparing to incoming calls or both, depending on the content of the… |