How the Zixi ESAM Agent Works

market switching via esam content switching the content switching component of the agent leverages the broadcaster’s redirect client json api call to switch the input connected to an output regardless of input or output type to adhere to scheduling requirements, zixi employs multiple types of switches as follows when switching off the source that reported the scte message that triggered the switch, the broadcaster will search for the pts within that stream before switching when switching from a different source to the source that reported the scte that triggered the switch (typical in a blackout workflow), the broadcaster will search the upcoming source for the pts if neither situation is applicable, the broadcaster will attempt to search for pts within the upcoming feed (assuming streams are synchronized in that circumstance) if pts is not found, it will switch after the pre defined timeout period all switching is seamless, meaning the broadcaster will wait for an i frame (which generally coincides with a scte message’s defined pts regardless) scte manipulation the scte manipulation component of the agent interfaces with an external pois server the agent sends all relevant scte messages to the external decisioning service as base64 and receives back an action to take on existing stream scte and updated scte payload in base64 if applicable actions are taken from the agent via the broadcaster’s add stream scte json api for more information, on api calls, refer to zixi broadcaster api manual on the customer portal special operating modes you should only use these modes if required by sds singlestreammode in this mode, the esam agent will create a spe message for each esam enabled output regardless of what input that output is connected to for output based workflows, this allows for switching away from a looping file based on scte 35 messages seen on another input the only outputs excluded from consideration are outputs without an esam id and outputs that are connected to the input where the scte 35 was seen add to “sds” section “singlestreammode” true zoneidentityinspemode some sds’s require zoneidentity as an added spe parameter this mode will evaluate all acquisitionpointidentities against zoneidentities when sending spe only use this mode if required add to “sds” section “zoneidentityinspemode” true