Voip Delay With 90+ connections.

[Bitou2k]

Hello, I am using the vRP2 Voip (WebRTC + nodejs + TURN server)

On my server, up to about 90 connections (players), voip works normally, but when more than 100+ people start to enter, there is a delay in the voice. People talk, and it takes up to 10 seconds of delay to receive the audio of what was said.
I would like to know if you, Imagic, have any suggestions or fixes so that I can continue using voip.
Example, which functions should be async, etc.

I appreciate if I can help.

[Bitou2k]

Imagic?

[mickeygeecom]

Sounds like something else is bottle-necking your server.
Are you getting hitches on the server console?

[Bitou2k]

Sounds like something else is bottle-necking your server.
Are you getting hitches on the server console?

no man. :/

[benzon]

Hmm sounds more like a bandwidth bottleneck to be honest.

Got to say i personally dont think WebRTC + nodejs + TURN server - is a good solution for ingame voice, use the integrated mumble og toko makes a lot more sence.

[Disquse]

@benzon It seems you're underrating modern WebRTC. Imagic's solution is not very scalable, it's true. But there's lots of ways to make WebRTC voip solution be able to handle hundreds or even thousands of actively talking people. Mumble is good too thought.

[benzon]

WebRTC works fine nothing there, but requires bandwith, and if you got it on the same server as fivem you might run in to a cap at some point, depends on your provider ofc.

[Disquse]

@benzon Mumble and WebRTC both using OPUS, there's almost no difference in bandwidth at the same bitrate (in case if your WebRTC solution is using SFU scheme). And I don't see anything wrong since it's very scaliable.

[Bitou2k]

There is a WebRTC solution created by one person, for the VioV server, I didn't get to test it, but it seems to be very scalable
https://github.com/Z8pn/VioVoice

I would like to use the vrp2 voip, as it is very simple and effective, you would only have to make it scalable from 200 to 500 players

[ImagicTheCat]

I'm not satisfied with the VoIP implementation, it's not very good. JavaScript, Node.js and WebRTC are to me overly complicated pieces of software; I don't feel sane when trying to workaround what I don't like / understand. And I can't use things I want with FiveM, like sockets or threads, thus I think I will just delegate by using other people's work.

[AleDema]

@ImagicTheCat Does that mean you'll switch to Mumble?

[ImagicTheCat]

@AleDema Probably not, it would use higher level libraries instead.

[AleDema]

@ImagicTheCat I meant the in game implementation of Mumble. It seems like its slowly becoming the standard. NoPixel is using it for voice chat along with RTC for calls/radio.