PKTC-IETF-SIG-MIB

Unsigned32 (1..255)

The index value that enumerates a particular codec combination in the pktcSigDevCodecTable.

PktcCodecType1 = other2 = unknown3 = g7294 = reserved5 = g729E6 = pcmu7 = g726at328 = g7289 = pcma10 = g726at1611 = g726at2412 = g726at4013 = ilbc14 = bv16This TEXTUAL-CONVENTION defines various types of codecs that MAY be supported. The description for each enumeration is listed below: Enumeration Description other a defined codec not in the enumeration unknown a codec not defined by the PacketCable Codec Specification g729 ITU-T Recommendation G.729 reserved for future use g729E ITU-T Recommendation G.729E pcmu Pulse Code Modulation u-law (PCMU) g726at32 ITU-T Recommendation G.726-32 (32 kbit/s) g728 ITU-T Recommendation G.728 pcma Pulse Code Modulation a-law (PCMA) g726at16 ITU-T Recommendation G.726-16 (16 kbit/s) g726at24 ITU-T Recommendation G.726-24 (24 kbit/s) g726at40 ITU-T Recommendation G.726-40 (40 kbit/s) ilbc IETF Internet low-bit rate codec bv16 Broadcom BroadVoice16 The list of codecs is consistent with the IETF Real-Time Transport Protocol (RTP) Profile registry and the RTP Map Parameters Table in PacketCable Audio/Video Codecs Specification [PKT-SP-CODEC]. The literal codec name for each codec is listed below: Codec Literal Codec Name g729 G729 g729E G729E pcmu PCMU g726at32 G726-32 g728 G728 pcma PCMA g726at16 G726-16 g726at24 G726-24 g726at40 G726-40 ilbc iLBC bv16 BV16 The literal codec name is the second column of the table with codec RTP Map Parameters. The Literal Codec Name Column contains the codec name used in the local connection options (LCO) of the NCS messages create connection (CRCX)/modify connection (MDCX) and is also used to identify the codec in the Call Management System (CMS) Provisioning Specification. The RTP Map Parameter column of the Table contains the string used in the media attribute line (a=) of the session description protocol (SDP) parameters in NCS messages. · Integer32

A codec type supported by this MTA.

Unsigned32 (1..255)

The maximum number of simultaneous sessions of a particular codec that the MTA can support.

Unsigned32 (1..255)

The index value that uniquely identifies an entry in the pktcSigCapabilityTable.

PktcSigType1 = other2 = ncsThis object lists the various types of signaling that may be supported: other(1) - set when signaling other than NCS is used ncs(2) - Network Call Signaling is a derivation of MGCP (Media Gateway Control Protocol) defined for IPCablecom/PacketCable MTAs. · Integer32

This object identifies the type of signaling used. This value has to be associated with a single signaling version.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

Provides the version of the signaling type - reference pktcSigCapabilityType. Examples would be 1.0 or 2.33 etc.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

The vendor extension allows vendors to provide a list of additional capabilities. The syntax for this MIB object in ABNF ([RFC5234]) is specified to be zero or more occurrences of vendor extensions, as follows: pktcSigCapabilityVendorExt = *(vendor-extension) vendor-extension = (ext symbol alphanum) DQUOTE ; DQUOTE ext = DQUOTE %x58 DQUOTE symbol = (DQUOTE %x2D DQUOTE)/(DQUOTE %x2D DQUOTE) alphanum = 1*6(ALPHA/DIGIT)

INTEGER1 = initialRing2 = pulseLoopClose3 = pulseLoopOpen4 = enableMeterPulse5 = meterPulseBurst6 = pulseNoBattery7 = pulseNormalPolarity8 = pulseReducedBattery9 = pulseReversePolarity · Integer32

There are nine types of international pulse signals. These signals are defined as follows: initial ring pulse loop close pulse loop open enable meter pulse meter pulse burst pulse no battery pulse normal polarity pulse reduced battery pulse reverse polarity ⓘ

INTEGER1 = twentyfive2 = twelvethousand3 = sixteenthousand · Integer32

