Snmp; Packet Sniffing; Voip Debugging Using Rtp-Mib; Object Tracking - Avaya G250 Overview

Media gateway

Hide thumbs Also See for G250:

Table of Contents

SNMP

The Branch Gateways report alarms using SNMP traps. The G350 fully supports SNMP

versions SNMPv1, SNMPv2c, and SNMPv3. The G250 supports SNMPv3 for sending

SNMPv1, SNMPv2c, and SNMPv3 traps, but does not support the SNMPv1 trap mechanism.

The Branch Gateways feature packet sniffing. All packets, including non-Ethernet packets, that

pass through the Branch Gateway, are recorded. The recorded packets are stored in a file that

can be uploaded either to the Media Server or to a PC and read by Ethereal for troubleshooting

purposes.

The Branch Gateways include the RTP-MIB feature for debugging QoS-related problems

across the VoIP network without any dedicated hardware. During each RTP stream, counters

representing various QoS metrics increment whenever configured thresholds for the metrics are

exceeded. A limited history of the QoS metric statistics is stored on the Branch Gateway for

active and terminated RTP streams. Statistics can be displayed via the G250/G350 CLI. In

addition, the Branch Gateway can be configured to send SNMP traps to the SNMP trap

manager on the media server at the termination of each RTP stream that has QoS problems.

The traps are converted to syslog messages and stored for viewing in the messages file on the

media server hard disk.

The Branch Gateways include object tracking. The purpose of Object tracking is to track the

state (up/down) of remote devices using keepalive probes, and notify registered applications

when the state changes. Object tracking is utilized by applications such as VPN to track remote

devices and take certain steps when the state of a remote device changes.

Alarms and troubleshooting

Issue 2 February 2006

Table of Contents

G350