Avaya VoIP Monitoring Manager Reference
57
Components of RTT
RTT can comprise the following four components:
Propagation delay: The time it takes for a packet to travel across the network from
sender to receiver. This variable is based on the speed of light and the distance the
signal must travel. For example, the propagation delay between Singapore and Boston is
much longer than the propagation delay between New York and Boston.
Transport delay: The time it takes to traverse the network devices along a transmission
path. Networks containing many routers, firewalls, congestion and low-speed WAN
services, for example, introduce more delay than an overprovisioned LAN on a single
floor of a building.
Packetization delay: The time it takes for a compressor/decompressor (codec) to
digitize an analog signal, build frames and then reverse the process at the other end. The
G.729 codec has a higher packetization delay than the G.711 codec.
Jitter buffer delay: The delay introduced by the receiver while it holds one or more
packets to reduce variations in packet arrival times.
Activity Monitor
Provides the ability to monitor RTCP activity for a set number of minutes, hours, or days. A trap is
generated when no activity is received within the specified time period. The number must be from
1 through 99.
The check box is cleared with a setting of 4 hours, as a default setting.
About the Database
By default, all data sent to VoIP Monitoring Manager via RTCP from the endpoints is stored in the
database. You can run reports against this data or export it for use in other programs, such as
spreadsheets. Depending on the number of monitored terminals and the trap settings, the
repository of data can become substantial.
VoIP Monitoring Manager is supplied by default with an MSDE database, which has a maximum
size of 2 GB per database. You can migrate to an SQL Server 2000 database or an SQL Server
2005 database.
If you are using an MSDE database, the historical data is stored for 30 days in the database.
After 30 days, the data will be deleted.
If you are using an SQL Server 2000 database or an SQL Server 2005 database, the historical
data is stored for 100 days in the database. After 100 days, the data will be deleted.
If you need access to historical data, you must either backup the database or export reports that
include the required data.
Data Storage Limits and Management
If you are using an MSDE database, the historical data is stored for 30 days in the database.
After 30 days, the data will be deleted.
If you are using an SQL Server 2000 database or an SQL Server 2005 database, the historical
data is stored for 100 days in the database. After 100 days, the data will be deleted.
(60 páginas)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentários a estes Manuais