This object is only applicable to the initialRing, enableMeterPulse, and meterPulseBurst signal types. This object identifies the frequency of the generated signal. The following table defines the default values for this object depending on signal type: pktcSigPulseSignalType Default initialRing 25 enableMeterPulse 16000 meterPulseBurst 16000 The value of twentyfive MUST only be used for the initialRing signal type. The values of twelvethousand and sixteenthousand MUST only be used for enableMeterPulse and meterPulseBurst signal types. An attempt to set this object while the value of pktcSigPulseSignalType is not initialRing, enableMeterPulse, or meterPulseBurst will result in an 'inconsistentValue' error. ⓘ

TenthdBmThis TEXTUAL-CONVENTION represents power levels that are normally expressed in dBm. Units are in tenths of a dBm; for example, -13.5 dBm will be represented as -135. (-350..0) · Integer32 · hint d-1 · 1/10 of a dBm

This object is only applicable to the enableMeterPulse and meterPulseBurst signal types. This is the decibel level for each frequency at which tones could be generated at the a and b terminals (TE connection point). An attempt to set this object while the value of pktcSigPulseSignalType is not enableMeterPulse or meterPulseBurst will result in an 'inconsistentValue' error. ⓘ

Unsigned32 (0..5000) · Milliseconds

This object specifies the pulse duration for each signal type. In addition, the MTA must accept the values in the incremental steps specific for each signal type. The following table defines the default values and the incremental steps for this object depending on the signal type: pktcSigPulseSignaltype Default (ms) Increment (ms) initialRing 200 50 pulseLoopClose 200 10 pulseLoopOpen 200 10 enableMeterPulse 150 10 meterPulseBurst 150 10 pulseNoBattery 200 10 pulseNormalPolarity 200 10 pulseReducedBattery 200 10 pulseReversePolarity 200 10 An attempt to set this object to a value that does not fall on one of the increment boundaries, or on the wrong increment boundary for the specific signal type, will result in an 'inconsistentValue' error. ⓘ

Unsigned32 (0..5000) · Milliseconds

This object specifies the repeat interval, or the period, for each signal type. In addition, the MTA must accept the values in the incremental steps specific for each signal type. The following table defines the default values and the incremental steps for this object, depending on the signal type: pktcSigPulseSignaltype Default (ms) Increment (ms) initialRing 200 50 pulseLoopClose 1000 10 pulseLoopOpen 1000 10 enableMeterPulse 1000 10 meterPulseBurst 1000 10 pulseNoBattery 1000 10 pulseNormalPolarity 1000 10 pulseReducedBattery 1000 10 pulseReversePolarity 1000 10 An attempt to set this object to a value that does not fall on one of the increment boundaries, or on the wrong increment boundary for the specific signal type, will result in an 'inconsistentValue' error. ⓘ

Unsigned32 (1..50)

This object specifies how many times to repeat a pulse. This object is not used by the enableMeterPulse signal type, and in that case, the value is irrelevant. The following table defines the default values and the valid ranges for this object, depending on the signal type: pktcSigPulseSignaltype Default Range initialRing 1 1-5 pulseLoopClose 1 1-50 pulseLoopOpen 1 1-50 enableMeterPulse (any value)(but not used) meterPulseBurst 1 1-50 pulseNoBattery 1 1-50 pulseNormalPolarity 1 1-50 pulseReducedBattery 1 1-50 pulseReversePolarity 1 1-50 An attempt to set this object to a value that does not fall within the range for the specific signal type will result in an 'inconsistentValue' error.

Unsigned32 (0..127)

A unique value ranging from 0 to 127 that corresponds to the value sent by the LE based on country-specific cadences, one row per cadence cycle. In any given system implementation for a particular country, it is anticipated that a small number of ring cadences will be in use. Thus, this table most likely will not be populated to its full size.

