For users of Media Room to gain access to Media Room's Aspera on Cloud, users will have to download Aspera Connect which is Aspera's desktop plugin. See Aspera Connect Installation.


The Aspera Connect application used with Aspera on Cloud requires specific ports for file transfers. If your local system is behind a firewall that does not allow inbound/outbound connections, you need to do the following:


Aspera transfers use one TCP port for session initialisation and control and one UDP port for data transfer. 

The TCP port is usually either 22 (default port for SSH) or 33001 and the UDP port is by default 33001


Typical: Consumer and business firewalls allow direct outbound connections from client computers on TCP and UDP. There is no configuration required for Aspera transfers in this case.

Special: In the case of corporate firewalls disallowing direct outbound connections typically using proxy servers for web browsing:

  • Allow outbound connections from the Aspera client on the TCP port.
  • Allow outbound connections from the Aspera client on the UDP port.


See below for a list of up to date public IP addresses that needs to be unblocked:


"13.55.179.142/32",

"54.153.233.24/32",

"52.65.160.223/32",

"13.210.124.202/32",

"54.153.195.226/32",

"13.210.147.115/32",

"52.65.131.30/32",

"52.63.144.180/32",

"52.64.252.68/32",

"52.63.203.123/32",

"13.210.117.153/32",

"13.55.30.30/32",

"13.55.132.19/32",

"54.206.43.20/32",

"13.55.216.56/32",

"52.62.40.201/32"


For technical documentation on how to unblock IP addresses, please see below link:

https://sup.ibmaspera.com/help/admin/basic-2/system_requirements_and_browser_support#toc-item-6

Note: There is an "In this topic" panel on the right hand side, and the user needs to find the section 
'Allowing Traffic to Transfer Service Nodes'
which displays as
'Allowing Traffic to Transfer Servic...'