- Voice Record
- Table of Contents
- Description
- Pre-Requisites
- Environmental Variables
- Running the Application
- Callback URLs
This sample app demonstrates how to record a message from an inbound call, similar to how a voicemail machine would work.
When the user calls the Bandwidth phone number associated with this application, the user will hear an audio prompt to leave a message, then a beep. Once this happens, the call will begin recording.
When the call ends, Bandwidth will start to process the recording. Once this processing is complete, Bandwidth will send a webhook to the /recordingAvailableCallback
endpoint on this application. Once received, the application will download the recording via Bandwidth's voice recording API.
In order to use the Bandwidth API users need to set up the appropriate application at the Bandwidth Dashboard and create API tokens.
To create an application log into the Bandwidth Dashboard and navigate to the Applications
tab. Fill out the New Application form selecting the service that the application will be used for (this sample app uses a voice application). All Bandwidth services require publicly accessible Callback URLs, for more information on how to set one up see Callback URLs.
For more information about API credentials see here
The sample app uses the below environmental variables.
BW_ACCOUNT_ID # Your Bandwidth Account Id
BW_USERNAME # Your Bandwidth API Token
BW_PASSWORD # Your Bandwidth API Secret
Use the following command to run the application:
cd VoiceRecord/
dotnet run
For a detailed introduction to Bandwidth Callbacks see https://dev.bandwidth.com/guides/callbacks/callbacks.html
Below are the callback paths:
/callbacks/callInitiatedCallback
/callbacks/recordingAvailableCallback
A simple way to set up a local callback URL for testing is to use the free tool ngrok.
After you have downloaded and installed ngrok
run the following command to open a public tunnel to your port (5001)
ngrok http 5001
You can view your public URL at http://127.0.0.1:4040
after ngrok is running. You can also view the status of the tunnel and requests/responses here.
Note: If you would like to change your port number feel free to do so. However, if you do change the port you will also need to change the number appended to the application URL in the launchSettings.json
file located in SendReceiveMMS/Properties/