Sony CNA-2 Parameter Controllable Device 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 CNA-2 Node uses two connections. hi signs in to the CNA-2 Web API over HTTPS, and CNA-2 posts Tally and assignment changes to a webhook listener on hi. Both connections must work for the Node to show the current state.
|
Configuration |
What hi Sees |
Use When |
|---|---|---|
|
CNA-2 Web API and Webhook |
Tally, Microphone gain, CCU Assignment, and RCP Assignment Parameters under the Node in Inventory. |
hi must read camera Tally, or read and set microphone gain and CCU or RCP assignments, through a CNA-2. |
Caution
The CNA-2 sign-in API accepts HTTPS only, and hi always connects on Port 443. The hi webhook listener accepts plaintext HTTP only, so the CNA-2 webhook protocol must be HTTP.
Before You Begin
-
The hi server address that CNA-2 posts to must be an IP address. CNA-2 does not accept webhook URLs with a host name.
-
Use Node admin and open Inventory > Nodes. See Manage Nodes.
-
Confirm the license and minimum hi version in Required Configuration.
-
Get access to the CNA-2 Settings menu and a CNA-2 account with Admin or Senior Operator authority.
-
Use the root account created at the first Web UI sign-in, or add an account under Settings > User Account > Add New User. Only accounts with Admin or Senior Operator authority can use the Web API.
-
Sony requires the optional software HZC-GWCN2 for some SSCP functions, such as MSU emulation mode, multi-camera control, and CCU format control. hi uses the Web API and not SSCP.
-
When the CNA-2 is part of a federation, Settings > Federation > Access Token > WebAPI Enable must be
On. -
Confirm the network access in Network Requirements. hi needs outbound TCP
443to the CNA-2, and the CNA-2 needs to reach the hi server on the webhook Port,31000by default.
Configure CNA-2 Web API and Webhook
Use this configuration for every CNA-2 Node.
Device Configuration
-
Connect the CNA-2 to a management network that the hi server can reach. Enable the CNA-2 network interface and record its IP address.
-
Set Settings > System > System Mode to
Management, and then set Settings > System > Management Mode toWeb API. -
Set Settings > System > CNS Mode to
MCS. hi addresses Web API domain0, which Sony assigns to MCS. -
Set Settings > System > MCS Settings > Master Mode to
On. -
Set Settings > Maintenance > Web API > Protocol to
Https. -
Optionally install a server certificate under Settings > Maintenance > Certification Install > CNA-2 Web CertFile. hi 3.0.0 does not validate it, so place the CNA-2 on a trusted management network.
-
Create the account that hi uses under Settings > User Account > Add New User, with Admin or Senior Operator authority. You can also use the root account.
-
Set Settings > Maintenance > Webhook > Protocol to
Http. CNA-2 has two LAN ports. It sends webhook packets from the LAN port in the same subnet as the registered URL, and from LAN1 when the URL is in a different subnet. Place the hi server so that this path is reachable. -
If the CNA-2 is a federation child, set Settings > Federation > Access Token > WebAPI Enable to
On. -
If 10 webhook server URLs are already registered under Settings > Maintenance > Webhook > Server, remove a stale entry. CNA-2 stores up to 10 URLs.
hi Configuration
-
Add the Sony CNA-2 Parameter Controllable Device in Inventory.
-
Enter the CNA-2 address in Host / IP Address. hi connects over HTTPS on Port
443; the Port is not configurable. -
Enter the CNA-2 account in Username and Password.
-
Leave Root SSL certificate empty and Accept Untrusted SSL Root Certificate at
No. hi 3.0.0 does not validate the CNA-2 certificate, so these settings have no effect. -
Set Webhook port to a free Port from
31000to31999. The default is31000. -
Create the Node. When it connects, hi signs in, removes its previous webhook entry, and registers
http://<hi server address>:<Webhook port>/webhookunder a name that starts withhi-.
All settings in this procedure remain editable after the Node is created.
Settings Summary
|
Setting |
Device Side |
hi Side |
|---|---|---|
|
API protocol |
Settings > Maintenance > Web API > Protocol
|
HTTPS on Port |
|
Account |
Settings > User Account
|
Username and Password |
|
Certificate |
Settings > Maintenance > Certification Install > CNA-2 Web CertFile (optional) |
Not validated in hi 3.0.0 |
|
Webhook protocol |
Settings > Maintenance > Webhook > Protocol
|
HTTP listener on Webhook port
|
|
Domain |
Settings > System > CNS Mode
|
Web API domain |
Common Checks
|
Symptom |
Check |
|---|---|
|
The Node does not connect. |
Confirm that the account can sign in and has Admin or Senior Operator authority, that the Web API protocol is |
|
Microphone gain updates, but Tally and assignment changes do not. |
Confirm that the CNA-2 can reach the hi server on Webhook port, that the webhook protocol is |
|
Webhook registration fails. |
Confirm that fewer than 10 webhook server URLs are registered on the CNA-2. |
|
Requests fail after the Node has been connected for some time. |
Check Settings > Maintenance > Auto Sign out Time on the CNA-2. The sign-in token expires after this period. |
|
A camera, CCU, or Panel number shows no value. |
hi lists numbers 1 to 96 whether or not they exist. Confirm that the number exists in the CNA-2 system in CNS Mode MCS. |
Verify the Configuration
Open the Node in Inventory. Confirm that Mic Gain 1 of a connected camera shows a value within 5 seconds. Then change the RCP assignment of a Panel that is not in use, and confirm that RCP Assignment > Panel n updates in hi without a refresh. This confirms webhook delivery.