G700-MG-MIB: View SNMP OID List / Download MIB

A MIB to support the Avaya H248 Media Gateways.

Indicates the type of component. Where 'media-gateway' refers to G700 Enumeration: 'g350': 2, 'avayaTRM480': 33, 'avayaG250-BRI': 4, 'media-gateway': 1, 'avayaCommunicationManagerBranchEditionG450': 35, 'avayaCommunicationManagerBranchEditioni40-A14': 34, 'avayaTGM550': 10, 'avayaG250-A14': 8, 'avayaG250-DS1': 5, 'avayaCommunicationManagerBranchEditioni120': 28, 'avayaG250': 3, 'avayaCommunicationManagerBranchEditioni40-DS1': 31, 'avayaG450': 7, 'avayaCommunicationManagerBranchEditioni40-DCP': 32, 'avayaCommunicationManagerBranchEditionG430': 37, 'avayaCommunicationManagerBranchEditioni40-BRI': 30, 'avayaG250-DCP': 6, 'avayaCommunicationManagerBranchEditioni40-Analog': 29, 'avayaG430': 41.

Model number of this component.

Description of this component: G700 Media Gateway.

Serial number of this gateway.

Hardware version of this gateway.

Hardware vintage suffix of this gateway.

Position of this media gateway in the Cajun stack, counting from the bottom of the stack.

List of the physical media modules installed in this gateway. Meaning of each octet is as follows. 1 Number of slots; in the G700 Media Gateway this is always 4. 2 Type of slot identifier; in the G700 Media Gateway this is always integer(2). 3-4 Length of each field in the following sequence; in the G700 Media Gateway this is always 1. 5-14 Module type ids in slot order, 1 - 10. Values are defined below for cmgModuleType, or none(0) if no module is installed. none(0), -- no module installed t1e1-voip(1), -- T1/E1 with integrated CSU/DSU & VoIP DSP bri(2), -- BRI trunk module dcp(3), -- DCP station module analog(4), -- combination analog line and trunk t1e1(5), -- T1/E1 with integrated CSU/DSU voip(6), -- dedicated VoIP media module icc(7), -- internal call controller fxo4fxs4(9), -- MM714 4 FXS + 4FXO analog ports module bri2(10), -- MM722 2 BRI trunk ports module ds1wan(11), -- MM340 1 DS1 (E1/T1) WAN data port module uspwan(12), -- MM342 1 USP WAN data port module dcp24hd(13), -- HDMM312 24 DCP station ports G350 high-density form-factor module poe24(14), -- HDMM314 24 power over Ethernet plus 1 GBIC port g350intana(16), -- G350 Integrated analog module dcp24(17), -- MM717 24 DCP station ports module fxs24(18), -- MM716 24 FXS analog ports module g250-int-analog-2L4T(19), -- G250 Integrated analog 2 Lines + 4 Trunks module g250-int-analog-2L1T(20), -- G250 Integrated analog 2 Lines + 1 Trunk module g250-int-BRI(21), -- G250 Integrated BRI Trunk module g250-int-DS1(24), -- G250 Integrated DS1 Trunk module g250-int-12pDCP(23), -- G250 Integrated 12 Port DCP lines module poe40(22), -- HDMM316 40 power over Ethernet plus 1 Giga bit copper poe24cr(25), -- HDMM314 24 power over Ethernet plus 1 GBIC port (Cost Reduction) poe8(26), -- MM118 - 8 10/100 power over Ethernet ports module tgm550-int-analog-2L2T(30), -- TGM550 Integrated analog 2 Lines + 2 Trunks module tim514(31), -- TIM514 4 FXS + 4 FXO analog ports module tim510(32), -- TIM510 1 DS1 (E1/T1) module tim521(33), -- TIM521 4 BRI trunk ports module avayaAM110ApplicationModule(34), -- Avaya Communication Manager Branch Edition Application Module for i40 and i120. g450Mainboard(40), -- G450 mainboard tim508(41), -- TIM508 8 FXS analog ports module tim516(42), -- TIM516 16 FXS analog ports module tim518(43), -- TIM518 8 FXS + 8 FXO analog ports module i120-intana(44), -- i120 Integrated analog module i40-int-analog-2L4T(45), -- avayaCommunicationManagerBranchEditioni40 Integrated analog 2 Lines + 4 Trunks module i40-int-analog-2L1T(46), -- avayaCommunicationManagerBranchEditioni40 Integrated analog 2 Lines + 1 Trunk module i40-int-BRI(47), -- avayaCommunicationManagerBranchEditioni40 Integrated BRI Trunk module i40-int-DS1(48), -- avayaCommunicationManagerBranchEditioni40 Integrated DS1 Trunk module i40-A14-int-analog-6L8T(49), -- avayaCommunicationManagerBranchEditioni40 Integrated analog 6 Lines + 8 Trunks module avayaCommunicationManagerBranchEditionG450Mainboard(50), -- Mainboard g430Mainboard(51), bri8(52), -- MM721 8 BRI trunk ports module unknown(255) -- type cannot be determined

Setting the value of this attribute to ON is interpreted as a reset command for the whole chassis. It initiates a complete reinitialisation of the chassis and of all the devices incorporated inside the chassis. Enumeration: 'on': 1, 'off': 2.

Reading of the internal temperature sensor at the CPU, expressed in degrees Celsius.

Internal enclosure temperature warning threshold, expressed in degrees Celsius. When the temperature at the CPU sensor exceeds the threshold, a trap is sent to the management console. If both CPU and DSP sensors exceed their thresholds, only one trap is sent.

Internal enclosure temperature shutdown threshold, expressed in degrees Celsius. When the temperature at the CPU sensor exceeds the threshold, a trap is sent to the management console and the media gateway begins a controlled shutdown.

Reading of the internal temperature sensor at the DSPs, expressed in degrees Celsius.

Internal enclosure temperature warning threshold, expressed in degrees Celsius. When the temperature at the DSP sensor exceeds the threshold, a trap is sent to the management console. If both CPU and DSP sensors exceed their thresholds, only one trap is sent.

Internal enclosure temperature shutdown threshold, expressed in degrees Celsius. When the temperature at the DSP sensor exceeds the threshold, a trap is sent to the management console and the media gateway begins a controlled shutdown.

Voltage reading in millivolts at the power supply serving the Media Gateway main processor. Nominal value is +5100 mV. If the reading falls outside the range 4950 to 5250 mV, a trap is sent to the management console and the corresponding bit in the fault mask is turned on.

Voltage reading in millivolts at the power supply serving the Media Modules. Nominal value is -48000 mV. If the reading falls outside the range -43000 to -53000 mV, a trap is sent to the management console and the corresponding bit in the fault mask is turned on.

Voltage reading in millivolts at the power supply serving the VoIP complexes. Nominal value is +3400 mV. If the reading falls outside the range 3200 to 3600 mV, a trap is sent to the management console and the corresponding bit in the fault mask is turned on.

Voltage reading in millivolts at the power supply serving the DSP units, derived from VoIP complex power. Nominal value is +1580 mV. If the reading falls outside the range 1530 to 1620 mV, a trap is sent to the management console and the corresponding bit in the fault mask is turned on.

Voltage reading in millivolts at the power supply serving the 8260 processor, derived from VoIP complex power. Nominal value is +2500 mV. If the reading falls outside the range 2430 to 2580 mV, a trap is sent to the management console and the corresponding bit in the fault mask is turned on.

