Great thanks, we will test and report if succeed here in a few.
Thank you for your prompt response. If you could also add a SIP connection category to the OpenAI status page, it would make it easier for us to explain the situation to our customers, so we would greatly appreciate it if you could consider this.
Ok we are fully rolled back to the old code!
I will work on fixing the PCMA+Silence bugs. Again I am really sorry for the mistake. These are all things I should have caught in automated testing.
Its working now thanks @Sean-Der
Working also here @Sean-Der
Thanks for the rollback.
Isn’t there an update feed that we can subscribe to be aware of the changes you plan to make or made ? To prepare ourselves for eventual adaptation on our own.
+1
it should be useful having a “warning” in order to check internally after the release
It works thanks @Sean-Der
This was a change that should have required zero effort on your side. I am trying to consolidate servers. Right now we are running a fleet of servers for SIP + WebRTC. I was trying to merge it into one codebase.
I don’t think we would have made an update/announcement on this. It was only noticeable because of my mistakes.
We are currently running 25% of the servers on the new code with bugs fixed. I am watching logs and will rollback if I see any issues.
Wanted to notify everyone in the thread!
Hi,
For about 15 min ago, we start receiving “SIP/2.0 403 Forbidden” on our sip Invites.
Any issues on your end?
/ Magnus
My logs + test calls are doing well!
What was the response you got from the /accept call? A 403 I believe is from a invalid Realtime API session.
Do you have any session ids?
Hi,
Actually we are not getting so long, SIP gives us 403 before it even send an webhook.
/ Magnus
Could you email me directly seaduboi@openai.com @magnus.lofqvist with some details that identify your sessions (numbers, project ids etc…) and I can debug?
I don’t want to make you post anything identifying on the forums. Sorry about the issue you are having 
@Sean-Der I have same issue as @magnus.lofqvist , I will send you email directly with details identifying my sessions, too.
Thanks for the emails everyone! It seems like people are getting 403s after 5 seconds. This was also reported in Realtime API unreliable over SIP
Two things that could be going wrong
- Webhooks are getting delivered slowly
- Timeout should be 10 seconds, not sure why time between 403 and INVITE is only 5 seconds. Are we seeing 5 seconds of latency in a different part of the system.