As Cloud Servers can be billed hourly for the uptime in the online state, we have implemented three options of how the server should be stopped after the device gets disconnected:
- Auto;
- Manual;
- Scheduled.
The user can configure this option when the server is online or in the process of launching one.
NOTE: The stopped server CAN'T be configured to auto-stop or scheduled. To do so, the customer needs to start it.
Auto-stop is used when the customer wants to set up a specific time (up to 24 hours) to stop the engine after the device is disconnected from it.
Manual is for the case when the customer wants to stop it manually on his/her end.
NOTE: Online servers will incur a $3/hour (Transcoding Server), $2/hour (Cloud Hyperion and Helios servers), and $4/hour (Cloud Hyperion and Helios servers with network optimized feature enabled) payment charge. If the server won't be stopped, it will keep charging the account for the usage, even if the device WILL NOT stream or not be connected to it.
Scheduled option was made for the customer to choose the date and the time for the server to stop.
NOTE: whether customer has the source connected or not, the server will go offline at the date&time which was set
Comments
0 comments
Please sign in to leave a comment.