BIANCA-BOX-PABX-MIB: View SNMP OID List / Download MIB

The pabxUserTable contains information about the pabx users. CAPI and TAPI users must authenticate to the system by means of user name and password, before active or passive connections may be established. The default configuration defines a user named with all permissions. This user will also be used by old CAPI applications which are not able to select a user. Please note, that the password for the user must be empty in this case. Entries in this table can be deleted by setting the object pabxUserTapiMon to the value .

The name of the user.

The password for the user.

Allow or deny monitoring of call activity with TAPI or delete entry. Enumeration: 'enable': 1, 'disable': 2, 'delete': 3.

Allow or deny controlling of calls for the terminal belonging to the user with TAPI. Enumeration: 'enable': 1, 'disable': 2.

Allow or deny the usage of TAPI media streams. Enumeration: 'enable': 1, 'disable': 2.

Allow or deny the usage of CAPI. Enumeration: 'enable': 1, 'disable': 2.

The user id uniquely identifies a user and is now used as reference to that user in other tables instead of her name. The id 0 has the meaning 'no special user'.

The PIN is the personal identification number that is needed for authorisation during telephone based configurations. It consists solely of digits and must be between 4 and 9 characters long. Default Value is '0000'.

PrimGroupId is the primary group identification number for that user. It serves only for configuration purposes so that all newly created extensions for a terminal that user is primary user of, will automatically become member in that group. The default value is 0.

This table contains an entry for each trunk-line (or central office line) connecting the system to an outside network. Entries are deleted from this table by setting the object pabxTrunkProtocol to the value .

The object pabxTrunkNumber ranges from 0..31 and specifies a unique identification for the trunk line.

Description text for the trunk-line. This object is for information only and not otherwise being used by the system.

This object specifies the number of the physical slot the trunk-line is leading to.

This object specifies the physical unit in the slot specified by pabxTrunkSlot. When there is only one unit in the slot, the unitnumber has to be set to 0.

This object specifies the protocol to be used on the trunk-line. Currently only dss1 is available. Enumeration: 'dss1': 2, 'delete': 1.

This object specifies, whether the trunk line is running in point-to-point or point-to-multipoint configuration. Enumeration: 'point-to-multipoint': 1, 'point-to-point': 2, 'unknown': 3.

This object specifies the TEI procedure to be used with the trunk-line. The procedure may be either or . In the latter case, the TEI value has to be specified in the object pabxTrunkTeiValue Enumeration: 'fixed': 2, 'automatic': 1.

This object specifies the TEI value to be used for fixed TEI configurations and is ignored in automatic TEI configurations.

This object specifies the country code of the trunk-line. This information has to be specified in point-to-point configurations, because the country code has to be skipped in the destination address of incoming calls in order to isolate the local extension part.

This object specifies the area code of the trunk-line. This information has to be specified in point-to-point configurations, because the area code has to be skipped in the destination address of incoming calls in order to isolate the local extension part.

This object specifies the subscriber number of the trunk-line. This information has to be specified in point-to-point configurations, because the subscriber number has to be skipped in the destination address of incoming calls in order to isolate the local extension part.

This object specifies the extension number of the trunk-line. This information has to be specified in point-to-point configurations, because the extension number has to be skipped in the destination address of incoming calls in order to isolate the local extension part. Please note, that this object shall be empty, when connected to a normal central office line.

The trunk type identifies the purpose of an ISDN interface. Normal external trunks are identified with type 'external'. When cascading trunks one side must behave as network side and, hence, a trunk entry must be created for it, despite of operating in NT (actually NT or LTS) mode. This is achieved by creating a trunk of type 'internal'. Internal trunks are always point to point type interfaces. Type 'external' is assumed by default. Enumeration: 'internal': 2, 'external': 1.

The TrunkL2Mode specifies the mode layer 2 is to operate in. To be able to use leased lines as well as back to back connections to link two machines, layer 2 mode must be configurable independently from layer 1 mode. If mode is set to auto(1), layer 2 mode is derived from physical configuration of interface (NT/TE). Settings te(2) and nt(3) force the respective configuration. By default mode is set to 'auto'. Enumeration: 'auto': 1, 'te': 2, 'nt': 3.

This table specifies escape codes, that may be used to access the available trunk-lines. Initially, the prefix <0> will be defined to use any trunk line in the system. Please note, that this table is only used, when The global object pabxLocalPrefix is set to an empty string. Entries in this table are deleted by setting the object pabxTrunkPrefixStatus to the value

