Phone numbers for Deepgram Voice Agent — SIP trunk setup with DIDHub
Deepgram Voice Agent API bundles STT + LLM + TTS into one realtime stack. DIDHub provides the missing PSTN layer: SIP trunk + DID inventory + STIR/SHAKEN A-attestation. Voice agent in production end-to-end.
Why DIDHub for Deepgram Voice Agent
- Deepgram has the agent stack; DIDHub has the PSTN. Clean division of responsibilities: Deepgram does STT/LLM/TTS, DIDHub does numbers + voice routing.
- STIR/SHAKEN A-attestation. US/CA outbound from Deepgram-powered agents.
- 136 countries. Global Deepgram Voice Agent deployments.
- Webhook events for the call lifecycle. Composable with Deepgram's own event surface.
BYOC setup — step by step
- Sign up at /signup and provision DIDs.
- Generate DIDHub SIP credentials.
- Build your agent: connect Deepgram Voice Agent API to a SIP-to-WebSocket bridge (LiveKit, custom, etc.) with DIDHub as the SIP carrier.
- Bind DIDs to your agent endpoints.
- Test inbound + outbound; validate Deepgram's STT/TTS pipeline latency.
Caller-ID configuration
Set the DIDHub DID as Caller-ID in your bridge / outbound dialer. DIDHub signs and routes.
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 Deepgram Voice Agent 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 Deepgram have native phone-call support?
Deepgram Voice Agent API is currently a WebSocket-based agent. To bridge to PSTN, you connect it to a SIP-to-WebSocket layer (LiveKit, Pipecat, custom) with DIDHub as the SIP carrier.
Why not use Deepgram's bundled telephony partners?
Deepgram supports several telephony partners; DIDHub is a clean fit for teams that want carrier control (A-attestation, country inventory, per-DID economics) rather than bundled.
Can I use Deepgram's STT separately from the Voice Agent API?
Yes — Deepgram STT works as a standalone STT in any pipeline. DIDHub provides the telephony regardless.
Latency expectations?
Deepgram's pipeline is fast; DIDHub's regional ingress keeps the PSTN hop tight. Sub-1s end-to-end is achievable.
Provision your first Deepgram Voice Agent DID
Sign up at /signup, pick a country / area code, and route the DID to your Deepgram Voice Agent 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.