connectOpenAi fails with `server_error code 42` on 0.4.2
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 45/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Tranquilo
- Stack tecnológico
- node.js, typescript
- Área
- api, audio-video-rtc, backend
Línea de trabajo
Comienza en la llamada TypeScript connectOpenAi y sigue su solicitud hasta el endpoint /video/connect_agent de Stream utilizando las versiones del SDK indicadas. Reproduce el flujo del webhook proporcionado y compara el error code 42 propagado con una conexión directa de OpenAI Realtime. Se considera completado cuando la misma clave válida puede conectar un agente a una llamada de Stream Video sin el error opaco del servidor.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
stream.video.connectOpenAi(...) consistently fails with server_error code 42 when connecting an OpenAI Realtime agent to a call. I have isolated the cause: the same OpenAI API key connects directly to OpenAI's GA Realtime API without error, so the key/account/access are fine. I guess the failure is still inside Stream's /video/connect_agent → OpenAI path.
Bumping to 0.4.2 (as advised on my previous, now-closed ticket) did not change the result.
What I'm trying to do
Connect an OpenAI Realtime (speech-to-speech) agent to a Stream Video call so it joins as a participant and talks. It's triggered server-side from the call.session_started webhook: look up the meeting/agent, then call connectOpenAi.
const call = stream.video.call("default", meetingId);
const client = await stream.video.connectOpenAi({
call,
openAiApiKey: process.env.OPENAI_API_KEY, // sk-proj-36XU_...
agentUserId: agent.id,
});
client.updateSession({ instructions });
No model is passed, so it defaults to gpt-realtime (GA).
Environment
- @stream-io/node-sdk: 0.7.62
- @stream-io/openai-realtime-api: 0.4.2
- @stream-io/video-react-sdk: 1.39.1 (client)
- Next.js: 16.2.10
What's failing
connectOpenAi rejects. The client only surfaces the opaque code 42:
Error: Stream connect_agent failed (code 42): Error: code
{
type: 'error',
error: { type: 'server_error', code: '42', message: 'Error: code ', param: null, event_id: '' }
}
The webhook itself is fine, signature verification passes (HTTP 200 via verifyAndParseWebhook on the raw gzipped body); the 500 comes solely from connectOpenAi.
Timeline
- On @stream-io/openai-realtime-api@0.4.0 → code 42.
- Support (previous ticket) said bump to 0.4.2; the ticket was closed.
- Bumped to 0.4.2 → still code 42, model set or unset.
Checks performed (ruling out my side)
- API key is loaded in the route: confirmed sk-proj-36XU_..., not undefined.
- Account: paid tier with credit.
- Model: default gpt-realtime (GA).
- Agent user: upserted via stream.upsertUsers([...]) at meeting creation, so the agentUserId exists as a Stream user on the call.
Decisive test: same key connects to OpenAI directly
I connected to OpenAI's GA Realtime API directly with the exact same OPENAI_API_KEY:
new WebSocket("wss://api.openai.com/v1/realtime?model=gpt-realtime", {
headers: { Authorization: `Bearer ${OPENAI_API_KEY}` }
});
Result: WebSocket opens cleanly, no error. So the key, its Realtime access, org verification, and tier are all confirmed working outside Stream.
Conclusion
This concluded that my OpenAI credentials/access were not the problem. Should probably be coming from Stream's connect_agent backend.
Error
⨯ Error: Stream connect_agent failed (code 42): Error: code
at ignore-listed frames {
type: 'error',
error: {
type: 'server_error',
code: '42',
message: 'Error: code ',
param: null,
event_id: ''
}
}
POST /api/webhook/stream 500 in 2.0s (next.js: 121ms, proxy.ts: 11ms, application-code: 1886ms)
POST /api/webhook/stream 200 in 514ms (next.js: 4ms, proxy.ts: 9ms, application-code: 501ms)
......
⨯ Error: Stream connect_agent failed (code 42): Error: code
at ignore-listed frames {
type: 'error',
error: {
type: 'server_error',
code: '42',
message: 'Error: code ',
param: null,
event_id: ''
}
}
- Lenguaje dominante
- TypeScript
- Estrellas
- 19
- Forks
- 3
- Merge medio
- 1 d 5 h
- PR fusionados (30 d)
- 11
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de GetStream/stream-node
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
GetStream/stream-node#132 · 2 comentarios ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
GetStream/stream-node#2 ·
Todos los issues de GetStream/stream-node
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
bug v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
modelcontextprotocol/inspector#2458 · 1 comentario ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 75/100
railmapgen/rmp-gallery#4068 ·
-
Mend: dependency security vulnerability status: needs triage 🕵️♀️
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
carbon-design-system/ibm-products#9907 ·