I am not sure what happen. I have service monitors running in background but none appear to have reported any services down. In some instance when a service is down the monitor will attempt to restart the service.
This issue happen after I updated Kaltura CE to the latest version and got a report that the live feed were not loading anymore. Since I was traveling it took two days before I could site down and dig in to investigate. After reading the change notes and seeing that Ngnix was using live streaming I change the port configuration and restarted Ngnix which resolved the issue.
Short answer I do not know why Wowza stopped allowing Ngnix to take control over the port.
I mean that when I load my live streams into Wowza they are unquie URL with authentication data in the URL and configured in our firewall appliance at the source of the live feed. All 22 live feeds feed into Wowza stream from a single IP using different ports served from a IP camera server (appliance) which uses a combination of network cameras and wired cameras.
So for my configuration to be served from Ngnix I would need to know where to paste the source URL for each of the IP cameras to stream into Ngnix. Wowza currently allows us to pull from each source URL once and server multiple connections from a single live source. I see how to push a live feed using an app like FME to serve a live feed to Kaltura CE and then how to call to that feed from within Kaltura CE. I do not see how to create a LIVE stream from a static or dynamic URL source and feed it into Ngnix and then serve it to Kaltura.
My current setup limits the amount of bandwidth and connections using from the source and expands the connections and bandwidth by using Wowza and Kaltura CE as a relay with more resources available. I hope this clarifies your understanding of my setup.