> ## Documentation Index
> Fetch the complete documentation index at: https://www.voiceflow.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Transferring SIP calls

> Forward a connected caller to a phone or SIP destination.

A connected SIP call can be forwarded to a phone number or SIP destination by the agent’s Call forward step or system tool. The managed telephony service performs the transfer; you do not need a Socket.IO client to consume the `call-forward` trace.

## Choose the transfer destination

| Destination | Configuration | Transfer behavior |
| --- | --- | --- |
| Phone | A destination phone number. | A phone transfer uses the agent’s phone identity as Caller ID. Inbound calls can pass through the original caller’s number when **Caller ID passthrough** is enabled. |
| SIP | A SIP URI such as `sip:support@example.com`. | Voiceflow requests a SIP `REFER`; the phone system must accept the transfer and route the target URI. |

Configure the destination in the [Call forward step](/docs/documentation/build/steps/call-forward) or [Call forward system tool](/docs/documentation/build/tools/system-tools#call-forward). Configure the connection’s **Outbound calls and transfers** settings for calls routed back through your phone system.

## Transfer handling and context

### Transfer result

Voiceflow waits for queued speech before requesting the transfer. After a successful transfer request, it stops the agent’s media stream without hanging up the bridged call. Acceptance of the request is not proof that a human answered.

If the provider rejects the SIP REFER or phone-transfer request, Voiceflow ends the agent call with `CALL_FORWARD_FAILED`. Check the PBX’s transfer policy and destination routing before testing again. Call forwarding is disabled for prototype outbound calls.

### Pass transfer context

Append SIP headers after `?`, separated by `&`. Percent-encode header values. Voiceflow separates these values from the URI before passing them to the provider. `User-to-User` receives dedicated UUI handling; other headers are passed as custom headers. A literal `+` stays a plus, rather than becoming a space.

Headers can carry customer context. Pass identifiers your phone system needs and ensure the receiving system interprets them; adding a header does not configure the receiving application.

## Transfer example

### Pass a ticket reference to a SIP destination

Add context headers to the destination configured in Call forward.

```text title="SIP transfer destination"
sip:support@example.com?X-Ticket-ID=1042&User-to-User=case%3D1042
```

The target URI is `sip:support@example.com`; the custom ticket header contains `1042`, and the UUI header contains `case=1042`. This is an illustrative destination, not a callable endpoint.

## Related references

Use [SIP troubleshooting](/docs/api-reference/agent-runtime/voice/sip/troubleshooting#choose-the-symptom) when a transfer ends the call. The [custom-client handoff reference](/docs/api-reference/agent-runtime/voice/handoff) documents `call-forward` trace fields for integrations that own their telephony client.
