Skip to main content

Connection Issues

Cannot Establish WebSocket Connection

Symptoms: Connection fails immediately or times out Possible Causes:
  • Invalid API key
  • Network/firewall blocking WebSocket connections
  • Incorrect WebSocket URL
Solutions:
  1. Verify API Key:
  2. Check WebSocket URL:
  3. Test Network Connectivity:

Connection Drops Unexpectedly

Symptoms: Connection closes without sending end signal Possible Causes:
  • Network instability
  • Server timeout
  • Invalid audio data
Solutions:
  1. Implement Reconnection Logic:
  2. Monitor Connection State:

Audio Encoding Problems

No Transcription Received

Symptoms: Connection established but no transcript messages Possible Causes:
  • Incorrect audio encoding
  • Mismatched sample rate
  • Invalid audio format
Solutions:
  1. Verify Encoding Parameters:
  2. Check Audio Format:
  3. Validate Chunk Format:

Poor Transcription Quality

Symptoms: Incorrect or garbled transcriptions Possible Causes:
  • Wrong sample rate
  • Incorrect encoding
  • Audio quality issues
Solutions:
  1. Match Sample Rate:
  2. Use Recommended Encoding:
  3. Preprocess Audio:

Response Handling Issues

Partial Transcripts Not Updating

Symptoms: Only final transcripts received, no partial updates Possible Causes:
  • Not checking is_final field
  • Filtering out partial messages
Solutions:
  1. Handle Both Types:

Performance Issues

High Latency

Symptoms: Long delay between speaking and transcription Possible Causes:
  • Chunk size too large
  • Streaming rate too slow
  • Network latency
Solutions:
  1. Optimize Chunk Size:
  2. Increase Streaming Rate:
  3. Check Network:

Memory Issues

Symptoms: Application crashes or slows down during streaming Possible Causes:
  • Buffering too much audio
  • Not cleaning up resources
Solutions:
  1. Stream Directly:
  2. Clean Up Resources:

Browser-Specific Issues

CORS Errors

Symptoms: WebSocket connection blocked in browser Solutions:
  1. Use WSS (Secure WebSocket):
  2. Handle Authentication:

Microphone Access Denied

Symptoms: Cannot access microphone in browser Solutions:
  1. Request Permissions:
  2. Handle HTTPS Requirement:
    • Microphone access requires HTTPS (or localhost)
    • Ensure your page is served over HTTPS

Debugging Tips

Enable Verbose Logging

Validate Audio Before Sending

Monitor Session State

Getting Help

If you continue to experience issues:
  1. Check API Status: Verify the API is operational
  2. Review Documentation: Ensure you’re following the correct API version
  3. Test with Sample Code: Use the provided examples as a baseline
  4. Note down: Reach out with:
    • Session ID (if available)
    • Error messages
    • Code snippets (sanitized of API keys)
    • Network conditions (if applicable)
  5. Reach out to us: