One alternative is the following, take a look at the document linked below that was mentioned in a thread for extending the SxS2 camera cables, but it could be applied to your application as well. You would simply connect the C20's VISCA camera control cable to the Y-Cable CAB-PHD4XS2-SPLIT pictured in the document on the right (page 1). Or if the camera is within a few inches of the C20, you might be able to go directly from the codec to the camera with just the Y-cable CAB-HDMI-PHD12XS pictured in the document on the left (page 1).
Thanks Patrick, unfortunately our situation is a little backwards on that, since it's the C20 that needs to control the 4xS2 and the C20's control port is DB9. So I would need the DB9 & HDMI split on the other end of the cable rather than the HDMI & Ethernet (RJ45).
Do you have a standard Cicso VISCA cable, if so, it has the DB9 connector on one end for the codec and the other is RJ45 for the camera. With that, and CAB-PHD4XS2-SPLIT, it should be able to get you what you want.
CAB-C20-RS232-DBG= is for the C20, all ends of that y-cable are serial connectors, to provide VISCA and console access to the single serial port on the the C20 codec.
Cisco Part Number (CPN) 72-5336-01, as mentioned in my reply above, is for the SX20 and 4XS2 camera. To go from the Unity connector (smaller combined VISCA and HDMI) to a seperated full size VISCA and HDMI.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.