This page is a brand-neutral reference for the telephony terminology that appears in the rest of the docs. The “Where this maps to ClutchCall” section at the bottom links each concept area to the page that implements it.

Networks and origination

Trunks and carriers

Codecs and media

Transports — how the audio actually travels

A modern voice platform must know these four transports: WebRTC vs SIP — the rule of thumb:
  • Use SIP/RTP for the trunk side (carrier ↔ gateway). The PSTN does not speak WebRTC.
  • Use WebRTC for the last mile to humans in browsers or vendor SDKs (LiveKit, Daily, Chime, Vapi, Twilio Media Streams).
  • Use QUIC / WebTransport for server-side or browser control workloads. Choose them when the audio source is already-decoded PCM (for example, a TTS pipeline) and you want minimum framing overhead.

Call lifecycle and patterns

Routing and dialplan

Compliance vocabulary

Where this maps to ClutchCall

This table maps each section above to the page that implements it on this platform:

The four numbers that bound a voice deployment

Every sizing or capacity discussion comes back to these four numbers:
  1. CPS sustained (per trunk and aggregate).
  2. Concurrent channel ceiling.
  3. End-to-end latency (caller mouth → callee ear, in ms).
  4. MOS under typical packet-loss conditions.
Codecs, dialplan, AI bridges, and WebRTC interop all depend on those four numbers.