Specifications for managedradio. playout node in private or corporate cloud

Description

deliver.media managedradio. is available as a fully managed private cloud service and ideal for larger networks that want to keep their playout infrastructure in-house or within their own cloud environment. The service is fully managed and monitored by the deliver.media team, combining the control of private infrastructure with the convenience of a managed service. 

Service Level Agreements (SLA) with a response time of less than 1 hour are available upon request, including 24/7 and 7-day coverage options. Please contact us for details and pricing.

Remote Access

deliver.media requires 24/7 remote access to the VM to operate, monitor, and maintain the managedradio. service. The customer is responsible for providing and securing the access method. The following options are supported:

• VPN – access via an existing customer VPN
• Jump host host – access via an existing jump or bastion server
• Other method – any other access method agreed upon with deliver.media (on request)

Access can be restricted to specific users or IP addresses provided by deliver.media.

User Accounts

The following user accounts must be available on the VM:

• Service user: a dedicated local user with access to all necessary directories and resources (e.g. svcdme or svcsmp)
• Admin user; a local user with administrator rights for maintenance and support (e.g. admindme or adminsmp)

Alternatively, a single local admin user covering both roles is also accepted.

System Requirements

The table below provides an overview of the minimum system requirements for running deliver.media managedradio. on a customer-provided VM. The Azure VM size Standard_F4s_v2 or equivalent is recommended as a reference.

* Local cache storage is used for audio file caching. Lower-performance storage (e.g. HDD or temporary volatile disk) is acceptable for this volume.

** A dedicated D: drive for audio file caching is recommended for larger music libraries. It enables preloading of audio files retrieved from the deliver.media cloud, improving playback reliability. Lower-cost, less responsive storage (e.g. standard HDD or cold storage tier) is sufficient for this purpose.

Firewall and Network Zone Settings

The following outbound connections must be permitted through the firewall for deliver.media managedradio. to operate correctly.

deliver.media services

MusicMaster (if applicable)

If deliver.media managedradio. is used together with MusicMaster Pro and CS, the following additional hosts must also be permitted:

If your VM does not fully meet these requirements, operation may still be possible. In this case, please contact our team at support@deliver.media before provisioning.