TELTREND-MIB: View SNMP OID List / Download MIB

The enterprise MIB module for Teltrend's NiQ routers.

The table of call details parameters.

A single entry of ISDN call details. This contains the parameters of a single ISDN call details.

The index of the call details entry in the call details table. When an entry is created in this table, the index does not have to be written. However, to reference the values that are written, an unused index must be found by reading the index values of the table until a no such object error is returned. Attempting to create a row by using an already used index will result in simply changing the parameters of an existing call details entry.

The name of the ISDN call details. This must be unique for all ISDN call details, when comparisons are done ignoring the case of letters. Valid characters in the ISDN call name include 0-9, a-z, A-Z and '-'. A name consisting of all digits is not valid. Setting this object is mandatory on row creation. However, this object cannot be set for an existing call. This is because for the command line interface calls are identified by name.

The remote ISDN call name. This name can be referenced by certain other call details parameters related with setting up the Q.931 SETUP message for outgoing calls, or searching for calls for incoming calls. Valid characters in the ISDN remote call name include 0-9, a-z, A-Z and '-'. A remote name consisting of all digits is valid.

The number called when this call details is activated. The number should include all telephone network access codes, country codes and area codes required to make a call from the particular ISDN interface. Setting this object is mandatory on row creation.

The number used as the calling number when this call is activated. The calling number can optionally be placed in the outgoing SETUP message.

The number called when all retries with the main called number have failed. In this event, the router tries once with the alternate number, then checks the ccDetailsKeepup object to determine whether to try again with the main number.

Whether this ISDN call is enabled or disabled for incoming and outgoing calls. If the call details entry is disabled, all existing active calls based on this call details entry are left active. Enumeration: 'disabled': 1, 'enabled': 2.

The direction for which calls may be made or received using this call details entry. Enumeration: 'both': 3, 'out-only': 2, 'in-only': 1.

The precedence of this call details entry in the event of call collision. Call collision occurs when an incoming call for a given details entry is detected while an outgoing call is waiting to complete. This object configures whether the router treats the incoming or outgoing call as having precedence. Since the device at the other end will also probably be experiencing a call collision, the precedence should be configured to the opposite value at the other end. Setting this object is mandatory on row creation. Enumeration: 'out': 2, 'in': 1.

The time, in seconds, that active calls created from this call details should be held up after initial activation. The call will be held up for at least this time, unless cleared from the network. Thus, for example, PPP idle timeouts will not bring the call down.

The ifIndex of an ISDN interface on this router which is the preferred ISDN interface on which to make an outgoing call using this call details entry. The ifIndex, if not 0, should reference the ifEntry which contains information about the entire ISDN interface, at the lowest layer. If a channel is not available on this interface, the call can try other interfaces in order to make the call. This object is not used on incoming calls. If the value of this object is set to 0, no interface will be preferred over any other. If the value of this object does not reference the ifEntry for the entire ISDN interface, no interface will be preferred.

The ifIndex of an ISDN interface on this router which is the required ISDN interface on which to make an outgoing call using this call details entry. The ifIndex, if not 0, must reference the ifEntry which contains information about the entire ISDN interface, at the lowest layer. If a channel is not available on this interface, the call fails. This object is not used on incoming calls. If the value of this object is set to 0, no interface will be required. If the value of this object does not reference the ifEntry for the entire ISDN interface, no interface will be required.

The priority of calls generated from this call details entry. The priority determines whether calls can be bumped for higher priority calls. The value of priority falls into ranges: 0-19 - call bumped by incoming or outgoing, voice or data calls 20-39 - call bumped by outgoing voice and incoming or outgoing data calls 40-59 - call bumped by emergency voice calls or incoming or outgoing data calls 60-99 - call bumped by emergency voice calls or outgoing data calls. Note that when the call is bumped by a data call, the data call must have higher priority than the call being bumped.

The time in seconds between retries of calls generated from this call details entry.

The number of retries in a retry group for calls generated from this call details entry. Note that the default value means that by default the call will not be retried.

The time in seconds between retry groups for retries of calls generated from this call details entry.

The number of retry groups for calls generated from this call details entry. Note that the default value means that by default no retry groups will be attempted.

