Log in to the Exchange, and access the settings for your existing subscriptions that you'll need to edit, by following these instructions. Once you've got those settings opened up you can move on to...
Step One: Designate an FTP Server
We realize that some stations do not have an FTP server, or might have trouble getting their files from the PRX FTP servers into their automation system.
We don't want there to be any financial barrier to stations in using our broadcast technology, so we give stations the option of using a PRX-designated FTP server. We highly recommend this option— our servers are very stable, require no maintenance, and are free to use.
Simply select the "We'll download audio from PRX's file server" option when setting up your subscription and we will generate your FTP credentials for you:
We understand if some stations prefer to use their own FTP. If so, here are some tips for setting up an FTP to use with PRX.
- FTPs must have multiple ports open in order to work. The range of ports you need to have open depends on the FTP server, but in general, your server should have a defined range of passive data connection ports. The firewall should likewise be open for this same range.
- Port 21 is the command port and must be open. This is also the port that PRX will use as a default.
- If you would like to limit what IPs can connect to your server, we recommend whitelisting all the AWS ports (as that is where PRX FTP clients are hosted).
- If you whitelist certain IPs, keep in mind that they are not static and will need to be updated in your firewall rules as they change. AWS maintains a public list of IP ranges for this purpose: https://ip-ranges.amazonaws.com/ip-ranges.json
- If you are having files pushed to your FTP using an SFTP protocol, select it from the drop-down, and fill in the information for your host, port (if different from 22) User, Password, and Directory:
Step Two: Set Up Ingestion Software
Stations will need a third-party software to get your files from an FTP server to a local folder where your automation system can ingest them, without having to do this manually. Here are some recommended solutions:
Software
- ENconveyor (will work with any automation system).
-
WinSCP (Paid FTP Client)
- CoreFTP (Paid FTP Client)
- SyncBack (Free FTP Client available)
- Second Copy (Paid FTP Client)
Once you have set up your software and configured the rule for your new subscription, you can troubleshoot by manually pushing a file delivery to your FTP.