Twilio Media Streams
Use this channel to connect your Rasa assistant to Twilio Media Streams for voice capabilities. Unlike the standard Twilio Voice connector, this channel handles speech-to-text (ASR) and text-to-speech (TTS) processing directly in Rasa.
Configuring Twilio Webhook
Visit this section to learn how to generate the required bot URL when testing the channel on your local machine.
Go to the Phone
Numbers section of your Twilio account and select the phone
number you want to connect to Rasa.
Select the option "Webhook, TwiML Bin, Function, Studio Flow, Proxy Service" and set the URL of your Rasa Server
as webhook. Depending on the hostname, the webhook URL would be
https://yourdomain.com/webhooks/twilio_media_streams/webhook
Your webhook endpoint must be served over HTTPS. Twilio Media Streams does not accept insecure HTTP URLs.
Using Basic Authentication
Rasa supports Basic Authentication for Twilio Media Streams in Rasa Pro 3.11.8+, Rasa Pro 3.12.7+ and latest releases.
If you want to use basic authentication for your Twilio Media Streams channel, you need to set the webhook URL in the following format:
https://<username>:<password>@yourdomain.com/webhooks/twilio_media_streams/webhook
For more info checkout the Twilio security documentation.
Basic Rasa Configuration
Create or edit your credentials.yml
and add the following channel configuration:
twilio_media_streams:
server_url: "<your-domain>"
# ASR Configuration
asr:
name: "azure" # or "deepgram"
# Add ASR-specific configuration here
# TTS Configuration
tts:
name: "azure" # or "cartesia"
# Add TTS-specific configuration here
# Monitor user silence
monitor_silence: false
# Basic Authentication
username: "<username>"
password: "<password>"
Support for username
and password
parameters is available
in Rasa Pro 3.11.8+, Rasa Pro 3.12.7+ and latest releases.
Twilio Media Streams channel configuration expects the following parameters:
-
server_url
(required): The domain at which Rasa server is available. Do not include protocol (ws:// or wss://). For example, if your server is deployed onhttps://example.ngrok.app
,server_url
should beexample.ngrok.app
. -
asr
(required): Configuration for Automatic Speech Recognition. See Speech Integrations for a list of ASR engines for which Rasa provides built-in integration with. -
tts
(required): Configuration for Text-To-Speech. See Speech Integrations for a list of TTS engines for which Rasa provides built-in integration with. -
monitor_silence
(optional, default false): Boolean parameter that enables user silence monitoring. If enabled, it triggers the pattern "user silence" when the user has been silent for longer than a threshold time. The silence threshold is controlled by the slotsilence_timeout
. -
username
(optional): Basic authentication username for Twilio Media Streams channel. -
password
(optional): Basic authentication password for Twilio Media Streams channel.
Check using basic authentication on how to setup Twilio webhook with basic authentication.
You can run the assistant using the command rasa run
. You'll need a URL accessible by Twilio for your Rasa assistant. For development, you can use tools like ngrok, Cloudflare Tunnel, or localhost.run.
You can also run it with a development inspector using rasa run --inspect
.
To see all available parameters for this command, use rasa run -h
.
Usage
Receiving Audio
When a user speaks, Twilio streams the audio to Rasa where:
- The audio stream is collected and buffered
- The configured ASR service converts speech to text
- The text is processed by Rasa's NLU pipeline
Sending Responses
For bot responses:
- Rasa generates text responses
- The configured TTS service converts text to audio
- Audio is streamed back to Twilio
Call Events
Like other voice channels, the following events are supported:
Event | Intent | Description |
---|---|---|
start | session_start | Triggered when call connects |
end | session_end | Triggered when call disconnects |
DTMF | - | Phone keypad presses (sent as text messages) |