ZHONE-COM-VOICE-DSP-MIB

OBJECT-IDENTITY

The MIB module to describe managed objects for Zhone's voice DSP applications. The Voice DSP MIB has the following components: * voiceDspDefaultConfiguration * voiceDspStatusTable * channelStatusTable * voiceDspTraps

OBJECT-IDENTITY

System-wide defaults for voice DSP variables. These values will be used by voice DSP to set up default values to be used per call.

OBJECT-TYPE

voice DSP redundancy over-subscription model. It is important to know the concept of active versus standby resources in order to understand how over- subscription works. For each call that is made on our equipment, resources are used. A resource is active if it is currently in use and it is standby if it is being held in case of the active's failure. If an active resourse fails, the standby can take over and the call continues. On the standby resources in a redundancy configuration can be oversubscribed. A service provider system administrator can configure a voice DSP system to use one of the following oversubscription models: * none: implies 1:1 (one to one) oversubscription. When a standby is allocated, the pool of available actives is depleted by one. * low: implies 1:2 oversubscription. * medium: implies 1:4 oversubscription. * high: implies infinite oversubscription. Active pool is never depleted when any standbys are allocated. If all active resources are used for real calls, no standby resources will be available to take over a failed call. The default value of this variable is high. This variable is supported only on BAN with VASP card(s).

OBJECT-TYPE

Voice DSP channel jitter buffer defaults. There are two types of jitter algorithms: static and dynamic. Dynamic allows the jitter buffer to grow and shrink as inter-arrival jitter changes. A static jitter buffer does not. Some examples of the voice connection types used for; Voice Over ATM (VoATM): pots-to-aal2, isdn-to-aal2, aal2-to-gr303, aal2-to-v52. Voice Over IP (VoIP) : sip-to-ds1, sip-to-gr303, sip-to-v52. Dynamic jitter buffer is not supported in VoATM case. Default jitter buffer type is static for VoATM, and dynamic for VoIP.

OBJECT-TYPE

Voice DSP jitter buffer size in milliseconds. More specifically, it refers to the amount of memory usage that can store certain milliseconds of voice. There are two types of jitter algorithms: static and dynamic. Dynamic allows the jitter buffer to grow and shrink as inter-arrival jitter changes. A static jitter buffer does not. When the jitterBufferType is dynamic, jitterBufferSize is the initial buffer size the jitter buffer can grow to. Some examples of the voice connection types used for; Voice Over ATM (VoATM): pots-to-aal2, isdn-to-aal2, aal2-to-gr303, aal2-to-v52. Voice Over IP (VoIP) : sip-to-ds1, sip-to-gr303, sip-to-v52. Valid range is 1 to 33 milliseconds for VoATM case. Valid range is 1 to 100 milliseconds for VoIP case. Default jitter buffer size is 10 milliseconds.

OBJECT-TYPE

The inter-arrival jitter threshold per channel used as a trigger value in milliseconds to generate a trap when its value is passed. If this value is 0, the threshold mointoring is disabled for inter-arrival jitter. Valid range is 0 to 100 milliseconds. The default value is 80 milliseconds. This variable is not supported.

OBJECT-TYPE

Voice DSP channel packets lost per minute threshold. A trap will be generated when this value is passed. If this value is 0, the threshold mointoring is disabled for packets lost. Valid range for this value is from 0 to 10000 pkts/ min. The default value is 600 pkts/min. This variable is not supported.

OBJECT-TYPE