Each bit of this value set to '1' indicates a specific fault in the module. Octets are numbered in the order in which they appear in the PDU. Bits are numbered from the most-significant leftmost bit in the octet (bit 0) to the least-significant rightmost bit (bit 7). Cajun numbering continues across octets, so that octet 1 bit 0 is called bit 8 in the Cajun scheme. That number is also shown below, with the octet value for each single bit set. Octet 0 high-order 4 bits show fan status. Octet 0 low-order 4 bits show temperature status. Octet 1 shows power supply status. Octet 2 shows other alarms. Cajun Octet Octet bit# /bit# value Meaning ----- ----- ----- ------- 0 0/0 0x80 Multiple fan warning: at least two fans have been operating at less than 90% of their nominal speed for 5 minutes or more. This may be an early warning of overheating. 1 0/1 0x40 PSU fan brief failure warning: the power supply fan has been operating at less than 90% of its nominal speed for 10 minutes or more, but less than 15 minutes. This may be an early warning of overheating. 2 0/2 0x20 PSU fan prolonged failure warning: the power supply fan has been operating at less than 90% of its nominal speed for 15 minutes or more. This may be an early warning of overheating. 3 0/3 Unused. 4 0/4 0x08 Temperature warning: cmgCpuTemp has exceeded its warning threshold. 5 0/5 0x04 Temperature warning: cmgDspTemp has exceeded its warning threshold. 6 0/6 Unused. 7 0/7 Power On Status Test failure -NCE, QUICC test failures on power up 8 1/0 0x80 The +5.1 v power supply to the MG processor is out of range. 9 1/1 0x40 The -48 v power supply to the media modules is out of range. 10 1/2 0x20 The +3.3 v power supply to the VoIP complexes is out of range. 11 1/3 0x10 The +1.58 v power supply to the DSP units is out of range. 12 1/4 0x08 The +2.5 v power supply to the 8260 processor is out of range. 13 1/5 0x04 The -48 v auxiliary power supply to the endpoints is out of range. 14 1/6 0x02 The +12 v power supply to the fans is out of range. 15 1/7 Unused. 16 2/0 0x80 Clock synchronization signal is lost. 17 2/1 0x40 Clock synchronization signal warning. Only one clock syncronization signal source remains. 18 2/2 0x20 Clock synchronization signal excessive switching. 19 2/3 0x10 TDM Test Expansion Box 1 Failure 20 2/4 0x08 TDM Test Expansion Box 2 Failure 21 2/5 0x04 PoE Power Supply Base Box Failure 22 2/6 0x02 PoE Power Supply Expansion Box 1 Failure 23 2/7 0x01 PoE Power Supply Expansion Box 2 Failure

Each bit of this value set to '1' indicates a specific status condition in the module. Octets are numbered in the order in which they appear in the PDU. Bits are numbered from the most-significant leftmost bit in the octet (bit 0) to the least-significant rightmost bit (bit 7). Cajun numbering continues across octets, so that octet 1 bit 0 is called bit 8 in the Cajun scheme. That number is also shown below, with the octet value for each single bit set. Octet 0 high-order 4 bits show LED status. Octet 0 low-order 4 bits show ICC status. Octets 1 - 5 show power-on self test (POST) results. Cajun Octet Octet bit# bit# value Meaning ----- ----- ----- ------- 0 0/0 0x80 Media gateway red LED is on. 1 0/1 0x40 The red LED is on in one or more of the media modules. 2-3 0/2-3 Unused. 4 0/4 0x08 Integrated Communications Controller hardware watchdog alert is on. 5-7 0/5-7 Unused. 8 1/0 0x80 POST HDLC local loopback failed. 9 1/1 0x40 POST Ethernet local loopback failed. 10 1/2 0x20 POST Ethernet physical local loopback failed. 11 1/3 0x10 POST Port I/O read-write test failed. 12-15 1/4-7 Unused. 16 2/0 0x80 POST NCE0 reset failed. 17 2/1 0x40 POST NCE0 internal RAM test failed. 18 2/2 0x20 POST NCE0 FIFO loop-around failed. 19 2/3 0x10 POST NCE0 internal channel loopback failed. 20 2/4 0x08 POST NCE0 internal TDM loopback failed. 21 2/5 0x04 POST NCE0 external channel loopback failed. 22-23 2/6-7 Unused. 24 3/0 0x80 POST NCE1 reset failed. 25 3/1 0x40 POST NCE1 internal RAM test failed. 26 3/2 0x20 POST NCE1 FIFO loop-around failed. 27 3/3 0x10 POST NCE1 internal channel loopback failed. 28 3/4 0x08 POST NCE1 internal TDM loopback failed. 29 3/5 0x04 POST NCE1 external channel loopback failed. 30-31 3/6-7 Unused. 32 4/0 0x80 POST DSP reset failed. 33 4/1 0x40 POST POST SPI internal loopback failed. 34 4/2 0x20 POST Spitfire FIFO test failed. 35 4/3 0x10 POST ADC test failed. 36 4/4 0x08 POST CPLD access test failed. 37-39 4/5-7 Unused. 40-47 5/0-7 Unused.

The fan speed level mode. Disable(2) is used for normal operation of two fan speeds. Enable(1) is used to activate additional lower speed level. Default is disable(2). Enumeration: 'enable': 1, 'disable': 2.

Table of physical media modules in this media gateway.

An entry in the table, representing a single media module.

Slot number of this module.

Type of this module. Enumeration: 'dcp24hd': 13, 'g430Mainboard': 51, 'voip': 6, 'i40-A14-int-analog-6L8T': 49, 't1e1': 5, 'g250-int-analog-2L4T': 19, 'invalid': 253, 'bri': 2, 'analog': 4, 'i40-int-analog-2L1T': 46, 'g450Mainboard': 40, 'tim521': 33, 'icc': 7, 'unknown': 255, 'g250-int-12pDCP': 23, 'fxo4fxs4': 9, 'i40-int-analog-2L4T': 45, 'fxs24': 18, 'tgm550-int-analog-2L2T': 30, 'dcp24': 17, 'g250-int-analog-6L8T': 29, 'tim508': 41, 'ds1wan': 11, 'poe40': 22, 't1e1-voip': 1, 'uspwan': 12, 'bri2': 10, 'g250-int-BRI': 21, 'g250-int-analog-2L1T': 20, 'i40-int-BRI': 47, 'avayaCommunicationManagerBranchEditionG450Mainboard': 50, 'avayaAM110ApplicationModule': 34, 'dcp': 3, 'poe24': 14, 'i120-intana': 44, 'i40-int-DS1': 48, 'g350intana': 16, 'poe24cr': 25, 'poe8': 26, 'tim518': 43, 'tim516': 42, 'tim514': 31, 'g250-int-DS1': 24, 'tim510': 32, 'bri8': 52.

Description of this media module, e.g. 'Avaya E1/T1 media module with integrated CSU/DSU'

User-assigned name of this media module.

Serial number of this module. The first 12 characters are meaningful. Form is yyLLmmnnnnnn, where yy = last 2 digits of the year of manufacture LL = manufacturing facility, e.g. DR for Denver, Colorado mm = month of manufacture, 01 - 12 nnnnnn = a six-digit sequence number

Hardware vintage of this module.

Hardware vintage suffix of this module.

Firmware version of this module. This duplicates information available in the Load MIB. It shows the media module run image version, plus the VoIP engine version if applicable.

Number of physical connectors on this module.

Each bit of this value set to '1' indicates a specific fault in the module. Octets are numbered in the order in which they appear in the PDU. Bits are numbered from the most-significant leftmost bit in the octet (bit 0) to the least-significant rightmost bit (bit 7). Cajun numbering continues across octets, so that octet 1 bit 0 is called bit 8 in the Cajun scheme. That number is also shown below, with the octet value for each single bit set. Cajun Octet Octet bit# bit# value Meaning ----- ----- ----- ------- 0 0/0 0x80 Media module is in administrative busy-out. 1 0/1 0x40 One or more ports on this media module is in administrative busy-out. 2 0/2 0x20 Insertion sequence failed. 3 0/3 AWOH data module conflict. 4 0/4 0x08 Media module automatic reset occurred. 5 0/5 0x04 One or more power-on startup tests failed. 6 0/6 0x02 Media module parameter exchange failed. 7 0/7 Unsupported module enrolment. 8-15 1/0-7 Unused.

Each bit of this value set to '1' indicates a specific status condition in the module. Octets are numbered in the order in which they appear in the PDU. Bits are numbered from the most-significant leftmost bit in the octet (bit 0) to the least-significant rightmost bit (bit 7). Cajun numbering continues across octets, so that octet 1 bit 0 is called bit 8 in the Cajun scheme. That number is also shown below, with the octet value for each single bit set. Cajun Octet Octet bit# bit# value Meaning ----- ----- ----- ------- 0 0/0 0x80 Red LED is on. 1 0/1 0x40 Module controlled by ACP on communications controller. 2-7 0/2-7 Unused. 8-15 1/0-7 Unused.

