Yesterday we had a strange problem with a CTS-3000 unit dialling into a scheduled multipoint call.
Prior to the call, the unit wasn't registering any errors, but as soon a the call was started, we recieved alerts via our NMS system for
"Main Camera: Link Error" and the unit self-rebooted without connecting into the MP call.
Once the unit came back up, it registered the following errors:
"Main Camera: Device error"
"Audio Expansion Unit: System Error".
We performed a manual reboot of the CTS-3000 and everything came back up OK.
As we needed to get it working again quickly due to the meeting being for a very high profile client, we performed a hard reboot and it resolved the issue, but of course we were unable to capture the logs from the CTS-3000 unit due to the unit being rebooted.
We checked the system errors on the CTMS afterwards, and it showed a "Media timeout error" for the DN of the affected CTS-3000 unit.
We are running:
Any advice on why this occured/how ro prevent it happening again would be much appreciated.
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.