This data informs which echo cancellation algorithm to be used by default: 165 or 168 for a particular channel. The numbers 165 and 168 are the ITU designations for the algorithms. The number following the designation describes the echo tail length in milliseconds. Both G.165 and G.168 are ITU-T recommendations. G.168 has slightly stricter technical specs. G.168 defines much better how the tests are performed. If an echo canceller passes the G.165 spec, then it is G.165 compliant. If it passes G.168, it is both G.168 and G.165 compliant. The echo tail length required depends on factors such as network configuration, local loop length, line frequency response, etc. Generally, 16 ms is more than adequate for local loop (ie. Zedge) and 32 ms is a good minimum for Network side. Our products currently support up to 48 ms of echo tail length, MALC supports 16 ms of echo tail length. Valid values for the variable are: * off - echo cancellation is off (on all platforms). * g165EchoTL16 - G.165 echo cancellation with echo tail length of 16ms (on MALC only). * g168EchoTL48 - G.168 echo cancellation with echo tail length of 48ms (on the other platforms, i.e.: BAN, Sechtor 100, Z-Edge64). Following values are not supported: * g165EchoTL32 - G.165 echo cancellation with echo tail length of 32ms. * g165EchoTL48 - G.165 echo cancellation with echo tail length of 48ms. * g168EchoTL32 - G.168 echo cancellation with echo tail length of 32ms. * g168EchoTL64 - G.168 echo cancellation with echo tail length of 64ms. * g168EchoTL80 - G.168 echo cancellation with echo tail length of 80ms. * g168EchoTL96 - G.168 echo cancellation with echo tail length of 96ms. * g168EchoTL112 - G.168 echo cancellation with echo tail length of 112ms. * g168EchoTL128 - G.168 echo cancellation with echo tail length of 128ms. The default value is g165EchoTL16 for MALC, and g168EchoTL48 for the other platforms.

OBJECT-TYPE

This data informs a voice DSP what type of silence suppression algorithm to use on a channel. Silence suppression is used to suppress packet generation during periods of silence of a voice call. The SID (silence descriptor) frame is generated at the start of a silence period, or periodically, and it is used to characterize the power level of the background noise during silence period on the encode side of the voice path. The SID frame is then passed to the decode side through the packet encoding medium (AAL2 or RTP). The decode side then generates comfort noise at an equivalent power level dictated by the SID frame values. Valid values for the variable are: * silSupOff - silence suppression is off. * silSupOnSidOn - send an SID frame at a specified constant interval (e.g. 100ms). Following values are not supported: * silSupOnSidOff - discontinue transmission during silence periods and no SID frame is sent. * silSupOnSidConst - send an initial SID frame and then discontinue transmission. Silence suppression is not supported on MALC. The default value is silSupOff.

OBJECT-TYPE

The amount of loss between the transmitted signal and the reflected echo back from the hybrid where the 4-to-2 wire conversion takes place. For MALC: 0dB and 6dB. 6dB is default. For all other platforms: 0dB, 3dB, 6dB. 3db is default.

OBJECT-TYPE

Current status information for the voice DSP application. This table gives a current view of how a voice DSP is doing since the voice DSP is started.

OBJECT-TYPE

An entry in the voiceDspStatusTable.

OBJECT-TYPE

Maximum number of channels a voice DSP can handle at the present time. The valid range for DSP boards we currently support is 0 to 1008.

OBJECT-TYPE

Number of channels currently active. The maximum value of this variable should not exceed voiceDspMaxChannelOnBoard.

OBJECT-TYPE

The highest channel count since this voice DSP has been running. The maximum value of this variable should not exceed voiceDspMaxChannelOnBoard.

OBJECT-TYPE

Number of slave DSP resets that have occurred within a voice DSP. A reset occurs when a slave DSP crashes. This counter is incremented each time voice DSP detects a slave DSP crash.

OBJECT-TYPE

This table gives a detailed snapshot view of all the voice calls the voice DSP is currently processing. Only the current active calls are reported in this table and there is no information about call sessions that are already terminated.

OBJECT-TYPE

An entry in the channelStatusTable.

OBJECT-TYPE

Logical channel id of a call. The valid range of this id is from 1 to 65536. At any single instance, there should at most one call with the same channel id but over time the same channel id can be used for different calls.

OBJECT-TYPE

The high 32 bits of the session number of a voice call. The session id is used to keep track all resources used by a call. Detailed call performance statistics can be supported in the future with session id uniquely identify each individual call. Voice session id is a unique 64 bit number and it will never be repeated.

