Player URLs for on-demand publishing points

The URL format you should use when streaming from an on-demand publishing point depends on the content source. Use the following table to identify the player URL for your publishing point.

Content source	URL	Description
Any	mms://server_name/publishing_point_name, mms://server_name/publishing_point_name/, or mms://server_name/publishing_point_name/.*	Requests all content. If you are sourcing from a directory, this URL includes subdirectories.
Directory	mms://server_name/publishing_point_name/ *.content_file_name_extension	Requests all digital media files with a particular file name extension, such as .mp3 or .wma.
Directory	mms://server_name/publishing_point_name/ *.playlist_file_name_extension	Requests all playlist files with a particular extension, such as .wsx.
Directory	mms://server_name/publishing_point_name/ subdirectory/content_file_name or mms://server_name/publishing_point_name/ subdirectory/playlist_file_name	Requests a specific file, such as mms://server1/ publishing_point1/movie1.wmv.

Note Image Note

The asterisk (*) wildcard character can be used to replace the entire file name, for example *.wma, or to replace both the file name and extension, for example *.*. In the examples provided in the table, if an asterisk (*) is used as a wildcard character or if nothing is specified after the publishing point name, then you must enable the WMS Directory Playlist Parser plug-in and the Enable access to directory content using wildcards property (located on the Properties tab of the publishing point). If either of those is not enabled, then an error message is returned to the client.

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

Player URLs for on-demand publishing points

Related topics

Internal Server Error