You can view the TwiML executed during your call by viewing the Request Inspector for a call log in Console. This guide will walk you through viewing the TwiML that was executed on a call.
View the Request Inspector
- Access the Call Logs page in Console.
- Click the desired call log.
- The Call Details page will be displayed. Scroll down the page to the Request Inspector to see the HTTP status code and response we received from your site.
Interpreting the Request Inspector
The Request Inspector for your call log is listed chronologically by HTTP request. Each request will show the following details:
- Request type: POST or GET
- Requested URL: The webhook, twiml bin, functions, or other URL used to serve TwiML.
- Timestamp: The date and time of the request.
- Response time: The time it took the requested URL to respond.
-
HTTP response status code: The requested URL's HTTP status response code. A successful request should respond with
200
, but3XX
may be seen with a redirect. Response codes4XX
and5XX
usually indicate an error occurred. - Replay request button: Request the URL again, helpful for troubleshooting issues.
In this example, we made an inbound call to a Twilio number configured with a webhook. When the call came in the, Twilio number made an HTTP POST request to the webhook URL, which responded in 55ms with an HTTP 200
response, and the TwiML listed in the Body section.
Common Issues
Here are some of the most common issues we see with requesting and processing TwiML responses:
<Reject/> or an empty <Response>
A TwiML response consisting of the <Reject/> TwiML verb, or an empty <Response></Response> response tells Twilio to ignore the call.
<Hangup/> TwiML verb
The <Hangup/> TwiML verb tells Twilio to end the call. Any TwiML after this point would be disregarded, as the call is ended.