Avaya VoIP Monitoring Manager Reference
81
Handling Jitter
Removing Jitter
Jitter can result from bad queuing strategies set up on network equipment. Check your equipment
manual for recommended settings. To remove jitter, the endpoints need to collect packets and
hold them long enough to allow the slowest packets to arrive, allowing them to be played at even
intervals in the correct sequence, which causes additional delay.
Jitter Effects
Jitter can create audible voice-quality problems if the variation is greater than 60ms. Symptoms of
excessive jitter could be reported as crackling or static. A faulty microphone or other hardware
problems can be reported as a similar sound problem to jitter, but they are not related. You need
to rule out that this is not the cause of the problem.
Interpreting RSVP Status
The RSVP status can change during a session. For example, if the RSVP status for a single
endpoint in a session has changed between significant states (such as Failed and Success),
VoIP Monitoring Manager will use the label Various to represent this situation. However, if the
status has only changed from Pending to Success, then VoIP Monitoring Manager will report
Success. Also, the RSVP status can be different for each endpoint in the session. For example,
RSVP may be disabled for one endpoint in the session, and enabled for the other.
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).
(60 strony)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Komentarze do niniejszej Instrukcji