Arabic transcriber not working
# support
m
Call ID: b11f590b-9c14-4313-90f0-d2b833a4edb6 Date of Error: 7th September Arabic transcription was working previously and was visible on my website, but it suddenly stopped working. The voice still works, but the transcript is no longer showing. I also tested it on the VAPI dashboard, and the issue is the same there. it was working perfect previously. Transcription settings: Provider: Talkscriber Language: AR Model: Whisper Dashboard Message Settings: Client messages: hang, speech-update, transcript, conversation-update, voice-input Server messages: end-of-call-report, hang, transcript, conversation-update, status-update
v
Thanks for sharing the details. To help narrow down the issue, could you please confirm if transcription works for other languages (e.g., English) with the same provider and model settings, or is the problem only with Arabic?
m
I believe the issue is with the provider. No language is working with Talkscriber, but when I switch the provider—for example, to OpenAI—it works.
c
Hello, Talkscriber supports multiple languages including Arabic for transcription. Since this was working previously and suddenly stopped, here are some things to check: 1. Verify your Talkscriber configuration is still correctly set: - Provider is set to "Talkscriber" - Language code is set to "AR" - Model is set to "Whisper" 2. Check that your subscription and API credentials for Talkscriber are still valid 3. Your message settings look correct for receiving transcripts: - You have "transcript" enabled for both client and server messages - You have "speech-update" enabled for client messages Since you're seeing the same issue on the VAPI dashboard, this suggests it might be an upstream issue with the Talkscriber service itself rather than your implementation.** I recommend: 1. Double-check your Talkscriber configuration 2. If the issue persists, please provide the following: - Example call IDs where transcription is missing - Timeline of when the issue started - Confirmation that the issue occurs on both your site and VAPI dashboard
3 Views