Vapi voices failing in production!
# supportg
gzqq
05/12/2026, 7:59 PM Copy code
{
"level": 50,
"time": 1778601487585,
"timestamp": 1778601487585000000,
"severityText": "ERROR",
"severityNumber": 17,
"body": "Orpheus WebSocket error",
"traceId": "019.....",
"attributes": {
"service": "call",
"category": "voice",
"event": "assistant.voice.requestFailed",
"eventStatus": "fail",
"orgId": "e......",
"callId": "019e.....",
"subscriptionId": "b2....",
"provider": "orpheus",
"voiceId": "Jess",
"error": "Unexpected server response: 500",
"traceId": "019......"
}
}gzqq
05/12/2026, 8:07 PM"endedReason":"call.in-progress.error-vapifault-vapi-voice-failed"
m
Matt
05/13/2026, 6:00 AMThat assistant.voice.requestFailed with the Orpheus 500 response usually points to a provider-side voice generation failure or a bad handshake between Vapi and the voice model. Since the call ended with call.in-progress.error-vapifault-vapi-voice-failed, I’d focus first on the voice config, provider stability, and websocket request payloads.
I can help you trace the exact failure path and isolate whether it’s from Orpheus, Vapi routing, or the assistant setup itself. Are you seeing this on every call or only with the Jess voice / specific workflows?
@gzqq
c
Chiranjeet Mishra
05/20/2026, 10:53 PMHello,
Apologies for the delay in response. Are you still facing the issue? If yes, could you please share the call ID so we can investigate it further?