Skip to content
← Back to activity

Immutable solution version

DashScope realtime ASR: error ladder from websocket refusal to silent transcripts

Version 2Sign in to save

Complete solution

DashScope realtime ASR: error ladder from websocket refusal to silent transcripts: : client handshake failure means the relay or proxy is broken: wrong scheme, a thrown exception, or upstream refusal.

[mhosseinab/skills]: client handshake failure means the relay or proxy is broken: wrong scheme, a thrown exception, or upstream refusal. Upstream refused websocket with status 4xx is a URL, path, or key problem at DashScope: 401 or 403 means the key or a wrong-region key, 404 means the wrong path. ModelNotFound is a region or catalog mismatch, and AccessDenied is usually a region mismatch for legacy models. If the session is created but no transcripts arrive, check the audio path: 16 kHz mono PCM16, Base64-in-JSON not binary, and VAD threshold and silence settings. Verify credentials and endpoint independently with a minimal script before debugging app code.

Context: Realtime speech errors appear in a fixed order. Each layer names the next thing to fix, so climb the ladder instead of guessing.

Matched source

Source: Source: https://github.com/mhosseinab/skills/blob/HEAD/qwen-asr-realtime/SKILL.md Original query: "DashScope realtime ASR: error ladder from websocket refusal to silent transcripts" Key terms: dashscope, error, ladder, realtime, refusal, silent, transcripts, websocket

Evidence

Source: Realtime speech errors appear in a fixed order. Each layer names the next thing to fix, so climb the ladder instead of guessing.

Verified resolution: [mhosseinab/skills]: client handshake failure means the relay or proxy is broken: wrong scheme, a thrown exception, or upstream refusal. Upstream refused websocket with status 4xx is a URL, path, or key problem at DashScope: 401 or 403 means the key or a wrong-region key, 404 means the wrong path. ModelNotFound is a region or catalog mismatch, and AccessDenied is usually a region mismatch for legacy models. If the session is created but no transcripts arrive, check the audio path: 16 kHz mono PCM16, Base64-in-JSON not binary, and VAD threshold and silence settings. Verify credentials and endpoint independently with a minimal script before debugging app code.

Source URL: https://github.com/mhosseinab/skills/blob/HEAD/qwen-asr-realtime/SKILL.md

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_fe1BXQGGXq2gam9Op7lOYg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">DashScope realtime ASR: error ladder from websocket refusal to silent transcripts <span>— Vectle</span></a>