hi human interface®
hi human interface®
English
Breadcrumbs

Nevion VideoIPath Core Integration

Nevion VideoIPath Core Integration

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.4

Caution

VideoIPath 2026.2.7 requires hi v3.0.0 or later.

Overview

The Nevion® VideoIPath™ Core Integration synchronizes devices, virtual devices, graph elements, junctions, profiles, endpoints, and current bookings with hi. Crosspoint changes create or cancel modern-service bookings.

Network Requirements

  • Connection Model: hi initiates API and subscription requests to the configured VideoIPath URL.

  • Multicast / Unicast: Unicast control traffic. Media transport remains under VideoIPath orchestration.

  • VLAN / IGMP: Configure through the VideoIPath network design.

  • Bandwidth: Control-plane traffic only.

  • IP Version: Determined by the configured VideoIPath URL and deployment.

  • Firewall: Permit outbound HTTP or HTTPS from hi to VideoIPath. Default web ports are 80 and 443.

Standards Conformance

Standard

Conformance

Notes

Nevion VideoIPath API

Implemented

API
configuration
status
session
subscription
and modern-service booking operations

Operator Workflow

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

  • Resources Controlled: Devices, virtual devices, graph elements, junctions, profiles, endpoints, and bookings

  • Routing Semantics: Connections are created as VideoIPath modern-service bookings. Disconnect cancels the matching booking.

  • Booking Behavior: hi creates each booking unlocked, starting immediately with no end time, using best-effort booking. When the destination already has a booking, the request also cancels the conflicting booking.

  • Name Workflow: The integration can follow supported VideoIPath name changes.

Connection Methods

Connection: Modern Services API

Connection Details

Property

Value

Protocol

Nevion VideoIPath modern-services API

Transport

HTTP or HTTPS

Default Port

From configured URL
normally 80 for HTTP or 443 for HTTPS

Authentication

API username and password using Basic authentication

Encryption in Transit

Available when the configured API URL uses HTTPS and the required certificate trust is configured

Connection Model

HTTP client

Required License

hiOrchestration

Traffic Flow

Outbound requests with inbound responses

Connection: UI Session API

Connection Details

Property

Value

Protocol

Nevion VideoIPath UI session API

Transport

HTTP or HTTPS

Default Port

From configured URL
normally 80 for HTTP or 443 for HTTPS

Authentication

UI username and password establish a session cookie

Encryption in Transit

Available when the configured API URL uses HTTPS and the required certificate trust is configured

Connection Model

HTTP client with a session cookie

Required License

hiOrchestration

Traffic Flow

Outbound sign-in requests with inbound responses

Connection: Session Subscriptions

Connection Details

Property

Value

Protocol

Nevion VideoIPath session subscriptions

Transport

HTTP or HTTPS

Default Port

From configured URL
normally 80 for HTTP or 443 for HTTPS

Authentication

VideoIPath UI session cookie

Encryption in Transit

Available when the configured API URL uses HTTPS and the required certificate trust is configured

Connection Model

Session-based configuration
endpoint-status
and booking subscriptions

Required License

hiOrchestration

Traffic Flow

Outbound subscription requests with inbound changes

Required Configuration

Parameter

Description

Default

API URL

Full HTTP(S) URL of the VideoIPath system

-

API Username

Service-account username for modern-service API operations

-

API Password

Password for the API service account

-

UI Username

Username used for VideoIPath configuration and status sessions

-

UI Password

Password for the VideoIPath UI session account

-

Root SSL certificate

Certificate information required by the commissioned HTTPS endpoint

-

Accept Untrusted SSL Root Certificate

Site-approved certificate handling for the VideoIPath endpoint

No

Follow name changes

Synchronize supported VideoIPath name changes into hi

No

Device-Side Setup

Follow Nevion VideoIPath Core Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Feature

Access

Exposed Operation and Scope

Device
Graph-element
Junction
and Profile Inventory

Read-only

Read the inventory and profiles exposed by VideoIPath.

Endpoint Status

Read-only updates

Read endpoint state and changes.

Booking Synchronization

Read-only updates

Read current modern-service bookings and changes.

Route Creation and Removal

Write-only actions

Create bookings from hi Crosspoint changes and cancel matching bookings on disconnect.

Device Coverage

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

Tested With

  • Nevion VideoIPath

Known Limitations

  • API and resource compatibility must be validated against the commissioned VideoIPath release.

  • VideoIPath session subscriptions expire when the session does not acknowledge received changes within the interval that VideoIPath defines, and VideoIPath limits the number of subscriptions for each session. Keep the UI account dedicated to hi.

  • Booking creation requires compatible endpoint or junction information and an applicable profile where VideoIPath requires one.

  • hi checks the VideoIPath server state every 60 seconds. When another VideoIPath server becomes active, hi restarts the integration after 30 seconds and synchronizes again.

What's Not Supported

  • Switch firmware updates or base network provisioning.

  • VideoIPath topology design, profile authoring, or global policy administration.

  • Reading VideoIPath alarms.

  • Acting as a VideoIPath driver through the VideoIPath External Driver API.

Trademarks

Note

Nevion and VideoIPath are trademarks of Nevion AS.

All product names, logos, and brands are property of their respective owners. Copyright in third-party software and materials remains with the respective owners. Use of these names does not imply endorsement.

RIEDEL Communications is not affiliated with, endorsed by, or officially partnered with Nevion unless explicitly stated.