The first week of any internal broadcast deployment is less about the hardware and more about the decisions that surface once the equipment is on site. We spent most of day one mapping the existing office network, checking where the switch rooms sat, and identifying which floors would need additional cabling before the streaming nodes could go in. The plan looked clean on paper, but the real layout of the building changed a few of our assumptions.
Bandwidth was the first constraint we hit. The headquarters had a solid fiber uplink, but the internal LAN was segmented in a way that created bottlenecks for live video. We ended up reallocating a few VLANs and moving the media server closer to the core switch. That single change cut the average latency for the test streams by nearly a third. It was a simple fix, but it required coordination with the building's IT team and a clear explanation of why the change mattered.
The second issue was the streaming protocol. We had planned to use SRT for the main feed, but the existing firewall rules made the UDP traffic difficult to manage. After a quick comparison, we switched the primary path to WebRTC for the interactive sessions and kept SRT for the one-way announcements. The tradeoff was straightforward: WebRTC handled the Q&A format better, while SRT gave us the stability we needed for the larger town hall broadcasts.
By the end of the week, the system was running, but the real lesson was about expectations. The staff had never used an internal streaming platform before, so the first two days were spent on basic training and troubleshooting access issues. Once the login flow was simplified and the player was embedded in the existing intranet page, adoption picked up quickly. The feedback from the pilot group was direct: they wanted shorter streams, clearer schedules, and a way to rewatch sessions they missed.
The week closed with a working setup and a list of adjustments for the next phase. The infrastructure held up, the network changes were documented, and the team now has a clearer picture of what the second week should address. If you are planning a similar rollout, the practical takeaway is to start with the network layout and the protocol choice, because those two decisions shape everything else.
For more context on how we approach these deployments, see our earlier posts or get in touch with the team.