Describe the bug
Crestron CP3N processor logs show `Stream write failed. Disconnected, closing' entries. Upon Cisco endpoint disconnection, end-user control becomes INOP. It appears that Crestron is no longer communicating with the endpoint even though the logs reflects 'connected' after the remote disconnecting.
Stacktrace
Include a stack trace of the exception if possible.
To Reproduce
Steps 'I believe' will reproduce the behavior:
Create PepperDash Essentials SSH connection to Cisco endpoint.
Connect to Cisco endpoint.
Reboot Cisco endpoint.
Review logs for stream write fails.
Expected behavior
I would expect a reboot, power cycle, or temporary loss of network connectivity to the Cisco endpoint automatically recover no matter what the specific scenario of communication loss is (power, network, or other).
Describe the bug Crestron CP3N processor logs show `Stream write failed. Disconnected, closing' entries. Upon Cisco endpoint disconnection, end-user control becomes INOP. It appears that Crestron is no longer communicating with the endpoint even though the logs reflects 'connected' after the remote disconnecting.
Stacktrace
Include a stack trace of the exception if possible.
To Reproduce Steps 'I believe' will reproduce the behavior:
Expected behavior I would expect a reboot, power cycle, or temporary loss of network connectivity to the Cisco endpoint automatically recover no matter what the specific scenario of communication loss is (power, network, or other).
Screenshots
Additional context
Cisco Endpoint Firmware: RoomOS 11.6.1.5 1058dcbc695