Conax DRM for Nagra Security Services Platform

Configure DRM for a stream as follows:

stream example_stream {
  input udp://239.0.0.1:1234;
  protocols dash hls;
  meta drm_id ev0234; # Optional, drm_id is a stream name by default
  drm conax keyserver=https://<domain_name> user_path=<key_server_path>;
}

Configure DRM for a VOD location as follows:

file drm {
  path /storage/vod;
  protocols dash hls;
  drm conax keyserver=https://<domain_name> user_path=<key_server_path>;
}

Here:

https://<domain_name> — a keyserver URL with credentials provided to you by Conax. Example: https://12345-op.anycast.nagra.com
user_path — your custom key server path. Example: 12345/nks/conax
drm_id — this parameter is called ContentId in Conax. If you want to specify ContentId in a live stream configuration, use the meta drm_id <ContentID> directive. For VOD files, for example, for /path/to/vod/content.mp4, Flussonic reads ContentId from the /path/to/vod/content.mp4.conax_id file.

Configuring the DRM systems in use

If you turned off some of the systems (for example, FairPlay) in your Nagra account, you should specify in Flussonic the systems that remain in use. Otherwise, an error will occur in Conax, and it will be impossible to play the stream.

Note

Flussonic issues the event 'drm_key_fetch_error' with the error description if DRM responds with an error.

To avoid errors after you turned off a DRM system, use the option systems where you specify which DRMs can be used.

For example, drm conax systems=widevine,playready

stream example_stream {
  input udp://239.0.0.1:1234;
  protocols dash hls;
  meta drm_id 123;
  drm conax keyserver=https://<domain_name> user_path=<key_server_path> systems=widevine,playready;
}