PktcRingCadenceThis object provides an encoding scheme for ring cadences, including repeatability characteristics. All fields in this object MUST be encoded in network-byte order. The first three higher-order octets are reserved. The octets that follow are used to encode a 'bit-string', with each bit corresponding to 50 milliseconds. A bit value of '1' indicates the presence of a ring-tone, and a bit value of '0' indicates the absence of a ring-tone, for that duration (50 ms) (Note: A minimum number of octets required to encode the bit-string MUST be used). The first two of the reserved octets MUST indicate the length of the encoded cadence (in bits) and MUST range between 1 and 264. (Note: The length in bits MUST also be consistent with the number of octets that encode the cadence). The MTA MUST ignore any unused bits in the last octet, but MUST reflect the value as provided on subsequent SNMP GETs. The third of the reserved octets indicates 'repeatability' and MUST be either 0x80 or 0x00 -- the former value indicating 'non-repeatability', and the latter indicating 'repeatability'. The MTA MUST reject attempts to set a value that violates any of the above requirements. SIZE (4..36) · OCTET STRING

This is the Ring Cadence.

INTEGER1 = busy2 = confirmation3 = dial4 = messageWaiting5 = offHookWarning6 = ringBack7 = reOrder8 = stutterdial9 = callWaiting110 = callWaiting211 = callWaiting312 = callWaiting413 = alertingSignal14 = specialDial15 = specialInfo16 = release17 = congestion18 = userDefined119 = userDefined220 = userDefined321 = userDefined4 · Integer32

A unique value that will correspond to the different tone types. These tones can be provisioned based on country-specific needs. This object defines the type of tone being accessed. The alertingSignal, specialDial, specialInfo, release, congestion, userDefined1, userDefined2, userDefined3, and userDefined4 tone types are used in the E line package.

Unsigned32 (1..4)

This MIB object represents the Tone Sequence reference of a multi-sequence tone.

Unsigned32 (1..8)

This MIB object represents the number of consecutive multi-frequency tones for the particular tone type in the multi-frequency table (pktcSigDevMultiFreqToneTable). Such a sequence of the consecutive multi-frequency tones forms the tone group for the particular tone type in the pktcSigDevToneTable.

Unsigned32 (0..5000)

This is the repeat count, which signifies how many times to repeat the entire on-off cadence sequence. Setting this object may result in a cadence duration longer or shorter than the overall signal duration specified by the time out (TO) 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 so that the TO duration setting should always be longer than the desired repeat count-time duration.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

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.

Unsigned32 (1..8)

This MIB object represents the frequency reference of a multi-frequency tone.

Unsigned32 (0..4000)

This MIB object represents the value of the first frequency of a tone type. A value of zero implies absence of the referenced frequency.

Unsigned32 (0..4000)

This MIB object represents the value of the second frequency of a tone type. A value of zero implies absence of the referenced frequency.

Unsigned32 (0..4000)

This MIB object represents the value of the third frequency of a tone type. A value of zero implies absence of the referenced frequency.

Unsigned32 (0..4000)

This MIB object represents the value of the fourth frequency of a tone type. A value of zero implies absence of the referenced frequency.

INTEGER1 = firstModulatedBySecond2 = summation · Integer32

This MIB object provides directive on the modulation or summation of the frequencies involved in the tone. It is to be noted that while summation can be done without any constraint on the number of frequencies, the modulation (amplitude) holds good only when there are two frequencies (first and second). Thus: - If the mode is set to a value of 'firstModulatedBySecond(1)', the first frequency MUST be modulated by the second, and the remaining frequencies (third and fourth) ignored. The percentage of amplitude modulation to be applied is defined by the MIB object pktcSigDevToneFreqAmpModePrtg. - If the mode is set to a value of 'summation(2)', all the frequencies MUST be summed without any modulation.

Unsigned32 (0..100)

This MIB object represents the percentage of amplitude modulation applied to the second frequency when the MIB object pktcSigDevToneFreqMode is set to a value of 'firstModulatedBySecond (1)'. If the MIB object pktcSigDevToneFreqMode is set to value of 'summation (2)', then this MIB object MUST be ignored.