Setting the value of this attribute to ON is interpreted as a reset command for the module. It initiates a complete reinitialization of the module and of all the devices incorporated inside the module. Enumeration: 'on': 1, 'off': 2.

Number of communications channels or spans on this module. Earlier Avaya products have referred to T1E1 channels as ports. This media gateway calls them channels.

Configuration of E1/T1 DSUs in this media gateway.

An entry in the table, representing the configuration of one DSU on a T1/E1 media module.

Slot number of this DSU.

Port number of this DSU.

This object allows a user to take the E1/T1 port out of service for administration. During administration, it may be in an inconsistent state. When administration is complete, the port may be enabled again. If the port is not yet correctly administered, the change to the enabled state will fail with an INCONSISTENT_VALUE error. Enumeration: 'disabled': 2, 'enabled': 1.

Data format (channel rate) of this DSU. Enumeration: 'rate64KbpsClear': 2, 'rate56Kbps': 1.

Specifies the conditions under which this DSU will send all ones to indicate data port not ready. dtr-rts(1) Monitor both DTR and RTS as described below. If either is interrupted, send all ones. dtr(2) Monitor the DTE Ready interchange circuit CD (CCITT 108/1/2). If DTR is interrupted, send all ones. rts(3) Monitor the Request-to-Send interchange circuit CD (CCITT 105). If RTS is interrupted, send all ones. disable(4) Do not monitor interchange circuits from the DTE. Enumeration: 'dtr': 2, 'dtr-rts': 1, 'disable': 4, 'rts': 3.

Specifies the action to take when a yellow alarm is received on the network interface. noAction(1) Ignore yellow alarms. halt(2) Stop transmission and disable the data port. Send all ones on the Received Data interchange circuit BB (CCITT 104) and interrupt the Clear-to-Send interchange circuit (CCITT 106). Enumeration: 'halt': 2, 'noAction': 1.

Specifies whether data received from the data port is clocked using the DSU internal clock or by an external clock provided by the DTE connected to the port. When an external clock is used, it must be synchronized to the same clock source as the DSU. The DSU Receive Clock is equivalent to the Data Port Transmit Clock. internal(1) The clock is provided internally by the DSU/CSU on the TXC interchange circuit DB (CCITT 114). external(2) The clock is provided externally by the DTE on the XTXC interchange circuit DA (CCITT 113). Enumeration: 'internal': 1, 'external': 2.

Specifies whether the clock supplied by the DSU/CSU on the TXC interchange circuit DB (CCITT 114) is phase inverted with respect to the Transmitted Data interchange ciucuit BA (CCITT 103). This option is useful when long cable lengths between the DSU/CSU and the DTE are causing data errors. Enumeration: 'disabled': 2, 'enabled': 1.

Specifies whether the receive clock supplied by the DSU/CSU or DTE is phase inverted. Enumeration: 'disabled': 2, 'enabled': 1.

Specifies whether the transmitted data stream is logically inverted before being transmitted. This option is useful for applications where HDLC data is being transported. Inverting the data ensures that the density requirements for the network interface are met. Enumeration: 'disabled': 2, 'enabled': 1.

Specifies whether the received data stream is logically inverted. This option is useful for applications where HDLC data is being transported. Inverting the data ensures that the density requirements for the network interface are met. Enumeration: 'disabled': 2, 'enabled': 1.

Specifies whether the DSU should accept loopback requests from the DTE port. The local DTE can send an LL or RL signal to the T1/E1 media module in the EIA-530A interface. The LL signal causes the module to activate a local DTE loopback. An RL signal causes the module to send an in-band code to signal the far end to go into loopback. Enumeration: 'allow': 1, 'disallow': 2.

Specifies whether the DSU should accept in-band loopback requests from the far end, that is, a DSU across the network. Enumeration: 'allow': 1, 'disallow': 2.

Specifies which channels are assigned to Voice and which to the DSU. Each bit represents one channel. If the bit is set to 1, the channel is assigned to the DSU; otherwise it is assigned to Voice. The channel number of a bit is determined by the formula (8*n + b + 1), where n is the octet number and b is the bit number. So the 3rd bit in octet 2 represents channel (8*2 + 3 + 1) = 20.

Data format (channel rate) of this DSU times the number of channels of type ds0-dsu-channel(5). See cmgChType in cmgChannelTable.

Status of E1/T1 DSUs in this media gateway.

An entry in the table, representing the configuration of one DSU on a T1/E1 media module.

State of request-to-send signal from the DTE to the DSU. Enumeration: 'on': 1, 'off': 2.

State of data-terminal-ready signal from the DTE to the DSU. Enumeration: 'on': 1, 'off': 2.

Is there a DTE local loopback active between the DTE and the DSU? Enumeration: 'on': 1, 'off': 2.

Is there a remote loopback active in the FPGA? Enumeration: 'on': 1, 'off': 2.

State of the Receive Line Signal Detect from the DSU to the DTE. Enumeration: 'on': 1, 'off': 2.

State of clear-to-send signal from the DSU to the DTE. Enumeration: 'on': 1, 'off': 2.

State of data-set-ready signal from the DCE to the DTE. Enumeration: 'on': 1, 'off': 2.

State of the DCE ring indicator signal to the DTE. Enumeration: 'on': 1, 'off': 2.

Indicates whether tests are currently in progress. Enumeration: 'on': 1, 'off': 2.

State of data transmission from the synchronous DTE to the data port on the DSU. Enumeration: 'space': 2, 'cycling': 3, 'mark': 1.

State of data reception at the synchronous DTE from the data port on the DSU/CSU. Enumeration: 'space': 2, 'cycling': 3, 'mark': 1.

Each bit of this value set to '1' indicates a specific fault in this DSU. Octets are numbered in the order in which they appear in the PDU. Bits are numbered from the most-significant leftmost bit in the octet (bit 0) to the least-significant rightmost bit (bit 7). Cajun numbering continues across octets, so that octet 1 bit 0 is called bit 8 in the Cajun scheme. That number is also shown below, with the octet value for each single bit set. Cajun Octet Octet bit# bit# value Meaning ----- ----- ----- ------- 0 0/0 0x80 DSU FPGA configuration failure. 1 0/1 0x40 DSU automatic reset. 2-3 0/2-3 Unused. 4 0/4 0x08 DSU DTE DTR off - DTE is disconnected or not functioning. 5 0/5 0x04 DSU DTE RTS off - DTE is not sending data. 6 0/6 0x02 DSU TxD failure - data received from DTE is all zeroes or all ones. 7 0/7 0x01 DSU RxD failure - data received from far end is all zeroes or all ones. 8-15 1/0-7 Unused.

