CISCO-WAN-VISM-TONE-PLAN-MIB Table View

This table contains configuration information about different 
Tone Plans. 
          
The first 32 entries of the table are 'provisionable' 
followed by an implementation specific number 
of 'builtIn' entries.

vismTonePlanEntry row .1.3.6.1.4.1.351.150.24.1.1.2.1.1

An entry in the vismTonePlanTable. Each entry consists of
configuration information for a specific Tone Plan.

The vismTonePlanTable is of fixed size with a predefined
number of entries, where each entry co…

Indexes

tonePlanIndex

Column	Syntax	OID
tonePlanIndex Serves as index to this table. However, the maximum entry allowed is specify in tonePlanCurrentSize.	Integer32 Constraints: range: 1-1000	.1.3.6.1.4.1.351.150.24.1.1.2.1.1.1
tonePlanEntryStatus This attribute specifies the status of this entry as to whether this entry (row) contains usable Tone Plan configuration information (object is set to 'configured'), or if it is empty (object is set to 'unused'), or i…	Enumerationr/w Enumerated Values: 1 unused 2 configured 3 reloading 4 lostFile	.1.3.6.1.4.1.351.150.24.1.1.2.1.1.2
tonePlanProvisionFlag This attribute specifies whether this entry contains predefined Tone Plan configuration information from internal firmware code (object is set to 'builtIn') or if it has been configured with tone plan configuration info…	Enumeration Enumerated Values: 1 builtIn 2 provisionable	.1.3.6.1.4.1.351.150.24.1.1.2.1.1.3
tonePlanRegionName The region (or country) for which this tone plan is defined. Any other entry in this table may have an identical name, but the combination of tonePlanRegionName and tonePlanVersionNumber must be unique. T…	OctetStringr/w Constraints: range: 1-64	.1.3.6.1.4.1.351.150.24.1.1.2.1.1.4
tonePlanVersionNumber This attribute specifies this entry's version number for a tone plan for a region. Multiple tone plans may be defined for each region, but each of these tone plans must have a unique tonePlanRegionName and tonePlanVers…	Integer32r/w Constraints: range: 0-65535	.1.3.6.1.4.1.351.150.24.1.1.2.1.1.5
tonePlanFileName This is the name of a valid file stored on the TFTP server which contains the tone definitions. A missing or invalid file name will cause a failure in the configuration of this entry. If this entry point…	OctetStringr/w Constraints: range: 1-32	.1.3.6.1.4.1.351.150.24.1.1.2.1.1.6

This table contains the list of user configurable dual
frequency tones that can be detected on VISM. The call
agent can request the VISM to detect any of the tones 
defined in this table.
          
Entries to this table can only be added or deleted,
not modified. Individual parameters within a row 
cannot be changed without deleting and re-adding
the entry.

vismConfigToneDetectEntry row .1.3.6.1.4.1.351.150.24.1.1.3.1.1

This is the primary entry in the vismConfigToneDetectTable.
Each entry references a User configurable dual
frequency tones that can be detected on VISM.

Indexes

vismConfigToneDetectNum