TenthdBmThis TEXTUAL-CONVENTION represents power levels that are normally expressed in dBm. Units are in tenths of a dBm; for example, -13.5 dBm will be represented as -135. (-250..-110) · Integer32 · hint d-1 · 1/10 of a dBm

This MIB object contains the decibel level for each analog signal (tone) that is locally generated (versus in-band supervisory tones) and sourced to the a-b terminals (TE connection point). Each tone in itself may consist of multiple frequencies, as defined by the MIB table pktcSigDevMultiFreqToneTable. This MIB object reflects the desired level at the Telco (POTS) a-b (T/R) terminals, including the effect of any MTA receiver gain (loss). This is required so that locally generated tones are consistent with remotely generated in-band tones at the a-b terminals, consistent with user expectations. This MIB object must be set for each tone. When tones are formed by combining multi-frequencies, the level of each frequency shall be set so as to result in the tone level specified in this object at the a-b (T/R) terminals. The wide range of levels for this Object is required to provide signal-generator levels across the wide range of gains (losses) -- but does not imply the entire range is to be achievable given the range of gains (losses) in the MTA.

Unsigned32 (0..5000) · milliseconds

This MIB object represents the duration for which the frequency reference corresponding to the tone type is turned on.

Unsigned32 (0..5000) · milliseconds

This MIB object represents the duration for which the frequency reference corresponding to the tone type is turned off.

Unsigned32 (0..5000)

This MIB object indicates the number of times to repeat the cadence cycle represented by the on/off durations (refer to the MIB objects pktcSigDevToneFreqOnDuration and pktcSigDevToneFreqOffDuration). Setting this object may result in a tone duration that is longer or shorter than the overall signal duration specified by the time out (TO) object for the corresponding tone type. If the value of this MIB Object indicates a longer duration than that specified by the TO, the latter overrules the former, and the desired tone duration will be truncated according to the TO. However, 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. A value of zero means the tone sequence is to be played once but not repeated.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (3..255) · OCTET STRING · hint 255t

This object contains a string indicating the call agent name (e.g., ca@example.com). The call agent name, after the character '@', MUST be a fully qualified domain name (FQDN) and MUST have a corresponding pktcMtaDevCmsFqdn entry in the pktcMtaDevCmsTable. The object pktcMtaDevCmsFqdn is defined in the PacketCable MIBMTA Specification. For each particular endpoint, the MTA MUST use the current value of this object to communicate with the corresponding CMS. The MTA MUST update this object with the value of the 'Notified Entity' parameter of the NCS message. Because of the high importance of this object to the ability of the MTA to maintain reliable NCS communication with the CMS, it is highly recommended not to change this object's value using SNMP during normal operation.

InetPortNumberRepresents a 16 bit port number of an Internet transport layer protocol. Port numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/>. The value zero is object-specific and must be defined as part of the description of any object that uses this syntax. Examples of the usage of zero might include situations where a port number is unknown, or when the value zero is used as a wildcard in a filter.Reference: STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960 (1025..65535) · Unsigned32 · hint d

This object contains the current value of the User Datagram Protocol (UDP) receive port on which the call agent will receive NCS from the endpoint. For each particular endpoint, the MTA MUST use the current value of this object to communicate with the corresponding CMS. The MTA MUST update this object with the value of the 'Notified Entity' parameter of the NCS message. If the Notified Entity parameter does not contain a CallAgent port, the MTA MUST update this object with the default value of 2727. Because of the high importance of this object to the ability of the MTA to maintain reliable NCS communication with the CMS, it is highly recommended not to change this object's value using SNMP during normal operation. ⓘ

Unsigned32 · seconds

This object contains the value of the partial dial time out. The time out (TO) elements are intended to limit the time a tone or frequency is generated. When this MIB object is set to a value of '0', the MTA MUST NOT generate the corresponding frequency or tone, regardless of the definitions pertaining to frequency, tone duration, or cadence. ⓘ

Unsigned32 · seconds

This object contains the value of the critical dial time out. The time out (TO) elements are intended to limit the time a tone or frequency is generated. When this MIB object is set to a value of '0', the MTA MUST NOT generate the corresponding frequency or tone, regardless of the definitions pertaining to frequency, tone duration, or cadence. ⓘ

