Live data from Hacker News

Asterisk AI Voice Agent

github.com

21–30 of 129 posts

Re: Asterisk AI Voice Agent

#22
post #11

Can I connect this to Twilio

One easy way to build voice agents and connect them to Twilio is the Pipecat open source framework. Pipecat supports a wide variety of network transports, including the Twilio MediaStream WebSocket protocol so you don't have to bounce through a SIP server. Here's a getting started doc.[1] (If you do need SIP, this Asterisk project looks really great.) Pipecat has 90 or so integrations with all the models/services peo…

This is good stuff.

In your opinion, how close is Pipecat + OSS to replacing proprietary infra from Vapi, Retell, Sierra, etc?

Re: Asterisk AI Voice Agent

#24

Earlier quoted context omitted.

The background noise is a recording for sure, no AI needed, just a background noise audiofile in a loop would do.

Why though? It adds nothing positive, it only makes me sure it is a scam call.

I assume it's to make it seem like an actual call center rather than a scam. I recently got two phone scam attempts (credit card related) that sounded exactly like this.

Re: Asterisk AI Voice Agent

#25

Can I connect this to Twilio

I developed a stack on Cloudflare workers where latency is super low and it is cheap to run at scale thanks to Cloudflare pricing.

Runs at around 50 cents per hour using AssemblyAI or Deepgram as the STT, Gemini Flash as LLM and InWorld.ai as the TTS (for me it’s on par with ElevenLabs and super fast)

Re: Asterisk AI Voice Agent

#26
post #11

Can I connect this to Twilio

One easy way to build voice agents and connect them to Twilio is the Pipecat open source framework. Pipecat supports a wide variety of network transports, including the Twilio MediaStream WebSocket protocol so you don't have to bounce through a SIP server. Here's a getting started doc.[1] (If you do need SIP, this Asterisk project looks really great.) Pipecat has 90 or so integrations with all the models/services peo…

The problem with PipeCat and LiveKit (the 2 major stacks for building voice ai) is the deployment at scale.

That’s why I created a stack entirely in Cloudflare workers and durable objects in JavaScript.

Providers like AssemblyAI and Deepgram now integrate VAD in their realtime API so our voice AI only need networking (no CPU anymore).

Re: Asterisk AI Voice Agent

#27
post #24

Earlier quoted context omitted.

Why though? It adds nothing positive, it only makes me sure it is a scam call.

I assume it's to make it seem like an actual call center rather than a scam. I recently got two phone scam attempts (credit card related) that sounded exactly like this.

I built a voice AI stack and background noise can be really helpful to a restaurant AI for example. Italian background music or cafe background is part of the brand. It’s not meant to make the caller believe this is not a bot but only to make the AI call on brand.

Re: Asterisk AI Voice Agent

#28
post #24

Earlier quoted context omitted.

Why though? It adds nothing positive, it only makes me sure it is a scam call.

I assume it's to make it seem like an actual call center rather than a scam. I recently got two phone scam attempts (credit card related) that sounded exactly like this.

you actually answer unknown callers?

Re: Asterisk AI Voice Agent

#30
post #26
post #11

Earlier quoted context omitted.

One easy way to build voice agents and connect them to Twilio is the Pipecat open source framework. Pipecat supports a wide variety of network transports, including the Twilio MediaStream WebSocket protocol so you don't have to bounce through a SIP server. Here's a getting started doc.[1] (If you do need SIP, this Asterisk project looks really great.) Pipecat has 90 or so integrations with all the models/services peo…

The problem with PipeCat and LiveKit (the 2 major stacks for building voice ai) is the deployment at scale. That’s why I created a stack entirely in Cloudflare workers and durable objects in JavaScript. Providers like AssemblyAI and Deepgram now integrate VAD in their realtime API so our voice AI only need networking (no CPU anymore).

let me get this straight, you are storing convo threads / context in DOs?

e.g. Deepgram (STT) via websocket -> DO -> LLM API -> TTS?

Post reply on HN