This value specifies whether the extension should be used as a default
extension (for outgoing calls) for the associated terminal. The flag to
be set currently only makes sense for physical analog terminals.
The case that this flag is yes(1) for more than one extension per terminal
is considered a configuration error. Which extension will be used in that
case depends on the order in which extensions are configured
(automatically at system start-up) and, hence, is undefined.
Parsed from file mibpabx.mib.txt
Company: None
Module: BIANCA-BOX-PABX-MIB
This value specifies whether the extension should be used as a default
extension (for outgoing calls) for the associated terminal. The flag to
be set currently only makes sense for physical analog terminals.
The case that this flag is yes(1) for more than one extension per terminal
is considered a configuration error. Which extension will be used in that
case depends on the order in which extensions are configured
(automatically at system start-up) and, hence, is undefined.
Parsed from file BIANCA-BOX-PABX-MIB.mib
Module: BIANCA-BOX-PABX-MIB
Vendor: BinTec Communications GmbH
Module: BIANCA-BOX-PABX-MIB
[Automatically extracted from oidview.com]
pabxExtDefaultExtFlag OBJECT-TYPE SYNTAX INTEGER { no(1), yes(2) } ACCESS read-write STATUS mandatory DESCRIPTION "This value specifies whether the extension should be used as a default extension (for outgoing calls) for the associated terminal. The flag to be set currently only makes sense for physical analog terminals. The case that this flag is yes(1) for more than one extension per terminal is considered a configuration error. Which extension will be used in that case depends on the order in which extensions are configured (automatically at system start-up) and, hence, is undefined." ::= { pabxExtensionEntry 14 }
pabxExtDefaultExtFlag OBJECT-TYPE SYNTAX INTEGER { no(1), yes(2) } ACCESS read-write STATUS mandatory DESCRIPTION "This value specifies whether the extension should be used as a default extension (for outgoing calls) for the associated terminal. The flag to be set currently only makes sense for physical analog terminals. The case that this flag is yes(1) for more than one extension per terminal is considered a configuration error. Which extension will be used in that case depends on the order in which extensions are configured (automatically at system start-up) and, hence, is undefined." ::= { pabxExtensionEntry 14 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.272.4.20.4.1.1 | pabxExtExtension | 0 | 0 | This object contains the extension, which is a dialable string consisting of the digits 0..9, * and #. |
| 1.3.6.1.4.1.272.4.20.4.1.2 | pabxExtType | 0 | 0 | Specifies the call types, for which the entry shall be valid. |
| 1.3.6.1.4.1.272.4.20.4.1.6 | pabxExtIpAddr | 0 | 0 | Specifies the ip-address, to which the call shall be routed if pabxExtDestination is set to internet-telephony. |
| 1.3.6.1.4.1.272.4.20.4.1.8 | pabxExtEAZ | 0 | 0 | The EAZ is to be used by 1TR6-based applications such as CAPI 1.1. and is only valid if the object pabxExtDestination is set to a… |
| 1.3.6.1.4.1.272.4.20.4.1.9 | pabxExtLayer1Prot | 0 | 0 | The layer1 protocol to be used for multiprotocol-routing (incoming calls only). |
| 1.3.6.1.4.1.272.4.20.4.1.10 | pabxExtIfIndex | 0 | 0 | The interface index of the MPR interface to be used for the call. This object is valid for routing only. |
| 1.3.6.1.4.1.272.4.20.4.1.11 | pabxExtId | 0 | 0 | The id uniquely identifies an extension may be within the range from 0 to 2147483647. This id is used to refer to that extension … |
| 1.3.6.1.4.1.272.4.20.4.1.12 | pabxExtUserId | 0 | 0 | This identificator refers to the user the extension is associated with. Its default value is 0 meaning no particular user. |
| 1.3.6.1.4.1.272.4.20.4.1.13 | pabxExtTermId | 0 | 0 | This identificator refers to the terminal the extension is associated with. Its value must be a valid identificator, i.e. there m… |
| 1.3.6.1.4.1.272.4.20.4.1.15 | pabxExtPresentationNr | 0 | 0 | This field allows for specifying an extension that will be presented to externally called partners instead of the actual calling… |
| 1.3.6.1.4.1.272.4.20.4.1.16 | pabxExtOutsideCallSeq | 0 | 0 | Set the ringing sequence for incoming calls from outside |
| 1.3.6.1.4.1.272.4.20.4.1.17 | pabxExtInsideCallSeq | 0 | 0 | Set the ringing sequence for incoming calls inside the PABX. |
| 1.3.6.1.4.1.272.4.20.4.1.18 | pabxExtPresentationFlag | 0 | 0 | Specify when the presentation number should take effect. By default its value is 'off' defining the actual extension is to be use… |
| 1.3.6.1.4.1.272.4.20.4.1.19 | pabxExtProfileId | 0 | 0 | ProfileId holds an id specifying an applying profile entry in pabx profile table. If set to 0 no profile applies as 0 is not a va… |
| 1.3.6.1.4.1.272.4.20.4.1.20 | pabxExtCtrlByCapiApp | 0 | 0 | CtrlByCapiAppl indicates whether a capi application controls this extension. If set to on a special CAPI application registered f… |
| 1.3.6.1.4.1.272.4.20.4.1.21 | pabxExtCtrlByCapiAppNo | 0 | 0 | CtrlByCapiAppl indicates capi application number that controls extension in case pabxExtCtrlByCapiApp is set to on. |