2015-05-12
Digital Signal Processing (DSP) Management MIB module. The MIB module monitors the DSP resource and status. Acronyms & Terms ================ DTMF - Dual Tone Multi-Frequency. DTMF uses two frequencies, the high frequency omponent and the low frequency component, to generate digit signals. DSPFarm - DSPFarm ia a logical name given to a functionality which groups the DSP resources to provide certain service like transcoding and conferencing using DSP. DSPFarm profile - A DSPFarm profile logically groups the DSP to perform service like transcoding and conferencing. It is uniquely identified by a profile number. MTP - Media Termination Point. RTP packet received by MTP in the incoming call leg will be regenerated and send out through the outgoing call leg. transcode - Translating codec. transcoder is used to do codec translation. If incoming call leg negotiates codec-A and outgoing call leg negotiates codec-B then transcoder will convert received RTP packet from codec-A to codec-B or codec-B to codec-A. MTP hardware session - Media termination functionality with using DSP. MTP software session - Media termination functionality without using DSP. RTP - Real-time Transport protocol. Video Pool - A group of DSP resources dedicated to providing video services.
Download CISCO-DSP-MGMT-MIB.txt Open CISCO-DSP-MGMT-MIB.txt in a new tab
SCALARS (10) · TABLES (8) · TRAPS (4)
END OF TOC
1.3.6.1.4.1.9.9.86.1.3.1
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This variable controls whether the system produces the cdspMIBCardStateNotification. A false value will prevent DSP card fatal notifications from being generated by this system.
1.3.6.1.4.1.9.9.86.1.3.2
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This variable controls whether the system produces the cdspOperStateNotification. A false value will prevent a DSP operational state notification from being generated by this system.
1.3.6.1.4.1.9.9.86.1.3.3
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This object specifies whether the system produces cdspVideoUsageNotification. 'true': Video usage notification is generated by this system. 'false': Video usage notification is not generated by this system.
1.3.6.1.4.1.9.9.86.1.3.4
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This object specifies whether the system produces cdspVideoOutOfResourceNotification. 'true': Video out-of-resource notification is generated by this system. 'false': Video out-of-resource notification is not generated by this system.
1.3.6.1.4.1.9.9.86.1.6.1
Unsigned32
This object indicates the maximum transcode sessions configured globally for the voice gateway.
1.3.6.1.4.1.9.9.86.1.6.2
Unsigned32
This object indicates the total number of available sessions from the maximum transcode sessions configured globally for the voice gateway.
1.3.6.1.4.1.9.9.86.1.7.1
Unsigned32
This object indicates the total number of transcode sessions available for the voice gateway. The value is equal to summation of all the values returned by transcode profile object cdspTranscodeProfileMaxAvailSess.
1.3.6.1.4.1.9.9.86.1.7.2
Unsigned32
This object indicates the total number of unused transcode sessions.
1.3.6.1.4.1.9.9.86.1.7.3
Unsigned32
This object indicates the total number of MTP sessions available for the voice gateway. The value is equal to summation of all the values returned by MTP profile object cdspMtpProfileMaxAvailHardSess.
1.3.6.1.4.1.9.9.86.1.7.4
Unsigned32
This object indicates the total number of unused MTP sessions.
1.3.6.1.4.1.9.9.86.1.1.1
Index: entPhysicalIndex
The DSP Card Table. It contains status information of the DSP cards present within the router.
from ENTITY-MIB
PhysicalIndexAn arbitrary value that uniquely identifies the physical entity. The value should be a small positive integer. Index values for different physical entities are not necessarily contiguous. (1..2147483647) · Integer32 · hint d
The index for this entry.
1.3.6.1.4.1.9.9.86.1.1.1.1.1
Integer32
The object corresponds to cardIndex in the chassis mib. If value of this object is 0, then the entry is not associated to cardIndex of the chassis mib.
1.3.6.1.4.1.9.9.86.1.1.1.1.2
INTEGER1 = normal2 = warning3 = critical4 = fatal5 = offLine · Integer32
The object indicates the current state of DSP card being monitored. normal - DSP card in normal condition. warning - DSP card has some problem and need attention. critical - DSP card has a major alarm. fatal - DSP card is not functional. DSP subsystem might reset DSP card to recover it from the fatal error condition. After the DSP card is reset successfully, the object cdspCardResourceUtilization and cdspCardLastHiWaterUtilization are reset to 0. If the fatal error is persistent in this object after card is reset, the card should be replaced. offLine - DSP card is in off-line maintenance state.
1.3.6.1.4.1.9.9.86.1.1.1.1.3
Unsigned32 (0..100) · percent
The object indicates the percentage of current DSP resource utilization of the card. The utilization is a ratio of number of busy DSP resources (for handling calls, transcoding, voice compression,...) to the total available DSP resources.
1.3.6.1.4.1.9.9.86.1.1.1.1.4
Unsigned32 (0..100) · percent
The object indicates the last high water mark of DSP resource utilization. This object is reset to 0 after DSP card is reset.
1.3.6.1.4.1.9.9.86.1.1.1.1.5
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The value of sysUpTime when the last DSP card reset occurred.
1.3.6.1.4.1.9.9.86.1.1.1.1.6
Unsigned32 · channels
The maximum number of channels allowed in each DSP. The value is chosen in an implementation-dependent manner by the DSP functionality. The value of 0 in this object indicates Channelized DSP mode is turned off.
1.3.6.1.4.1.9.9.86.1.1.1.1.7
Unsigned32 (1..2048)
The total number of DSPs in the card.
1.3.6.1.4.1.9.9.86.1.1.1.1.8
Gauge32 (0..2048)
The number of DSPs in the failed state (i.e cdspOperstate is 'failed')
1.3.6.1.4.1.9.9.86.1.1.1.1.9
Unsigned32 (1..2048)
This object specifies the threshold of DSP failures. When 'cdspFailedDsp' reaches the value of this object, the voice gateway switchover will occur. The maximum value of this object can not be more than the value in 'cdspTotalDsp'
1.3.6.1.4.1.9.9.86.1.1.1.1.10
Gauge32 (0..2048)
The number of DSPs in the congested state (i.e cdspOperstate is 'congested').
1.3.6.1.4.1.9.9.86.1.1.1.1.11
Gauge32 (0..2048)
The number of DSPs in the normal state (i.e cdspOperstate is 'normal').
1.3.6.1.4.1.9.9.86.1.1.1.1.12
Unsigned32 (0..2048)
This object specifies the number of DSPs that need to be set aside for making Nx64 calls. The max value of this object is limited to the value of the object 'cdspTotalDsp'. If this value is 0, it is not allowed to make any Nx64 call. The default value of this object is 0.
1.3.6.1.4.1.9.9.86.1.1.1.1.13
INTEGER1 = tgw2 = cable3 = umts3G4 = cdma3G5 = tgw26 = fmc · Integer32
This object indicates the codec template supported in DSP image. The codec template can be: tgw - Codec template for wireline used in Trunking GateWay application. cable - Codec template for AES (Advanced Encryption Standard) encryption used in cable application. umts3G - Codec template for AMR (Adaptive Multi-Rate) codecs used in 3G UMTS (Universal Mobile Telecommunication System) application. cdma3G - Codec template for EVRC (Enhanced Variable Rate Codec) used in 3G CDMA (Code Division Multiple Access) application. tgw2 - Codec template for iLBC (Internet Low Bandwidth Codec) codec used in Tandem Gateway application. fmc - Codec template for AMR (Adaptive Multi-Rate) codec used in Fixed Mobile Convergence (FMC) application.
1.3.6.1.4.1.9.9.86.1.1.1.1.14
PercentAn integer that is in the range of a percent value. (0..100) · Integer32
The object indicates the percentage of current DSP video resource pool utilization of the card.
1.3.6.1.4.1.9.9.86.1.1.1.1.15
Unsigned32 (1..100)
This object specifies the threshold of DSP video pool resource usage. When cdspCardVideoPoolUtilization crosses the value of this threshold in the rising direction, cdspVideoUsageNotification is generated. If cdspCardVideoPoolUtilization stays above the value of this threshold, cdspVideoUsageNotification is generated whenever the value of cdspCardVideoPoolUtilization increases, but no notification is sent if when the value of cdspCardVideoPoolUtilization decreases. No notification is sent if cdspCardVideoPoolUtilization crosses the value of this threshold in the falling direction.
1.3.6.1.4.1.9.9.86.1.2.1
Index: entPhysicalIndex
Status information for the DSPs. This status table is used for tracking dangling DSP resources. The dangling DSP channel means that the DSP channel is reserved for serving calls but the channel is not used by active calls. The number of the dangling DSP channels can be computed by 'cdspInUseChannels - cdspActiveChannels'.
from ENTITY-MIB
PhysicalIndexAn arbitrary value that uniquely identifies the physical entity. The value should be a small positive integer. Index values for different physical entities are not necessarily contiguous. (1..2147483647) · Integer32 · hint d
The index for this entry.
1.3.6.1.4.1.9.9.86.1.2.1.1.1
INTEGER1 = normal2 = shutdown3 = congested4 = failed · Integer32
The current operational state of the DSP. normal - DSP operates normally shutdown - DSP is shutdown due to fatal error congested - DSP does not accept call because the DSP buffer is full failed - DSP failed
1.3.6.1.4.1.9.9.86.1.2.1.1.2
Counter32
The object indicates the accumulated number of DSP Alarms.
1.3.6.1.4.1.9.9.86.1.2.1.1.3
INTEGER1 = other2 = noAlarm3 = dspFatalError4 = dspMemoryError5 = dspBufferError6 = dspDownloadError · Integer32
The object indicates the current or last alarm state of DSP. other - none of the following noAlarm - alarm condition had not been detected dspFatalError - DSP fatal error dspMemoryError - DSP memory error is detected dspBufferError - DSP buffer error dspDownloadError - Failed to download software to DSP. The cdspOperState will be set to 'shutdown(2) if the alarm condition of DSP is persistent.
1.3.6.1.4.1.9.9.86.1.2.1.1.4
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The object indicates the failure reason for the current or last DSP Alarm. It should be used only for direct, human-readable display and only if a management station is unable to decode the value of cdspLastAlarmCause.
1.3.6.1.4.1.9.9.86.1.2.1.1.5
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The value of sysUpTime when the last DSP Alarm occurred. The value of this object is 0 if the value of cdspLastAlarmCause object is 'noAlarm'.
1.3.6.1.4.1.9.9.86.1.2.1.1.6
Unsigned32 · channels
The total number of channels in the DSP. This value is predetermined by the DSP functionality upon initialization. The value of 0 in this object indicates Channelized DSP mode is turned off.
1.3.6.1.4.1.9.9.86.1.2.1.1.7
Gauge32 · channels
The number of channels that are reserved for serving calls. The value is incremented when the DSP channel is reserved for call setup and is decremented after the DSP channel is free due to call disconnection.
1.3.6.1.4.1.9.9.86.1.2.1.1.8
Gauge32 · channels
The number of channels that are used by active calls to process media stream. The value is incremented after the reserved DSP channel enters call connection state and is decremented after the call is disconnected.
1.3.6.1.4.1.9.9.86.1.2.1.1.9
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This object indicates if the DSP channels are splitted for signaling call and bearer call. If the value of this object is 'true' which means that signaling call and bearer call cannot share any DSP channel. This object is not applicable when Channelized DSP mode is turned off.
1.3.6.1.4.1.9.9.86.1.2.1.1.10
Counter32
The number of congestion occurred on the DSP. This value is set to 0 when system is reset.
1.3.6.1.4.1.9.9.86.1.2.1.1.11
Unsigned32 (1..252)
This object identifies the DSP number associated with this DSP entity.
1.3.6.1.4.1.9.9.86.1.2.2
augments cdspStatusTable
Index: entPhysicalIndex
This table provides the additional detailed state and statistics information for a DSP that supports the splitted signalling and bearer channels.
from ENTITY-MIB
PhysicalIndexAn arbitrary value that uniquely identifies the physical entity. The value should be a small positive integer. Index values for different physical entities are not necessarily contiguous. (1..2147483647) · Integer32 · hint d
The index for this entry.
1.3.6.1.4.1.9.9.86.1.2.2.1.1
Gauge32 · calls
The current number of bearer calls on the DSP.
1.3.6.1.4.1.9.9.86.1.2.2.1.2
Gauge32 · calls
The current number of signaling calls on the DSP.
1.3.6.1.4.1.9.9.86.1.2.2.1.3
Gauge32 · percent
The percentage of channels on the DSP currently available for bearer calls.
1.3.6.1.4.1.9.9.86.1.2.2.1.4
Gauge32 · percent
The percentage of channels on the DSP currently available for signaling calls.
1.3.6.1.4.1.9.9.86.1.4.1
Index: entPhysicalIndex
This table contains information on voice call setup related parameters for DSP resource.
from ENTITY-MIB
PhysicalIndexAn arbitrary value that uniquely identifies the physical entity. The value should be a small positive integer. Index values for different physical entities are not necessarily contiguous. (1..2147483647) · Integer32 · hint d
The index for this entry.
1.3.6.1.4.1.9.9.86.1.4.1.1.1
INTEGER13 = decimal19 = hexadecimal · Integer32
Reference: Section 5.1 of RFC2833
This object specifies the RTP (Real Time Protocol) payload type of the SID (Silence Insertion Descriptor) packet that is sent to the remote endpoint at the onset of silence suppression.
1.3.6.1.4.1.9.9.86.1.4.1.1.2
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
Reference: Appendix A.7 of RFC1889
This objects controls if RTCP (Real Time Control Protocol) will be enabled. If this object is set to 'true', both transmission and reception of RTCP packets are enabled; otherwise, transmission of RTCP packets is disabled while any received RTCP packets are ignored.
1.3.6.1.4.1.9.9.86.1.4.1.1.3
Unsigned32 (5000..65535) · milliseconds
Reference: Appendix A.7 of RFC1889
This attribute specifies the RTCP report interval (defined in RFC1889). It indicates the interval in which the RTCP reports should be sent to the participating members. RTCP reports is sent out in a random interval computed by using 'cdspRtcpTransInterval' and a random number that is between 0.5 and 1.5. This interval timer also serves the purpose of RTP packets receive timer. At every interval multiplier times this interval, where a check is made on a VoIP connection (which is in SENDRECV or RECVONLY xGCP modes) to see if any RTP packets have been received. If not, gateway-initiated DLCX should be sent to the Call Agent. This object is applicable only if 'cdspRtcpControl' is set to 'true'.
1.3.6.1.4.1.9.9.86.1.4.1.1.4
Unsigned32 (1..60)
Reference: Section 6.2.1 of RFC1889
This object specifies an approximate RTCP report interval (defined in RFC 1889) in milliseconds in which the RTCP reports should be sent to the participating members. It specifies how many times the RTCP reports may fail before exception condition activity may be done. In the time elapse of value of this MIB object times the RTCP Report Interval specified by 'cdspRtcpTransInterval', a check will be done on a VoIP connection (which is in SENDRECV or RECVONLY xGCP modes) to see if any RTP packets have been received. If not, gateway-initiated DLCX should be sent to the Call Agent. This object is applicable only if 'cdspRtcpControl' is set to 'true'.
1.3.6.1.4.1.9.9.86.1.4.1.1.5
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This attribute is used to enable or disable the Adaptive VAD knob of the VAD algorithm. Adaptive VAD works in conjunction with VAD Threshold (cvifcfgMusicOnHoldThreshold from CISCO-VOICE-IF-MIB). When this object set to 'true', VAD Threshold is ignored and the DSP adjusts the threshold automatically according to the background noise level. When the adaptive VAD configuration is 'false', VAD threshold is used directly. The VAD configuration is ignored for all CODECs that contain their own VAD (G.729AB, G.723.1A and GSM-EFR). Likewise, when a channel is configured in ClearChannel mode (Clear Channel is Non-Compression CODEC channel), VAD will automatically be disabled irrespective of the configuration.
1.3.6.1.4.1.9.9.86.1.4.1.1.6
Integer32 (-250..30) · 0.1 dBm
Reference: Q.23, Q.24, EIA/TIA-464
This object specifies the power level of the low frequency component of DTMF. The power level of the high frequency component of DTMF is relative above or below the value specified in object cdspDtmfPowerTwist. If the value of cdspDtmfPowerTwist is 0, the power level of the high frequency component as well as the low frequency component is specified by this object.
1.3.6.1.4.1.9.9.86.1.4.1.1.7
Integer32 (-100..100) · 0.1 dB
Reference: Q.23, Q.24, EIA/TIA-464
This object specifies the relative power level of the high frequency component of DTMF. The low frequency group is always fixed to the value specified by cdspDtmfPowerLevel. When this object is set to 0, the power level of both frequency components is set to the same level. When this object is set to a positive value, the power level of the high frequency component is set to relatively higher specified in this object than the low frequency component. For example if cdspDtmfPowerLevel is set to -120(-12 dBm) and this object is set to 50, the power level of the high frequency component becomes -70(-7 dBm). When this object is set to a negative value, the power level of the high frequency component is set to relatively lower specified in this object than the low frequency component. For example if cdspDtmfPowerLevel is set to -120(-12 dBm) and this object is set to -100, the power level of the high frequency component becomes -220(-22 dBm). The power level of the high frequency component has to be in the data range specified in cdspDtmfPowerLevel. For example if cdspDtmfPowerLevel is set to -200(-20 dBm) and this object is set to -100, the power level of the high frequency component will become -300(-30 dBm) which is out of the range (-250..30) of data specified in cdspDtmfPowerLevel, so -100 is illegitimate for this setting.
1.3.6.1.4.1.9.9.86.1.4.1.1.8
INTEGER1 = disabled2 = startImmediately3 = startRtpOrRtcpPktRcvd4 = startRtcpPktRcvd · Integer32
This object specifies when the RTCP receive timer is started. disabled - timer is disabled startImmediately - timer starts immediately as soon as RTCP is enabled on the call startRtpOrRtcpPktRcvd - timer starts upon reception of the first RTP or RTCP packet startRtcpPktRcvd - timer starts upon reception of the first RTCP packet
1.3.6.1.4.1.9.9.86.1.4.1.1.9
INTEGER1 = disable2 = rfc3611Vqm3 = xnq · Integer32
Reference: RFC 3611
This object is used to disable VQM or enable either RFC 3611 RTCPXR or Extended Network Quality Metrics VQM. disable - VQM is disabled. rfc3611Vqm - RFC 3611 RTCPXR. RTCPXR packet uses extended report block type as defined in RFC3611. xnq - Extended Network Quality Metrics. The difference between RFC 3611 RTCPXR and Extended Network Quality Metrics is the extended report block type used in RTCPXR packets. RFC 3611 RTCPXR uses voip-metrics block type as defined in RFC3611. Extended Network Quality Metrics uses a proprietary block type. If this object is set to 'disabled', the RTP terminations (object cmedxTermTypePkgIds in CISCO-MEGACO-EXT-MIB) on the card cannot be provisioned with the related packages, rtcpxr or pkgXnq, respectively. If this object is set to 'rfc3611Vqm', the RTP terminations (object cmedxTermTypePkgIds in CISCO-MEGACO-EXT-MIB) on the card can include package ID 'rtcpxr (27)' and/or 'xrbm (28)', but can not include package ID 'pkgXnq (32)'. If this object is set to 'xnq', the RTP terminations (object cmedxTermTypePkgIds in CISCO-MEGACO-EXT-MIB) on the card can include package ID 'pkgXnq (32)', but can not include 'rtcpxr (27)' or 'xrbm (28)'.
1.3.6.1.4.1.9.9.86.1.4.1.1.10
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This object controls if RTCPXR (Real Time Control Protocol Extended Report) is enabled. If this object is set to 'true', both transmission and reception of RTCPXR packets are enabled; otherwise, transmission of RTCPXR packets is disabled while any received RTCPXR packets are ignored. If object cdspVqmControl is set to 'xnq (3)', this object is read-only with the value of 'true'.
1.3.6.1.4.1.9.9.86.1.4.1.1.11
Unsigned32 (1..5)
This object is used to configure the RTCPXR report frequency. i.e. how many RTCP packets during the interval of every RTCPXR packet. The RTCPXR report is sent every 'cdspRtcpXrTransMultiplier' of RTCP packet. Example: If RTCP packet is sent every 10 ms(frequency of RTCP packet = 10 ms), and 'cdspRtcpXrTransMultiplier' is set to 3, then RTCPXR is sent every 3x10 ms = 30 ms(frequency of RTCPXR packet = 30 ms). This object is applicable only if 'cdspRtcpXrControl' is set to 'true'. If object cdspVqmControl is set to 'xnq (3)', this object is read-only with the value of '1'.
1.3.6.1.4.1.9.9.86.1.4.1.1.12
Unsigned32 (1..255)
Reference: RFC3611
This object is the default minimum gap value configured for the IP stream. This object is applicable only if 'cdspVqmControl' is set to 'rfc3611Vqm'.
1.3.6.1.4.1.9.9.86.1.4.1.1.13
Unsigned32 (0..65535)
This object is the external R factor metric value. The value 127 means it is not applicable. This object is applicable only if 'cdspVqmControl' is set to 'rfc3611Vqm'. When 'cdspVqmControl' is not 'rfc3611Vqm', this object is set to 127.
1.3.6.1.4.1.9.9.86.1.4.1.1.14
INTEGER1 = none2 = simple3 = g711A1 · Integer32
Reference: ITU G.711 Appendix 1
This object specifies the packet loss concealment: (1) none: No packet loss concealment applied (2) simple: Cisco Proprietary packet loss concealment (3) g711A1: ITU G.711 Appendix I compliant
1.3.6.1.4.1.9.9.86.1.4.1.1.15
Unsigned32 (10..1000) · milliseconds
This attribute specifies the threshold for Severely Errored Second on VQM. If the total number of milliseconds sampled as bad voice quality in one second period exceeds threshold, then this second is considered a 'severely errored second'. This object is applicable only if 'cdspVqmControl' is set to 'xnq'.
1.3.6.1.4.1.9.9.86.1.4.1.1.16
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This attribute is used to enable or disable the transparent mode when establishing a non-transcoding IP-IP connection. The attribute does not apply for the transcoding IP-IP connections. A non-transcoding connection is one where the codec and packetization period are the same between the two IP terminations. When this object is set to 'true', the non-transcoding IP-IP connection is established in such a way that the bearer stream is not interrupted by the gateway. When this object is set to 'false', the non-transcoding IP-IP connection is established in a way the gateway terminates the bearer stream at one leg, and regenerates the bearer stream at the other leg.
1.3.6.1.4.1.9.9.86.1.4.1.1.17
INTEGER1 = normal2 = fastRoute3 = transparent · Integer32
This object specifies the voice mode for IP IP connections. normal : A normal Mode is a transcoding mode for IP-IP connections where the bearer properties will be different on two ends of a call. fastRoute : A voice call will be esatblished in this mode when the codec is same on two ends of a call but packetization period is different. tranparent : A voice call will be established in transparent mode when the all the bearer properties for a voice call are same on the two ends of a call.
1.3.6.1.4.1.9.9.86.1.5.1
Index: entPhysicalIndex · cdspCodecPoolIndex
This table contains DSP utilization information for all the codec families available in codec template currently active on VXSM.
from ENTITY-MIB
PhysicalIndexAn arbitrary value that uniquely identifies the physical entity. The value should be a small positive integer. Index values for different physical entities are not necessarily contiguous. (1..2147483647) · Integer32 · hint d
The index for this entry.
1.3.6.1.4.1.9.9.86.1.5.1.1.1
Unsigned32 (1..64)
This object identifies a row. Pool index is corresponding to the number of DSP channels utilized. The instance identifier value of this object depends on the codec template supported on this module as indicated by the value of corresponding instance of 'cdspCodecTemplateSupported' of cdspCardStatusTable table. A pool index will map to codec family utilizing pool index number of DSP channels, codecs consuming same number of DSP channels will be part of one family. Based on the value of the corresponding instance of 'cdspCodecTemplateSupported', the possible instance identifier values of 'cdspCodecPollIndex' specific set of codec families: Codec Template Pool Index Codec family tgw 1 G.711 family/HDLC/CCD 3 G.729/G.726/T.38 family 4 G.723 family cable 1 G.711 family/HDLC/T.38 3 iLBC family tgw2 1 G.711 family/HDLC/T.38 3 G.729/G.726/T.38 family 4 iLBC family fmc 1 G.711 family/HDLC/T.38 2 G.729/G.726/T.38 family 3 AMR/EFR family
1.3.6.1.4.1.9.9.86.1.5.1.1.2
Unsigned32
This object indicates the number of DSP channels which are currently being utilized corresponding to active calls on VXSM segregated on the basis of codec families.
1.3.6.1.4.1.9.9.86.1.5.1.1.3
Unsigned32
This object indicates the number of DSP channels which are currently available on VXSM corresponding to a codec family.
1.3.6.1.4.1.9.9.86.1.6.3
Index: cdspTranscodeProfileId
This table contains information about each transcode DSPFarm profile. It gives the maximum number of transcode sessions configured and the number of available sessions per profile.
1.3.6.1.4.1.9.9.86.1.6.3.1.1
Unsigned32 (1..4294967295) · codecs
This object indicates the maximum number of codecs to be configured in the DSPFarm transcode profile.
1.3.6.1.4.1.9.9.86.1.6.3.1.2
Unsigned32 (1..4294967295)
This object indicates the profile number of the DSPFarm transcode profile.
1.3.6.1.4.1.9.9.86.1.6.3.1.3
Unsigned32 · sessions
This object indicates the maximum transcode sessions configured on the DSPFarm transcode profile for the voice gateway.
1.3.6.1.4.1.9.9.86.1.6.3.1.4
Unsigned32
This object indicates the total number of available transcode sessions per transcode profile from the configured maximum transcode sessions per transcode profile for the voice gateway.
1.3.6.1.4.1.9.9.86.1.6.3.1.5
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 is used to create a new entry or delete an existing entry in cdspTranscodeProfileTable. The storage type for all the entries created would be volatile. To retain the configured entries. One must write the configuration to memory in the voice gateway.
1.3.6.1.4.1.9.9.86.1.6.3.1.6
Unsigned32
The object indicates resource ID in the DSPFarm transcode profile
1.3.6.1.4.1.9.9.86.1.6.3.1.7
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 object indicates description of DSPFarm transcode profile.
1.3.6.1.4.1.9.9.86.1.6.3.1.8
INTEGER1 = nonSecure2 = secure · Integer32
This object indicates the profile service type of the DSPFarm transcode profile.
1.3.6.1.4.1.9.9.86.1.6.3.1.9
INTEGER1 = down2 = up · Integer32
This object specifies the admin state of the DSPFarm transcode profile
1.3.6.1.4.1.9.9.86.1.6.3.1.10
INTEGER1 = none2 = sccp3 = sbc4 = cube5 = other · Integer32
This object indicates the application used by the DSPFarm transcode profile
1.3.6.1.4.1.9.9.86.1.6.3.1.11
INTEGER1 = none2 = done3 = activeInProgress4 = activeInDown5 = notDone6 = invalid · Integer32
The object indicates application Status of DSPFarm transcode profile.
1.3.6.1.4.1.9.9.86.1.6.4
Index: cdspMtpProfileId
This table contains information about each MTP DSPFarm profile. It gives the maximum number of MTP sessions configured and the number of available sessions per profile.
1.3.6.1.4.1.9.9.86.1.6.4.1.1
Unsigned32 (1..4294967295)
This object indicates the profile number of the DSPFarm MTP profile.
1.3.6.1.4.1.9.9.86.1.6.4.1.2
Unsigned32 · sessions
This object indicates the maximum MTP software sessions configured per DSPFarm MTP profile for the voice gateway.
1.3.6.1.4.1.9.9.86.1.6.4.1.3
Unsigned32 · sessions
This object indicates the maximum MTP hardware sessions configured per DSPFarm MTP profile for the voice gateway.
1.3.6.1.4.1.9.9.86.1.6.4.1.4
Unsigned32 · sessions
This object indicates the total number of available MTP Hardware sessions per MTP profile from the configured maximum MTP sessions per MTP profile for the voice gateway.
1.3.6.1.4.1.9.9.86.1.6.4.1.5
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 is used to create a new entry or delete an existing entry in cdspMtpProfileTable. The storage type for all the entries created would be volatile. To retain the configured entries. One must write the configuration to memory in the voice gateway.
1.3.6.1.4.1.9.9.86.1.6.4.1.6
Unsigned32
The object indicates resource ID in the DSPFarm MTP profile
1.3.6.1.4.1.9.9.86.1.6.4.1.7
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 object indicates description of DSPFarm MTP profile.
1.3.6.1.4.1.9.9.86.1.6.4.1.8
INTEGER1 = nonSecure2 = secure · Integer32
This object indicates the profile service type of the DSPFarm Mtp profile.
1.3.6.1.4.1.9.9.86.1.6.4.1.9
INTEGER1 = down2 = up · Integer32
This object specifies the admin state of the DSPFarm MTP profile
1.3.6.1.4.1.9.9.86.1.6.4.1.10
INTEGER1 = none2 = sccp3 = sbc4 = cube5 = other · Integer32
This object indicates the Application used by the DSPFarm MTP profile
1.3.6.1.4.1.9.9.86.1.6.4.1.11
INTEGER1 = none2 = done3 = activeInProgress4 = activeInDown5 = notDone6 = invalid · Integer32
The object indicates application Status of DSPFarm MTP profile.
1.3.6.1.4.1.9.9.86.1.6.4.1.12
Unsigned32 · codecs
This object specifies maximum number of codecs to be configured in the DSPFarm MTP profile.
1.3.6.1.4.1.9.9.86.1.6.4.1.13
Unsigned32 · sessions
This object indicates the total number of available MTP Software sessions per MTP profile from the configured maximum MTP sessions per MTP profile for the voice gateway.
1.3.6.1.4.1.9.9.86.1.6.5
Index: cdspConferenceProfileId
This table contains information about each conference DSPFarm profile. It gives the maximum number of conference sessions configured and the number of available sessions per profile.
1.3.6.1.4.1.9.9.86.1.6.5.1.1
Unsigned32 (1..4294967295)
This object indicates the profile number of the DSPFarm conference profile.
1.3.6.1.4.1.9.9.86.1.6.5.1.2
Unsigned32
The object indicates resource ID in the DSPFarm conference profile.
1.3.6.1.4.1.9.9.86.1.6.5.1.3
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 object indicates description of DSPFarm conference profile.
1.3.6.1.4.1.9.9.86.1.6.5.1.4
INTEGER1 = nonSecure2 = secure · Integer32
This object indicates the profile service type of the DSPFarm conference profile.
1.3.6.1.4.1.9.9.86.1.6.5.1.5
INTEGER1 = down2 = up · Integer32
This object specifies the admin state of the DSPFarm conference profile.
1.3.6.1.4.1.9.9.86.1.6.5.1.6
INTEGER1 = none2 = sccp3 = sbc4 = cube5 = other · Integer32
This object indicates the application used by the DSPFarm conference profile.
1.3.6.1.4.1.9.9.86.1.6.5.1.7
INTEGER1 = none2 = done3 = activeInProgress4 = activeInDown5 = notDone6 = invalid · Integer32
The object indicates application Status of DSPFarm conference profile.
1.3.6.1.4.1.9.9.86.1.6.5.1.8
Unsigned32 · codecs
This object specifies maximum number of codecs to be configured in the DSPFarm conference profile.
1.3.6.1.4.1.9.9.86.1.6.5.1.9
Unsigned32
This object specifies the maximum conference sessions configured on the DSPFarm conference profile for the voice gateway.
1.3.6.1.4.1.9.9.86.1.6.5.1.10
Unsigned32
This object indicates the total number of available conference sessions per conference profile from the configured maximum conference sessions per conference profile for the voice gateway.
1.3.6.1.4.1.9.9.86.1.6.5.1.11
StorageType1 = other2 = volatile3 = nonVolatile4 = permanent5 = readOnlyDescribes the memory realization of a conceptual row. A row which is volatile(2) is lost upon reboot. A row which is either nonVolatile(3), permanent(4) or readOnly(5), is backed up by stable storage. A row which is permanent(4) can be changed but not deleted. A row which is readOnly(5) cannot be changed nor deleted. If the value of an object with this syntax is either permanent(4) or readOnly(5), it cannot be written. Conversely, if the value is either other(1), volatile(2) or nonVolatile(3), it cannot be modified to be permanent(4) or readOnly(5). (All illegal modifications result in a 'wrongValue' error.) Every usage of this textual convention is required to specify the columnar objects which a permanent(4) row must at a minimum allow to be writable. · Integer32
The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
1.3.6.1.4.1.9.9.86.1.6.5.1.12
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 is used to create a new entry or delete an existing entry in cdspConferenceProfileTable. The storage type for all the entries created would be volatile. To retain the configured entries. One must write the configuration to memory in the voice gateway.
1.3.6.1.4.1.9.9.86.2.0.1
A cdspMIBCardStateNotification is sent when the cdspCardState enters into normal(1) state and enters into or exits from fatal(4) state.
1.3.6.1.4.1.9.9.86.1.1.1.1.2
INTEGER1 = normal2 = warning3 = critical4 = fatal5 = offLine · Integer32
The object indicates the current state of DSP card being monitored. normal - DSP card in normal condition. warning - DSP card has some problem and need attention. critical - DSP card has a major alarm. fatal - DSP card is not functional. DSP subsystem might reset DSP card to recover it from the fatal error condition. After the DSP card is reset successfully, the object cdspCardResourceUtilization and cdspCardLastHiWaterUtilization are reset to 0. If the fatal error is persistent in this object after card is reset, the card should be replaced. offLine - DSP card is in off-line maintenance state.
1.3.6.1.4.1.9.9.86.2.0.2
A cdspOperStateNotification is sent when the cdspOperState enters into normal(1) state or shutdown(2) state. The value of entPhysicalName contains the name of the DSP.
1.3.6.1.4.1.9.9.86.1.2.1.1.1
INTEGER1 = normal2 = shutdown3 = congested4 = failed · Integer32
The current operational state of the DSP. normal - DSP operates normally shutdown - DSP is shutdown due to fatal error congested - DSP does not accept call because the DSP buffer is full failed - DSP failed
1.3.6.1.2.1.47.1.1.1.1.7
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 textual name of the physical entity. The value of this object should be the name of the component as assigned by the local device and should be suitable for use in commands entered at the device's 'console'. This might be a text name (e.g., 'console') or a simple component number (e.g., port or module number, such as '1'), depending on the physical component naming syntax of the device. If there is no local name, or if this object is otherwise not applicable, then this object contains a zero-length string. Note that the value of entPhysicalName for two physical entities will be the same in the event that the console interface does not distinguish between them, e.g., slot-1 and the card in slot-1.
1.3.6.1.4.1.9.9.86.2.0.3
This notification is sent when cdspCardVideoPoolUtilization reaches the specified threshold (cdspCardVideoPoolUtilizationThreshold). cdspCardVideoPoolUtilization indicates the DSP video pool usage at the time this notification is sent. cdspCardVideoPoolUtilizationThreshold indicates the threshold configured to trigger this notification. DSP video pool resource usage (cdspCardVideoPoolUtilization) is updated and compared against the threshold (cdspCardVideoPoolUtilizationThreshold) in the events below: 1. A call that requires DSP video resource connects. 2. A call that requires DSP video resource disconnects. 3. DSPFarm profile for video resource is enabled. 4. DSPFarm profile for video resource is disabled. During comparison, if usage is larger than threshold, this notification is generated.
1.3.6.1.4.1.9.9.86.1.1.1.1.14
PercentAn integer that is in the range of a percent value. (0..100) · Integer32
The object indicates the percentage of current DSP video resource pool utilization of the card.
1.3.6.1.4.1.9.9.86.1.1.1.1.15
Unsigned32 (1..100)
This object specifies the threshold of DSP video pool resource usage. When cdspCardVideoPoolUtilization crosses the value of this threshold in the rising direction, cdspVideoUsageNotification is generated. If cdspCardVideoPoolUtilization stays above the value of this threshold, cdspVideoUsageNotification is generated whenever the value of cdspCardVideoPoolUtilization increases, but no notification is sent if when the value of cdspCardVideoPoolUtilization decreases. No notification is sent if cdspCardVideoPoolUtilization crosses the value of this threshold in the falling direction.
1.3.6.1.4.1.9.9.86.2.0.4
A cdspVideoOutOfResourceNotification is sent when there is not enough DSP resource in the video pool of the system for video services. cdspCardVideoPoolUtilization indicates the DSP video pool usage at the time this notification is sent. cdspCardVideoPoolUtilizationThreshold indicates the threshold configured to trigger this notification. DSP video resources required is computed for each incoming call that requires DSP video resources. If there is not enough video resource, this call will not have any video capabilities and is treated as audio-only; and this notification is generated.
1.3.6.1.4.1.9.9.86.1.1.1.1.14
PercentAn integer that is in the range of a percent value. (0..100) · Integer32
The object indicates the percentage of current DSP video resource pool utilization of the card.
1.3.6.1.4.1.9.9.86.1.1.1.1.15
Unsigned32 (1..100)
This object specifies the threshold of DSP video pool resource usage. When cdspCardVideoPoolUtilization crosses the value of this threshold in the rising direction, cdspVideoUsageNotification is generated. If cdspCardVideoPoolUtilization stays above the value of this threshold, cdspVideoUsageNotification is generated whenever the value of cdspCardVideoPoolUtilization increases, but no notification is sent if when the value of cdspCardVideoPoolUtilization decreases. No notification is sent if cdspCardVideoPoolUtilization crosses the value of this threshold in the falling direction.