You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 57562ce
Browse filesBrowse the repository at this point in the historyBrowse files
fix(server): name the model a voice join and a standalone socket actually run
Two ways a live request reached a model its key had not been granted.
A Realtime standalone socket forwards its own model= query untouched, but the
external audio path read that query only for the Frameless style, so a
realtime-standalone join was judged as the default voice model while its query
carried another. Both standalone styles now report the model they forward.
A join names no model of its own. The external path has a per-key call
registry, so the model a call settled on is recorded at create time and a
rejoin is judged against it -- a key scoped to the default can no longer ride a
call created for another model. The native compatibility path keeps no such
record and gains none here: a join, and a call-create that sends no session
model, name no destination, so a key carrying a model list is refused rather
than admitted against an assumed default. A provider-only scope and an
unscoped key are unchanged on both paths.
Reported in review of #5290.
0 commit comments