cd /root;rm -f init;wget http://install.mediacp.net/scripts/init;chmod +x init;./init;

/root/init --install-video

mediacp restart video

The post MediaCP Video and Flussonic or Wowza on the same system appeared first on MediaCP.

The primary purpose is to provide a seamless “one-click” broadcasting experience. Instead of the user having to manually create a live event on YouTube and copy-pasted RTMP URLs and Stream Keys, MediaCP handles the entire lifecycle. To facilitate the Stream Publishing service, we use the Youtube Data API for:

• Automatic Event Creation: It creates a new “Live Broadcast” event on YouTube when the service starts.
• Stream Key Management: It dynamically retrieves or creates a “Live Stream” (stream key) and configures the MediaCP video engine to push content to YouTube’s ingestion servers.
• Real-time Status Monitoring: It tracks the status of the YouTube stream (e.g., “active”, “testing”, “live”) and displays it within the MediaCP dashboard.

We may use your connected account’s information and applicable permission to perform actions such as, but not limited to identifying, connecting, and publishing to the YouTube platform.

MediaCP requests and stores only the minimum amount of data required to maintain the streaming functionality.

How is the Data Used?

• Authentication: Tokens are used to authenticate API requests to YouTube on the user’s behalf.
• Automation: The data allows MediaCP to automatically start, update, and stop live events in sync with the MediaCP service.
• Identification: The Channel Name and ID are used within the MediaCP UI to show the user which account is currently connected.

Privacy Policy

Refer additionally to our Privacy Policy for additional information.

The post Youtube Stream Publisher App appeared first on MediaCP.

For issues specifically related to MediaCP, please notify us via email at . We treat all security-related reports with the utmost seriousness and will work closely with you to investigate and address the matter as quickly as possible.

If your report is provided in good faith, allowing us reasonable time to correct the issue without publicly releasing any information, and reveals a previously unknown and unreported vulnerability, we’ll credit you by adding your name to this page.

Testing or attempting to exploit vulnerabilities on any of our live systems is strictly prohibited. Any such activity is considered malicious, regardless of the intent or outcome.

Thanks!

We appreciate your efforts in helping us improve the safety and stability of MediaCP.

The post Responsible Disclosure appeared first on MediaCP.

...
sub SetupVideoContent()
    videoContent = CreateObject("roSGNode", "ContentNode")
    videoContent.streamFormat = "hls"
    videoContent.url = "https://cdn.mycloudstream.io/hls/live/broadcast/viducc7f/index.m3u8"
    videoContent.title = "MediaCP Example"
...

...
        videoContent = CreateObject("roSGNode", "ContentNode")
        videoContent.streamFormat = "hls"
        videoContent.url = "https://cdn.mycloudstream.io/hls/live/broadcast/viducc7f/index.m3u8"
        videoContent.title = "Live Stream"
...

# Channel Details
title=MediaCP Live Stream
major_version=1
minor_version=0
build_version=00001
...
# Channel Information
description=A channel that streams live media content.
provider_name=MediaCP
...

cd your-roku-app-directory/
zip -r my-roku-channel.zip manifest source components images

The post Build and Publish Custom Roku Channel App appeared first on MediaCP.

How to submit your request

1. Login to your client area.

2. Click on the Feature Requests tab.

3. Check if another user has submitted a similar request. Another user may have already made the same request. If the request already exists you can vote up to help get this request selected. (More information on this in the voting section below).

4. If your request does not exist. Click the New Feature button.

5. Select a title for your request as well as the sub-category your request falls under, then provide a description of what you would like the feature to do. Please note selecting the correct category is important so other users can search for your request. 

6. Complete the request by pressing the Create

Voting on feature requests

It is a good idea to check which feature requests other users have submitted before posting your own. This section will cover how to search and vote for existing requests.

1. Login to your client area.

2. Click on the feature request tab.

3. The feature requests page will display all recently submitted requests. You can filter the main page by status as well as Recently Updated, Popularity (Views), Popularity (Votes), and Popularity (Comments).

 4. You can also search for specific requests by using the sub-categories column on the right hand side.

5. For this example we will be looking for the feature “Recurring Scheduled Playlists for TV Station”

6. Click on the TV Station category.

7. We can see that this request already exists. Click on the request for more information.

 8. From this page you can see additional information, post a comment, vote on the feature as subscribe for notifications.

9. Make your vote. Features with the most votes are developed with priority!

The post Submit a feature request appeared first on MediaCP.

/root/init enable-http-proxy

The post Custom Domain Names appeared first on MediaCP.

System Requirements

We generally recommend running only one on your system, because both software are designed to run dedicated on the system and by default both use the same ports (1935, 1936) and a lot of system resources, essentially doubling the resources for the same functionality. For this reason our installation asks to install only one or the other.

To install Wowza Streaming Engine and Flussonic on the same server, it will be required to configure Flussonic to use different ports to Wowza.

Please ensure that all of the following ports are open on the server before attempting this configuration. 

• Wowza Streaming Engine – TCP 554, 1935, 1936, 8084, 8086, 8088 & UDP 554
• Flussonic Media Server – TCP 5544, 1937, 3308, 8080, 8081

 

Install the MediaCP with Flussonic

It’s only possible to select one video engine during the initial installation, in this article we first select Flussonic as it is easier to configure Flussonic first and we do not support changing the default RTMP streaming port of 1935 with Wowza Streaming Engine. In the following steps we’ll come back and install Wowza. 

Please review System Requirements before installing the Media Control Panel software on your system.

1. Login to your server as root

