AI voice integration

Phone numbers for Vocode — SIP trunk setup with DIDHub

Vocode is an open-source voice agent framework. DIDHub provides the SIP trunk + DID inventory for production Vocode deployments — STIR/SHAKEN A-attestation on US outbound, multi-country reach, per-DID flat pricing.

Get a number for Vocode Visit Vocode →

Why DIDHub for Vocode

Open-source-friendly carrier. Vocode is open source; DIDHub plays cleanly via standard SIP without proprietary integration.
STIR/SHAKEN A-attestation. For US/CA outbound from Vocode agents.
136-country DIDs. Global Vocode deployments without juggling carriers.
Webhook events. Call lifecycle webhooks signed and retry-friendly.

BYOC setup — step by step

Sign up at /signup and provision DIDs.
Generate DIDHub SIP credentials.
In Vocode: configure your TelephonyServer with DIDHub as the telephony provider (Vocode's TelephonyConfig accepts standard SIP credentials).
Wire your Vocode agent's start_call / handle_call hooks.
Test inbound + outbound; validate audio quality.

Documentation note. Vocode's BYOC / SIP trunk configuration UI changes occasionally. The steps above reflect the current pattern at time of writing. If a screen has moved, the underlying values (SIP URI, credentials, allowed source IPs) are the same — check Vocode's docs for the latest UI path.

Caller-ID configuration

Set the DIDHub DID as Caller-ID in Vocode's outbound call config. DIDHub signs US/CA outbound with A-attestation.

For US/CA outbound: DIDHub signs every call with STIR/SHAKEN attestation A on DIDHub-allocated and DIDHub-ported numbers. This is the level that mobile carriers (T-Mobile, Verizon, AT&T) treat with baseline trust — calls signed with weaker attestation are increasingly flagged as “Spam Likely” or sent straight to voicemail. See STIR/SHAKEN explained for the full background.

For non-US destinations: present a local DID as Caller-ID for best answer rates. AI agent calling a Madrid customer should present a +34 (Spanish) Caller-ID, not a US number. DIDHub serves 136 countries with dedicated landing pages so you can match Caller-ID to destination.

Latency & regional ingress

Realtime AI voice is brittle to network latency — an extra 100ms of SIP egress can break the natural-conversation feel. DIDHub operates SIP/RTP edges in:

NOAM: Ashburn (US-East), San Jose (US-West), Dallas
EU: Frankfurt, Amsterdam
APAC: Singapore, Tokyo
MENA: Dubai

Pick the edge nearest to your Vocode inference region. Typical sub-50ms regional ingress for the closest pair. If you need a region we don't list, talk to [email protected] — we add edges in response to customer demand.

FAQ

Does Vocode support BYOC SIP?

Yes. Vocode is open source and can be configured to use any SIP carrier.

How does Vocode compare to Pipecat / LiveKit?

Vocode is more focused on phone agents specifically; Pipecat and LiveKit Agents are broader voice/multimodal frameworks. All three can work with DIDHub via SIP.

Is Vocode production-ready?

Vocode is used in production deployments. Validate the specific version + integration before scaling.

Can I record Vocode calls?

Yes — in Vocode itself or via DIDHub's call-recording feature on the carrier side.

Provision your first Vocode DID

Sign up at /signup, pick a country / area code, and route the DID to your Vocode BYOC SIP trunk. $1.99/mo for a US number, sub-60-second activation on most countries. No commits.

Ready to get a number?

Pick a DID in 130+ countries from $1.99/month. Activates instantly on most numbers.

Browse numbers Talk to sales