Enable/Disable "Notify Surveillance Center" via ISAPI

rug4096 · Apr 5, 2024

I have learned how to control this setting via ISAPI:

http://user:[email protected]/ISAPI/Smart/FieldDetection/1

But how can I control this one?

This would be really cool if someone can help here!

rug4096 · Apr 5, 2024

Nevermind... found the URLs by sniffing the browser-traffic with WireShark:

http://192.168.1.101/ISAPI/Event/triggers/fielddetection

http://192.168.1.101/ISAPI/Event/triggers/linedetection

trempa92 · Apr 7, 2024

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

rug4096 · Apr 7, 2024

trempa92 said:
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

Thats great! Thanks!

123456 · Tuesday at 12:07 PM

Hi all,
I'm interested too, but I can't find the HTTP command:

johnfitz · Tuesday at 1:54 PM

123456 said:
I'm interested too, but I can't find the HTTP command:

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:

Toggle "Notify Surveillance Center" off:

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>

johnfitz · Tuesday at 2:51 PM

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.

123456 · Wednesday at 9:25 PM

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

johnfitz · Thursday at 5:32 PM

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:

trempa92 · Friday at 5:30 AM

Sometimes body co tains multipart, you dont necesarilly need to send post put entire body, just part of it that you need

123456 · Friday at 2:15 PM

NVR Device Model DS-7608NXI-I2 / 8P/S
Firmware Version V4.62.225 build 240123

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.

johnfitz · Friday at 6:46 PM

123456 said:
To enable or disable the "Surveillance Center" notification, which HTTP PUT should I send without modifying other parts?

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>

johnfitz · Friday at 7:10 PM

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.

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

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

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.

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...

123456 · 2025-11-03T03:56:06-0500

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"?

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.

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...

Yes, the camera is newer than the NVR
Device Model DS-2CD2387G2H-LISU/SL
Firmware Version V5.7.17 build 240606

johnfitz · 2025-11-03T15:20:02-0500

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.

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

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.

Search

Search

Enable/Disable "Notify Surveillance Center" via ISAPI

rug4096

n3wb

rug4096

n3wb

trempa92

Getting comfortable

rug4096

n3wb

123456

Young grasshopper

johnfitz

Known around here

johnfitz

Known around here

123456

Young grasshopper

johnfitz

Known around here

trempa92

Getting comfortable

123456

Young grasshopper

johnfitz

Known around here

johnfitz

Known around here

123456

Young grasshopper

johnfitz

Known around here