Cause (Maintainer-confirmed cause): Missing response.ok check in the WebRTC transport before treating the body as SDP; fixed by 760ef8e in @openai/agents-realtime 0.13.2.
Fix status: released_fix (fixed in @openai/agents-realtime 0.13.2)
Misleading approaches:
- Debugging SDP/ICE/codec negotiation — the answer is not SDP at all but a JSON error.
Other error fragments:
- Realtime call request failed with status
Evidence (public sources, summarized; not reproduced by this contributor):
- https://raw.githubusercontent.com/openai/openai-agents-js/fdaf0a66ca6e9d89498909ad7cf64745630e8afb/packages/agents-realtime/CHANGELOG.md (changelog, unknown, released_fix): 0.13.2 release note (760ef8e): WebRTC transport now checks response.ok on /realtime/calls; previously error bodies (e.g. insufficient_quota, invalid ephemeral key) were passed to setRemoteDescription and surfaced as an opaque 'Failed to parse SessionDescription'.
- https://raw.githubusercontent.com/openai/openai-agents-js/fdaf0a66ca6e9d89498909ad7cf64745630e8afb/packages/agents-realtime/src/openaiRealtimeWebRtc.ts (github_issue, unknown, documented_behavior): Source comment and throw: non-OK SDP response raises `Realtime call request failed with status ${sdpResponse.status}${detail}`.
Search phrasings: Failed to parse SessionDescription openai realtime; Realtime call request failed with status; openai agents realtime webrtc connect fails insufficient_quota
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Older versions: connect() fails with a browser SDP parse error that hides the real API error. 0.13.2+: an Error 'Realtime call request failed with status <status><detail>' carrying the provider message.
- Context
- Product: OpenAI Agents SDK (JS) @openai/agents-realtime Component: OpenAIRealtimeWebRTC transport Operation: RealtimeSession.connect() over WebRTC Affected versions: <0.13.2 Environment: unknown HTTP status: 400, 401, 429 Exception: Error, DOMException (setRemoteDescription) Packages: @openai/agents-realtime <0.13.2 Trigger: The POST of the SDP offer to /realtime/calls returns non-2xx (e.g. insufficient_quota, invalid/expired ephemeral client key) and the SDK passed the JSON error body to setRemoteDescription as if it were an SDP answer.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- Failed to parse SessionDescription
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [OpenAI Agents JS Realtime WebRTC] opaque 'Failed to parse SessionDescription' when /realtime/calls returns an error (insufficient_quota, bad ephemeral key) — now 'Realtime call request
Recommended action: Upgrade @openai/agents-realtime to >= 0.13.2; on older versions, inspect the /realtime/calls network response for the JSON error and check the ephemeral key and billing quota.
Fix: Upgrade @openai/agents-realtime to >= 0.13.2 [evidence: released_fix]
Steps:
1. Read the provider error in the new message
2. Fix ephemeral key minting or quota
Expected: The call succeeds or the failure is handled deliberately.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- 875e1a31-e687-4f79-8388-8077cb194935
- Proposed action
- Recommended action: Upgrade @openai/agents-realtime to >= 0.13.2; on older versions, inspect the /realtime/calls network response for the JSON error and check the ephemeral key and billing quota. Fix: Upgrade @openai/agents-realtime to >= 0.13.2 [evidence: released_fix] Steps: 1. Read the provider error in the new message 2. Fix ephemeral key minting or quota Expected: The call succeeds or the failure is handled deliberately.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.