Short answer: ElevenLabs’ public docs don’t list a “twirp error unknown: request timed out” message. However, timeouts during a transfer typically stem from telephony configuration or tool setup. Here’s what the official docs say to verify:
Use case check: The Transfer to Human tool only works on phone calls, not in the chat widget. Ensure the call is a telephony session. (elevenlabs.io)
Tool configuration: Confirm you added the transfer_to_number system tool to the agent and defined transfer rules with correctly formatted destinations:
Phone numbers must be E.164 (+12125551234).
SIP URIs must be valid sip: or sips: addresses.
Also verify any SIP REFER usage meets requirements (call must be via SIP and your trunk must allow REFER). (elevenlabs.io)
Twilio vs SIP trunking:
Twilio native integration: make sure the number is properly imported and has the expected inbound/outbound capabilities before testing transfers. (elevenlabs.io)
SIP trunking: verify your trunk setup and network:
Dial ElevenLabs with a proper SIP URI that includes an identifier (e.g., sip:+19991234567@sip.rtc.elevenlabs.io:5060). (elevenlabs.io)
Check transport/ports and TLS (TCP 5060 or TLS 5061), certificate validity, and that your provider supports required codecs (G.711/G.722). UDP for SIP signaling isn’t available. (elevenlabs.io)
Diagnose the exact failure: Open Calls History in the dashboard; failed calls show a red reason (e.g., missing dynamic variables after transfer). If no reason is shown, contact Support. (help.elevenlabs.io)
Tools overview (sanity check): Transfers are a built‑in “system tool”; ensure you haven’t misconfigured client/webhook tools instead. (help.elevenlabs.io)
If you still hit timeouts after the above checks, please contact ElevenLabs Support with the call ID and a timestamp so they can review backend logs. (help.elevenlabs.io)
gilded aurora
sonic lantern