|
|
The data group contains the objects that enable you to set up groups and define the rules that determine how your switch functions.
The data group consists of the following:
Use the resource group table to organize and allocate system resources. This includes setting parameters to determine how the ports assigned to the group function. You must first establish resource groups before you assign ports. Then, assign the ports to the resource group with objects in the port tables. The input to the port table object is the number of the resource group.
{data 1}
Description
Resource group table.
Object Identifier
1.3.6.1.4.1.886.1.9.1
Data Type
Sequence of ResGroupEntry
Access Policy
Not accessible
Status
Mandatory
{resGroupTable 1}
Description
An object in the resGroupTable.
Data Type
ResGroupEntry
Object Identifier
1.3.6.1.4.1.886.1.9.1.1
Access Policy
Not accessible
Status
Mandatory
Index
{resGroupIndex}
Sequence
resGroupIndex | Integer |
resGroupName | DisplayString |
resGroupHuntType | Integer |
resGroupPortCnt | Integer |
resGroupRhuntThres | Integer |
resGroupBusyThres | Integer |
resGroupErrorStatus | Integer |
resGroupOwnerString | OwnerString |
resGroupEntryStatus | EntryStatus |
{resGroupEntry 1}
Description
Indicates the number of the resource group.
Object Identifier
1.3.6.1.4.1.886.1.9.1.1.1
Data Type
Integer. Possible values range from 1 to 63 for 2K mode, and 1 to 224 for 4K mode.
Access Policy
Read only
Status
Mandatory
{resGroupEntry 2}
Description
Indicates the name of the resource group.
Object Identifier
1.3.6.1.4.1.886.1.9.1.1.2
Data Type
DisplayString. The field accepts up to 8 upper- and lowercase alphanumeric characters
Access Policy
Read-write
Status
Mandatory
{resGroupEntry 3}
Description
Determines the way in which the system selects resources for use from this group.
Object Identifier
1.3.6.1.4.1.886.1.9.1.1.3
Data Type
Integer. The valid numerical and string values are shown in the following table:
| Value | String | Meaning |
|---|---|---|
0 | none | Not set. |
1 | rotary | Hunt always begins with position 1. |
2 | cyclic | Initial hunt (after power-up/reboot) begins with position 1. Subsequent hunts begin with position following last successfully allocated resource. |
Access Policy
Read-write
Status
Mandatory
{resGroupEntry 4}
Description
Indicates the number of circuits currently in the resource group. This number is updated when you make changes to this resource group through the resGroup objects in the port tables.
Object Identifier
1.3.6.1.4.1.886.1.9.1.1.4
Data Type
Integer. The valid value are from 0 to 999 for 2K mode, or 0 to 1920 for 4K mode.
Access Policy
Read only
Status
Mandatory
{resGroupEntry 5}
Description
Auto Retry (rehunt) is available for outgoing ports only (COS = O or AO; also COS = 2) and is currently used as outgoing in a call.
This object indicates the number of times for each call the switch hunts this group for a new outgoing port if an outgoing supervision error is encountered.
Object Identifier
1.3.6.1.4.1.886.1.9.1.1.5
Data Type
Integer. Possible values range from 0 to 5. A value of zero (0) disables this feature for the group.
Access Policy
Read-write
Status
Mandatory
{resGroupEntry 6}
Description
Auto Makebusy is available for outgoing ports only (COS = O or AO; also COS = 2) and is currently used as outgoing in a call.
This object indicates the number of times the switch can detect a supervision error for a port in this group before the switch takes that port out of service (makebusy).
The error count is cleared at midnight.
Object Identifier
1.3.6.1.4.1.886.1.9.1.1.6
Data Type
Integer. Possible values range from 0 to 255. A value of zero (0) disables this feature for the group.
Access Policy
Read-write
Status
Mandatory
{resGroupEntry 7}
Description
Registers the last error that occurred in this resource group.
Object Identifier
1.3.6.1.4.1.886.1.9.1.1.7
Data Type
Integer. The possible values and their meanings are shown in the following table:
| Value | String |
|---|---|
513 | resourceGroupAlreadyExists |
514 | resourceGroupIsNotEmpty |
515 | invalidHuntType |
516 | exceededMaxNumOfPorts |
517 | invalidPosition |
518 | invalidPortType |
519 | portIsAlreadyInAGroup |
520 | portAndResourceGroupTypeAreDifferent |
521 | conferencePortCannotPutInNonconferenceGroup |
522 | mfrcPortCannotBePutInNonMfrcGroup |
523 | mfrc2PortCannotBePutInNonMfrc2Group |
524 | dtmfPortCannotBePutInNonDtmfGroup |
525 | srcPortCannotBePutInNonSrcGroup |
526 | cpaPortCannotBePutInNonCpaGroup |
527 | announcementPortCannotBePutInNonAnnouncementGroup |
528 | resourceGroupIsAlreadyEmpty |
529 | invalidValue |
530 | cannotGroupIsdnAndNonIsdnPorts |
Access Policy
Read only
Status
Mandatory
{resGroupEntry 8}
Description
The entity that configured this object and is therefore using the assigned resources.
Object Identifier
1.3.6.1.4.1.886.1.9.1.1.8
Data Type
OwnerString
Access Policy
Read-write
Status
Mandatory
{resGroupEntry 9}
Description
The status of this resource group object.
Object Identifier
1.3.6.1.4.1.886.1.9.1.1.9
Data Type
EntryStatus
Access Policy
Read-write
Status
Mandatory
{data 2}
Description
The time, displayed in hundredths of a second, since the resource group table was last modified. Helps NMS application developers determine the polling of the agent parameters.
Object Identifier
1.3.6.1.4.1.886.1.9.2
Data Type
TimeTicks
Access Policy
Read only
Status
Mandatory
The resource group port table shows the association between the resource groups and the ports assigned to a particular resource group.
{data 4}
Description
A table representing the association between the resource groups and the ports assigned to a particular resource group.
Data Type
Sequence of ResGroupPortEntry
Object Identifier
1.3.6.1.4.1.886.1.9.4
Access Policy
Not accessible
Status
Mandatory
{resGroupPortTable 1}
Description
An entry in the resGroupPortTable.
Object Identifier
1.3.6.1.4.1.886.1.9.4.1
Data Type
ResGroupPortEntry
Access Policy
Not accessible
Status
Mandatory
Index
{resGroupIndex, resGroupPortPosition}
Sequence
resGroupPortPosition | Integer |
resGroupCardIndex | Integer |
resGroupSpanNum | Integer |
resGroupPortNum | Integer |
{resGroupPortEntry 1}
Description
Specifies the order in which ports are assigned to a resource group. This is the secondary index to the resGroupPortTable.
Object Identifier
1.3.6.1.4.1.886.1.9.4.1.1
Data Type
Integer
Access Policy
Read only
Status
Mandatory
{resGroupPortEntry 2}
Description
Corresponds to the physical location of the card to which the port belongs.
Object Identifier
1.3.6.1.4.1.886.1.9.4.1.2
Data Type
CardIndex
Access Policy
Read only
Status
Mandatory
{resGroupPortEntry 3}
Description
Specifies the span number to which the port belongs.
Object Identifier
1.3.6.1.4.1.886.1.9.4.1.3
Data Type
Integer
Access Policy
Read only
Status
Mandatory
{resGroupPortEntry 4}
Description
Specifies which port is assigned to the resource group.
Object Identifier
1.3.6.1.4.1.886.1.9.4.1.4
Data Type
Integer
Access Policy
Read only
Status
Mandatory
Use the inpulse rules table to define the inpulse rules in call processing. For more information on inpulse rules and how to configure them, refer to the Cisco VCO/4K Extended Programming Reference or Cisco VCO/4K Standard Programming Reference.
{data 5}
Description
A list of inpulse rules.
Object Identifier
1.3.6.1.4.1.886.1.9.5
Data Type
Sequence of InpulseRuleEntry
Access Policy
Not accessible
Status
Mandatory
{inpulseRuleTable 1}
Description
A combination of the tokens and arguments that make up a single inpulse rule.
Object Identifier
1.3.6.1.4.1.886.1.9.5.1
Data Type
InpulseRuleEntry
Access Policy
Not accessible
Status
Mandatory
Index
{inpulseRuleIndex}
Sequence
inpulseRuleIndex | Integer |
inpulseRuleErrorStatus | Integer |
inpulseRuleOwnerString | OwnerString |
inpulseRuleEntryStatus | EntryStatus |
{inpulseRuleEntry 1}
Description
Identifies the inpulse rule. Users specify inpulse rules by entering a number at the control console as the default in the Line and Trunk Card Configuration screens, or as a programming command.
Object Identifier
1.3.6.1.4.1.886.1.9.5.1.1
Data Type
Integer. Valid inpulse rule numbers are from 1 to 30 for 2K mode, or 1 to 255 for 4K mode.
Access Policy
Read only
Status
Mandatory
{inpulseRuleEntry 2}
Description
Registers the last error that occurred in this inpulse rule table.
Object Identifier
1.3.6.1.4.1.886.1.9.5.1.2
Data Type
Integer. The possible values and their meanings are shown in the following table:
| Value | String |
|---|---|
1280 | inpulseRuleAlreadyExists |
1281 | inpulseRuleIsEmpty |
1282 | invalidPosition |
1283 | exceededNumOfInstructions |
1284 | illegalTokenValue |
1285 | illegalArg |
Access Policy
Read only
Status
Mandatory
{inpulseRuleEntry 3}
Description
The entity that configured this entry and is therefore using the inpulse rule assigned to it.
Object Identifier
1.3.6.1.4.1.886.1.9.5.1.3
Data Type
OwnerString
Access Policy
Read-write
Status
Mandatory
{inpulseRuleEntry 4}
Description
The status of the inpulse rule entry. This object also determines whether you can modify the corresponding entries in the inpulseRuleInstructionTable.
Object Identifier
1.3.6.1.4.1.886.1.9.5.1.4
Data Type
EntryStatus
Access Policy
Read-write
Status
Mandatory
The inpulse rule instruction table shows the association between the inpulse rule table and the instructions assigned to a particular rule. You can define up to 16 instructions, comprising tokens for a single rule. Use the rules to condition a line or trunk to wait for supervision events, collect MF/DTMF digits, and store received digits in an internal system call record.
{data 6}
Description
A matrix of inpulse rule instructions.
Object Identifier
1.3.6.1.4.1.886.1.9.6
Data Type
Sequence of InpulseRuleInstructionEntry
Access Policy
Not accessible
Status
Mandatory
{inpulseRuleInstructionTable 1}
Description
An inpulse rule instruction—a combination of a token and an argument that constitutes a single inpulse rule instruction.
Object Identifier
1.3.6.1.4.1.886.1.9.6.1
Data Type
InpulseRuleInstructionEntry
Access Policy
Not accessible
Status
Mandatory
Index
{inpulseRuleIndex, inpulseRuleInstructionIndex}
Sequence
inpulseRuleInstructionIndex | Integer |
inpulseRuleToken | Integer |
inpulseRuleArg | Integer |
{inpulseRuleInstructionEntry 1}
Description
Identifies the instruction in an inpulse rule. An inpulse rule is made up of 1 to 16 instructions.
Object Identifier
1.3.6.1.4.1.886.1.9.6.1.1
Data Type
Integer. The possible values are from 1 to 16.
Access Policy
Read only
Status
Mandatory
{inpulseRuleInstructionEntry 2}
Description
The operator token in an inpulse rule instruction.
Object Identifier
1.3.6.1.4.1.886.1.9.6.1.2
Data Type
Integer. The integer can be any one of the following values. For further information, refer to the Cisco VCO/4K Extended Programming Reference.
| Value | Token Name |
|---|---|
0 | illegal |
1 | repEnd |
2 | repEach |
3 | repNext |
4 | noRep |
5 | dtmf |
6 | dtmf4 |
7 | mf |
8 | mfcr2 |
9 | ipAni |
10 | ipField |
11 | digits |
12 | endChar1 |
13 | endChar2 |
14 | clrChar1 |
15 | clrChar2 |
16 | winkEnab |
17 | toneEnab |
18 | toneClr |
19 | toneEnd |
20 | toneFdig |
21 | timField |
22 | timFdig |
23 | timInter |
24 | route |
25 | winkNow |
26 | answer |
27 | toneNow |
28 | speak |
29 | record |
30 | library |
31 | maxRec |
32 | stopVoic |
33 | loopLast |
34 | loopAll |
35 | release |
36 | retain |
37 | waitTime |
38 | isdnRx |
39 | isdnTx |
40 | gotoRule |
41 | doIrule |
42 | doOrule |
43 | contRep |
44 | contNrep |
45 | glare |
46 | noHost |
47 | ipCat2 |
48 | apendAni |
49 | apendFld |
Access Policy
Read-write
Status
Mandatory
{inpulseRuleInstructionEntry 3}
Description
The additional data field, the notation [xx] indicates that additional data entry is required. Refer to the Cisco VCO/4K Extended Programming Reference for inpulse rule field descriptions.
Object Identifier
1.3.6.1.4.1.886.1.9.6.1.3
Data Type
Integer. The possible values, token name, and description of the additional data field is shown in the following table:
| Value | Token Name | Token Argument |
|---|---|---|
0 | illegal | Not Applicable |
1 | repEnd | Not Applicable |
2 | repEach | Not Applicable |
3 | repNext | Not Applicable |
4 | noRep | Not Applicable |
5 | dtmf | Not Applicable |
6 | dtmf4 | Not Applicable |
7 | mf | Not Applicable |
8 | mfcr2 | Not Applicable |
9 | ipAni | 1 to 40 |
10 | ipField | 1 to 4 |
11 | digits | 1 to 40 |
12 | endChar1 | 1 digit - 0 to 9 (0 to 15 for MFCR2), A-F (when 4th column DTMF is enabled), *, # |
13 | endChar2 | 2 digits - 0 to 9 (0 to 15 for MFCR2), A-F (when 4th column DTMF is enabled), *, # |
14 | clrChar1 | 1 digit - 0 to 9 (0 to 15 for MFCR2), A-F (when 4th column DTMF is enabled), *, # |
15 | clrChar2 | 2 digits - 0 to 9 (0 to 15 for MFCR2), A-F (when 4th column DTMF is enabled), *, # |
16 | winkEnab | Not Applicable |
17 | toneEnab | 0 to 63 |
18 | toneClr | 0 to 63 |
19 | toneEnd | 0 to 63 |
20 | toneFdig | 0 to 63 |
21 | timField | 1 to 60 |
22 | timFdig | 1 to 30 |
23 | timInter | 1 to 10 |
24
| route | 1 to 10 (where 1 = A and 10 = J) |
Ex: Route A =17(10) 0x11 | ||
25 | winkNow | Not Applicable |
26 | answer | Not Applicable |
27 | toneNow | 0 to 63 |
28 | speak | 1 to 255 |
29 | record | 1 to 255 |
30 | library | 1 to 16, and 255 (255 = TMP) |
31 | maxRec | 1 to 255 |
32 | stopVoic | Not Applicable |
33 | loopLast | Not Applicable |
34 | loopAll | Not Applicable |
35 | release | IPR=16, MRC=5, DRC=4, DTG=7, CPA=22 |
36 | retain | 16 (IPRC) |
37 | waitTime | 1 to 10 |
38 | isdnRx | 1 to 96 |
39 | isdnTx | 1 to 96 |
40 | gotoRule | 1 to 255 (rule to be executed) |
41 | doIrule | 1 to 255 (rule to be executed) |
42 | doOrule | 1 to 255 (rule to be executed) |
43 | contRep | Not Applicable |
44 | contNrep | Not Applicable |
45 | glare | 1 to 255 (rule to be executed) |
46 | noHost | 1 to 255 (rule to be executed) |
47 | ipCat2 | Not Applicable |
48 | apendAni | 1 to 40 |
49 | apendFld | 1 to 4 |
Access Policy
Read-write
Status
Optional
{data 7}
Description
The time, displayed in hundredths of a second, since the inpulse rule table was last modified. Helps NMS application developers determine the polling of the agent parameters.
Object Identifier
1.3.6.1.4.1.886.1.9.7
Data Type
TimeTicks
Access Policy
Read only
Status
Mandatory
The outpulse rules table is used to define the outpulse rules for use in call processing. For more information on outpulse rules and how to configure them, refer to the Cisco VCO/4K Extended Programming Reference or Cisco VCO/4K Standard Programming Reference.
{data 9}
Description
A list of outpulse rules. An inpulse rule instruction DO ORULE (XX) acts as an entry point to this table, where (XX) is the outpulseRuleIndex in the outpulseRuleTable.
Object Identifier
1.3.6.1.4.1.886.1.9.9
Data Type
Sequence of OutpulseRuleEntry
Access Policy
Not accessible
Status
Mandatory
{outpulseRuleTable 1}
Description
Indicates a single outpulse rule.
Object Identifier
1.3.6.1.4.1.886.1.9.9.1
Data Type
OutpulseRuleEntry
Access Policy
Not accessible
Status
Mandatory
Index
{outpulseRuleIndex}
Sequence
outpulseRuleIndex | Integer |
outpulseRuleErrorStatus | Integer |
outpulseRuleOwnerString | OwnerString |
outpulseRuleEntryStatus | EntryStatus |
{outpulseRuleEntry 1}
Description
Identifies the outpulse rule entry.
Object Identifier
1.3.6.1.4.1.886.1.9.9.1.1
Data Type
Integer. Valid outpulse rule numbers are from 1 to 30 for 2K mode, or 1 to 255 for 4K mode.
Access Policy
Read only
Status
Mandatory
{outpulseRuleEntry 2}
Description
Registers the last error that occurred in this outpulseRule table.
Object Identifier
1.3.6.1.4.1.886.1.9.9.1.2
Data Type
Integer. The possible values and their meanings are shown in the following table:
| Value | String |
|---|---|
1024 | outpulseRuleAlreadyExists |
1025 | outpulseRuleIsEmpty |
1026 | invalidPosition |
1027 | exceededMaxNumberOfInstructions |
1028 | illegalTokenValue |
1029 | illegalArg |
Access Policy
Read only
Status
Mandatory
{outpulseRuleEntry 3}
Description
The entity that configured this object and is therefore using the assigned outpulse rule.
Object Identifier
1.3.6.1.4.1.886.1.9.9.1.3
Data Type
OwnerString
Access Policy
Read-write
Status
Mandatory
{outpulseRuleEntry 4}
Description
The status of the outpulse rule entry. This object also determines whether you can modify the corresponding table entries in the outpulseRuleInstructionTable.
Object Identifier
1.3.6.1.4.1.886.1.9.9.1.4
Data Type
EntryStatus
Access Policy
Read-write
Status
Mandatory
The outpulse rule instruction table shows the association between the outpulse rule table and the instructions assigned to a particular rule. You can define up to 16 instructions, comprising tokens for a single rule. Use the rules to condition a line or trunk to wait for supervision events, collect MF/DTMF digits, and store received digits in an internal system call record.
{data 10}
Description
A matrix of outpulse rule instructions.
Object Identifier
1.3.6.1.4.1.886.1.9.10
Data Type
Sequence of OutpulseRuleInstructionEntry
Access Policy
Not accessible
Status
Mandatory
{outpulseRuleInstructionTable 1}
Description
An entry containing a single outpulse rule instruction.
Object Identifier
1.3.6.1.4.1.886.1.9.10.1
Data Type
OutpulseRuleInstructionEntry
Access Policy
Not accessible
Status
Mandatory
Index
{outpulseRuleIndex, outpulseRuleInstructionIndex}
Sequence
outpulseRuleInstructionIndex | Integer |
outpulseRuleToken | Integer |
outpulseRuleArg | Integer |
{outpulseRuleInstructionEntry 1}
Description
Identifies the instruction in an outpulse rule.
Object Identifier
1.3.6.1.4.1.886.1.9.10.1.1
Data Type
Integer. Up to 16 tokens make an outpulse rule.
Access Policy
Read only
Status
Mandatory
{outpulseRuleInstructionEntry 2}
Description
The operator token is an outpulse rule instruction.
Object Identifier
1.3.6.1.4.1.886.1.9.10.1.2
Data Type
Integer. The integer can be any one of the following values. For further information, refer to the Cisco VCO/4K Extended Programming Reference.
| Value | Meaning |
|---|---|
0 | illegal |
1 | repEnd |
2 | repNext |
3 | opDtmf |
4 | opMf |
5 | opMfcr2 |
6 | opPulse |
7 | opAni |
8 | opField |
9 | opDigit |
10 | opTone |
11 | opCat |
12 | waitSup |
13 | finalSup |
14 | timeSup |
15 | seize |
16 | waitTime |
17 | retain |
18 | release |
19 | isdnRx |
20 | isdnTx |
21 | isdnSup |
22 | gotoRule |
23 | doIrule |
24 | doOrule |
25 | noHost |
26 | opCat2 |
27 | ansSup |
Access Policy
Read-write
Status
Mandatory
{outpulseRuleinstructionEntry 3}
Description
The additional data object. The notation [xx] indicates that additional data entry is required. For example, the additional data field value depends on the value of the InpulseRuleToken field.
Object Identifier
1.3.6.1.4.1.886.1.9.10.1.3
Data Type
Integer. The possible values, token name, and description of the additional data field is shown in the following table:
| Token Name | Meaning |
|---|---|
illegal | Not applicable |
repEnd | Not applicable |
repEach | Not applicable |
repNext | Not applicable |
noRep | Not applicable |
opDtmf | Not applicable |
opMf | Not applicable |
opMfcr2 | Not applicable |
opPulse | Not applicable |
opAni | Not applicable |
opField | 1 to 4 |
opDigit | 1 digit - DTMF mode: 0 to 9, *, #, A-F (*, E and #, F are interchangeable MF mode: 0 to 9, KP, ST, S1, S2, S3 Tone mode: 0 to 8 |
opTone | Not applicable |
opCat | 0 to 15 |
waitSup | 1 to 24, A(25) or W(26) |
finalSup | 1 to 24, A(25) or W(26) |
timeSup | 1 to 60 |
seize | Not applicable |
waitTime | 1 to 10 |
retain | 16 (IPR) |
release | IPR=16, MRC=5, DRC=4, DTG=7, CPA=22 |
isdnRx | 1 to 96 |
isdnTx | 1 to 96 |
isdnSup | 1 to 24 |
gotoRule | 1 to 255 (the rule to be executed) |
gotoIrule | 1 to 255 (the rule to be executed) |
doOrule | 1 to 255 (the rule to be executed) |
noHost | 1 to 255 (the rule to be executed) |
opCat2 | Not applicable |
ansSup | 1 to 24 |
Access Policy
Read-write
Status
Optional
{data 11}
Description
The time, displayed in hundredths of a second, since the outpulse rule table was last modified. Helps NMS application developers determine the polling of the agent parameters.
Object Identifier
1.3.6.1.4.1.886.1.9.11
Data Type
TimeTicks
Access Policy
Read only
Status
Mandatory
Standard ISDN PRI consists of 23 B+D channels, where a single signaling channel (D-channel) controls the remaining 23 bearer channels (B-channels) on the interface. In system terms, this means that Ports 1 through 23 on the PRIN/N card (B-channel) are controlled by Port 24 (D-channel). The NFAS option extends D-channel control to B-channels not resident on the same interface. This enables a single D-channel to control up to 20 interfaces (a maximum of 479 B-channels).
An NFAS group is a listing of all PRI/N and/or T1 cards for which a specified D-channel receives call control messages.
{data 13}
Description
A table that lists all PRI/N and/or T1 cards for which a specified D-channel receives call control messages.
Object Identifier
1.3.6.1.4.1.886.1.9.13
Data Type
Sequence of NfasGroupEntry
Access Policy
Not accessible
Status
Mandatory
{nfasGroupTable 1}
Description
An object representing an NFAS group.
Object Identifier
1.3.6.1.4.1.886.1.9.13.1
Data Type
NfasGroupEntry
Access Policy
Not accessible
Status
Mandatory
Index
{nfasGroupIndex}
Sequence
nfasGroupIndex | Integer |
nfasGroupName | DisplayString |
nfasGroupPriDChannelCardIndex | CardIndex |
nfasGroupPriDChannelState | Integer |
nfasGroupBkupDChannelCardIndex | CardIndex |
nfasGroupBkupDChannelState | Integer |
nfasGroupCmd | Integer |
nfasGroupErrorStatus | Integer |
nfasGroupOwnerString | OwnerString |
nfasGroupEntryStatus | EntryStatus |
{nfasGroupEntry 1}
Description
Indicates the number of the NFAS group.
Object Identifier
1.3.6.1.4.1.886.1.9.13.1.1
Data Type
Integer. Possible values for this field are from 1 to 37.
Access Policy
Read only
Status
Mandatory
{nfasGroupEntry 2}
Description
Indicates the name assigned to the NFAS group.
Object Identifier
1.3.6.1.4.1.886.1.9.13.1.2
Data Type
DisplayString. Length of the display string is from 1 to 8 characters.
Access Policy
Read-write
Status
Mandatory
{nfasGroupEntry 3}
Description
Indicates the physical location (hardware address) of the card that contains the D-channel designated as the primary control channel for this NFAS group. The index object lists the rack (R), level (L), and slot (S) where the card resides.
Object Identifier
1.3.6.1.4.1.886.1.9.13.1.3
Data Type
CardIndex
Access Policy
Read-write
Status
Mandatory
{nfasGroupEntry 4}
Description
Indicates the current state of the primary D-channel. With the exception of the MOOS (Manual Out-of-Service) state, link signaling between the system and the network interface controls the state transitions.
Object Identifier
1.3.6.1.4.1.886.1.9.13.1.4
Data Type
Integer. The valid numerical and string values for this field are shown in the following table:
| Value | String | Meaning |
|---|---|---|
1 | is | In Service |
2 | stby | Standby |
3 | mb | Maintenance Bust |
4 | wait | Wait |
5 | moos | Manual Out-of-Service |
6 | oos | Out-of-Service |
Access Policy
Read only
Status
Mandatory
{nfasGroupEntry 5}
Description
Indicates the physical location (hardware address) of the card that contains the D-channel designated as the primary control channel for this NFAS group. The index object lists the rack (R), level (L), and slot (S) where the card resides.
Object Identifier
1.3.6.1.4.1.886.1.9.13.1.5
Data Type
CardIndex
Access Policy
Read-write
Status
Mandatory
{nfasGroupEntry 6}
Description
Indicates the current state of the backup D-channel. With the exception of the MOOS (Manual Out-of-Service) state, link signaling between the system and the network interface controls the state transitions.
Object Identifier
1.3.6.1.4.1.886.1.9.13.1.6
Data Type
Integer. The valid numerical and string values are shown in the following table:
| Value | String | Meaning |
|---|---|---|
1 | is | In Service |
2 | stby | Standby |
3 | mb | Maintenance Bust |
4 | wait | Wait |
5 | moos | Manual Out-of-Service |
6 | oos | Out-of-Service |
Access Policy
Read-write
Status
Mandatory
{nfasGroupEntry 7}
Description
Use this object to change the state of the backup D-channel with one of three commands. Use the nfasGroupCmd to perform the following tasks:
 |
