Avaya VoIP Monitoring Manager Configuration manual

Download

Page 1

Avaya VoIP Monitoring Manager Release 3.0

Configuration

555-233-510

Issue 6

June 2005

Page 2

Notice

Every effort was made to ensure that the information in this document was complete and accurate at the time of printing. However, information is subject to change.

Warranty

Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya’s standard warranty language as well as information regarding support for this product, while under warranty, is available through the following Web site: http://www.avaya.com/support

Preventing Toll Fraud

"Toll fraud" is the unauthorized use of your telecommunications system by an unaut horized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there may be a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services.

Avaya Fraud Intervention

If you suspect that you are being victimized by toll fraud and you need technical assistance or support, in the United States and Canada, call the Technical Service Center's Toll Fraud Intervention Hotline at 1-800-643-2353.

Disclaimer

Avaya is not responsible for any modifications, additions or deletions to the original published version of this documentation unless such modifications, additions or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User.

How to Get Help

For additional support telephone numbers, go to the Avaya support Web site: http://www.avaya.com/support

• Within the United States, click the Escalation Management link. Then click the appropriate link for the type of support you need.

• Outside the United States, click the Escalation Management link. Then click the Internationa l Service s link that includes telephone numbers for the international Centers of Excellence.

Providing Telecommunications Security

Telecommunications security (of voice, data, and/or video communications) is the prevention of any type of intrusion to (that is, either unauthorized or malicio us access to or use of) your company's telecommunications equ ipm ent by some part y.

Your company's "telecommunications equipment" includes both this Avaya product and any other voice/data/video equipment that could be accessed via this Avaya product (that is, "networked equipment").

An "outside party" is anyone who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf. Whereas, a "malicious party" is anyone (including someone who may be otherwise authorized) who accesses your telecommunications equipment with either malicious or mischievous intent.

Such intrusions may be either to/through synchronous (time-multiplexed and/or circuit-based), or asynchronous (character-, message-, or packet-based) equipment, or interfaces for reasons of:

• Utilization (of capabilities special to the accessed equipment)

• Theft (such as, of intellectual property, financial assets, or toll facility access)

• Eavesdropping (privacy invasions to humans)

• Mischief (troubling, but apparently innocuous, tampering)

• Harm (such as harmful tampering, data loss or alteration, regardless of motive or intent)

Be aware that there may be a risk of unauthorized intrusions associated with your system and/or its networked equipment. Also realize that, if such an intrusion should occur, it could result in a variety of losses to your company (including but not limited to, human/data privacy, intellectual property, material assets, financial resources, labor costs, and/or legal costs).

. If you are:

Responsibility for Your Company’s Telecommunications Security

The final responsibility for securing both this system and its networked equipment rests with you - Avaya’s customer system administrator, your telecommunications peers, and your managers. Base the fulfillment of your responsibility on acquired knowledge and resources from a variety of sources including but not limited to:

• Installation docume nts

• System administration documents

• Security documents

• Hardware-/software-based security tools

• Shared information between you and your peers

• Telecommunications security experts

To prevent intrusions to your telecommunications equipment, you and your peers should carefully program and configure:

• Your Avaya-provided telecommunications systems and their interfaces

• Your Avaya-provided software applications, as well as their underlying hardware/software platforms and interfaces

• Any other equipment networked to your Avaya products

TCP/IP Facilities

Customers may ex perien ce dif fer ences i n prod uct p erforma nce, relia bili ty and security depending upon network configurations/design and topologies, even when the product performs as warranted.

Standards Compliance

Avaya Inc. is not responsible for any radio or television interference caused by unauthorized modifications of this equipment or the substitution or attachment of connec ting cab le s and equ ipme nt oth er than those specified by Avaya Inc. The correction of interference caused by such unauthorized modifications, substitution or attachment will be the responsibility of the user. Pursuant to Part 15 of the Federal Communications Commission (FCC) Rules, the user is cautioned that changes or modifications not expressly approved by Avaya Inc. could void the user’s authority to operate this equipment.

Product Safety Standards

This product complies with and conforms to the following international Product Safety standards as applicable:

Safety of Information Technology Equipment, IEC 60950, 3rd Edition, or IEC 60950-1, 1st Edition, including all relevant national deviations as listed in Compliance with IEC for Electrical Equipment (IECEE) CB-96A.

Safety of Information Technology Equipment, CAN/CSA-C22.2 No. 60950-00 / UL 60950, 3rd Edition, or CAN/CSA-C22.2 No. 60950-1-03 / UL 60950-1.

Safety Requirements for Information Technology Equipment, AS/NZS 60950:2000.

One or more of the following Mexican national standards, as applicable: NOM 001 SCFI 1993, NOM SCFI 016 1993, NOM 019 SCFI 1998.

The equipment described in this document may contain Class 1 LASER Device(s). These devices comply with the following standards:

• EN 60825-1, Edition 1.1, 1998-01

• 21 CFR 1040.10 and CFR 1040.11.

The LASER devices used in Av aya equipment typi cally operate within t he following parameters:

Typical Center Wavelength Maximum Output Power

830 nm - 860 nm -1.5 dBm 1270 nm - 1360 nm -3.0 dBm 1540 nm - 1570 nm 5.0 dBm

Luokan 1 Laserlaite Klass 1 Laser Apparat Use of controls or adjustments or performance of procedures other than

those specified herein may result in hazardous radiation exposures. Contact your Avaya representative for more laser pr oduct information.

Page 3

Electromagnetic Compatibility (EMC) Standards

This product complies with and conforms to the following international EMC standards and all relevant national deviations:

Limits and Methods of Measurement of Radio Interference of Information Technology Equipment, CISPR 22:1997, EN55022:1998, and AS/NZS

3548. Information Technology Equipment - Immunity Characteristics - Limits

and Methods of Measurement, CISPR 24:1997 and EN55024:1998, including:

• Electrostatic Discharge (ESD) IEC 61000-4-2

• Radiated Immunity IEC 61000-4-3

• Electrical Fast Transient IEC 61000-4-4

• Lightning Effects IEC 61000-4-5

• Conducted Immunity IEC 61000-4-6

• Mains Frequency Magnetic Field IEC 61000-4-8

• Voltage Dips and Variations IEC 61000-4-11

Power Line Emissions, IEC 61000-3-2: Electromagnetic compatibility (EMC) - Part 3-2: Limits - Limits for harmonic current emissions.

Power Line Emissions, IEC 61000-3-3: Electromagnetic compatibility (EMC) - Part 3-3: Limits - Limitation of voltage changes, voltage fluctuations and flicker in public low-voltage supply systems.

Federal Communications Commission Statement Part 15:

Note: This e qui pm en t ha s b ee n te ste d a nd fo un d t o c omp ly w it h the limit s for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and us ed in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the in terference at his own expense.

Part 68: Answer-Supervision Signaling

Allowing this equipment to be operated in a manner that does not provide proper answer-supervision signaling is in violation of Part 68 rules. This equipment returns answer-supervision signals to the public switched network when:

• answered by the called station,

• answered by the attendant, or

• routed to a recorded announcement that can be administered by the customer premises equipment (CPE) user.

This equipment returns answer-supervision signals on all direct inward dialed (DID) calls forwarded back to the public switched telephone network. Permissible exceptions are:

• A call is unanswered.

• A busy tone is received.

• A reorder tone is received.

Avaya at test s tha t thi s r egis te red eq ui pmen t is cap ab le o f pr ovid in g user s access to interstate providers of operator services through the use of access codes. Modification of this equipment by call aggregators to block access dialing codes is a violation of the Telephone Operator Consumers Act of 1990.

REN Number For MCC1, SCC1, CMC1, G600, and G650 Media Gateways:

This equipment complies with Part 68 of the FCC rules. On either the rear or inside the front cover of this equipment is a label that contains, among other information, the FCC registration number, and ringer equivalence number (REN) for this equipment. If requested, this information must be provided to the telephone company.

For G350 and G700 Media Gateways:

This equipment complies with Part 68 of the FCC rules and the requirements adopted by the ACTA. On the rear of this equipment is a label that contains, among other information, a product identifier in the format US:AAAEQ##TXXXX. The digits represented by ## are the ringer equivalence number (REN) without a decimal point (for example, 03 is a REN of 0.3). If requested, this number must be provided to the telephone company.

For all media gateways:

The REN is used to determine the quantity of devices that may be connected to the telephone line. Excessive RENs on the telephone line may result in devices not ringing in response to an incoming call. In most, but not all areas, the sum of RENs should not exceed 5.0. To be certain of the number of devices that may be connected to a line, as determin ed by the total RENs, contact the local telephone company.

REN is not required for some types of analog or digital facilities.

Means of Connection

Connection of this equipment to the telephone network is shown in the following tables.

For MCC1, SCC1, CMC1, G600, and G650 Media Gateways:

Manufacturer’s Port Identifier

Off premises stat ion OL13C 9.0F RJ2GX,

DID trunk 02RV2-T 0.0B RJ2GX,

CO trunk 02GS2 0.3A RJ21X

Tie trunk TL31M 9.0F R J2GX Basic Rate Interface 02IS5 6.0F, 6.0Y RJ49C

1.544 digital interface 04DU9-BN 6.0F RJ48C,

120A4 channel service unit

For G350 and G700 Media Gateways:

Manufacturer’s Port Identifier

Ground Start CO trunk 02GS2 1.0A RJ11C DID trunk 02RV2-T AS.0 RJ11C Loop Start CO trunk 02LS2 0.5A RJ11C

