Documentation for Intellect 4.11.0-4.11.3. Documentation for other versions of Intellect is available too.

Previous page Configuring the Technoserv integration  Examples of commands to work with the Technoserv integration Next page


The ApiBgConfig.xml file is used to configure the login and password for connecting the Technoserv system to Intellect, as well as for associating Intellect events with the Technoserv event codes (see the table below).

The file has the following format:

  1. The time in milliseconds between sending PING events
    <PingTimeout>120000</PingTimeout>

  2. The IP-address to be returned on requests of Technoserv.
    <MainHost>192.168.0.171</MainHost>

  3. Username and password to connect to the Technoserv server and send events (if any)
    <Login></Login> <Password></Password>
  4. Correspondence of the Intellect event to the event code: 
    <ApiBgEventMatch>
    <ProductObjectName>CAM_VMDA_DETECTOR</ProductObjectName>
    <ProductEventName>ALARM</ProductEventName>
    <ApiBgEventCode>264400</ApiBgEventCode>
    <ProductObjectIds>
      <id>2</id>
      <id>1</id>
    </ProductObjectIds>
    <ParamMatch>
        <ProductEventParamName>num</ProductEventParamName>
       <ApiBgEventParamCode>NUMBER_OF_DETECTED_PEOPLE</ApiBgEventParamCode>
    </ParamMatch>
    <Shapes>1</Shapes>
    <Picture>1</Picture>
</ApiBgEventMatch>

    1. ProductObjectName, ProductEventName – Intellect object and event, for example, CAM|MD_START.
    2. ProductObjectIds – Intellect object id, if you need to specify specific detectors. May be absent, then events will be transmitted to all detectors.
    3. ApiBgEventCode – event code, see below.
    4. Shapes – whether to transfer the Shapes field.
    5. Picture – whether to send a link to the freeze frame.
    6. ParamMatch – correspondence of the Intellect event parameter name to the event parameter. May be absent.

Event codes:

Code

Event name

1799

Crowd Detection (detect crowds, including in unauthorized places)

264393

Abandoned object detection

264383

People counter

264385

Estimated people traffic density in significant city sites

264388

Detection of moving against crowd flow

264387

Person stopped in the controlled area (with the preset stop time)

264386

Sharp acceleration of human movement

264389

Chaotic human movement (idleness)

264391

Indexing events in traffic conditions (traffic jams)

264392

Indexing of events in traffic conditions (massive accumulation of vehicles)

264390

Indexing events in traffic conditions (traffic density)

264394

Detection of crossing the forbidden zone (by human or vehicle)

264395

Disappeared object detection

264396

Responding to the passage of people in a given direction (entrance)

264397

Responding to the passage of people in a given direction (exit)

264399

Responding to the passage of people in a given direction (corridor etc.)

264398

Responding to the passage of people in a given direction (crosswalk)

264400

Appearance of a person or car in the observation zone (streets, squares, intersections, parks)

1795

Focus loss detection

1797

Dirty camera lens

264403

Background change

264402

Camera shift

1796

Blind/cover detection

264401

Bare flame

287069

Target detected

siren

Siren or car alarm detected

shout

Human cry detected

klaxon

The sound of the car horn detected

voice

Human speech detected

brake

The sound of a vehicle brake detected

shockwave

A shock wave detected

shock

A bang/shot/blast detected

PING

It is used for a regular event periodicity sent to control the communication channel between the IS and the "Safe City" software and hardware complex. Value is filled as cameraCode=-1.

not_available

The camera is unavailable (there is no video stream or no connection with the camera, etc.)

available

The camera is available

  • No labels