-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
Title
Audio Playback Requires Silence Stream
Background
When playing back audio responses from the OpenAI Realtime API, the channel currently requires a looped silence_stream toward the caller leg.
This workaround is functional but not ideal, as it depends on an external application. We should handle the playback flow entirely within the module.
Expected Behavior
Audio playback should start correctly without requiring an external silence_stream.
The media path toward the caller should open automatically when playback begins.
Actual Behavior
Playback only works if a looped silence_stream is running toward the caller leg.
Without it, the media path does not open properly.
Steps to Reproduce
- Start audio playback of Realtime API responses without a
silence_stream. - Observe that the media path toward the caller fails to open.
- Start a
silence_streamand retry — playback works.
Possible Solutions / Investigation Ideas
- Start the
silence_streaminternally within the module when invokingstart. - Investigate why the media path fails to open toward the caller without it, and implement a cleaner, self-contained solution.
Notes
We haven’t fully identified the root cause yet — the quick workaround using the silence_stream was used initially to unblock audio playback. Further investigation is required.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels