hi human interface®
hi human interface®
English
Breadcrumbs

Imagine Communications Selenio Network Processor (SNP) Integration Configuration

Imagine Communications Selenio Network Processor (SNP) Integration Configuration

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.

Configuration Overview

The SNP connects to hi as one Parameter Control Node over TCP or UDP. The SNP uses a different CCSP server Port for each transport, so the transport and the Port in hi must match.

Configuration

What hi Sees

Use When

CCS-P over TCP

The SNP parameter tree. hi sends keep-alives to the SNP.

Default. Use it unless the SNP must use UDP.

CCS-P over UDP

The SNP parameter tree. hi expects keep-alives from the SNP.

The SNP must use UDP.

Caution

hi does not change the Port when you change Network Transport. When you select UDP, enter the UDP Port of the SNP, because the pre-filled 4517 is the TCP Port.

Before You Begin

Configure CCS-P Over TCP

Use this configuration for a standard SNP connection.

Device Configuration

  1. In the SNP Manager, open Configure Element for the SNP, select the System tab, and in the Security section clear Disable CCSP Port. The SNP then serves CCS-P on TCP Port 4517.

  2. In the SNP Manager console view, open the CCSP Interface Documentation section and confirm the parameters that the SNP publishes.

hi Configuration

  1. Add the SNP integration, manufacturer Imagine Communications, in Inventory.

  2. Enter the SNP address. Keep the Port at 4517.

  3. In the Connection Settings group, keep Network Transport at TCP.

  4. Create the Node. hi loads the top four levels of the CCS-P tree.

  5. In the Parameter Browser, open the branches that you need, select the parameters that hi must monitor, and select Pin Selected.

Configure CCS-P Over UDP

Use this configuration only when the SNP must use UDP.

Device Configuration

  1. In the SNP Manager, open Configure Element for the SNP, select the System tab, and in the Security section clear Disable CCSP Port. The SNP then serves CCS-P on UDP Port 4050.

  2. In the SNP Manager console view, open the CCSP Interface Documentation section and confirm the parameters that the SNP publishes.

hi Configuration

  1. Add the SNP integration, manufacturer Imagine Communications, in Inventory.

  2. Enter the SNP address and replace the Port with 4050.

  3. In the Connection Settings group, set Network Transport to UDP.

  4. Allow inbound UDP from the SNP to Port 4000 on the hi server.

  5. Create the Node. hi loads the top four levels of the CCS-P tree.

  6. In the Parameter Browser, open the branches that you need, select the parameters that hi must monitor, and select Pin Selected.

Settings Summary

Setting

Device Side

hi Side

Transport

TCP or UDP CCSP server

Network Transport
default TCP

Port

TCP 4517 or UDP 4050

Port
pre-filled 4517

UDP replies

Messages to the hi server

Local UDP Port 4000 on the hi server

Common Checks

Symptom

Check

The Node does not connect over UDP.

Confirm that the Port is 4050 and not the TCP Port 4517.

The Node over UDP shows as disconnected after about 50 seconds.

hi received no keep-alive from the SNP. Confirm that UDP Port 4000 on the hi server is reachable from the SNP.

AudioFlex controls are missing.

Confirm in the CCSP Interface Documentation section that the SNP publishes them. They depend on the SNP configuration and licensed options.

Verify the Configuration

Confirm that the Node reports a connected state and that the Parameter Browser shows the SNP tree. Pin a known parameter, change it in the SNP Manager, and confirm that hi shows the new value. Then change a safe parameter from hi and confirm that the SNP Manager shows the same value.