This object specifies a prefix used to access (a subset of) the available trunk-lines. It's value is a string consisting of the dialable digits 0..9, * and #.

This object is a bit mask consisting of bit 0 to bit 31. Each bit corresponds to the trunk-line index with the same number (Bit 0 <-> Number 0 ...). The whole mask specifies the set of trunk lines to be used with the trunk-prefix.

This object specifies the status of the trunk-prefix. When set to valid, the trunk prefix will be used normally, when set to invalid, the prefix will not be used and when set to delete, the table-entry will be deleted. Enumeration: 'valid': 1, 'invalid': 2, 'delete': 3.

This object specifies handling of trunk-prefix on outgoing calls: When set to enable (by default) the trunk prefix will be stripped on outgoing calls, what must be set for external trunks (otherwise a wrong called party number would be passed on). When set to disable, the prefix will remain in the called party number, allowing a distributed PABX via internal trunks. Enumeration: 'enable': 1, 'disable': 2.

This object specifies handling of trunk-prefix on incoming calls: When set to enable (by default) the trunk prefix will be appended to the calling party number on incoming calls, what must be set for external trunks (otherwise a wrong calling party number would be provided, hence leading to the calling party number being unusable for a call back). When set to disable, no prefix will be prepended to the calling party number, nedded for a distributed PABX via internal trunks. Enumeration: 'enable': 1, 'disable': 2.

This table defines the local numbers (extensions), that shall be used within PABX and assigns an identifier to it. Besides the extension is assigned to a terminal and user via apropriate identifiers and to either a physical or a logical destination. The items pabxExtSlot and pabxExtUnit moved to the terminal table as every extension must be associated with a terminal and, moreover, a terminal is always as a whole physically attached to a slot and unit. Also pabxExtUser is no longer valid, because the associated user is now refered to via the pabxExtUserId, avoiding some possible configuration faults. Rows are deleted from the table by setting the object pabxExtDestination to the value .

This object contains the extension, which is a dialable string consisting of the digits 0..9, * and #.

Specifies the call types, for which the entry shall be valid. Enumeration: 'voice': 1, 'data': 2, 'voice-and-data': 3, 'delete': 4.

Specifies the ip-address, to which the call shall be routed if pabxExtDestination is set to internet-telephony.

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 application.

The layer1 protocol to be used for multiprotocol-routing (incoming calls only). Enumeration: 'v110-2400': 16, 'modem': 13, 'modem-profile-7': 32, 'v110-4800': 17, 'auto': 1, 'v110-38400': 21, 'modem-profile-1': 26, 'v110-9600': 18, 'modem-profile-6': 31, 'v110-1200': 15, 'modem-profile-4': 29, 'modem-profile-5': 30, 'v110-14400': 19, 'modem-profile-3': 28, 'v110-19200': 20, 'modem-profile-2': 27, 'sync-56k': 12, 'sync-64k': 11, 'modem-profile-8': 33.

The interface index of the MPR interface to be used for the call. This object is valid for routing only.

The id uniquely identifies an extension may be within the range from 0 to 2147483647. This id is used to refer to that extension from other tables. Id 0 has the special meaning, that the PABX shall choose a valid one.

This identificator refers to the user the extension is associated with. Its default value is 0 meaning no particular user.

This identificator refers to the terminal the extension is associated with. Its value must be a valid identificator, i.e. there must be a terminal with the given id. The special number -1 is used for specifying that the extension is a group extension.

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. Enumeration: 'yes': 2, 'no': 1.

This field allows for specifying an extension that will be presented to externally called partners instead of the actual calling number. Hence it allows to use a group extension so that the called partner does only see the extension she should use for call back if necessary, rather than the extension within the group. Default value is the empty string meaning that no mapping shall take place.

Set the ringing sequence for incoming calls from outside Enumeration: 'systeltype7': 7, 'systeltype9': 9, 'systeltype8': 8, 'systeltype10': 10, 'type5': 5, 'type4': 4, 'type6': 6, 'type1': 1, 'type3': 3, 'type2': 2.

Set the ringing sequence for incoming calls inside the PABX. Enumeration: 'systeltype7': 7, 'systeltype9': 9, 'systeltype8': 8, 'systeltype10': 10, 'type5': 5, 'type4': 4, 'type6': 6, 'type1': 1, 'type3': 3, 'type2': 2.

