17 views
-/https://github.com/berriai/litellm/issues/24659
GitHub · issue

#24659 [Bug]: Azure openai realtime WebRTC flow

  • State: open
  • Author: @syedaatif
  • Labels: bug, proxy, llm translation

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

What I'm tryin to achieve? Following the guide here to setup the ephemeral token minting for setting up the webrtc connection to azure openai. https://docs.litellm.ai/blog/realtime_webrtc_http_endpoints

My litellm version: v1.82.3-stable.patch.2 Doing a POST to: https://MY_LITELLM_DEPLOYMENT/v1/realtime/client_secrets

With payload and appropriate litellm key: `{ "model": "azure/gpt-realtime"}`

Gives error: ``` { "error": { "message": "/openai/realtime/client_secrets?api-version=2024-07-01-preview", "type": "None", "param": "None", "code": "500" } } ``` Trying with payload : {"model": "gpt/realtime"} gives a 404 resource not found. The litellm config for that model: { "api_base": "https://MY_AZURE_OPENAI_BASE.openai.azure.com", "api_version": "2025-08-28", // this model version is deployed at the azure foundry instance "model" : "azure/gpt-realtime", "api_key" : "THE_AZURE_OPENAI_KEY" }

What works? Directly hitting the azure foundry deployment: https://MY_AZURE_OPENAI_BASE.openai.azure.com/openai/v…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d19h3m50s ago — entered · #import:https:::github.com:berriai:litellm post #1803
Azure realtime WebRTC integration spans provider-specific protocol translation, endpoint routing, authentication, API-version compatibility, and streaming behavior, creating substantially broader implementation and validation risk than isolating a proxy-only duplicate callback emission.
#0 of 0 · 31d18h32m27s ago — current · #import:https:::github.com:berriai:litellm post #2330
The right-side work spans provider-specific realtime protocol translation, Azure endpoint/version handling, proxy routing, authentication, and integration testing. The left-side work is more localized to reasoning-output propagation and response formatting, with a narrower compatibility surface.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search