Synology DS418 Transactions in Surveillance Station 8.1.0 and above - Page 32

dsName, sessionId, deviceName, timestamp, same parameter is sent again

Page 32 highlights

Note: • If your Synology NAS is a CMS Host server, you can specify dsName to designate a CMS recording server which the transaction device is on. If dsName is not specified, the CMS Host server is first searched before CMS recording servers for transaction devices matching the given name. If two or more CMS recording servers connects to transaction devices matching the given name and dsName is not specified, the command will be ignored. • sessionId is used to distinguish between different transaction events. The same deviceName and sessionId will be treated as the same record. If the same parameter is sent again, the Begin method will be ignored until the transaction has completed, canceled, or exceeded transaction time limit. After that, sessionId can be reused. • After the start of the transaction, if the time limit is exceeded before receiving the Complete or Cancel methods, the transaction record will be saved and marked as Incomplete. • timestamp is in UTC format, you can use https://www.epochconverter.com/ to convert the current time to timestamp or check if the timestamp is correct. Send Transactions Using WebAPI 31

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35

31
Send Transactions Using WebAPI
Note:
• If your Synology NAS is a CMS Host server, you can specify
dsName
to
designate a CMS recording server which the transaction device is on. If
dsName
is not specified, the CMS Host server is first searched before CMS recording
servers for transaction devices matching the given name. If two or more CMS
recording servers connects to transaction devices matching the given name and
dsName
is not specified, the command will be ignored.
sessionId
is used to distinguish between different transaction events. The
same
deviceName
and
sessionId
will be treated as the same record. If the
same parameter is sent again, the Begin method will be ignored until the
transaction has completed, canceled, or exceeded transaction time limit. After
that,
sessionId
can be reused.
• After the start of the transaction, if the time limit is exceeded before receiving
the Complete or Cancel methods, the transaction record will be saved and
marked as Incomplete.
timestamp
is in UTC format, you can use
to convert the current time to timestamp or check if the timestamp is correct.