Public Access
1.5 KiB
1.5 KiB
Azure Speech Offline Resilience
Summary
Make Azure Speech transcription resilient to transient and longer network loss by keeping meeting audio capture alive, surfacing reconnect/disconnect state in the transcript note, and draining buffered audio once Azure Speech can be reached again.
Motivation
When IPv4 connectivity was lost while IPv6 still worked, Azure Speech stopped producing transcript lines but recovered after connectivity returned. The app continued running, which points to Azure Speech connectivity rather than local audio capture. Users need visible status and continued recording instead of silent transcript stalls.
Scope
- Confirm Azure Speech live transcription consumes only Meeting Assistant's audio channel.
- Add transcript marker support for reconnect/disconnect status lines.
- Add Azure Speech transient reconnect markers like
<Reconnecting... n/m>. - Replace a reconnect marker with the next real transcript line when Azure resumes.
- Keep audio capture and buffering alive while Azure Speech is unavailable.
- Reset live speaker identity assumptions after Azure reconnects because speaker IDs may change across SDK sessions.
- Queue stopped Azure meetings durably when the SDK cannot drain before the stop timeout, then replay the recorded WAV and complete transcription/summary after connectivity returns.
Out Of Scope
- Replacing Azure Speech with local models.
- Changing the temporary mixed WAV format.
- Replacing the summary or workflow engines used after an offline replay.