• s2_391120
  • 1.5MB
  • zip
  • 0
  • VIP专享
  • 0
  • 2022-06-15 00:59
Kaltura Wowza 媒体服务器 Kaltura Wowza 媒体服务器是为在 Wowza 流引擎基础架构上运行而构建的应用程序。 它是用 Kaltura Java 客户端编译的,允许它访问 Kaltura API。 该应用程序利用 WSE 动态流功能,结合 Kaltura API 进行身份验证和跟踪。 默认情况下,Kaltura Wowza 应用程序称为kLive 。 Kaltura API 集成 接口使用Kaltura 媒体服务器可以通过以下两种可配置方式之一使用 API 客户端: 相反的内置合作伙伴 (-5),它模拟所有 API 调用的已处理合作伙伴。 作为 eCDN 安装 - 在这种情况下,Wowza 服务器安装在客户端的机器上,而合作伙伴继续在 SaaS 安装对面工作(与本地安装相反)。 如此安装的 Wowza 服务器仅与它所属的合作伙伴 ID 相对,并且不使用模拟。
Kaltura Wowza Media Server ========================== --- The Kaltura Wowza Media Server is an application built to run over the Wowza Streaming Engine infrastructure. It is compiled with a Kaltura Java client, allowing it access to the Kaltura API. The application utilizes the WSE dynamic streaming capabilities, combined with the Kaltura API for purposes of authentication and tracking. By default, the Kaltura Wowza application is called **kLive**. --- Kaltura API Integration --- --- **API Usage** The Kaltura media server can use API client in one of two configurable ways: 1. Opposite built-in partner (-5), which impersonates the handled partner for all API calls. 2. As an eCDN installation- in this case the Wowza Server is installed on the client's machine while the partner continues working opposite the SaaS installation (as opposed to on-prem installations). The Wowza server thus installed works only opposite the partnerId it belongs to and does not use impersonation. The KS is regenerated periodically according to the KS expiry time. --- **Broadcast URL** Example URL to kLive application: rtmp://domain/kLive/?p=102&e=0_rkij47dr&i=0&t=dj94kfit The broadcast URL consists of the following arguments: * p – partner id. * e – entry id. * i – index (0 for primary and 1 for backup). * t – token. Stream name example: 0_rkij47dr_1 The stream name consists of entry id, underscore and stream index (between 1 to 3). The stream index could be used for multiple bitrate streams ingestion, if only one bitrate is streamed the index should be 1. --- **Integration points** * Connection – **liveStream.authenticate** action is called to validate the entry id with the supplied token. The action should return a KalturaLiveStreamEntry object, or an exception in case the authentication failed. The returned entry object could be used later to determine if DVR and recording are enabled for this entry. * Publish – **liveStream.registerMediaServer** action is called to inform the server that this entry is live. This API call is repeated every 60 seconds, otherwise a server-side batch process will remove the flag and mark the entry as non-live. * Transcoding - **wowza_liveStreamConversionProfile.serve** is called for each published entry. This action returns an XML formatted according to the Wowza required structure, indicating the transcoding that the stream should undergo. * Unpublish – **liveStream.unregisterMediaServer** action is called to inform the server that this entry is not live anymore. * Recorded segment end – **liveStream.appendRecording** action is called to ingest the recorded media file. * Server status report- the SaaS Wowza servers are logged as entries into the DB, and periodically report their status using the mediaServer.reportStatus action. ---- **Configuration** * DVR – set KalturaLiveStreamEntry::dvrStatus to determine if DVR should be enabled for the live stream, and use KalturaLiveStreamEntry::dvrWindow to get/set the configured DVR duration in minutes. * Recording – set KallturaLiveStreamEntry::recordStatus to determine if VOD recording should be enabled. * Transcoding – set KalturaLiveStreamEntry::conversionProfileId. The required flavors are fetched using conversionProfileAssetParams.list and flavorParams.getByConversionProfileId actions. -- Media Server Installation -- Instructions to install a Wowza SaaS server can be found here: https://github.com/kaltura/media-server/blob/3.0.8/Installation.md