Realtime API SIP Calls Failing with 403 Forbidden

Issue Description

Our SIP integration with the OpenAI Realtime API suddenly stopped working. All outbound SIP calls to OpenAI’s endpoint are being rejected with SIP/2.0 403 Forbidden, even though HTTP/WebSocket authentication works perfectly.

What’s Working

  • :white_check_mark: Webhook verification succeeds

  • :white_check_mark: HTTP API calls to accept endpoints work correctly

  • :white_check_mark: WebSocket connections authenticate successfully

  • :white_check_mark: Project settings and billing are confirmed as normal

What’s Failing

  • :cross_mark: All SIP INVITE requests rejected with 403 Forbidden

  • :cross_mark: OpenAI leg fails to connect to conference

  • :cross_mark: Calls reach the user’s phone but no AI audio (silent call)

Current Status

100% failure rate on SIP calls over the past week

Troubleshooting Already Done

  • Generated new API key and deployed

  • Removed old API key

  • Verified FreeSWITCH gateway configuration is correct

  • Confirmed project has Realtime API access

  • Checked billing status (all normal)

Configuration

  • Using FreeSWITCH with TLS transport

  • SIP gateway configured with correct endpoint and project ID

  • Same setup that was working previously

Question

Has anyone else experienced SIP authentication failures recently? The fact that HTTP/WebSocket auth works but SIP doesn’t suggests this might be a service-side issue rather than our configuration.

Tags (if available):

  • realtime-api

  • sip

  • api-error

  • troubleshooting

I’m using Asterisk in a similar configuration. I tested it now, and it’s working.