{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifn5bjh5k7mfhhderatnvccnfp5gv5jfczbhrxdhm3o3442chm54e",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mlnhqyff6wa2"
  },
  "path": "/t/firefox-realtime-api-webrtc-voice-sessions-drop-deterministically-on-the-users-second-speech-turn/1380257#post_9",
  "publishedAt": "2026-05-12T09:08:35.000Z",
  "site": "https://community.openai.com",
  "textContent": "> Hi Prashant — the `x-request-id` response header doesn’t appear to be exposed to JavaScript via CORS on this endpoint, and Firefox DevTools’ Network panel isn’t capturing the cross-origin POST for some reason. Here’s the precise timestamp anchor for the failing request instead:\n>\n>   * **POST** `https://api.openai.com/v1/realtime/calls?model=gpt-realtime-2`\n>\n>   * **Sent:** `2026-05-12T09:00:26.078+02:00` (CEST, Warsaw)\n>\n>   * **Response received:** `09:00:27.595` (status 201)\n>\n>   * **ICE disconnect fired at:** `09:01:07.934` (~40 seconds later, 8.3s after `response.created`)\n>\n>   * **Same Firefox 150 / Win64 / gpt-realtime-2 flow.**\n>\n>   * **Earlier failing repro for reference:** `2026-05-11T12:55:55.603+02:00` (POST sent) → ICE disconnect at `12:56:38.554`.\n>\n>\n\n>\n> Let me know if there’s another way to capture the request ID on your end, or if I should adjust the repro to log it differently. Thanks.",
  "title": "Firefox + Realtime API (WebRTC): voice sessions drop deterministically on the user's second speech turn"
}