A flag indicating whether calls generated from this call details entry should be kept up always. Inspection of this flag takes place when a call is cleared from an external source. If set to 'yes', the call will be retried. Enumeration: 'yes': 2, 'no': 1.

The CLI information placed into outgoing SETUP messages when this call details is used to generate an outgoing call. The value 'off' means that no CLI information in placed in the SETUP message. The value 'calling' means that the calling number from the call details entry is placed in the SETUP message. The value 'interface' means that the Q.931 interface number for the interface and DLC on which the call is made is placed in the SETUP message. The value 'nonumber' means that the CLI information element is placed in the SETUP message with no number information. The network will fill the number in. Enumeration: 'interface': 3, 'nonumber': 4, 'off': 1, 'calling': 2.

The user-user information placed into outgoing SETUP messages when this call details is used to generate an outgoing call. The value 'off' means that no user-user information in placed in the SETUP message. The value 'local' means that the call name from the call details entry is placed in the SETUP message. The value 'remote' means that the remote call name from the call details entry is placed in the SETUP message. Enumeration: 'local': 2, 'off': 1, 'remote': 3.

The called subaddress information placed into outgoing SETUP messages when this call details is used to generate an outgoing call. The value 'off' means that no called subaddress information in placed in the SETUP message. The value 'local' means that the call name from the call details entry is placed in the SETUP message. The value 'remote' means that the remote call name from the call details entry is placed in the SETUP message. Note that the action of this object is overridden by the value of the object ccDetailsOutSubaddress. Enumeration: 'local': 2, 'off': 1, 'remote': 3.

This object gives a way to override the called subaddress information placed into outgoing SETUP messages when this call details is used to generate an outgoing call, as given by the ccDetailsOutSetupCalledSub object. The object is an arbitrary string of ASCII characters, from 0 to 31 characters long.

A flag indicating whether or not to call back the caller when an incoming call is generated from this call details entry. If set to 'yes', the incoming call will be cleared, and after a short delay, an outgoing call will be activated for this call details entry. Enumeration: 'yes': 2, 'no': 1.

The time, in tenths of a second, which the router will wait after clearing an incoming call whose call details entry specified that the caller should be called back before making the return call. The purpose of this object is to allow the user to specify a delay in callback which will allow the network to properly clear the call at both this end and the remote end.

Determines whether this call details entry is used in a search of call details for an incoming call based on the contents of the called subaddress information in the incoming SETUP message. The value 'off' means that this call details entry is not used in the search. The value 'local' means that the call details entry is used in the search and the called subaddress information is compared with the call details entry name. The value 'remote' means that the call details entry is used in the search and the called subaddress information is compared with the call details entry remote name. A number of searches are carried out until a matching call is found. First a search against the called subaddress in the SETUP message, then a search against the user-user information in the SETUP message, then a search against the calling number information in the SETUP message, then a search for any call that is configured to respond to any incoming call. Enumeration: 'local': 2, 'off': 1, 'remote': 3.

Determines whether this call details entry is used in a search of call details for an incoming call based on the contents of the user-user information in the incoming SETUP message. The value 'off' means that this call details entry is not used in the search. The value 'local' means that the call details entry is used in the search and the user-user information is compared with the call details entry name. The value 'remote' means that the call details entry is used in the search and the user-user information is compared with the call details entry remote name. A number of searches are carried out until a matching call is found. First a search against the called subaddress in the SETUP message, then a search against the user-user information in the SETUP message, then a search against the calling number information in the SETUP message, then a search for any call that is configured to respond to any incoming call. Enumeration: 'local': 2, 'off': 1, 'remote': 3.

Determines whether this call details entry is used in a search of call details for an incoming call based on the contents of the calling number information in the incoming SETUP message. The value 'off' means that this call details entry is not used in the search. The value 'on' means that the call details entry is used in the search and the calling number information is compared with the call details entry called number. The value 'list' means that the call details entry is used in the search and the calling number information is compared with the numbers on the CLI list reference by the object ccDetailsInSetupCliSearchList. The value 'list' cannot be set by an SNMP management entity. Rather the ccDetailsInSetupCliSearchList object should be set to a non-zero value, which will automatically set this object to 'list'. A number of searches are carried out until a matching call is found. First a search against the called subaddress in the SETUP message, then a search against the user-user information in the SETUP message, then a search against the calling number information in the SETUP message, then a search for any call that is configured to respond to any incoming call. Enumeration: 'on': 2, 'list': 3, 'off': 1.

