Ant Media Server is a live streaming engine software that provides adaptive, ultra low latency streaming by using WebRTC technology with ~0.5 seconds latency. Ant Media Server is auto-scalable and it can run on-premise or on-cloud.
To clarify and understand things better, I would like to know if we use of SDK to develop iOS, Android, Window and Mac apps are enough to make end-to-end encryption or do you also need to modify the server to support end-to-end encryption.
Our purpose is to develop the WebRTC Conference call client for iOS, Android, Mac, and Windows10/11. Does current SDK support make End-To-End encryption without changing the server SW?
It is important to know how we can make the thing works if SDK supports the end-to-end encryption without touching server SW. Anyway server using relay NAT” (TURN) allows clients to send and receive data through an intermediary server or as STUN to find out the client's public address if so why do we need to change serve SW?
If you use Peer to Peer mode (mesh networking), SDK supports End-to-End encryption. It's likely that this is not your case. You likely need to have a scalable solution so that the server needs to support E2E encryption for the client side. Because data is relayed through server.
To clarify and understand things better, I would like to know if we use of SDK to develop iOS, Android, Window and Mac apps are enough to make end-to-end encryption or do you also need to modify the server to support end-to-end encryption. Our purpose is to develop the WebRTC Conference call client for iOS, Android, Mac, and Windows10/11. Does current SDK support make End-To-End encryption without changing the server SW? It is important to know how we can make the thing works if SDK supports the end-to-end encryption without touching server SW. Anyway server using relay NAT” (TURN) allows clients to send and receive data through an intermediary server or as STUN to find out the client's public address if so why do we need to change serve SW? If you use Peer to Peer mode (mesh networking), SDK supports End-to-End encryption. It's likely that this is not your case. You likely need to have a scalable solution so that the server needs to support E2E encryption for the client side. Because data is relayed through server.