Hi we are seeing a weird behaviour with realtime webrtc api. Currently we have built push to talk feature which basically unmutes the user and mutes the user. We use webrtc api to do muting and unmuting as follows.
audioStreamRef.current.getAudioTracks()[0].enabled = false/true
This whole thing was working 24 hours ago, now it just keeps speaking no matter what the user is trying to say. We haven’t made any changes to the whole system since last 48 hours.
Surprisingly openai-relatime-console is working fine.(It doesn’t allow mute/unmute and just handles vad)
Debugging we tried:
- Changed models.
- Rolling back to a week earlier version which was working.
- Using an api key from another account(in case of caching or rate limit)
Nothing worked, it is still not responding to the user query no matter what user is speaking. Also updated chrome in case there were any changes in browser webrtc.
Anyone else facing similar issue or have idea what could be rca for this?
1 Like
I think both Websocket and WebRTC are having issues. We are using WebSocket and its not working at all on Chrome.
I see. Have reached out to support as well. They have raised it to engineering.
1 Like
How do you know they have reached out to Egg? Coz I have raised the ticket for now 10 hrs and no one has come back.
Got a reply from their support team.
1 Like
I heard there was an Azure issue that may have been fixed. But we are still seeing outage. What about you?
Looks like its fixed now.
Not the audio input feature.
Is this the exact same issue you all are facing or am I doing something wrong?
I tested this in chrome and edge, throws the same error. But in safari, the console has no errors but the mic isnt functioning anyways.
Seems like they have removed the response.create event flag. Hence you can’t manually create the response.
The issue with muting/unmuting in your push-to-talk feature could be due to browser updates, microphone permission resets, or changes in WebRTC handling. Test in Incognito Mode or a different browser to rule out interference. Ensure the audio track is still valid and properly targeted. Check your WebRTC setup and try disabling Voice Activity Detection (VAD) to see if it conflicts with muting. Also, look for JavaScript errors and check network conditions, and consider restarting the stream to refresh the setup.
