---
title: "What debugging tools are available in a mobile softphone SDK?"
topic: "Troubleshooting"
updated: 2026-05-06
canonical: https://acrobits.net/resources/knowledge-base/softphone-sdk-debugging-tools/
summary: "Softphone SDKs include SIP message tracing, packet capture, call quality metrics, and diagnostic logs. Cloud Softphone adds operator-level debugging without requiring Wireshark on end-user devices."
---

# What debugging tools are available in a mobile softphone SDK?

> Softphone SDKs include SIP message tracing, packet capture, call quality metrics, and diagnostic logs. Cloud Softphone adds operator-level debugging without requiring Wireshark on end-user devices.

When a VoIP call fails, the problem could be anywhere — [SIP](/voip-glossary/sip/) registration, [NAT traversal](/voip-glossary/nat-traversal/), codec negotiation, network quality, or OS-level audio routing. **Debugging tools** in a softphone SDK help you isolate the issue without guessing.

## Standard Debugging Tools

### SIP Message Tracing

Records every SIP INVITE, 200 OK, BYE, and error response. This is the first thing support engineers check. Most softphone SDKs include built-in SIP logging that can be exported as a text file.

### Packet Capture

Captures network packets sent to and from the softphone — SIP signaling and RTP media. Useful for diagnosing NAT issues, firewall blocks, and codec mismatches. Export as **pcap files** for analysis in Wireshark.

### Call Quality Metrics

Real-time and post-call statistics: **jitter, packet loss, MOS score, round-trip latency**. These tell you whether the problem is the network, the codec, or the endpoint.

### Registration Logs

Track SIP REGISTER attempts, responses, and timeouts. Identifies authentication failures, DNS resolution issues, and server-side rejections.

### Audio Diagnostics

Detect which audio device is active (earpiece, speaker, Bluetooth), whether echo cancellation is engaged, and whether the OS is routing audio correctly.

## External Tools

  - **Wireshark** — open-source protocol analyzer for pcap files. The standard for SIP/RTP debugging.

  - **VoIPmonitor** — open-source live network sniffer for SIP + RTP with web interface.

  - **SIP Workbench** — graphical SIP/RTP/STUN/TURN protocol analyzer.

  - **sngrep** — terminal-based SIP message flow visualization.

## What Cloud Softphone Provides

**[Cloud Softphone's SDK](/acrobits-sdk/)** includes debugging tools designed for operators — not just developers:

  - **Built-in SIP logging** — full message trace exportable from the app without connecting to a computer

  - **Call quality reports** — per-call metrics (jitter, loss, MOS) visible to the operator, not just the end user

  - **Diagnostic export** — one-tap log export that bundles SIP traces, registration logs, and system info into a single file for support

  - **Remote debugging** — operators can request diagnostic data from end-user devices without requiring the user to run Wireshark or packet capture tools

  - **Push notification diagnostics** — track whether push tokens are valid, whether notifications were delivered, and where in the chain a failure occurred

This matters because your end users are not network engineers. They can't run Wireshark. Cloud Softphone puts the debugging tools in the operator's hands.

**Debug VoIP issues without burdening end users.** [Learn about Cloud Softphone's SDK](/cloud-softphone/). When the failure is a call that never rings, see [why a SIP app stops ringing in the background on Android](/resources/knowledge-base/sip-background-ringing-android/).

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What debugging tools are available in a mobile softphone SDK?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Softphone SDKs include SIP message tracing, packet capture, call quality metrics, and diagnostic logs. Cloud Softphone adds operator-level debugging without requiring Wireshark on end-user devices."
      }
    }
  ]
}