1.544 digital interface 04DU9-BN 6 .0Y R J48C

Basic Rate Interface 02IS5 6.0F RJ49C

For all media gateways:

If the terminal equipment (for example, the media server or media gateway) causes harm to the telephone network, the telephone company will notify you in advance that temporary discontinuance of service may be required. But if advance notice is not practical, the telephone company will notify the customer as soon as possible. Also, you will be advised of your right to file a complaint with the FCC if you believe it is necessary.

The telephone company may make changes in its facilities, equipment, operations or procedures that could affect the operation of the equipment. If this happens, the telephone company will provide advance notice in order for you to make necessary modifications to maintain uninterrupted service.

If trouble is experienced with this equipment, for repair or warranty information, please contact the Technical Service Center at 1-800-242- 2121 or contact your local Avaya representative. If the equipment is causing harm to the telephone network, the telephone company may request that you disconnect the equipment until the problem is resolved.

FIC Code SOC/

02LS2 0.3A RJ21X

04DU9-IKN 6.0F RJ48C,

04DU9-ISN 6.0F RJ48C,

04DU9-DN 6.0Y RJ48C

FIC Code SOC/

04DU9-DN 6.0Y RJ48C 04DU9-IKN 6.0Y RJ48C 04DU9-ISN 6.0Y RJ48C

REN/ A.S. Code

Network Jacks

RJ21X, RJ11C

RJ21X

RJ48M

Network Jacks

Page 4

A plug and jack used to connect this equipment to the premises wiring and telephone network must comply with the applicable FCC Part 68 rules and requirements adopted by the ACTA. A compliant telephone cord and modular plug is provided with this product. It is designed to be connected to a compatible modular jack that is also compliant. It is recommended that repairs be performed by Avaya certified technicians.

The equipment cannot be used on public coin phone service provided by the telephone company. Connection to party line service is subject to state tariffs. Contact the state public utility commission, public service commission or corporation commission for information.

This equipment, if it uses a telephone receiver, is hearing aid compatible.

Canadian Department of Commu nications (DOC) Interference Information

This Class A digital apparatus complies with Canadian ICES-003. Cet appareil numérique de la classe A est conforme à la norme

NMB-003 du Canada. This equipment meets the applicable Industry Canada Terminal

Equipment Technical Specifications. This is confirmed by the registration number. The abbreviation, IC, before the registration number signifies that registration was performed based on a Declaration of Conformity indicating that Industry Canada technical specifications were met. It does not imply that Industry Canada approved the equipment.

Installation and Repairs

Before installing this equipment, users should ensure that it is permissible to be connected to the facilities of the local telecommunications company. The equipment must also be installed using an acceptable method of connection. The customer should be aware that compliance with the above conditions may not prevent degradation of service in some situations.

Repairs to certified equipment should be coordinated by a representative designated by the supplier. Any repairs or alterations made by the user to this equipment, or equipment malfunctions, may give the telecommunications company cause to request the user to disconn ect the equipment.

Declarations of Conformity

United States FCC Part 68 Supplier’s Declaration of Conformity (SDoC) Avaya Inc. in the United States of America hereby certifies that the

equipment described in this document and bearing a TIA TSB-168 label identification number complies with the FCC’s Rules and Regulations 47 CFR Part 68, and the Administrative Council on Terminal Attachments (ACTA) adopted technical criteria.

Avaya further asserts that Avaya handset-equipped terminal equipment described in this document complies with Paragraph 68.316 of the FCC Rules and Regulations defining Hearing Aid Compatibility and is deemed compatible with hearing aids.

Copies of SDoCs signed by the Responsible Party in the U. S. can be obtained by contacting your local sales representative and are available on the following Web site: http://www.avaya.com/support

All Avaya media servers and media gateways are compliant with FCC Part 68, but many have been registered with the FCC before the SDoC process was available. A list of all Avaya registered products may be found at: http://www.part68.org manufacturer.

European Union Declarations of Conformity

by conducting a search using "Avaya" as

To order copies of this and other docume nts:

Call: Avaya Publications Center

Voice 1.800.457.1235 or 1.207.866.6701 FAX 1.800.457.1764 or 1.207.626.72 69

Write: Globalware Solutions

200 Ward Hill Avenue Haverhill, MA 01835 USA

Attention: Avaya Account Manage ment E-mail: totalware@gwsmail.com For the most current versions of documentation, go to the Avaya support

Web site: http://www.avaya.com/support

Avaya Inc. declares that the equipment specified in this document bearing the "CE" (Conformité Europeénne) mark conforms to the European Union Radio and Telecommunications Terminal Equipment Directive (1999/5/EC), including the Electromagnetic Compatibility Directive (89/336/EEC) and Low Voltage Directive (73/23/EEC).

Copies of these Declarations of Conform ity (DoCs) can be obtai ne d by contacting your local sales representative and are available on the following Web site: http://www.avaya.com/support

Japan

This is a Class A product based on the standard of the Voluntary Control Council for Interference by Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio disturbance may occur, in which case, the user may be required to take corrective actions.

Page 5

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Intended Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Conventions Used in This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Support Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Avaya Technology and Consulting (ATAC) . . . . . . . . . . . . . . . . . . . 8

Communications, Solutions, and Integration (CSI ) Group of Software Services 8

Avaya Technical Service Organization (TSO) . . . . . . . . . . . . . . . . . . 9

Avaya Network Management Software Systems Support Group (NMSSS) . . 9

Customized Management Solutions for Avaya Integrated Management. . . . 10

Avaya Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Product Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

How to Access Books on the Web . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Tell Us What You Think! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 1: Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

What is Avaya Voi ce Over IP Monitoring Manager?. . . . . . . . . . . . . . . . . 13

Avaya VoI P Monitoring Manager Components . . . . . . . . . . . . . . . . . . . 14

Avaya VoIP Monitoring Manager Server . . . . . . . . . . . . . . . . . . . . . 14

Avaya VoIP Monitoring Manager RTCP Monitor. . . . . . . . . . . . . . . . . 14

Avaya VoIP Monitoring Manager Client . . . . . . . . . . . . . . . . . . . . . 15

Avaya VoIP Monitoring Manager Web Client . . . . . . . . . . . . . . . . . . 15

WebLM License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 2: Using Avaya VoIP Monitoring Manager . . . . . . . . . . . . 17

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Starting the Avaya VoIP Monitoring Manager Server . . . . . . . . . . . . . . . . 17

Starting the Avaya VoIP Monitoring Manager Client. . . . . . . . . . . . . . . . . 18

Start ing the Avaya VoIP Monitoring Manager Web Client. . . . . . . . . . . . . . 19

Searching for Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Viewing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Viewing the Session Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Exporting the Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Changing the VoIP Monitoring Manager Server Settings . . . . . . . . . . . . . . 23

Generating Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Recommended Trap Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Call Traps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

System Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Issue 6 June 2005 5

Page 6

Contents

Chapter 3: Interpreting Reports . . . . . . . . . . . . . . . . . . . . . . 25

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Endpoint Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Interpreting Summary Reports for Endpoints . . . . . . . . . . . . . . . . . . 25

Interpreting Detailed Reports for Endpoints. . . . . . . . . . . . . . . . . . . 27

Media Gateway Link Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Interpreting Summary Media Gateway Link Reports . . . . . . . . . . . . . . 29

Interpreting Detailed Media Gateway Link Report s . . . . . . . . . . . . . . . 30

Interpreting Trace Routes Media Gateway Link Reports . . . . . . . . . . . . 31

Difference Between Endpoint and Session Reports . . . . . . . . . . . . . . . . 32

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

6 Avaya VoIP Monitoring Manager Release 3.0 Configuration

Page 7

Preface

Purpose

The purpose of this book is to provide the following information:

● An overview of Avaya VoIP Monitoring Manager capabilities and components.

● Procedures for starting and using Avaya VoIP Monitoring Manager.

● A description of how to interpret Avaya VoIP Monitoring Manager reports.

Intended Audience

This book is intended for network managers familiar with network management and its

fundamental concepts.

Conventions Used in Th is Book

The following typographical conventions are used:

● Bold type is used to indicate information that you type, but tons in a window, select ions in a

menu, and the Enter key on the keyboard. It is also used for emphasis.

● Courier font is used for any information that the computer screen displays.

● Arrows indicate options that you sel ect from cascading menus; for example, “Select File >

Open” means choose the “Open” option from the “File” menu.

Issue 6 June 2005 7

Page 8

Preface

Support Resources

Avaya provides a variety of planning, consulting, and technical services. The following sections

describe the resources and services that are available.

Avaya Technology and Consulting (ATAC)

Avaya Technology and Consulting (ATAC) works with client teams to develop det ail ed soluti ons

for connectivity to Avaya Communication Manager solutions. The ATAC also designs network

configurations. Due to configur ation complexities, we strongly recommend that you contract for

professional implementat ion servi ces for t he foll owing Avaya Integrated Management pr oduct s:

● Avaya MultiSite Administration

● Avaya Fault and Performance Manager

● Avaya Proxy Agent

Communications, Solutions, and Integration (CSI) Group of Software Services

Avaya Communications, Solutions, and Integration (CSI) Group of Software Servi ces offers

customers the following services:

● Platform readiness verification

● Remote implementation and installation

● Network management server configuration

● Customer acceptance verification

● Custom on-site services

The CSI Group consists of the following two teams:

● Converged Solutions Implementation Engineering

