> ## Documentation Index > Fetch the complete documentation index at: https://docs.cognigy.com/llms.txt > Use this file to discover all available pages before exploring further. # Voice Gateway Events > Voice Gateway includes events related to the call lifecycle, for example, transfer and DTMF input. You can capture event data for analysis in Cognigy Insights. Updated in 2025.21 During the call, the following voice events are recorded in the payload: | Event | Description | | --------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [ANSWERING\_MACHINE\_DETECTION](/voice-gateway/references/events/ANSWERING_MACHINE_DETECTION) | The call was initiated and the answering machine detection process started. | | [CALL\_COMPLETED](/voice-gateway/references/events/CALL_COMPLETED) | The call was terminated by the AI Agent or by the user. | | [CALL\_CREATED](/voice-gateway/references/events/CALL_CREATED) | The user created a call. | | [CALL\_FAILED](/voice-gateway/references/events/CALL_FAILED) | The call was terminated. | | [CALL\_IN\_PROGRESS](/voice-gateway/references/events/CALL_IN_PROGRESS) | The call is in progress once the call has been successfully established. This event is only available, when the event is activated in the Voice Gateway Endpoint. | | [RECOGNIZED\_SPEECH](/voice-gateway/references/events/RECOGNIZED_SPEECH) | The user's answer was recognized by the AI Agent. | | [RECOGNIZED\_DTMF](/voice-gateway/references/events/RECOGNIZED_DTMF) | The DTMF code was recognized by the AI Agent. | | [TRANSFER\_DIAL\_ERROR](/voice-gateway/references/events/TRANSFER_DIAL_ERROR) | The call transfer using the `Dial` method failed due to various reasons, like unreachable destination or network issues. | | [TRANSFER\_DIAL\_SUCCESS](/voice-gateway/references/events/TRANSFER_DIAL_SUCCESS) | The call transfer using the `Dial` method succeeded with the new phone line established to the destination. | | [TRANSFER\_REFER\_ERROR](/voice-gateway/references/events/TRANSFER_REFER_ERROR) | The call transfer using the `Refer` method failed, possibly due to an unavailable or rejecting destination. | | [TRANSFER\_REFER\_SUCCESS](/voice-gateway/references/events/TRANSFER_REFER_SUCCESS) | The call transfer using the `Refer` method succeeded, with the call responsibility passed to another destination. | | [USER\_BUSY](/voice-gateway/references/events/USER_BUSY) | The user (caller) was busy and unable to answer the call or engage in the desired action. | | [USER\_INPUT\_TIMEOUT](/voice-gateway/references/events/USER_INPUT_TIMEOUT) | The AI Agent terminated the call because the user did not respond. | | [NO\_ANSWER](/voice-gateway/references/events/NO_ANSWER) | The recipient of the call does not answer. | You can [collect event data](/ai/agents/analyze/collecting-data) for further analysis in [Insights](/ai/agents/analyze/insights). To collect this data, you can access Voice Gateway events in the [Output Transformer](/ai/for-developers/transformers/output-transformer) and the `input.data.event` Input object, except for the `CALL_COMPLETED` event. You can't access `CALL_COMPLETED` in `input.data.event` since the Input object's content is deleted after `CALL_COMPLETED` occurs. Alternatively, you can register the `CALL_COMPLETED` events by enabling the `CALL_COMPLETED` toggle in the Call Events section of the [Voice Gateway Endpoint](/ai/agents/deploy/endpoint-reference/voice-gateway) configuration. The Output Transformer is executed after processing the flow. For example, if you receive the `CALL_COMPLETED` event, write some metrics in the transformer via HTTP request. You can also use a **Lookup** Node with the [Call Event Status](/ai/agents/develop/node-reference/logic/lookup) type for reusing these events, streamlining call handling and improving efficiency.