If the ccDetailsInSetupCliSearch object is set to 'list', this object gives the index of the CLI list to search. The value of CLI list indices is 1..100. The value 0 is returned when the ccDetailsInSetupCliSearch object is not set to 'list'. If the value of this object is set to 0 via SNMP, then the ccDetailsInSetupCliSearch object will be internally set to 'off'. Subsequently setting the value of this object to a non-zero value will set the ccDetailsInSetupCliSearch object to 'list'.

Determines whether this call details entry will match any incoming call. After all searched for incoming calls have been carried out based on called subaddress, user-user information and calling number, a search is carried out for the first call found with this flag set to 'yes'. Enumeration: 'yes': 2, 'no': 1.

Determines whether to perform a check when an incoming call matches this call details entry based on the contents of the called subaddress information in the incoming SETUP message. The value 'off' means that the check is not carried out. The value 'local' means that the check is carried out and the called subaddress information is compared with the call details entry name. The value 'remote' means that the check is carried out and the called subaddress information is compared with the call details entry remote name. A number of checks are optionally carried out once a matching call is found. The first check is against the called subaddress in the SETUP message, then against the user-user information in the SETUP message, then against the calling number information in the SETUP message. Enumeration: 'local': 2, 'off': 1, 'remote': 3.

Determines whether to perform a check when an incoming call matches this call details entry based on the contents of the user-user information in the incoming SETUP message. The value 'off' means that the check is not carried out. The value 'local' means that the check is carried out and the user-user information is compared with the call details entry name. The value 'remote' means that the check is carried out and the user-user information is compared with the call details entry remote name. A number of checks are optionally carried out once a matching call is found. The first check is against the called subaddress in the SETUP message, then against the user-user information in the SETUP message, then against the calling number information in the SETUP message. Enumeration: 'local': 2, 'off': 1, 'remote': 3.

Determines whether to perform a check and which check to perform when an incoming call matches this call details entry based on the contents of the calling number information in the incoming SETUP message. The value 'off' means that the check is not carried out. The value 'present' means that the check is carried out only if calling number information is present. The value 'required' means that the calling number must be present for the check to pass. When the check is carried out, the calling number information is compared with the numbers in the CLI list referenced by the object ccDetailsInSetupCliCheckList. A number of checks are optionally carried out once a matching call is found. The first check is against the called subaddress in the SETUP message, then against the user-user information in the SETUP message, then against the calling number information in the SETUP message. Enumeration: 'required': 3, 'off': 1, 'present': 2.

If the ccDetailsInSetupCliCheck object is set to 'present' or 'required', this object gives the index of the CLI list to check against. The value of CLI list indices is 1..100. The value 0 means that no list to check against is defined and the check immediately fails.

The type of user of this call. The value 'attach' means that users have to attach to this call before the call can be used for outgoing or incoming calls. The value 'ppp' means that for incoming calls only dynamic PPP interfaces will be created whenever this call details entry is matched. Enumeration: 'attach': 1, 'ppp': 2.

The type of login for calls generated using this call details entry, for incoming calls only. Incoming calls can be configured to go through a logging in phase before the call is brought up. This object defines which login types are used. The value 'none' means don't do a login phase. The value 'userdb' means use the user database on the router to check login parameters. The value 'radius' means use the router's configured RADIUS servers to check the login parameters. The values 'pap-tacacs', 'chap' and 'pap-radius' apply only when the user is 'ppp' and determine how the dynamic PPP interface are configured for authentication. The value 'pap-tacacs' means use PAP to authenticate and use the TACACS server to check the login parameters. The value 'pap-radius' means use PAP to authenticate and use the RADIUS server to check the login parameters. The value 'chap' means use CHAP to authenticate. The value 'tacacs' means use the TACACS server to check login parameters. The value 'all' means use the user database, TACACS and RADIUS to check the login parameters. The login parameters for values 'userdb', 'radius', 'tacacs' and 'all' are determined by the ccDetailsUsername and ccDetailsPassword objects. Enumeration: 'userdb': 2, 'none': 1, 'tacacs': 7, 'all': 8, 'pap-tacacs': 4, 'chap': 5, 'radius': 3, 'pap-radius': 6.