The Converged Solutions Implementation Engineering (CSIE) team implements multi-sit e media gateway (G350/G650/G700) deployment projects for both voice and data design. The overall directio n of the CSI E te am is to br in g the cor rect methodo logy to t hese complex deployments that span vari ous regions and to provide continuity to the overall project from the voice and data implementation standpoint.

8 Avaya VoIP Monitoring Manager Release 3.0 Configuration

Page 9

● Data Network Implementation Engineering (for merly RNIS)

The Data Network Implementation Engineering team implements and/or upgrades existing or new data networks. This te am analyzes the customer’s network desi gn requirement s and performance expectations, and then creates the hardware and software inst allation specification used to implement data devices including Cajun, VPN, Wireless LAN, Secure Gateways, Extreme, and multi-vendor data equipment.

The CSI Group provides support on a contract basi s. You can purchase various implementation

offers from the CSI Group in Tampa, Florida. See Table 1: Customer-Accessible Resources

page 11 for contact information.

Avaya Technical Service Organization (TSO)

The Avaya Technical Service Organization (TSO) provides suppor t to the Avaya Integrated

Management client teams, field technicians, and cust omers. The TSO will bill customers for

support on a time and materials basis if the following conditions exist:

● Customers do not provide remote access.

Support Resources

● Customers do not have a current maintenance agreement.

● Customers do not procure and install the required systems and software as defined in the

Avaya Integrated Management Services Support Plan.

● Customers request support that is outside the purchase agreement.

The TSO does not support hardware or software that cust ome rs purchase from third-party

vendors.

Avaya Network Management Software Systems Support Group (NMSSS)

The Avaya Network Management Software Systems Support Group (NMSSS) in Tampa Bay,

Florida answers customer calls about products in Avaya Integrated Management. NMSSS will

either answer your questions directly or connect you with an associate who can answer

questions about the products.

Issue 6 June 2005 9

Page 10

Preface

Customized Management Solutions for Avaya Integrated Management

The Integrated Management Product Team understands customer’s needs and is focused on

customer satisfaction. See Table 1: C ustomer-Accessible Resources

information. The Product Team will assist customers with Avaya Integrated Management

projects and will provide:

● Project Management — An Integrated Management project person will work with the

customer to access configuration and customization requirements for any or all applications within each Avaya Int egrated Management offer. If custom work is required, the evaluation will include a proposed statement of work and price. Note that this offer is not intended to provide installation for customers that choose to implement Integrated Management applications using Avaya Services or third-party implementation services.

● Training — Basic training can be performed remotely using an interactive medium to

display the applications and a conference bridge for audio. On-site training can be customized to meet the customer’s needs. Customized training will focus on application functionality that is relevant to the customer and provide focused knowledge transfer to facilitate application-specific training.

on page 11 for contact

10 Avaya VoIP Monitoring Manager Release 3.0 Configuration

Page 11

Avaya Contact Information

Table 1 and Table 2 provide contact information that you may use if you need as sistance during

the process of installing and setting up Avaya Integrated Management. To access the links in

Table 2

, you must be able to access the Avaya intranet.

Table 1: Customer-Accessible Resources

Resource Contact Information

Avaya Support Center http://www.avaya.com/support

Support Resources

Network Management Software Systems Support (NMSSS)

Communications, Solutions, and Integration (CSI) Group of Software Services

Integrated Management Product Team

Toll Fraud Intervention +1 800 643-2353, prompt 1

Table 2: Avaya Internal Resources

Resource Contact Information

Avaya System Management Support

Avaya Technology and Consulting (ATAC)

Communications, Solutions, and Integration (CSI) Group of Software Services

+1 800 237-0016

+1 800 730-9108, prompt 3

Send email to: AIMtraining@avaya.com

http://aem-support.dr.avaya.com

+1 888 297-4700, prompt 2,6

http://forum.avaya.com http://associate2.avaya.com/sales_market/products/

data-implementation-services/

(requires a password)

Integrated Management Services Support Plan

http://associate2.avaya.com/solution/support_plans/ #Enterprise

Issue 6 June 2005 11

Page 12

Preface

Product Documentation

The latest version of Avaya Integrated Management product documentation, including this

book, is available from the Avaya Suppor t W eb Sit e. To view or download these books from the

Web, you must have access to the Internet, an Internet browser, and Adobe Acrobat Reader,

version 5.0 or later. Adobe Acrobat Reader is provided on the System Management CD and is

also available from http://www.adobe.com

instructions on how to view or download these books.

. See How to Access Books on the Web for

How to Access Books on the Web

To view or download books from the Avaya Support Web Site, follow these steps:

1. Access http://www.avaya.com/support

2. In the left column, click System and Network Management.

3. Scroll to Integrated Management, locate the product name, and click the link corresponding to the software release to display a list of availab le books for that product.

Tell Us What You Think!

Let us know how this book measured up to your expectations. Your opinions are crucial to helping us meet your needs! Please send us your comments by mail, fax, or e-mail as follows:

Mail: Avaya Inc.

Avaya Integrated Management Documentat ion Team Room 3C-313 307 Middletown Lincroft Rd. Lincroft, NJ 07738 USA

Fax: Avaya Integrated Management Documentation Team

+ 1 732 852-2469

E-mail: document@avaya.com Subject: Avaya Integrated Management Documentation Team

12 Avaya VoIP Monitoring Manager Release 3.0 Configuration

Page 13

Chapter 1: Overview

What is Avaya Voice Over IP Monitoring Manager?

Avaya Voice Over IP (VoIP) Monitoring Manager is a VoIP Quality of Service (QoS) monitoring tool. It enables you to monitor and review the quali ty of a call on an Avaya VoIP network.

Avaya VoIP Monitoring Manager allows you to view the QoS data (that is, jitter, round trip time (RTT) and packet loss) experienced at th e endpoint s and during a session. Thi s data display s in real-time or for pre vio usly act ive endpoints. With th is in forma tion, you can begin to tr oubleshoot and isolate problems.

Avaya VoIP Monitoring Manager allows you to:

● Search Endpoints. You can search endpoints acti ve from a specified time in the past or

between a date range. Advanced search options enable you to narrow your search to match phone numbers, SIP user names, network addresses, or QoS levels.

● View Reports. Once you have a l ist of endpoints, you can select on e or mor e end poi nt s in

a session and view the associated reports. The reports display QoS data such as jitt er, round trip time (RTT), and packet loss. This is particul arly 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 dat a to a spr eadsheet e nabl es you to manipul ate t he dat a so you c an create your own reports.

● Generate Automatic Alarms. You can generate Simple Network Management Protocol

(SNMP) Trap s/Alarms, which allow the VoIP Monitoring Manager to alert you when the jitter, RTT, or packet loss reaches certain levels. You can routinely monitor the network and troubleshoot problems.

Issue 6 June 2005 13

Page 14

Overview

Avaya VoI P Monitoring Manager Comp onents

The Avaya VoIP Monitoring Manager incorporates the Avaya VoIP Monitoring Manager Real-time Transport Control Protocol (RTCP) Monito r and the Avaya VoIP Monitoring Manager Server , which acc ept s co nnections from t he A vay a VoIP Monitoring Manager Client. The server software must be inst alle d on the network t o work c orr ectly. A Windows SNMP Agent must also be installed on the server.

VoIP Monitoring Manager also uses a database. During installation, the VoIP Monitoring Manager Integrated MSDE Database is instal led by default . However, you can choose to install a different Microsof t SQL database.

The components are described in more detail in the following sections.

Avaya VoIP Monitoring Manager Server

The Avaya VoIP Monitoring Manager Server acts as a proxy between the MSDE databas e and the Avaya VoIP Monitoring Manager Client . It manages connectivity to the database an d provides an interface to configure the Avaya VoIP Monitoring Manager RTCP Monitor. The server resides on the same PC as the R TCP Monit or. The databas e can reside on the same PC as the server and RTCP Monitor, or it can reside on a separate machine.

Avaya VoIP Monitoring Manager RTCP Monitor

The Avaya VoIP Monitoring Manager RTCP Monitor col lects the RTCP packet s sent from the Avaya endpoints and stores the information in a proprietary database. The RTCP Monitor also runs as a sub-agent of t he Windows SNMP Agent. All the informati on contai ned in the dat abase can be queried using Microsoft SQL.

14 Avaya VoIP Monitoring Manager Release 3.0 Configuration

Page 15

Avaya VoIP Monitoring Manager Components

Note:

Avaya VoIP Monitoring Manager Client

The Avaya VoIP Monitoring Manager Client provides the graphical user interface (GUI). The client does not communicate with the RTCP Monitor, does not use the Windows SNMP service, and does not communicate with the database. The data that is displayed is gathered from the Avaya VoIP Monitoring Manager Server. The client may be installed on the same machine as the server, or it may be installed on another machine on the network.

Avaya VoIP Monitoring Manager Web Client

The Avaya VoIP Monitoring Manager Client can run as a Web appli cation in a browser. This is useful if you only have the Avaya VoIP Monitoring Manager Server installed. To run the Avaya VoIP Monitoring Manager Client as a Web application, the following requirements must be met:

● The VoIP Monitoring Manager Server 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 in s talled .

● The Web server must be configured to publish the file to the following VoIP Monitoring

Manager installation path: C:\Program Files\Avaya\VoIP Monitoring Manager\ jars\ClientApplet.htm

Note: The server installati on will apply this configuration.

● The PC you will use to access the Avaya VoIP Monitoring Manager Server must be able to

connect to the VoIP Monitoring Manager Server via a web browser and have the foll owing software installed:

- Microsoft Internet Explorer 6.0 or later

- SUN Java 2 Runtime Environment, SE v1.4.2_06

