SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site,, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

Call Recording Support on Elastic SIP Trunks

Twilio Elastic SIP Trunks do support call recording. When recording is enabled, all calls are recorded (both origination and termination traffic), in a pay-as-you-go consumption model. 

Elastic SIP Trunking Call Recording Options

There are three different recording settings to select from:

  • Do Not Record (Default option): Recording is disabled on this trunk.
  • Record from Answer: Recording will begin when a call is answered.
  • Record from Ringing: Recording will begin when the ringing starts.

Enable Call Recording for an Elastic SIP Trunk

  1. Login to your project at
  2. Select Elastic SIP Trunking > Trunks, or click here.
  3. Click the desired SIP Trunk to modify.
  4. Click the Recording Setting drop-down menu, and then select the desired recording option.
  5. Click Save.

Access Call Recordings in Console

Single call recordings can be viewed and manually deleted one at a time from the Recordings log in Console:

  1. Login to your project at
  2. Select Elastic SIP Trunking > Logs, or click here.
  3. Navigate to and select the desired recordings -
    • From Calls logs: select the desired call, and then click on the Recording SID.
    • From Recordings logs: click the desired recording.
  4. From here, you can play or delete a recording.

Access Call Recordings Programmatically via the REST API

Call recordings can be be accessed via calls to the Recordings API resource.

  • HTTP DELETE requests are used to delete call recordings.
  • HTTP GET requests are used to download call recordings.

To download or delete multiple recordings using the API, a script would be required that iterates over the list of recordings, making a separate API request for each action.

More information, including sample code and best practices for managing recordings, can be found in the blog post Manage Your Call Recordings with the REST API.

Have more questions? Submit a request
Powered by Zendesk