PKTC-IETF-SIG-MIB :: pktcSigDevToneSteady

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › PKTC-IETF-SIG-MIB › pktcSigDevToneSteady

pktcSigDevToneSteady

Module: PKTC-IETF-SIG-MIB

OID (symbolic): PKTC-IETF-SIG-MIB::pktcSigDevToneSteady

OID (numeric): 1.3.6.1.2.1.169.1.1.32.1.5

Node type: OBJECT-TYPE

Type: TruthValue

Access: read-only

Description: This MIB object represents the steady tone status. A value of 'true(1)' indicates that the steady tone is applied, and a value of 'false(2)' indicates otherwise. Devices must play out the on-off cadence sequence for the number of times indicated by the MIB object 'pktcSigDevToneWholeToneRepeatCount' prior to applying the last tone steadily, indefinitely. If the MIB table 'pktcSigDevToneTable' contains multiple rows with this Object set to a value of 'true(1)', the steady tone is applied to the last repeating frequency group of the tone.

Setting this MIB object may result in a tone duration that is longer or shorter than the overall signal duration specified by the time out (TO) MIB object for a particular signal. If the repeat count results in a longer tone duration than the signal duration specified by the TO, the tone duration defined by the TO object for a particular signal always represents the overall signal duration for a tone. In this case, the tone duration repeat count will not be fully exercised, and the desired tone duration will be truncated per the TO setting. If the repeat count results in a shorter tone duration than the signal duration specified by the TO, the tone duration defined by the repeat count takes precedence over the TO and will end the signal event. In this case, the TO represents a time not to be exceeded for the signal.

It is recommended to ensure proper telephony signaling that The TO duration setting should always be longer than the desired repeat count-time duration, plus the desired maximum steady tone period.

What is pktcSigDevToneSteady?

Read-only flag indicating whether, after its repeat cycles finish, this tone is then held steady indefinitely (true) rather than stopping (false); when multiple rows are steady, the last repeating frequency group in the sequence is the one held.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.169.1.1.32.1.5
snmpwalk -v2c -c public <target> PKTC-IETF-SIG-MIB::pktcSigDevToneSteady

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.169.1.1.32.1.5.1
snmpget -v2c -c public <target> PKTC-IETF-SIG-MIB::pktcSigDevToneSteady.1

Start monitoring PacketCable/IPCablecom-compliant cable-telephony equipment (Network Call Signaling) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the PKTC-IETF-SIG-MIB::pktcSigDevToneSteady OID value, configure state conditions and alerts, and monitor any PacketCable/IPCablecom-compliant cable-telephony equipment (Network Call Signaling) from a single console.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.169pktcIetfSigMibPKTC-IETF-SIG-MIB
1.3.6.1.2.1.169.1pktcSigMibObjectsPKTC-IETF-SIG-MIB
1.3.6.1.2.1.169.1.1pktcSigDevObjectsPKTC-IETF-SIG-MIB
1.3.6.1.2.1.169.1.1.32pktcSigDevToneTablePKTC-IETF-SIG-MIB
1.3.6.1.2.1.169.1.1.32.1pktcSigDevToneEntryPKTC-IETF-SIG-MIB
1.3.6.1.2.1.169.1.1.32.1.5pktcSigDevToneSteadyPKTC-IETF-SIG-MIB