CISCO-CAS-IF-MIB

OCTET STRING SIZE (0..4)

This object contains the bit map of the available DS0 channel in the DS1. The MSB (most significant bit) is DS0 channel number 1. The missing bytes is default to a value of 0. A 1-bit indicates the channel is available for configuration and a 0-bit indicates it isn't. The length of this object is either 3 octets (for T1) or 4 octets (for E1). The most significant bit is transmitted first.

Integer32 (0..30)

An arbitrary index that uniquely identifies a DS0 group in a T1/E1.

INTEGER1 = emWinkStart2 = emWinkStartFgd3 = emImmedStart4 = emDelayDial5 = fxsLoopStart6 = fxsGroundStart7 = sasLoopStart8 = sasGroundStart9 = r2Analog10 = r2Digital11 = r2Pulse12 = p713 = fxoLoopStart14 = fxoGroundStart15 = fgdOS16 = nullSignaling17 = r1Itu18 = r1Modified19 = r1Turkey20 = fgdEANA21 = emMelImmedStart22 = emMelWink23 = emMelDelayDial24 = fxsMelcas25 = fxoMelcas26 = extsig27 = emLmr · Integer32

Reference: EIA/TIA-464B, chapter 6.2.1.1 Signaling Interface Types. ITU-T Q411 - Specifications of signalling system R2 line signalling, analogue version. ITU-T Q421 - Specifications of signalling system R2 line signalling, digital version. ITU-T R2 Supplement 7 - Specifications of signalling system R2 line signalling, pulsed version. Bellcore, TR-NPL-000258 - Feature Group D section 3.4 for Exchange Access North American section 3.6 for Operator Services Signaling

The Signaling type of the DS0 group. emWinkStart - CAS E&M Wink Start. emWinkStartFgd - CAS E&M Wink Start with Feature group D. emImmedStart - CAS E&M Immediate Start. emDelayDial - CAS E&M Delay Dial. fxsLoopStart - CAS FXS Loop Start. fxsGroundStart - CAS FXS Ground Start. sasLoopStart - CAS SAS Loop Start. sasGroundStart - CAS SAS Ground Start. r2Analog - R2 ITU Q411. r2Digital - R2 ITU Q421. r2Pulse - R2 ITU Supplement 7. p7 - P7 switch. fgdOS - Bellcore Feature Group D : Operator Services Signaling nullSignaling - 64k clear channel r1Itu - R1 ITU. r1Modified - R1 Modified. r1Turkey - R1 Turkey. fgdEANA - FGD Exchange Access North American. emMelImmedStart - CAS E&M Melcas Immediate Start emMelWink - CAS E&M Melcas Wink Start emMelDelayDial - CAS E&M Melcas Delay Dial fxsMelcas - CAS FXS Melcas fxoMelcas - CAS FXO Melcas extsig - External Signal emLmr - CAS E&M Land Mobil Radio(LMR) interface

OCTET STRING SIZE (4)

This object contains the bit map of the selected DS0 channels to be added into this group. The MSB (most significant bit) is DS0 channel number 1. For T1, only higher 24 bits are used to specify the the CAS channels for the CAS group. A 1-bit indicates the channel to be added into group and a 0-bit indicates it isn't.

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

This object is used to create a new row or modify or delete an existing row in this table. The corresponding instance of ccasGrpCfgType can not be modified while this object has the value 'active'.

INTEGER1 = none2 = casServSw563 = casServModem4 = casServAuto5 = sgcp6 = mgcp7 = other8 = trunkingService9 = h24810 = ds0xconn11 = xgcp · Integer32

Specify the Service type of the CAS/DS0 group. none - no service type casServSw56 - sw56 service for CAS casServModme - modem service for CAS casServAuto - auto service for CAS sgcp - Simple Gateway Control Protocol (SGCP) service. Used when DS0 is configured for null signaling. mgcp - Media Gateway Control Protocol (MGCP) service. Used when DS0 is configured for null signaling. other - none of the above and the below. trunkingService - This DS0 group is handled by trunking service application. h248 - ITU H.248 Media Gateway Control service. Used when DS0 is configured for null signaling. ds0xconn - Used for DS0 cross connection. xgcp - Media Gateway Control Protocol (MGCP) extension service including TGCP (Trunking Gateway Control Protocol) profiles feature. Used when DS0 is configured for null signaling.

INTEGER1 = dtmf2 = pulse3 = mf · Integer32

Specify the addressing type of the CAS group. dtmf - Dual Tone Multi-Frequency (DTMF) digit. pulse - dial pulse. mf - Multi-Frequency (MF) digit. The default value of this object is dtmf(1).

BITS

