I have a question about webhooks.

Wowza Streaming Engine
,
1

I want to use a webhook with the Wowza engine.

When I start a stream by sending an RTSP request, can I trigger an alert to a specified IP address?

I plan to create a Java program running on localhost to receive stream start alerts from the Wowza engine, store them in a database, and manage them.

Is this possible?

The webhook guide seems a bit complicated…

Which REST API URI should I configure to receive stream start notifications?

I want to receive alerts for:

  • RTSP transmission start
  • Stream information (codec, resolut
2

Hello,

Thank you for reaching out in Wowza Community Forum.

You can configure the WebhookListener in Server.xml and add a Webhooks.json target (your Java app URL); Wowza will POST stream.started, stream.stopped and recording.* events. You would need to ensure that the target URL is reachable from the Wowza server.

You can read about it in the following documentation: Create webhooks to monitor streaming events

Additionally, you can use the REST API calls to get stream statistics by referring to the following documentation: Get stream statistics with the REST API

However, there are no REST API Calls to get Stream Information like Codecs and resolution using REST API calls. We will create a feature request on your behalf to include this functionality in future release of Wowza Streaming Engine.

Hope that clarifies your doubt.

Best Regards,

Drumil Desai

Technical Support Engineer

Wowza | The solution you start with, the partner you scale with.

3

cwkang,

If you are up to writing a java module, the WSEs Java APIs will get you that info. A more custom solution would handle the unsupported event types, and could make this more specific to your use case. And make it easier to config/deploy, Can be banged out pretty quickly.

Another option is a custom solution developed by a consultant, such as myself. I know the APIs quite well

Scott Kellicker, independent

scott@blankcanvas.video

1 Like
4

I was setting it up incorrectly.

It’s resolved now.

Thank you.