| tonePlanCurrentSize |
.1.3.6.1.4.1.351.150.24.1.1.1.1 |
|
This object specifies the number of entries
in vismTonePlanTable.
|
| vismTonePlanEntry |
.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 contains usable
information or not depending upon the value of the
tonePlanEntryStatus MIB object.
The configuration is retained after VISM card reboots.
tonePlanRegionName, tonePlanVersionNumber, and
tonePlanFileName can be modified only if the
tonePlanProvisionFlag is 'provisionable' and
tonePlanEntryStatus is 'configured' when loading a new
tone plan (see MIB object tonePlanEntryStatus below). After
the new tone plan is loaded, these three MIB objects may
not be modified. To change these objects, the entry in
this table must be deleted, and all objects re-added
with new corrected values.
The rest of the entries of this table, (the 'builtIn' ones)
cannot be modified after the table is build at reload time.
|
| vismConfigToneDetectEntry |
.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.
|
| seqToneNumOfFrequencies |
.1.3.6.1.4.1.351.150.24.1.1.4.1 |
|
The number of single frequencies which have to be detected
by the sequential tone detector command on VISM. The
frequencies should specified below (seqToneFrequency1 to
seqToneFrequency10). This number should correspond to the
non-zero frequency values seqToneFrequency1 to
seqToneFrequency10.
|
| seqToneEventID |
.1.3.6.1.4.1.351.150.24.1.1.4.2 |
|
The eventID corresponding to the sequential frequency.
Currently only supports Event 74 (SIT tone)
|
| seqToneDurationOfEachTone |
.1.3.6.1.4.1.351.150.24.1.1.4.3 |
|
Nominal tone duration of each single tone in counts of 10ms
used with sequential tone detector on VISM DSP.
|
| seqToneGapBetweenEachTone |
.1.3.6.1.4.1.351.150.24.1.1.4.4 |
|
Nominal silence gap duration between each tone in 10ms
used with sequential tone detector on VISM DSP.
|
| seqToneDurationDeviation |
.1.3.6.1.4.1.351.150.24.1.1.4.5 |
|
Tone duration deviation allowed in 10ms
used with sequential tone detector on VISM DSP.
|
| seqToneMaximumGapDuration |
.1.3.6.1.4.1.351.150.24.1.1.4.6 |
|
Maximum tone duration allowed in 10ms
used with sequential tone detector on VISM DSP.
|
| seqToneGapDurationDeviation |
.1.3.6.1.4.1.351.150.24.1.1.4.7 |
|
Tone duration deviation allowed in 10ms
used with sequential tone detector on VISM DSP.
|
| seqToneFreqDeviation |
.1.3.6.1.4.1.351.150.24.1.1.4.8 |
|
Frequency deviation allowed (1 - 1000 Hz)
used with sequential tone detector on VISM DSP.
|
| seqTonePowerLevelCeiling |
.1.3.6.1.4.1.351.150.24.1.1.4.9 |
|
Maximum ceiling power level of the sequential
frequency tone (absolute value in dBm)
used with sequential tone detector on VISM DSP.
Range from 0 to 40 (0 to -40dB)
|
| seqTonePowerLevelFloor |
.1.3.6.1.4.1.351.150.24.1.1.4.10 |
|
Lowest (floor) power level of the sequential
frequency tone (absolute value in dBm)
used with sequential tone detector on VISM DSP.
Range from 0 to 40 (0 to -40dB)
|
| seqToneFrequency1 |
.1.3.6.1.4.1.351.150.24.1.1.4.11 |
|
1st frequency in the SequentialTone to detect (280 - 3800),
used with sequential tone detector on VISM DSP.
|
| seqToneFrequency2 |
.1.3.6.1.4.1.351.150.24.1.1.4.12 |
|
2nd frequency in the SequentialTone to detect (280 - 3800),
used with sequential tone detector on VISM DSP.
|
| seqToneFrequency3 |
.1.3.6.1.4.1.351.150.24.1.1.4.13 |
|
3rd frequency in the SequentialTone to detect (280 - 3800),
used with sequential tone detector on VISM DSP.
|
| seqToneFrequency4 |
.1.3.6.1.4.1.351.150.24.1.1.4.14 |
|
4th frequency in the SequentialTone to detect (280 - 3800),
used with sequential tone detector on VISM DSP.
|
| seqToneFrequency5 |
.1.3.6.1.4.1.351.150.24.1.1.4.15 |
|
5th frequency in the SequentialTone to detect (280 - 3800),
used with sequential tone detector on VISM DSP.
|
| seqToneFrequency6 |
.1.3.6.1.4.1.351.150.24.1.1.4.16 |
|
6th frequency in the SequentialTone to detect (280 - 3800),
used with sequential tone detector on VISM DSP.
|
| seqToneFrequency7 |
.1.3.6.1.4.1.351.150.24.1.1.4.17 |
|
7th frequency in the SequentialTone to detect (280 - 3800),
used with sequential tone detector on VISM DSP.
|
| seqToneFrequency8 |
.1.3.6.1.4.1.351.150.24.1.1.4.18 |
|
8th frequency in the SequentialTone to detect (280 - 3800),
used with sequential tone detector on VISM DSP.
|
| seqToneFrequency9 |
.1.3.6.1.4.1.351.150.24.1.1.4.19 |
|
9th frequency in the SequentialTone to detect (280 - 3800),
used with sequential tone detector on VISM DSP.
|
| seqToneFrequency10 |
.1.3.6.1.4.1.351.150.24.1.1.4.20 |
|
10th frequency in the SequentialTone to detect (280 - 3800),
used with sequential tone detector on VISM DSP.
|
| tonePlanIndex |
.1.3.6.1.4.1.351.150.24.1.1.2.1.1.1 |
|
Serves as index to this table. However, the maximum
entry allowed is specify in tonePlanCurrentSize.
|
| tonePlanEntryStatus |
.1.3.6.1.4.1.351.150.24.1.1.2.1.1.2 |
|
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 if is
temporarily (object is set to 'reloading') or
permanently (object is set to 'lostFile') unusable.
This tone plan information for this row can be used
by a DS-1 line only if this object has a value of
'configured (2)'.
To add a configured entry in the vismTonePlanTable
table, there must be an existing empty row with its
entry status set to 'unused(1)'.
Then before this empty row in the vismTonePlanTable
table can be changed to 'configured', it must, in
one single operation, be given all the usable
values necessary to be stored in the
tonePlanRegionName, tonePlanVersionNumber and
tonePlanFileName MIB objects for this row. In addition,
those values for the tonePlanRegionName and
tonePlanVersionNumber MIB objects pair must be
unique with respect to every other row of the
vismTonePlanTable. Then, as this existing empty row
is set with all three valid entries for the
tonePlanRegionName, tonePlanVersionNumber,
and tonePlanFileName MIB objects, the Entry Status
MIB object for this row will be finally, internally,
set to 'configured(2)'. This final 'configured' status
is the direct result of correctly setting these three
MIB objects with valid data.
In no case will an external manager be able to directly
set this MIB object to 'configured(2)' by a SNMP set
command, for such a single stand alone command will
be rejected.
Once a table entry is set to 'configured(2)' with
valid tonePlanRegionName, tonePlanVersionNumber, and
tonePlanFileName MIB objects for this row, then these
MIB objects may not be modified by any subsequent
SNMP set command. In the case where a row needs to
have these objects changed, this entry must be cleared
from the table (paragraph below) and a new entry added
by the add process above.
Once an entry exists in the vismTonePlanTable table it
may be cleared and set to unused by setting this MIB
object to 'unused(1)'. But before the entry status of
any entry in this table can be set to 'unused(1)',
there is a check to make sure there is no
vismDsx1TonePlanRegion MIB object and
vismDsx1TonePlanVersion MIB object pair in the
dsx1VismCnfGrpTable MIB table that may point to or
refer to this table entry (row) with its unique
tonePlanRegionName and tonePlanVersionNumber.
Once the entry status of an entry in this table is set
to 'unused(1)', all the other MIB objects for this
table row are set to defaults or to NULL.
Once an entry is 'configured', if a subsequent card
reset occurs the VISM card will attempt to restore
all of the configuration information by doing the
normal download of the latest MIB database, set all
'configured (2)' MIB objects to 'reloading (3)', and
then do an automatic background process to retrieve
all of the tone plan files from the server since they
were not downloaded by the PXM. If this retrieval of
the tone plan files succeeds then this MIB object
will be set back to 'configured (2)'. If this file
retrieval does not succeed, then this MIB object will
be set to 'lostFile (4)'. In no way will an external
manager be able to directly set this MIB object
to 'reloading (3)' or 'lostFile (4)' by a SNMP set
command.
|
| tonePlanProvisionFlag |
.1.3.6.1.4.1.351.150.24.1.1.2.1.1.3 |
|
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
information that has been downloaded from the PXM
(object is set to unused).
Only entries that are provisionable may have their
tonePlanEntryStatus MIB object marked as unused in
this table. BuiltIn entries may not be marked as unused.
|
| tonePlanRegionName |
.1.3.6.1.4.1.351.150.24.1.1.2.1.1.4 |
|
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.
This field may be from 1 to 64 alphabetic, numeric, or
underscore characters long, with no embedded spaces.
A NULL entry will consist of a single space character
of length one.
|
| tonePlanVersionNumber |
.1.3.6.1.4.1.351.150.24.1.1.2.1.1.5 |
|
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
tonePlanVersionNumber. When a new tone plan is added
for a region, it should be added with a newer(larger)
version number.
Allowed values are in range (1..65535) but a value of
zero being set in this object means that this object
is a NULL entry.
|
| tonePlanFileName |
.1.3.6.1.4.1.351.150.24.1.1.2.1.1.6 |
|
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 points to a build-in tone plan predefined
in firmware, then this name will be: 'BUILTIN'.
Provisionable file names are not allowed to have the
string 'BUILTIN' as their names.
This field may be from 1 to 32 alphabetic, numeric, or
underscore characters (no embedded spaces) long for a
valid entry. A NULL entry will consist of a single
space character of length one.
|
| vismConfigToneDetectNum |
.1.3.6.1.4.1.351.150.24.1.1.3.1.1.1 |
|
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.
|
| vismEventCode |
.1.3.6.1.4.1.351.150.24.1.1.3.1.1.2 |
|
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 VISM supports
detection of only a handful of supervision tones like
Ringing, Busy, Dial-Tone and SIT tones.
|
| vismConfigToneDetectRowStatus |
.1.3.6.1.4.1.351.150.24.1.1.3.1.1.3 |
|
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 'active'
by the agent. An entry may be deleted by setting the
vismConfigToneDetectRowStatus to 'destroy'.
|
| vismFreqMaxDeviation |
.1.3.6.1.4.1.351.150.24.1.1.3.1.1.4 |
|
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.
|
| vismFreqMaxPower |
.1.3.6.1.4.1.351.150.24.1.1.3.1.1.5 |
|
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.
|
| vismFreqMinPower |
.1.3.6.1.4.1.351.150.24.1.1.3.1.1.6 |
|
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.
|
| vismFreqPowerTwist |
.1.3.6.1.4.1.351.150.24.1.1.3.1.1.7 |
|
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 used for this field.
|
| vismFreqMaxDelay |
.1.3.6.1.4.1.351.150.24.1.1.3.1.1.8 |
|
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 is measured in units of 10ms.
|
| vismMinOnCadence |
.1.3.6.1.4.1.351.150.24.1.1.3.1.1.9 |
|
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 configuration guide for standard
values to be used for this field.
|
| vismMaxOffCadence |
.1.3.6.1.4.1.351.150.24.1.1.3.1.1.10 |
|
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 configuration guide for standard
values to be used for this field.
|
| vismFreqNumOfCadenceMatch |
.1.3.6.1.4.1.351.150.24.1.1.3.1.1.11 |
|
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.
|
| vismFrequency1 |
.1.3.6.1.4.1.351.150.24.1.1.3.1.1.12 |
|
Specifies the 1st frequency component of the dual
frequency to be detected by the VISM.
|
| vismFrequency2 |
.1.3.6.1.4.1.351.150.24.1.1.3.1.1.13 |
|
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.
|
| vismFreqOnCadence |
.1.3.6.1.4.1.351.150.24.1.1.3.1.1.14 |
|
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.
|
| vismFreqOffCadence |
.1.3.6.1.4.1.351.150.24.1.1.3.1.1.15 |
|
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.
|