Specify the type of Destination Number Identification Service (DNIS) and Automatic Number Identification (ANI) support. MF tone supports both ANI and DNIS services. The DTMF tone only supports both incoming and outgoing DNIS. incomingDnis - support incoming DNIS feature. incomingAni - support incoming ANI feature. outgoingDnis - support outgoing DNIS feature. outgoingAni - support outgoing ANI feature. The default value of this object is '00'H.

INTEGER1 = inact2 = audio3 = dial · Integer32

The M lead behavior of E&M LMR interface. inact - The m-lead status should be ignored. audio - The m-lead status is used to control generating voice packet. dial - The first m-lead off to on status indicates call setup request. The following m-lead status change during the call should be ignored.

INTEGER4 = seize5 = voice6 = inactive · Integer32

The E lead behavior of E&M LMR interface. seize - The e-lead used as seize signal. voice - The e-lead status is used to indicate voice packet received or not. inactive -- e-lead is inactive.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is used to enabling or disabling automatic gain control on this interface. AGC allows dsp to adjust the input voice volume and avoid rapid voice volume change.

Integer32 (200..2000) · milliseconds

Time of Inactive incoming seizure signal to declare call cleared. This object is relevant to the interfaces in the CAS group if the ccasGrpCfgType object is emWinkStart(1) or emWinkStartFgd(2). The default value of this object is 400 milliseconds.

Integer32 (100..5000) · milliseconds

Maximum wink wait duration for sending out wink start signaling. This object is relevant to the interfaces in the CAS group if the ccasGrpCfgType object is emWinkStart(1) or emWinkStartFgd(2). The default value of this object is 200 milliseconds.

Integer32 (100..3000) · milliseconds

Maximum wink duration for sending out wink start signaling. This object is relevant to the interfaces in the CAS group if the ccasGrpCfgType object is emWinkStart(1) or emWinkStartFgd(2). The default value of this object is 200 milliseconds.

Integer32 (20..2000) · milliseconds

Timing of generation of outgoing delayed start signal from detection of incoming seizure. This object is relevant to the interfaces of the CAS group if the ccasGrpCfgType object is emDelayDial(4). The default value of this object is 300 milliseconds.

Integer32 (100..5000) · milliseconds

Maximum delay signal duration for sending out delay dial signaling. This object is relevant to the interfaces in the CAS group if the ccasGrpCfgType object is emDelayDial(4). The default value of this object is 2000 milliseconds.

Integer32 (0 | 140..5000) · milliseconds

Minimum delay-dial pulse duration for incoming call. If the value of this object is 0, then no delay-dial is sent to the far end for the incoming call. This object is relevant to the interfaces in the CAS group if the ccasGrpCfgType object is emDelayDial(4). The default value of this object is 140 milliseconds.

Integer32 (50..500) · milliseconds

Outgoing DTMF/MF digit duration in milliseconds. This object is not relevant to the addressing timing of the interfaces in the CAS group if ccasGrpCfgDialType is dtmf or R2 tone. The default value of this object is 100 milliseconds.

Integer32 (50..500) · milliseconds

Outgoing DTMF/MF inter-digit duration in milliseconds. This object is not relevant to the addressing timing of the interfaces in the CAS group if ccasGrpCfgDialType is dtmf or R2 tone. The default value of this object is 100 milliseconds.

Integer32 (10..20) · pulses per second

Outgoing Pulse dialing rate in pulses per second (pps). This object is relevant to the addressing timing of the interfaces in the CAS group only if ccasGrpCfgDialType is pulse. The default value of this object is 10 pps.

Integer32 (100..1000) · milliseconds

Outgoing Pulse dialing inter-digit timing in milliseconds. This object is relevant to the addressing timing of the interfaces in the CAS group only if ccasGrpCfgDialType is pulse. The default value of this object is 500 milliseconds.

Integer32 (0..10000) · milliseconds

The hangover time used to determine there is no more voice packet arrived. The default value of this object is 250 milliseconds.

Integer32 (-1 | 5..60000) · seconds

LMR port tear down timeout. This object is relevant to the waiting time of teardown call on LMR port. If the value of this object is '-1', then the timeout is disable.

Integer32 (0..30) · minutes

This object signifies LMR port maximum transmit time. This object is relevant to how long LMR port can continue transmit voice packet without pause.

Integer32 (0..30) · minutes

This object signifies LMR port maximum receive time. This object is relevant to how long LMR port can continue receive voice packet without pause.

Integer32 (0..1500) · milliseconds

This object is relevant to how long LMR will delay sending the voice packet to the LMR port.

Integer32 (0..10) · rings

The number of rings detected before closing loop. If the value of this object is 0, then the managed system answers immediately after the interface detects a incoming seizure if the ccasGrpCfgType is 'fxsGroundStart' or 'sasGroundStart'. The default value of this object is 1 ring.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Specifies whether a supervisory disconnect signal will be presented to the interface when the connected party at the interface hangs up. this object is only relevant to the ccasGrpCfgType is fxsLoopStart or sasLoopStart. The default value of this object is 'true'.

