Has anyone had problem by controlling the far-end camera on icon 400, even though it is marked as controllable?
This feature should work even in a private network scenario like yours, as it's a pure negotiation between the 2 endpoints.
I could suggest doing a factory reset on both endpoints (please save the endpoints's configurations from the Icon WebUIs previously) just in case they are not on a stable state.
In case it doesn't work I'd suggest opening a case with our Support for a deeper troubleshoot.
What device is the Icon in a call with and are either one of them behind a firewall? Icons support the H.224/H.281 far end camera control standards and should be interoperable with other vendors. Far end camera control typically does not work when on a multiway call (MCU).
It is 2 Icon 400 systems, who are calling eachother on the same network with a VPN tunnel between them.
Is their any ports or other that you should be aware of?
The ports used for FECC (far-end camera control) on a point-to-point call through cloud are already included in the list of ports required for LS Cloud to work and are listed in the Cloud online help (link below):
Could you please confirm that the Far Control of Near Camera is enabled on the Icon WebUI on both endpoints?
Yes, the "far move to camera presets" are checked.
The systems are both Icon 400, and they are not connected to a cloud account, but just connected to their internally network.
I am in agreement with Gustavo. A cursory test here in support showed expected behavior between an Icon 600 and Icon 400; both standalone and on the same network.
Retrieving data ...