Column	Syntax	OID
vismConfigToneDetectNum This is the index of this table. Currently only tones 1 to 10 are used and call agent can request up to ten tones to be detected on different endpoints at any point in time.	Integer32 Constraints: range: 1-10	.1.3.6.1.4.1.351.150.24.1.1.3.1.1.1
vismEventCode This is the secondary index of this table. Call agent can request supervision tone detection indexed by this field. The values of event code are mapped from the subscriber line event codes defined in RFC2833. Currently…	Integer32r/w Constraints: range: 0-255	.1.3.6.1.4.1.351.150.24.1.1.3.1.1.2
vismConfigToneDetectRowStatus Controls the creation and deletion of a Config Tone. An entry may be created using the 'createAndGo' option. When the row is successfully created, the vismConfigToneDetectRowStatus would be set to 'activ…	SNMPv2-TCRowStatusr/w Type Values: 1 active 2 notInService 3 notReady 4 createAndGo 5 createAndWait 6 destroy Description: The 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 …	.1.3.6.1.4.1.351.150.24.1.1.3.1.1.3
vismFreqMaxDeviation Specifies the maximum frequency deviation to be used by VISM when detecting a specific dual frequency tone. Please refer the VISM configuration guide for standard values to be used for this field.	HzInteger32r/w Constraints: range: 10-125	.1.3.6.1.4.1.351.150.24.1.1.3.1.1.4
vismFreqMaxPower Specifies the maximum frequency power to be used by VISM when detecting a specific dual frequency tone. Please refer the VISM configuration guide for standard values to be used for this field.	dBInteger32r/w Constraints: range: 0-30	.1.3.6.1.4.1.351.150.24.1.1.3.1.1.5
vismFreqMinPower Specifies the minimum frequency power to be used by VISM when detecting a specific dual frequency tone. Please refer the VISM configuration guide for standard values to be used for this field.	dBInteger32r/w Constraints: range: 10-35	.1.3.6.1.4.1.351.150.24.1.1.3.1.1.6
vismFreqPowerTwist Specifies the maximum frequency power twist permitted between the two frequencies used by VISM when detecting a dual frequency tone. Please refer the VISM configuration guide for standard values to be u…	dBInteger32r/w Constraints: range: 0-15	.1.3.6.1.4.1.351.150.24.1.1.3.1.1.7
vismFreqMaxDelay Specifies the maximum frequency delay to be used by VISM when detecting a dual frequency tone. Please refer the VISM configuration guide for standard values to be used for this field. It i…	millisecondsInteger32r/w Constraints: range: 0-100	.1.3.6.1.4.1.351.150.24.1.1.3.1.1.8
vismMinOnCadence Specifies the minimum tone cycle ON time that is necessary for the VISM to detect the dual frequency tone. The vismMinOnCadence has to be less than vismFreqOnCadence value. Please refer the VISM configur…	millisecondsInteger32r/w Constraints: range: 3-100	.1.3.6.1.4.1.351.150.24.1.1.3.1.1.9
vismMaxOffCadence Specifies the maximum tone cycle OFF time that is necessary for the VISM to detect the dual frequency tone. The vismMaxOffCadence should be greater than vismFreqOffCadence value. Please refer the VISM …	Integer32r/w Constraints: range: 5-5000	.1.3.6.1.4.1.351.150.24.1.1.3.1.1.10
vismFreqNumOfCadenceMatch Specifies the number of pairs of the dual frequency that needs to be detected. Currently ten pairs of frequency can be detected by the DSP.	Integer32r/w Constraints: range: 0-6	.1.3.6.1.4.1.351.150.24.1.1.3.1.1.11
vismFrequency1 Specifies the 1st frequency component of the dual frequency to be detected by the VISM.	HzInteger32r/w Constraints: range: 280-3800	.1.3.6.1.4.1.351.150.24.1.1.3.1.1.12
vismFrequency2 Specifies the 2nd frequency component of the dual frequency to be detected by the DSP. A value of 0 means this is a single frequency. The range of 1 to 279 is not a valid range in the DSP.	HzInteger32r/w Constraints: range: 0-3800	.1.3.6.1.4.1.351.150.24.1.1.3.1.1.13
vismFreqOnCadence The On time in each cycle of the dual frequency to be detected by the DSP. The vismFreqOnCadence has to be less than vismMinOnCadence value. It is measured in units of 10ms.	millisecondsInteger32r/w Constraints: range: 3-5000	.1.3.6.1.4.1.351.150.24.1.1.3.1.1.14
vismFreqOffCadence The Off time in each cycle of the dual frequency to be detected by the DSP. The vismFreqOffCadence should be lesser than the vismMaxOffCadence value. It is measured in units of 10ms.	millisecondsInteger32r/w Constraints: range: 5-5000	.1.3.6.1.4.1.351.150.24.1.1.3.1.1.15