~1,200Camera feeds, managed via API
4Regions: North, Central, South and Hattiesburg
~100Cameras per origin, to preserve headroom
~200Streams per origin, with dual bitrates
“With Wowza, servers became appliances. We script, provision, move, and rebuild cameras through the API, keep our video walls fed, and let operators focus on incidents instead of plumbing.”
The architecture
Regional origins, one point of control.
Regional placement shortens paths and keeps operations predictable. Wowza stays the authoritative origin, while perimeter caches serve the public site.
What they did
A programmable origin, simple operations.
Automated ingest
MDOT’s Camera Manager treats Wowza as an API-driven fabric. Add a camera, select a regional host, and the application is provisioned automatically.
One-click rebuilds
If a stream drifts, operators trigger a one-click rebuild, turning servers into true appliances and reducing manual touches.
Efficient public delivery
Since adopting edge caching, MDOT has seen significant improvements in circuit utilization, while maintaining responsiveness.
Technical highlights
At a glance.
- Efficiently manages about 1,200 video feeds via API with Wowza Streaming Engine
- Automated ingest and management of about 100 cameras per origin
- Wowza Transcoder generates still images for maps and listings
- NGINX perimeter caches, with Wowza as the authoritative origin
- Runs on Ubuntu and AMD EPYC processors, validated for high stream counts in testing