HTTP request soft trigger execution failing when executing from remote client
Answered
Hi All!
I have a soft trigger that I set up that allows me to activate and deactivate a cameras' privacy mask.
The soft trigger triggers an http request sent to a Hikvision camera using ISAPI commands.
I have the rule working successfully when executing it from a client that is directly installed on the server, but the soft trigger is failing when trying to execute it via a remote client.
The Server has 2 NICs. One is for the camera network only, and the other is for the company data network. All camera remote viewing is routed to the clients via the data network NIC. The camera network is isolated except for the server connection.
My first thought was that the reason for failure is because the remote client does not have access to the isolated camera network. I don't think that is the case though as I have other deployments where I'm utilizing soft triggers to activate ControlByWeb relays that are also configured in the same way where the CBW relay is in an isolated network, yet the soft trigger activates those relays successfully. This leads me to understand that the trigger is executed by the server and should therefore work.
Any help would be greatly appreciated!!!
-
Hi Tuli Dem,
Regarding:
My first thought was that the reason for failure is because the remote client does not have access to the isolated camera network.
That is my thought as well. I would run Wireshark in both situations, and check for the differences.
Most likely, you have to send the soft trigger to an external IP address, and adjust some setting in the firewall.
Also, you could route API Calls via Nx Cloud, although the rules will a bit different.- Soft trigger >>> Do HTTP Request (the cloud API call)
- Generic Event (to receive the cloud API call) >>> Do HTTP request (to change the state of the camera).
-
Hi Norman, Thanks for getting back to me and thanks for these recommendations.
I've tried the http request (same as I did yesterday) as well as the cloud api call that you recommended at a different site/system than the original site/system and there is does work successfully both internally and externally.
Back at the original site/system - both, the http request as well as the cloud api call work when initiating them from the local client, but both fail when initiating them from the outside.
These two lead me to believe that the issue is where something is being blocked. Both of the sites listed above are connected via the cloud.
Do you have a tool to test what might be blocked and/or what has to be allowed?
Thanks!
-
Hi Tuli Dem,
I'm sorry, I have been missing your reply.
Regarding:
Do you have a tool to test what might be blocked and/or what has to be allowed?
As said:
I would run Wireshark in both situations, and check for the differences.
Please sign in to leave a comment.
Comments
3 comments