Stream Not Starting After Successful Response from rest-api/vod/startup

jainam

New Member
Hello Team,

I am facing an issue while trying to start a VOD stream using the REST API.

Steps to reproduce:

  1. I called rest-api/stream/find to check whether the stream was running. The API indicated that the stream was not found.
  2. Since the stream was not found, I called rest-api/vod/startup to start the stream.
  3. The rest-api/vod/startup API returned a 200 OK response.
  4. However, when I checked the stream status again, the stream had still not started.
Expected behavior:

After receiving a successful response from rest-api/vod/startup, the VOD stream should start and become available.

Actual behavior:

The API returns 200 OK, but the stream does not start and remains unavailable.

Could you please help me understand why this is happening? Does a 200 OK response from rest-api/vod/startup mean that the stream has started successfully, or does it only indicate that the startup request was accepted? Are there any additional parameters, configurations, or steps required to start the VOD stream successfully?

Thank you for your help.
 
Good day.
VOD streaming is an asynchronous operation, so 200 OK response to /rest-api/vod/startup means the request is accepted only. There is a new REST API v3 in WCS 5.3 branch returning 202 Accepted response in this case.
Please update to the latest WCS build 5.3.500 (or 5.2.2317 if you still using WCS 5.2 branch). If the problem still persists, check the file you're trying to play as VOD for supported codecs and format requirements. If the file seems to be good, reproduce the problem, collect the report and send the report archive using this link.
 
Top