• Home
  • Troubleshooting

Use PingPlotter to Diagnose Network Issues

Written by Marissa Orsini

Updated at November 7th, 2024

Contact Us

  • The Essentials
    FAQs Forms
  • Announcements
    Carrier Events mFax Events Platform Events Release Notes
  • Billing Administration
    Datagate OneBill
  • Faxing
    mFax - Analog mFax - Digital Native Fax
  • Hardware & Software
    Manual Configuration Provisioning NDP Axis Cisco Fanvil Grandstream Polycom Snom Yealink Mobile Applications Desktop Applications Mobile-X SNAPbuilder TeamMate Connector UC Integrator
  • Hosted Voice
    Auto Attendants Branding Call Queues Call Routing CDRs Conferencing E-911 Features Fraud Integrations Inventory / Phone Numbers Local & Toll Free Porting Onboarding Recommendations SNAP.HD SIP Trunking SMS / MMS Users Voicemail Caller ID
  • Troubleshooting
    VoIPmonitor Firewalls PBX
  • Ray's Stuff
+ More

Table of Contents

Install PingPlotter Configuring PingPlotter Exporting Data Interpreting PingPlotter Results Check for packet loss. Check for latency. Follow the pattern to the source.

Scope:

This document will show you how to run a ping towards our SIP servers and export the data. This application is used to see if there latency or packet loss within the network or ISP. Data can explain why you may be experiencing call quality issues.

 

Requirements:

  • Install PingPlotter (Has a 14 day free trial) 
     
  • Workstation/Server on the same local network as endpoints.
 

Install PingPlotter

  1. Download PingPlotter here
  2. Install and select the option for the 14 day trial.

Configuring PingPlotter

  1. Set Enter target name or IP to one of our servers (see IP Addresses and Ports)
  2. Press the Play button and let it run for 4 hours during work hours.

Exporting Data

  1. Click Pause icon.
  2. Click File.
  3. Click Export Sample Set.
  4. Save it on your computer.
  5. Email it to support for troubleshooting.

Interpreting PingPlotter Results

Understanding PingPlotter graphs begins with the final destination — that's the target you're testing. PingPlotter represents the final destination with the bottom row of the trace graph.

Check for packet loss.


Take a look at your PingPlotter results. Do you see a red bar? If so, that means some data was lost between your computer and the target. This effect is known as packet loss, and if you're seeing it on the final destination, there's a good chance you captured a problem.

Check for latency.


What about the black line? It shows how long it takes data to travel to your target and back. This measurement is known as latency. It's another network problem indicator. The further to the right the black line is the longer it takes for data to travel around the network. If you see high latency on your final destination, you've probably captured a network problem.

Follow the pattern to the source.


When you have an idea of what's happening at the final destination, it's time to look at the rows leading up to the final destination. Do you notice any patterns leading up to the final destination?

Where the pattern begins, helps you understand the source of the problem. If the pattern starts on the first row in the graph (your router), you're probably dealing with a local network problem.

If the pattern originates somewhere in between the first and last row, the problem is probably outside your local network.

 

network pingplotter ping plotter

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Troubleshooting Not Provisioned e911
  • Troubleshooting Outbound Calls Marked as Spam
  • IP Addresses & Ports
  • Network Configuration Best Practices

Knowledge Base Software powered by Helpjuice

Expand