Skip to content
DromlikDocs
sv

Use the IP Ping tool

Last updated: 2026-08-04

IP Ping tests whether your Dromlik system can reach a given hostname or IP address, and how long the round trip takes. It is built on ICMP and is usually the first check to run when something on the network is not reachable or call quality has degraded.

When to use IP Ping

  • Reachability — confirm the system can reach a trunk provider, an IP phone, a CRM host, or a DNS name.
  • Call quality — echo, buzzing, or latency during calls often shows up as high or unstable round-trip times and packet loss.

Run a ping test

  1. 1

    Open the tool

    Go to Maintenance > Troubleshooting > IP Ping in the admin console.

  2. 2

    Enter the target

    In Target Host, type the domain name or IP address you want to test.

  3. 3

    Start the test

    Click Start. Results stream into the output panel as each reply arrives.

  4. 4

    Stop when you have enough data

    Click Stop. For quality troubleshooting, let it run for at least 30–60 seconds so the statistics are meaningful.

Read the output

A successful ping

PING 192.168.6.11 (192.168.6.11): 56 data bytes
64 bytes from 192.168.6.11: seq=0 ttl=64 time=8.853 ms
64 bytes from 192.168.6.11: seq=1 ttl=64 time=0.778 ms
64 bytes from 192.168.6.11: seq=2 ttl=64 time=1.394 ms

--- 192.168.6.11 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.778/3.675/8.853 ms
  • Three packets were sent and all three came back — 0% packet loss.
  • Each packet is 64 bytes.
  • ttl is the remaining time-to-live; a consistent value means packets follow the same path.
  • time is the round-trip time. Rising or erratic values point to congestion.

A failed ping

PING 192.168.7.2 (192.168.7.2): 56 data bytes

--- 192.168.7.2 ping statistics ---
60 packets transmitted, 0 packets received, 100% packet loss

Nothing came back. Either the connection to the target is broken, or the target device is down or is blocking ICMP.

Interpreting the numbers

ResultWhat it usually means
0% loss, stable time under ~50 msHealthy path — look elsewhere for the fault.
0% loss, times swinging widelyJitter. Expect choppy audio; check for congestion or a saturated uplink.
1–5% lossAudible gaps and clipping on calls. Investigate the link.
100% lossNo route, host down, or ICMP blocked by a firewall.

If ping shows loss but you need to know where on the path it happens, use the Traceroute tool.