Each bit of this value set to '1' indicates a specific status condition in this DSU, or a fault or status condition in its associated CSU. Octets are numbered in the order in which they appear in the PDU. Bits are numbered from the most-significant leftmost bit in the octet (bit 0) to the least-significant rightmost bit (bit 7). Cajun numbering continues across octets, so that octet 1 bit 0 is called bit 8 in the Cajun scheme. That number is also shown below, with the octet value for each single bit set. If the CSU is reporting a Blue Alarm (AIS), multiple other alarms may be hidden by the Blue Alarm. -- The four octets of the T1E1 status mask are taken from three different -- maintenance APIs and assembled by the SNMP agent. Octets 0-1 show CSU fault status. -- From t1e1csu_status.mask, built by the macro T1E1CSU_STATUS_MKMASK. -- This is defined in CAPIStructures.h:851 and used in T1E1Csu.C:194. Octet 2 shows CSU loopbacks active. -- From t1e1csu_lpbkstatus.mask, built by the macro T1E1CSU_LPBKSTATUS_MKMASK. -- This is defined in CAPIStructures.h:803 and used in T1E1Csu.C:173. Octet 3 shows DSU loopbacks active. -- From t1e1dsu_tstmgmt.mask, built by the macro T1E1DSU_TSTMGMT_MKMASK -- This is defined in CAPIStructures.h:1115 and used in T1E1Dsu.C:1574. -- Note this just copies t1e1dsu_tstmgmt.status_lpbk into the mask field. -- Don't confuse t1e1dsu_tstmgmt.lpbk and t1e1dsu_tstmgmt.status_lpbk. The -- first is what a CLI user requested; the second is what the board reports. -- -- The bit assignments are chosen to facilitate retrieval from the board. Cajun Octet Octet bit# bit# value Meaning ----- ----- ----- ------- 0-5 0/0-5 Unused. 6 0/6 0x02 CSU CRC multiframe lost (LCM) - E1 only 7 0/7 0x01 CSU remote multiframe alignment lost (RMA) - E1 only 8 1/0 0x80 CSU local multiframe alignment lost (LMA) - E1 only 9 1/1 0x40 CSU polar density violations (PDV) - in the T1 configuration using AMI line coding, this is equivalent to bipolar violations (BPV). 10 1/2 0x20 CSU alarm indication signal (AIS, Blue Alarm). 11 1/3 0x10 CSU remote alarm indication signal (RAI, Yellow Alarm). 12 1/4 0x08 CSU loss of frame (LOF, Red Alarm) - unable to synchronize 13 1/5 0x04 CSU excessive error rate (EER) - applies to ESF framing only. on DS1 signal. 14 1/6 0x02 CSU out of frame (OOF) - 2 of 4 frame synchronization bits in error. 15 1/7 0x01 CSU loss of signal (LOS) - 175 consecutive zeroes received. 16-20 2/0-4 Unused. 21 2/5 0x04 CSU Digital diagnostic loopback active (towards DTE). This is the equivalent of either equipment (DTE) or repeater loopback in the Paradyne 3160. 22 2/6 0x02 CSU Line loopback active (towards network). 23 2/7 0x01 CSU Payload loopback active (towards network). 24-26 3/0-2 Unused. 27 3/3 0x10 DSU Far-end Data Channel loopback active. 28 3/4 0x08 DSU Data Terminal loopback active. 29 3/5 0x04 DSU Remote loopback active. 30 3/6 0x02 DSU Near-end Data Channel loopback active. 31 3/7 0x01 DSU Local DTE loopback active.

Loopback tests in effect on DSUs in this media gateway.

An entry in the table, representing the configuration of one DSU on a T1/E1 media module.

Specifies the pattern to be sent during a loopback test. allZeroes(1) is most often used to verify B8ZS line encoding. allOnes(2) is most often used to measure signal power. oneZeroOne(3) alternates ones and zeroes. It is most often used to test bridge taps. oneIn5(4) is the pattern '00001', to send a remote loopback request. oneIn8(5) is the pattern '00000001', used to test repeater timing recovery. threeIn24(6) is 21 zeroes followed by 3 ones, used to test the ones density tolerance in AMI coded lines. qrs(7) is a quasi-random signal approximating live data. It is also available in repeating patterns of 511 or 2047 bits. none means no pattern; used for response. Enumeration: 'none': 255, 'allOnes': 2, 'oneIn5': 4, 'allZeroes': 1, 'qrs511': 8, 'oneZeroOne': 3, 'threeIn24': 6, 'qrs': 7, 'qrs2047': 9, 'oneIn8': 5.

Indicates whether a Local DTE loopback is active, in which a signal received from the DTE is looped back after passing through the transceivers, but before passing through the FIFOs. This loopback can be activated by this DSU or by the local DTE. Enumeration: 'active': 1, 'inactive': 2.

Indicates whether a Near-end Data Channel loopback is active, in which a signal received from the CSU is looped back after passing through the FIFOs but before entering the transceivers. This loopback was activated by the near end, that is, this DSU. Enumeration: 'active': 1, 'inactive': 2.

Indicates whether a Far-end Data Channel loopback is active. This is functionally equivalent to the Near-end Data Channel loopback, except that this loopback was activated by the far end, that is, a DSU across the network. Enumeration: 'active': 1, 'inactive': 2.

Indicates whether a Remote loopback is active, in which a signal received from the CSU is looped back before entering the FIFOs. This loopback may have been activated by either the near end (this DSU) or the far end (a DSU across the network). Enumeration: 'active': 1, 'inactive': 2.

Indicates whether a Data Terminal loopback is active, in which a signal received from the DTE is looped back after passing through the FIFOs. This loopback can only be activated by the near end, that is, this DSU. Enumeration: 'active': 1, 'inactive': 2.

Set to on(1) to request reinitialization of the DSU. Enumeration: 'on': 1, 'off': 2.

Table of analog ports in this media gateway.

An entry in the table, representing a single analog port.

Slot number of this analog port.

Port number of this analog port.

The echo canceller control setting for this analog port. auto means that the system will enable or disable the echo canceller as appropriate for each call. fixedOn indicates that the analog firmware always enables the echo canceller (this value cannot be changed). Similarly, notSupported indicates that the analog HW does not contain echo cancellers (this value cannot be changed). Enumeration: 'auto': 0, 'notSupported': 4, 'off': 2, 'fixedOn': 3, 'on': 1.

Echo canceller configuration setting for this analog port (byte 1 of 2). This value is not writeable if cmgAnalogEchoCancellerControl is fixedOn(3) or notSupported(4).

Echo canceller configuration setting for this analog port (byte 2 of 2). This value is not writeable if cmgAnalogEchoCancellerControl is fixedOn(3) or notSupported(4).

Balance index.

The receive gain multiplied by 100, for instance -123 indicates -1.23dB.

The transmit gain multiplied by 100, for instance +287 indicates 2.87dB.

Table of Expansion Units connected to this media gateway.

An entry in the table, representing a single Expansion Unit.

Expansion Unit Slot.

Expansion Unit model.

Expansion Unit description.

Expansion Unit serial number.

Expansion Unit HW vintage.

Expansion Unit HW suffix.

When set to on(1), activates on demand test for the Expansion Unit. Enumeration: 'on': 1, 'off': 2.

Result of the on demand test for the Expansion Unit. Failure(1) may be the result of a disconnected or bad cable. Enumeration: 'fail': 1, 'pass': 255.

Timeslot Monitoring flag. When on, timeslot usage is monitored and traps are sent when thresholds are crossed. Those traps are cmgTimeslotOccupancyFault, cmgTimeslotOccupancyClear, cmgTimeslotAvailabilityFault and cmgTimeslotAvailabilityClear. Enumeration: 'on': 1, 'off': 2.

Timeslot Upper threshold. The gateway will send trap cmgTimeslotOccupancyFault as soon as the timeslot usage goes above this threshold. This threshold must be set greater than the lower threshold; for example, cmgTimeslotLowerThreshold=85, cmgTimeslotUpperThreshold=90. Default is 90. cmgTimeslotMonitoring must be set to on(1) for traps to be sent.

Timeslot Lower threshold. After the gateway has sent a cmgTimeslotOccupancyFault trap, it will send a cmgTimeslotOccupancyClear as soon as the timeslot usage goes below this threshold. Also after the gateway has sent a cmgTimeslotAvailabilityFault trap, it will send cmgTimeslotAvailabilityClear as soon as the timeslot usage goes below this threshold. This lower threshold must be less than the upper threshold; for example cmgTimeslotLowerThreshold=85, cmgTimeslotUpperThreshold=90. Default is 85. cmgTimeslotMonitoring must be set to on(1) for traps to be sent.

Media gateway number by which the Call Controller knows this media module.

MAC address of this processor.

Firmware version of this gateway.

Current IP address of this processor. If cmgUseDhcpForIpAddress was on(1) at the time of last startup, this was received from the DHCP server. Otherwise it is the value of cmgStaticIpAddress at the last startup. If cmgUseDhcpForIpAddress was on(1) and the DHCP request failed, this value will be '0.0.0.0'.

Specifies whether the gateway should get its IP address, default gateway, and subnet mask from the DHCP server, or use the locally administered static IP address, default gateway, and subnet mask. Enumeration: 'on': 1, 'off': 2.

Specifies whether the gateway should get its VLAN ID from the DHCP server, or use the locally administered static VLAN ID cmgStatic802Vlan. Enumeration: 'on': 1, 'off': 2.

Specifies the DHCP Site-Specific Option Number to use with a DHCP request. This gives the DHCP server information about the client's capabilities and properties.

