Signalr Owin Self-Host on Linux/Mono Socketexception When Clients Lose Connection

Clients can make maximum 15 connections to linux custom server in mono

I was using mono 2.6.7. Upgrading to 2.10.8 solves the problem.

Which socket serverside software for video conferencing?

Disclaimer: I work at XSockets.

I would use OHM's law in combination with what hosting you are planning.
With XSockets and SuperWebSocket you will have support for full-duplex communication (websockets) on all server platforms.

SignalR and Microsoft.WebSockets require Win8+/2012 Server and IIS8 to be able to provide websockets on the server. If you use another platform you will get half-duplex techniques (SSE, Longpolling...) See supported platforms
Maybe that is why you ask about SignalR being slow since you will run on Linux and that means that you will not get WebSocket-support from the server when using SignalR/Microsoft.WebSocket?

When it comes to implementation both SignalR and XSockets has implementations of WebRTC (I assume that it is WebRTC you are talking about event though you do not mention it). I have no idea if SuperWebSocket has any WebRTC samples, but you should be able to port the samples of SignalR and XSockets to SuperWebsocket if you want to.

When it comes to client support there is obviously the issue with IE, but Chrome, FF and Opera will support WebRTC in desktop. On mobile you will have support on Android, but on iOS you will need something like this Cordova lib
It is tested with XSockets webrtc implementation, but I cant speak for others. Should work with the SignalR implementation as well, but we have not tried that.

So, IMHO you should choose between 1,2 and 4 depending on server platform and the implementation that suits your project the best.

Option 3 is probably not a good choice at all...

EDIT:
A link to a WebRTC sample

Related Topics