Enable/Disable "Notify Surveillance Center" via ISAPI

You dont need wireshark for this

Developer tools any browser / Network tab, click the option you want on camera web interface(save optional) and check for url and body if its put or post
 
  • Like
Reactions: rug4096
123456 said:
I'm interested too, but I can't find the HTTP command:
Click to expand...

Howdy @123456 ...

I used Wireshark and Postman and came up with this on a DS-2CD2387G2-LU camera firmware version V5.7.19 build 241207... it successfully toggles "Notify Surveillance Center" on/off for "Intrusion Detection" Rule 1... IP Adress/Port is NVR virtual host PoE port 1 (192.168.154.5:65001)...

Toggle "Notify Surveillance Center" on:

Screenshot 2025-10-28 133133.png


Toggle "Notify Surveillance Center" off:

Screenshot 2025-10-28 132937.png


Here is the body code so you don't have to retype it...

Code: 
<?xml version="1.0" encoding="UTF-8"?>
<EventTrigger>
    <id>fielddetection-1</id>
    <eventType>fielddetection</eventType>
    <videoInputChannelID>1</videoInputChannelID>
    <EventTriggerNotificationList>
        <EventTriggerNotification>
            <id>center</id>
            <notificationMethod>center</notificationMethod>
        </EventTriggerNotification>
    </EventTriggerNotificationList>
</EventTrigger>

Code: 
<?xml version="1.0" encoding="UTF-8"?>
<EventTrigger>
    <id>fielddetection-1</id>
    <eventType>fielddetection</eventType>
    <videoInputChannelID>1</videoInputChannelID>
    <EventTriggerNotificationList/>
</EventTrigger>
 
  • Like
Reactions: JDreaming, alastairstevenson, 123456 and 1 other person
One thing to note...

All the "Linkage Method" items need to be set together, so the above "off" body code actually toggles off "Send Email", "Notify Surveillance Center", "Upload to FTP/Memory Card/NAS", "Supplement Light", and "Recording Linkage"... the "on" body code only turns "Notify Surveillance Center" back on.

So, let me know if you want me to adjust the code so that the other items (besides "Notify Surveillance Center") should be on or off, and I will adjust the code.

Screenshot 2025-10-28 144320.png
 
  • Like
Reactions: JDreaming, 123456 and alastairstevenson
Thanks for your help.
After your help, for camera setting I used the browser developer mode to select "Network" and then "Payload." I was able to see the code I needed to insert to enable and disable the various links.

Now the problem is if I activate "Notify Surveillance Center" from the NVR always via Postman PUT, the "Area settings" configuration of the camera is also overwritten, and I would like to keep it because the draw areas set by the camera have more points than those of the NVR

1761787131303.png
 
  • Like
Reactions: JDreaming and johnfitz
I imagine you will need to do an HTTP GET to get the "Area Setting" configuration... and then include that in the HTTP PUT...

What NVR model and firmware version do you have? I have DS-7616NI-M2/16P firmware V5.04.070 build 250828... it looks different than yours:


Screenshot 2025-10-30 172557.png
 
  • Like
Reactions: JDreaming
NVR Device Model DS-7608NXI-I2 / 8P/S
Firmware Version V4.62.225 build 240123
1761933381363.png

for enable enable Notify Surveillance Center send HTTP PUT ....
<?xml version
"1.0" encoding="UTF-8"?>
<EventTrigger>
<id>fielddetection-4
</id>
<eventType>fielddetection
</eventType>
<dynVideoInputChannelID>4
</dynVideoInputChannelID>
<EventTriggerNotificationList>
<EventTriggerNotification>
<id>record-4
</id>
<notificationMethod>record
</notificationMethod>
<dynVideoInputID>4
</dynVideoInputID>
</EventTriggerNotification>
<EventTriggerNotification>
<id>center
</id>
<notificationMethod>center
</notificationMethod>
</EventTriggerNotification>
</EventTriggerNotificationList>
</EventTrigger>

for disable Notify Surveillance Center HTTP PUT ....
<?xml version
"1.0" encoding="UTF-8"?>
<EventTrigger>
<id>fielddetection-4
</id>
<eventType>fielddetection
</eventType>
<dynVideoInputChannelID>4
</dynVideoInputChannelID>
<EventTriggerNotificationList>
<EventTriggerNotification>
<id>record-4
</id>
<notificationMethod>record
</notificationMethod>
<dynVideoInputID>4
</dynVideoInputID>
</EventTriggerNotification>
</EventTriggerNotificationList>
</EventTrigger>