Locally administered static IP address of this processor. If cmgUseDhcpForIpAddress is on(1), this object is ignored.

Comma-separated list of DNS server IP addresses this processor may use.

DNS Hostname of this processor.

Each bit of this value set to '1' indicates a specific fault in the Media Gateway processor. Octets are numbered in the order in which they appear in the PDU. Bits are numbered from the most-significant leftmost bit in the octet (bit 0) to the least-significant rightmost bit (bit 7). Cajun numbering continues across octets, so that octet 1 bit 0 is called bit 8 in the Cajun scheme. That number is also shown below, with the octet value for each single bit set. Cajun Octet Octet bit# bit# value Meaning ----- ----- ----- ------- 0 0/0 0x80 Memory failure. 1 0/1 0x40 DHCP request failure. 2 0/2 0x20 Firmware download failure. 3 0/3 0x10 Software watchdog alert - MG processes restarting. 4 0/4 0x08 Internal Communications Controller expected but not present. 5 0/5 0x04 Internal Communications Controller automatic reset. 6 0/6 0x02 Media Gateway busy-out. 7 0/7 0x01 Configuration upload failure. 8 1/0 0x80 Primary controller not found. 9 1/1 0x40 No controller found. 10 1/2 0x20 Registration failure. 11 1/3 0x10 H.248 control link down. 12-13 1/4-5 Unused. 14 1/6 0x02 Maintenance test failure. 15 1/7 0x01 Maintenance test failure over threshold. 16 2/0 0x80 Configuration download failure. 17-23 2/0-7 Unused.

Current IPv6 address type of this processor. The processor can have two IP address one IPv4 and the second IPv6. cmgCurrentIpAddress presents the IPv4 address and this MIB item presents the IPv6 address.

The Inet Address of the processor. 1. The address type of this object is specified in cmgCurrentInetAddressType. 2. Default of cmgCurrentInetAddressType is unknown(0) and cmgCurrentInetAddress is zero length.

Specifies whether this processor should use the locally administered Quality of Service parameters, or whether it should use the parameters downloaded from the controller. This affects both signaling and voice traffic. Enumeration: 'remote': 2, 'local': 1.

DiffServ Code Point for signaling traffic on the H.248 link, received from the controller. If cmgQosControl is local(1), this value is ignored.

802.1 Priority for signaling traffic on the H.248 link, received from the controller. If cmgQosControl is local(1), this value is ignored.

DiffServ Code Point for signaling traffic on the H.248 link, locally administered. If cmgQosControl is remote(2), this value is ignored.

802.1 Priority for signaling traffic on the H.248 link, locally administered. If cmgQosControl is remote(2), this value is ignored.

802.1 VLAN ID for this processor, locally administered. If cmgUseDhcpForVlan is on(1), this value is ignored.

802.1 VLAN ID currently in use for this processor. If cmgUseDhcpForVlan was on(1) at the last startup, this came from the DHCP server. Otherwise it is equal to cmgStatic802Vlan at the time of the last startup.

Primary clock source configured for this processor. If a T1 or BRI module is providing the clock, it reads 'Vs' or 'Vs(pp,pp,...)', where s is slot number and pp are the port numbers. If the VoIP module is providing the clock, it reads 'voip'. It reads 'None' if no primary clock source is configured. If cmgClockSourceControl is remote(2), access is read-only. If cmgClockSourceControl is local(1), access is read-write.

Secondary clock source configured for this processor. If a T1 or BRI module is providing the clock, it reads 'Vs' or 'Vs(pp,pp,...)', where s is slot number and pp are the port numbers. If the VoIP module is providing the clock, it reads 'voip'. It reads 'None' if no secondary clock source is configured. If cmgClockSourceControl is remote(2), access is read-only. If cmgClockSourceControl is local(1), access is read-write.

Identifies the clock source in use at this processor. If cmgClockSourceControl is remote(2), access is read-only. If cmgClockSourceControl is local(1), access is read-write. Enumeration: 'local': 3, 'primary': 1, 'secondary': 2.

A flag to enable/disable sync switching. If cmgClockSourceControl is remote(2), access is read-only. If cmgClockSourceControl is local(1), access is read-write. Enumeration: 'disabled': 2, 'enabled': 1.

Specifies whether this processor sync administration parameters are controlled locally or remotely. Enumeration: 'remote': 2, 'local': 1.

Shows whether this media gateway is currently registered with any call controller. Enumeration: 'registered': 1, 'notRegistered': 2.

IPv4 Address of the call controller now serving this media gateway. If cmgRegistrationState is notRegistered(2), this will be '0.0.0.0'. If cmgRegistrationState is registered(1) and the controller IP address is IPv6 address, this will be '0.0.0.0'. Otherwise it will be taken from one of the two address lists at registration time.

Status of the H.248 link connecting this media gateway to its active call controller. Enumeration: 'down': 2, 'up': 1.

Most recently received H.248 error code affecting the link between this media gateway and its active call controller. If cmgH248LinkStatus is up(1), this value will be zero. 0 No error 400 Syntax error in message 403 Syntax error in TransactionRequest 406 Version not supported 410 Incorrect identifier 411 The transaction refers to an unknown ContextId 412 No ContextIDs available 421 Unknown action or illegal combination of actions 422 Syntax error in action 430 Unknown TerminationID 431 No TerminationID matched a wildcard 432 Out of TerminationIDs or No TerminationID available 433 TerminationID is already in a Context 434 Max number of Terminations in a Context exceeded 440 Unsupported or unknown package 441 Missing remote or local descriptor 442 Syntax error in command 443 Unknown command 444 Unsupported or unknown descriptor 445 Unsupported property 446 Unsupported or unknown parameter 447 Descriptor not legal in this command 448 Descriptor appears twice in a command 450 No such property in this package 451 No such event in this package 452 No such signal in this package 453 No such statistic in this package 454 No such parameter value in this package 455 Parameter illegal in this descriptor 456 Parameter or property appears twice in this descriptor 457 Missing parameter in signal or event 471 Implied add for multiplex failure 500 Internal software failure in the media gateway 501 Not implemented 502 Not ready 503 Service unavailable 504 Command received from unauthorized entity 505 Transaction Request received before ServiceChange Reply received 510 Insufficient resources 512 Gateway unequipped to detect requested event 513 Gateway unequipped to generate requested signal 514 Gateway cannot send the specified announcement 515 Unsupported media type 517 Unsupported or invalid mode 518 Event buffer full 519 Out of space to store digit map 520 Digit map undefined in MG 521 Termination is 'Service Changing' 526 Insufficient bandwidth 529 Internal hardware failure in MG 530 Temporary network failure 531 Permanent network failure 581 Does not exist

Should this gateway get its controller IP address from the DHCP server, or should it use the locally administered controller list? If this value is on(1), the gateway will try the DHCP-provided addresses first, and if they fail it will try the static addresses. If the value is off(2), the gateway will try only static addresses. Changes to this object take effect when the gateway is restarted. Enumeration: 'on': 1, 'off': 2.

Comma-separated list of up to four administered static IPv4 and IPv6 addresses for primary and backup call controllers. IPv4 addresses should be in the form '123.124.125.126', with no port numbers. (The Media Gateway always uses the default H.248 port number 2945). IPv6 address should be in the form of '2002:8740:64e2::8740:64e2'. Use '+' if there is both IPv4 and IPv6 address on the same index/location. An IP address may appear more than once in the list. If cmgUseDhcpForMgcList is equal to off(2), these are the only addresses the gateway will try. In that case this list must contain at least one active entry. Changes to the list take effect when the gateway is restarted. Example for IPv4 and IPv6 address configuration: '135.6.8.98+2001:db8::370:7334, 135.6.8.99, 2001:db8::1428:57ab'

List of IP addresses for up to four primary and backup call controllers, received from the DHCP server. An IP address may appear more than once in the list. If cmgUseDhcpForMgcList is equal to on(2), the gateway will try these addresses first, and if none succeed, it will try the addresses in cmgStaticControllerHosts.

Number of minutes for the Primary Search Timer.

Number of minutes for the Total Search Timer.

Value of the Transition Point.

