Skip to main content

UDP destination

LTN Global
Updated

About: Publish to destinations via UDP.

Hint: UDP destinations do not support packet-loss recovery. Lost packets will not be recovered. UDP destinations should only be used for controlled environments in which no packet loss is guaranteed. Do not use UDP destinations for connections of the public internet.

 

Not sure how to start?

→ Learn to create destinations.

Create a UDP destination

To create a UDP destination, modify your destinations, add a new destination and follow the instructions below:

outputs-adddestination.png

  1. Enter a name.
  2. As type, select "UDP".
  3. Click "Save".

Continue your configuration in the new dialog appearing:

outputs-udp.png

  1. Enable/Disable: Activates or deactivates the destination for publishing.
  2. Target name: As described above, the name of your destination.
  3. URL (port): Enter the destination URL and port.
  4. Write ad trigger as SCTE-35 markers into output: Activate to write configured events and markers from incoming live streams into the outgoing stream.

Press "Modify destination" (5) to save your changes. Your destination is now ready to use.

Configure Custom API Calls (Webhooks)

With the Custom API configuration events (Webhooks), you can start/stop external services, transmit the playing element metadata such as title and description, and transmit ad-trigger information to external APIs. (Available since version 9.5)

These API webhooks can be configured and activated by switching on the five API configuration event areas for each output push destination (RTMP, HLS, SRT, TCP, and UDP) as needed.

 

Cutom_API_Calls_-_Webhooks_1.png

 

  • Publish Start: This webhook is called when Schedule starts pushing to this target.
  • Publish Stop: This webhook is called when Schedule stops pushing to this target, such as when it's disabled or playback is stopping.
  • Ad Start: This webhook is called when an advertisement call is starting. This could be triggered by a received SCTE, manual ad break, VOD ad break, or any other relevant event. You can also add AD_DURATION and PREROLL (seconds) values, configured for assets of your playlist, within the API string with {} like this {AD_DURATION} to hand over those values to the external API. 
    • Example:
    • "method": "POST"
"requestUrl": "http://localhost:59191/ad/{AD_DURATION}/{PREROLL}"
  • Ad End: This webhook is called when the started advertisement call has been cancelled. This could be triggered by a received SCTE for cancelling or manual cancellation.
    • Example:
    • "method": "GET"
"requestUrl": "http://localhost:59191/adcancel"
  • Element Switch: This feature is called when the playlist switches to the next element.
    • Example:
    • "method": "GET"
"requestUrl": "http://localhost:59191/switch/{TITLE}/{DESCRIPTION}/{PREROLL}"

 

To use a custom API Call:

Cutom_API_Calls_-_Webhooks_3.png

 

  1. Switch on one or multiple webhooks you want to use
  2. Enter the API URL
  3. Select one of the Methods GET or POST
  4. Optional: If you want to use a request header, enter the header name
  5. and the header value
  6. Optional: If you want to use multiple request headers, click the plus button to get more inputs

 

How to continue?

→ Learn to activate/deactivate your rundown.

→ Learn to turn on/off destinations.

Related articles