Avaya VoIP Monitoring Manager Reference Release 3.0 Manual de usuario descargar pdf (Pagina 116)

Avaya VoIP Monitoring Manager Reference

108

Reservation Success:

This state shows that the receiver’s receiving RTP channel is

protected by an installed RSVP reservation. Ideally this reservation

will need to be successfully refreshed until the RTP session ends.

Various:

The RSVP status for a single endpoint in a session has changed

between significant states (such as Failed and Success).

Interpreting Terminal Names

The canonical name or CNAME is the unique identifier for each participant within one RTP

session, or set of related RTP sessions.

The format is user@host, or host if a user name is not available as on single-user systems. For

both formats, host is either the fully qualified domain name or IP address of the host from which

the real-time data originates.

For Avaya VoIP systems CNAMEs are of the format:

IP Telephone

ext<extension>@<IP address>

IP Softphone

ext<extension>@<IP address>

Gateway Board

gwp@<IP address>

Gateway Box

gwt@<IP address>

See Also

Export Results List

Some Fields are Blank in the Exported Data

SNMP Community ID

An authentication ID allowing read and/or write access to SNMP information. This is set as part of

the VMM Server configuration. A single field is used to set both the SNMP Read Community ID

and the SNMP Write Community ID.

A community ID with both read and write privileges must be available to VoIP Monitoring

Manager (via the SNMP dialog). When creating the community ID, ensure that it has both read

AND write privileges

SNMP Read Community ID

The read ID is necessary for obtaining information from the agent, for example, client queries and

existing configuration settings. The read ID must match the ID defined in the Windows SNMP

Service Properties dialog.

1 2 ... 111 112 113 114 115 116 117 118 119 120 121 ... 141 142

Sin comentarios

Avaya VoIP Monitoring Manager Reference Release 3.0 Manual de usuario Pagina 116