> ## Documentation Index
> Fetch the complete documentation index at: https://help.fieldpulse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting Dropped or Rough Engage Calls

> Run the built-in network diagnosis in FieldPulse Engage on web or mobile to test your connection and audio quality when calls drop or sound rough.

> **Who uses this:** Any user with access to Engage. **Availability:** Engage add-on, available in the United States and Canada; the network diagnosis runs on both web and mobile.

When [Engage](https://www.fieldpulse.com/features/engage) calls drop, cut out, or sound rough, run the built-in network diagnosis to see where your connection stands. The diagnosis tests your internet connection and call audio, then grades each result, so you can see which metric is dragging call quality down. Open **Engage Settings > Network Diagnosis** and select **Run Diagnosis** to get started.

## Overview

The Engage network diagnosis runs a test of your internet connection and call audio, then reports twelve metrics with a quality status next to each — excellent, good, average, poor, or bad. Engage is a VoIP phone system, so call quality depends on your network: bandwidth, jitter, packet loss, and the type of connection all affect how a call sounds. Running a network diagnosis in Engage shows which metric needs attention so you know what to fix.

## Run a network diagnosis

1. In Engage, go to **Engage Settings > Network Diagnosis**, located at the bottom left of the menu.
2. Select **Run Diagnosis**. Engage runs its tests and displays the results.
3. Speak aloud while the test runs so Engage can check your audio quality too.
4. Read the quality status next to each data point — excellent, good, average, poor, or bad.

<Frame caption="Video walkthrough: running a network diagnosis in Engage">
  <iframe src="https://www.loom.com/embed/8e90c8d0832e41689670096e62f6dc0e?hide_owner=true&hide_share=true" width="100%" height="420" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen />
</Frame>

## What each metric means

The diagnosis reports twelve metrics. Use the table to see what each one measures, the target to aim for where one applies, and what to do when the status reads poor.

| **Metric**                | **What it measures**                                                  | **Target**             | **If it's poor**                                                                                                        |
| ------------------------- | --------------------------------------------------------------------- | ---------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| **MOS Average**           | Average call quality, on a scale of 1 to 5                            | Greater than 4         | Upgrade your internet plan for more bandwidth; close apps that consume bandwidth.                                       |
| **Jitter Average**        | Variability in packet arrival times                                   | Less than 30           | Replace outdated networking hardware; reduce the number of connected devices.                                           |
| **RTT Average**           | Round-trip time for a signal to travel to the destination and back    | Less than 200          | Run regular speed tests; raise consistently high RTT with your ISP.                                                     |
| **Turn Used**             | Whether a relay server was needed to bypass NAT/firewall restrictions | —                      | Configure your network for direct peer-to-peer connections; temporarily adjust firewall settings.                       |
| **Edge**                  | The edge of the network, where user interactions occur                | —                      | Check edge devices for delays or malfunctions.                                                                          |
| **Network Type**          | Whether you're on Wi-Fi, Ethernet, 4G, and so on                      | Ethernet preferred     | Switch to a different network type to test whether connectivity improves.                                               |
| **MOS Max**               | The highest quality score observed during the test                    | —                      | Note what changed in your setup or environment when MOS scores drop.                                                    |
| **Jitter Max**            | The worst-case packet delay variability                               | —                      | Reset routers or switches to clear temporary congestion.                                                                |
| **Packets Lost Fraction** | Percentage of data packets lost in transmission                       | Less than 5%           | Ask your ISP about packet prioritization; add redundancy to data transmission; use apps with built-in error correction. |
| **Signaling Duration**    | Time taken to set up the network connection                           | —                      | Check for VoIP software updates or patches that improve signaling.                                                      |
| **ICE Duration**          | Time to establish a connection using ICE                              | —                      | Contact technical support to optimize ICE configuration settings.                                                       |
| **Protocol**              | The protocol in use, which affects data handling                      | UDP preferred for VoIP | Switch between TCP and UDP to see which performs better on your network.                                                |

## Tips

For steadier call quality overall:

* Use a high-speed internet connection, and choose wired Ethernet over Wi-Fi where possible — a wired connection is more stable and faster.
* Turn on Quality of Service (QoS) settings on your router to prioritize VoIP traffic.
* Keep the load on your network low during important calls, and test your setup beforehand to confirm it connects quickly.
* When the diagnosis reports a high MOS score, note the conditions — aim to replicate them for later calls.
* Keep your network configuration up to date to support faster ICE processing.
* For advanced setups, edge computing solutions process data closer to the source.

If call quality is poor on desk phones specifically, confirm your SIP connection and Yealink phone are configured correctly — see [Setting Up Engage via SIP (DID)](/add-ons/engage/sip-did) and [Setting Up a Yealink VoIP Phone](/add-ons/engage/yealink-voip).

## Still need help?

Reach the [FieldPulse support team](https://www.fieldpulse.com/company/contact-us) through in-app chat or at [support@fieldpulse.com](mailto:support@fieldpulse.com). Sharing your network diagnosis results helps the team give guidance tailored to your network environment.

## Related articles

* [Engage Overview](/add-ons/engage/overview)
* [Setting Up Engage via SIP (DID)](/add-ons/engage/sip-did)
* [Setting Up a Yealink VoIP Phone](/add-ons/engage/yealink-voip)
* [Troubleshooting Connectivity & Slow Loading](/troubleshooting/connectivity/connectivity-slow-loading)


## Related topics

- [Troubleshooting Engage Network Warning Messages](/add-ons/engage/network-warning-messages.md)
- [Troubleshooting Connectivity & Slow Loading](/troubleshooting/connectivity/connectivity-slow-loading.md)
- [Phone Number Format (E.164) Details](/add-ons/engage/phone-number-format.md)
- [Setting Up Engage via SIP (DID)](/add-ons/engage/sip-did.md)
