CA ehealth. Voice Over IP (VoIP) Deployment and Quick Reference Guide. r6.1

(1)

CA

e

Health

®

Voice Over IP (VoIP) Deployment and Quick

Reference Guide

(2)

This documentation and any related computer software help programs (hereinafter referred to as the

“Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by CA at any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of the Documentation for their own internal use, and may make one copy of the related software as reasonably required for back-up and disaster recovery purposes, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the provisions of the license for the product are permitted to have access to such copies.

The right to print copies of the Documentation and to make a copy of the related software is limited to the period during which the applicable license for the product remains in full force and effect. Should the license terminate for any reason, it shall be the user’s responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE.

The use of any product referenced in the Documentation is governed by the end user’s applicable license agreement. The manufacturer of this Documentation is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section

252.227-7014(b)(3), as applicable, or their successors.

(3)

CA Product References

3

CA Product References

This document references the following CA product:

CA eHealth® (eHealth) CA eHealth® for Voice

CA AdvantEDGE View™ (AdvantEDGE View) CA eHealth® SystemEDGE™ (SystemEDGE) CA eHealth® Voice Quality Monitor (VQM)

CA eHealth® Live Health® Application (Live Health)

Contact Technical Support

For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact Technical Support at

(4)

(5)

Contents 5

Chapter 1: Deploying and Discovering VoIP Resources

How to Deploy and Discover VoIP Resources . . . 7

Deployment and Discovery Requirements and Tips . . . 9

eHealth for Voice . . . 9

VQM Systems and Mean Opinion Score (MOS) . . . 10

Routers (and QoS-Enabled Routers) . . . 10

Voice Gateways . . . 11

LAN Switches. . . 11

Network Interfaces. . . 11

Chapter 2: Licensing VoIP Resources

eHealth for Voice Licenses . . . 13

Voice Quality Monitor (VQM) System Licenses . . . 13

eHealth Requirements for VQM and MOS. . . 13

eHealth Poller Requirements for VQM and MOS . . . 14

Router (and QoS-Enabled Router) Licenses . . . 14

eHealth Requirements for Routers . . . 14

Poller Requirements for Routers . . . 14

Voice Gateway Licenses . . . 14

eHealth Requirements for Voice Gateways. . . 14

Poller Requirements for Voice Gateways . . . 15

LAN Switch Licenses . . . 15

eHealth Requirements for LAN Switches . . . 15

Poller Requirements for LAN Switches. . . 15

System Licenses . . . 15

eHealth Requirements for Systems. . . 15

Poller Requirements for Systems . . . 15

Network Interface Licenses . . . 16

eHealth Requirements for Network Interfaces . . . 16

Poller Requirements for Network Interfaces . . . 16

Technology, Reporting, and Live Health Licenses. . . 16

Chapter 3: Setting Up eHealth for Voice—Voice Quality Monitor

Software Prerequisites. . . 18

Discover VQM Systems . . . 19

Create Voice Quality Paths . . . 19

Create Groups for VQM Path Elements. . . 22

Create Group Lists . . . 23

Create Profile Associations . . . 24

Copy and Modify the eHealth Voice Quality Monitor Template . . . 25

Apply the eHealth Voice Quality Monitor Template. . . 26

(6)

6 eHealth Voice Over IP (VoIP) Deployment and Quick Reference Guide

Perform Capacity Planning for VoIP Environments. . . 28 Delete or Disable Tests . . . 30

(7)

Deploying and Discovering VoIP Resources 7

Chapter 1: Deploying and Discovering

VoIP Resources

A Voice Over IP (VoIP) network contains a variety of devices, interfaces, and applications that contribute to (or impact) the quality of voice signals. eHealth can help you manage and monitor all these resources, and monitor the Mean Opinion Score (MOS) for the connections that support your users.

How to Deploy and Discover VoIP Resources

To manage your VoIP network resources, you must deploy and discover (identify) these resources as follows:

Install the eHealth for Voice software.

Note: Cisco CallManager (CCM) 5.0 and above are supported with eHealth

for Voice.

Install the eHealth Voice Quality Monitor (VQM) module and the eHealth

SystemEDGE agent on the systems that support VQM.

You must install an additional VQM site to act as a reflector. Use AdvantEDGE View to configure VQM paths to the reflectors.

Discover VQM paths by using System and Response Elements modes.

Discover network resources by using Remote Access Service (RAS) mode.

eHealth creates elements for the voice gateway, each CPU, each digital signal processor (DSP), DS0 links, and any voice gateway peer-to-peer links (if configured).

Discover any QoS-configured routers that you have by using QoS mode to

identify your class of service (CoS) elements.

(8)

How to Deploy and Discover VoIP Resources

In addition to the VoIP-specific features shown in the graphic, you can use the LAN/WAN, router/switch, and system features to manage the routers, switches, and interfaces that compose your network.

Note: For more information about the eHealth VoIP solution, see the eHealth

Overview Guide.

Discover resources by using RAS mode.

Discover QoS-configured routers and any Cisco Service Assurance

(9)

Deployment and Discovery Requirements and Tips

This section summarizes eHealth requirements and provides tips for deploying and discovering resources in a VoIP network.

eHealth for Voice

The eHealth for Voice environment consists of the following components:

A PC running the Microsoft SQL Server and containing the eHealth for Voice

database

One or more application PCs running eHealth components for task

scheduling, data collection, data archiving, and report generation

Any number of client PCs, which provide access to the database for viewing

data, running reports and administering data collection

You can set up a single-PC environment or a distributed environment. Each environment, however, can have only one database server.

In a single-PC environment, the eHealth for Voice database, the SQL

Server, and all eHealth software components reside on one PC.

In a distributed environment, the database resides on a separate system

running the Microsoft SQL Server. Only one application PC can run the task scheduler (task scheduling component), but any number of additional eHealth application PCs can run the data collection services. You can add clients to any configuration to provide remote access to all operations. Install the eHealth for Voice software on the following:

The primary computer, which will contain the task manager service. In most

cases it will also contain the eHealth for Voice database, although the dastabase can reside on another PC in the network.

Note: The environment must contain at least one primary installation of

eHealth for Voice before you can set up clients.

(Optional) Other network machines that will act as collectors, collecting data

from remote machines, clients, or both, and will provide access to the database for viewing data, running reports, and managing program operations

Note: For more information about setting up an eHealth for Voice environment,

(10)

VQM Systems and Mean Opinion Score (MOS)

Install the following on a minimum of two Windows systems in your network:

eHealth SystemEDGE agent

eHealth Voice Quality Monitor module

One VQM site must serve as a transmitter (where you configure the VQM paths to test voice quality), and one site must be a reflector (a destination for the tests).

Deploy VQM systems as follows:

Place the eHealth VQM sites as close as possible to the IP phone devices

within the network.

Use AdvantEDGE View on the eHealth VQM system to create the VQM paths

for testing.

Deploy several eHealth VQM systems to configure many VQM paths (to test

capacity loading) and possible connections throughout the network. Discover VQM systems as follows:

Use System and Response Elementsmodes.

Configure your VQM paths by using AdvantEDGE View.

After you create, delete, or modify paths, rediscover the system by using

Response Elementsmode to update the VQM response path elements.

Routers (and QoS-Enabled Routers)

Make sure that routers are eHealth-certified devices. Software is not required on routers. If you use Cisco routers that support Service Assurance Agent (SAA) features, you can create SAA response paths to monitor jitter to specific destinations.

Deploy routers by configuring and enabling QoS support per vendor instructions. With eHealth – Response, you can use eHealth to configure Cisco SAA tests on Cisco routers and test jitter and response time to other Cisco devices across the network.

Discover routers by using QoS mode to obtain class of service (COS) elements. Also do the following:

(11)

Voice Gateways

Make sure that voice gateways are eHealth-certified devices. Software is not required on gateways.

Configuration is not required to deploy voice gateways. Voice gateway peer-to-peer links are optional.

Discover each gateway by using RAS mode.

LAN Switches

Make sure that LAN switches are eHealth-certified devices. Software is not required on switches.

Discover LAN switches as follows:

Use Router/Switch mode to manage each device. Use LAN/WAN mode to manage interfaces.

Network Interfaces

(12)

(13)

Licensing VoIP Resources 13

Chapter 2: Licensing VoIP Resources

eHealth license planning for Voice Over IP (VoIP) covers the licenses and software required for each type of VoIP resource and the eHealth poller licenses consumed after those resources are discovered.

Note: For an overview of VoIP and how eHealth manages it, see the eHealth

Overview Guide.

eHealth for Voice Licenses

Your eHealth for Voice environment requires a license for at least one platform from which you intend to collect data.

Note: Policy Manager, which provides powerful automated alarm and threshold

tracking features, is an optional and separately licensed component of eHealth for Voice. For more information about the Policy Manager elements, see the

Policy Manager User Guide.

Voice Quality Monitor (VQM) System Licenses

VQM systems and Mean Opinion Score(MOS) require eHealth and eHealth poller licenses.

eHealth Requirements for VQM and MOS

Each VQM system requires licenses for the following:

eHealth SystemEDGE agent

eHealth Voice Quality Monitor module

Note: You must install a minimum of two VQM systems to create VQM paths.

(14)

Router (and QoS-Enabled Router) Licenses

14 eHealth Voice Over IP (VoIP) Deployment and Quick-Reference Guide

eHealth Poller Requirements for VQM and MOS

To poll a VQM system, the following are required:

One universal license for each VQM path configured between a transmitter

and a reflector. (If you configure multiple paths between the same transmitter and reflector, the paths share the same license.)

One system license for the VQM system element (to manage the system,

CPU, disks, interfaces, and partitions)

Router (and QoS-Enabled Router) Licenses

Routers require only eHealth poller licenses.

eHealth Requirements for Routers

eHealth-related agents are not required on routers.

Poller Requirements for Routers

To poll a QoS router, the following are required:

One poller license and 1/10 universal license for each class of service (CoS)

configured at the router for each direction (in and out).

Note: eHealth consumes one universal element for every 10 QoS elements

discovered.

One universal license for the router (to manage the router, CPU, and

interfaces). The interfaces share the router license unless you record detailed data for one or more interfaces individually. In this case, each interface requires a poller license.

For Cisco routers that support Service Assurance Agent, one universal

license for each SAA path to test jitter.

Voice Gateway Licenses

Voice gateways require only eHealth poller licenses.

eHealth Requirements for Voice Gateways

(15)

LAN Switch Licenses

Licensing VoIP Resources 15

Poller Requirements for Voice Gateways

To poll a voice gateway, the following are required:

One universal license for the gateway device (which includes all the CPU and

DSP cards on the gateway)

One universal license for each T1/E1 DS0 interface

LAN Switch Licenses

LAN switches require only eHealth poller licenses.

eHealth Requirements for LAN Switches

eHealth-related agents are not required on switches, but other agents must be eHealth-certified devices.

Poller Requirements for LAN Switches

To poll a switch, one universal license for the switch (to manage the switch, CPU, and interfaces) is required. The interfaces share the switch license unless you record detailed data for one or more interfaces individually. In this case, each interface requires a universal license.

System Licenses

Systems require only eHealth poller licenses.

eHealth Requirements for Systems

eHealth SystemEDGE agents, modules, or both may be required. Other system agents must be eHealth-certified devices.

Poller Requirements for Systems

To poll a system, the following are required:

One license for the system element (to manage the system, CPU, disks,

interfaces, and partitions)

One universal license for each Application Insight Module (AIM) or service

(16)

Network Interface Licenses

Network interfaces require only eHealth poller licenses.

eHealth Requirements for Network Interfaces

eHealth-related agents are not required on interfaces. Other agents must be eHealth-certified interfaces.

Poller Requirements for Network Interfaces

To poll an interface, one universal license for each interface is required. Some interfaces such as mobile wireless may require more than one poller license.

Technology, Reporting, and Live Health Licenses

To discover and monitor VoIP resources, you need the following:

eHealth – E2EConsole package, which provides the technology and reporting

licenses that you need including Router/Switch, LAN/WAN, QoS, System, Application Insight, Remote Access, Response, and others

Report licenses for Health and Service Level reports

Live Health license to monitor your resources for realtime alarms and

notifications of problems

Note: For more information about the reports and capabilities of eHealth VoIP,

(17)

Setting Up eHealth for Voice—Voice Quality Monitor 17

Chapter 3: Setting Up eHealth for

Voice—Voice Quality Monitor

(18)

Software Prerequisites

VQM systems from which you transmit the tests are known as

transmitter/receivers. The systems at the other end of the test (which reflect

back the call) are reflectors. You must install a SystemEDGE agent and eHealth Voice Quality Monitor module on every transmitter/receiver and reflector system.

You use AdvantEDGE View to create paths from a transmitter/receiver to a reflector and specify the codec and the jitter/MOS path configuration parameters to use for testing. You can create up to 100 paths from each transmitter/receiver system. After you create the paths, use AdvantEDGE View to monitor MOS from one system to the other in real time and use the eHealth console to discover the VQM paths that you created. Then you can run eHealth reports on those paths. You can install the eHealth VQM module on laptop computers and move them throughout the network as needed. You can also configure new tests to obtain MOS values for a variety of potential network paths.

Software Prerequisites

You must be an eHealth administrator and an eHealth Web administrator to perform the tasks described in this document. Before you begin, you must do the following:

If necessary, install and license eHealth. VQM requires a minimum release

of eHealth 5.7.

Note: For more information, see the eHealth Installation Guide.

On every system that you want to use as a transmitter/receiver or reflector,

install and license the following:

– Microsoft Windows® 2000 with a minimum of Service Pack 1, Microsoft Windows XP with a minimum of Service Pack 1, or Microsoft Windows 2003 (32 bit)

– SystemEDGE Agent Version 4.1 with a minimum of Patch Level 3 – An eHealth VQM module

You can deploy the SystemEDGE agent and eHealth VQM module simultaneously to multiple systems by using AdvantEDGE View Agent Deployment.

(19)

Discover VQM Systems

After you have installed and licensed the SystemEDGE agent and eHealth VQM module on all the systems that you want to use as transmitter/receivers and reflectors, use the eHealth console to run the discover process for those systems.

Both the Response Source and the System Element require a read-write community string setting for discovery to succeed.

To discover VQM systems

1. Open the eHealth console and select Setup, Discover. The Discover dialog appears.

2. Select ‘System’and ‘ResponseElements’ under Mode.

3. Specify the read/write community string in the Community Strings field and the method for discovering under Discover Using.

4. Click Discover.

eHealth discovers the transmitter/receiver and reflector systems and displays them with a jitterMos-RD suffix.

5. Click Save in the Discovering dialog.

eHealth saves the discovered elements in the Poller Configuration.

Create Voice Quality Paths

After you discover the VQM systems, you can use AdvantEDGE View to create Voice Quality paths from those systems.

To create Voice Quality paths

1. Log in to the eHealth Web interface.

2. Click the Systems & Apps tab and then click AdvantEDGE View.

3. Select the transmitter/receiver system (the system from which you want to create the paths) from the System drop-down list.

Note: If a system from which you want to create paths does not appear in

the Systemlist, eHealth has not discovered it. Use the eHealth console to run the discover process for this system and any systems that you want to use as reflectors (by using System and Response Elements modes). Then refresh the pagein your Web browser to view the systems in the System list. 4. Select Voice Quality Monitor from the Applications list.

(20)

Create Voice Quality Paths

AdvantEDGE View displays the Voice Quality Report for this system. If Voice Quality paths do not exist for this system, the report does not contain any data.

The Voice Quality Report is shown in the following graphic.

6. Click Add New Voice Quality Path.

The Add Voice Quality Path form, shown in the following graphic, appears.

7. Complete the form as follows:

a. Specify an index number for the row in the Index field.

Limits: The number must be greater than zero and cannot be in use in

the Voice Quality configuration file (mosmod.cf_{), located on the} SystemEDGE agent machine in:

drive:\sysedge\plugins\mosmod

b. Specify a description for the path in the Description field. c. Locate the Reflector list.

(21)

Create Voice Quality Paths

Only systems that have the Voice Quality Monitor module installed and that eHealth has discovered (by using System and Response Elements modes) are available in the Reflector list.

e. Specify the port number for the reflector in the Reflector Port field. Use the reflector port number that you specified when installing the eHealth Voice Quality Monitor module.

f. Locate the Parameter Setlist.

g. Select the parameter set that matches the codec that you are using to convert analog voice to digital packets.

h. Specify an octet value for the IP Type of Service (TOS) in the IP TOS Octet Value field.

Use this field only if you have configured your routers to use TOS, and use the same setting that you specified for your routers.

i. Specify the response time limit (in milliseconds) for this response path in the Response Limitfield.

Use a value that reflects the average length of time for the systems to respond, based on their distance from one another.

Examples: In a LAN environment with low jitter values, you might want

to enter a value of 3 ms. In a WAN environment, you might want to use a value of 100 ms to account for the distance between the systems. You must set this field to a value that makes sense for the type of network that you are testing.

Default: 100 ms

The default value displays as a goal line on the Average Network Response chart in the At-a-Glance report for VQM Path response elements. You can use the goal line to determine quickly whether your response time is under or over the expected time. The chart scales to include this goal line. If you select a value that is much greater than average response times for your network, the charts may not be useful. 8. Click Create to create the new path.

AdvantEDGE View adds the new path to the VQM configuration file (mosmod.cf) and displays a status message. If you receive a failure message, review the error and then attempt to add the path again. 9. Click Back to Voice Quality Monitor.

10. Repeat steps 5 through 9 in this procedure to create additional paths from this transmitter/receiver system and steps 3 through 9 to create paths from other transmitter/receivers.

Limits: You can create up to 100 paths from each transmitter/receiver.

(22)

Create Groups for VQM Path Elements

eHealth offers flexible grouping. Elements can belong to multiple groups, and groups can belong to multiple group lists.

After you have created and discovered Voice Quality paths and saved them to the Path/PVC Manager, you can group the elements to provide meaningful reports. For example, you can create one group for all VQM paths that originate from one transmitter/receiver or many groups of paths that originate from a single transmitter/receiver.

After you create groups, you can organize them into group lists and generate report data on an entire group list. The organization of VQM paths into groups is unrestricted, so these group lists can consist of groups that contain different types of elements or the same types of elements. For example, you could create a group list for the following:

Response groups that include VQM paths

LAN/WAN groups that include the WAN elements that carry VoIP traffic and

T1/E1 DS0 elements for voice gateways

Application groups

QoS groups that include QoS Class of Service (CoS) elements Remote Access groups that include voice gateways

To create groups for VQM path elements

1. Log in to the OneClick for eHealth console by opening a web browser and entering the following address:

eHealthSystem/OneClickEH

eHealthSystem

Specifies the name of the eHealth system that is installed. If your eHealth system is configured to run in a High Availability

environment, specify the shared hostname or shared IP address for your system rather than the specific eHealth system name.

The Connect to eHealthSystemName window appears.

2. Specify a user name and password of an administrator who has permission to access OneClickEH and then click OK.

The OneClick for eHealth page appears. 3. Click Launch OneClick for eHealth.

The File Download window appears. 4. Click Run.

The OneClickEH login window appears.

5. Log in to the eHealth server as an administrator who has permission to manage groups.

(23)

Create Group Lists

6. Click Managed Resources, Find Elements in the left pane. The Element Chooser window appears.

7. Select Element Chooser to filter the list.

Include a wildcard such as an asterisk (*) to match characters. You can sort by Element Type.

8. Select the jittermos elements that you want to include in the group, right-click, and select Create Group with Selected Elements.

The Create Group window appears.

9. Specify the group name and a description and then click OK. The group immediately appears under By Group.

10. (Optional) Repeat Steps 8 through 9 to create other groups.

The new groups appear in the console (under Managed Resources, select By Group).

Create Group Lists

After you create groups, you can add them to group lists.

To create a group list

1. Right-click By Group List in the Managed Resources folder and select New Group List.

The Create Group List window appears.

2. Specify a name and a description, and then click OK.

(Optional) You can enable the group list to be visible in the Business Service Console (BSC).

The window closes, the console refreshes, and the new group list appears in the left pane under By Group List.

3. Double-click the group list name under By Group List and select the Groups Not in Any Group List tab.

eHealth displays all groups that are not associated with an existing group list.

4. Select the groups of VQM elements from the list, right-click, and select Add Selected Groups to Group List.

eHealth adds the groups to the group list.

(24)

Create Profile Associations

If you are a Live Health administrator, you can use the Live Exceptions Browser to associate default Live Health profiles for monitoring VoIP environments with the groups and group lists that you create.

To create profile associations

1. Start the Live Exceptions Browser. 2. Select Setup, Subjects to Monitor. The Setup Subjects dialog appears. 3. Click New.

The Setup Subjects Editor dialog appears.

4. Select Groups orGroup Lists under Subject Type.

Depending on your selection, groups or group lists appear in the Subjects list.

5. Select Response from the Technology list. 6. Locate groups and group lists underSubjects.

7. Select one or more groups or group lists that you want to monitor. 8. Locate the profiles underProfiles.

9. Select the following profiles to associate with the group or group list:

VQM Response Path – Delay. This profile monitors availability and low

MOS ratings, which can indicate problems (delays, jitter, packet loss) in voice-traffic processing.

VQM Response Path – Unusual Workload. This profile monitors increase

in jitter, packet traffic and discards, and round-trip times, which can indicate unexpected or unusual capacity or changes in volume of traffic. 10. Select a calendar Under Calendars.

A time range is applied to the profile and subject pairs.

11. ClickOKto close the Setup Subjects Editor dialog box and then click OK again.

(25)

Copy and Modify the eHealth Voice Quality Monitor Template

Copy and Modify the eHealth Voice Quality Monitor

Template

eHealth provides three default SystemEDGE templates for monitoring VQM paths—one for each codec. Entries in the templates are disabled by default. You cannot modify the default template, but you can make a copy of it. You can then modify the copy to enable the existing entries and to create additional entries that send traps to your eHealth system if the MOS ratings start to degrade.

To copy and modify the eHealth Voice Quality Monitor template

1. Log in to the eHealth Web interface and open the AdvantEDGE View page.

2. Click the Administrationicon and then click the Template Administration icon.

The Existing SystemEDGE Templateslist appears. 3. Select eHealth Voice Quality Monitor.

The default template appears.

4. Click Copy Template, complete the Copy Template form, and click Copy Template.

The Existing Rules for the new template appear. 5. Do one of the following:

Edit an existing entry by clicking the pencil icon in the Edit

column next to the row that you want to edit in the top frame.

Important! Editing VQM parameters should be done only under the

direction of CA Technical Support. You must satisfy certain mathematical constraints or the data will be meaningless.

Add new entries by selecting the type of monitoring directive that

you want to add in the Add a New field and then clicking Add in the bottom frame.

6. Complete the Edit Monitor Row form that appears and then click one of the following:

Save Row

Saves the row that you were editing

Delete Row

Deletes the row that you selected

Save Template Changes

Saves all changes that you have made to the template

Cancel Edits

(26)

Apply the eHealth Voice Quality Monitor Template

After creating a new template, you can apply it to the systems that you want to test.

To apply the template to a system

1. Access the AdvantEDGE Viewpage.

2. Select Template Configuration from the Configuration list and the system to which you want to apply the template from the System list. 3. Click the Configurationicon .

4. Select the template you created (in the previous procedure) from the ‘Templates available for installation’ list and then click Apply Selected Templates.

Perform Operational Testing for VoIP

For a general check of VoIP service quality, you can use eHealth Voice Quality Monitor to continuously monitor of commonly used voice quality paths in the background. To perform this task, you must create voice quality paths between two VQM modules, poll them over time to collect data on jitter and MOS, and then correlate changes in MOS ratings to network and system events.

To perform operational testing for VoIP

1. Configure your environment for Voice Quality testing by completing the procedures described in the previous sections of this document.

2. View the AdvantEDGE View Voice Quality and Voice Quality Path reports. These reports provide information about the MOS ratings for these paths and other performance data.

To view the reports, do the following:

a. Select the transmitter/receiver system from the System list in AdvantEDGE View.

b. Select Voice Quality Monitor from the Applications list. c. Click the Applicationsicon .

AdvantEDGE View displays the Voice Quality Report for this system. (If Voice Quality paths do not exist for this system, the report does not contain data.)

(27)

Perform Operational Testing for VoIP

d. (Optional) Click Enable AutoRefresh to obtain automatic, real-time updates of the MOS ratings.

(28)

Perform Capacity Planning for VoIP Environments

3. (Optional) View SystemEDGE monitoring information for the VQM paths as follows if you created and applied a new template for monitoring VQM paths:

a. SelectSelf Monitoringfrom the Configuration list in AdvantEDGE View and select the system or group to monitor from theSystem or Group list.

b. Click the Configuration icon .

The Monitor Table Information page appears and provides information about the variables that the template instructed the agent to monitor.

4. Use the Live Exceptions Browser to view alarms and drill down to more information about them by right-clicking the alarm and selecting Event Information.

5. Run At-a-Glance, Trend, and Top N reports for the elements on this path.

Specify Response Path under Technology Type and select the paths on which you want to report.

You can run this test continuously to test the performance of your network. The test, however, uses network bandwidth while it is running.

More information:

Delete or Disable Tests on page 30

Perform Capacity Planning for VoIP Environments

You can use eHealth Voice Quality Monitor to determine whether your network has enough excess capacity to handle VoIP traffic, how much VoIP traffic it can handle, and the associated resource usage. To obtain this information, you create tests across a link, increase the number of tests over time until the MOS degenerates, and then use this value to determine optimal settings.

To perform capacity planning for VoIP

1. Configure your environment for Voice Quality testing (as described in the previous sections of this document).

2. Enable Flood Mode for the VQM module as follows:

a. Open the Voice Quality configuration file (mosmod.cf_{) on the} SystemEDGE agent machine in the following location:

drive:\sysedge\plugins\mosmod

(29)

Perform Capacity Planning for VoIP Environments

Flood Mode synchronizes all Voice Quality tests from a single transmitter/receiver to enable them to run in parallel.

c. Restart the SystemEDGE agent by using the SystemEDGE Control Panel.

3. (Optional) View SystemEDGE monitoring information for the VQM paths as follows if you created and applied a new template for monitoring VQM paths:

a. SelectSelf Monitoringfrom the Configuration list in AdvantEDGE View and select the system or group to monitor from theSystem or Group list.

b. Click the Configuration icon .

The Monitor Table Information page appears and provides information about the variables that the template instructed the agent to monitor.

4. View the AdvantEDGE View Voice Quality and Voice Quality Path reports (as described in step 2 of the previous procedure).

5. (Optional) Modify the paths that you created by increasing their traffic rates, the number of paths between each transmitter/receiver and reflector systems, or both.

6. Run the Voice Quality and Voice Quality Path reports again.

To modify a path, click the pencil icon in the Index column of the Path Configuration Overview table, complete the Modify Voice Quality Path form, and click Modify. Check the codec to be sure that the data rate matches the bit rate of the test. Keep in mind, that the time it takes the test to run must be less than the test cycle time. If the test is scheduled to run every minute, the test needs to end before the next cycle begins. 7. Run the discover process by using Response Elementmode after you

create or modify paths.

8. Use the groups of VQM paths that you created and run Top N reports on WAN link utilization and related variables for the links on which you would run VoIP traffic.

This report will indicate which systems might create bottlenecks for your VoIP traffic.

9. Use AdvantEDGE View to create additional Voice Quality paths between two systems on opposite ends of any bottleneck links that you identified with the Top N report.

10. Repeat steps 7 through 9 until the report displays MOS ratings that are unacceptable.

This information indicates the limit on the amount of traffic that the link can support.

11. Run At-a-Glance and Trend reports for these VQM paths (by selecting Response Pathas the Technology Type) to obtain additional information about the elements and groups.

(30)

Delete or Disable Tests

12. Delete or disable the Voice Quality paths that you created for testing purposes.

13. Disable Flood Mode as follows:

a. Open the VQM configuration file for editing.

b. Replace the pound sign [#] in front of the flood_mode line and then save and close the mosmod.cf_file.

c. Restart the SystemEDGE agent by stopping and starting the SNMP Service in the Windows Control Panel.

Discover VQM Systems on page 19

Create Groups for VQM Path Elements on page 22

Delete or Disable Tests

Delete or disable your operational and capacity planning tests when you are no longer using them. (You may want to run operational tests over a defined period, but you should delete your capacity planning tests as soon as you have obtained the necessary data so that the tests do not interfere with the operation of your VoIP network.) If you may want to use the tests again, disable them so that you will not have to recreate them.

To delete or disable a test

1. Log in to the eHealth Web interface.

2. Access the System list in AdvantEDGE View and select the transmitter/receiver system for the tests that you want to delete. 3. Select Voice Quality Monitor from the Applications list.

4. Click the Applicationsicon .

AdvantEDGE View displays the Voice Quality Report for this system. 5. Click the pencil icon for the test that you want to delete or disable.

The Modify Voice Quality Path form appears. 6. Select one of the following from theStatus list:

destroy(6)

Deletes the tests.

notInService(2)

(31)

Delete or Disable Tests

You can reactivate a disabled test by repeating this procedure and selecting active(1)in the Status column. To begin polling the path again, you must run the discover process from the eHealth console after you set the status to active.

8. Use the eHealth console to delete or retire this response path from the Path Manager as follows:

a. Select Setup, Poller Configuration on the eHealth console. The Poller Configuration dialog appears.

b. Select Path/PVC Manager.

The Path/PVC Manager dialog appears. c. Click Response Path under Elements of Type.

The response paths appear.

d. Select the paths that you want to delete or retire from the Element Name list and then do one of the following.

Click Delete and then click Delete again on the Confirm Delete

dialog.

Click Retire and then click Yeson the Confirm Retirement dialog.

When you retire an element, eHealth retains the data for the element but does not collect new data for it. You can include retired elements in reports until the data ages out or until you delete them.

e. Click OK in the Path/PVC Manager dialog.

f. Rerun the discover process and specify Response Elementsmode.

Note: For more information about using eHealth Voice Quality Monitor to

monitor your VoIP environment, see the eHealth Help.

(32)

(33)

Index 33

Index

A

AdvantEDGE View Agent Deployment • 18 AdvantEDGE View, using • 18

Application Insight Module (AIM) • 15 Applications icon • 19, 26, 30

apply the eHealth VQM template • 26

C

capacity planning, in VoIP environments • 28 Cisco CallManager (CCM) • 7

Cisco Service Assurance Agent (SAA), router support for • 7

codecs, specifying • 18 collectors • 9

Configuration icon • 26, 28, 29

copying and modifying VQM templates • 25 Create Group List window • 23

Create Group window • 23 creating

group lists • 23

groups for VQM path elements • 22 Voice Quality paths • 19

D

deleting or disabling operational and capacity planning tests • 30

deployment and discovery of VoIP resources eHealth for Voice • 9

LAN switches • 11 network interfaces • 11 process • 7

requirements and tips • 9 routers • 10 voice gateways • 11 VQM systems • 10 dialogs Discover • 19, 21 Discovering • 19 Path/PVC Manager • 21, 31 Poller Configuration • 21, 31 Setup Subjects • 24

Setup Subjects Editor • 24 Discover dialog • 19, 21 discovering VoIP resources • 9 VQM systems • 19 Discovering dialog • 19

E

eHealth – E2EConsole package, licensing • 16 eHealth for Voice

deploying • 9 licensing • 13

eHealth requirements for deploying and discovering VoIP resources • 9

eHealth Status Summary window • 22 Element Chooser window • 23

F

File Download window • 22 Flood Mode, disabling • 30

G

group lists, creating • 23

groups, creating for VQM path elements • 22

I

icons Applications • 19, 26, 30 Configuration • 26, 28, 29 magnifying glass • 27 pencil • 25, 30

(34)

J

jitter, testing • 14

jitter/MOS path configuration, specifying parameters • 18

jitterMos-RD suffix • 19

L

LAN switches

deployment and discovery requirements • 11 license requirements • 15

license requirements eHealth for Voice • 13 for reporting • 16 for technology • 16 LAN switches • 15 Live Health • 16 network interfaces • 16 reporting • 16

routers (including QoS enabled) • 14 systems • 15

technology • 16 voice gateways • 14

VQM and MOS systems • 13 licensing VoIP resources • 13 Live Health

creating profile associations • 24 license requirements • 16

M

magnifying glass icon • 27 Mean Opinion Score (MOS) • 13

monitoring • 7

Microsoft SQL Server, in an eHealth for Voice environment • 9

N

network interfaces

P

Path/PVC Manager dialog • 21, 31 pencil icon • 25, 30

Poller Configuration dialog • 21, 31

Public Switched Telephone Network (PSTN) • 7

Q

QoS Class of Service (CoS) elements • 22

R

reflector, for VQM systems and MOS • 10 reflectors • 18

Remote Access Service (RAS) • 7 reporting, license requirements • 16 routers

S

Service Assurance Agent (SAA) • 10, 14 setup prerequisites • 18

Setup Subjects dialog • 24 Setup Subjects Editor dialog • 24 SystemEDGE agent

deploying • 18 installing • 7, 18

systems, license requirements • 15

T

T1/E1 DS0 interface • 15

technology, license requirements • 16

testing (operational), performing for VoIP • 26 tests (operational and capacity planning), deleting or disabling • 30

(35)

Index 35

V

voice gateways

Voice Quality Monitor (VQM) systems

deployment and discovery requirements • 10 discovering • 19

license requirements • 13 setup in an IP WAN • 17 Voice Quality Monitor template

applying • 26

copying and modifying • 25 Voice Quality Path form • 20

Voice Quality paths, creating • 19 Voice Quality Report • 20

VoIP environments, capacity planning • 28 VoIP resources

deployment and discovery process • 7 licensing • 13

W

windows

Create Group • 23 Create Group List • 23

eHealth Status Summary • 22 Element Chooser • 23

(36)