If you run the W eb c lient , you wil l not h ave access t o s ome of t he feature s—such a s c onnecting to a new server and copying — that are available in the applicati on.

WebLM License Server

The WebLM License Server manages your licenses for Avaya Integrated Management products. It is requir ed when you purchase the VoIP Monitoring Manager license key to activate VoIP Monitoring Manager beyond the 90-trial period. The WebLM License Server is not required to use the 90-day trial version.

Issue 6 June 2005 15

Page 16

Overview

16 Avaya VoIP Monitoring Manager Release 3.0 Configuration

Page 17

Chapter 2: Using Avaya VoIP Monitoring Manager

Note:

Overview

This chapter describes how to

● start the Avaya VoIP Monitoring Manager Server

● start the Avaya VoIP Monitoring Manager Client

● start the Avaya VoIP Monitoring Manager Web Client

● search for endpoints

● view reports

● view session data

● export data

● change the settings of the VoIP Monito ring Manager Server

Note: Avaya VoIP Monitoring Manager Server must be installed and running on the

network before you sta rt th e Avaya V o IP Moni tori ng Manager Cl ient or the A vay a VoIP Monitoring Manager Web Client.

Starting the Avaya VoIP Monitoring Manager Server

To start the Avaya VoIP Monitoring Manager Server, perform the following steps:

1. From the machine where the V oIP Monitoring Server software is installed, select Start > Programs > Avaya > VoIP Monitoring Manager > Server.

The License Server Administration dialog box appears, which enables you to log into the WebLM server that manages your Avaya lic enses. The license server is required to activate Avaya V oIP Monitori ng Manager beyond the 90-day trial perio d. If you do not have a license to use Avaya VoIP Monitoring Manager, you can use the software for a 90-day trial period.

2. In the License Server box, enter the IP address of the WebLM server.

3. In the Port Number box, enter the port number of the WebLM server.

Issue 6 June 2005 17

Page 18

Using Avaya VoIP Monitoring Manager

Note:

4. Click the OK button. The About dialog box appears and displays the licensing informati on.

5. Click the Close button. Avaya VoIP Monitoring Manager Server window appears.

Starting the Avaya VoIP Monitoring Manager Client

The VoIP Monitoring Manager (VMM) Client provides the graphical user interf ace (GUI) for VoI P Monitori ng Manager. The VMM Client does not communicate with the VMM R TCP Monitor and does not use SNMP

Manager (VMM) Server.

. The data that is displayed is gathered fr om the VoIP Monitoring

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.

Note: The Avaya V oIP Monitorin g Manager Server must be running before you st art the

Avaya VoIP Monitoring Manager Client.

To start the Avaya VoIP Monitoring Manager Client, perform the following steps:

1. From the machine where the V oIP Monitoring Manager Client softwar e is i nstalled, select Start > Programs > Avaya > VoIP Monitoring Manager > Client.

2. In the License Server box, enter the IP address of the WebLM server.

3. In the Port Number box, enter the port number of the WebLM server.

4. Click the OK button. The About dialog box appears and displays the licensing informati on.

5. Click the Close button. Avaya V oI P Monitoring Manager Client window appears. Now you can search for end poin t s

and then view the QoS data in a report format

18 Avaya VoIP Monitoring Manager Release 3.0 Configuration

Page 19

Starting the Avaya VoIP Monitoring Manager Web Client

Note:

Starting the Avaya VoIP Monitoring Manager Web Client

The Avaya VoIP Monitoring Manager Client can run as a Web appli cation in a browser. This is useful if you only have the Avaya VoIP Monitoring Manager Server installed.

The VoIP Monitoring Manager Web Client has the following limitations:

● You can access only one monitor that is directly connected to the server running the Vo IP

Monitoring Manager Server.

● You cannot connect to a new server.

● You cannot use the Copy function.

These limitations are imposed by the security restrictions associated with running unsigned applets.

Note: The Avaya V oIP Monitorin g Manager Server must be running before you st art the

Avaya VoIP Monitoring Manager Web Client.

To start the Avaya VoIP Monitoring Manager Web Client, perform the following step:

1. Using Microsoft Internet Explorer 6.0 or later, go to

http://VMMServerMachineName/VoIPMonMgr/ClientApplet.html

where VMMServerMachineName is the machine running the VMM Server. The License Server Administration dialog box appears, which enables you to log into the

WebLM server that manages your Avaya lic enses. The license server is required to activate Avaya V oIP Monitori ng Manager beyond the 90-day trial perio d. If you do not have a license to use Avaya VoIP Monitoring Manager, you can use the software for a 90-day trial period.

2. In the License Server box, enter the IP address of the WebLM server.

3. In the Port Number box, enter the port number of the WebLM server.

4. Click the OK button. The About dialog box appears and displays the licensing informati on.

5. Click the Close button. Avaya VoIP Monitoring Manager Web Client window appears. Now you can search for

endpoints and then view the QoS data in a report format.

To exit the Avaya VoIP Monitoring Manager Web Client, close Microsoft Internet Explorer.

Issue 6 June 2005 19

Page 20

Using Avaya VoIP Monitoring Manager

Searching for Endpoint s

You can search for endpoints active 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 user name, network addresses, or QoS value. Once you have completed your search, the Results List provides a list of endpoints. You can then select an endpoint from the Results List to view QoS data for that endpoi nt in a report format.

To run a search, perform the following steps:

1. Perform one of the following steps:

● Select Edit > Search.

● Click Search on the Endpoint pane.

2. From the Search dialog box, click the dr op down arrow to select a time period to search for active endpoints. The d efault 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 then click the calendar(s) drop down arrow to open the calendar.

4. From the calendars, select the start (From) and end date (To) of the range. You can select hours, minutes, seconds, and AM/PM.

5. Click Search. The Results List provides a list of endpoints. Select an endpoint to view its report.

Viewing Reports

You can generate reports for endpoints and media gatewa ys from the VoIP Monitoring Manager Client.

There are two types of endpoint reports:

● Summary Reports

Summary Reports display the QoS data as a reading on a gauge. Th e needl e on the g auge shows the average values measured and the black inner arc shows the minimum and maximum values measured.

● Detailed Reports

Detailed Reports show how the QoS values changes during the call and when this occurred. The upper values on the Y-axis indicate unacceptable limits. Each point on the line graph represents the maximum value since the last point displayed.

There are three types of media gateway reports:

20 Avaya VoIP Monitoring Manager Release 3.0 Configuration

Page 21

Viewing the Session Data

● Summary Media Gateway Link Reports

Summary Media Gateway Link Reports display the aggregate Qo S data of all the VoIP sessions for the selected media gateway as a reading on a gauge.

● Detailed Media Gateway Link Reports

Detailed Media Gateway Link Report s show the aggregate jitt er, RTT , and per cent loss on a graph for V oIP session going between the two selected media gateways.

● Trace Routes Media Gateway Link Reports

Trace Routes Media Gateway Link Reports show the pr obable routes used be tween the two selected media gateways.

To view an Endpoint report, perform the following step s:

1. From the Results List, select an endpoint or click on the expanding icon and select a child endpoint that was in a session with the parent endpoint.

The Report button becomes enabled.

2. Click Report. The Endpoint reports appear.

3. Click the tab of the Endpoint report you want to view.

To view a Media Gateway Link report, perform the following steps:

1. From the System pane, select a media gateway or click on the exp anding ico n and select a child endpoint that was in a session with the parent endpoint.

The Report button becomes enabled.

2. Click Report. The Media Gateway Link reports appear.

3. Click the tab of the Media Gateway Link report you want to view.

For more information about reports, see Interpreting Reports

Viewing the Session Data

Reports show both endpoints involved in a session. The reports show the parent endpoint involved in the session in the top part of the report with the child endpoint below.

The terms parent and child endpoints are used to describe the way endpoints are displayed in the Results List. A parent i s like t he branch in a tree view. A child is like a leaf in a tree vi ew. You will see the same endpoi nt can be s hown as both a p arent and a chi ld. A parent endpoint is a ny endpoint listed as a result of a search.

on page 25.

Issue 6 June 2005 21

Page 22

Using Avaya VoIP Monitoring Manager

Note:

To view sessions in a report, perform the following steps:

1. Click on the expanding icon positioned in the far left column of the Results List. A sub list appears.

2. Select a child endpoint from the sub list .

3. Click the Report button. The reports appear.

Exporting the Data

The data in the Result s List or from a single report can be exported to a comma separated val ue (cvs) file. The cvs file can be opened in most database and spreadsheet programs. Exporting the data to a spreadsheet enables you to manipulate the data so you can create your own reports. The data exported is divided into the following tables:

● Ses sion Table

● Time-varying Data Table

● Trace Route Table

To export data, perform the following steps:

1. Select File > Export Result List or click the Export button located at the bottom of the Result List.

The Save dialog box appears.

2. Navigate to a folder.

3. In the File name: field, type a name for the file.

4. Click Save as. The file saves with the .csv extension.

5. From Microsoft Excel, open the file. From here you can build your own report. If you want to export a single report, open your

report and click the Report button.

Note: Microsoft Excel can only handle 65,53 6 rows of data. If you need to export more

data, you will need to writ e a script that splits the data int o smaller files bef ore you import the data.

22 Avaya VoIP Monitoring Manager Release 3.0 Configuration

Page 23

Changing the VoIP Monitoring Manager Server Settings

Data that is report ed depends on se tting s that are made i n the se rver. The default settings are a good starting point, but are intended only as a guide. Changing some settings can help you obtain better report s. Over time, you will be able to fine-tune the server se ttings in order to highlight abnormal operation for your specific environment.