The source of the username when the ccDetailsLoginType object has a value of 'userdb', 'radius', 'tacacs' or 'all'. The value 'none' means no username is defined. The value 'cli' means take the username from the calling number information in the SETUP message. The value 'calledsub' means take the username from the called subaddress information in the SETUP message. The value 'useruser' means take the username from the user-user information in the SETUP message. The value 'callname' means take the username from the call details entry name. Enumeration: 'useruser': 4, 'callname': 5, 'none': 1, 'calledsub': 3, 'cli': 2.

The source of the password when the ccDetailsLoginType object has a value of 'userdb', 'radius', 'tacacs' or 'all'. The value 'none' means no password is defined. The value 'cli' means take the password from the calling number information in the SETUP message. The value 'calledsub' means take the password from the called subaddress information in the SETUP message. The value 'useruser' means take the password from the user-user information in the SETUP message. The value 'callname' means take the password from the call details entry name. Enumeration: 'useruser': 4, 'callname': 5, 'none': 1, 'calledsub': 3, 'cli': 2.

The time, in tenths of a second, which the router will wait after clearing an existing call which has been bumped to make way for a call based on this call details entry.

The data rate to use for active calls based on this call details entry. The actual data rate for outgoing calls is determined by both this object and the data rate parameter for the Q.931 interface chosen for the call. If either this object or the interface object specify a rate of 56k, then 56k will be the rate for the call. Otherwise, the default rate of 64k will be used. This allows interoperability between ISDNs which only allow 56k of data on a B channel. Enumeration: 'rate-56k': 2, 'rate-64k': 1.

The PPP template to use when creating dynamic PPP interfaces for calls generated from this call details entry. The value 33 represents a default PPP template, the values 0 to 31 represent PPP templates that are currently defined in the router.

The module ID of the user module currently attached to this ISDN call details entry.

The number of attachments from the user module currently attached to this call details entry. The ccAttachmentsTable gives the actual attachments for each call details entry.

The table of CLI list entries.

A single entry in the CLI list table. This contains a single number, as well as index information.

The index of the CLI list. CLI lists from 1 to 100 are defined in the router.

The index of the CLI list entry within the CLI list. The minimum CLI list entry is 1. CLI lists are unlimited in length, although internal memory requirements could result in failure to create a given entry. When creating a row in this table, the entry index should be set to index the first empty row. Only one CLI list row in a given list should be created in any one SNMP message. Attempting to create more than one row will result in failure.

The number for this CLI list entry. Setting the number to a zero length string removes the entry from the CLI list, with consequent reshuffling of CLI entry indices. Thus the easiest way to delete an entire CLI list is to repeatedly set the first element in the list to a zero length string. A failure to SET will occur when this is attempted on an empty list.

The table of ISDN active calls.

A single entry in the active call table.

The index of the active call. There are 128 possible active calls in the router simultaneously.

The index of the call details entry which generated this active call. Thus the index into the ccDetailsTable for this call.

The interface index of the interface on which this active call is being made or received. A value of zero indicates that the active has not yet had an interface assigned to it. The ifEntry indexed by this object is the ifEntry for the entire ISDN interface, not the ifEntry for the active call's B channel.

The data rate in use for this active call. This is determined by the call details setting of data rate, the ISDN interface setting for data rate, and the contents of the bearer capability information in the incoming SETUP message. Enumeration: 'rate-56k': 2, 'rate-64k': 1.

The state of this active call. The value 'null' indicates that this active call does not actually exist, in other words it is in the process of being created or destroyed. The value 'off' means that the active call is just being activated. The value 'try' means that the active call is attempting to establish. The value 'on' means that the active call is established. The value 'wait' means that the active call is waiting to retry. The value 'await1' means that the active call is waiting for authentication to succeed before becoming established. Enumeration: 'on': 4, 'off': 2, 'try': 3, 'null': 1, 'await1': 6, 'wait': 5.