To enable or disable the "Surveillance Center" notification, which HTTP PUT should I send without modifying other parts?
Sending the above strings strangely overwrites the "Area Settings" previously configured by the camera because the draw areas set by the camera have more points than those of the NVR.
 
123456 said:
To enable or disable the "Surveillance Center" notification, which HTTP PUT should I send without modifying other parts?
Click to expand...

This code turns everything on:

Code: 
<?xml version="1.0" encoding="UTF-8"?>
<EventTrigger>
    <id>FieldDetection-1</id>
    <eventType>FieldDetection</eventType>
    <dynVideoInputChannelID>1</dynVideoInputChannelID>
    <EventTriggerNotificationList>
        <EventTriggerNotification>
            <id>record-1</id>
            <notificationMethod>record</notificationMethod>
            <dynVideoInputID>1</dynVideoInputID>
        </EventTriggerNotification>
        <EventTriggerNotification>
            <id>email</id>
            <notificationMethod>email</notificationMethod>
        </EventTriggerNotification>
        <EventTriggerNotification>
            <id>monitorAlarm</id>
            <notificationMethod>monitorAlarm</notificationMethod>
        </EventTriggerNotification>
        <EventTriggerNotification>
            <id>beep</id>
            <notificationMethod>beep</notificationMethod>
        </EventTriggerNotification>
        <EventTriggerNotification>
            <id>center</id>
            <notificationMethod>center</notificationMethod>
        </EventTriggerNotification>
        <EventTriggerNotification>
            <id>audio</id>
            <notificationMethod>audio</notificationMethod>
        </EventTriggerNotification>
    </EventTriggerNotificationList>
</EventTrigger>

If an <EventTriggerNotification> block is omitted, then that option is turned off... for example, this code will only turn on "Notify Surveillance Center" and "Buzzer":

Code: 
<?xml version="1.0" encoding="UTF-8"?>
<EventTrigger>
    <id>FieldDetection-1</id>
    <eventType>FieldDetection</eventType>
    <dynVideoInputChannelID>1</dynVideoInputChannelID>
    <EventTriggerNotificationList>
        <EventTriggerNotification>
            <id>beep</id>
            <notificationMethod>beep</notificationMethod>
        </EventTriggerNotification>
        <EventTriggerNotification>
            <id>center</id>
            <notificationMethod>center</notificationMethod>
        </EventTriggerNotification>
    </EventTriggerNotificationList>
</EventTrigger>

Therefore, this code turns everything off:

Code: 
<?xml version="1.0" encoding="UTF-8"?>
<EventTrigger>
    <id>FieldDetection-1</id>
    <eventType>FieldDetection</eventType>
    <dynVideoInputChannelID>1</dynVideoInputChannelID>
    <EventTriggerNotificationList>
    </EventTriggerNotificationList>
</EventTrigger>
 
123456 said:
Sending the above strings strangely overwrites the "Area Settings" previously configured by the camera because the draw areas set by the camera have more points than those of the NVR.
Click to expand...

Are you sure that is happening? The "Area Settings" are on a different tab/page... are you also possibly using ISAPI to toggle "Enable"?

Screenshot 2025-10-31 184929.png


I see that toggling "Enable" on/off with ISAPI can cause the draw area to be reset... Here is what I see being sent in Wireshark when I toggle "Enable" on/off and hit "Save" (<enabled>true</enabled> for on, <enabled>false</enabled> for off):