Unsigned32 · seconds

This object contains the default time out value for busy tone. The MTA MUST NOT update this object with the value provided in the NCS message (if present). If the value of the object is modified by the SNMP Management Station, the MTA MUST use the new value as a default only for a new signal requested by the NCS message. The time out (TO) elements are intended to limit the time a tone or frequency is generated. When this MIB object is set to a value of '0', the MTA MUST NOT generate the corresponding frequency or tone, regardless of the definitions pertaining to frequency, tone duration, or cadence. ⓘ

Unsigned32 · seconds

This object contains the default time out value for dial tone. The MTA MUST NOT update this object with the value provided in the NCS message (if present). If the value of the object is modified by the SNMP Management Station, the MTA MUST use the new value as a default only for a new signal requested by the NCS message. The time out (TO) elements are intended to limit the time a tone or frequency is generated. When this MIB object is set to a value of '0', the MTA MUST NOT generate the corresponding frequency or tone, regardless of the definitions pertaining to frequency, tone duration, or cadence. ⓘ

Unsigned32 · seconds

This object contains the default time out value for message waiting indicator. The MTA MUST NOT update this object with the value provided in the NCS message (if present). If the value of the object is modified by the SNMP Manager application, the MTA MUST use the new value as a default only for a new signal requested by the NCS message. The time out (TO) elements are intended to limit the time a tone or frequency is generated. When this MIB object is set to a value of '0', the MTA MUST NOT generate the corresponding frequency or tone, regardless of the definitions pertaining to frequency, tone duration, or cadence. ⓘ

Unsigned32 · seconds

This object contains the default time out value for the off-hook warning tone. The MTA MUST NOT update this object with the value provided in the NCS message (if present). If the value of the object is modified by the SNMP Manager application, the MTA MUST use the new value as a default only for a new signal requested by the NCS message. The time out (TO) elements are intended to limit the time a tone or frequency is generated. When this MIB object is set to a value of '0', the MTA MUST NOT generate the corresponding frequency or tone, regardless of the definitions pertaining to frequency, tone duration, or cadence. ⓘ

Unsigned32 · seconds

This object contains the default time out value for ringing. The MTA MUST NOT update this object with the value provided in the NCS message (if present). If the value of the object is modified by the SNMP Management Station, the MTA MUST use the new value as a default only for a new signal requested by the NCS message. The time out (TO) elements are intended to limit the time a tone or frequency is generated. When this MIB object is set to a value of '0', the MTA MUST NOT generate the corresponding frequency or tone, regardless of the definitions pertaining to frequency, tone duration, or cadence. ⓘ

Unsigned32 · seconds

This object contains the default time out value for ring back. The MTA MUST NOT update this object with the value provided in the NCS message (if present). If the value of the object is modified by the SNMP Management Station, the MTA MUST use the new value as a default only for a new signal requested by the NCS message. The time out (TO) elements are intended to limit the time a tone or frequency is generated. When this MIB object is set to a value of '0', the MTA MUST NOT generate the corresponding frequency or tone, regardless of the definitions pertaining to frequency, tone duration, or cadence. ⓘ

Unsigned32 · seconds

This object contains the default time out value for reorder tone. The MTA MUST NOT update this object with the value provided in the NCS message (if present). If the value of the object is modified by the SNMP Management Station, the MTA MUST use the new value as a default only for a new signal requested by the NCS message. The time out (TO) elements are intended to limit the time a tone or frequency is generated. When this MIB object is set to a value of '0', the MTA MUST NOT generate the corresponding frequency or tone, regardless of the definitions pertaining to frequency, tone duration, or cadence. ⓘ

Unsigned32 · seconds