Generating Traps

Rules are set to generate traps that notify you when the V oIP network QoS parameters have reached unacceptable levels. Rules are defined in the Trap Threshold Settings dialog box, which provides a tab for Call Traps and a tab for System and Terminal Traps. To open the Trap Threshold Settings dialog box, from the VoIP Monitoring Manager Server window, sel ect Edit > Trap Settings.

More than one rule can be set f or each type of trap, and each r ule can be made up of more t han one condition. When a rule has more than on e condi tion, all cond it ions must be sati sfi ed befo re a trap is sent.

The RTCP Monitor generates a t rap to a pr e-confi gured Trap Manager when the R TCP Monit or experiences the conditions defined. The Trap Manager is generally configured to be the Gateway Alarm Manager (GAM) or Network Alarm Manager (NAM) but any Trap Manager application can be used. Traps can be set for Calls (Sessions), Systems (Networks), and Terminals (endpoint).

VoIP Monitoring Manager creates traps based on two sets of rules:

● Call Traps

If a specified condition occurs anywhere in the system, a trap is sent immediately.

● System Traps

The specified condition must occur a spec ifie d number of times befo re a trap is sent . This is based on an accumulation of warnings from the entire system.

Recommended Trap Settings

Values that you use to trigger tr aps must be fine-tuned to suit your environment. Appropriate settings may vary greatly from one country to another.

The default settings that are in place when VoIP Monitoring Manger is installed are a useful starting point. These settings are based on an environment with high-quality telecommunications facili ties. For example, in this envir onment it is reasonable to expect R TT of less than 300. Recommended trap settings are provided i n Table 3

Issue 6 June 2005 23

Page 24

Using Avaya VoIP Monitoring Manager

Table 3: Recommended Trap Settings

Severity Jitter Delay % loss

MAJ 60 0 0 MAJ 0 500 0

MAJ 0 0 50 WRN 45 0 0 WRN 0 0 4.0

Call Traps

A Call Trap (also referred to as a Call Alarm) is where a trap has been triggered because a customer’s call (session) has reached one of the pre-defined QoS parameter's thresholds.

At the end of a call, the RTCP Monitor checks its trap configurations and generates an alarm to a pre-configured Trap Manager. The conditions for the trap are defined in the Trap Threshold Settings dialog box.

The system alarm can be based on any combination of jitter, delay (RTT) or packet loss.

System Traps

A System Trap (also call ed a System Alarm) is where a tr ap has been triggered because the number of warnings has exceeded the defined threshold. The conditions for the System Tr ap are defined in the Trap Threshold Settings dialog box.

A trap can be defined for the total number of warnings detected on the system, or the total number of warnings detected on an indiv idual terminal. Each trap has a specified in terval during which the number of warnings must be accumulated.

The RTCP Monitor periodically checks to see if the defined interval has expired. It count s the number of warnings recorded during this int erval. If it has reached the defined threshold then a System Trap is generated. To generate an trap as soon as the thresholds are reached, use an interval of zero (0).

The system trap can be based on any combination of jitter, delay (RTT) or packet loss.

24 Avaya VoIP Monitoring Manager Release 3.0 Configuration

Page 25

Chapter 3: Interpreting Reports

Overview

This chapter describes how to interpret the Avaya Vo IP Monitoring Manager reports.

Endpoint Reports

You can generate the following reports for endpoints:

● Summary Report

● Detailed Report

Interpreting Summary Reports for Endpoints

Figure 1 shows a sample Summary Report for an endpoint. Summary Reports show the QoS

data as a reading on a gauge. The needle on the gauge shows the average values measured and the black inner arc shows the minimum and maximu m values measured. Each of the three QoS parameters is dis played on a sep arate gauge. You can alter these values b y selectin g Edit > Report Properties. Summary Report s also show the date range during which the data was collected, the type of endpoint that was monitored, and the phone number and IP address of that endpoint.

You interpret the Summary Reports by noting where the needle on each gauge is positioned. When the needle is positioned in either the yellow or red r anges, it indicates degradation in the QoS. Table 4: Values for t he Summary Report s three QoS parameters on a Summary Report.

on page 26 describes the values for each of the

Issue 6 June 2005 25

Page 26

Interpreting Reports

Figure 1: Summary Report

Table 4: Val ues for the Summary Reports

Acceptable

Gauges

Jitter (ms) 0 to 5 0ms

Round Trip Time (ms)

(Green) Warning (Yellow)

50 to 150ms

Conversation was smooth.

0 to 180ms No delay

between each endpoint.

Crackling, static or intermittent delay could be reported.

180 to 500ms Slight pause in the conversation if at

the lower end of the range to more lengthy delays at the top end of the range could be reported.

Loss (%) 0 to 10%

No drop out in conversation.

10 to 30% Drop out and missing parts of the

conversation could be reported.

Not Acceptable (Red)

> 150ms

> 500ms

> 30%

26 Avaya VoIP Monitoring Manager Release 3.0 Configuration

Page 27

Interpreting Detailed Reports for Endpoints

Figure 2 shows a sample Detailed Report for an endpoint. Detail ed Report s show how the QoS

values change during the call and when this occurred. This information is displayed on a line graph. The X-axis shows the time range and the Y-axis shows the value for each of the QoS parameters. Each point on the line graph represents the maximum value since the last point displayed.

Each of the QoS parameters is represented on the graph by a different color. This makes it easier to see the data on the same line graph. You can uncheck the display of one or more of the QoS parameters on the active line graph. The QoS parameter colors are as follows:

● Jitter is shown in red.

● Round Trip Time is shown in blue.

● Packet Loss is shown in brown.

Detailed Reports provide a tool tip that enables you to point your mouse at the data on the line graph to see the exact data measured. You can also alter the date range to show more or less detail.

Endpoint Reports

You interpret the Detailed Report by noting where the sampled points for each QoS value appears on the line graph and when this may have occurred. The default upper val ues on the Y-axis indicate unacceptable limits. Select Edit > Report Properties to change the lower and upper limits of each QoS value.

Issue 6 June 2005 27

Page 28

Interpreting Reports

Figure 2: Detailed Report

Table 5 describes the values for each of the three QoS parameters on a Det ailed Report.

Table 5: Values for Detailed Reports

QoS

Jitter (ms) (Displayed Red)

Round Trip T ime (ms)

(Displayed Blue)

Lower Acceptable

0 to 50ms Conversation

was smooth. 0 to 180ms

No delay reported.

Middle Warning

50 to 150ms Crackling, static or intermittent

delay could be reported. 180 to 500ms

Slight pause in the conversation if at the lower end of the range to

Upper Not Acceptable

> 150ms

> 500ms

more lengthy delays at the top end of the range could be reported.

Packet Loss (%) (Displayed

Brown)

0 to 10% No drop out in

conversation.

10 to 30% Drop out and missing part s of the

conversation could be reported.

> 30%

28 Avaya VoIP Monitoring Manager Release 3.0 Configuration

Page 29

Media Gateway Link Reports

You can generate the following reports for media gateways:

● Summary Media Gateway Link Report

● Detailed Media Gateway Link Report

● Trace Routes Media Gateway Link Report

Interpreting Summary Media Gateway Link Reports

Summary Media Gateway Link reports display the following aggregate information of all the VoIP sessions for the selected media gateway:

● Jitter

● RTT

● % Loss

● Max Jitter

● Jitter Buffer Overruns

● Jitter Buffer Underruns

● Jitter Buffer Delay

● Max Sequence Jump

● Number Sequence Jumps

● TTL

● Max Sequence Fail

● Number Sequence Fails

Figure 3

shows a sample Summary Media Gateway Link report.

Issue 6 June 2005 29

Page 30

Interpreting Reports

Figure 3: Summary Media Gateway Link Report

Interpreting Detailed Media Gateway Link Reports

Detailed Media Gateway Link reports show the aggregate jitter, RTT, and percent loss on a graph for VoIP sessions going between the two selected media gateways. This report excludes VoI P sessions at the media gate ways tha t ar e with phones. The p ar ent end poi nt invol ved in the session appears at the top of the report, and child endpoint appears at the bottom of the report.

Figure 4

30 Avaya VoIP Monitoring Manager Release 3.0 Configuration

shows a sample Detailed Media Gateway Link report.

Page 31

Figure 4: Detailed Media Gateway Link Report

Media Gateway Link Reports

Interpreting Trace Routes Media Gateway Link Reports

The Trace Routes Medi a Gateway Lin k report s show the probable rout es used between the t wo selected media gateways.

Figure 5

shows a sample Trace Routes Media Gateway Link report.

Issue 6 June 2005 31

Page 32

Interpreting Reports

Figure 5: Trace Routes Media Gateway Link Report

Difference Between Endpoint and Session Reports

The QoS data that appears on an endpoint report is an aggregation of all the sessions that are active at this endpoint. Some endpoints (such as media gateways) can p a rticipate in multiple concurrent sessions, so a high value on a single endpoint report indicates that one or more of the sessions is/was experiencing degradat ion of quality. Because an endpoint can participate in multiple concurrent sessions, a high value on the report indicates that one or more of the sessions is experiencing degradation of quality. It does not indicate which session.

In contrast, a report showing both end points involved in the session displays the QoS data as experienced by both endpoints for that sessi on only. To isolate problems, you must narrow your search by either searching for a specific Qo S value or altering the date of the report.

32 Avaya VoIP Monitoring Manager Release 3.0 Configuration