Code: 
<?xml version="1.0" encoding="UTF-8"?>
<FieldDetection xmlns="http://www.isapi.org/ver20/XMLSchema" version="2.0">
    <id>1</id>
    <enabled>true</enabled>
    <normalizedScreenSize>
        <normalizedScreenWidth>1000</normalizedScreenWidth>
        <normalizedScreenHeight>1000</normalizedScreenHeight>
    </normalizedScreenSize>
    <FieldDetectionRegionList size="4">
        <FieldDetectionRegion>
            <id>1</id>
            <sensitivityLevel>50</sensitivityLevel>
            <timeThreshold>5</timeThreshold>
            <detectionTarget>all</detectionTarget>
            <alarmConfidence>mediumHigh</alarmConfidence>
            <RegionCoordinatesList xmlns="">
                <RegionCoordinates>
                    <positionX>263</positionX>
                    <positionY>868</positionY>
                </RegionCoordinates>
                <RegionCoordinates>
                    <positionX>508</positionX>
                    <positionY>865</positionY>
                </RegionCoordinates>
                <RegionCoordinates>
                    <positionX>633</positionX>
                    <positionY>813</positionY>
                </RegionCoordinates>
                <RegionCoordinates>
                    <positionX>792</positionX>
                    <positionY>675</positionY>
                </RegionCoordinates>
                <RegionCoordinates>
                    <positionX>888</positionX>
                    <positionY>513</positionY>
                </RegionCoordinates>
                <RegionCoordinates>
                    <positionX>904</positionX>
                    <positionY>312</positionY>
                </RegionCoordinates>
                <RegionCoordinates>
                    <positionX>820</positionX>
                    <positionY>186</positionY>
                </RegionCoordinates>
                <RegionCoordinates>
                    <positionX>625</positionX>
                    <positionY>202</positionY>
                </RegionCoordinates>
                <RegionCoordinates>
                    <positionX>477</positionX>
                    <positionY>296</positionY>
                </RegionCoordinates>
                <RegionCoordinates>
                    <positionX>395</positionX>
                    <positionY>434</positionY>
                </RegionCoordinates>
            </RegionCoordinatesList>
        </FieldDetectionRegion>
        <FieldDetectionRegion>
            <id>2</id>
            <sensitivityLevel>50</sensitivityLevel>
            <timeThreshold>0</timeThreshold>
            <detectionTarget>all</detectionTarget>
            <alarmConfidence>low</alarmConfidence>
            <RegionCoordinatesList xmlns=""/>
        </FieldDetectionRegion>
        <FieldDetectionRegion>
            <id>3</id>
            <sensitivityLevel>50</sensitivityLevel>
            <timeThreshold>0</timeThreshold>
            <detectionTarget>human,human</detectionTarget>
            <alarmConfidence>low</alarmConfidence>
            <RegionCoordinatesList xmlns=""/>
        </FieldDetectionRegion>
        <FieldDetectionRegion>
            <id>4</id>
            <sensitivityLevel>50</sensitivityLevel>
            <timeThreshold>0</timeThreshold>
            <detectionTarget>human,human</detectionTarget>
            <alarmConfidence>low</alarmConfidence>
            <RegionCoordinatesList xmlns=""/>
        </FieldDetectionRegion>
    </FieldDetectionRegionList>
</FieldDetection>


trempa92 said:
Sometimes body co tains multipart, you dont necesarilly need to send post put entire body, just part of it that you need
Click to expand...

I think in this case, the entire body needs to be sent, or the draw area is lost?


123456 said:
Sending the above strings strangely overwrites the "Area Settings" previously configured by the camera because the draw areas set by the camera have more points than those of the NVR.
Click to expand...

What model number/firmware version is the camera? I suspect it's a newer model camera... I think the NVR firmware has not "kept up" with full support for this newer camera...
 
johnfitz said:
Are you sure that is happening? The "Area Settings" are on a different tab/page... are you also possibly using ISAPI to toggle "Enable"?
Click to expand...
No, By changing "Linkage Method" on NVR, "Area Settings" is also overwritten, perhaps because even if it is part of a different tab, the page is saved only once.
1762160119438.png


johnfitz said:
What model number/firmware version is the camera? I suspect it's a newer model camera... I think the NVR firmware has not "kept up" with full support for this newer camera...
Click to expand...
Yes, the camera is newer than the NVR
Device Model DS-2CD2387G2H-LISU/SL
Firmware Version V5.7.17 build 240606
 
123456 said:
No, By changing "Linkage Method" on NVR, "Area Settings" is also overwritten, perhaps because even if it is part of a different tab, the page is saved only once.
Click to expand...

I don't see that happening on my NVR...

Screenshot 2025-11-03 152600.png


Here's what I see using Wireshark when I hit "Save" on the "Rule Configuration" tab (you can see the "FieldDetectionRegionList" being sent):

