See Also................................................................................................................................... 1
About VoIP Monitoring Manager Client ........................................................................................... 3
See Also................................................................................................................................... 3
About VoIP Monitoring Manager Web Client................................................................................... 5
See Also................................................................................................................................... 5
About VoIP Monitoring Manager Server.......................................................................................... 7
See Also................................................................................................................................... 7
Components of VoIP Monitoring Manager...................................................................................... 9
See Also................................................................................................................................... 9
About Licenses..............................................................................................................................11
Help ............................................................................................................................................... 13
What’s this help...................................................................................................................... 13
VoIP Monitoring Manager is a Voice over IP (VoIP) Quality of Service (QoS) monitoring tool. It
enables you to monitor and review the quality of a call on an AVAYA™ VoIP network. Using the
VoIP Monitoring Manager, you can view the Jitter, Round Trip Time (RTT) and Packet Loss
experienced at the endpoints and during a session. The QoS data displays currently active
endpoints or for endpoints active in the past. With this information, you can begin to troubleshoot
and isolate problems.
If you are new to using the VoIP Monitoring Manager, the following information explains what you
can do with this tool.
Search for Endpoints
You search endpoints active from some time in the past or within a date range. The Advanced
Search options enable you to narrow your search to match phone numbers, SIP user names,
network addresses, or QoS level.
View Reports
Once you have completed your search, you can view a summary or a detailed report. The reports
display the QoS data for selected endpoints. This is particularly useful for monitoring Gateways or
locating problems at a particular endpoint. You can also view a report for endpoints involved in a
session. This will assist with determining problems that occur between two endpoints or in an
isolated area of the network.
Generate Automatic Alarms
You can generate SNMP Traps/Alarms , which enables the VoIP Monitoring Manager to alert you
when the Jitter, Round Trip Time or Packet Loss reaches certain levels. This assists you to
routinely monitor the network, and troubleshoot problems.
See Also
Components of VoIP Monitoring Manager
Starting VoIP Monitoring Manager
How to Use VoIP Monitoring Manager Client
About Licenses
1
About VoIP Monitoring Manager Client
The VoIP Monitoring Manager (VMM) Client provides the graphical user interface (GUI) for VoIP
Monitoring Manager. The VMM Client does not communicate with the VMM RTCP Monitor and
does not use SNMP. The data that is displayed is gathered from the VoIP Monitoring Manager
(VMM) Server.
The VMM Client may be installed on the same machine as the VMM Server, or it may be installed
on another machine on the network. It is possible for the VMM Server and the VMM Client to
communicate over a dial-up connection.
See Also
Components of VoIP Monitoring Manager
Starting the VoIP Monitoring Manager
How to Use VoIP Monitoring Manager Client
3
About VoIP Monitoring Manager Web Client
The VoIP Monitoring Manager (VMM) Client can run as a web application in a browser. This is
useful if you only have the VMM Server installed.
The VMM Server needs to be running a web server. If you purchased Avaya Integrated
Management, the Apache web server will already be installed and running. If you choose to run
the Apache web server, the VMM installation will assist with configuration. The machine running
the VMM Web Client needs to have the Sun Java Plug-in installed to run the Web Client.
Configure the web server to publish the file to the following default install path:
If you run the web client you will not have access to all the functionality available in the
application. This includes features such as copy and connect to a new server. For more
information see Starting VoIP Monitoring Manager Web Client.
See Also
Components of VoIP Monitoring Manager
Starting the VoIP Monitoring Manager Web Client
Web Client Displaying Incorrect Time
5
About VoIP Monitoring Manager Server
The VoIP Monitoring Manager Server acts as a proxy between the VoIP Monitoring Manager
Client and the VoIP Monitoring Manager RTCP Monitor. The main purpose of the VoIP Monitoring
Manager Server is to reduce the amount of traffic to the VoIP Monitoring Manager Client by
performing large data downloads and extensive processing of the MIB data stored on the RTCP
Monitor. The VoIP Monitoring Manager Server can reside on the same PC as the RTCP Monitor.
See Also
Components of VoIP Monitoring Manager
Starting the VoIP Monitoring Manager
7
Components of VoIP Monitoring Manager
The VoIP Monitoring Manager (VMM) application comprises the VMM RTCP Monitor and the
VMM Server, which accepts connections from the VMM Client. If you only have the VMM Server
installed, you can run VMM Client as a web client.
To ensure it will run correctly, you will need to have configured the Switch Administration Forms,
have a Windows SNMP Agent installed on the Server and the Monitoring Manager Server needs
to be installed onto the network.
The components and their relationship are described in more detail in the following links:
VoIP Monitoring Manager Server
VoIP Monitoring Manager RTCP Monitor
VoIP Monitoring Manager Client
VoIP Monitoring Manager Web Client
Database
See Also
About VoIP Monitoring Manager
Starting VoIP Monitoring Manager
How to Use VoIP Monitoring Manager Client
Configure the Avaya Communication Manager IP-Network Region Form
Configure the Avaya Communication Manager System-Parameters IP-Options Form
9
About Licenses
VoIP Monitoring Manager requires licenses that you must purchase from Avaya. You can
purchase these licenses in sets of 2000 phone endpoints and 40 media gateways. The Avaya
licenses are managed by the WebLM server, which is provided with VoIP Monitoring Manager.
By selecting Help>About in the VMM Server or the VMM Client, you can view the following
information:
the number of licenses purchased
the number of phones at the local server. This number represents the phones that
reported to VMM in the last 28 days. This number will increase if you move phones (for
example, change extensions or IP addresses). In this case, these phones appear to be
new endpoints to VMM. Since there is a 30-day grace period, this will not be a problem.
the number of phones at the local server that exceed the license (that is, the number of
phones that are unlicensed). If greater than zero, this number is displayed in red. This
can occur if you have only one monitor connected to the WebLM License Server, and you
have more phones stored in the database than licenses purchased.
the number of media gateways at the local server. This number represents the media
gateways that reported to VMM in the last 28 days.
the number of media gateways at the local server that exceed the license (that is, the
number of media gateways that are unlicensed). If greater than zero, this number is
displayed in red. This can occur if you have only one monitor connected to the WebLM
License Server, and you have more media gateways stored in the database than licenses
purchased.
Each VMM RTCP monitor periodically checks the number of endpoints it knows about and
requests/renews the licenses for them. If there is more than one RTCP monitor and the total
number of endpoints known exceeds the number of licenses, the RTCP monitor that requests
licenses first will get its licenses. The RTCP monitor that requests licenses last will be denied
licenses. If you enter the 30-day grace period because license limits were exceeded, the About
dialog box will appear every time the VMM Server and VMM Client are started. If you exceed the
30-day grace period, VoIP Monitoring Manager stops collecting RTCP data.
Avaya provides a 90-day trial version of VoIP Monitoring Manager. After 90 days, VoIP
Monitoring Manager stops collecting RTCP data. You have the option of purchasing the VoIP
Monitoring Manager license key from Avaya to fully activate the VoIP Monitoring Manager beyond
the 90-day trial period. When a license key is purchased, an instance of WebLM License Server
is required to manage the license key.
Contact your authorized Avaya Sales Representative to purchase additional VMM licenses.
11
Help
Most screens and tasks in VoIP Monitoring Manager have matching topics in this help. You can
go directly to the matching topic by clicking the Help button shown on the screen or dialog.
If the topic displayed does not show the required information, you can open the entire help at any
time.
To open the Help Contents, select Help > Contents.
To open the Help File, click on this icon on the Tool Bar or Help> Contents.
What’s this help
The What’s this? button located on the Tool Bar enables you find out what a Tool Bar or button is
in the application. You click on the What’s this? button as shown above and then click the object.
The help will open explaining that particular object.
Context-sensitive help
If you click the help button on a form, help about that form (or its uses) is displayed.
About menu
You access the About menu from Help > About. The About dialog shows the version number for
the VoIP Monitoring Manager (VMM) Client. This is useful to ensure that you are using the same
version number for the VMM Client as the VMM Server.
Send us feedback!
To send us feedback or to suggest any improvements about this Online Help, send an email to
performance@avaya.com
13
Support Details
If you require further support details check the Avaya web site located at www.avaya.com for the
most recent information. From the main page, navigate to the support page and search for VoIP
Monitoring Manager.
15
Installation Checklist
Installation Checklist
The VoIP Monitoring Manager Server (VMM Server) needs to be installed on the VoIP network.
Before you install the software, you need to configure the Switch Administration Forms.
1. Configure Switch Administrator forms
You need to configure the System-Parameters IP-Options Form and the IP-NetworkRegion Form to send RTCP reports to the RTCP Monitor.
2. Make one port 1099
The VMM Client and Server communicate using Java Remote Method Invocation (RMI),
and uses port 1099 as its default port on the machine running the VMM server. If port 1099
is not available, another port must be made available.
3. Check for Windows SNMP Agent
The SNMP Agent must be installed for the VoIP Monitoring Manager Server to function.
You can check if the Windows SNMP Agent has been configured to run at startup
automatically. The installation also checks to see if the Windows SNMP Agent is installed.
If the Windows SNMP Agent is not installed, the Add/Remove Windows Components
starts automatically and you are be prompted for the Windows 2000 CD location to install
the Windows SNMP Agent.
4. Check for a valid SNMP Community ID
You must set an ID with the correct privileges.
5. Configure SNMP agent for sending traps
Although SNMP is installed and running, it dies not send the required traps until you
configure it.
6. Download VoIP Monitoring Manager or Install from CD
If you are downloading the program from a web site, select to Run this program from its
current location and the installation program starts automatically. Alternatively, you can
select to save the file to disk, which may be the faster option. Once saved to your hard
drive, double-click the saved program's name to start the install. If you are installing the
program from a CD-ROM, insert the CD into your drive and follow the instructions.
7. Connect to a database
When you first install VoIP Monitoring Manager, you need to connect Server to a
database.
Solving Installations Problems: If you are experiencing difficulties running
the application after installation the following checks may assist you:
Check Windows SNMP Agent is Running
Check for a Valid Community ID
17
Avaya VoIP Monitoring Manager Reference
See Also
About VoIP Monitoring Manager
Components of VoIP Monitoring Manager
VoIP Monitoring Manager Server Error Messages
Configure IP-Network-Region form
There are two Switch Administration Forms (SAT) that need to be configured to send RTCP
reports to the RTCP Monitor. These forms are called the ip-network-region form and the systemparameters ip-options form.
Configuration for the ip-network-region form
Set the RTCP Reporting Enabled? field to y (yes).
Set UseDefault Server Parameters? field to y (yes). This indicates that this network
region uses the default values specified previously on the system-parameters-ip-options
form as well.
Why you might not want to use the default parameters?
Multiple VoIP Monitoring Manager Servers might be installed on a large system in order to reduce
the network traffic between a set of endpoints and the RTCP Monitor (e.g. low bandwidth link
between endpoints in one network region and a remote RTCP Monitor). The network traffic due to
RTCP reports being sent from the endpoints to the RTCP Monitor is usually low, less than 40
bytes per second per currently active VoIP call (RTP session). Therefore, it is usually
unnecessary to have multiple RTCP Monitors.
If multiple VoIP Monitoring Manager Servers are installed on the system then the endpoints in
each network region can be configured to send their RTCP reports to different RTCP Monitors.
To achieve this set the Use Default Server Parameters? field to n (no) and specify the IP
address of the Windows 2000 PC running the VoIP Monitoring Manager Server for that network
region.
18
Installation Checklist
See Also
Troubleshooting
No Endpoints Matched the Search
Components of VoIP Monitoring Manager
Configure System Parameters IP Options Forms
Configure System-Parameters IP-Options Form
There are two Switch Administration Forms (SAT) that need to be configured to send RTCP
reports to the RTCP Monitor. These forms are called the system-parameters ip-options form (as
shown below) and the ip-network-region form.
Configuration for the system-parameters ip-options form
Set the RTCP MONITOR SERVER, Default Server IP Address to the address of the
Windows 2000 PC running the VoIP Monitoring Manager Server.
See Also
Troubleshooting
No Endpoints Matched the Search
Components of VoIP Monitoring Manager
Configure IP-Network-Region Form
19
Avaya VoIP Monitoring Manager Reference
Make one port available
The VMM client and server communicate using Java Remote Method Invocation (RMI), and uses
the port 1099 on the machine on which the VMM server is running.
If this port is not available, the VMM server will attempt to use the following ports: 49177, 51173,
or 63006. Although it is unlikely that all of these ports will be in use on a single machine, please
ensure that at least one of these ports is available.
Check Windows SNMP Agent is Installed and Running
The Windows SNMP Agent must be installed before you install the VoIP Monitoring Manager
Server. You are prompted during the VoIP Monitoring Manager install to install it from the
Windows 2000 CD. If the Windows SNMP Agent is not installed or not running, you will
experience problems receiving data.
Check if Windows SNMP Agent is Installed and Running
2. Scroll down until you see the words SNMP Service. It should have a status as Started
and Startup Type as Automatic. If it is not included in the list you will need to install it
from the Windows 2000 CD.
3. If it is listed but not set to run automatically, you will need to change its properties as
follows:
4. Right-click on SNMP and select Properties from the context menu. The SNMP Service
Properties dialog opens.
5. Select Automatic from the Startup Type drop down list.
6. Click OK.
See Also
Check for a Valid Community ID
Troubleshooting
Components of VoIP Monitoring Manager
Check for a Valid SNMP Community ID
The Community ID for your Windows SNMP Agent must match the Community ID defined in the
VoIP Monitoring Manager Options. By default it is public but it may have been changed.
You cannot complete this procedure unless you have already checked that Windows SNMP is
installed and running.
3. Right-click on SNMP Service and select Properties from the context menu.
4. Select the Traps tab.
5. Type the community name that is configured on the network management system where
trap messages will be sent and click Add to list.
6. In the Trap destinations area, click Add. The SNMP Service Configuration dialog
displays.
7. In the SNMP Service Configuration dialog, type the IP Address of the network
management system you want the traps to be sent and click Add. The dialog closes.
8. From the SNMP Service Properties dialog, click OK.
If the changes do not take effect immediately, you may have to restart the SNMP Service. To
restart either Service, right-click on it and select Restart from the context menu.
See Also
Generating Traps & Alarms
Connect to Database
When VoIP Monitoring Manager is first installed, you need to connect it to the database. You also
need to perform this task if you decide to change to a different database (for example you
upgrade to a SQL Server database from the standard MSDE database). This is explained in
Migrate Data.
This setting is for both reading of monitor data, and writing of RTCP data.
To connect to a database:
1. From the VoIP Monitoring Manager server interface, select File > Connect to Database.
22
Loading...
+ 112 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.