Niches · Phone calling & voice transport

Know a call's state for certain and end it from code

One company's docs show a full fit.

1companies, full fit
12companies, fit with a limit
26companies carry the tag
9share of the category's work
5first-hand accounts

What counts as done

Status events (ringing, answered, completed, failed, no-answer) are signed, retried when the endpoint is down, and carry an ordering field or timestamp; a hang-up and a cancel-while-ringing exist in the API; a call's live state can be read back by id so a missed webhook can be recovered.

Measured, for our own tests: after 20 test calls the provider's active-call count returns to zero and every call has precisely one final status event. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: hang up when the agent is done, tell me when the call ended, is this call still live, cancel the call if nobody answers

Does the job 1

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
Telnyx Voice API + MCP BB
Telnyx LLC
Webhooks are Ed25519-signed with occurred_at and attempt fields, retried, and documented as possibly duplicated or out of order with event ids for deduplication; call commands carry command_id. Measured 20-call bar unpublished. source

Does the job, with a limit 12

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
46elks Voice API E
46elks AB
whenhangup posts the end, GET /calls/{id} reads state, and a bye message hangs up. Callbacks are verified by IP allow list, not signed; no retry schedule or cancel-while-ringing found. source
Bandwidth Voice API + MCP BB
Bandwidth Inc.
Disconnect webhook, call read-back by id and hang-up through /calls/{callId} exist, but asynchronous callbacks are retried only once on a connection error and are not signed. source
didlogic Voice API D
DID Logic PTE. LTD.
Click2call webhooks carry event_seq for ordering and retry five times with backoff, and GET /api/v1/click2call/{id} recovers state. Webhooks are not signed, and no hang-up or cancel endpoint is in the spec. source
Exotel Voice API + MCP E
Exotel Techcom Private Limited
StatusCallback gives terminal and answered events and a Legs hangup action exists, but Exotel warns delivery may be delayed or fail and says to fall back to the Call Details API; no signature or retry schedule. source
Infobip Calls API + MCP B
Infobip Ltd
CALL_RECEIVED, ESTABLISHED, FINISHED and FAILED events with causes, CANCELLED states and call details by id exist; the subscription profile carries webhook security settings, but no retry schedule or ordering field was found. source
jambonz D
FirstFive8, Inc.
Webhooks can be signed, calls read, updated and deleted by REST, and a call count endpoint exists, but HTTP webhooks are not retried unless #rc and #rp are added to the URL, and acc-33 saw 245 phantom sessions after a FreeSWITCH crash. source
LiveKit Telephony BB
LiveKit Incorporated
Participants can be removed and SipCallError carries the SIP status, but cancelling a ringing call can drop a callee whose 200 OK crosses the CANCEL (sip 983, open), and no signed status webhook schedule was found in the telephony pages. source
Plivo Voice API B
Plivo Inc.
Hangup URL callbacks are signed and retried, and calls can be read, hung up and transferred by API, but duplicates must be handled, no ordering field was found, and status webhooks failed for 6.5 hours on 25 August (listing notes). source
SignalWire Voice API B
SignalWire, Inc.
calling.end hangs up a call by id and connect status callbacks report connecting, connected, failed and disconnected; no retry schedule or ordering field was found on the webhooks page. source
Sinch Voice API + MCP B
Sinch AB (publ)
Webhooks are signed, failed deliveries go to a fallback URL and must be deduplicated, GET /calls/{callId} reads state and PATCH can force a hangup; no ordering field or retry schedule beyond fallback was found. source
Twilio Programmable Voice API + MCP A
Twilio Inc.
An Update a Call resource exists for live calls, but the Calls resource and webhook retry pages were not read; acc-16 saw inbound calls arrive with a status that did not match what happened, and acc-32 left provider calls up once the socket closed. source
Vonage Voice API + MCP C
Vonage Holdings Corp.
Calls are read and modified at /v1/calls/:uuid, websocket disconnects send a status event with fallback options, and signed webhooks are available; retry schedule and ordering not found. source

Couldn't check 1

The docs were closed to us, or silent. These carry no mark either way.

ListingWhy
Voximplant C
Voximplant, Inc.
HTTP callbacks are indexed but their signing and retry behaviour were not read. source

Doesn't do this job 1

Listings in the category that do something else, with the reason.

ListingWhy
DIDWW Voice and Number Management API B
DIDWW Ireland Limited
DIDWW cannot hang up or read a live call through the API; calls are controlled by the customer's SIP system. source

What stops agents finishing

  • status callbacks not retried, or failing for hours (Plivo, 25 August 2026)
  • no API to read a live call's state
  • phantom sessions count against a concurrency cap (acc-33)

Around it

Before: voice-calling.number-to-agent-stream, voice-calling.place-outbound-call. After: voice-calling.record-and-retrieve, crm.log-activity.

Where this comes from

Weight 9 of 100 in Phone calling & voice transport: 5 of 49 accounts: a second inbound call dropping both, an agent that would not hang up, inbound calls arriving with a no-answer status, hang-up skipped once the socket closed, and 245 phantom sessions after a media-server crash

The same as data: /api/v1/use-cases/voice-calling.call-lifecycle-control.json, or the MCP tool get_use_case with id voice-calling.call-lifecycle-control. Other jobs in this category: /api/v1/niches?category=voice-calling.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.