Hi Support Team, I encountered a critical failure in the Agentic Warm Transfer workflow where the bridge_transfer tool reported a successful connection, but the actual SIP bridge never occurred. The Incident: Interaction: The Transfer Agent successfully spoke to the human representative. Acceptance: The human rep agreed to take the call. Tool Execution: The agent executed bridge_transfer. Log Result: The logs show the tool successfully returned: Tool Result: {"status": "bridged"} Actual Behavior: despite the "bridged" status, the audio was never connected to the human representative. The user remained on the line with the Transfer Agent (in a dead/silent state) until the system timed out and terminated the call. The Logs: Call ID: call_3868ad6fdde4b184836fe847 Agent ID: agent_4b155057108f3b0e0c9d769eef Tool Call ID: 36de04d5e6937064 (from my logs) My Request: Why is the API returning {"status": "bridged"} before the SIP media stream is actually established? This "false positive" is breaking our logic because our system marks these calls as successful "Warm Transfers" even though the customer was never connected. Can you investigate why the bridge signal fired but the media failed to traverse? Thanks

hello

hello sir

could you provide SIP connection logs that will be in call log

2026-01-13 10:17:06.938 call_3868ad6fdde4b184836fe847 info: Starting call: call_3868ad6fdde4b184836fe847 2026-01-13 10:17:08.728 call_3868ad6fdde4b184836fe847 info: Webhook triggered for call_started 2026-01-13 10:17:08.883 call_3868ad6fdde4b184836fe847 info: Webhook response received for call_started 2026-01-13 10:17:24.574 call_3868ad6fdde4b184836fe847 info: Calling tool: bridge_transfer Arguments: {"execution_message":"Connecting you now."} 2026-01-13 10:17:24.574 call_3868ad6fdde4b184836fe847 info: Received result for tool: 36de04d5e6937064 bridge_transfer Result: {"status":"bridged"} 2026-01-13 10:17:25.974 call_3868ad6fdde4b184836fe847 info: E2E latency for this turn: 852 2026-01-13 10:17:45.848 call_3868ad6fdde4b184836fe847 info: E2E latency for this turn: 3396 2026-01-13 10:17:52.727 call_3868ad6fdde4b184836fe847 info: Transfer agent max duration reached, using timeout action: cancel_transfer 2026-01-13 10:17:52.727 call_3868ad6fdde4b184836fe847 info: Received agentic transfer decision: cancel_transfer 2026-01-13 10:17:52.727 call_3868ad6fdde4b184836fe847 info: Ending call: call_3868ad6fdde4b184836fe847 2026-01-13 10:17:53.355 call_3868ad6fdde4b184836fe847 info: Webhook triggered for call_ended 2026-01-13 10:17:53.541 call_3868ad6fdde4b184836fe847 info: Webhook response received for call_ended 2026-01-13 10:17:53.884 call_3868ad6fdde4b184836fe847 info: Webhook triggered for call_analyzed 2026-01-13 10:17:54.033 call_3868ad6fdde4b184836fe847 info: Webhook response received for call_analyzed this one?

Yes, have you tried increasing the agent detection timeout?

you mean Transfer Timeout?

Hello @Vako-SV , the issue could be from our side , I've let the team know I will update you soon , If you can try the conversation flow for this feature it should be working fine.

i cant change the whole agents now into conversational flow sir - i use 4 agent combination for 1 purpose and only 1 transfer agent - i tried to work with Single prompt agent and tranfer agent to be conversation flow - but its not working

got it, I've report it to the team,I will get back to you on this.

eprox response time? @Omar Ashraf | Community Lead

~ 1 business day.

okey let me check