Making high-risk changes in a real-time production application; a Media Server Migration

I will walk through the key steps for migrating a media server, including requirement gathering, evaluating media server options, planning, implementation and testing.

I will explain it from the perspective of a migration project we performed for a real-time production application for a client. The aforementioned application had multiple features, like conference and webinar rooms, a call center with IVR, outbound calls, recordings, and live transcription and translation, which makes a migration more complex than a basic meeting application. In this case, we migrated from Kurento to LiveKit, making use of the LiveKit Agents framework to integrate with AI agents for some of the workflow (call center solution and live transcription and translation).

This migration simplified the architecture and application, fixed some of the issues the previous one had, improved the performance both client side (while in a meeting) and server side (less resources used), made it more scalable (can handle many more and way bigger meetings) and allowed us to easily integrate with more modern AI solutions.