Voice and telephony agents for live calls
AshnaAI can place and receive live calls through LiveKit telephony plus Twilio or Telnyx numbers. Inbound routing attaches a SIP trunk or voice webhook. Numbers are filtered for voice capability before purchase.
Method: Review of the telephony provider router and number-search contracts: inbound/outbound flags, voice-only filters, and LiveKit SIP inbound trunk setup.
Key findings
- The telephony router supports inbound webhooks and outbound calls attached to a LiveKit room.
- Number search defaults to voice-capable numbers (voiceOnly true) on Twilio and Telnyx providers.
- Inbound setup creates a LiveKit SIP inbound trunk and dispatch rule, or configures a Twilio voice webhook URL.
Numbers are inventory, calls are rooms
AshnaAI treats a phone number as something you search, buy, and then route. Voice capability is a filter, not an afterthought. Twilio and Telnyx both expose whether a number can carry voice.
Once a number is attached, a live call becomes a LiveKit room. That is how an agent can speak on the same infrastructure used for realtime media, instead of a one-off carrier webhook with no session.
Inbound versus outbound
Inbound setup creates the path from the carrier to AshnaAI: a LiveKit SIP inbound trunk and dispatch rule, or a Twilio voice URL. Outbound is the reverse: place a call from the number and attach it to a room.
Both directions are flags on the number record (inboundEnabled, outboundEnabled). A number can be purchased and still be wrongly routed if those flags and the trunk are not set.
Where this compounds
Healthcare and retail solution pages are the conversion layer for industry language. This article is the mechanism: numbers, trunks, and rooms. WhatsApp Business is a send-message connector, documented on the connector page, not a hosted inbound inbox.
The agent that talks on the call is still a spec with tools and permissions. Telephony does not bypass guardrails.
Limitations
AshnaAI does not become your PBX, and it does not build a patient portal or storefront. Recording, consent, and healthcare privacy remain the customer’s policy problem.
Carrier coverage and number availability depend on Twilio and Telnyx inventory in the destination country.
Frequently asked questions
- Can AshnaAI answer a phone call?
- Yes. Inbound routing attaches a purchased number to a LiveKit room through a SIP inbound trunk and dispatch rule, or through a Twilio voice webhook.
- Can AshnaAI place outbound calls?
- Yes. The provider router exposes outbound calling from a number, attached to a LiveKit room when the call is active.
- Which carriers are supported?
- Twilio and Telnyx number providers sit behind a shared router. Voice capability is a first-class filter when searching and buying numbers.
- Is this the same as a voice clone in chat?
- No. Chat voice and live telephony are related product surfaces, but this research is about PSTN numbers, inbound trunks, and outbound origination.
- Does a healthcare or retail team need a different product?
- They need the same telephony stack plus their industry solution page. The agent spec still decides tools and permissions.
- Can AshnaAI replace a contact-center platform on day one?
- This note documents number attach and live-call routing. It does not claim a full CCaaS suite, workforce management, or carrier SLAs beyond the configured providers.
Related
Try this in AshnaAI. Create a free account.