INTEGER1 = dtmf2 = pulse · Integer32

Specify the addressing type of the CAS group. dtmf - Dual Tone Multi-Frequency (DTMF) digit. pulse - dial pulse. The default value of this object is dtmf(1).

Integer32 (50..500) · milliseconds

Outgoing DTMF digit duration in milliseconds. This object is not relevant to the addressing timing of the interfaces in the CAS group if ccasGrpLineCfgDialType is dtmf. The default value of this object is 100 milliseconds.

Integer32 (50..500) · milliseconds

Outgoing DTMF inter-digit duration in milliseconds. This object is not relevant to the addressing timing of the interfaces in the CAS group if ccasGrpLineCfgDialType is dtmf. The default value of this object is 100 milliseconds.

Integer32 (10..20) · pulses per second

Outgoing Pulse dialing rate in pulses per second (pps). This object is relevant to the addressing timing of the interfaces in the CAS group only if ccasGrpStaCfgDialType is pulse. The default value of this object is 10 pps.

Integer32 (100..1000) · milliseconds

Outgoing Pulse dialing inter-digit timing in milliseconds. This object is relevant to the addressing timing of the interfaces in the CAS group only if ccasGrpStaCfgDialType is pulse. The default value of this object is 500 milliseconds.

Integer32 (0..1000) · rings

The number of rings sent before sending reorder to the originator and releasing resources. If the value of this object is 0, then sending reorder to the originator is disabled. The default value of this object is 20 rings.

INTEGER1 = dtmf2 = pulse · Integer32

Specify the addressing type of the CAS group. dtmf - Dual Tone Multi-Frequency (DTMF) digit. pulse - dial pulse. The default value of this object is dtmf(1).

Integer32 (50..500) · milliseconds

Outgoing DTMF digit duration in milliseconds. This object is not relevant to the addressing timing of the interfaces in the CAS group if ccasGrpStaCfgDialType is dtmf. The default value of this object is 100 milliseconds.

Integer32 (50..500) · milliseconds

Outgoing DTMF inter-digit duration in milliseconds. This object is not relevant to the addressing timing of the interfaces in the CAS group if ccasGrpStaCfgDialType is dtmf. The default value of this object is 100 milliseconds.

Integer32 (10..20) · pulses per second

Outgoing Pulse dialing rate in pulses per second (pps). This object is relevant to the addressing timing of the interfaces in the CAS group only if ccasGrpStaCfgDialType is pulse. The default value of this object is 10 pps.

Integer32 (100..1000) · milliseconds

Outgoing Pulse dialing inter-digit timing in milliseconds. This object is relevant to the addressing timing of the interfaces in the CAS group only if ccasGrpStaCfgDialType is pulse. The default value of this object is 500 milliseconds.

BITS

Specify the A/B/C/D bit mask to invert the A/B/C/D bits value before the A/B/C/D bits are sent or after the A/B/C/D bits are received. 1-bit - enable bit inversion. 0-bit - disable bit inversion. The default value of this object is '00'H.

BITS

Specify the Unused A/B/C/D bit values to transmit. If any A/B/C/D bit is unused, the bit values in this object will be used to transmit for the unused A/B/C/D bits. The default value of this object is '00'H

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

the ifIndex of this CAS channel associated T1/E1.

Integer32 (0..30)

The CAS channel associated CAS group number.

Integer32 (1..31)

The CAS channel associated T1/E1 timeslot.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

The CAS channel busyout configuration. true - the CAS channel is busied out. false - the CAS is normal. The default value for this object is 'false'.

BITS

Reference: EIA/TIA-464B, chapter 6.2 Digital Signaling and Supervision

The receive ABCD signaling bits for the CAS channel. aBit - the signaling bit in the 6th frame bBit - the signaling bit in the 12th frame cBit - the signaling bit in the 18th frame dBit - the signaling bit in the 24th frame the cBit and dBit are only valid for E1 or T1 interface is operating in extended superframe (ESF) mode.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

The CAS channel busyout state. true - the CAS channel is busied out. false - the CAS is normal.

INTEGER1 = unknown2 = speech3 = data564 = audio315 = audio76 = video7 = fax8 = modem · Integer32

Reference: Q.931 [8], chapter 4.5.5, octet 3 of bearer capability information element, combined with the User Rate (as defined in octets 5 and 5a to 5d), if rate adoption is being used.

The Information Transfer Capability for the current or last call. unknown - If since system startup there has been no call on this interface, this object has a value of unknown(1). speech - refers to a non-data connection data56 - 56k data. audio31 - audio 3.1 kHz; refers to data mode connections audio7 - audio 7 kHz; refer to data mode connections; 'Unrestricted digital information with tones/ announcements'. video - as defined in Q.931 fax - Facsimile modem - V.3x modem

