Quick Start User Guide 12909-02

Quick Start VoIPCare User Guide 12909-02

BroadSoft PacketSmart 2010 Confidential Materials Page 1

Quick Start

User Guide

For PacketSmart

VoIPCare GUI



Table of Contents Page

1. Introduction 3

2. Launching the PacketSmart GUI 3

2.1 Logging in 4

2.2 Your Login Credentials 4

2.3 Understanding the GUI 5

3. How to read Traffic Flows 6

4. Requesting reports 7

5. Explanation of Reports 11

5.1 Verification Report 11

5.2 VoIP SLA Report 14



1. Introduction

This quick start user guide will provide steps on how to access the PacketSmart GUI via the web

and also how to read traffic flows and generate reports from the GUI.

By having monitoring micro-appliances deployed you will be able to see VoIP calls and generate

reports on your network. The GUI offers these functions to proactively manage the

performance of your network. The list of these attributes is provided below:

• Measures any Packet Loss

• Provides packet per second performance measurements

• Measures any jitter

• Measures any latency

• Provides Summary MOS scores

• Measures packet usage

• Provides traffic isolation between LAN and WAN measurements

• Provide on-demand and daily network performance reports

2. Launching the PacketSmart GUI

BroadSoft PacketSmart’s PacketSmart GUI application is the way you will interact with the

PacketSmart server which will provide the data collected by micro appliances.

NOTE: The PacketSmart GUI is a Java application that will run on any computer – Windows,

Linux or Mac - with Java Runtime Environment (JRE) installed. Please ensure that you have at

least version 4.2 installed. You can download the JRE from here:

http://www.java.com/en/download/index.jsp

Once the JRE has been installed, you can download BroadSoft PacketSmart’s GUI Application

from here: http://admin.packetisland.net:8080/gui.jnlp,

While you can launch the PacketSmart GUI from this link each time, it is probably more

convenient to save the application locally on your computer so some of the basic settings are

preserved from session to session.

NOTE: Due to variations of implementation of JRE for different OS, the appearance of the GUI

application windows may vary slightly from the examples that will be shown below.



2.1 Logging in

When you launch the PacketSmart GUI application, you will be greeted with a log-in pop-up

menu as shown in Figure 1.

Figure 1

2.2 Your Login Credentials are the following:



Figure 2

2.3 Understanding the GUI

After a successful log-in, the GUI will display the main window of the PacketSmart GUI as

illustrated in Figure 3.



Figure 3

The GUI consists of two sides, the left side represents the micro-appliances that are provisioned

on the PacketSmart Enterprise server and the rest is the VoIPCare analyzer screen. The GUI

screen provides a calendar field at the top which allows you to select data 30 days in the past.

The top tabs provide Call Metrics, Signaling Records, Traffic Flows, Packet Capture (not offer

with VoIPCare), VoIP Nw Eval and Video (Not offered with VoIPCare) Control and Reports.

When selecting any micro appliance you need to highlight the name on the left side and select

the device’s MAC address. Once you have a selected device that is connected to the

PacketSmart server, you will be able to engage the top tabs. Figure 4 represents that example.



Figure 4

3. How to read Traffic Flows

By clicking on the traffic flow tab you can view a 24 hour period of time with data representing

Kbps and Pps across the network. An example of that chart is found in Figure 5.

Having the ability to view real-time data across your network allows you to pinpoint high usage

areas and any potential congestion points within your network. Two key areas that are

valuable are the amount of bandwidth that is provided on the WAN connection and secondly

the router or Ethernet switch capacity to process packet per second (pps). Both charts above

provide the information necessary to determine whether you are exceeding your network

capabilities and possibly impacting real-time applications.

With the micro appliance in line or off a monitor/span port you are able to capture all packets

to provide the necessary performance data analysis required to address transient issues, like

TCP/IP vs. UDP). This in-line monitoring is available 24/7 on a (SIP Based) analysis.



Figure 5

This chart above shows a 24 hour period of time showing bandwidth usage, source and

