About VoIP Monitoring Manager Client ........................................................................................... 2
About VoIP Monitoring Manager Web Client................................................................................... 2
About VoIP Monitoring Manager Server.......................................................................................... 2
Components of VoIP Monitoring Manager...................................................................................... 2
About Licenses................................................................................................................................ 3
Help ................................................................................................................................................. 4
What’s this help........................................................................................................................ 4
Avaya 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. Avaya
VoIP Monitoring Manager allows you to view the QoS data (such as Jitter, Round Trip Time
(RTT) and Packet Loss) experienced at the endpoints and during a session. The QoS data
displays in real-time or for previously active endpoints. 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 can search endpoints active from a specified 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 select one or more endpoints in a session and
view the associated reports. The reports display the QoS data for the selected endpoints. This is
particularly useful for monitoring media gateways or locating problems at a particular endpoint.
Since you can view reports for endpoints involved in a session, this information will assist you
with determining problems that occur between two endpoints or in an isolated area of the
network.
Export Reports
You can export the report data to a comma separated value (csv) file. You can open this file in
most database and spreadsheet programs such as Microsoft Excel. Exporting the data to a
spreadsheet enables you to manipulate the data so you can create your own reports..
Generate Automatic Alarms
You can generate Simple Network Management Protocol (SNMP) traps/alarms, which allow 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.
1
Avaya VoIP Monitoring Manager Reference
About VoIP Monitoring Manager Client
The VoIP Monitoring Manager (VMM) Client provides the graphical user interface (GUI) to view
the VMM data. The VMM Client does not communicate with the VMM RTCP Monitor, does not
use SNMP, and does not communicate with the database. 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 PC on the network. It is possible for the VMM Server and the VMM Client to
communicate over a dial-up connection.
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. To run the VMM Client as a web application, the
following requirements must be met:
The VMM Server needs to be running a web server. The Apache web server is
automatically installed on the server when the VMM Server software is installed.
The web server must be configured to publish the file to the following VMM installation
The server installation will apply this configuration.
The PC you will use to access the VMM Server must be able to connect to the VMM
Server via a web browser and have the following software installed:
Microsoft Internet Explorer 6.0 or later
Sun Java 2 Runtime Environment, SE v1.4.2_06.
If you run the web client, you will not have access to all the functionality available in the VMM
Client application. For example, you will be unable to copy and connect to a new server. For more
information, see Starting VoIP Monitoring Manager Web Client.
About VoIP Monitoring Manager Server
The VoIP Monitoring Manager Server acts as a proxy between the database and the VoIP
Monitoring Manager Client. It manages connectivity to the database and provides an interface to
configure 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 is a Java application that runs as a Windows service on the
same PC as the RTCP Monitor. The VoIP Monitoring Manager Server can reside on the same PC
as the RTCP Monitor, or it can reside on a separate PC.
Components of VoIP Monitoring Manager
The VoIP Monitoring Manager (VMM) application consists of 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 VMM will run correctly, you must perform the following steps:
Configure the Switch Administration Forms on Avaya Communication Manager.
Install a Windows SNMP Agent on the server (if not installed already).
Install the VMM Server on to the network.
2
Avaya VoIP Monitoring Manager Reference
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
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 window 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 you start the VMM Client or open the VMM Server window. If
you exceed the 30-day grace period, VoIP Monitoring Manager Server 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.
3
Avaya VoIP Monitoring Manager Reference
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 box.
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 box 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.
Support Details
If you require further support details for VoIP Monitoring Manager, 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.
4
Avaya VoIP Monitoring Manager Reference
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 on Avaya
Communication Manager.
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 does not send the required traps until you
configure it.
6. Install VoIP Monitoring Manager.
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 the VMM 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
5
Avaya VoIP Monitoring Manager Reference
Configure IP-Network-Region form
You must configure two Switch Administration Forms (SAT) on Avaya Communication Manager
to send RTCP reports to the RTCP Monitor. These forms are called the ip-network-region form
and the system-parameters 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 (for example, 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 configure the endpoints in each network region to send their RTCP reports to different RTCP
Monitors, perform the following steps:
Set UseDefault Server Parameters? field to n (yes).
Specify the IP address of the Windows 2000 PC running the VoIP Monitoring Manager
Server for that network region.
6
Avaya VoIP Monitoring Manager Reference
Configure System-Parameters IP-Options Form
You must configure two Switch Administration Forms (SAT) on Avaya Communication Manager
to send RTCP reports to the RTCP Monitor. These forms are called the system-parameters ipoptions form 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.
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. If Windows SNMP Agent is not installed already, you are prompted during the VoIP
Monitoring Manager installation to install it from the Windows CD.
NOTE:
If the Windows SNMP Agent is not installed or is not running, you will experience problems
receiving data.
7
Avaya VoIP Monitoring Manager Reference
Check if Windows SNMP Agent is Installed and Running
2. Scroll down until you see 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 CD.
3. If the SNMP Service is listed but not set to run automatically, you will need to change its
properties as follows:
1. Right-click on SNMP and select Properties from the context menu. The SNMP
Service Properties dialog box opens.
2. Select Automatic from the Startup Type drop down list.
3. Click OK.
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 dialog box. 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 to
which trap messages will be sent, and click Add to list.
6. In the Trap destinations area, click Add. The SNMP Service Configuration dialog box
displays.
7. In the SNMP Service Configuration dialog box, type the IP address of the network
management system to which the traps will be sent, and click Add.
8. From the SNMP Service Properties dialog box, click OK.
9
Avaya VoIP Monitoring Manager Reference
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.
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 an 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.
2. Enter the Database Server name, Logon Name, and Password.
The database server name can be either a name or an IP address. In either case, it must
be accessible on your network.
3. Click OK.
Manage your licenses
You must log into the WebLM server that manages your Avaya licenses. The license server is
required to activate VoIP Monitoring Manager beyond the 90-trial period. If you do not have a
license to use VoIP Monitoring Manager, you can use the software for a 90-day trial period.
10
Avaya VoIP Monitoring Manager Reference
Customized Setup
You only need to use these procedures if you are changing the default installation (for example,
creating your own database).
Change Monitoring Manager Server
To change the VoIP Monitoring Manager Server that the VoIP Monitoring Manager Client is
communicating with:
1. Select File > Connect to New Server. The Host Name of Server dialog box appears.
2. Enter the name of the new VoIP Monitoring Manager Server, and click OK.
If you are using the VoIP Monitoring Manager Client from a browser, you
will be unable to change the server from which the Client is receiving
information. The monitor that is displaying the Client must be directly
connected to the Server that is running the VoIP Monitoring Manager
Server.
Configure Database Tables
You do not need to configure the database tables as part of a normal installationthis happens
automatically. You only need to configure the database tables if you initially use the default
MSDE database, but then decide to migrate to an SQL Server database.
Migrate Data
Use this procedure if you want to migrate VoIP Monitoring Manager data from the standard
MSDE database to an SQL Server 2000 database or an SQL Server 2005 database. Reasons for
performing this migration include:
Database content needs to exceed 2 GB.
You want access to improved management and reporting tools available in SQL Server.
You want the remote administration capabilities of SQL Server.
You regularly need a connection pool of more than five connections.
11
Avaya VoIP Monitoring Manager Reference
To migrate data:
1. Install SQL Server. VoIP Monitoring Manager supports SQL Server 2000 and SQL Server
2005.
2. Set up the VMM database:
1. Copy SetupNewVmmDatabase.zip to the MS SQL Server machine. (This zip can
be found in the VMM installation\SQL folder.)
2. Extract the zip file and follow the instructions in the extracted readme.txt file.
3. Create a backup of the existing MSDE database.
4. Using the standard SQL Server tools, restore the backed-up database as a new SQL
Server database. (Alternatively, use the script provided: <VMM installation directory>\sql\RestoreVmmDatabase.bat.)
5. Start Avaya VoIP Monitoring Manager Server.
6. Select File > Connect to Database.
7. Enter the Database Server name, Logon Name, and Password. (Note the default VMM
login/password created by the setup scripts is VmmUser/VmmUserPassword.)
8. Click OK.
The Avaya VoIP Monitoring Manager Server shows the progress of the connection. When both
Server Status and SNMP Agent Status bars at 100%, the connection has been successful.
For security reasons, you must change the VmmUser password. Run the batch file
ChangeVmmUserPassword.bat, which is included in the zip, to change the password
associated with the VmmUser SQL login. Then, reconfigure the VMM Server with the new
password.
12
Avaya VoIP Monitoring Manager Reference
Overview of VoIP Monitoring Manager Client
VoIP Monitoring Manager Client
The following image displays an example of the VoIP Monitoring Manager Client in use. A search
has been completed and a Summary Report is displaying ready for analysis. To familiarize
yourself with the environment such as its tools and menus, click on it in the image below.
System Pane
The System pane is populated based on the media gateways that have reported to the VMM
server in the last hour (or specified time period).
Data for the System pane is only obtained over the last hour because this
uses an expensive query if the database is large. If your system has a
small database, you may want to increase this "look back" time. To
increase the "look back" time, you must change the value of the
SystemViewSearchInterval attribute in the VoIPMonMgrClient.ini file.
The VoIPMonMgrClient.ini file is located in the VMM installation
directory. Note that the value of the SystemViewSearchInterval attribute
is in hours.
13
Avaya VoIP Monitoring Manager Reference
For each object, the System pane displays the following information (if available):
Name (if you configured friendly names for gateways)
IP address
The following image shows a sample System pane.
The System pane may contain the following icons:
Gatekeeper
Unknown Gatekeeper
Gateway
From the System pane, you can select a gateway and click the Report button to view an
aggregated report of all the VoIP sessions over the selected link.
Endpoints Pane
The Endpoints pane displays:
the list of active endpoints
the list of endpoints that are the result of a Search you performed
From the Endpoints pane, you can click the Toggle Aliases check box to view/hide the friendly
names for gateways.
14
The following image shows a sample Endpoints pane.
Avaya VoIP Monitoring Manager Reference
15
Avaya VoIP Monitoring Manager Reference
The Endpoints pane may contain the following icons:
Gateway
IP Phone
Avaya IP Softphone
SIP Phone
Identification information is unavailable for this endpoint
Connection Status
When you start the VoIP Monitoring Manager Client, it attempts to connect to the VoIP Monitoring
Manager Server. The results of this connection are displayed in the Status Bar. Some of the
possible connection icons are as follows:
The VoIP Monitoring Manager Client is connected to the
VoIP Monitoring Manager Server.
The VoIP Monitoring Manager Client is not connected to
the VoIP Monitoring Manager Server.
Display in Status Bar
When you connect to a new VoIP Monitoring Manager Server, a message displays in the status
bar as shown below.
Status Bar
The Status bar is the area of space at the bottom of the VoIP Monitoring Manager Client window
that shows the Connection Status and the current license state. You toggle the display of the
Status bar either by clicking on its icon on the Tool bar or selecting/deselecting the checkbox in
the View menu.
Search Dialog Box
The Search dialog box is where you set your search criteria for gathering endpoints. You access
this dialog box by clicking the Search button on the Endpoints tab or selecting Edit > Search. A
search is based on the time period for the active endpoints. This search could contain endpoints
that were active in the last minute, hour, day or month or were active between a date range.
You can use the Advanced Search to run a search for a specific phone number, SIP username,
network address, or based on a QoS value. Once you have entered the details, click the Search
button. A Search updates the Results List with the endpoints. You can then select an endpoint
and view the report.
16
Avaya VoIP Monitoring Manager Reference
Results List
The Results List shown in this image displays a list of endpoints that are a result of the Search.
You can toggle the display of the Results List by unchecking the option from View > Results.
You can also reduce and expand the Result Lists pane by pointing your mouse at the right side
edge and dragging the edge to the desired size.
17
Avaya VoIP Monitoring Manager Reference
18
Avaya VoIP Monitoring Manager Reference
The Results List pane may contain the following icons:
Gateway
IP phone
Avaya IP Softphone
Avaya SIP phone
View Tool Bar
You can toggle the display of the Tool Bar in the VoIP Monitoring Manager Client. Hiding the
Tool Bar provides you with more screen space. Toggle this option by selecting/deselecting the
Tool Bar option from the View Menu.
Search Button
To access the Search dialog box, perform one of the following steps:
Click on the Search button on the Results List.
Click the Search icon on the Tool Bar.
Select Edit > Search.
This opens the Search dialog box, which allows you to run a search for endpoints based on a
time period. You can also use the Advanced Search options to narrow your search to match
phone number, SIP username, network address, and/ or QoS level.
19
Avaya VoIP Monitoring Manager Reference
Getting Started Guide (Client)
Starting VoIP Monitoring Manager Client
You need to ensure that the VoIP Monitoring Manager (VMM) Server is installed and running on
the network before you start the VMM Client. If you only have the VMM Server installed, you can
also start the VMM Client as a Web Client.
To start VoIP Monitoring Manager Client:
From the PC where the VoIP Monitoring Manager Client software is installed, select Start >
Programs > Avaya > VoIP Monitoring Manager > Client.
The Avaya VoIP Monitoring Manager Client window appears. Now you can search for endpoints
and then view the QoS data in a report format.
How to Use VoIP Monitoring Manager Client
To use the VoIP Monitoring Manager, you must start the VoIP Monitoring Manager Server before
you start the Client. Then you can begin to search for endpoints, view reports and begin your
analysis.
Using VoIP Monitoring Manager Client, you can:
Run a Search
View a Report
Interpret the Values Using Summary Reports
Interpret the Values Using Detailed Reports
If you want to become familiar with the application’s tools and menus, see VoIP Monitoring
Manager Client.
Starting VoIP Monitoring Manager Web Client
The Avaya VoIP Monitoring Manager Client can run as a Web application in a browser. This is
useful if you only have the server installed. To run the Avaya VoIP Monitoring Manager Client as
a Web application, the following requirements must be met:
The PC on which the Avaya VoIP Monitoring Manager Server software is installed must
be running a Web server. The Apache Web server is automatically installed on the server
when the Avaya VoIP Monitoring Manager Server software is installed.
The Web server must be configured to publish the file to the following VoIP Monitoring
where VMMServerMachineName = the machine running the VMM Server. This url points
to the machine running the VMM Server.
If you do not have the Sun Java Plug-in installed, you are prompted to install it.
To exit the Web Client, just close the browser.
There are limitations in using the VMM Web Client. These are imposed by
the security restrictions associated with running unsigned applets. The
limitations are:
You can only access one monitor that is directly connected to the
server running the VMM Server.
You cannot:
Connect to a new server.
Use the Copy functionality.
Persist the settings from the Report Properties dialog box.
Log to the Windows event log or files.
Configure aliases for gateways on the client system.
Run a Search
The first action required when using the VoIP Monitoring Manager Client is to search for
endpoints. You can search endpoints active from a point in time in the past or between a date
range. You can also use the Advanced Search options to narrow the search based on phone
number, SIP username, network addresses, or QoS value. Once you have completed your
search, the Results List display the list of endpoints that match your search criteria. You can then
view a report for an endpoint in the Results List.
To Run a Search
1. Perform one of the following steps:
Select Edit > Search.
Click Search on the Endpoints pane.
The Search dialog box appears.
2. From the Search dialog box, click the drop-down arrow to select the time period for
active endpoints. The default is 1 minute, but you can select hours, days, weeks, or
months.
3. If you want to select a date range of active endpoints, click From and click the
calendar(s) drop-down arrow to open the calendar.
21
Avaya VoIP Monitoring Manager Reference
4. From the calendars, select the start (from) and end date (to) of the range. You can
select hours, minutes, seconds, and AM/PM. You can also use the arrow buttons to scroll
through the months and years.
5. Click Search. The Results List updates with a list of endpoints that match your search
criteria. Now, you can select an endpoint and view its report.
View a Report
You can generate reports for endpoints and media gateways.
Endpoint Reports
After you run a search, you can view the report on selected endpoints and endpoints involved in a
session. There are two types of Endpoint reports: Summary Reports and Detailed Reports.
To View the QoS Data for an Endpoint
1. From the Results List, select an endpoint or click the expanding icon and select a child
endpoint that was in a session with the parent endpoint. The Report button becomes
available.
2. Click Report. The Report dialog box opens.
Media Gateway Link Reports
From the System pane, you can select a media gateway and click the Report button to view an
aggregated report of all the VoIP sessions over the selected link. There are three types of Media
Gateway Link reports: Summary Media Gateway Link Report, Detailed Media Gateway Link
Report, and Trace Routes Media Gateway Link Report.
22
Loading...
+ 84 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.