Your terminal window should look like this: In a new terminal window, we’ll tell Ngrok to forward TCP traffic for port 1935 (the default RTMP port) through our public tunnel ngrok tcp 1935 Now that we have confirmed the server accepts RTMP streams, we’ll need to set up our server so that it is accessible to Zoom.Ĭurrently, it’s hosted on localhost, and in order to make the server accessible publicly, we’ll need to use Ngrok. They might need to analyze the audio and video to create a transcript and gather details needed for their service.Īfter, they could overlay their data on a recording of the meeting captured through live stream. This enables developers to record the live stream or parse audio and video.Īn example of this would be a service that offers analytics on meeting content.
There are quite a few use cases for utilizing a custom service and that is because this option is designed to allow developers to receive an RTMP stream of the meeting at an endpoint they provide. This allows them to watch and engage with the content where they otherwise wouldn’t be able to. For example, when using YouTube or Facebook as your streaming service, you can redirect participants to the live stream. This might be because you’ve built an audience there or because it adds to how discoverable your event is or simply because you can distribute your recorded content easier on that platform.įor example, if you have an established YouTube channel it makes the most sense to stream the event to your subscribers and/or have it available for them directly on YouTube.Īnother common use case for live streaming is to offload additional attendees when an event is full. The primary use case for livestreaming is to bring your Zoom meeting/webinar to a different platform.
0 kommentar(er)