Release string of the call controller now serving this media gateway. Release string should be in format 'R015x.02.0.947.0' without patch information. If cmgRegistrationState is notRegistered(2) or this information is unknown to the agent, then this object will contain a zero-length string. Changes to the value take effect when the gateway is registered or re-registered.

IPv4/IPv6 Address of the call controller now serving this media gateway. If cmgRegistrationState is notRegistered(2), this will be unknown(0). cmgActiveControllerAddress will present IPv4 address controller only.

The Inet Address of the controller that the gateway is registered to. 1. The address type of this object is specified in cmgActiveControllerInetAddressType. 2. Default of cmgActiveControllerInetAddressType is unknown(0) and cmgActiveControllerInetAddress is zero length.

Determines whether VoIP engines use their statically administered IP addresses or whether they get their addresses from the DHCP server. Enumeration: 'on': 1, 'off': 2.

This is the same as cmgQosControl in the MG Processor group. That parameter determines whether the gateway uses voice and signaling QoS parameters administered locally or whether it gets the parameters from its call controller. It is reproduced here for convenience. Enumeration: 'remote': 2, 'local': 1.

The Better-than-Best-Effort DiffServ code point received from the controller. This is a value to be assigned to the code point part of the Differentiated Services field in the IP header of each voice packet. See RFC2475 for a full description of Differentiated Services.

The Expedited-Forwarding DiffServ code point received from the controller. This is a value to be assigned to the code point part of the Differentiated Services field in the IP header of each voice packet. See RFC2475 for a full description of Differentiated Services.

The 802.1 priority received from the call controller. This is a priority value to be assigned to the tag header for priority-tagged voice frames. See IEEE standard 802.1Q-1998 for a full description.

The lower end of the range of UDP ports assigned to voice traffic, received from the call controller. Must be less than or equal to cmgVoipRemoteMaxRtpPort.

The upper end of the range of UDP ports assigned to voice traffic, received from the call controller. Must be greater than or equal to cmgVoipRemoteMinRtpPort.

A flag that determines whether the Media Gateway will collect and report RTCP statistics. See RFC 1889 for a full description of RTCP. If this value is disabled(2), the rest of this group will be ignored. Enumeration: 'disabled': 2, 'enabled': 1.

The IPv4 address of an RTCP monitor to which the Media Gateway should report its RTCP statistics. cmgVoipRemoteRtcpMonitorIpAddress will present 0.0.0.0 if no IP address was configured or IPv6 address configured.

The port on the RTCP monitor to which the Media Gateway should report its RTCP statistics.

The RTCP reporting interval in seconds.

The IPv6 address type of an RTCP monitor to which the Media Gateway should report its RTCP statistics. User can define sending RTCP monitor packets to IPv4 host and IPv6 host. This mib item is used for IPv6 host, while cmgVoipRemoteRtcpMonitorIpAddress is used for the IPv4 host. cmgVoipRemoteRtcpMonitorIpAddress will present IPv4 address controller only.

The IPv6 address of an RTCP monitor to which the Media Gateway should report its RTCP statistics. 1. The address type of this object is specified in cmgVoipRemoteRtcpMonitorInetAddressType. 2. Default of cmgVoipRemoteRtcpMonitorInetAddressType is unknown(0) and cmgVoipRemoteRtcpMonitorInetAddress is zero length.

The port on the IPv6 RTCP monitor to which the Media Gateway should report its RTCP statistics.

A flag that determines whether the VoIP engines should use RSVP to control call admission. See RFC 2205 for a full description of RSVP. If this value is disabled(2), the rest of this group will be ignored. Enumeration: 'disabled': 2, 'enabled': 1.

A flag that determines whether the VoIP engines should retry a reservation request after the first one fails. If this value is disabled(2), the next object will be ignored. Enumeration: 'disabled': 2, 'enabled': 1.

The interval in seconds between a reservation request failure and the subsequent retry. If cmgVoipRemoteRetryOnFailure is disabled(2), this object will be ignored.

The RSVP service model to request. Enumeration: 'guaranteedService': 1, 'controlledLoadService': 2.

The Better-than-Best-Effort DiffServ code point received from the controller. This is a value to be assigned to the code point part of the Differentiated Services field in the IP header of each voice packet. See RFC2475 for a full description of Differentiated Services.

The Expedited-Forwarding DiffServ code point received from the controller. This is a value to be assigned to the code point part of the Differentiated Services field in the IP header of each voice packet. See RFC2475 for a full description of Differentiated Services.

The 802.1 priority received from the call controller. This is a priority value to be assigned to the tag header for priority-tagged voice frames. See IEEE standard 802.1Q-1998 for a full description.

The lower end of the range of UDP ports assigned to voice traffic, received from the call controller. Must be less than or equal to cmgVoipLocalMaxRtpPort.

The upper end of the range of UDP ports assigned to voice traffic, received from the call controller. Must be greater than or equal to cmgVoipLocalMinRtpPort.

A flag that determines whether the Media Gateway will collect and report RTCP statistics. See RFC 1889 for a full description of RTCP. If this value is disabled(2), the rest of this group will be ignored. Enumeration: 'disabled': 2, 'enabled': 1.

The IPv4 address of an RTCP monitor to which the Media Gateway should report its RTCP statistics. cmgVoipLocalRtcpMonitorIpAddress will present 0.0.0.0 if no IP address was configured or IPv6 address configured.

The port on the RTCP monitor to which the Media Gateway should report its RTCP statistics.

The RTCP reporting interval in seconds.

The IPv6 address type of an RTCP monitor to which the Media Gateway should report its RTCP statistics. User can define sending RTCP monitor packets to IPv4 host and IPv6 host. This mib item is used for IPv6 host, while cmgVoipLocalRtcpMonitorIpAddress is used for the IPv4 host. cmgVoipLocalRtcpMonitorIpAddress will present IPv4 address controller only.

The IPv6 address of an RTCP monitor to which the Media Gateway should report its RTCP statistics. 1. The address type of this object is specified in cmgVoipLocalRtcpMonitorInetAddressType. 2. Default of cmgVoipLocalRtcpMonitorInetAddressType is unknown(0) and cmgVoipLocalRtcpMonitorInetAddress is zero length.

The port on the IPv6 RTCP monitor to which the Media Gateway should report its RTCP statistics.

A flag that determines whether the VoIP engines should use RSVP to control call admission. See RFC 2205 for a full description of RSVP. If this value is disabled(2), the rest of this group will be ignored. Enumeration: 'disabled': 2, 'enabled': 1.

A flag that determines whether the VoIP engines should retry a reservation request after the first one fails. If this value is disabled(2), the next object will be ignored. Enumeration: 'disabled': 2, 'enabled': 1.

The interval in seconds between a reservation request failure and the subsequent retry. If cmgVoipLocalRetryOnFailure is disabled(2), this object will be ignored.

The RSVP service model to request. Enumeration: 'guaranteedService': 1, 'controlledLoadService': 2.

Table of VoIP engines in the media gateway.

An entry in the table representing one VoIP engine.

Location of this VoIP engine, either a media module slot (1-4 for G700) or the motherboard (100 for G700, 10 for G350, G250). For G450/G430 the index arrangement is as follows: * For V1 - V10 the rule is cmgVoIPSlot = Slot# * 10 + SoDIMM#. Note that MM760 is not supported in G430/G450, nor other MM which support VoIP engine. Thus, only V10 is relevant. * For G450 motherboard is 101-104. * For G430 motherboard is 101-102 (101 is the on board DSP and 102 is the replaceable VoIP SoDIMM module.

MAC address of the component hosting this VoIP engine.

Administered static IPv4 Address of this VoIP engine. If cmgVoipEngineUseDhcp was off(2) at startup time, this value determined the current IPv4 address of the engine.

IPv4 Address currently in use at this VoIP engine. If cmgVoipEngineUseDhcp was on(2) at startup time, this value was received from the DHCP server. Otherwise it is equal to cmgVoipStaticIpAddress at startup time.

Size in bytes of the dynamic jitter buffer at this VoIP engine.

Total channels available to this VoIP engine.

Number of channels in use at this VoIP engine.

5-minute average occupancy of this VoIP engine.

