Understanding Licensing

licensing portability, evaluation and expiry zixi broadcaster and zec licenses govern what connection modes a device can use, how the license validates itself over time, and how that license behaves when hardware changes this article covers the areas that prompts the most questions license portability during hardware migration, license expiry and validation behavior, and connection mode limits by license tier license types metered vs perpetual every broadcaster or zec license is issued as one of two types, and the type determines how the license validates itself while the device is running perpetual license issued for the life of the hardware or a defined term, with no recurring validation requirement against zixi's licensing servers metered license requires the device to check in with zixi's licensing servers on a recurring basis to remain valid 72 hour license server check in requirement a metered license must successfully check in at least once every 72 hours if the device cannot reach the licensing server (due to network outage, firewall change, dns failure) within that window, the license enters a failed validation state and will de activate the connections relying on that license will be rejected, even though the license itself is still good and the portal listed expiry date is unaffected the device will require the license to be re activated to restart connections license portability & new machine detection licenses are tied to a hardware fingerprint (host id), not just a license key certain hardware changes are treated as a new machine and require re activation what triggers a new machine detection • a nic change on the host, since the primary network interface is part of the fingerprint used for activation • an ip address change alone does not typically trigger new machine detection on its own, but is often accompanied by a nic change during migrations which does trigger one • moving the license to genuinely new hardware (new vm, new physical host, cloned image with a new interface) how license activation works each license has a fixed number of activation availability slots activating on a new machine consumes one slot decommissioning the old server does not automatically return its slot to the pool slot recovery after decommissioning, and re activation on replacement hardware, both require zixi to release and reissue an activation your sales team or solutions engineer can assist you with additional activation slots for broadcaster for zec you can issue additional activation slots yourself within the zixi portal migrating a license to new infrastructure 1\ confirm the license type and current activation count in the license portal before starting the migration 2\ provision the new hardware and retrieve its host fingerprint (host id) from the broadcaster or zec installer 3\ submit the new host id to zixi along with the license key and a request to release the old activation slot, if the old server is being decommissioned 4\ apply a new activation slot to the new machine once zixi confirms the activation slot has been added to your account 5\ decommission the old server once you confirm the new machine is up and active steps 1, 2, and 4 are self service step 3, releasing or reassigning an activation slot, requires zixi involvement and is not available directly in the zixi portal prepare ahead when scheduling your migration connection modes by license feature license features determine which input and output connection modes a broadcaster or how zec is permitted to run, independent of whether the physical hardware can support them all of these may have specific limits push input the license permits the device to receive a stream initiated by the sending encoder listener input the license permits the device to open a port and wait for a third party encoder to connect to it push output the license permits the device to initiate an outbound connection to a receiver listener output the license permits the device to wait for a downstream receiver to connect third party encoders vary in which mode they support when integrating a third party device, confirm both that the broadcaster/zec license permits the required mode and that the third party encoder itself supports initiating or listening for a connection accordingly mismatches here are a common source of connections that appear licensed at the device level but fail to establish license comparisons for zec, broadcaster, feeder & receiver zec has specific limitation which requires using zixi protocol as either the input or an output for each stream troubleshooting license failed before expiry a license failed error appearing before the portal listed expiry date is not an expiry issue it typically points to one of two causes check in failure on a metered license (see the 72 hour requirement above) server side recognition failure following a license push or update in the second case, a corrected or reissued license push from zixi resolves the failure this can affect both the zixi broadcaster and third party licensed devices connected to it, so a license failure on a downstream third party device does not rule out a licensing issue on the upstream broadcaster immediate remediation steps 1\ confirm the expiry date listed in the zixi portal to rule out an actual license expiration 2\ check network connectivity from the device to zixi's licensing servers if the license is metered see the network port settings docid znprthruh2rzo8rhei2z 3\ contact zixi support with the license key, the affected device's host id, and the timestamp the failure began