Niches · Phone calling & voice transport

Connect a phone number's calls to the agent's audio socket

Four or more companies' docs show a full fit.

4companies, full fit
10companies, fit with a limit
31companies carry the tag
24share of the category's work
12first-hand accounts

What counts as done

An inbound call to the number opens a bidirectional audio stream to the given URL, the stream's codec and sample rate are stated in docs and selectable, the called and calling numbers and a call id reach the socket as parameters, two calls at once get two independent streams, and audio sent back is heard by the caller.

Measured, for our own tests: first caller audio reaches the socket within 1 second of answer, and audio sent back plays at normal speed with no gaps over 200 ms across a 5-minute call. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: give my agent a phone number, stream the call audio to my websocket, hook my voice bot up to a real phone line, answer calls on this number with my agent

Does the job 4

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

ListingWhy
46elks Voice API E
46elks AB
Each call to a websocket number opens a new socket; hello carries callid, from and to; the agent picks pcm_8000, pcm_16000, pcm_24000, g722, ulaw and others with listening and sending messages, and audio goes both ways. Measured bar not published. source
Infobip Calls API + MCP B
Infobip Ltd
A WEBSOCKET call leg joined to the caller streams L16 at 8, 16, 24 or 32 kHz both ways, set per configuration, with up to 512 bytes of customData (numbers, call id) in websocket:connected; one socket per leg. Needs a calls configuration and subscription first. Measured bar unpublished. source
SignalWire Voice API B
SignalWire, Inc.
SWML connect to stream:wss:// gives a bidirectional stream with codec PCMU, PCMA, G722 or L16 at a chosen rate (for example L16@24000h), custom_parameters in the start message and the callSid. Trial projects take only verified numbers. Measured bar unpublished. source
Telnyx Voice API + MCP BB
Telnyx LLC
stream_url with stream_bidirectional_mode rtp and stream_bidirectional_codec PCMU, PCMA, G722, Opus 16 kHz, AMR-WB 16 kHz or L16 16 kHz; the start event carries from, to, call ids and client_state, and connections are Ed25519-signed. One stream per call. Measured bar unpublished. source

Does the job, with a limit 10

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
Bandwidth Voice API + MCP BB
Bandwidth Inc.
StartStream mode=bidirectional sends callId and up to 12 StreamParams in the start message, but call audio reaches the socket only as 8 kHz PCMU; 16 or 24 kHz PCM sent back is resampled to 8 kHz. Default cap 100 active sessions. source
didlogic Voice API D
DID Logic PTE. LTD.
A number destination with transport 12 streams each call to your wss:// URL, but the spec only says the endpoint must speak "the didlogic WebSocket call protocol"; no protocol page, codec, sample rate or call-context fields were found in the docs index or OpenAPI file. source
Exotel Voice API + MCP E
Exotel Techcom Private Limited
The Voicebot applet opens a bidirectional socket per call with call_sid, from, to and up to 3 custom parameters, and ?sample-rate=16000 or 24000 picks the PCM rate. The applet page also says all payloads are 8 kHz, so the docs disagree, and acc-31 hit a field-spelling mismatch. source
jambonz D
FirstFive8, Inc.
The listen verb streams L16 at 8, 16, 24, 48 or 64 kHz both ways, and the first text frame carries callSid and the call attributes plus custom metadata. jambonz sells no numbers, so the inbound call needs another carrier's trunk first. Measured bar unpublished. source
LiveKit Telephony BB
LiveKit Incorporated
Calls join a room as SIP participants and a dispatch rule starts the agent, rather than streaming to your socket URL; trunk media config picks PCMU, PCMA, G722 or AMR-WB. Phone Numbers are US only, and acc-19 and acc-20 hit missing dispatch and post-greeting silence. source
Plivo Voice API B
Plivo Inc.
Stream bidirectional=true with contentType audio/x-l16;rate=16000, audio/x-l16;rate=8000 or mulaw; the start event carries callId, streamId and extraHeaders for custom context. Free tier allows 2 concurrent calls and a new paid US account 5, above which calls fail with 5030. source
Sinch Voice API + MCP B
Sinch AB (publ)
A SVAML dial to a STREAM destination opens a bidirectional PCM socket at a chosen sampleRate (8000 to 96000), and ConnectRequest carries callId and arbitrary callHeaders. Voice API v2 is labelled preview, and a lost socket hangs up the call with no reconnect. source
Twilio Programmable Voice API + MCP A
Twilio Inc.
Connect Stream opens a bidirectional socket with callSid and custom Parameter values in start, one per call, but the documented media format is audio/x-mulaw at 8000 Hz only, which acc-03 blamed for poor recognition; acc-01, acc-02 and acc-11 hit dropped or silent streams. source
Vonage Voice API + MCP C
Vonage Holdings Corp.
An NCCO connect to a websocket endpoint picks audio/l16 at 8, 16 or 24 kHz and passes custom headers, with call uuid, from and to in websocket:connected. acc-12 saw replies randomly play at 4 to 8 times speed into the call. source
Voximplant C
Voximplant, Inc.
A VoxEngine scenario on the number calls sendMediaTo a WebSocket with encoding and customParameters set per stream, defaulting to PCM16 at 8 kHz; the call logic must be written as VoxEngine JavaScript first, and the full encoding list was not opened. 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 sends calls over SIP trunks only; the API v3 resource list has no call, stream or websocket resource. source

What stops agents finishing

  • only 8 kHz mu-law offered on the stream, which degrades recognition (acc-03, acc-30)
  • trial account answers only verified numbers
  • stream protocol fields documented differently from what the platform sends (acc-31)
  • a new paid account capped at a handful of concurrent calls

Around it

Before: voice-calling.get-number-in-country. After: voice-agents.inbound-receptionist, speech-to-text.voice-agent-live, text-to-speech.voice-agent-turn.

Where this comes from

Weight 24 of 100 in Phone calling & voice transport: 12 of 49 accounts, the largest group: Twilio Media Streams starter-repo issues and Stack Overflow questions about silence, dropped sockets, speeded-up audio and 8 kHz audio hurting recognition, plus Telnyx, Vonage and Exotel stream accounts

The same as data: /api/v1/use-cases/voice-calling.number-to-agent-stream.json, or the MCP tool get_use_case with id voice-calling.number-to-agent-stream. 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.