<Refer>
Transfer the call to a SIP endpoint.
Element body
The SIP URI to transfer to — either as the element body or inside a nested <Sip> child.
Example
<Response>
<Refer action="https://app.example.com/after-refer">
<Sip>sip:support@pbx.example.com</Sip>
</Refer>
</Response>Attributes
| Attribute | Default | Behaviour |
|---|---|---|
action |
unset |
URL posted when the transfer completes; the returned VoiceML continues the call. |
method |
POST |
HTTP method for the action request: POST or GET. |
Nesting
<Refer> accepts these nested elements:
Callbacks
action request
| Field | Description |
|---|---|
ReferStatus |
completed or failed. |
ReferCallSid |
Unique identifier of the transfer leg. |
Cause |
Failure cause, present when the transfer failed. |
Every callback also carries the standard call parameters (CallSid, AccountSid, From, To, CallStatus) and is signed with your account's API key.
Notes
- The platform implements the transfer as a locally bridged leg: the transfer target is dialled and bridged to the caller, which matches cold-transfer expectations end to end. Raw SIP REFER is not propagated to the carrier. Attended/consultative transfer flows are not in scope.