Set account login and password and save changes:

STB without provision, may be configure by this way:

From the Launcher screen go to TV settings

Choose Middleware API protocol (same as jsonapi in provision)

Setup protocol:

As server you must setup address of your server, example has http://tvip.media as server address:

After applying server you must see “Register” buttom, click button and enter account credintails.

After successful registration you can go to TV interface and check channel aviability.

In same cases yo can use Quick bind feature, used for pre activations boxes:

1. Eneable option “Allow quick device bind” in provider settings (Settings → Providers)
2. Add unique id of device in Device Editor (Account editor → devices grid, then click “+” in to left corner)

Limits of this method are disabling unregister feature from the box, all devices will be remvoe “Derigstration” from UI

Subscriptions plans (Tarif) joined to channels via Tags, example of this relations are pictured below:

In this example:

• Channel “Channel A” and “Channel B” tagged by tag “public channels”
• Channel “Channel B” and “Channel C” tagged by “sport channels”
• Tarif (subscription plan) “All channels” included both tags (“public channels” and “sport channels”), this Tarif (subscription plan) are included all channels: Channel A, Channel B, Channel C
• Tarif “Sport channels” include only “sport channels”, then that tarif included only Channel B, Channel C.

Same hierarchy allow flexibility tarif setup.

Tarif plans may be mapped to device and account entities, device subscriptions have more priority than account, account tarif plans will be accepted to device if device are not have tarif plans

In the sametime device and account may be have anymore subscriptions, system is merging subscripions to summary playlist.

TMS are support DVR from Flussonic streaming server.

Minimal channel setup on flussonic :

stream TEST{
  url udp://225.100.50.10:1234;
  dvr /media/HDD2 6d;
}

In this config we are declare channel TEST with DVR for 6 days, archive will be stored to “media/HDD2”, and archive will be allowed via HLS

More about DVR setup you may read there

Declare DVR server via Channels→ DVR Servers In DVR editor will be setup theese parameters:

Base URL (not channel!), in our example that is http://fs.example.net, if your flussonic use non-standard port for streaming you must enter port via colons. For the server specify archive deep (in our example - 86400), that value will be used if channel specifed value is empty.

For the mapping Channel with Flussonic entity used attribute System name, that attribute will be same with Channel declaration in flussonic (in our Example - TEST)

At the Archive tab of Channel specifty server where archive stored: Also in this tab may be override archive deep from default value (defined in DVR server). Value presented in seconds.

Before 4.0.11 archive indicated by icon “Play” in the EPG screen:

From 4.0.11 version icon changed to cinema film in the EPG screen:

STB used “deep value” from TMS, if archive unavailable STB return to live stream.

After pressing pause button STB stay on timestamp and using DVR for playing from knowing timestamp. Local storage is not used for this case.

Yes, we support JSON REST API, documentations included to distributive, API may be extended from version to version, about new features you can read at changelog article.

Link to doc's you may found in top right corned of Admin panel:

TMS with Flussonic streamer support AES-128 encoding.

1. flussonic are requesting encryption keys from tvip-cas server and encode content by that key, key rotation every 10 minutes.
2. HLS playlist has special link to decription key, client after detecting that link will be trying to request key via presented link (to tvip-cas)
3. TVIP TMS and tvip-cas are sync liceinse information, if licenese is allowed to device tvip-cas answer to request with key, else - answer with error.

About tvip-cas you can read in this article.

You can read this doc at Flussonic web site for explain how Auth via Middleware may help protect your streams.

1. Enable Flussonic auth feature for provider:

2. Enable feature for channel:

3. Setup auth path in Flussonic for each stream http:/tms.example.com/api/drm/auth_token: