Startup Function not working with Websockets

[rohan-richard]

Hi, I am running into a weird error where if I use webRTC, my startup function emits the audio I want, but if I use a websocket on the same endpoint, it does not. In both cases, when I start talking, it responds normally in the same way, but the difference is the way the startup function works.

[freddyaboulton]

hey! Probably an oversight. Will take a look

[mahimairaja]

Hey @rohan-richard

Can you please share the instructions to reproduce

[tusharrrr1]

Make sure the startup function’s audio goes through a common abstraction (e.g. sendAudioFrame(buffer)) that works the same whether the transport is WebRTC or WebSocket. That way, you don’t rely on WebRTC’s auto-track behavior.
let me try this if possible?