The PullMessage interval in ONVIF EVENT timing

Ahger

July 13, 2026 03:08

First of all, we would like to express our sincere gratitude to NX for their strong support. 

We have corrected the DI token and tested it in NX version V6.1.2.42921,The Sunmore IPCamera 's DI triggering is now working correctly.

I'm very sorry, I have a question to ask.

The PullMessage interval in ONVIF EVENT is too long (approximately 10 seconds). 

Could it be changed to 1 second?

We hope ，DI triggering will be more immediate.

Sunmore IPcamera  

0

• 

  Ichiro

  • Network Optix team

  July 20, 2026 09:48

  Hi Ahger,

  Thanks for the questions. DI events should typically arrive fairly quickly — depending on network conditions, average latency is usually under seconds even over the public Internet.

  Given that, it's not yet confirmed that "ONVIF EVENT is too long (approximately 10 seconds)" is actually the root cause. Changing the interval to 1 second (or any other value) without a full picture of the behavior could introduce side effects, so we'd prefer to know more context.

  To help us properly understand this,  you may provide the following:

  1. A screen recording showing the delay as it happens
  2. Wireshark packet captures showing what the camera sent and when the server received it
  3. Server debug-level logs

  With this information, we can take a closer look at what might be happening on your end. Right now, "PullMessage interval in ONVIF EVENT is too long" is a potential direction but not yet something we can really act on directly.

  We'd suggest following our standard troubleshooting procedure and sharing the information above when you're able. (please let us know)

   

  Thanks.

  0

Please sign in to leave a comment.