The direction of this active call. The value 'in' indicates that this active call is an incoming call, the value 'out' indicates that the active call is an outgoing call. The value 'undefined' indicates that the active call has just been created and a direction has not been assigned to it yet. Enumeration: 'out': 2, 'undefined': 3, 'in': 1.

The module ID of the user module attached to this ISDN active call.

The instance of the user module attached to this ISDN active call.

The B channel number for this active entry. BRI interfaces have B channels in the range 1..2, PRI interfaces have B channels in the range 1..31, excluding a channel which is the D channel. A value of 0 for this entry means that either a B channel is not currently allocated for this call, or that more than one B channel is allocated. In the second case, the management client will have to walk the B channel allocation table looking for channels with the same active call index as this call's.

The table of ISDN call log entries.

A single entry in the ISDN call log table.

The index of the call log entry. Since the call log table is dynamic, there is no guarantee that this index will continue to refer to the same log entry over time.

The name of the call details entry which generated the active call for which this is the log entry.

The state of the log entry. The value 'initial' means that the call is being established. The value 'active' means that the call is currently established. The value 'disconnected' means that the call was disconnected after being established for some time. The value 'cleared' means that the call was cleared abormally while in the establishment phase. Enumeration: 'active': 2, 'initial': 1, 'disconnected': 3, 'cleared': 4.

A string in the format 'dd-mmm-yyyy hh:mm:ss' which gives the start time of the call for which this is the log entry. If the call never reached or has not yet reached the active state, this object will be a zero-length string.

The direction of the call for which this is the log entry. Enumeration: 'out': 2, 'in': 1.

The duration in seconds, of the call for which this is the log entry. A value of 0 in this field means either that the call has just started, that the call was cleared before becoming established, or that the call is still active. In other words, a non-zero value is present in this object only for calls which reach establishment and have since been cleared.

For incoming calls, the calling number, if this was made available in the SETUP message. For outgoing calls, the number dialed. If the number was not available, this object is a zero length string.

The table of call detail attachment entries.

A single entry in the attachment table.

The index of the call details entry to which this attachment entry belongs.

The index of the attachment entry within the attachment list.

The index of the active call for this attachment. A value of 0 indicates that there is currently no active call for this attachment. A value of 1 to 128 references the active call currently in place for this attachment.

The instance of the user module attached to the ISDN active call for this attachment. This object should return the same value as the object ccActiveCallUserInstance for the active call indexed by ccAttachmentActiveCallIndex, if this is not 0.

The table of B channel attachment entries.

A single entry in the B channel attachment table.

The interface index of the interface which this B channel entry is on. The ifEntry indexed by this object is the ifEntry for the entire ISDN interface, not the ifEntry for the active call's B channel.

The B channel number for this B channel entry. BRI interfaces have B channels in the range 1..2, PRI interfaces have B channels in the range 1..31, excluding a channel which is the D channel.

A flag indicating whether this B channel is actually allocated to a call or not. Enumeration: 'yes': 2, 'no': 1.

The type of call on this B channel. If the B channel is not allocated, the call type will be undefined. Enumeration: 'x25': 4, 'voice': 3, 'data': 2, 'undefined': 1.

The index of the active call which is currently attached to this B channel. If the value of this object is 0 the channel is either not allocated, or is not allocated to a data call.

The priority of the call which has this B channel allocated to it. This is in the range 0..99 for data calls, 150 for voice calls and 200 for emergency voice calls. A B channel which is not allocated will have a priority of 0.

The direction of the call which has this B channel allocated to it. If this B channel is not allocated the value will be 'unallocated'. Enumeration: 'out': 2, 'unallocated': 3, 'in': 1.

The table of load parameters, dynamic and static.

A single entry of load parameters. This contains the parameters required to perform a load from the router.

There are two sets of load information, dynamic and static. The dynamic information is used once, then cleared. The static information is used whenever the dynamic information is not available. The dynamic information is also used to indicate the current load parameters when a load is in progress. Enumeration: 'dynamic': 2, 'static': 1.

The IP address from which load will load.

