stop publishing live stream server side

[Gabriel_Troisgros]

still having issues with the rest api…im trying to stop publishing server side a live stream.

if i make a call like:

http://xxx.xxx.com:8087/v2/servers/_defaultServer_/vhosts/_defaultVHost_/applications/wcs/instances/1/incomingstreams/1-Gabdroid%5E5a375fdf9439c%5Eok%5Efr-3b7f

its fine i get all stream informations

if i issue this command:

http://xxx.xxx.com:8087/v2/servers/_defaultServer_/vhosts/_defaultVHost_/applications/wcs/instances/1/incomingstreams/1-Gabdroid%5E5a375fdf9439c%5Eok%5Efr-3b7f/actions/disconnectStream

i have a 404 error…help

[Michelle_B]

Hi,

The disconnectStream REST API method can only be used if the incomingstream object was initially connected through the MediaCaster system (using a stream file). If you are publishing the stream by pushing it from the encoder (similar to Wirecast and GoCoder), then this is not the appropriate method to disconnect the stream.

Michelle

[Pericas-Moya_Ruben]

Hey there,

Having a similar case; any hints about what the “appropriate method” would be ?

Btw, where can I find a list of all actions available? They don’t seem to be listed in the doc, or I missed them…

[Michelle_B]

If the stream is being pushed to the server (where the encoder initiated the connection), it’s best to stop it from the source encoder. You can have a module in place that rejects or shuts down the connection, but this will not prevent the encoder from re-sending the connection request repeatedly (similar to a DOS).

To shut down an on going RTMP publisher, you can call stream.getClient().setShutdownClient(true); for that stream object.

Michelle

[Pericas-Moya_Ruben]

Good to know, thank you