Indicates whether hyperactivity has been detected by this VoIP engine. Enumeration: 'unknown': 255, 'hyperactive': 2, 'normal': 1.

Maintenance busy-out state of this VoIP engine. Enumeration: 'release': 2, 'camp-on': 3, 'busy-out': 1, 'unknown': 255.

Firmware version of the DSP complex on this VoIP engine. This is also available in the Load MIB.

Status of the DSP complex on this VoIP engine. Enumeration: 'fault': 3, 'idle': 1, 'inUse': 2.

Setting the value of this attribute to ON is interpreted as a reset command for the VoIP engine. It initiates a complete reinitialisation of the VoIP engine. Enumeration: 'on': 1, 'off': 2.

Each bit of this value set to '1' indicates a specific fault in the VoIP engine. Octets are numbered in the order in which they appear in the PDU. Bits are numbered from the most-significant leftmost bit in the octet (bit 0) to the least-significant rightmost bit (bit 7). Cajun numbering continues across octets, so that octet 1 bit 0 is called bit 8 in the Cajun scheme. That number is also shown below, with the octet value for each single bit set. Cajun Octet Octet bit# bit# value Meaning ----- ----- ----- ------- 0 0/0 0x80 Occupancy above threshold, based on a snapshot of cmgVoipChannelsInUse divided by cmgVoipTotalChannels. 1 0/1 0x40 Occupancy above threshold, based on cmgVoipAverageOccupancy. 2 0/2 0x20 VoIP engine automatic reset. 3 0/3 0x10 VoIP hardware fault. 4 0/4 0x08 VoIP IP configuration fault. 5 0/5 0x04 VoIP DSP Failure 6 0/6 0x02 VoIP DSP CORE Failure 7 0/7 0x01 VoIP DSP FPGA Failure 8 1/0 0x80 Unsupported DSP module. 9--15 1/1-7 Unused

Administered static IPv6 Address Type of the VoIP engine. The VoIP Engine Processor can have two IP addresses: one IPv4 and the second IPv6. cmgVoipStaticIpAddress presents the IPv4 address and this MIB item presents the IPv6 address.

Administered static IPv6 Address of the VoIP engine. 1. The address type of this object is specified in cmgVoipStaticInetAddressType. 2. Default of cmgVoipStaticInetAddressType is unknown(0) and cmgVoipStaticInetAddress is zero length.

IPv6 Address Type currently in use at this VoIP engine. The VoIP Engine Processor can have two IP address one IPv4 and the second IPv6. cmgVoipCurrentIpAddress presents the IPv4 address and this MIB item presents the IPv6 address.

IPv6 Address currently in use at this VoIP engine. 1. The address type of this object is specified in cmgVoipCurrentInetAddressType. 2. Default of cmgVoipCurrentInetAddressType is unknown(0) and cmgVoipCurrentInetAddress is zero length.

Table representing the DSP cores in VoIP engine of the media gateway.

An entry in the table representing one DSP Core of a VoIP engine. This table uses an external index from cmgVoIPEngineTable which selects a DSP SoDIMM/engine module and secondary index cmgDSPVoIPCoreID that selects a core on SoDIMM module

The DSP core ID within the specific DSP VoIP engine.

Total channels available to this DSP core.

Number of channels in use at this DSP core.

Maintenance busy-out state of this DSP core. Enumeration: 'release': 2, 'camp-on': 3, 'busy-out': 1, 'unknown': 255.

Status of the DSP Core. Enumeration: 'fault': 3, 'idle': 1, 'inUse': 2.

Activates on demand test for the DSP Core. Enumeration: 'on': 1, 'off': 2.

Result of the on demand test for the DSP Core. Enumeration: 'pass': 255, 'notResponding': 7, 'errorCode1': 1, 'errorCode3': 3, 'errorCode2': 2, 'errorCode5': 5, 'errorCode4': 4, 'errorCode6': 6.

The echo canceller control setting for all VoIP engines. auto means that the system will enable or disable the echo cancellers as appropriate for each call. fixedOn indicates that the VoIP firmware always enables the echo cancellers (this value cannot be changed). Enumeration: 'auto': 0, 'off': 2, 'fixedOn': 3, 'on': 1.

Echo canceller configuration setting for all VoIP engines (byte 1 of 2). This value may not be writable if the VoIP firmware is old.

Echo canceller configuration setting for all VoIP engines (byte 2 of 2). This value may not be writable if the VoIP firmware is old.

Total channels enforced by Communications Manager.

Table of trap receivers in this media gateway.

An entry in the table, representing a single trap receiver.

IP address of this trap receiver.

Specifies whether this trap receiver is currently receiving traps. Enumeration: 'active': 1, 'inactive': 2.

A bit mask indicating the trap categories of interest to this trap receiver. Bit Category 0 Power warnings 1 Fan and temperature warnings 2 Application faults 3 Module insert or remove 4 Configuration traps: port enable or disable, administrative busy-out and release for ports and media modules 5-7 Not supported 8 Voice faults: Quality of service problems, voice hardware faults 9 Normal operations: successful registration with the gateway controller, successful firmware download. 10-31 Not supported

The status of this entry in the table. Available states: active(1), -- Trap receiver is administered, though not -- necessarily active. createAndGo(4), -- Used to add a new receiver to the table. destroy(6) -- Used to delete a receiver from the table. The cmgTrapManagerAddress of a new entry must be different from all other entries, or the create request will return INCONSISTENT-VALUE-ERROR.

Location of the problem in the form gggVspp, where ggg Media gateway number, or zero if the gateway is not currently registered with any controller. V The letter V; a field separator. s Slot number, if applicable. If the fault occurred on the media gateway processor, this will be omitted. pp Port number, if applicable. If the fault occurred on the media gateway processor or on a media module as a whole, this will be omitted.

Expected values are 'no' and 'yes'. If a problem is on-board, replacing the media module is likely to resolve the problem.

The high-level subsystem that generated the trap. Expected values are 'HW', 'SW', and 'Net'.

Should the media gateway send a trap on startup if there is no integrated communications controller in slot 1? Enumeration: 'yes': 2, 'no': 1.

A display string to identify the module type in module insert and remove traps.

The severity of the notification.

The Product Id of Avaya Device - 10 characters.

Number of Timeslots available on this gateway.

Number of Timeslots in use on this gateway.

The type of FIPS error. Enumeration: 'cryptoTestError': 1, 'prngFailure': 2, 'hashIntegrity': 3.

At least two fans have been operating at less than 90% of their nominal speed for five minutes or more. This may be an early warning of overheating.

At least three fans are operating normally. The system should be operable indefinitely without overheating.

The power supply fan has been operating at less than 90% of its optimal speed for 10 minutes or more, but less than 15 minutes. This may be an early warning of overheating.

The power supply fan is operating normally.

The power supply fan has been operating at less than 90% of its optimal speed for 15 minutes or more. This may be an early warning of overheating.

The power supply fan is operating normally.

The temperature sensor at the CPU has exceeded its warning threshold.

The temperature sensor at the CPU has dropped below its warning threshold.

The temperature sensor at the DSP complex has exceeded its warning threshold.

The temperature sensor at the DSP complex has dropped below its warning threshold.

The CPU temperature sensor has exceeded its shutdown threshold. The system is about to begin controlled shutdown.

The voltage reading at the +5.1v power source serving the MG Processor is out of tolerance.

The voltage reading at the +5.1v power source serving the MG Processor is back within its tolerance range.

The voltage reading at the -48v power source serving the media modules is out of tolerance.

The voltage reading at the -48v power source serving the media modules is back within its tolerance range.

The voltage reading at the +3.4v power source serving the VoIP complexes is out of tolerance.

The voltage reading at the +3.4v power source serving the VoIP complexes is back within its tolerance range.

The voltage reading at the +1.58v power source serving the DSP units is out of tolerance.

The voltage reading at the +1.58v power source serving the DSP units is back within its tolerance range.

The voltage reading at the +2.5v power source serving the 8260 processor is out of tolerance.

The voltage reading at the +2.5v power source serving the 8260 processor is back within its tolerance range.

The voltage reading at the -48v auxiliary power source serving the end points is out of tolerance.