Specify when the presentation number should take effect. By default its value is 'off' defining the actual extension is to be used. If presentation number shall be used only on internal calls ExtPresentation must be set to 'internal'. Analogous to the last, value 'external' is for use on external calls. The last value 'on' specifies that the presentation number is to be used in any case. Enumeration: 'on': 4, 'internal': 2, 'off': 1, 'external': 3.

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 valid id for profiles. In that case terminal profile applies, or if also 0, system default settings apply for the extension.

CtrlByCapiAppl indicates whether a capi application controls this extension. If set to on a special CAPI application registered for handling incoming calls, causing PABX to only signal that incoming call towards CAPI application, hence avoiding a spurious short alerting of Phone until call is answered by application. A CAPI application can request this feature by a LISTEN request with special contents. The default value is off. Enumeration: 'on': 2, 'off': 1.

CtrlByCapiAppl indicates capi application number that controls extension in case pabxExtCtrlByCapiApp is set to on.

This table stores all extension related feature settings that would have overloaded the extension table. The extension for which the settings apply is identified by its id. Currently found features are only the different call forwarding modes. For every mode (unconditional, busy and no reply) a separate telephone number can be stored. The active call forwarding mode is stored in an extra mode field. The pabxExtUsrConfigTable is replaced by that one. To delete a row set pabxExtFeatureCFMode to value delete. CAUTION: deleting a row will result in also deleting the related extension table entry!

This parameter identifies the extension for which all feature settings stored here apply. It must be a valid one, i.e. one that is also found in the pabxExtensionTable.

This field contains the phone number to be used for unconditional call forwarding.

This field contains the phone number to be used for call forwarding in case of busy subscriber.

This field contains the phone number to be used for call forwarding in case user does not respond.

This field defines the time in seconds a call must be in state alerting until call forwarding will be activated. Reasonable values are 3 up to maybe 30, nevertheless all values between 1 and 120 are allowed.

In this field the active call forwarding mode for the extension is stored. It can have the values none, busy, noreply and uncond for the different modes. Besides it makes sense to allow both noreply and busy to be active at a time, so there's the additional value busy-noreply. Apart from that, if mode is set to delete the entry will be deleted. Enumeration: 'uncond': 6, 'none': 2, 'busy': 3, 'noreply': 4, 'busy-noreply': 5.

This field contains the E-Mail address for the extension

SystelMSNSlot is only valid for extensions associated with system terminals. It identifies the MSN configuration slot within the system phone (1 through 10) where it is to be stored when configuring system phone from brick. Value 0 has the special meaning that the configuration slot is undefined; the configuration position is chosen randomly then. Default value is 0.

SystelVolume specifies ringing volume setting within system phone for externally (to brick) initiated incoming calls. Default value is 4.

SystelText contains info text shown in system phone display on incoming and outgoing calls indicating the used/directed-to MSN.

The group table contains all defined groups. It contains the group id and the associated name and one more field that is currently only needed for deleting groups. To delete a row set pabxGroupCalladdInhibit to value delete.

The group id is a non-negative identificator that is unique. The maximum value for it is 2147483647. Id 0 treated specially meaning 'auto group id' when creating new groups.

The group name is just a human readable description for the group and serves for ease of configuration.

As of the necessity to be able of removing groups, another integer variable had to be added. Therefore only the value delete has consequences. The other values are for future use and normal entries so far may have either value. Enumeration: 'enable': 2, 'disable': 3, 'delete': 1.

The terminal table contains all terminals with specification of their corresponding hardware interface, hence invalidating the respective entries in the extension table. Besides a primary user may be given that will be assumed for newly created extensions for that terminal. Deleting a row is done by setting pabxTermDestination to value delete.

The id uniquely identifies a terminal and can have the values 0 up to 2147483647, where number 0 has the special meaning 'auto id' when creating new terminals.

This optional field contains just a (preferably unique) descriptive name for the terminal.

Designates the slot of the physical interface the terminal is attached to.

Designates the unit of the physical interface the terminal is attached to.

This object specifies the type of the destination. When set to physical, the destination is the physical device selected by pabxExtSlot and pabxExtUnit. When set to application, the extension may be used by CAPI or TAPI software applications. When set to internet-telephony, the destination is the computer on the network with the ip-address pabxExtIpAddr. When this object ist set to multiprotocol-routing, the destination is the builtin multiprotocol-router. In this case the object pabxExtLayer1Prot may be used to specify the layer1 protocol and pabxExtIfIndex may be used to assign the extension to a specific multiprotocol-interface. Finally isdn-login may be used to assign the extension to the isdn-login facility of the system. Enumeration: 'delete': 1, 'isdn-login': 6, 'application': 3, 'msg-box': 7, 'internet-telephony': 4, 'multiprotocol-routing': 5, 'physical': 2.

