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

> Return a caller that a Classical IVR transferred to your SIP endpoint, so the flow can route them to a team. Use when your system is done with the call.

# Hand back call

When a Classical IVR transfers a caller to a SIP destination, the caller stays on the OpenCX call while your SIP endpoint talks to them. Call this endpoint, instead of hanging up, when the caller should continue with the organization. OpenCX hangs up your SIP leg, then the IVR continues with the steps after the transfer, usually a transfer to a team. The caller keeps the same call, recording and session throughout.

Send the session ID you received in the `X-OPENCX-SESSION-ID` SIP header of the transfer. The destination must list `X-OPENCX-SESSION-ID` among its allowed headers if it uses an allowlist.

* Create the API key with the **Hand back transferred calls** (`phone-calls:write`) scope. That scope cannot read or change any other phone configuration. A `phone:write` key can also hand calls back.
* Pass an optional `summary` of the conversation so far. It replaces the session's summary before the teammate is connected, so they see it when the call rings. It is saved only when the hand-back is accepted.
* Repeating a successful hand-back returns the same response and changes nothing; a `summary` sent with the repeat is ignored.
* A `409` means the session has no transferred call waiting: your leg has not answered yet, your leg or the caller already hung up, or the session has no SIP transfer. Hanging up without calling this endpoint returns the caller to the IVR, which continues with the `completed` outcome.
* A `404` means the session does not exist in the organization that owns the API key.

Do not hang up your leg first: OpenCX hangs it up for you once the hand-back is accepted. If your leg hangs up before the hand-back arrives, the hand-back is still accepted for a few seconds.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.