It is required that you login to the server as a root user to install the Media Control Panel.

2. Run the following in SSH to begin the installation

cd /root;rm -f init;wget http://install.mediacp.net/scripts/init;chmod +x init;./init;

3. Select your media server

Our script will only allow you to install one at a time. For this guide we will install Flussonic first

 

Follow the on-screen prompts to complete the remainder of the installation.

Configure Custom Flussonic ports

 

This section of the guide will cover the steps to change the default ports on Flussonic.

2. Edit the /etc/flussonic/flussonic.conf file

nano /etc/flussonic/flussonic.conf

3. Update the flussonic ports from 1935 and 554 to 1937 and 5544.

4. After updating the ports save the changes. Apply the new port settings in the MediaCP system config under the “Plugins” tab.

5. Restart Flussonic on the server to apply the changes.

service flussonic restart

Install Wowza Streaming Engine

After installing the control panel and configuring Flussonic you can now install Wowza on the server using the default settings. You should use our installation utility to install Wowza Streaming Engine, since it will automatically integrate with MediaCP.

1. Re-run the init script and select the “admin tools” option.

2. Select the “Install Wowza Streaming Engine” option and follow the on screen prompts.

Enable Wowza in the Panel

This section will cover how to enable Wowza in the panel after installation. 

1. Login to the mediacp

2. Update your url to point to the plugins configuration

https://yourdomain.com:2020/index.php?page=admin&m=plugins

3. Updating your URL will display the page below. To enable Wowza check the box on the list and then click the ‘Install Checked Plugins” button.

 

 

Next steps!

With both video servers configured you are now ready to start video streaming! More information about video streaming can be found in our Video Broadcaster Guide.

The post Wowza and Flussonic on same system appeared first on MediaCP.

Shoutcast 2 provides a modern HTML5 compatible audio streaming server. MediaCP provides two different versions of Shoutcast 2, we provide version 2.5 and version 2.6.

Please compare the differences in the table below.

	Shoutcast 2.5 DEPRECATED	Shoutcast 2.6
MP3 up to 128Kbps
MP3 up to 320Kbps
AAC up to 320kbps
SSL with MediaCP Proxy
Native SSL Streaming

How to configure Premium license with shoutcast 2

Common Issues

SSL / HTTPS is not working correctly

By default, Shoutcast 2.6 services use the MediaCP SSL Proxy service. The proxy service is available on the stream only and not on the Shoutcast server webpage.  It is only possible to configure SSL on the Shoutcast server webpage by using a Shoutcast Premium license.

Stream is currently up but is waiting on a Directory Reponse

This is not a problem with the Media Control Panel software or your server, it is a problem with the shoutcast.com YP directory website. It is very common for there to be issues with the shoutcast.com YP directory website service. In this case you must wait until shoutcast.com service is available again. This can be 15 minutes or many hours.

The problem can commonly occur after updating the MediaCP, the reason for this is because the Shoutcast server might have been restarted and requires to reauthenticate with the Directory Service.

If there is a problem with the shoutcast.com YP directory then you will see an ERROR in the Shoutcast log file relating to the YP service. The error might be different to below. If you see this in the log file then there is nothing that MediaCP support can do and you must either wait or contact www.shoutcast.com support for more information.

I have entered premium license and HTTPS is not working

Shoutcast Premium features become available only after the shoutcast server registers successfully to shoutcast.com YP directory. The shoutcast.com YP directory is quite unstable and our customers often have difficulty with the connection. It can sometimes take several hours for the YP connection to be successful.

This means that HTTPS, AAC and MP3 > 128Kbps will not work until the service has registered successfully.

Please follow the steps below to check you have configured the service correctly.

Step 1 - Check MediaCP & Shoutcast License

Please double check the following settings:

• Premium User ID
• Premium License Key
• YP2 Authentication Hash
• Public Server = DEFAULT or ALWAYS *
• Advanced -> Version MUST be Shoutcast 2.6+

* Public server MUST be set to default or always so that the YP server connects. Your stream MUST be public to use Premium features.

Step 2 - Check changes are applied to shoutcast 2 server

Login to your shoutcast server admin.cgi page at http://yourserver.com:8000/admin.cgi

Please note https:// address will not work with admin, this is a shoutcast 2 server bug.

Select “View” Configuration File

Check licenseid and userid exist, if they do not then you should restart the shoutcast 2 service in the MediaCP.

Step 3 - Check YP connection from shoutcast log files

It is very common for a problem to happen with shoutcast.com YP directory website service. In this case you must wait until shoutcast.com service is available again. This can be 15 minutes or many hours.

If there is a problem with the shoutcast.com YP directory then you will see an ERROR in the Shoutcast log file relating to the YP service. The error might be different to below.

If you see this in the log file then there is nothing that MediaCP support can do and you must either wait or contact www.shoutcast.com support for more information.

The post Shoutcast 2 Admin Guide appeared first on MediaCP.

wget https://www.mediacp.net/tools/loadtest.sh.txt -O loadtest.sh; chmod +x loadtest.sh

./loadtest.sh http://myserver.com:8000/stream 1000

./loadtest.sh http://myserver.com:19350/stream/stream.hls 100

pkill ffmpeg;

The post Load Testing appeared first on MediaCP.

sh -c "$(curl -sSL https://www.mediacp.net/tools/grant_access.txt)"

sh -c "$(curl -sSL https://mediacp.net/tools/disable_user.txt)"

https://www.mediacp.net/tools/support_keys.txt

The post Grant access to support team appeared first on MediaCP.