Page 33

Glossary

802.1 The 802.1p and 8021Q metrics represent s th e value of inc oming RTP p acket s

of the 802.1ptag field and the 802.1Q tag field respectively. Both are a 16-bit unsigned integer.These metrics are sent for the first RTP packet received.

Acoustic Echo Cancellation

The acoustic echo cancellation metri c indicates if an end point is configu red for full-duplex, half-duplex or acoustic echo cancellat ion mode. The ac oustic echo cancellation metric is an enumerated type metric. The possibl e values are:

● 0 = Half-duplex

● 1 = Full-duplex

● 2 = AEC

There is no acoustic echo cancellation on the VoIP engines. Acoustic echo cancellation is a feature for IP phones only.

Alarm Trap or Alarm is a message sent by a Windows SNMP Agent to a Trap

Manager , console, or te rminal to indic ate the occurr ence of a significant event, such as a specifically defined condition or a threshold that was reached.

The Trap Manager is generally configured to be the Gateway Alarm Manager (GAM) or Network Alarm Manager (NAM) but any Trap Manager application can be used with the Avaya VoIP Monitoring Manager.

Apache Apache HTTP server is an open-source HTTP server t hat is mainta ined by the

ApacheSoftware Foundation. A free downl oad is available from http:// www.apache.org follow the links to the HTTPD(HTTP daemon, web server).

AVAYA-VMON-MIB The AVAYA-VMON-MIB is for the storage of RTCP data received from IP

endpoints in the IP telephony system. (The ASN.1 definitions of this MIB and associated T raps are included as text files in the installation.)

Canonical Name (CNAME)

The canonical name or CNAME is the unique identifier for each participant within one RTP session, or set of related RTP sessions.

The format is user@host, or host if a user name is not available as on single-user systems. For both formats, host i s either the fully qualified domain name or IP address of the host from which the real-time data originates. For Avaya VoIP systems CNAMEs are of the format:

● IP Telephone ext<extension>@<IP address>

● IP Softphone exs<extension>@<IP address>

Issue 6 June 2005 33

Page 34

Child Endpoint

● Gateway Board gwp@<IP address>

● Gateway Box gwt@<IP address>

Child Endpoint The terms parent and child endpoints are purely for describing the way

endpoints are displayed i n the Results Lis t. A parent is like the br anch in a tree view . A child is like a leaf in a tree view . The same endpoint can be shown as both a parent and a child.

You click on the expanding icon positioned i n the far left column of the Resul t s List to expand the tree to display a sub list with the child endpoints. A child endpoint represents a session between itself and its p arent. This is different from a parent endpoint that just represents a physical endp o int.

Codec A Codec is an encoder/decoder. In the context of RT P, it is the type of

encoding used for the payload of the RTP packets exchanged as part of a conversation. For example, some RTP Codecs are G.723, G.711 aLaw and G.729. Session Properties shows which Codec is in use.

RTP does not distinguish between different types of payload (such as g729A, g729B, and so on). The value reported by VoIP Monitoring Manager is the sum of all types of g729 data received.

DiffServ Code Point The DiffServ Code Point (DSCP) metric represents the value of the IP DSCP

field of the incoming RTP packets. The DSCP metric is a number in the ra nge 0-63. This value is sen t for the f irst R TP p ac ket rec eived, and r esent when t he DSCP value has changed from the previously reported value.

Echo Tail Length The echo tail length metric represents the length of echo cancellation

processing determined by the distance between the gateway and the endpoint. The echo tail length metric is represented in milliseconds and can have typical value ranging from 8ms to 32ms. The default value is 16ms.

EndTime The EndTime column in the exported file displays the date and time the

session ended. This column appears in the Session Table of the exported file.

Framesize Frame size is the logical units into which data is partitioned for processing. In

the case of a voice coder/decoder (codec) t his is the time sliced blocks used by the codec algorithm. For example, the G.729 codec breaks the input audio signal into 10ms blocks for encoding purposes; therefore if the RTP packet payload is in 30ms blocks then there are 3 frames per packet.

VoI P Monitoring Manager displays t he framesize in the Session Pro perties tab of the report dialog.

34 Avaya VoIP Monitoring Manager Release 3.0 Configuration

Page 35

Interval

Gatekeeper The Gatekeeper column in the Session Table displays the telephony switch

that manage/administers the endpoint.

Gateway A Gateway is generally used as a bridge between signaling protocols and

bearer media. In this context, the Gateways allow IP endpoints to communicate with non-IP endpoints (e.g. the traditional circuit switched world of analogue and digital phones). Avaya mixing the media channels in a conference call. A pair of Gateways can also be set up as an IP trunk.

VoIP Monitoring Manager: The Results List will display one or more phone numbers next to the Gateway endpoint type. These phone numbers are the phone numbers that the Gateway is acting as an intermediary for. Therefore, the phone number of the Gateway can change and can be multiple phone numbers. The Results List wil l sep ar ate endpoints involved in a sessi on with a comma (,). Conferenced calls are separated by a colon (:).

For example, if the following phone number 8616,1111:1222, 8904 displays in the Results List then the Gateway has three active sessions as explained:

● Telephone 8616 is a Non-IP telephone which is in a session with a

Softphone.

Gateways also perform the task of

● Telephones 1111 and 1222 are conferenced (e.g. IP phone 8888 is in a

Session with these two phones).

● Telephone 8904 is a Non-IP telephone in a session with an IP tel ephone.

HopAddress The Hop Address column in the Trace Route Table displays the network node

of each IP address in the trace route.

HopCount The HopCount column in the T race Rout e Table indicates the hop number, i.e.

that is the position in the path of the trace route.

HopTime (ms) The HopTime column in the Trace Route Table displays the results in

milliseconds the round-trip-time of the trace route packet, from the source to each path in the trace route.

Interval The period during which the specified number of warnings must be r eceived to

trigger an alarm (trap).

Issue 6 June 2005 35

Page 36

Jitter

Note:

Jitter Jitter is a measure of variance in the time it takes for communications to

traverse from the sender (application) to the receiver, as seen from the application layer, or the difference between when a packet is supposed to be received and when it is actually receiv ed. We tend to think of jitter as the statistical average variance in delivery time between packets or datagrams. Jitter displays in mill is e c on d s .

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 coll ect packets and hold them long enough to allow th e sl owest p acke ts t o arri ve, a llowi ng them t o 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 fa ulty microphone or other hardware problems can be reported as a similar sound proble m to jitte r but th ey are not rel ated. You need to rule out that this is not the cause of the problem.

Jitter Buffer Over Runs

Jitter Buffer Under Runs

Largest Sequence Fall (LargestSeqFall)

Largest Sequence Jump (LargestSeqJump)

The number of jitter buffer over-r uns metric represents the number of times during a call the jitter buffer was too small . This metric is an 8-bit unsigned integer.

The number of jitter buffer under-r uns metric represents the number of times during a call the jitter buffer became empty or starved. This metric is an 8-bit unsigned integer.

The Largest Sequence Fall metric represents the number of packets that are received from when an out-of-order packet was expected to be received.

Note: A value of 0xFF implies that ther e were too many p acket s out of

order to be able to calculate the correct value.

The Largest Sequence Jump metric represents the maximum number of consecutive packet s lost in the last RTCP reporting interval.

For example, when the following packet sequ ence numb ers 1,2,3,8, are received, the largest Sequence Jump is 4.

Note: A value of 0xFF implies that there were too many pac kets lost to

be able to calculate the correct value.

36 Avaya VoIP Monitoring Manager Release 3.0 Configuration

Page 37

Parent Endpoint

Maximum Jitter The Maximum Jitter metric represents the maximum value of jitter seen in the

RTCP reporting interval. T his metric would be useful to identify transient spikes of jitter in a session. This metric is a 32-bit unsigned integer displayed in milliseconds. The unit is defined by the profile of the RTP session.

Media Encryption The Media Encryption metric indic ates whether media encrypt ion is enabled or

disabled for the RTP session. The Media encrypti on metric is an enumerated type metric. The possible values are:

● 0 = No encryption

● 1 = AEA1.2

● 2 = AES

● 3-255 = Reserved for future use

Number Sequence Falls

The number of sequence fall metric represents how many times during the RTP session there was at least 1 packet that was out of order.

(NumberSeqFalls) Number Sequence

Jumps

The number of sequence jump instances metric represents how many times during the reporting interval there was at least 1 packet which was lost.

(NumberSeqJumps)

Octet The Octet column in the Session Table indicates the size of the packets.

Packet A packet is the logical grouping of information that includes a header

containing control information and (usually) the user data . The term packet is most often used to refer to the applicati on layer data units.

Packet Loss Packet Loss is the result of packets being lost in the transmission from one

endpoint to another. When packet loss occurs there could be a drop out of words or partial words in the conversation. At low levels, poor voice quality would result. At high levels, the conversat ion becomes unintelligible. Packet Loss can result from line congestion.

Parent Endpoint The terms parent and child endpoin ts are purely for describing the way

endpoints are displayed i n the Results Lis t. A parent is like the br anch in a tree view . A child is like a leaf in a tree view . The same endpoint can be shown as both a parent and a child.

A parent endpoint is any endpoint listed as a result of a search. You click on the expanding icon positioned in the far l e ft column to expand the parent endpoint and show the child endpoints.

Issue 6 June 2005 37

Page 38

ParticipantID

ParticipantID The ParticipantI D column assigns a unique identifier to each participant in the

