What is Server-Side Media Processing?
WebRTC is designed to send media directly via peers. Often this occurs between two clients, but many applications require the server to act as a media peer.
When does server-side media make sense?
Many applications require or perform more efficiently when media is anchored in the network. Media processing helps optimize bandwidth and minimize CPU cycles while adhering to regulatory requirements.
Mobile devices, fringe areas, and developing regions often do not have sufficient bandwidth.
User is paying per GB
WebRTC media flows can consume significant network capacity, inhibiting users with data caps from using your app.
Power is limited
Handling WebRTC media flows and stream processing consume many processing cycles, burning valuable battery life in mobile applications.
There is regulation
Existing regulations often require recording and analysis of media for compliance purposes.
Major server-side media use cases
Dialogic’s PowerMedia XMS provides widely needed capabilities in many applications. While WebRTC is designed to be primarily browser-to-browser, there is a growing number of use cases that require server side media support or that would be greatly enhanced by it.