Phone numbers for Pipecat (Daily) — SIP trunk setup with DIDHub
Pipecat is the open-source voice-and-multimodal agent framework from Daily. DIDHub bridges PSTN inbound and outbound to Pipecat pipelines via SIP, giving you phone-number access to your Pipecat agents without the Daily/Twilio bundled-DID layer.
Why DIDHub for Pipecat (Daily)
- Open-source-aligned. Pipecat is open source; DIDHub plays cleanly as the underlying SIP carrier without Pipecat-specific lock-in.
- Sub-50ms regional ingress for the realtime pipeline. Pipecat's pipeline architecture is latency-sensitive (STT → LLM → TTS → egress). DIDHub regional edges keep the PSTN side tight.
- STIR/SHAKEN A-attestation. For US/CA outbound from Pipecat agents.
- 136-country DID inventory. International Pipecat deployments without multi-vendor coordination.
BYOC setup — step by step
- Sign up at /signup and provision DIDs.
- Generate DIDHub SIP credentials.
- In your Pipecat deployment: configure the SIP transport (Pipecat supports Daily's SIP transport, which can ingest from any compliant SIP carrier).
- Point Daily's SIP config at DIDHub's SIP URI + credentials.
- Wire your Pipecat pipeline (Python) to handle the inbound call: STT → LLM → TTS → egress.
- Test inbound + outbound; validate audio quality and pipeline latency end to end.
Caller-ID configuration
For outbound, set the Caller-ID in Daily's SIP outbound config to a DIDHub DID. Daily passes that to DIDHub on the outbound INVITE; we sign and route.
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 Pipecat (Daily) 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 Pipecat support BYOC SIP directly?
Pipecat itself routes through Daily's media transport, which handles SIP. DIDHub is the SIP carrier upstream of Daily.
Can I bypass Daily and connect Pipecat to DIDHub directly?
If you build a custom SIP-to-Pipecat bridge, yes. Most teams use Daily's bundled SIP transport for simplicity.
How does latency look on Pipecat + DIDHub + OpenAI Realtime?
Tight if you put DIDHub regional ingress, Daily, and OpenAI in the same region. Sub-1s end-to-end is achievable.
Is Pipecat production-ready?
Pipecat is stable and used in production deployments; it's been actively developed since 2023. Always test the specific version + pipeline you're deploying.
Provision your first Pipecat (Daily) DID
Sign up at /signup, pick a country / area code, and route the DID to your Pipecat (Daily) 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.