Code: 
<?xml version="1.0" encoding="UTF-8"?>
<FieldDetection xmlns="http://www.isapi.org/ver20/XMLSchema" version="2.0">
    <id>1</id>
    <enabled>true</enabled>
    <normalizedScreenSize>
        <normalizedScreenWidth>1000</normalizedScreenWidth>
        <normalizedScreenHeight>1000</normalizedScreenHeight>
    </normalizedScreenSize>
    <FieldDetectionRegionList size="4">
        <FieldDetectionRegion>
            <id>1</id>
            <sensitivityLevel>50</sensitivityLevel>
            <timeThreshold>0</timeThreshold>
            <detectionTarget>human</detectionTarget>
            <alarmConfidence>mediumHigh</alarmConfidence>
            <RegionCoordinatesList xmlns="">
                <RegionCoordinates>
                    <positionX>508</positionX>
                    <positionY>697</positionY>
                </RegionCoordinates>
                <RegionCoordinates>
                    <positionX>773</positionX>
                    <positionY>657</positionY>
                </RegionCoordinates>
                <RegionCoordinates>
                    <positionX>910</positionX>
                    <positionY>376</positionY>
                </RegionCoordinates>
                <RegionCoordinates>
                    <positionX>816</positionX>
                    <positionY>149</positionY>
                </RegionCoordinates>
                <RegionCoordinates>
                    <positionX>604</positionX>
                    <positionY>78</positionY>
                </RegionCoordinates>
                <RegionCoordinates>
                    <positionX>212</positionX>
                    <positionY>191</positionY>
                </RegionCoordinates>
                <RegionCoordinates>
                    <positionX>268</positionX>
                    <positionY>507</positionY>
                </RegionCoordinates>
                <RegionCoordinates>
                    <positionX>369</positionX>
                    <positionY>700</positionY>
                </RegionCoordinates>
            </RegionCoordinatesList>
        </FieldDetectionRegion>
        <FieldDetectionRegion>
            <id>2</id>
            <sensitivityLevel>50</sensitivityLevel>
            <timeThreshold>0</timeThreshold>
            <detectionTarget>all</detectionTarget>
            <alarmConfidence>low</alarmConfidence>
            <RegionCoordinatesList xmlns=""/>
        </FieldDetectionRegion>
        <FieldDetectionRegion>
            <id>3</id>
            <sensitivityLevel>50</sensitivityLevel>
            <timeThreshold>0</timeThreshold>
            <detectionTarget>human,human</detectionTarget>
            <alarmConfidence>low</alarmConfidence>
            <RegionCoordinatesList xmlns=""/>
        </FieldDetectionRegion>
        <FieldDetectionRegion>
            <id>4</id>
            <sensitivityLevel>50</sensitivityLevel>
            <timeThreshold>0</timeThreshold>
            <detectionTarget>human,human</detectionTarget>
            <alarmConfidence>low</alarmConfidence>
            <RegionCoordinatesList xmlns=""/>
        </FieldDetectionRegion>
    </FieldDetectionRegionList>
</FieldDetection>


Here's what I see using Wireshark when I hit "Save" on the "Linkage Method" tab (you can see the "FieldDetectionRegionList" is NOT being sent):

Code: 
<?xml version="1.0" encoding="UTF-8"?>
<EventTrigger>
    <id>FieldDetection-1</id>
    <eventType>FieldDetection</eventType>
    <dynVideoInputChannelID>1</dynVideoInputChannelID>
    <EventTriggerNotificationList>
        <EventTriggerNotification>
            <id>center</id>
            <notificationMethod>center</notificationMethod>
        </EventTriggerNotification>
    </EventTriggerNotificationList>
</EventTrigger>

It may be different on your NVR/firmware... I think you need to check with Wireshark.
 
Last edited:
  • Like
Reactions: 123456
123456 said:
What's your NVR and firmware?
Click to expand...

NVR DS-7616NI-M2/16P firmware V5.04.070 build 250828
Camera DS-2CD2387G2-LU firmware V5.7.19 build 241207

I was wondering... why not send the ISAPI directly to the cameras instead of the NVR... that would bypass the problem you have with the differences in the "draw area" between your NVR and camera.

You can do this even if the cameras are connected to the NVR PoE ports... just make sure NVR "virtual host" is on and send the request to http://<NVR_IP>:65001 for camera on PoE port 1, http://<NVR_IP>:65002 for camera on PoE port 2, etc.
 
Last edited:
johnfitz said:
I was wondering... why not send the ISAPI directly to the cameras instead of the NVR... that would bypass the problem you have with the differences in the "draw area" between your NVR and camera.
Click to expand...
I have always enabled "Notify Surveillance Center" on the cameras because otherwise it doesn't mark intrusion detect on the recording timeline.

While I want to automate Enable/Disable "Notify Surveillance Center" on nvr to notify me on HikConnet app only when I have armed my alarm system
 
You must log in or register to reply here.
Top Bottom