Note This command is effective as soon as you set this object. You can set the command object only if this is the only attribute that you have changed since you placed the status of the object in underModification mode. |
Object Identifier
1.3.6.1.4.1.886.1.9.13.1.7
Data Type
Integer. The valid numerical and string values are shown in the following table:
| Value | String | Meaning |
|---|---|---|
1 | none | No change. |
2 | moos | Places the D-channel currently in STBY state into Manual Out-of-Service state, regardless of its current state. The D-channel remains in MOOS state until you enter an activate command. |
3 | activate | Enables you to change the D-channel from MOOS to OOS state. |
4 | switch | Causes a manual D-channel switchover. The standby D-channel becomes active (IS) and assumes control of the NFAS group. This command is valid only when you specify a backup D-channel for the group. The standby D-channel must be in STBY state for the switchover to take place. |
Access Policy
Read-write
Status
Mandatory
{nfasGroupEntry 8}
Description
Registers the last error that occurred in this NFAS group table.
Object Identifier
1.3.6.1.4.1.886.1.9.13.1.8
Data Type
Integer. The possible values and their meanings are shown in the following table:
| Value | String |
|---|---|
769 | interfaceCardMustbeT1orPRI-N |
770 | priCardMustHaveNfasDesignation |
771 | invalidConfigurationNumber |
772 | beginningofNfasConfigurationTable |
773 | endofNfasConfigurationTable |
774 | primaryD-channelMustbePRI-NCard |
775 | backupD-channelMustbePRI-NCard |
776 | cardAlreadyDefinedInAnotherGroup |
777 | cardAlreadyEntered |
778 | primaryD-channelNotOOS |
779 | backupD-channelNotOOS |
780 | nullValueNotAllowed |
782 | cardNotOutofService |
784 | nfasConfigurationUpdated |
785 | updateCanceled |
786 | noNfasConfigurationChangesDetected |
787 | primaryD-channelMustAppearInGroup |
788 | backupD-channelMustAppearInGroup |
789 | cardIsConfiguredAs24BNoD-channel |
790 | d-chanStatesHaveChangedPressREDRAW |
792 | commandAborted |
793 | invalidD-chanStatesDetected |
794 | memoryAllocationFailedForCommand |
795 | adminD-chanSWITCHCommandSubmitted |
796 | adminD-chanMOOSCommandSubmitted |
797 | adminD-chanACTIVATECommandSubmitted |
798 | nfasGroupAlreadyExists |
799 | nfasGroupIsNotEmpty |
800 | fatalErrorInNfasGroupProcessing |
801 | invalidPosition |
802 | exceededMaxNumOfInterfaces |
803 | invalidArgument |
804 | nfasGroupWasChanged |
805 | dChannelAlreadyManuallyOOS |
806 | dChannelAlreadyActive |
807 | backupChannelNotStandby |
Access Policy
Read only
Status
Mandatory
{nfasGroupEntry 9}
Description
The entity that configured this object and is therefore using the NFAS-assigned group.
Object Identifier
1.3.6.1.4.1.886.1.9.13.1.9
Data Type
OwnerString
Access Policy
Read-write
Status
Mandatory
{nfasGroupEntry 10}
Description
The status of the NFAS group object.
Object Identifier
1.3.6.1.4.1.886.1.9.13.1.10
Data Type
EntryStatus
Access Policy
Read-write
Status
Mandatory
{data 14}
Description
The time, displayed in hundredths of a second, since the NFAS group table was last modified. Helps NMS application developers determine the polling of the agent parameters.
Object Identifier
1.3.6.1.4.1.886.1.9.14
Data Type
TimeTicks
Access Policy
Read only
Status
Mandatory
The NFAS interface table is a read-only list of the interfaces in the NFAS groups. It enables quick enumeration of the interfaces in NFAS groups.
{data 16}
Description
A list of the interfaces in the NFAS Groups.
Object Identifier
1.3.6.1.4.1.886.1.9.16
Data Type
Sequence of NfasInterfaceEntry
Access Policy
Not accessible
Status
Mandatory
{nfasInterfaceTable 1}
Description
An object representing an NFAS interface entry.
Object Identifier
1.3.6.1.4.1.886.1.9.16.1
Data Type
nfasInterfaceEntry
Access Policy
Not accessible
Status
Mandatory
Index
{nfasGroupIndex, nfasInterfaceNum}
Sequence
nfasInterfaceNum | Integer |
nfasInterfaceCardIndex | CardIndex |
nfasInterfaceSpanNum | Integer |
[nfasInterfaceEntry 1}
Description
Specifies the interface number of the T1 or PRI/N card being added to the NFAS Group. Up to 20 interfaces, including those containing the primary and the backup D-channels, are listed for each NFAS group. This is the secondary index into the interface table.
Object Identifier
1.3.6.1.4.1.886.1.9.16.1.1
Data Type
Integer. Possible values for this field are from 1 to 20.
Access Policy
Read-write
Status
Mandatory
{nfasInterfaceEntry 2}
Description
Indicates the physical location (hardware address) of the card. The index object lists rack (R), level (L), and slot (S) where the card resides.
Object Identifier
1.3.6.1.4.1.886.1.9.16.1.2
Data Type
CardIndex
Access Policy
Read only
Status
Mandatory
{nfasInterfaceEntry 3}
Description
For 4XT1 and 4XE1 cards, this field specifies the span number.
Object Identifier
1.3.6.1.4.1.886.1.9.16.1.3
Data Type
Integer
Access Policy
Read only
Status
Mandatory
Use the answer supervision templates with the ANS SUP [xx], WAIT SUP, and FINAL SUP outpulse rule tokens. For further information on answer supervision templates, refer to the Cisco VCO/4K System Administrator's Guide.
{data 19}
Description
A list of answer supervision template entries.
Object Identifier
1.3.6.1.4.1.886.1.9.19
Data Type
Sequence of AnsSupTempEntry
Access Policy
Not accessible
Status
Mandatory
{ansSupTempTable 1}
Description
A table entry which consists of the fields of a template.
Object Identifier
1.3.6.1.4.1.886.1.9.19.1
Data Type
AnsSupTempEntry
Access Policy
Not accessible
Status
Mandatory
Index
{ansSupTempIndex}
Sequence
ansSupTempIndex | Integer |
ansSupTempDialTone | Integer |
ansSupTempRingback | Integer |
ansSupTempBusy | Integer |
ansSupTempReorder | Integer |
ansSupTempSitTones | Integer |
ansSupTempRingCess | Integer |
ansSupTempVoiceCess | Integer |
ansSupTempVoiceDet | Integer |
ansSupTempWink | Integer |
ansSupTempAnswer | Integer |
ansSupTempTime | Integer |
ansSupTempHookFlash | Integer |
ansSupTempPagerCue | Integer |
ansSupTempIsupTone | Integer |
ansSupTempIsupCess | Integer |
ansSupTempErrorStatus | Integer |
ansSupTempOwnerString | OwnerString |
ansSupTempEntryStatus | EntryStatus |
{ansSupTempEntry 1}
Description
Identifies the specific template configuration for use with the WAIT SUP and FINAL SUP outpulse rule tokens.
Object Identifier
1.3.6.1.4.1.886.1.9.19.1.1
Data Type
Integer. Valid template numbers are from 1 to 24.
Access Policy
Read only
Status
Mandatory
{ansSupTempEntry 2}
Description
Dial Tone—Signal indicates the connected equipment is ready to receive digits. The signal is a combined 350-Hz and 440-Hz steady tone. The event is reported after approximately 0.75 seconds (requires CPA).
Object Identifier
1.3.6.1.4.1.886.1.9.19.1.2
Data Type
Integer. The valid numerical and string values are shown in the following table. For further information, refer to the Cisco VCO/4K System Administrator's Guide.
| Value | String | Meaning |
|---|---|---|
0 | empty |
|
1 | ok | Ends template processing when the system detects the tone, but it is not reported to the host. |
2 | okrep | Events assigned OKREP tokens are handled like OK tokens, but okrep also generates a report to the host. |
3 | ansbk | Causes the system to answerback over the incoming port. A report is not sent to the host. |
4 | ansrep | Handled like ANSBK tokens, but ansrep also generates a report to the host. |
5 | rep | Reported to the host when detected by the system, but rep does not end template processing. |
6 | error | Specifies that the signaling event should be treated as a supervision error. Causes a rehunt for another outgoing port (if the outgoing resource group is configured for rehunting). |
7 | fail | Specifies that the signaling event indicates a failed call. The outgoing port is removed from the call (no rehunt performed) and the incoming port is left in setup. |
8 | quit | Specifies that the signaling event causes outpulse rule processing to abort. Template processing ends, and the outgoing port returns to the state it was in prior to outpulse rule processing (CP_IDLE, CP_ATT, CP_SETUP or CP_STAB) but is not removed from the call. |
Access Policy
Read-write
Status
Mandatory
{ansSupTempEntry 3}
Description
Ringback—Signal indicates a connection is established to the called equipment, although the call is not completed until answer supervision is received. Audible ringback is a combination of 440 Hz and 480 Hz with a cadence of 2 seconds on followed by 4 seconds off. Ringback, including non-precise or "dirty" ringback, is reported after two cycles (requires CPA).
Object Identifier
1.3.6.1.4.1.886.1.9.19.1.3
Data Type
Integer. The valid numerical and string values are shown in the following table. For further information, refer to the Cisco VCO/4K System Administrator's Guide.
| Value | String | Meaning |
|---|---|---|
0 | empty |
|
1 | ok | Ends template processing when the system detects the tone, but it is not reported to the host. |
2 | okrep | Events assigned OKREP tokens are handled like OK tokens, but okrep also generates a report to the host. |
3 | ansbk | Causes the system to answerback over the incoming port. A report is not sent to the host. |
4 | ansrep | Handled like ANSBK tokens, but ansrep also generates a report to the host. |
5 | rep | Reported to the host when detected by the system, but rep does not end template processing. |
6 | error | Specifies that the signaling event should be treated as a supervision error. Causes a rehunt for another outgoing port (if the outgoing resource group is configured for rehunting). |
7 | fail | Specifies that the signaling event indicates a failed call. The outgoing port is removed from the call (no rehunt performed) and the incoming port is left in setup. |
8 | quit | Specifies that the signaling event causes outpulse rule processing to abort. Template processing ends, and the outgoing port returns to the state it was in prior to outpulse rule processing (CP_IDLE, CP_ATT, CP_SETUP or CP_STAB) but is not removed from the call. |
Access Policy
Read-write
Status
Mandatory
{ansSupTempEntry 4}
Description
Busy—Signal indicates the called equipment is in use. Combined 480-Hz and 620-Hz tone with 0.5 seconds on followed by 0.5 seconds off. The event is reported after two (precise) or three (non-precise) cycles of this pattern (requires CPA).
Object Identifier
1.3.6.1.4.1.886.1.9.19.1.4
Data Type
Integer. The valid numerical and string values are shown in the following table. For further information, refer to the Cisco VCO/4K System Administrator's Guide.
| Value | String | Meaning |
|---|---|---|
0 | empty |
|
1 | ok | Ends template processing when the system detects the tone, but it is not reported to the host. |
2 | okrep | Events assigned OKREP tokens are handled like OK tokens, but okrep also generates a report to the host. |
3 | ansbk | Causes the system to answerback over the incoming port. A report is not sent to the host. |
4 | ansrep | Handled like ANSBK tokens, but ansrep also generates a report to the host. |
5 | rep | Reported to the host when detected by the system, but rep does not end template processing. |
6 | error | Specifies that the signaling event should be treated as a supervision error. Causes a rehunt for another outgoing port (if the outgoing resource group is configured for rehunting). |
7 | fail | Specifies that the signaling event indicates a failed call. The outgoing port is removed from the call (no rehunt performed) and the incoming port is left in setup. |
8 | quit | Specifies that the signaling event causes outpulse rule processing to abort. Template processing ends, and the outgoing port returns to the state it was in prior to Outpulse Rule processing (CP_IDLE, CP_ATT, CP_SETUP or CP_STAB) but is not removed from the call. |
Access Policy
Read-write
Status
Mandatory
{ansSupTempEntry 5}
Description
Reorder—Signal indicates an error condition (for example, all circuits are busy, invalid destination, Permanent Signal Condition). Combined 480-Hz and 620-Hz tone with 0.25 seconds on followed by 0.25 seconds off. The event is reported after two (precise) or three (non-precise) cycles of this pattern. This feature requires CPA.
Object Identifier
1.3.6.1.4.1.886.1.9.19.1.5
Data Type
Integer. The valid numerical and string values are shown in the following table. For further information, refer to the Cisco VCO/4K System Administrator's Guide.
| Value | String | Meaning |
|---|---|---|
0 | empty |
|
1 | ok | Ends template processing when the system detects the tone, but it is not reported to the host. |
2 | okrep | Events assigned OKREP tokens are handled like OK tokens, but okrep also generates a report to the host. |
3 | ansbk | Causes the system to answerback over the incoming port. A report is not sent to the host. |
4 | ansrep | Handled like ANSBK tokens, but ansrep also generates a report to the host. |
5 | rep | Reported to the host when detected by the system, but rep does not end template processing. |
6 | error | Specifies that the signaling event should be treated as a supervision error. Causes a rehunt for another outgoing port (if the outgoing resource group is configured for rehunting). |
7 | fail | Specifies that the signaling event indicates a failed call. The outgoing port is removed from the call (no rehunt performed) and the incoming port is left in setup. |
8 | quit | Specifies that the signaling event causes outpulse rule processing to abort. Template processing ends, and the outgoing port returns to the state it was in prior to outpulse rule processing (CP_IDLE, CP_ATT, CP_SETUP or CP_STAB) but is not removed from the call. |
Access Policy
Read-write
Status
Mandatory
{ansSupTempEntry 6}
Description
SIT Tones—Signals provide additional information (special information tones). Signal frequencies and cadences depend on the system applications. Standard tones are used for incorrectly dialed numbers and changed numbers. All SIT tones are treated the same and each SIT tone type is not distinguished (requires a CPA).
Object Identifier
1.3.6.1.4.1.886.1.9.19.1.6
Data Type
Integer. The valid numerical and string values are shown in the following table. For further information, refer to the Cisco VCO/4K System Administrator's Guide.
| Value | String | Meaning |
|---|---|---|
0 | empty |
|
1 | ok | Ends template processing when the system detects the tone, but it is not reported to the host. |
2 | okrep | Events assigned OKREP tokens are handled like OK tokens, but okrep also generates a report to the host. |
3 | ansbk | Causes the system to answerback over the incoming port. A report is not sent to the host. |
4 | ansrep | Handled like ANSBK tokens, but ansrep also generates a report to the host. |
5 | rep | Reported to the host when detected by the system, but rep does not end template processing. |
6 | error | Specifies that the signaling event should be treated as a supervision error. Causes a rehunt for another outgoing port (if the outgoing resource group is configured for rehunting). |
7 | fail | Specifies that the signaling event indicates a failed call. The outgoing port is removed from the call (no rehunt performed) and the incoming port is left in setup. |
8 | quit | Specifies that the signaling event causes outpulse rule processing to abort. Template processing ends, and the outgoing port returns to the state it was in prior to outpulse rule processing (CP_IDLE, CP_ATT, CP_SETUP or CP_STAB) but is not removed from the call. |
Access Policy
Read-write
Status
Mandatory
{ansSupTempEntry 7}
Description
Ring Cessation—Silence is detected immediately after presence of ringback is established. Event is reported after 3 to 6.5 seconds of silence. Timing starts once ringback is detected (requires a CPA).
Object Identifier
1.3.6.1.4.1.886.1.9.19.1.7
Data Type
Integer. The valid numerical and string values are shown in the following table. For further information, refer to the Cisco VCO/4K System Administrator's Guide.
| Value | String | Meaning |
|---|---|---|
0 | empty |
|
1 | ok | Ends template processing when the system detects the tone, but it is not reported to the host. |
2 | okrep | Events assigned OKREP tokens are handled like OK tokens, but okrep also generates a report to the host. |
3 | ansbk | Causes the system to answerback over the incoming port. A report is not sent to the host. |
4 | ansrep | Handled like ANSBK tokens, but ansrep also generates a report to the host. |
5 | rep | Reported to the host when detected by the system, but rep does not end template processing. |
6 | error | Specifies that the signaling event should be treated as a supervision error. Causes a rehunt for another outgoing port (if the outgoing resource group is configured for rehunting). |
7 | fail | Specifies that the signaling event indicates a failed call. The outgoing port is removed from the call (no rehunt performed) and the incoming port is left in setup. |
8 | quit | Specifies that the signaling event causes outpulse rule processing to abort. Template processing ends, and the outgoing port returns to the state it was in prior to outpulse rule processing (CP_IDLE, CP_ATT, CP_SETUP or CP_STAB) but is not removed from the call. |
Access Policy
Read-write
Status
Mandatory
{ansSupTempEntry 8}
Description
Voice Detection—Signal is within the range of human speech. Signal must be within 200 Hz to 3400 Hz. Event is reported after 0.25 to 0.50 seconds (requires CPA).
Object Identifier
1.3.6.1.4.1.886.1.9.19.1.8
Data Type
Integer. The valid numerical and string values are shown in the following table. For further information, refer to the Cisco VCO/4K System Administrator's Guide.
| Value | String | Meaning |
|---|---|---|
0 | empty |
|
1 | ok | Ends template processing when the system detects the tone, but it is not reported to the host. |
2 | okrep | Events assigned OKREP tokens are handled like OK tokens, but okrep also generates a report to the host. |
3 | ansbk | Causes the system to answerback over the incoming port. A report is not sent to the host. |
4 | ansrep | Handled like ANSBK tokens, but ansrep also generates a report to the host. |
5 | rep | Reported to the host when detected by the system, but rep does not end template processing. |
6 | error | Specifies that the signaling event should be treated as a supervision error. Causes a rehunt for another outgoing port (if the outgoing resource group is configured for rehunting). |
7 | fail | Specifies that the signaling event indicates a failed call. The outgoing port is removed from the call (no rehunt performed) and the incoming port is left in setup. |
8 | quit | Specifies that the signaling event causes outpulse rule processing to abort. Template processing ends, and the outgoing port returns to the state it was in prior to outpulse rule processing (CP_IDLE, CP_ATT, CP_SETUP or CP_STAB) but is not removed from the call. |
Access Policy
Read-write
Status
Mandatory
{ansSupTempEntry 9}
Description
Voice Cessation—Silence is detected immediately after presence of voice is established. Event is reported after 0.5 to 1 second of silence. Timing starts once voice is detected (requires CPA).
Object Identifier
1.3.6.1.4.1.886.1.9.19.1.9
Data Type
Integer. The valid numerical and string values are shown in the following table. For further information, refer to the Cisco VCO/4K System Administrator's Guide.
| Value | String | Meaning |
|---|---|---|
0 | empty |
|
1 | ok | Ends template processing when the system detects the tone, but it is not reported to the host. |
2 | okrep | Events assigned OKREP tokens are handled like OK tokens, but okrep also generates a report to the host. |
3 | ansbk | Causes the system to answerback over the incoming port. A report is not sent to the host. |
4 | ansrep | Handled like ANSBK tokens, but ansrep also generates a report to the host. |
5 | rep | Reported to the host when detected by the system, but rep does not end template processing. |
6 | error | Specifies that the signaling event should be treated as a supervision error. Causes a rehunt for another outgoing port (if the outgoing resource group is configured for rehunting). |
7 | fail | Specifies that the signaling event indicates a failed call. The outgoing port is removed from the call (no rehunt performed) and the incoming port is left in setup. |
8 | quit | Specifies that the signaling event causes outpulse rule processing to abort. Template processing ends, and the outgoing port returns to the state it was in prior to outpulse rule processing (CP_IDLE, CP_ATT, CP_SETUP or CP_STAB) but is not removed from the call. |
Access Policy
Read-write
Status
Mandatory
{ansSupTempEntry 10}
Description
Wink—Signal indicates the distant end is ready to receive outpulsed address digits from the originating central office. Signal is a brief off-hook/on-hook on an unanswered circuit. This signal is detected on T1, E+M and UTC ports only.
Object Identifier
1.3.6.1.4.1.886.1.9.19.1.10
Data Type
Integer. The valid numerical and string values are shown in the following table. For further information, refer to the Cisco VCO/4K System Administrator's Guide.
| Value | String | Meaning |
|---|---|---|
0 | empty |
|
1 | ok | Ends template processing when the system detects the tone, but it is not reported to the host. |
2 | okrep | Events assigned OKREP tokens are handled like OK tokens, but okrep also generates a report to the host. |
3 | ansbk | Causes the system to answerback over the incoming port. A report is not sent to the host. |
4 | ansrep | Handled like ANSBK tokens, but ansrep also generates a report to the host. |
5 | rep | Reported to the host when detected by the system, but rep does not end template processing. |
6 | error | Specifies that the signaling event should be treated as a supervision error. Causes a rehunt for another outgoing port (if the outgoing resource group is configured for rehunting). |
7 | fail | Specifies that the signaling event indicates a failed call. The outgoing port is removed from the call (no rehunt performed) and the incoming port is left in setup. |
8 | quit | Specifies that the signaling event causes outpulse rule processing to abort. Template processing ends, and the outgoing port returns to the state it was in prior to outpulse rule processing (CP_IDLE, CP_ATT, CP_SETUP or CP_STAB) but is not removed from the call. |
Access Policy
Read-write
Status
Mandatory
{ansSupTempEntry 11}
Description
Answer—True answer supervision received from the far end. Answer supervision varies based on link/trunk type. This signal is detected on all line and trunk types except for DID and Loop Start UTC.
Object Identifier
1.3.6.1.4.1.886.1.9.19.1.11
Data Type
Integer. The valid numerical and string values are shown in the following table. For further information, refer to the Cisco VCO/4K System Administrator's Guide.
| Value | String | Meaning |
|---|---|---|
0 | empty |
|
1 | ok | Ends template processing when the system detects the tone, but it is not reported to the host. |
2 | okrep | Events assigned OKREP tokens are handled like OK tokens, but okrep also generates a report to the host. |
3 | ansbk | Causes the system to answerback over the incoming port. A report is not sent to the host. |
4 | ansrep | Handled like ANSBK tokens, but ansrep also generates a report to the host. |
5 | rep | Reported to the host when detected by the system, but rep does not end template processing. |
6 | error | Specifies that the signaling event should be treated as a supervision error. Causes a rehunt for another outgoing port (if the outgoing resource group is configured for rehunting). |
7 | fail | Specifies that the signaling event indicates a failed call. The outgoing port is removed from the call (no rehunt performed) and the incoming port is left in setup. |
8 | quit | Specifies that the signaling event causes outpulse rule processing to abort. Template processing ends, and the outgoing port returns to the state it was in prior to outpulse rule processing (CP_IDLE, CP_ATT, CP_SETUP or CP_STAB) but is not removed from the call. |
Access Policy
Read-write
Status
Mandatory
{ansSupTempEntry 12}
Description
Time—Expiration of a timer on a port waiting for supervision. The timer starts when template processing begins. Timing ends when an event that satisfies the template is detected. The timer's duration is specified in a preceding TIME SUP [xx] outpulse rule token. If you do not specify a token, timing is not performed (supported for all line and trunk types). When an ANSBK or ANSREP token is specified, timeout functions as a grace timer. When an ERROR or FAIL token is specified, timeout indicates a supervision error or a call failure.
Object Identifier
1.3.6.1.4.1.886.1.9.19.1.12
Data Type
Integer. The valid numerical and string values are shown in the following table. For further information, refer to the Cisco VCO/4K System Administrator's Guide.
| Value | String | Meaning |
|---|---|---|
0 | empty |
|
1 | ok | Ends template processing when the system detects the tone, but it is not reported to the host. |
2 | okrep | Events assigned OKREP tokens are handled like OK tokens, but okrep also generates a report to the host. |
3 | ansbk | Causes the system to answerback over the incoming port. A report is not sent to the host. |
4 | ansrep | Handled like ANSBK tokens, but ansrep also generates a report to the host. |
5 | rep | Reported to the host when detected by the system, but rep does not end template processing. |
6 | error | Specifies that the signaling event should be treated as a supervision error. Causes a rehunt for another outgoing port (if the outgoing resource group is configured for rehunting). |
7 | fail | Specifies that the signaling event indicates a failed call. The outgoing port is removed from the call (no rehunt performed) and the incoming port is left in setup. |
8 | quit | Specifies that the signaling event causes outpulse rule processing to abort. Template processing ends, and the outgoing port returns to the state it was in prior to outpulse rule processing (CP_IDLE, CP_ATT, CP_SETUP or CP_STAB) but is not removed from the call. |
Access Policy
Read-write
Status
Mandatory
{ansSupTempEntry 13}
Description
Hook Flash—Indicates a change in the status of the call (depending on application). Signal is a brief on-hook/off-hook. This signal is detected by SLIC, LTC-8, and E+M cards only.
Object Identifier
1.3.6.1.4.1.886.1.9.19.1.13
Data Type
Integer. The valid numerical and string values are shown in the following table. For further information, refer to the Cisco VCO/4K System Administrator's Guide.
| Value | String | Meaning |
|---|---|---|
0 | empty |
|
1 | ok | Ends template processing when the system detects the tone, but it is not reported to the host. |
2 | okrep | Events assigned OKREP tokens are handled like OK tokens, but okrep also generates a report to the host. |
3 | ansbk | Causes the system to answerback over the incoming port. A report is not sent to the host. |
4 | ansrep | Handled like ANSBK tokens, but ansrep also generates a report to the host. |
5 | rep | Reported to the host when detected by the system, but rep does not end template processing. |
6 | error | Specifies that the signaling event should be treated as a supervision error. Causes a rehunt for another outgoing port (if the outgoing resource group is configured for rehunting). |
7 | fail | Specifies that the signaling event indicates a failed call. The outgoing port is removed from the call (no rehunt performed) and the incoming port is left in setup. |
8 | quit | Specifies that the signaling event causes outpulse rule processing to abort. Template processing ends, and the outgoing port returns to the state it was in prior to outpulse rule processing (CP_IDLE, CP_ATT, CP_SETUP or CP_STAB) but is not removed from the call. |
Access Policy
Read-write
Status
Mandatory
{ansSupTempEntry 14}
Description
Pager Cue—Signal is presented by pager terminal equipment requesting the callback number (the callback number is then transmitted to the paged party). Signal is nominally three to four 1400-Hz tone burst at 100 to 125-ms intervals. This feature requires CPA.
Object Identifier
1.3.6.1.4.1.886.1.9.19.1.14
Data Type
Integer. The valid numerical and string values are shown in the following table. For further information, refer to the Cisco VCO/4K System Administrator's Guide.
| Value | String | Meaning |
|---|---|---|
0 | empty |
|
1 | ok | Ends template processing when the system detects the tone, but it is not reported to the host. |
2 | okrep | Events assigned OKREP tokens are handled like OK tokens, but okrep also generates a report to the host. |
3 | ansbk | Causes the system to answerback over the incoming port. A report is not sent to the host. |
4 | ansrep | Handled like ANSBK tokens, but ansrep also generates a report to the host. |
5 | rep | Reported to the host when detected by the system, but rep does not end template processing. |
6 | error | Specifies that the signaling event should be treated as a supervision error. Causes a rehunt for another outgoing port (if the outgoing resource group is configured for rehunting). |
7 | fail | Specifies that the signaling event indicates a failed call. The outgoing port is removed from the call (no rehunt performed) and the incoming port is left in setup. |
8 | quit | Specifies that the signaling event causes outpulse rule processing to abort. Template processing ends, and the outgoing port returns to the state it was in prior to outpulse rule processing (CP_IDLE, CP_ATT, CP_SETUP or CP_STAB) but is not removed from the call. |
Access Policy
Read-write
Status
Mandatory
{ansSupTempEntry 15}
Description
ISUP Tone.
Object Identifier
1.3.6.1.4.1.886.1.9.19.1.15
Data Type
Integer. The valid numerical and string values are shown in the following table. For further information, refer to the Cisco VCO/4K System Administrator's Guide.
| Value | String | Meaning |
|---|---|---|
0 | empty |
|
1 | ok | Ends template processing when the system detects the tone, but it is not reported to the host. |
2 | okrep | Events assigned OKREP tokens are handled like OK tokens, but okrep also generates a report to the host. |
3 | ansbk | Causes the system to answerback over the incoming port. A report is not sent to the host. |
4 | ansrep | Handled like ANSBK tokens, but ansrep also generates a report to the host. |
5 | rep | Reported to the host when detected by the system, but rep does not end template processing. |
6 | error | Specifies that the signaling event should be treated as a supervision error. Causes a rehunt for another outgoing port (if the outgoing resource group is configured for rehunting). |
7 | fail | Specifies that the signaling event indicates a failed call. The outgoing port is removed from the call (no rehunt performed) and the incoming port is left in setup. |
8 | quit | Specifies that the signaling event causes outpulse rule processing to abort. Template processing ends, and the outgoing port returns to the state it was in prior to outpulse rule processing (CP_IDLE, CP_ATT, CP_SETUP or CP_STAB) but is not removed from the call. |
Access Policy
Read-write
Status
Mandatory
{ansSupTempEntry 16}
Description
ISUP cessation.
Object Identifier
1.3.6.1.4.1.886.1.9.19.1.16
Data Type
Integer. The valid numerical and string values are shown in the following table. For further information, refer to the Cisco VCO/4K System Administrator's Guide.
| Value | String | Meaning |
|---|---|---|
0 | empty |
|
1 | ok | Ends template processing when the system detects the tone, but it is not reported to the host. |
2 | okrep | Events assigned OKREP tokens are handled like OK tokens, but okrep also generates a report to the host. |
3 | ansbk | Causes the system to answerback over the incoming port. A report is not sent to the host. |
4 | ansrep | Handled like ANSBK tokens, but ansrep also generates a report to the host. |
5 | rep | Reported to the host when detected by the system, but rep does not end template processing. |
6 | error | Specifies that the signaling event should be treated as a supervision error. Causes a rehunt for another outgoing port (if the outgoing resource group is configured for rehunting). |
7 | fail | Specifies that the signaling event indicates a failed call. The outgoing port is removed from the call (no rehunt performed) and the incoming port is left in setup. |
8 | quit | Specifies that the signaling event causes outpulse rule processing to abort. Template processing ends, and the outgoing port returns to the state it was in prior to outpulse rule processing (CP_IDLE, CP_ATT, CP_SETUP or CP_STAB) but is not removed from the call. |
Access Policy
Read-write
Status
Mandatory
{ansSupTempEntry 17}
Description
Registers the last error that occurred on this ansSupTemp object.
Object Identifier
1.3.6.1.4.1.886.1.9.19.1.17
Data Type
Integer. The possible values and their meaning are shown in the following table:
| Value | String |
|---|---|
2304 | invalidAnsSupvTemplateId |
2305 | templateAlreadyExists |
2306 | invalidAction |
2307 | templateNotEmpty |
2308 | pagerDetectSelectedWithIsupTone |
2309 | hookFlashSelectedWithIsupCessation |
Access Policy
Read only
Status
Mandatory
{ansSupTempEntry 18}
Description
The entity that configured this object and is therefore using the assigned object.
Object Identifier
1.3.6.1.4.1.886.1.9.19.1.18
Data Type
OwnerString
Access Policy
Read-write
Status
Mandatory
{ansSupTempEntry 19}
Description
The status of this entry.
Object Identifier
1.3.6.1.4.1.886.1.9.19.1.19
Data Type
EntryStatus
Access Policy
Read-write
Status
Mandatory
{data 20}
Description
The time, displayed in hundredths of a second, since the answer supervision template was last modified. Helps NMS application developers determine the polling of the agent parameters.
Object Identifier
1.3.6.1.4.1.886.1.9.20
Data Type
TimeTicks
Access Policy
Read only
Status
Mandatory
Routing tables define call routes (resource group hunted and inpulse/outpulse rule executed) based on pattern matching of the dialed digits. You can define and distribute up to 1000 routes among the ten route tables. The routes do not have to be divided equally among the route tables. For example, one table can have 217 routes, another 1056 routes, and so forth. Users can also assign all 1000 possible routes to a single routing table. Refer to the Cisco VCO/4K TeleRouter Reference Guide for further information.
{data 22}
Description
A listing of all the route tables defined in your system.
Object Identifier
1.3.6.1.4.1.886.1.9.22
Data Type
Sequence of RouteGrpEntry
Access Policy
Not accessible
Status
Mandatory
{routeGrpTable 1}
Description
An entry representing a Routing Group table group.
Object Identifier
1.3.6.1.4.1.886.1.9.22.1.
Data Type
RouteGrpEntry
Access Policy
Not accessible
Status
Mandatory
Index
{routeGrpIndex)
Sequence
routeGrpIndex | Integer |
routeGrpTableID | DisplayString |
routeGrpNumberOfRoutes | Integer |
routeGrpTableName | DisplayString |
routeGrpTemplateSize | Integer |
routeGrpTemplateStart | Integer |
routeGrpMinimumDigits | Integer |
routeGrpTest | DisplayString |
routeGrpErrorStatus | Integer |
routeGrpOwnerString | OwnerString |
routeGrpEntryStatus | EntryStatus |
{routeGrpEntry 1}
Description
This object indicates the number of route table groups.
Object Identifier
1.3.6.1.4.1.886.1.9.22.1.1
Data Type
Integer. Length of the display string is from 1 to 10 alphanumeric characters.
Access Policy
Read only
Status
Mandatory
{routeGrpEntry 2}
Description
Indicates the letter of the routeGrp table.
Object Identifier
1.3.6.1.4.1.886.1.9.22.1.2
Data Type
DisplayString. Length of the display string is one character. The possible values for this display string are the characters A to J.
Access Policy
Read only
Status
Mandatory
{routeGrpEntry 3}
Description
Indicates the number of routes defined for the routeGrp table.
Object Identifier
1.3.6.1.4.1.886.1.9.22.1.3
Data Type
Integer. Possible value for this object are from 1 to 1000.
Access Policy
Read only
Status
Mandatory
{routeGrpEntry 4}
Description
Indicates the name of the routeGrp table.
Object Identifier
1.3.6.1.4.1.886.1.9.22.1.4
Data Type
DisplayString. The display string contains from 1 to 12 alphanumeric characters.
Access Policy
Read-write
Status
Mandatory
{routeGrpEntry 5}
Description
Determines the number of consecutive digits used in pattern matching for this routeGrpTable. The size should include any special matching characters.
Object Identifier
1.3.6.1.4.1.886.1.9.22.1.5
Data Type
Integer. The valid values are from 1 to 20.
Access Policy
Read-write
Status
Mandatory
{routeGrpEntry 6}
Description
Determines the starting position of the digits used in pattern matching for this routeGrp table. The value set for this variable must be less than or equal to the difference between the template size and 20, plus 1. For example, if the size is 20 the start must be 1. The following table shows the template and start sizes.
| Template Size | Start Size | Template Size | Start Size |
|---|---|---|---|
20 | 1 | 10 | 11 |
19 | 2 | 9 | 12 |
18 | 3 | 8 | 13 |
17 | 4 | 7 | 14 |
16 | 5 | 6 | 15 |
15 | 6 | 5 | 16 |
14 | 7 | 4 | 17 |
13 | 8 | 3 | 18 |
12 | 9 | 2 | 19 |
11 | 10 | 1 | 20 |
Object Identifier
1.3.6.1.4.1.886.1.9.22.1.6
Data Type
Integer. The possible values are from 0 to 20.
Access Policy
Read-write
Status
Mandatory
{routeGrpEntry 7}
Description
Determines the number of digits the switch must detect when it uses pattern matching in the routeGrp table.
Object Identifier
1.3.6.1.4.1.886.1.9.22.1.7
Data Type
Integer. The valid values are from 0 to 20.
Access Policy
Read-write
Status
Mandatory
{routeGrpEntry 8}
Description
Use the Test command to enter and compare a specific digit string to the entries in the route table to determine if there is a match.
Object Identifier
1.3.6.1.4.1.886.1.9.22.1.8
Data Type
DisplayString. The display string contains from 1 to 20 alphanumeric characters.
Access Policy
Read-write
Status
Mandatory
{routeGrpEntry 9}
Description
This object register the last error that occurred in this routing table.
Object Identifier
1.3.6.1.4.1.886.1.9.22.1.9
Data Type
Integer. The valid values and their meanings are shown in the following table:
| Value | String |
|---|---|
3840 | invalidGroup |
3841 | routeGroupExists |
3842 | invalidIndex |
3843 | noRouteExists |
3844 | invalidRouteNumber |
3845 | invalidPattern |
3846 | templateParametersNotDefined |
3847 | routeEsists |
3848 | invalidSize |
3849 | invalidValue |
3850 | maxRoutesExceeded |
Access Policy
Read only
Status
Mandatory
{routeGrpEntry 10}
Description
The entity that configured this object and is therefore using the assigned routing table.
Object Identifier
1.3.6.1.4.1.886.1.9.22.1.10
Data Type
OwnerString
Access Policy
Read-write
Status
Mandatory
{routeGrpEntry 11}
Description
The status of the routing table. This object also determines whether you can modify the corresponding entries in the exrteTable and routeTable.
Object Identifier
1.3.6.1.4.1.886.1.9.22.1.11
Data Type
EntryStatus
Access Policy
Read-write
Status
Mandatory
{data 23}
Description
The time, displayed in hundredths of a second, since the route table was last modified. Helps NMS application developers determine the polling of the agent parameters.
Object Identifier
1.3.6.1.4.1.886.1.9.23
Data Type
TimeTicks
Access Policy
Read only
Status
Mandatory
Use the exception routing table to configure the error condition routes. There are four exception conditions: Short Collection (S), Empty Collection (E), Unmatched Pattern (U), and Direct Route (D). Refer to the Cisco VCO/4K TeleRouter Reference Guide for further information.
{data 24}
Description
Lists the individual exception routes.
Object Identifier
1.3.6.1.4.1.886.1.9.24
Data Type
Sequence of ExrteEntry
Access Policy
Not accessible
Status
Mandatory
{exrteTable 1}
Description
An entry representing an exception route.
Object Identifier
1.3.6.1.4.1.886.1.9.24.1
Data Type
ExrteEntry
Access Policy
Not accessible
Status
Mandatory
Index
{routeGrpIndex, exrteIndex}
Sequence
exrteIndex | Integer |
exrteLabel | Displaystring |
exrtePrimaryGroup | Integer |
exrtePrimaryRule | Integer |
exrteSecondaryGroup | Integer |
exrteSecondaryRule | Integer |
exrteFinalGroup | Integer |
exrteFinalRule | Integer |
{exrteEntry 1}
Description
Specifies the route number in the routing table.
Object Identifier
1.3.6.1.4.1.886.1.9.24.1.1
Data Type
Integer
Access Policy
Read only
Status
Mandatory
{exrteEntry 2}
Description
Specifies the route label in the routing table.
Object Identifier
1.3.6.1.4.1.886.1.9.24.1.2
Data Type
DisplayString. The display string can contain from 1 to 20 alphanumeric characters.
Access Policy
Read only
Status
Mandatory
{exrteEntry 3}
Description
Indicates the resource group from which the switch should hunt for an outgoing port if the dialed digits match the corresponding pattern. A value of 0 causes the switch to execute an inpulse rule. A value from 1 to 63 causes the switch to execute an outpulse rule.
Object Identifier
1.3.6.1.4.1.886.1.9.24.1.3
Data Type
Integer. The valid values are from 0 to 63.
Access Policy
Read-write
Status
Mandatory
{exrteEntry 4}
Description
Indicates the inpulse/outpulse rule the switch should execute if the dialed digits match the corresponding pattern.
Object Identifier
1.3.6.1.4.1.886.1.9.24.1.4
Data Type
Integer. The valid values are from 0 to 30. If both the Group and Rule are 0, no routing actions are performed.
Access Policy
Read-write
Status
Mandatory
{exrteEntry 5}
Description
Indicates the resource group from which the switch should hunt for an outgoing port if the dialed digits match the corresponding pattern.
Object Identifier
1.3.6.1.4.1.886.1.9.24.1.5
Data Type
Integer. The valid values are from 0 to 63. A value of 0 causes the switch to execute an inpulse rule. A value from 1 to 63 causes the switch to execute an outpulse rule.
Access Policy
Read-write
Status
Mandatory
{exrteEntry 6}
Description
Indicates the inpulse/outpulse rule the switch should execute if the dialed digits match the corresponding pattern.
Object Identifier
1.3.6.1.4.1.886.1.9.24.1.6
Data Type
Integer. The valid values are from 0 to 30. If both the group and rule are 0, no routing actions are performed.
Access Policy
Read-write
Status
Mandatory
{exrteEntry 7}
Description
Indicates the resource group from which the switch should hunt for an outgoing port if the dialed digits match the corresponding pattern.
Object Identifier
1.3.6.1.4.1.886.1.9.24.1.7
Data Type
Integer. The valid values are from 0 to 63. A value of 0 causes the switch to execute an inpulse rule. A value from 1 to 63 causes the switch to execute an outpulse rule.
Access Policy
Read-write
Status
Mandatory
{exrteEntry 8}
Description
Indicates the inpulse/outpulse rule that the switch should execute if the dialed digits match the corresponding pattern. If both the group and rule are 0, then no routing actions are performed.
Object Identifier
1.3.6.1.4.1.886.1.9.24.1.8
Data Type
Integer. The valid values are from 0 to 30.
Access Policy
Read-write
Status
Mandatory
{data 25}
Description
The time, displayed in hundredths of a second, since the route table was last modified. Helps NMS application developers determine the polling of the agent parameters.
Object Identifier
1.3.6.1.4.1.886.1.9.25
Data Type
Integer
Access Policy
Read only
Status
Mandatory
The route table enables the user to specify routes for the TeleRouter. Refer to the Cisco VCO/4K TeleRouter Reference Guide for further information.
{data 26}
Description
Lists the individual routes.
Object Identifier
1.3.6.1.4.1.886.1.9.26
Data Type
Sequence of RouteEntry
Access Policy
Not accessible
Status
Mandatory
{routeTable 1}
Description
An entry that represents a route.
Object Identifier
1.3.6.1.4.1.886.1.9.26.1
Data Type
RouteEntry
Access Policy
Not accessible
Status
Mandatory
Index
{routeGrpIndex, routeIndex}
Sequence
routeIndex | Integer |
routePattern | DisplayString |
routePrimaryGroup | Integer |
routePrimaryRule | Integer |
routeSecondaryGroup | Integer |
routeSecondaryRule | Integer |
routeFinalGroup | Integer |
routeFinalRule | Integer |
routeAdd | DisplayString |
routeDelete | Integer |
{routeEntry 1}
Description
Specifies the number of routes in the routing table.
Object Identifier
1.3.6.1.4.1.886.1.9.26.1.1
Data Type
Integer. The valid number of routes, across the ten possible route groups, is from 1 to 1000.
Access Policy
Read only
Status
Mandatory
{routeEntry 2}
Description
Specifies the route pattern in the routing table.
Object Identifier
1.3.6.1.4.1.886.1.9.26.1.2
Data Type
DisplayString. The display string contains from 1 to 20 alphanumeric characters.
Access Policy
Read only
Status
Mandatory
{routeEntry 3}
Description
Indicates the resource group from which the switch should hunt for an outgoing port if the dialed digits match the corresponding pattern. A value of 0 causes the switch to execute an inpulse rule. A value from 1 to 63 causes the switch to execute an outpulse rule.
Object Identifier
1.3.6.1.4.1.886.1.9.26.1.3
Data Type
Integer. The valid values are from 0 to 63 for 2K mode, or 0 to 224 for 4K mode.
Access Policy
Read-write
Status
Mandatory
{routeEntry 4}
Description
Indicates the inpulse/outpulse rule that the switch should execute if the dialed digits match the corresponding pattern. If both the group and rule are 0, then no routing actions are performed.
Object Identifier
1.3.6.1.4.1.886.1.9.26.1.4
Data Type
Integer. The valid values are from 0 to 30 for 2K mode, or 0 to 255 for 4K mode.
Access Policy
Read-write
Status
Mandatory
{routeEntry 5}
Description
Indicates the resource group from which the switch should hunt for an outgoing port if the dialed digits match the corresponding pattern. A value of 0 causes the switch to execute an inpulse rule. A value from 1 to 63 (or 1 to 224 for 4K mode) causes the switch to execute an outpulse rule.
Object Identifier
1.3.6.1.4.1.886.1.9.26.1.5
Data Type
Integer. The valid values are from 0 to 63 for 2K mode, or 0 to 224 for 4K mode.
Access Policy
Read-write
Status
Mandatory
{routeEntry 6}
Description
Indicates the inpulse/outpulse rule that the switch should execute if the dialed digits match the corresponding pattern. If both the Group and Rule are 0, then no routing actions are performed.
Object Identifier
1.3.6.1.4.1.886.1.9.26.1.6
Data Type
Integer. The valid values are from 0 to 30 for 2K mode, or 0 to 225 for 4K mode.
Access Policy
Read-write
Status
Mandatory
{routeEntry 7}
Description
Indicates the resource group from which the switch should hunt for an outgoing port if the dialed digits match the corresponding pattern. A value of 0 causes the switch to execute an inpulse rule. A value from 1 to 63 (1 to 224 for 4K mode) causes the switch to execute an outpulse rule.
Object Identifier
1.3.6.1.4.1.886.1.9.26.1.7
Data Type
Integer. The valid values are from 0 to 63 for 2K mode, or 0 to 224 for 4K mode.
Access Policy
Read-write
Status
Mandatory
{routeEntry 8}
Description
Indicates the inpulse/outpulse rule that the switch should execute if the dialed digits match the corresponding pattern. If both the group and rule are 0, then no routing actions are performed.
Object Identifier
1.3.6.1.4.1.886.1.9.26.1.8
Data Type
Integer. The valid values are from 0 to 30 for 2K mode, or 0 to 225 for 4K mode.
Access Policy
Read-write
Status
Mandatory
{routeEntry 9}
Description
Adds a route to the route table. You must specify the pattern that you want to match. When adding routes, the routeIndex component of the index must be 1 higher than the number of routes already in the table.
Object Identifier
1.3.6.1.4.1.886.1.9.26.1.9
Data Type
DisplayString. The display string contains from 1 to 20 alphanumeric characters.
Access Policy
Read-write
Status
Mandatory
{routeEntry 10}
Description
Deletes a specific route from the routing table. The route specified must equal the routeIndex component of the index. Also, you can only delete the last route in the table.
Object Identifier
1.3.6.1.4.1.886.1.9.26.1.10
Data Type
Integer. The valid number of routes, across the ten possible route groups, is from 1 to 1000.
Access Policy
Read-write
Status
Mandatory
{data 27}
Description
The time, displayed in hundredths of a second, since the beginning of the time that the route table was last modified. Helps NMS application developers determine the polling of the agent parameters.
Object Identifier
1.3.6.1.4.1.886.1.9.27
Data Type
Integer
Access Policy
Read only
Status
Mandatory
Posted: Sat Sep 28 11:09:28 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.