BITS

Reference: EIA/TIA-464B, chapter 6.2 Digital Signaling and Supervision

The transmit ABCD signaling bits for the CAS channel. aBit - the signaling bit in the 6th frame bBit - the signaling bit in the 12th frame cBit - the signaling bit in the 18th frame dBit - the signaling bit in the 24th frame the cBit and dBit are only valid for E1 or T1 interface is operating in extended superframe (ESF) mode.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

The object indicates whether or not the background noise should be played to fill silence gaps if VAD is activated. The default value of this object is 'true'.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

The object indicates whether or not the Nonlinear Processing is enabled for the interface. The default value of this object is 'true'.

Integer32 (-70..-30) · dBm

The object specifies the Music On Hold Threshold for the interface. The default value of this object is -38 dBm.

Integer32 (-6..14) · dB

This object contains the amount of gain inserted at the receiver side of the interface. The input gain settings only define a gain/loss relative to the 0 dB setting. The absolute loss at the 0 dB setting could be implementation dependent based on the desired network loss plan. The default value of this object is 0 dB (decibel).

Integer32 (0..14) · dB

This object contains the amount of attenuation inserted at the transmit side of the interface. The output attenuation settings only define a loss relative to the 0 dB setting. The absolute loss at the 0 dB setting could be implementation dependent based on the desired network loss plan. The default value of this object is 0 dB (decibel).

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

The object specifies whether or not the Echo Cancellation is enabled for the interface. The default value of this object is 'true'.

INTEGER1 = echoCanceller8ms2 = echoCanceller16ms3 = echoCanceller24ms4 = echoCanceller32ms5 = echoCanceller64ms6 = echoCanceller128ms · Integer32

The object specifies the Echo Canceller coverage for the interface. This object is valid if the ccasVoiceCfgEchoCancelEnable object is 'true'. echoCanceller8ms - 8 milliseconds echo canceller coverage. echoCanceller16ms - 16 milliseconds echo canceller coverage. echoCanceller24ms - 24 milliseconds echo canceller coverage. echoCanceller32ms - 32 milliseconds echo canceller coverage. echoCanceller64ms - 64 milliseconds echo canceller coverage. echoCanceller128ms- 128 milliseconds echo canceller coverage. The default value of this object is echoCanceller8ms.

INTEGER1 = normal2 = trunk3 = plar · Integer32

The object indicates the connection mode of the interface. normal - the interface acts normally to handle incoming and outgoing call. trunk - the interface acts in trunking mode. trunking mode causes two interfaces (on either the same or different routers) to be always conferenced together, and for telephony signaling to be passed transparently through the VoIP system rather than trapped and interpreted by the session application on the router(s). plar - the interface acts in PLAR (private line automatic ringdown) mode. PLAR is handled by associating a peer directly with an interface such that when the interface goes off-hook, that peer is used to setup the second call leg and conference them together without the caller having to dial any digits.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..32) · OCTET STRING · hint 255a

This is the E.164 phone number that is used to establish connection with trunking mode or PLAR mode. If the ccasVoiceCfgConnectionMode is 'normal', then this object will be a zero length string.

Integer32 (0..120) · seconds

This is the initial digit timeout that indicates the amount of time the managed system waits for an initial input digit from the caller. The timer is activated when the call is accepted and is deactivated upon digit input. If the timer expires, the caller is signaled through the appropriate tone and the call is abandoned. The value of zero disables the timer. The default value of this object is 10 seconds.

Integer32 (0..120) · seconds

This is the inter-digit timeout that indicates the amount of time the managed system waits for a subsequent input digit from the caller. The timer is started upon receipt of an input digit and restarted as each digit is received until the destination address is identified. If the timer expires and no destination address is identified, the caller is signaled through the appropriate tone and the call is abandoned. The value of zero disables the timer. The default value of this object is 10 seconds.

CountryCodeRepresents a case-insensitive 2-letter country code taken from ISO-3166. Unrecognized countries are represented as empty string. SIZE (0 | 2) · OCTET STRING

This object contains the current regional setting for the call progress tone to be used by this CAS group.

Integer32 (280..3800) · hertz

Reference: Bellcore GR-317-CORE spec, Rev 3, Nov. 1996, section 3.1.1.3.

This object specifies the continuity test tone frequencies for co1. Co1 is the COT tone frequency from the terminating switch in transponder mode and is from the originating switch in loopback mode.

Integer32 (280..3800) · hertz

Reference: Bellcore GR-317-CORE spec, Rev 3, Nov. 1996, section 3.1.1.3.

This object specifies the continuity test tone frequencies for co2. Co2 is the COT tone frequency from the originating switch only in transponder mode.