Wowza vs FusionPBX

Wowza's feed is its marketing blog, and the last six posts are effectively one campaign: the Video Intelligence Framework, an inference layer that pulls frames out of Wowza Streaming Engine, routes them to models, and returns detections as metadata, overlays, and alerts. Four of the six entries are VIF explainers aimed at utilities, traffic management centers, hospitals, and stadiums — operators with hundreds of cameras nobody watches. The shipped engineering sits just outside this window: Streaming Engine 4.11 rebuilt the WebRTC stack around WHIP/WHEP signaling, full ICE connectivity checks, and configurable STUN/TURN.

The two halves fit together. WebRTC modernization is the delivery side — sub-second camera video to an operator in any browser without a custom SDK — and VIF is the analysis side, and the traffic-management post explicitly joins them. Wowza is repositioning a media server as infrastructure for operational video, where the buyer is a facility or agency rather than a broadcaster. Note that cadence here measures blog output, not releases, so velocity reads higher than the shipping rate warrants.

Expect the VIF campaign to keep running ahead of the product, and for the next concrete move to be packaged detection models or customer-trained model support — the "train your own model" post reads as demand-testing for exactly that.