THE VOICE OVER IP FIELD DESK

Plan the capacity.
Understand the conversation.

Estimate bandwidth, interpret call statistics, and find a sensible next step when the audio is not right.

01

MODEL YOUR CALLS

Bandwidth Calculator

Link and Additional Overhead

Use a verified allowance for SRTP tags, RTP extensions, or encapsulation. Do not count the same header twice.

Continuous audio, one stream each way per call. The 25% starting margin is illustrative—not a universal standard. Confirm the packet interval your endpoints support.

02

CAPACITY PER DIRECTION

Your Bandwidth Plan

↑ Upload / with added margin1 Mbps
↓ Download / with added margin1 Mbps

Each direction needs its own capacity. Do not compare a doubled total against upload alone.

Per Call / Per Direction
80 kbps
Packets / Second / Stream
50
Payload / Packet
160 bytes
Modeled Overhead / Packet
40 bytes

Where the capacity goes

Audio payload0.64 Mbps
Modeled overhead0.16 Mbps
Added margin0.2 Mbps

10 calls × 80 kbps × 1.25 ÷ 1,000 = 1 Mbps per direction

G.711 · IPv4 · 20 ms packets · 0 link-layer bytes + 0 additional bytes per packet.

Capacity is not a call-quality test. Signaling, RTCP, video, redundancy, competing traffic, and any unmodeled overhead still need allowance. No traffic is generated to test your phone system.

03 / OBSERVE, THEN INTERPRET

Put Call Metrics in Context

Enter readings from your phone, softphone, monitoring system, or an authorized test. Blank fields remain unknown; this page does not measure the media path.

Use the same call interval and direction for comparable readings. Do not enter account details, phone numbers, or customer information.

Your observations belong here.

Enter measured values above, or explore the explicitly labeled example. No invented live readings, MOS score, or connection certification.

Reference targets: one-way delay below 150 ms, jitter below 30 ms, loss below 1%. Read their limitations and sources →

Local Tools. Shared Fair-use Limits.The calculators work in this tab; their inputs are not sent to our server.
60 Requests / Minute / IPPages, assets, CLI and API requests share the server allowance.
CLI / API Guide →

FIELD NOTES

Make the next check useful.

Choppy or robotic audio

Compare the affected call’s loss and jitter with a known-good interval. A fast download is not evidence of stable media delivery.

One-way audio

Separate device and mute checks from media routing, NAT, and firewall investigation. Do not broadly open ports.

Delay or echo

Separate timing problems from acoustic feedback. A headset is a useful isolation test; ping is not mouth-to-ear delay.

Open the Field Checklist →

TERMINAL FRIENDLY

Your Public IP. One Command.

Get the source address seen by this service, with no banner or markup in the response.

Terminal
curl aboutvoip.info

The bare command uses HTTP. Use https://aboutvoip.info for encryption. Your web connection may follow a different path from a desk phone or SIP trunk.

curl, PowerShell and JSON Examples →

HARDWARE / TEXT-ONLY EXAMPLES

Match the endpoint to the call path.

Three neutral examples for recognizing the role of a desk phone, a DECT handset system, and a headset. Examples are listed alphabetically, not ranked. Manufacturer references support the explanations; the Amazon link is clearly marked as a paid link.

Read the hardware guide →

Desk SIP phone

Poly Edge E220

A wired desk endpoint with two gigabit Ethernet ports and IEEE 802.3af PoE support. Its setup still depends on a provider or PBX that supports the device and its provisioning method.

For call-quality work, record the phone, media direction, and affected interval before changing network settings. Read the call-statistics field note →

Cordless IP/DECT handset system

Snom M70 + M900

The M70 is the handset; it registers through a compatible DECT base. This example pairs two components, not a guaranteed retail bundle. The M900 is a multicell base, so base placement, coverage, handset compatibility, and the provider or PBX configuration are separate checks.

For a roaming or coverage complaint, separate handset, wireless coverage, and media-path evidence. Read the troubleshooting field note →

USB / Bluetooth headset

Yealink BH70

A Bluetooth headset for a computer or supported phone accessory workflow, with USB-A or USB-C dongle variants and UC or Teams variants. It is not a SIP phone; confirm the exact variant and call-control support with the calling platform.

For echo, feedback, or low volume, use a headset as one controlled isolation step rather than a diagnosis. Read the troubleshooting field note →

As an Amazon Associate I earn from qualifying purchases.

Paid link: Amazon — Yealink BH70 Dual Teams USB-C/A (opens in a new tab)

BUILD YOUR FIELD KNOWLEDGE

Useful Before, During, and After a Call.

KEEP EXPLORING

Useful Internet Tools

A little curiosity goes a long way. Find your next useful tool or plain-English guide.

13 more places to explore

Part of our independent learning network Browse a topic. Learn something useful.