The primary user id allows for automatically setting the user for newly created extensions for that terminal. The default value is 0 meaning no particular user.

The terminal type identifies which kind of terminal it is. By default type is set to phone; other possibilities are modem, fax and headset. When set to modem or fax the normal dial tone is provided instead of a pulsed one normally (without automatic dialout on trunks). Enumeration: 'headset': 4, 'fax': 3, 'answeringmachine': 5, 'system-phone': 6, 'phone': 1, 'modem': 2.

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 valid id for profiles. In that case system default settings apply for the terminal (-> pabxSTATICTable).

This field is only for terminals of type system-phone and specifies its serial number. For terminals set to terminal type 'system phone' the next system terminal found will automatically be associated with a terminal in case serial number is left blank. Default value is the empty string.

The exttogroup table contains all associations of extensions to groups. To allow for extensions being in arbitrary groups as well as groups containing any number of extensions it is necessary to implement an extra table holding that informations and is done right here. Currently the table has only 3 columns (beside the index) where two of them hold an id either, one an extension id the other a group id, and the last column currently serves solely for the purpose of deleting rows. Deleting a row is done by setting pabxTerminalLock to value delete.

This field identifies the extension that should become member in a group.

This field identifies the group the extension will become member of

Currently the only purpose of that field is to supply the user with a possibility to delete such association entries. Enumeration: 'enable': 2, 'delete': 1.

The pabxTrunkMsnTable contains all MSNs that were detected during auto-configuration process on point-to-multipoint trunk lines. The table is handled solely by pabxautocf, hence there's no chance for alteration or deletion of rows.

Specifies slot of interface for which an MSN is found.

Specifies unit of interface for which an MSN is found.

Holds the found MSN.

Tells the type of number stored in pabxTrunkMsnNumber field. Enumeration: 'unknown': 1, 'public-other': 6, 'private': 2, 'public-subscriber': 5, 'public-national': 4, 'public-international': 3.

The pabxProfileTable.

Identifies a profile entry for association to extension, terminal or user. Must be within range 0-2147483647 where value '0' has special meaning 'automatic id' when creating a new entry. Hence, value '0' cannot be used and may only show up in MIB table for ignored entries.

Descriptive - preferably unique - name for profile.

Number string to be dialled automatically when just starting a call. Allows for automatical dialout via trunk. Default is the empty string '' meaning the system default shall be used (see pabxSTATICTable). If not empty it takes precedence over system default.

Define dial permissions of extension. When set to 'internal' dialling out over (external) trunks is prevented. Value 'local' allows dialling external numbers without an area prefix. With setting 'national' any national number but special numbers (like mobile numbers) may be dialled. The only restriction applying to value 'national_special' is dialling of internaltional numbers. The default setting 'full' grants access to any number. Enumeration: 'national-special': 4, 'national': 3, 'internal': 1, 'local': 2, 'full': 5.

Define availability of an extension/terminal. By default extensions are fully available (full), i.e. internal and external bound calls can reach the extension depending on the trunk constellation. Setting availability to internal restricts the extension to be called only by internal callers. Enumeration: 'internal': 1, 'external': 2, 'full': 3, 'delete': 15.

The pabxExtNoPermTable.

Enumeration: 'deny': 6, 'full': 5, 'national': 3, 'national-special': 4, 'internal': 1, 'provider': 7, 'local': 2, 'delete': 255.

Enumeration: 'format-error': 2, 'exists-error': 3, 'ok': 1.

The systelTerminalTable stores all information about system phones attached to the brick. This covers serial number, software version, release date and other information provided by system phone. Deleting a row is done by setting systelTermAutoMove to value delete.

This field is only for terminals of type system-phone and specifies its serial number.

This field specifies whether a terminal shall be automatically reconfigured in case terminal logs in on another port than the one defined in current configuration. By default automatic reconfiguration is disabled. Enumeration: 'enable': 2, 'disable': 1, 'delete': 3.

SystelSWVersion shows the version of the attached system phone and is only valid for terminals of type system-phone.

SystelRelDate shows the system phone software's release date and is only valid for terminals of type system-phone.

