@Shubham Bajaj
Hi, we're intermittently encountering this issue during call initiation. In some cases, a callId is generated even when the call fails to connect. In other cases, no callId is generated at all.
Here are some callIds where the call failed to start but a callId was still generated:
89a1e8e6-2163-4879-ba99-40c1c2dc9eff
df659c7c-34df-49d3-bb6f-1d353a3b6fad
83c40e06-e748-4c1b-ba6d-bb3f4fc1ae15
bc83a9d5-e8dd-40ad-96fa-0c037c5f1ae6
90902b54-bc59-445b-97b0-661f7fe40927
For all of these calls, the VAPI dashboard shows the error:
"An error occurred in this call: call.in-progress.error-assistant-did-not-receive-customer-audio"
This seems to only occur at the time of call initiation. Once a call is successfully connected, it never fails due to this error, even if network conditions are poor. That makes us suspect it might not be purely a network issue, and could be related to how daily_flutter handles call startup.
Could you help us investigate whether this is an issue on the SDK side or something misconfigured in our integration?