Closed PaulCailly closed 6 months ago
@PaulCailly Sorry for not responding sooner, I had minor health issues. If you'd want you can drop me an email so we can try solving the case. You can post the solution here for the others if its helpful. BR!
I hope you're feeling better now. We've explored an alternative solution for the WebSocket and FreeSWITCH integration issue we discussed. However, I'm open to revisiting this with you at a later time to potentially refine our approach.
Are you having the same issue with an alternative solution in your use case?
We are now using Jambonz (same author as drachtio modules) as a cloud solution and it fits our needs for now.
Nice, so it's working for you. Glad you worked it out. I don't think (with mod_audio_stream) that the issue is module related. You start the streaming in pre-processing stage, before bridging the channel. At that stage channel has no media so nothing to stream, attached media bug receives closing event (no media on the channel) and it is disconnecting.
Hello,
I am working on integrating a Node.js server using NestJS with a FreeSWITCH server to handle real-time audio streams via WebSockets. I have set up a WebSocket gateway in NestJS and a dialplan in FreeSWITCH that executes a Lua script to start the audio stream. However, I am encountering an issue where the WebSocket connection is established (I can see the "WebSocket connection is open" log on my Node.js server), but I am not receiving any audio data.
Here is the relevant code snippet from my NestJS server:
And here is the dialplan from FreeSWITCH:
The Lua script being executed (start_audio_stream.lua) is as follows:
I am looking for guidance on how to properly configure the WebSocket module in NestJS to handle the incoming audio stream from FreeSWITCH. Any insights or suggestions would be greatly appreciated.
Additionally, here is the log output from FreeSWITCH:
Thank you for your time and assistance.