OBJECT-TYPE

The low 32 bits of the session number of a voice call. The session id is used to keep track all resources used by a call. Detailed call performance statistics can be supported in the future with session id uniquely identify each individual call. Voice session id is a unique 64 bit number and it will never be repeated.

OBJECT-TYPE

The shelf where the Call Control Resource Provider (CCRP) resides. CCRP process acts as a gateway for call signaling between TDM equipment and the ATM AAL2 network. Range of valid values is 1-255. Note 0 is an invalid value.

OBJECT-TYPE

The slot where the Call Control Resource Provider (CCRP) resides. CCRP process acts as a gateway for call signaling between TDM equipment and the ATM AAL2 network. Range of valid values is 1-17. Note 0 is an invalid value.

OBJECT-TYPE

The shelf where the Trunk Call Temrination Resource Provider (TrunkCtrp) resides. TrunkCtrp is a proccess through which call signaling travels to and from TDM equipment. The CCRP above does not communicate directly with TDM; it does so through this CTRP. Range of valid values is 1-255. Note 0 is an invalid value.

OBJECT-TYPE

The slot where the Trunk Call Temrination Resource Provider (TrunkCtrp) resides. TrunkCtrp is a proccess through which call signaling travels to and from TDM equipment. The CCRP above does not communicate directly with TDM; it does so through this CTRP. Range of valid values is 1-17. Note 0 is an invalid value.

OBJECT-TYPE

The shelf where the Packet Call Temrination Resource Provider (PktCtrp) resides. PktCtrp is a proccess through which call signaling travels to and from ATM AAL2 network. Range of valid values is 1-255. Note 0 is an invalid value.

OBJECT-TYPE

The slot where the Packet Call Temrination Resource Provider (PktCtrp) resides. PktCtrp is a proccess through which call signaling travels to and from ATM AAL2 network. Range of valid values is 1-17. Note 0 is an invalid value.

OBJECT-TYPE

Types of voice codecs on the current call. G.711, G.726, G.729 and G.723 are ITU-T standards for voice and multimedia modulation and digital encoding. Valid values for this variable can be: * g711Ulaw - G.711 Ulaw coding standard at 64 kbps * g711Alaw - G.711 Alaw coding standard at 64 kbps * g726 - G.726 ADPCM coding stardards at 48/56/64 kbps * g729A - G.729 Annex A CS-ACELP coding standard at 8 kbps * g729B - G.729 Annex B CS-ACELP coding standard with silence suppressionat 8 kbps * g729E - G.729 Annex E CS-ACELP coding standard with silence suppressionat 11.8 kbps * g723R1KBPS5Dot3 - G.723.1 coding standard at 5.3 kbps * g723R1KBPS6Dot3 - G.723.1 coding standard at 6.3 kbps * g723R1AKBPS5Dot3 - G.723.1 Annex A coding standard at 5.3 kbps * g723R1AKBPS6Dot3 - G.723.1 Annex coding standard at 6.3 kbps

OBJECT-TYPE

This indicates how long this channel has been running in TimeTicks. A channel is considered alive when the call parties pick up the phone and data starts to flow and it is no longer alive when the phone is hung up. One TimeTick is one hundredth of a second.

OBJECT-TYPE

Number of packets transmitted.

OBJECT-TYPE

Number of bytes transmitted.

OBJECT-TYPE

Number of packets received.

OBJECT-TYPE

Number of bytes received.

OBJECT-TYPE

Number of packets lost.

OBJECT-TYPE

The inter arrival jitter in milliseconds.

OBJECT-TYPE

Size of jitter buffer in milliseconds. The jitter buffer is used to compensate for inter-arrival packet jitter. It is accomplished by keeping a buffer of packets to allow continuous playout of voice.

OBJECT-IDENTITY

All voice DSP related traps are defined under voiceDspTraps.

OBJECT-IDENTITY

prefix 0 for voiceDspTraps as required by SNMPv2.