This object contains the default time out value for stutter dial tone. The MTA MUST NOT update this object with the value provided in the NCS message (if present). If the value of the object is modified by the SNMP Management Station, the MTA MUST use the new value as a default only for a new signal requested by the NCS message. The time out (TO) elements are intended to limit the time a tone or frequency is generated. When this MIB object is set to a value of '0', the MTA MUST NOT generate the corresponding frequency or tone, regardless of the definitions pertaining to frequency, tone duration, or cadence. ⓘ

Unsigned32

This MIB object is used as part of an NCS retransmission algorithm. Prior to any retransmission, the MTA must check to make sure that the time elapsed since the sending of the initial datagram does not exceed the value specified by this MIB object. If more than Tsmax time has elapsed, then the retransmissions MUST cease. Refer to the MIB object pktcSigEndPntConfigThist for information on when the endpoint becomes disconnected. ⓘ

Unsigned32

This object contains the suspicious error threshold for signaling messages. The pktcSigEndPntConfigMax1 object indicates the retransmission threshold at which the MTA MAY actively query the domain name server (DNS) in order to detect the possible change of call agent interfaces. ⓘ

Unsigned32

This object contains the disconnect error threshold for signaling messages. The pktcSigEndPntConfigMax2 object indicates the retransmission threshold at which the MTA SHOULD contact the DNS one more time to see if any other interfaces to the call agent have become available. ⓘ

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object enables/disables the Max1 domain name server (DNS) query operation when the pktcSigEndPntConfigMax1 threshold has been reached. A value of true(1) indicates enabling, and a value of false(2) indicates disabling.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object enables/disables the Max2 domain name server (DNS) query operation when the pktcSigEndPntConfigMax2 threshold has been reached. A value of true(1) indicates enabling, and a value of false(2) indicates disabling.

Unsigned32 · seconds

Maximum Waiting Delay (MWD) contains the maximum number of seconds an MTA waits, after powering on, before initiating the restart procedure with the call agent. ⓘ

Unsigned32 · seconds

This MIB object represents the 'disconnected' initial waiting delay within the context of an MTA's 'disconnected procedure'. The 'disconnected procedure' is initiated when an endpoint becomes 'disconnected' while attempting to communicate with a call agent. The 'disconnected timer' associated with the 'disconnected Procedure' is initialized to a random value, uniformly distributed between zero and the value contained in this MIB object. For more information on the usage of this timer, please refer to the PacketCable NCS Specification. ⓘ

Unsigned32 · seconds

This MIB object represents the 'disconnected' minimum waiting delay within the context of an MTA's 'disconnected procedure', specifically when local user activity is detected. The 'disconnected procedure' is initiated when an endpoint becomes 'disconnected' while attempting to communicate with a call agent. For more information on the usage of this timer, please refer to the PacketCable NCS Specification. ⓘ

Unsigned32 · seconds

This object contains the maximum number of seconds the MTA waits, after a disconnect, before initiating the disconnected procedure with the call agent. ⓘ

Unsigned32 · seconds

This object specifies the maximum number of seconds the MTA waits for a response to an NCS message before initiating a retransmission. ⓘ

Unsigned32 · milliseconds

This object contains the initial number of seconds for the retransmission timer. ⓘ

Unsigned32 · minutes

Specifies a time out value, in minutes, for sending long duration call notification messages. ⓘ

Unsigned32 · seconds

Time out period, in seconds, before no response is declared. ⓘ

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

This object contains the Row Status associated with the pktcSigEndPntConfigTable. There are no restrictions or dependencies amidst the columnar objects before this row can be activated or for modifications of the columnar objects when this object is set to a value of 'active(1).

Unsigned32 (0..10)

This object contains the default value of the maximum number of repetitions of the Call Waiting tone that the MTA will play from a single CMS request. The MTA MUST NOT update this object with the information provided in the NCS message (if present). If the value of the object is modified by the SNMP Manager application, the MTA MUST use the new value as a default only for a new signal requested by the NCS message.

Unsigned32 (1..100) · seconds

This object contains the delay between repetitions of the Call Waiting tone that the MTA will play from a single CMS request.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

This object contains the type of Internet address contained in the MIB object 'pktcSigEndPntStatusCallIpAddress'. Since pktcSigEndPntStatusCallIpAddress is expected to contain an IP address, a value of dns(16) is disallowed.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

