Table Of Contents

Devices generate and transmit their replies to an autodetect request with a random delay of up to 2 seconds. When implementing your own detection software, please bear in mind that, when calculating the necessary waiting period until all replies are received, additionally to the possible span of max 2 seconds, you need to consider the time necessary to process the reply as well as the time the packet spends on the wire and in propagation devices like switches or routers on its way to and back from the device to be detected.

The scanned devices send their replies either to the source IP address of the request, or to the broadcast address 255.255.255.255. In case the source IP address of the request resides inside the same subnet, that is defined by the scanned device's IP address and it's subnet mask, the reply is addressed to the source IP address in the request. If the originator is not located in the same subnet as the scanned device, the reply is addressed to the broadcast address 255.255.255.255. In case of a scan request sent to the device via the multicast scan group, the reply is addressed to the same multicast group.

An autodetect scan request packet must consist of an autodetect request header, that may or may not be preceeded by an RCP plus protocol header for command id CONF_RCP_AUTODETECT (0xffdc). In case of an existing RCP plus protocol header in the scan request, the length field of the RCP plus protocol header must contain the length of the autodetect request header.

The format for the autodetect request header as well as for the autodetect reply is shown below:

<?xml version="1.0" encoding="UTF-8"?>
<root xmlns="OEMExtXX:device-1-0">
<device>
   <deviceType>OEMExtXX:device:deviceIDYY</deviceType>
   <friendlyName>VideoJet</friendlyName>
   <unitName>UnitName</unitName>
   <deviceGUID>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</deviceGUID>
   <serialNumber>XXXXXXXX:YYYYYYYY</serialNumber>
   <physAddress>XX-XX-XX-XX-XX-XX</physAddress>
   <sessionKey>XXXXXXXXXXXXXXXX</sessionKey>
   <unitIPAddress>XXX.XXX.XXX.XXX</unitIPAddress>
   <unitSubnetMask>XXX.XXX.XXX.XXX</unitSubnetMask>
   <unitGatewayIp>XXX.XXX.XXX.XXX</unitGatewayIp>
   <unitIPv6Address>XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX</unitIPv6Address>
   <activeConnections>XX</activeConnections>
   <RCPPort>XXXX</RCPPort>
   <HTTPPort>XXXX</HTTPPort>
   <HTTPSPort>XXXX</HTTPSPort>
   <dhcp>X</dhcp>
   <cameraFrontendID>XXXX</cameraFrontendID>
   <Flags>X</Flags>
   <Lines>X</Lines>
   <BcJpeg>X</BcJpeg>
   <ClusterMember>XXX.XXX.XXX.XXX</ClusterMember>
   <ClusterMemberMAC>XX-XX-XX-XX-XX-XX</ClusterMemberMAC>
   <ClusterID>X</ClusterID>
</device>
</root>

<root xmlns="OEMExtXX:device-1-0">
XX is the OEM Extension; 0x00 for Bosch Security Systems; OEM specific

<deviceType>OEMExtXX:device:deviceIDYY</deviceType>
XX is the OEM Extension; 0x00 for Bosch Security Systems; OEM specific
YY is the VideoJet ID from the request packet

<friendlyName>VideoJet</friendlyName>
The name and type of the VideoJet; type and OEM specific

<unitName>UnitName</unitName>
The name of the unit coded in UTF-8

<serialNumber>XXXXXXXX:YYYYYYYY</serialNumber>
XXXXXXX is the Hardware version of the VideoJet
YYYYYYY is the Softwareware version of the VideoJet

<physAddress> XX-XX-XX-XX-XX-XX </physAddress>
XX-XX-XX-XX-XX-XX is the MAC address of the VideoJet

<sessionKey>XXXXXXXXXXXXXXXX</sessionKey>
No common use

<unitIPAddress> XXX.XXX.XXX.XXX </unitIPAddress>
XXX.XXX.XXX.XXX is the current IP address of the VideoJet

<unitSubnetMask>XXX.XXX.XXX.XXX</unitSubnetMask>
XXX.XXX.XXX.XXX is the subnet mask of the VideoJet

<unitGatewayIp>XXX.XXX.XXX.XXX</unitGatewayIp>
XXX.XXX.XXX.XXX is the current gateway IP address of the VideoJet

<unitIPv6Address>XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX</unitIPv6Address>
XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX is the current IPv6 address of the VideoJet e.g. FD00::1234:5678

<activeConnections>XX</activeConnections>
XX is the number of active media connections of the VideoJet

<RCPPort>XXXX</RCPPort>
XXXX is the current RCP port number the VideoJet is listening to

<HTTPPort>XXXX</HTTPPort>
XXXX is the current HTTP port number the VideoJet is listening to

<HTTPSPort>XXXX</HTTPSPort>
XXXX is the current HTTPS port number the VideoJet is listening to

<dhcp>X</dhcp>
X indicates if dhcp is switched on (1) or off (0)

<cameraFrontendID>XXXX</cameraFrontendID>
XXXX is the ID of the (internal) camera frontend (see also Bicom documentation)

<Flags>X</Flags>
X is the flag value returned by RCP command CONF_CM_DEFAULT_CONFIG
 
<Lines>X</Lines>
X is the number of video lines the device has

<BcJpeg>X</BcJpeg>
X indicates the ability to deliver JPEGs via the broadcast JPEG retrieval mechanism

<ClusterMember>XXX.XXX.XXX.XXX</ClusterMember>
XXX.XXX.XXX.XXX is the ip address of one of the cluster members; there might be multiple entries including this device

<ClusterMemberMAC>XX-XX-XX-XX-XX-XX</ClusterMemberMAC>
XX-XX-XX-XX-XX-XX is the MAC address of one of the cluster members; there might be multiple entries including this device

<ClusterID>XX</ClusterID>
XX is index number of the above ClusterMember list of this device

1. The client opens up a TCP connection to the VideoJet.
2. The client sends an RCP registration as mentioned above.
3. The RCP server (the VideoJet) will respond with the result code and the assigned Client ID.
4. The client is now allowed to send RCP Requests provided with the Client ID.

1. The client opens up a TCP connection to the VideoJet.
2. The client sends an RCP registration with the ‘Hook On’ command and an existing Client ID on the same host. The password is not needed in this case (PL set to 0).
3. The RCP server (the VideoJet) will check whether the other client is registered properly on the same host.
4. The RCP server (the VideoJet) will respond with the result code and a NEWLY assigned Client ID.
5. The client is now allowed to send RCP Requests provided with this Client ID.

• live – For video access only; no control
• user – For video access and control over the video stream (e.g. caminput)
• service - for video and all administrative access

1. A 16 character random string for MD5 hash calculation must be requested from the VideoJet (RCP command CONF_RCP_REG_MD5_RANDOM).
2. A string +random_string+++username:password+ must be formed.
3. The response MD5 hash over this string must be calculated.
4. The identification string in the register packet must have the following format: +Username:random_string:response_string+