exported file. Each exported session has two p articipants. The exported data contains three sets of dat a. Thi s dat a i s listed in t hree separate tables that are separated by a blank row: Session Table, Time-v arying Data Table and the TraceRoute Table. For every session a p articipant was involved i n there will be a unique pair: SessionID and ParticipantID, enabling you to associate the session data, time-varying data and the trace route data as belonging to that participant in a specific session. Use the ParticipantID to identify the participant in each table to analyze the data.

Payload Payload refers to the contents of a packet. In RTP, it is encoded audio that is

the user data of a packet.

Perceived Delay Perceived delay is the total effect RTT and Jitter have on a phone user’s

conversation.

Quality of Service (QoS)

QoS is the measure of the level of quality that a service requir e s. The VoIP Monitoring Manager monitors and displays the 3 main fa ctors that determine the quality of calls. These factors are Jitt er, Round Trip Time, and Packet Loss. On the Summary Report each of the 3 factors display as a separate gauge. The Detailed Report displays the QoS as follows;

● Jitter is shown on the Detailed Report in red.

● Round Trip Time is shown on the Detailed Report in blue.

● Packet Loss is shown on the Detailed Report in brown.

RcvrIPAddr The RcvrIP Ad dr column displays the I P address of this sess ion par ticipant (i.e.

endpoint). This column appears in the Session Table of the exported file.

RcvrPHONE The RcvrIPAddr column displays the phone number of the participant. This

column appears in the Session Table of the exported file.

Real-Time T ransport Control Protocol (RTCP)

A protocol providing support for applications with real-time properti es, including timing reconstructi on, loss detection, security, and content identification. It reports information about the RTP stream.

RTCP provides support for real-time conferencing for large groups within an Internet, including source identification and support for Gateways (like audio and video bridges) and multicast-to-unicast translators.

RTCP provides information about Round Trip T ime, Jitter, Packet Loss and other data useful for analyzing voice quality.

Endpoints transmitting real time data send an RTP stream, which carries the actual data (e.g. audio, video). The endpoints also send a corresponding RTCP stream. For more informati on see RFC 1889 located at

http://www.ietf.org/rfc/rfc1889.txt

38 Avaya VoIP Monitoring Manager Release 3.0 Configuration

Page 39

RSVP Status

Real-Time T ransport Protocol (RTP)

Resource ReSerVation Protocol (RSVP)

Round Trip Time (RTT)

Real-Time Transport Protocol is the protocol used for transmitting real-t ime data. For more information see IETF RFC 1889 located at

http://www.ietf.org/rfc/rfc1889.txt

RSVP is a protocol for reserving network bandwidth on the routers and switches between two end points in a session (i n some other pr ot ocol, such a s RTP. There are two reservations per session, one for each direction the data has to travel. For further referen ce see the IETF RFCs 2205 and 2750 loc ated at http://www.ietf.org/rfc/rfc2205.txt

Round trip time is the length of time it takes a packet to traverse the network and return (thus being a round trip). It is the sum of the t wo one-way network delays between two endpoints. Call ers can experience difficulties i n carrying on a normal conversation when the one-way network delay exceeds 500 milliseconds (ms). However, some users may elect to tolerate this. It 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 tr avel. 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 t akes t o travers e the n etwork devic es along

a transmission path. Networks containing many routers, firewalls, congestion and low-speed WAN services, for example, introduce mor e 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.

RSVP Status The RSVP status for an endpoint shows whether the RSVP is enabled on the

endpoint, and if it is, whether a reservation was established for the received RTP data stream.

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) then VoIP Monitoring Manager will use the label Various to represent thi s situation. However, if the status has only changed from Pending to Success, then VoIP Monitoring Manager wil l report Success. Also, the RSVP status can be different for each endpoint in the session. For example, RSVP may be dis abled for one end point in the session, and enabled for the other.

Issue 6 June 2005 39

Page 40

RTCP Listen Port

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 Us e : 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 i t has received s ince the call start ed with a Resv message, and is waiting for a ResvConf to confirm the reservation is install ed.

● 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 c onfigur able por t that i s used t o c ollect the RTCP

packets sent by A vaya 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-t ime

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 betwe en two IP endpoints. For more

information see RFC 1889 located at

http://www.ietf.org/rfc/rfc1889.txt?number=1889

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.

40 Avaya VoIP Monitoring Manager Release 3.0 Configuration

Page 41

Time-To-Live (TTL)

Silence Suppression In Voice over IP (VoIP), silence suppression is a method of detecting the

silence in audio and purposefully dropping si lent packets at the sender to conserve network bandwidth. The receiver will generate comfort noise or conceal the loss of packets when packets are dropped. Because the receiver conceals loss and generates comfort noise, silence suppression is usually imperceptible to the l istener. The Silence Suppression field will be repor ted as enabled, disabled or unknown.

Session Table The Session Table is one of the exported t ables co ntaining data tha t general ly

remains the same during a ses sion. As a resul t, t her e is one entry per session in this table. The Session t able will display in Microsoft Excel at the top of t he same worksheet as the Ti me-varying Data table and the Tr ace Route table. The data in the Session table is indexed by Sessi onID and ParticipantID.

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 T rac eRoute Table. Use the SessionID to identify the session in each table to analyze the data.

StartTime The StartTime column in the exported file displays the dat e and time the

session started. This col umn appears in th e Session Table of the exported file .

TimeOffset The TimeOffset column displays the number of seconds since the session

started for this set of data. This column appears in the Time-varying Data Table of the exported file.

Time-varying Dat a Table

Time-To-Live (TTL) Time-to-live (TTL) is a value in an Internet Protocol (IP) packe t that tells a

The Time-varying Data table is one of the exported tables containing the time-varying data f or the sessions in the Session table. The data i n this t able is indexed by SessionID, Particip antID, and a time offset. The SessionID and ParticipantID enable the data to be linked to corresponding sessions in the Session table. The time offset indicates when this set of information was reported (in seconds sinc e the start of each call) . T he Time-varying Dat a table will display in Microsoft Excel below the Session Table on the same worksheet. To view the information more easily, you may want to copy the table and paste it to another worksheet.

network router if a packet has been forwarded towards its destination too many times and should be discarded. For a number of reasons, packets may not get delivered to their destinat ion in a reasonable length of time. For example, a combination of incorrect routing tables could cause a packet to loop endlessly. A solution is to discard the packet after the packet has been forwarded a certain number of times and send a message to the originator, who decides whether to resend the packet.

Issue 6 June 2005 41

Page 42

TOOL

The initial TTL value is set, usually by a system default, in a field of the IP packet header wit h a v alue in the rang e 0 to 255. T he ori gina l id ea of TTL was that it would specify a certain time span in seconds that, when exhausted, would cause the packet to be discarded.

Since each router is required to subtract at lea st one count fro m the TTL field, the count usually indicates the number of router hops the packet has remaining before it must be discarded. Each router that receives a packet subtracts one from the count in the TTL field. When the count reaches zero, the router detecting it discards the packet and sends an Internet Control Message Protocol (ICMP) message back to the originating host.

TOOL The TOOL value is the name and version of the applicati on generating the

stream, e.g., Avaya VoIP Engine v.123. This information may be useful for diagnosis. The TOOL value should remain constant for the duration of the session.

Trace Route Table The Trace Route table contains inf ormation about the route in the network that

the RTP packets traverse between the two endpoints of the call. It will display in Microsoft Excel below the Time-varying Data t able.

Trap or Alarm A Trap or Alarm is a message sent by a Windows SNMP Agent to a Trap

Manager , console, or te rminal to indic ate the occurr ence of a significant event, such as a specifically defined condition or a threshold that was reached. It is also referred to as an Alarm. The T rap Manager is generally configured to be the Gateway Alarm Manager (GAM) or Network Alarm Manager (NAM) but any Trap Manager application can be used with the Avaya VoIP Monitoring Manager.

VoIP or Voice over Internet Protocol

Windows SNMP Agent

VoIP is an acronym for Voice over Internet Protocol. This is the technology standard that allows Internet telephony. It provides the capability for liv e voice communication over the Internet so tha t you can talk using the multimedia capabilities of your computer, in the same way you would talk using a telephone.

The Simple Network Management Protocol (SNMP) Agent is the Windows SNMP service that runs on your computer. SNMP is a protocol for communications between remote network management stations and managed network elements (such as Avaya devices).

The VoIP Monitoring Manager Server needs the Windows SNMP Agent installed as it enables the RTCP Monitor to collect and publish the data. The Windows SNMP service is provided with the Windows 2000 CD but is not installed by defaul t. You will be prompted during the VoIP Monitoring Manager install to install it from the Windows 2000 CD.

42 Avaya VoIP Monitoring Manager Release 3.0 Configuration

Page 43

Index

Symbols

>, meaning of in text . . . . . . . . . . . . . . . . . 7

Numerical

802.1D . . . . . . . . . . . . . . . . . . . . . . 33

Acoustic Echo Cancellation. . . . . . . . . . . . . 33

Advanced Search . . . . . . . . . . . . . . . . . 13

Avaya

support web site

AVAYA-VMON-MIB . . . . . . . . . . . . . . . . 33

. . . . . . . . . . . . . . . . 12

blue. . . . . . . . . . . . . . . . . . . . . . . . 27

bold text, meaning of. . . . . . . . . . . . . . . . . 7

brown . . . . . . . . . . . . . . . . . . . . . . . 27

Canonical Name (CNAME) . . . . . . . . . . . . . 33

Child Endpoint. . . . . . . . . . . . . . . . . . . 34

CName . . . . . . . . . . . . . . . . . . . . . . 33