destination IPs, ports used, protocol types and each applications use of bandwidth across the

network. Having the ability to see data applications used allows you to determine whether

there is misuse of bandwidth or even data threats.

Because we store all data for 30 days, it is important when checking any tests or traffic flows

you have selected the correct date on the Date Navigator Bar at the very top of the

PacketSmart GUI window and that the correct micro appliance is selected on the left.

4. Requesting reports

The reports requested from the GUI are dispatched and generated typically within an hour of

the request.

In Step 1, select the report tab and move to SUBMIT NEW REQUEST on the GUI screen. Figure 6

shows the GUI screen and the two reports available VoIP Verification and VoIP SLA.



Figure 6

To request a VoIP Verification report you’ll be required to have live VoIP calls to a call target,

like another IP phone or PSTN phone number. These calls would appear in the Call Metrics tab.

Step 2, the text boxes Report Provider, Customer Name are used to create the title page of the

report, so please enter what you wish.

Next, you can select the time zone that the report will use. This usually means the time zone of

the SMB location, but you may use any time zone that is convenient.

Finally, name the report under the “Report Description/Comments” section and don’t forget to

include an email address – this will be used to send you a link where you can download the

report. You will need to use the same user and password as for the GUI to have access to these

reports. See figure 7.



Figure 7

In Step 3, submit report request to notify our PacketSmart to generate your report request.

Listed below Figure 8 is where you would check to see if your report was generated and

completed.



Figure 8

Just like the verification report request you can submit a VOIP SLA report. Just select VoIP SLA

and proceed to with the same steps as the Verification report with the exception of verification

targets. See Figure 9.

Figure 9

5. Explanation of Reports

When interpreting any report always review with your Service Provider or ISP provider.

5.1. Verification Report

Verification reports are used to validate any new VoIP implementation after the install.

Verification reports provide immediate proof of a solid installation and that each IP phone is

correctly configured and working properly. Some of the key components are the following:



Figure 10



Figure 11

The most important piece of the report is the individual results on each IP Phone. Listed below

is an example of that detail.



Figure 12

Recommendations on Verification Report

If any IP Phone has failed to meet your baseline criteria the above chart would show a poor

MOS score, possibly packet loss and jitter reading on the individual call. To resolve this poor



test result you could call a different target to make sure the far end test point is not the issue.

Another troubleshooting step would be to confirm the IP phone configuration is the same as

any other IP Phone that passed.

The area to check would either a firewall or edge router settings to validate the configuration

are set to support QoS on all VoIP calls.

5.2. VoIP SLA Report

The VoIP SLA report provides performance feedback on all live VoIP calls that the Micro-

Appliance is sniffing. Listed below are the features of the VoIP SLA report.



Figure 13

The purpose of running a VoIP SLA report is to identify problem areas like packet loss, jitter,

dropped calls, and WAN congestion points. Listed below is the detail you receive on any call

that is below a MOS score of 3.2 or has detected RTP stream loss (Dropped Call).



Figure 14

Typically issues that cause these conditions:

1. QoS has not be configured on edge router

2. Local loop facilities do not support QoS

3. Firewall is not configured correctly to support VoIP calls

4. ISP or Service Provider circuit does not have sufficient bandwidth

5. Concurrent call levels have been exceeded

6. Edge router congestion due to small buffer memory or packet handling

7. Bad IP phone if all calls point to one IP address

8. Bad trunk route to terminating location exceeds recommended latency

measurements

9. LAN switches not configured correctly to support both data and VoIP together

10. Hubs deployed without prior knowledge

11. Data cabling is not adequate to support new applications

12. Route flaps occurring in the network

13. High jitter in LAN

14. High packet loss in LAN



Customer Support Services

BroadSoft PacketSmart’s Customer Support Services is available to be of service to you.

Please contact our professional VoIP experts to assist you.

Our contact information:

Customer Support Services

Phone: (877) 322-9888 Option 2

Email: [email protected]

Documents

Quick Start User Guide 12909-02