If at any point an encoder stops pushing your live stream, then the viewing experience for the clients currently connected to the live stream may be affected. In such a case, you may not be allowed to restart your encoder until the publishing point has been shut down. The proper procedure for shutting down a publishing point depends on whether the encoded feed is being ingested by your own IIS server or directly by our CDN. The stream will be restarted once the encoder resumes pushing data to the ingest point.
Key information:
- Shutting down a publishing point will disconnect all client connections to your live stream.
- It is important to perform a recursive purge on the publishing point location prior to reusing it. If this location is not purged, then audio/video fragments from the previous event may be served to your customers. Keep in mind that purging will discard the video and audio assets stored for the purposes of DVR playback.
- This step is automatically performed when shutting down a publishing point from within the MCC.
- Learn how to purge publishing point content.
- It may take up to two minutes for a request to shut down a publishing point to take effect. You can estimate when the shutdown process has been finalized by adding 2 minutes to the time reported by the Last Shut Down Request option for that publishing point.
- Prevent clients from being disconnected from a stream when an ingest point experiences a point of failure by creating multiple ingest points for a single stream. This type of configuration is only recommended when using an encoder that supports pushing encoded video to multiple ingest points.
- Clients that were connected to a stream prior to the shutdown of a publishing point won’t be able to continue viewing a stream until the media player sends a new request to the edge server.
- Example: Refreshing a web page will cause an embedded video player to send a new request.
Shutting Down a Publishing Point (CDN Ingest Point)
A publishing point can be shut down from the Live Smooth Streaming page. Once you have shut down the publishing point, the date and time on which the publishing point was last shutdown will be displayed. After shutting it down, use an encoder to restart encoding your live stream.
To restart an interrupted stream
- If your encoder is still encoding video, you should disconnect it from our publishing point. One way to ensure that it is disconnected from our publishing point is to close the encoder application.
- Navigate to the Live Smooth Streaming page.
- Under the Publishing Points section, click the pencil (
) that appears to the left of the desired publishing point. The settings associated with that publishing point will appear directly below the Publishing Points section. - Click the Shut Down link. A message will indicate whether it was successfully shutdown.
- Using the desired encoder, resume encoding your video feed to our publishing point.
Shutting Down a Publishing Point (IIS Ingest Point)
A publishing point can be shut down through Internet Information Services (IIS) Manager. The Actions pane of the Live Smooth Streaming Publishing Points page provides a Shut Down Publishing Point option. For detailed instructions on how to shut down your publishing point, please consult IIS documentation.
Reminder: After shutting down a publishing point, a recursive purge of the directory corresponding to the publishing point locationSample purge URL: http://wpc.0001.{Base Domain}/800001/Path/PublishingPoint.isml/* is highly recommended. This procedure prevents old content from being accidentally served to customers connecting to the new live stream.