Codec. . . . . . . . . . . . . . . . . . . . . . . 34

contact information for Avaya. . . . . . . . . . . . .11

courier font, meaning of . . . . . . . . . . . . . . . 7

crackling . . . . . . . . . . . . . . . . . . . . . 28

delay

no delay

detailed

interpreting

Detailed Media Gateway Link reports . . . . . . . . 21

interpreting . . . . . . . . . . . . . . . . . . . 30

Detailed Reports. . . . . . . . . . . . . . . . . . 25

endpoints . . . . . . . . . . . . . . . . . . . 20

difference between endpoi nt & session . . . . . . . 32

DiffServ Code Point . . . . . . . . . . . . . . . . 34

drop out. . . . . . . . . . . . . . . . . . . . .26, 28

DSCP. . . . . . . . . . . . . . . . . . . . . . . 34

. . . . . . . . . . . . . . . . . . . . 28

. . . . . . . . . . . . . . . . . . . 27

Echo Tail Length . . . . . . . . . . . . . . . . . . 34

endpoint

difference between session and

endpoints reports. . . . . . . . . . . . . . 25, 27, 32

EndTime. . . . . . . . . . . . . . . . . . . . . . 34

Export . . . . . . . . . . . . . . . . . . . . . . . 13

Export the Data. . . . . . . . . . . . . . . . . . . 13

. . . . . . . . . 32

feedback about this book . . . . . . . . . . . . . . 12

Framesize . . . . . . . . . . . . . . . . . . . . . 34

Gatekeeper . . . . . . . . . . . . . . . . . . . . 35

Gateway . . . . . . . . . . . . . . . . . . . . . . 35

generating automatic alarms . . . . . . . . . . . . 13

Glossary . . . . . . . . . . . . . . . . . . . . . . 33

HopAddress . . . . . . . . . . . . . . . . . . . . 35

HopCount . . . . . . . . . . . . . . . . . . . . . 35

HopTime (ms) . . . . . . . . . . . . . . . . . . . 35

intermittent delay, QoS values indicating . . . . . 26, 28

interpreting. . . . . . . . . . . . . . . . . . . . . 32

interpreting reports . . . . . . . . 25, 27, 29, 30, 31, 32

jitter . . . . . . . . . . . . . . . . . . . . 13, 26, 27

Jitter buffer delay. . . . . . . . . . . . . . . . . . 39

Jitter Buffer Over Runs . . . . . . . . . . . . . . . 36

Jitter Buffer Under Runs . . . . . . . . . . . . . . 36

Largest Sequence Fall (LargestSeqFall) . . . . . . . 36

Largest Sequence Jump (LargestSeqJump) . . . . . 36

loss . . . . . . . . . . . . . . . . . . . . . . . . 26

Issue 6 June 2005 43

Page 44

Index

match

phone number, network addres s, Qo S

Maximum Jitter . . . . . . . . . . . . . . . . . . 37

Media Encryption . . . . . . . . . . . . . . . . . 37

Media Gateway Link reports . . . . . 21, 29, 30, 31, 32

missing parts of the conversation . . . . . . . . . . 26

. . . . . . 13

Results List . . . . . . . . . . . . . . . . . . . . 21

Round Trip Time . . . . . . . . . . . . . . . . 26, 27

Round Trip Time (RTT) . . . . . . . . . . . . . . . 39

RSVP Status. . . . . . . . . . . . . . . . . . . . 39

RSVP status . . . . . . . . . . . . . . . . . . . . 13

RTCP Listen Port. . . . . . . . . . . . . . . . . . 40

RTCP monitor . . . . . . . . . . . . . . . . . . . 14

RTP MIB. . . . . . . . . . . . . . . . . . . . . . 40

RTP Session. . . . . . . . . . . . . . . . . . . . 40

Number Sequence Falls (NumberSeqFalls) . . . . . 37

Number Sequence Jumps (NumberSeqJumps) . . . 37

packet. . . . . . . . . . . . . . . . . . . . . . . 37

packet loss . . . . . . . . . . . . . . . . .13, 27, 37

Packetization delay . . . . . . . . . . . . . . . . 39

Parent Endpoint . . . . . . . . . . . . . . . . . . 37

ParticipantID. . . . . . . . . . . . . . . . . . . . 38

pauses

QoS values indicatin g

pauses, QoS values indicating . . . . . . . . . . . 28

Payload . . . . . . . . . . . . . . . . . . . . . . 38

Perceived Delay . . . . . . . . . . . . . . . . . . 38

Propagation delay . . . . . . . . . . . . . . . . . 39

. . . . . . . . . . . . . . 26

Quality of Service (QoS) . . . . . . . . . . . . . . 38

query

customizing using filters

. . . . . . . . . . . . . 13

RcvrIPAddr . . . . . . . . . . . . . . . . . . . . 38

RcvrPHONE. . . . . . . . . . . . . . . . . . . . 38

Real-Time Transport Control Protocol (RTCP) . . . . 38

Real-Time Transport Protocol (RTP) . . . . . . . . 39

red . . . . . . . . . . . . . . . . . . . . . . . . 27

reports . . . . . . . . . . . . . . . . . . . . . . 32

interpreting . . . . . . . . . . . . 25, 27, 29, 30, 31

Resource ReSerVation Protocol (RSVP) . . . . . . 39

resources

Avaya Communications, Solutions, and Integration

(CSI) Group of Software Services

Avaya Network Management Software Systems

Support Group (NMSSS) . . . . . . . . . . . . 9

Avaya Technical Service Organization (TSO). . . . 9

Avaya Technology and Consulting (ATAC) . . . . . 8

Customized Management Solutions for Avaya

Integrated Management . . . . . . . . . . . . 10

. . . . . . . . 8

Session . . . . . . . . . . . . . . . . . . . . . . 32

Session Table . . . . . . . . . . . . . . . . . . . 41

session, difference between endpoint and . . . . . . 32

SessionID . . . . . . . . . . . . . . . . . . . . . 40

Silence Suppression . . . . . . . . . . . . . . . . 41

Simple Network Management Protocol Agent. . . . . 13

SNMP traps, generating automatically . . . . . . . . 13

StartTime . . . . . . . . . . . . . . . . . . . . . 41

static, QoS values indicating . . . . . . . . . . . . 28

summary

interpreting

Summary Media Gateway Link reports. . . . . . . . 21

interpreting . . . . . . . . . . . . . . . . . . . 29

Summary Reports

endpoints

. . . . . . . . . . . . . . . . . . . 25

. . . . . . . . . . . . . . . . . . . . 20

TimeOffset. . . . . . . . . . . . . . . . . . . . . 41

Time-To-Live (TTL). . . . . . . . . . . . . . . . . 41

Time-varying Data Tab le . . . . . . . . . . . . . . 41

TOOL . . . . . . . . . . . . . . . . . . . . . . . 42

Trace Route Table . . . . . . . . . . . . . . . . . 42

Trace Routes Media Gateway Link reports . . . . . . 21

interpreting . . . . . . . . . . . . . . . . . . . 31

Transport delay. . . . . . . . . . . . . . . . . . . 39

Trap or Alarm . . . . . . . . . . . . . . . . . . . 42

traps, generating automatically . . . . . . . . . . . 13

typographical conventions. . . . . . . . . . . . . . .7

View Reports. . . . . . . . . . . . . . . . . . 13, 20

Voice Codec . . . . . . . . . . . . . . . . . . . . 13

VoIP or Voice over Internet Protocol . . . . . . . . . 42

Web Client. . . . . . . . . . . . . . . . . . . . . 15

WebLM License Server . . . . . . . . . . . . . . . 15

Windows SNMP Agent . . . . . . . . . . . . . . . 42

44 Avaya VoIP Monitoring Manager Release 3.0 Configuration

Avaya VoIP Monitoring Manager Configuration manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Preface

Purpose

Intended Audience

Conventions Used in Th is Book

Support Resources

Avaya Technology and Consulting (ATAC)

Communications, Solutions, and Integration (CSI) Group of Software Services

Avaya Technical Service Organization (TSO)

Avaya Network Management Software Systems Support Group (NMSSS)

Customized Management Solutions for Avaya Integrated Management

Avaya Contact Information

Product Documentation

How to Access Books on the Web

Tell Us What You Think!

Chapter 1: Overview

What is Avaya Voice Over IP Monitoring Manager?

Avaya VoI P Monitoring Manager Comp onents

Avaya VoIP Monitoring Manager Server

Avaya VoIP Monitoring Manager RTCP Monitor

Avaya VoIP Monitoring Manager Client

Avaya VoIP Monitoring Manager Web Client

WebLM License Server

Chapter 2: Using Avaya VoIP Monitoring Manager

Overview

Starting the Avaya VoIP Monitoring Manager Server

Starting the Avaya VoIP Monitoring Manager Client

Starting the Avaya VoIP Monitoring Manager Web Client

Searching for Endpoint s

Viewing Reports

Viewing the Session Data

Exporting the Data

Changing the VoIP Monitoring Manager Server Settings

Generating Traps

Recommended Trap Settings

Call Traps

System Traps

Chapter 3: Interpreting Reports

Overview

Endpoint Reports

Interpreting Summary Reports for Endpoints

Interpreting Detailed Reports for Endpoints

Media Gateway Link Reports

Interpreting Summary Media Gateway Link Reports

Interpreting Detailed Media Gateway Link Reports

Interpreting Trace Routes Media Gateway Link Reports

Difference Between Endpoint and Session Reports

Glossary

Index

Symbols

Numerical