- Custom Domain Names – Provides the ability to configure a custom domain name on a per-service basis that differs from the configured Host Address. Custom Domain names are available currently for Audio Services including SHOUTcast and Icecast and are not available for video streaming services. Before Custom Domain Names can be enabled you must first configure the Port 80/443 Proxy which ensures an SSL certificate can be automatically created.
- Portbase Range Start – One or more ports are assigned to each new media service that is created, depending on what media service type is created. The MediaCP will automatically select the next port to assign based on this value.
- Automatic SHOUTcast 2 HTTPS – Automatically enable HTTPS Proxy for all SHOUTcast 2 services by default.
- Preferred Connection – Determines the connection that the HTMl5 player uses to your streaming service. Proxy connection provides better firewall accessibility, however direct connection provides slightly improved performance.
- Display Port on Service List – Show or Hide portbase on service listing page (Audio Services Only).
- Services Listing Order – The default order will list services by their status (online, offline), then number of connections and finally the name of the service.
- Suspended Services – Configure how suspended services are displayed within the panel.
Station Public Page
- Station Publish Pages – Audio Services include their own publish Station Page, otherwise known as a Start Page. This option controls whether Station Pages can be used within this MediaCP installation.
- New Service Default – Defines if new services should include a Station Page.
- Widgets – Controls whether Widgets can be used in the MediaCP. All Media Services include a Widgets page which includes different components that can be embedded onto external websites. These includes widgets such as Audio & Video Players, Now Playing, Recently Played and more.
- Automatic Suspension – Defines if a media service should be suspended after reaching its disk quota allocation, and at what percentage it will be suspended. The default is to suspend the service at 100%.
Some streaming service engines are incapable of limiting the bitrate to an individual stream effectively. The MediaCP includes a mechanism to check the bitrate that a media service is broadcasting at, and apply an action if it is above the limit imposed on the service.
A log file of bitrate abuse detections and actions taken exists in /usr/local/mediacp/log/mediacp/abuse.log
- Abuse Action – By default, the action when a user streams above the bitrate will attempt disconnection of the broadcasting source or encoder. The Stop action will switch the entire service offline, requiring the Customer or an Administrator to start the service again before it can be streamed too.
- Abuse Email – Defines whether to send an email notifying of the overage and/or suspension when a service exceeds its defined bitrate limit.
- Bitrate Overage % – Provides a grace percentage of overage on the bitrate limit before the abuse action is triggered. For example a limit of 256Kbps with a 10% overage will not trigger the Abuse Action until the broadcast streams at 281Kbps. Some streaming services, especially related to video streaming use a Variable Bitrate (VBR) and when set to 256Kbps may exceed this value occasionally. For this reason it is recommended to include at least a 10% buffer.
- Suspend service after – It is possible to temporarily suspend a service if it is consistently exceeding the bitrate. This ensures that a user cannot restart the service and begin streaming again for a short period of time. Default is set to “Do not suspend”.
- Suspend service for – Define the duration to temporarily suspend a service for.
- Action on traffic limit reached – Defines if a media service should be suspended after reaching its allocated amount of bandwidth usage. The default is to suspend the service at 100% until the end of the current month.