The destination of the file loaded, either flash or nvs memory, or undefined. Enumeration: 'flash': 3, 'nvs': 2, 'undefined': 1.

The file name of the file being loaded.

A delay in seconds between the initiation of the load and the start of the load. This allows for time to set up TFTP servers in cases where the terminal and TFTP server are using the same piece of equipment but will not work simultaneously.

Status and action object for the load module. The values 1 to 5 are read-only values and reflect the state of the load module. Values 4 and 5 (complete and reset) are 'read-once', that is, if their values are read, either by SNMP or by manager console command, then they will be changed back to idle. The action values (6 and 7) cause a start and stop of the load process respectively. Starting the load can only occur if this field has the values 1, 4, or 5. Stopping the load can only occur is this field has the values 2 or 3. Reading the value of the loadStatus after one of actionstart or actionstop has been set will give one of the values 1 to 5. Enumeration: 'reset': 5, 'loading': 3, 'complete': 4, 'idle': 1, 'actionstop': 7, 'actionstart': 6, 'wait': 2.

The list of install configurations for the router.

An entry in the list of install configurations.

The index for the install table. There are three install configurations defined in the router, default, preferred and temporary. The router will attempt to use these in the order temporary, preferred, default when it boots. An install that is undefined will be skipped, an install which points to a file which is not present will be skipped. When the temporary install is used, the information is deleted. Enumeration: 'default': 3, 'temporary': 1, 'preferred': 2.

The device for the release in the install. If the device is flash the file for the release is given in instRelName. Devices none(1) or flash(3) are invalid for the default(3) release. Enumeration: 'none': 1, 'flash': 3, 'eprom': 2.

The file name for the release in the install, if the instRelDevice is flash(3). If the instRelDevice is none(1) or eprom(2), this object should be a null string.

The major release number for this install. This information is obtained by the router when the other elements in the row are set and is thus not directly set by management. If the release number is a.b.c, the major release number is a.

The minor release number for this install. This information is obtained by the router when the other elements in the row are set and is thus not directly set by management. If the release number is a.b.c, the major release number is b.

The device for the patch in the install. The file for the patch is given in instPatName unless the device is none(1). Enumeration: 'none': 1, 'flash': 3, 'nvs': 4.

The file name for the patch in the install.

The interim release number for this install. This information is obtained by the router when the other elements in the row are set and is thus not directly set by management. If the release number is a.b.c, the major release number is c. If the release number is a.b, the interim release number is 0.

The table of descriptions of events in the install history of the router.

A single line describing part of the install history of the router.

The index of this event in the install history. Indices run from 1 to the maximum number. The maximum number is not available as a managed object so this table will have to be traversed in order to find out how large it is.

A line of text describing a single event in the install history of the router.

The name of the file that the router will configure from at boot. The format of the name is the same as that for fileName described above. If the configuration file name is a zero length string, then there is no configuration file defined in the router.

The list of release licences in the router.

An entry in the list of release licences.

A unique licence index. Licence indices are recalculated every time the router reboots to reflect the current licences on the router. As licences are added, new indices are allocated to the new licences.

The status of the file. When read, this object will always return a value of ok(1), since the object will not exist if the value is deleting(2). Write the value deleting(2) to this object to delete the file. Enumeration: 'deleting': 2, 'ok': 1.

The file name for the release whose licence this is.

The major release number for the release whose licence this is.

The minor release number for the release whose licence this is.

The password for this release. The password is a string of hex digits.

A human-readable string that gives the expiry date of this licence.

The interim release number for the release whose licence this is.

A list of all the files in the router's non-volatile storage.

An entry in the list of files containing information about a single file in the router.

A unique file index. File indices are recalculated every time the router reboots to reflect the current files on the router. As files are added, new indices are allocated to the new files.

The name of the file, in the form . The name is up to eight characters long, the type is up to three characters long.

The device on which the file resides. Enumeration: 'flash': 1, 'nvs': 2.

The creation date and time for the file, in the format .

The status of the file. When read, this object will always return a value of ok(1), since the object will not exist if the value is deleting(2). Write the value deleting(2) to this object to delete the file. Enumeration: 'deleting': 2, 'ok': 1.

The size, in bytes, of the file.