hi human interface®
hi human interface®
English
Breadcrumbs

Riedel MediorNet IP - FusioN / MuoN

Riedel MediorNet IP - FusioN / MuoN

Driver Maturity

Production

Recommended for normal production use.

Caution

Compatibility Note: This information is a general guide and may be incomplete, may not match a specific project implementation, and is subject to change as supported products and versions evolve. Confirm the exact implementation and requirements for each project with Riedel and the relevant equipment vendor, then validate the required functions end to end in the target environment before deployment.

Minimum hi Version: v2.7.7

Overview

Riedel® MediorNet® IP FusioN™ and MuoN™ devices expose NMOS media resources and a REST parameter surface. Available operations depend on the firmware and enabled options.

Network Requirements

  • Permit the NMOS discovery and API traffic required by the commissioned hi NMOS workflow.

  • When Parameter Control is enabled, allow outbound HTTP from hi to the device on Port 80 by default.

  • The FusioN REST surface does not use a callback to hi and does not provide TLS.

Standards Conformance

Standard

Conformance

Notes

AMWA NMOS

Implemented as an IP-transceiver capability

Exact protocol versions depend on the commissioned NMOS workflow

Riedel FusioN REST API

API v1 implemented

Parameter discovery
reads
and writes

Operator Workflow

  • UI Surface in hi: Inventory, Routing Matrix, Topology, and Parameter Control

  • Routing Semantics: NMOS resources participate in the commissioned NMOS workflow. Supported REST parameters appear under the device Node when Parameter Control is enabled.

  • Vendor Tooling: Continue to use the Riedel FusioN web interface for engineering, firmware, licenses, and parameters not exposed in hi.

Connection Methods

Connection: AMWA NMOS

Property

Value

Purpose

NMOS discovery and media-resource control

Endpoint

Services discovered by the commissioned NMOS workflow

Security

Validate authentication and transport policy for the deployed NMOS services

Required License

hiNMOS

Required Configuration

The FusioN or MuoN device must use the NMOS registry configured for hi. Its registry settings are available in Riedel MNSet and through the device REST API resource /emsfp/node/v1/self/diag/nmos. See Configure NMOS Routing.

Supported Features

Feature

Access

Exposed Operation and Scope

NMOS Resource Discovery

Read-only

Discover the NMOS resources exposed by the device through the commissioned NMOS workflow.

NMOS Connection Management

Read/write

Establish and change supported NMOS connections through the commissioned workflow.
Known Limitations

  • Validate the IS-04 and IS-05 versions of the commissioned NMOS workflow against the device.

Connection: Riedel FusioN REST API v1

Property

Value

Transport

HTTP

Default Port

80

Base Path

/emsfp/node/v1

Authentication

None configured by this integration

Encryption in Transit

Not supported by this HTTP surface

Connection Model

Request/response. hi checks reachability every 30 seconds and refreshes pinned Parameters every 5 seconds.

Required License

hiNMOS

Traffic Flow

Outbound from hi

Required Configuration

The device REST API must be reachable at /emsfp/node/v1 on HTTP Port 80, and the Node's Parameter Control capability must be enabled. See Configure NMOS Routing with Parameter Control.

Supported Features

Feature

Access

Exposed Operation and Scope

REST Parameter Tree

Read-only discovery

Discover folders and parameters exposed by API v1.

REST Parameter Values

Per-parameter access

Read all values. Write parameters that hi marks writable. Available controls include flow labels, names, enables, bit depth, sampling format, addresses, UDP ports, MAC, VLAN, audio format and packet time; device IP configuration and reboot; clean-switch type; SFP pinout; SDI color bars, loss-of-input mode and frame sync; NMOS registry and DNS settings; and flow-impairment syslog. The device must accept the requested value.

API Connectivity Status

Read-only

Monitor API reachability through periodic polling.
Known Limitations

  • The available parameter tree is determined by the connected device and its enabled capabilities.

Synchronize and Verify

See Verify the Configuration.

Required Configuration

Parameter

Description

Default

Parameter Control

Capability that enables the FusioN REST parameter surface on the Node

Off

Host / IP Address

Device address for the REST parameter surface

-

Port

HTTP port for the FusioN REST API

80

Manage Master Enable

Allow hi to manage the Node Master Enable state during NMOS routing
in the Settings group
set at runtime

Yes

Manage Primary RTP Enable

Allow hi to manage the primary RTP leg enable state during NMOS routing
in the Settings group
set at runtime

Yes

Manage Secondary RTP Enable

Allow hi to manage the secondary RTP leg enable state during NMOS routing
in the Settings group
set at runtime

Yes

The three Manage settings appear only while Automatic RTP and Master Enable Management is Yes on the NMOS Core Integration.

Device-Side Setup

Follow Riedel MediorNet IP - FusioN / MuoN Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Connection

Access

Exposed Operation and Scope

AMWA NMOS

Read-only discovery and read/write connection control

Discover and control the NMOS resources exposed by the device.

Riedel FusioN REST API v1

Per-parameter access

Discover and read exposed parameters; write parameters that hi marks writable; monitor API reachability.

Device Coverage

Tested With identifies devices that have been tested with hi. Device-specific configuration, firmware, and feature support can affect results.

Tested With

  • Riedel MediorNet FusioN

  • Riedel MediorNet MuoN

Known Limitations

  • Validate NMOS resources, REST parameters, licensed options, and required operations during commissioning.

  • Authentication and TLS behavior for NMOS services depends on the commissioned NMOS workflow.

  • The hi REST surface uses HTTP on Port 80 without authentication. Device or firmware variants that require HTTPS or authentication are not covered by that surface.

  • Confirm REST parameter availability on the commissioned MuoN device; available operations can differ from FusioN.

  • The Parameter Control capability is off by default. hi does not read REST parameters until it is turned on for the Node.

  • hi recognizes a FusioN or MuoN device in NMOS from the group hint tag and the Riedel interface MAC address that the device reports. A device that does not report both appears as a generic NMOS Node without the REST parameter surface.

What's Not Supported

  • Codec profile design and bitrate ladder authoring - configured in the device's own Riedel FusioN web interface.

  • Firmware updates and licensing activation - handled through the device's own Riedel FusioN web interface.

  • Stream forensics and packet-level diagnostics - outside the scope of this integration.

  • Writing SDP files to Senders or Receivers, and SDI embedded-audio channel mapping, through the REST API. hi presents these resources as read-only.

Trademarks

Note

Riedel, MediorNet, FusioN, and MuoN are trademarks of Riedel Communications GmbH & Co. KG.