Question
Why is the uuid missing in DTMF timeout webhook events?
Is it possible to force the uuid field to be included in DTMF timeout events posted to webhook?
Applies to
- Voice API
- DTMF Input
Answer
When a DTMF input times out, the uuid field may not be included in the webhook payload. This is expected behaviour. The reason for this behaviour is that a conversation can contain multiple calls. When a DTMF input times out, the platform cannot determine which specific call was expected to provide the DTMF input. As a result, the timeout event is not associated with a particular call UUID and the uuid field may be absent.
Currently there is no option or configuration available to force the uuid field to be included in DTMF timeout webhook events.
Additional Information
Articles in this section
- Why is the UUID not present when DTMF times out
- Multiple Record Actions in Same Conversation
- Do we retry if the voice event webhook fails?
- How do I verify that the Voice API Webhook request and it's payload has not been tampered during transit?
- How To Check Call Quality With Voice Inspector
- What is a Conversation ID?
- How to configure the custom webhook timeout for Voice API functionality and what are the allowed timeout ranges ?
- How do I change TTL for the Conversations and Call Legs?
- Why are call progress events not being received on the Event URL defined in the conversation action NCCO?
- Why is there an extended silence at the beginning of a call and how can it be reduced?