Avaya VoIP Monitoring Manager Release 3.1 Configuration Manuel d'utilisateur Page 44

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 48
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 43
RTCP Listen Port
44 Avaya VoIP Monitoring Manager Release 3.1 Configuration
The RSVP status can be:
Unknown: Information about the RSVP status was not available.
Disabled: The end-point has been configured to ignore RSVP signaling.
Not in Use: RSVP is enabled for use but there is no receiver RTP
channel session active, or no attempt has been made by the sender to
protect the receiver’s RTP channel (i.e. no Path message has been
received).
Reservation Pending: This state indicates that the receiver has
responded to the first Path message it has received since the call started
with a Resv message, and is waiting for a ResvConf to confirm the
reservation is installed.
Reservation Failed: This state indicates that the receiver has had a
reservation fail or timeout, or an existing reservation was torn down
prematurely.
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).
RTCP Listen Port The RTCP Listen Port is the configurable port that is used to collect the RTCP
packets sent by Avaya endpoints. The default port is 5005. You can change
the port that is used in the RTCP Monitor Properties dialog.
RTP Real-Time Transport Protocol is the protocol used for transmitting real-time
data. For more information see IETF RFC 1889 located at http://www.ietf.org/
rfc/rfc1889.txt.
RTP MIB The RTP MIB stores the information for the active RTP Sessions. The
reference for the definition of the RTP MIB is located at
http://www.ietf.org/rfc/rfc2959.txt
RTP Session A session is a VoIP connection between two IP endpoints. For more
information see RFC 1889 located at
http://www.ietf.org/rfc/rfc1889.txt?number=1889
S
SessionID The SessionID column assigns a unique identifier to each session in the
exported file. Each exported session contains three sets of data. This data is
listed in three separate tables that are separated by a blank row: Session
Table, Time-varying Data Table and the TraceRoute Table. Use the
SessionID to identify the session in each table to analyze the data.
Vue de la page 43
1 2 ... 39 40 41 42 43 44 45 46 47 48

Commentaires sur ces manuels

Pas de commentaire