The voltage reading at the -48v auxiliary power source serving the end points is back within its tolerance range.

The voltage at the +12 auxiliary power source serving the fans is out of tolerance.

The voltage at the +12 auxiliary power source serving the fans is back within its tolerance range.

Synchronization signal lost.

Synchronization signal normal.

One or more of the DSP complexes serving VoIP engines has failed.

All the DSP complexes serving VoIP engines are back in service.

Synchronization signal lost.

Synchronization signal normal.

The synchronization signal source (primary or secondary) is experiencing excessive failures in a short period of time causing excessive switching to an alternate source.

Synchronization signal source which was causing excessive switching due to excessive failures is now normal.

One or more of the DSP Cores serving VoIP engines has failed.

All the DSP Cores serving VoIP engines are back in service.

A media module has been removed.

Media module insertion sequence has failed.

A media module has been inserted.

An administrator has moved a media module or port to the busy-out state.

An administrator has moved a media module or port from the busy-out state back into service.

The event is sent when a module is inserted to a slot where it can be identified but not supported due to hardware limitations.

This event is generated when a data module is found in a slot that was Administered without hardware as a voice module in the call controller.

The media gateway has begun download of a software module.

The media gateway has completed successful download of a software module.

The media gateway has successfully registered with a controller.

The media gateway is beginning a user-requested reset operation.

A media module is beginning a user-requested reset operation.

A VoIP engine is beginning a user-requested reset operation.

An E1/T1 DSU is beginning a user-requested reset operation.

The media gateway has begun upload of a configuration file.

The media gateway has completed successful upload of a configuration file.

Main processor memory has issued a failure warning.

Main processor memory is back in normal service.

The media gateway cannot contact its DHCP server, or the server failed to respond to a request.

The media gateway has received a successful response to a DHCP request.

An attempt to download a software module has failed.

One or more media gateway software processes have terminated and been restarted by the software task manager.

Media gateway software processes are running normally.

An Internal Communications Controller expected in slot 1 is missing.

The Internal Communications Controller expected in slot 1 is present.

The Media gateway has automatically reset the Internal Communications Controller.

The Internal Communications Controller is running normally.

The media gateway cannot contact the first controller in its controller list.

The media gateway has successfully contacted the first controller in its controller list.

The media gateway cannot contact any controller in its controller lists.

The media gateway has successfully contacted one of the controllers in its controller lists.

The media gateway cannot register with any controller in its controller list.

The H.248 link between the media gateway and its controller is down.

The H.248 link between the media gateway and its controller is back in service.

A maintenance test has failed.

Failed maintenance tests have succeeded.

Maintenance test failure count has exceeded its reporting threshold.

Maintenance test failure count has dropped below its reporting threshold.

The media gateway is beginning automatic reinitialization.

One of the media modules is beginning automatic reinitialization.

The reset media module is running normally.

A media module has failed its power-on startup test.

Media module power-on startup test successful.

A media module has failed its parameter exchange.

Media module parameter exchange successful.

An attempt to upload a configuration file has failed.

One or more of the VoIP engines in the media gateway is over its occupancy threshold, as measured by a snapshot: (Channels In Use)/(Total Channels).

All the VoIP engines in the media gateway are operating below occupancy threshold, as measured by a snapshot: (Channels In Use)/(Total Channels).

One or more of the VoIP engines in the media gateway is over its average occupancy threshold.

All the VoIP engines in the media gateway are operating below occupancy threshold, as measured by a snapshot: (Channels In Use)/(Total Channels).

A VoIP engine has begun automatic reset.

A VoIP engine has completed automatic reset, and is running normally.

The DSU in one of the E1/T1 media modules failed to configure its Field Programmable Gateway Array.

The DSU in one of the E1/T1 media modules has successfully configured its Field Programmable Gateway Array.

A DSU in one of the E1/T1 media modules has begun automatic reset.

A DSU in one of the E1/T1 media modules has completed automatic reset, and is running normally.

One of the E1/T1 media modules has detected that the DTR signal from its DTE is off. This indicates that the DTE is not connected or not functioning.

One of the E1/T1 media modules has detected that the DTR signal from its DTE is back to normal.

An E1/T1 media module has detected that the RTS signal from its DTE is not on whenever the DTE requests to send data and during data transfer. This indicates that the DTE is not functioning.

An E1/T1 media module has detected that the RTS signal from its DTE is back to normal.

An E1/T1 media module has detected that the data received from the local DTE to be sent to the far end is either all ones or all zeroes.

The E1/T1 media module is receiving normal data from the local DTE to be sent to the far end.

An E1/T1 media module has detected that the data received from the far end to be sent to the local DTE is either all ones or all zeroes.

The E1/T1 media module is receiving normal data from the far end to be sent to the local DTE.

There is an IP configuration failure in the VoIP Engine. No static IP address has been supplied or the firmware is getting indications that this is a duplicate IP address.

The IP configuration of the VoIP Engine is successful.

An attempt to download a configuration file has failed.

The media gateway has begun download of a configuration file.

The media gateway has completed successful download of a configuration file.

Timeslot usage is over the occupancy threshold, as measured by a snapshot: (Timeslots In Use)/(Total Timeslots).

Timeslot usage is below the occupancy threshold, as measured by a snapshot: (Timeslots In Use)/(Total Timeslots).

No more Timeslot are available on this gateway.

Timeslots are again available on this gateway, usage is below the occupancy threshold, as measured by a snapshot: (Timeslots In Use)/(Total Timeslots).

The media gateway has successfully registered with a controller. This trap is identical to cmgRegistrationSuccess but with INET Address varbind instead of IPv4 varbind.

The media gateway cannot register with any controller in its controller list. This trap is identical to cmgRegistrationFault but with INET Address varbind instead of IPv4 varbind.

ISDN Layer-2 is down on a Ds1.

ISDN Layer-2 is established on a Ds1.

The Gateway is in FIPS error mode.

A Gateway TLS Certificate was revoked.

The Gateway could not access a Certificate Revocation List.

The Gateway could not download a Certificate Revocation List due to filesystem limitations.

A Gateway TLS Certificate has expired.

A Gateway TLS Certificate is near expiry and should be updated.

A Gateway TLS Certificate could not be authenticated

Non critical event occur during attempt to download a software module.

This table is used for managing contact closure adjunct port. The adjunct box contains two relays.

Each contact closure port can control two relays on the adjunct

The admin state of the contact-closure where: Auto(1): The Contact Closure is controlled by the call Controller. Trigger(2): The contact closure relay is triggered. Off(3): The contact closure relay is off (not triggered). Enumeration: 'manualOff': 3, 'auto': 1, 'manualTrigger': 2.

The number of second the relay is triggred after each pulse activation signal is received from the call-controller.

The actual contact closure relay state Enumeration: 'off': 2, 'triggered': 1.

Emergency Transfer Function Table (short circuit Line and Trunk ports in case of call-controller connectivity problems)

Module number - 10 on G450

Module's ETR administration state where: off(1): ETR is turned off without checking if there is an active call among trunk-line port pairs auto(2): ETR is turned off as soon as the module is operational (controlled by a call controller) on(3): ETR is never turned off Enumeration: 'auto': 1, 'off': 3, 'on': 2.

The number of ETR TRUNK-LINE pairs

The current status of the ETR function Enumeration: 'on': 1, 'off': 2.

Each bit in the bit-mask represents a current-loop-detector of one trunk-line ETR pairs. The bit is set when current is detected

Dynamic CAC status Enumeration: 'active': 1, 'notArmed': 3, 'notSupported': 255, 'armedNotConfigured': 4, 'notConfigured': 2.

The last Reported BBL value sent to the MGC

The last time (sysUpTime) a 'dynamic CAC' event was sent to the MGC

The current state of the SLA Monitor. Enumeration: 'disabled': 0, 'enabled': 1.

The IP address type (IPv4 or IPv6) of this SLA Monitor server.

The IPv4 or IPv6 address of the SLA Monitor server.

The SLA Monitor server port.

The SLA Monitor packet capture mode. Enumeration: 'withoutPayload': 1, 'none': 0, 'all': 2.

The SLA Monitor firmware version.