Consume a real-time Media Stream using WebSockets, Python, and Flask
Meet Media Streams
With Twilio's Media Streams, you can access real-time voice data from a Twilio call. Media Streams will stream the audio from the call for its entire duration to a location of your choice.
In this tutorial, you will learn how to stream audio from a live phone call using Twilio, Python, and Flask. You might want to stream audio to provide real-time sentiment analysis for all calls happening within a call center. While we will dial a specific number in this tutorial, you can imagine this number being populated dynamically from the call center software.
Want to see the Flask portion of this project in its entirety? Head over to the GitHub repository, where you can clone the project and run it locally.
What are WebSockets?
Twilio Media Streams uses WebSockets to deliver your audio.
A WebSocket is an upgraded HTTP protocol. WebSockets are intended to be used for long-running connections and are ideal for real-time applications. A handshake is made, a connection is created, and, unlike HTTP, multiple messages are expected to be sent over the socket until it is closed. This helps to remove the need for long-polling applications.
The WebSocket interface is included natively in nearly all client-side web browser implementations.
There are numerous WebSocket Server implementations available for just about every web framework. We'll use the Flask-Sockets to help us through this tutorial.
Set up your Python environment
In this tutorial, we're going to use the web framework Flask and the WebSocket package Flask Sockets. Create a virtual environment and install flask-sockets in your terminal:
python3 -m venv venv source ./venv/bin/activate pip install flask flask-sockets
Now that the package is installed, we can spin up a Flask web server.
Build your WebSocket server
sockets decorator helps you create a WebSocket route with
Flask Sockets relies on
gevent for multithreading, so this server startup looks a little more detailed than a typical Flask server setup.
A typical pattern in most WebSocket server implementations is to continue reading until the WebSocket connection closes:
All messages that are passed over MediaStreams WebSockets are in JSON format.
Python provides a straightforward way to decode JSON:
There are four different message types that you will encounter:
The Start message will contain important information about the stream, like the type of audio, its name, the originating call and any other custom parameters you might have sent.
This information will likely come in handy for whatever service you plan to use with your real-time audio.
You can handle each type by looking at the messages
The media payload is encoded in
base64. Use the built-in Python function
b64decode to decode it to
Once your code is all in place, start your Flask server by running this command in your terminal:
Now your server should be running on your localhost port 5000. Congratulations! Only one thing left to do here: make sure that Twilio can reach your local webserver.
We recommend that you make use of an ssh tunnel service like ngrok, which supports the
wss scheme. We highly recommend installing ngrok if you haven't already.
Since our server is running on port 5000, we'll start a tunnel using:
ngrok http 5000
This will generate a random ngrok subdomain. Copy that URL – you'll need it in the next section.
Start streaming audio
To begin streaming your call's audio with Twilio, you can use the <Stream> TwiML verb.
Create a new TwiML Bin with the following TwiML:
<?xml version="1.0" encoding="UTF-8"?> <Response> <Start> <Stream url="wss://yourdomain.ngrok.io/media" /> </Start> <Dial>+15550123456</Dial> </Response>
You'll need to update the above sample in two key ways:
- Replace the phone number nested in the
<Dial>tag with your personal phone number, or the number of a friend or family member who can help you see this in action.
- Replace the
Stream urlwith your new nrgok subdomain – you can find this in the terminal if ngrok is running. The
urlattribute must use the
wssscheme (WebSockets Secure), but we're in the clear since ngrok itself uses the
<Start> tag will asynchronously fork your media and immediately continue onto the next TwiML statement. Streaming will continue for the entire duration of the call unless <Stop><Stream>is encountered.
Save your new TiwML Bin, then wire it up to one of your incoming phone numbers by selecting TwiML Bin in the A Call Comes In section and then selecting your bin from the dropdown. Now, when a call comes into that number, Twilio will stream the real-time data straight to your webserver!
By default, Twilio will stream the incoming track – in our case, the incoming phone call. You can always change this by using the
Try it out
Find a friend or family member willing to help you test your streaming web server (or use a second phone that is different than the one you listed in your TwiML bin).
One of you should call your Twilio phone number, which will then connect the call to the number you specified in your TwiML bin. Keep an eye on your console output and start talking – you should see your conversation appear in the console as you talk!
Real-time access to your audio data opens up new doors of innovation for you. From real-time visual effects to bioinformatics, you are certain to benefit from this access to live data.
There are several services that you can connect with to provide live speech to text transcriptions. Now that you have the text in real-time, you can perform all sorts of text-based operations like translations, sentiment analysis, and keyword detection.
You might want to pipe your real-time data into a number of external providers. You can use Google's Cloud Speech to Text, Amazon's Transcribe, or IBM Watson Speech to Text. All of these providers have a language translation service available as well.
Our community has created a starter set for many languages and services. Please check it out for inspiration in building your real-time applications, and consider contributing.
We can't wait to see what you build!
Need some help?
We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.