This MIB object contains the chosen IP address of the CMS currently being used for the corresponding endpoint. The device determines the IP address by using DNS to resolve the IP address of the CMS from the FQDN stored in the MIB object 'pktcSigEndPntConfigCallAgentId'. The processes are outlined in the PacketCable NCS and Security specifications, and MUST be followed by the MTA. The IP address type contained in this MIB object is indicated by pktcSigEndPntStatusCallIpAddressType. ⓘ

INTEGER1 = operational2 = noSecurityAssociation3 = disconnected · Integer32

This object contains the error status for this interface. The operational status indicates that all operations necessary to put the line in service have occurred, and the CMS has acknowledged the Restart In Progress (RSIP) message successfully. If pktcMtaDevCmsIpsecCtrl is enabled for the associated call agent, the noSecurityAssociation status indicates that no Security Association (SA) yet exists for this endpoint. If pktcMtaDevCmsIpsecCtrl is disabled for the associated call agent, the noSecurityAssociation status is not applicable and should not be used by the MTA. The disconnected status indicates one of the following two: If pktcMtaDevCmsIpsecCtrl is disabled, then no security association is involved with this endpoint. The NCS signaling software is in process of establishing the NCS signaling link via an RSIP exchange. Otherwise, when pktcMtaDevCmsIpsecCtrl is enabled, security Association has been established, and the NCS signaling software is in process of establishing the NCS signaling link via an RSIP exchange.

Unsigned32 (20..1550) · Milliseconds

This is the minimum time a line needs to be on-hook for a valid hook flash. The value of this object MUST be greater than the value of pktcSigEndPntConfigPulseDialMaxBreakTime. The value of pktcSigEndPntConfigMinHookFlash MUST be less than pktcSigEndPntConfigMaxHookFlash. This object MUST only be set via the MTA configuration during the provisioning process. Furthermore, given the possibility for the 'pulse dial' and 'hook flash' to overlap, the value of this object MUST be greater than the value contained by the MIB Object 'pktcSigEndPntConfigPulseDialMaxMakeTime'.

Unsigned32 (20..1550) · Milliseconds

This is the maximum time a line needs to be on-hook for a valid hook flash. The value of pktcSigEndPntConfigMaxHookFlash MUST be greater than pktcSigEndPntConfigMinHookFlash. This object MUST only be set via the MTA configuration during the provisioning process.

Unsigned32 (100..1500) · Milliseconds

This is the pulse dial inter-digit time out. This object MUST only be set via the MTA configuration during the provisioning process.

Unsigned32 (20..200) · Milliseconds

This is the minimum make pulse width for the dial pulse. The value of pktcSigEndPntConfigPulseDialMinMakeTime MUST be less than pktcSigEndPntConfigPulseDialMaxMakeTime. This object MUST only be set via the MTA configuration during the provisioning process.

Unsigned32 (20..200) · Milliseconds

This is the maximum make pulse width for the dial pulse. The value of pktcSigEndPntConfigPulseDialMaxMakeTime MUST be greater than pktcSigEndPntConfigPulseDialMinMakeTime. This object MUST only be provided via the configuration file during the provisioning process. Furthermore, given the possibility for the 'pulse dial' and 'hook flash' to overlap, the value of this object MUST be less than the value contained by the MIB object pktcSigEndPntConfigMinHookFlash.

Unsigned32 (20..200) · Milliseconds

This is the minimum break pulse width for the dial pulse. The value of pktcSigEndPntConfigPulseDialMinBreakTime MUST be less than pktcSigEndPntConfigPulseDialMaxBreakTime. This object must only be provided via the configuration file during the provisioning process.

Unsigned32 (20..200) · Milliseconds

This is the maximum break pulse width for the dial pulse. The value of pktcSigEndPntConfigPulseDialMaxBreakTime MUST be greater than pktcSigEndPntConfigPulseDialMinBreakTime. This object MUST only be provided via the configuration file during the provisioning process.