Различия

Здесь показаны различия между двумя версиями данной страницы.

--- tvip_tms_changelog [2018/08/13 11:50]
Egor Danilenko
+++ tvip_tms_changelog [2018/11/06 12:41]
Egor Danilenko
@@ Строка 1: / Строка 1: @@
 ====== TVIP TMS Changelog ======
+<WRAP center round important 60%>
+=== Update requirements (from version before 3.1.12 to 3.1.12 and newer) ===
+From version 3.1.12 TVIP TMS require <color #ed1c24>java 11</color>.
+If you use version before 3.1.12 - you are using JAVA 10. For prevent startup issues (newer TMS is not support Java 10) after updating to newer version, we are recommend the next scenario (steps for Ubuntu users):
+) Update your repositories:
+<code>
+apt-get update
+</code>
+) Install Java 11, if you have plan to use Oracle Java 11, you can use  oracle-java11-installer package from our repo (this is copy of deb package from linux uprising ppa)
+<code>
+apt-get install oracle-java11-installer
+</code>
+) This is important - set java 11 as default
+<code>update-java-alternatives --set java-11-oracle</code>
+) Check java version: <code>java --version</code>
+) After version check - install newest tvip-tms: <code>apt-get install tvip-tms</code>
+) Restart tvip-tms service: <code>service tvip-tms restart</code>
+Notice: Java 11 is not affected to runned process. If you  install java 11 and not install tvip-tms (3.1.12 and higher) you must set Java 10 as default.
+</WRAP>
@@ Строка 8: / Строка 35: @@
 From version 3.1.0 TVIP TMS require java 10.
-You must install java 10 or above by yourself. You can find distributive on [[http://www.oracle.com/technetwork/java/javase/downloads/jre10-downloads-4417026.html|Oracle web-site]]
+You must install java 11 or above by yourself.
 </WRAP>
+==== 3.1.12 (06.11.2018) [beta] ====
+=== Fixed ===
+* TVIP API: Fixed bad URL of images assigned as VoD entry series logo.
+=== New features ===
+* TVIP API: Updated up to v2. It supports some new features and backward compatible with v1.
+* General: TMS requires Java 11.
+==== 3.1.9 (08.10.2018) [beta] ====
+=== Fixed ===
+* XML RPC: Some fixes have been applied for outmodel devices like DIB to provide compliance with new features.
+* XML RPC: Fixed case when the creating device with existing unique ID for account will result in device with no account.
+* JSON API: Fixed timeshift depth available, even if no timeshift enabled.
+* Admin API: Fixed the problem of creating the VOD source item "Quality" field has no value to set.
+* Admin API: Fixed problem when "Apply" button stays disabled after any channel changed.
+* Admin API: WS interaction has been improved to represent the more accurate state of device connection.
+* Admin API: Fixed that non-global admin provider was set as default when creating a new device.
+* Admin API: EPG source now may be a file having no name extension like ".xml". Such file with no extension will be considered as XML.
+=== Improvements ===
+* Performance: general performance parameters have been optimised for high load. If you override any such properties, please, consider to eliminate your overrides, because your parameters may be not optimal solution.
+* JSON API: We're still working on accurate interaction with devices in different cases. As a part of this, now you may allow your devices to work in networks that are not specified for your provider networks (<server.url>dmin#provider_networks) and domains (<server.url>admin#provider_domains). To enable this feature, select "Enable device roaming" checkbox on your provider editor form (<server.url>/admin#providers). It's disabled by default.
+* JSON API: Search API has been updated with new parameters like genre, rating and so on.
+* JSON API: EPG import and update has been optimised and performance has been increased. In addition, new validation procedures have been added to eliminate problems like no EPG, even it's available in the EPG source, or need to upload EPG manually under force mode. But the option to force EPG import manually remains available.
+* JSON API: Strict security mode has been implemented. You may disable it, if you'd like to use "Quick bind" not only as the first auth mode, but the following auth requests. Be aware to use this feature because it will slightly decrease the JSON API security. You may find this option in provider editor form (<server.url>/admin#providers)
+* Media: media selections rules now are filtered by provider assigned to the particular admin.
+* CAS: If you have no CAS data specified, the default TVIP configuration will be added.
+=== New features ===
+* Media: You may find details on how to use this new feature here([[en:tvip_tms_media_guide|]]).
+* Flussonic support: Now you may use Flussonic content protection described here (https://erlyvideo.ru/doc/auth/middleware).
+To enable it from TVIP TMS, you need to switch on "Flussonic auth enabled" checkboxes on your provider editor form (<server.url>/admin#providers) and the particular channel editor form (<server.url>/admin#channels). It's disabled by default.
+To enable this feature on Flussonic, you need to add path (<server.url>/api/drm/auth_token) as "auth" parameter of Flussonic config file.
+The feature will work for those channels only that are tuned for Flussonic stream server for live and timeshift playback. To provide more reliable security, you may specify a secret key in application.propeties as 'flussonic.app.secret.key' property.
+* Admin UI: Tariffs with no provider may be created. These tariffs must be created by global admin and may be used by any provider. Any admin may apply these global tariffs in subscriptions regardless of his provider assigned and state is global or not.

TVIP Wiki

Инструменты пользователя

Инструменты сайта

Различия

Инструменты страницы