SystelCountry shows the active country profile in the attached system phone and is only valid for terminals of type system-phone.

SystelOEMString shows OEM string found in system phone and is only valid for terminals of type system-phone.

SystelDBVersion shows data base version found in system phone and is only valid for terminals of type system-phone.

The field systelTermSlot serves as a hint to which port the system phone is attached to and is only needed for automatical configuration purposes.

The field systelTermUnit serves as a hint to which port the system phone is attached to and is only needed for automatical configuration purposes.

The field systelTermTei only shows the TEI of an active system terminal.

AutoConf controls whether the brick tries setting system phone configuration automatically. Value off means no automatic setting is performed, value on-registration causes the brick to invoke automatic configuration upon system phone registration. Default value is off. Enumeration: 'on-registration': 2, 'off': 1.

TriggerConf allows for initiation of configuration process by setting variable to start anytime when system phone is registered with brick. Beyond termination status of last configuration process is reflected: either done upon success or error upon failure. Default value is done. Enumeration: 'set': 3, 'get-and-create': 5, 'get': 4, 'done': 1, 'error': 255, 'check': 2.

LastConfAction remembers the most recently performed action initiated via TriggerConf helping users interpreting return value of either done or error there. Default value is unknown. Enumeration: 'unknown': 1, 'get-and-create': 5, 'set': 3, 'check': 2, 'get': 4.

The pabxSpeedDialTable contains shortcuts for dialling arbitrary numbers. and is in fact part of the dial plan like extensions and trunk prefixes. Deleting a row is done by setting pabxSpeedDialCtrl to value delete.

This field contains the shortcut number for an arbitrary number by which it is replaced.

This field contains actual number that replaces shortcut.

This field specifies whether a speed dial entry is active at all. Besides entries in speed dial table can be deleted by setting this field to delete. Default value is on Enumeration: 'on': 1, 'off': 2, 'delete': 3.

When this object is not empty, internal numbers are dialed by using the contents of this object as a prefix. External numbers are dialled as usual, without using a prefix. When this object is empty, internal numbers are dialled without a prefix, while external numbers need a prefix specified in the pabxTrunkPrefixTable.

This object is a bitmask specifying the set of trunk-lines to be used for external calls, when pabxLocalPrefix is not empty and external numbers are dialled without trunk-prefix.

Enable of Disable Priority Voice Feature Enumeration: 'enable': 2, 'disable': 1.

Select the source while call in hold state Enumeration: 'internal': 1, 'external': 2.

Specify extension to be called by door intercom.

Specifies whether opening the door (i.e. calling a door intercom extension) is possible via a trunk call ('allow') or not ('deny'). The default is 'denied'. Enumeration: 'deny': 2, 'allow': 1.

Password for TAPI super-user named 'TAPIadmin'. Default is 'bintec'.

String to be used by default if auto dialout is selected for a user/terminal/extension that has no profile associated with. Default value at system initialisation (no boot configuration) is '0'. If it's set to an empty string autodialout is disabled by system default.

Define default availability of extension w/o associated profile. By default extensions are fully available (full), i.e. internal and external bound calls can reach the extension depending on the trunk constellation. Setting availability to internal restricts referred to extensions to be available only by internal callers. Enumeration: 'internal': 1, 'external': 2, 'full': 3.

Define dial permissions of extensions w/o associated profile. When set to 'internal' dialling out over (external) trunks is prevented. Value 'local' allows dialling external numbers without an area prefix. With setting 'national' any national number but special numbers (like mobile numbers) may be dialled. The only restriction applying to value 'national_special' is dialling of internaltional numbers. The default setting 'full' grants access to any number. Enumeration: 'national-special': 4, 'national': 3, 'internal': 1, 'local': 2, 'full': 5.

Define dial permissions for external calls. When set to 'internal' dialling out over (external) trunks is prevented. Value 'local' allows dialling external numbers without an area prefix. With setting 'national' any national number but special numbers (like mobile numbers) may be dialled. The only restriction applying to value 'national_special' is dialling of internaltional numbers. The default setting is 'internal'. Enumeration: 'national-special': 4, 'national': 3, 'internal': 1, 'local': 2, 'full': 5.

Password for CAPI super-user named 'CAPIadmin'. Default is an empty password meaning CAPIadmin registration is blocked.

Specifies country where machine resides for country specific settings. Enumeration: 'germany': 1, 'uk': 2, 'france': 3.