About Central_Support

Question   Is it possible to get Metadata from Bosch camera integrated in Milestone?   Answer   Yes! The way to get Metadata in Milestone is through the Bosch Enhanced Metadata Plug-in. The installation manual and the download link for the plugin is here.   Scroll down the page and go to the “HOW TO INSTALL” menu:   Scroll down to find the installation manual:   Scroll down to find the Plugin and click on the Download link:   This plug-in enables the following: - Visualize object classifications, outlines and trajectories and counting data. - Control Intelligent Tracking with AUTODOME or MIC cameras. - Visualize metadata fusion. - Control the MIC wiper through Milestone’s rule engine.    Nice to know: What web browsers are supported by Bosch IP cameras? What to do with missing metadata in Milestone XProtect What is the difference between the 3 metadata streaming modes in Milestone XProtect? ... View more

Question   New check in BVMS Configuration Client has been implemented, which blocks the disabling of the "Secure connection" if camera port 1756 is disabled. This should prevent the camera from getting "unreachable" by miss-configuration of the administrator.  What is the possible impact on BVMS of the disabled Bosch camera port 1756 RCP?   Answer   Camera communication blocked if option „Secured connection” is disabled in the Edit Camera dialog Retrieving device capabilities might not work Initial password setting might not work   1. Impact on BVMS 12.1   All communication is done via port 443. When adding new cameras (with Secure by default firmware) the option "Secure connection" in the Edit camera dialog is enabled by default. Disabling the secure connection is not possible as long the camera port 1756 is closed (see feature explained below (Secure Connection: New check blocks the disabling of the "Secure connection" if camera port 1756 is closed).   2. Impact on BVMS 12.0.1   Without additional software patch, new cameras where port 1756 is disabled (Secure by default firmware), can be added to BVMS, but requires several steps, Authentication fails (red cross on the cameras). Additional Patch needs to be installed to "redirect" all former 1756 communication through port 443. The patch release is planned for end of December 2023. Workaround as long the patch is not yet released or without installing the patch: 1. Scan the camera and provide the pre-assigned password in the scan dialog 2. Camera will be added to the Device tree but red cross is indicating: No connection 3. Right click on the camera, Edit Encoder, the capabilities will be read in and authentication works now, green unlock appears Remark related to BVMS 12.0 installations: There will be no patch provided for BVMS 12.0, upgrade to 12.0.1 is advised instead.     3. Impact on BVMS 11.1.1   Without additional software patch, new cameras where port 1756 is disabled (Secure by default firmware), can be added to BVMS, but requires several steps, Authentication fails (red cross on the cameras).  Additional Patch needs to be installed to "redirect" all former 1756 communication through port 443.  https://resources-boschsecurity-cdn.azureedge.net/public/software/Software_BVMS111165_Patch_CantAddCamSpecFW_424238_all_104628585227.zip Workaround without installing the patch:  1. Add the camera manually with type "Placeholder, it will be added to the device tree 2. Right click on the camera and open the Edit Encoder dialog 3. Enter the pre-assigned password and press Authenticate, this will read in the capabilities. After pressing OK the camera should be fully connected to BVMS and green unlock is shown.     4. Impact on BVMS 11.0 and earlier versions   There will be no additional software patch provided. New cameras where port 1756+80 is disabled cannot be added to BVMS, the authentication process will fail.  Note According to the BVMS firmware support policy (which is max. 2 years between  the firmware release date and the BVMS version release date) the firmware 9.00 or 8.90 should not be used with BVMS 11.0 or earlier versions.   Secure Connection: New check blocks the disabling of the "Secure connection" if camera port 1756 is closed   When adding new cameras to the system, this option is enabled by default in BVMS, started with version 9.0 (August 2018). This follows the company recommendation from a Data Security point of view. The main communication from the BVMS Management Server to the camera is done via secure port 443. It also impacts the live view streaming in the Operator Client (depending on uni-multicast/UDP/TCP settings). There are some exceptional cases where the disabling of the secure connection in the Edit Encoder dialog is necessary. This results in all communication being passed through the legacy RCP+ port 1756. If the port is not enabled in the camera configuration, a connected camera becomes unreachable and new camera cannot be added and used in BVMS, it will simply not work. To avoid misconfiguration, a new check in BVMS has been implemented, which does not allow to disable the "Secure connection" for a camera if port 1756 is disabled in the camera. If you need to disable it and the Secure connection option is grayed out:   go to the Network menu and under the Details section select On from the drop-down menu next to the RCP+ port 1756   and the Secure connection option will be available again to be disabled/ enabled:    Nice to know: Secure by default - Increasing the default level of IP camera security We also recommend you to have a look in our Bosch Building Technologies Academy:  BVMS 12.1 - Technical and Commercial Introduction "Online" Training ... View more

 Note This is just an example how to start and stop an audio recording of a camera on particular BVMS event that trigger scriplets. Any event could be used. For example Operator Client Event Buttons, can be used, when the requirement is that the operator should be able to start and stop recording from Operator Client.    Follow the step-by-step guide below:   Step-by-step guide   1. Configure the Virtual Input that can be toggled by the Operator in BVMS Operator Client (Devices)   Do not forget to Save Drag & drop the Virtual Input into the Logical Tree from Maps and structure Save   2. Configure Event for this Virtual Input: Go in the Events tab and open the Command Script Editor Attached you can find an example script. Paste the script into Command Script Editor:  AudioOnOff_EncoderCredentials.zip   Note: They just turn on or off the Audio setting of a camera, by sending the respective rcpp command to the camera. When Audio is ON, it will be recorded.   Paste the Script and Save   Configure the Event for this Virtual Input: VI on - call a server scriplet AudioON VI off - call a server scriplet AudioOFF   Save & Activate   3. Configure the Audio settings of the camera and click Set   4. Open the Operator Client and start using the Virtual Inputs   Script example - explained: Note: Where text is red, adapt it for your system // ScriptType: ServerScript // ScriptLanguage: CS using System; using System.Diagnostics; using System.Collections.Generic; using log4net; using Bosch.Vms.Core; using Bosch.Vms.SDK; using System.Net; [BvmsScriptClass()] public class ServerScript : IDisposable { private readonly IServerApi Api; private readonly ILog Logger;   private void RequestURL(string lcUrl) { // *** Establish the request HttpWebRequest HttpWebRequest loHttp = (HttpWebRequest)WebRequest.Create(lcUrl); // *** Set properties loHttp.Timeout = 10000; // 10 secs loHttp.UserAgent = "Code Sample Web Client"; // camera autentication loHttp.Credentials = new NetworkCredential("service","WSS4Bosch!"); loHttp.PreAuthenticate=true; // *** Retrieve request info headers HttpWebResponse loWebResponse = (HttpWebResponse)loHttp.GetResponse(); loWebResponse.Close(); } public ServerScript(IServerApi api) { this.Logger = LogManager.GetLogger("ServerScript"); this.Api = api; }   public void Dispose() { // Use this method to cleanup any resources here (consider fully implementing the Dispose pattern). // For example, stop and dispose any started timers. Ensure that all threads that were started are stopped here. // DO NOT BLOCK in this method for a very long time, as this may block the applications current activity. }   [Scriptlet("169ad1f0-0b55-4bdd-a817-581371a95316")] public void AudioOn(EventData e) { //this is just example ip address RequestURL("http://192.168.1.46/rcp.xml?command=0x000c&type=F_FLAG&direction=WRITE&payload=1"); }   [Scriptlet("f36bb5b0-2fea-4722-bcb2-15f3ed64878f")] public void AudioOff(EventData e) { //this is just example ip address RequestURL("http://192.168.178.46/rcp.xml?command=0x000c&type=F_FLAG&direction=WRITE&payload=0"); } } ... View more

In case you have noticed a gap between the left and right of the lens installation, this might cause improperly focus for the camera's image. Therefore, please proceed as explained in this document or as per steps below:   Step-by-step guide   1. Disassemble IR ASSY (IR LED + IR Holder): 3x M2x6 torx screw.   2. Loosen the 2x side screws holding the lens: 2x M2 hex screw.   3. Pull slightly the lens (do not pull it out completely) and push it back.   4. Tighten the 2x side screws holding the lens: 2x M2 hex screw, 0,025Nm torque   5. Re-assemble the IR ASSY (IR les + IR Holder): 3x M2x6 torx screw, 0,1Nm torque   In case the focus issue is not solved after following the steps above, RMA is recommended. 1. You have to fill in the RMA form with the necessary contact details. Please make sure that the customer number is filled in correctly. You can find your customer number on every Bosch invoice in the right top corner. It should start with 820, 190, 119 or 200. If in doubt, you can contact your Bosch sales representative. 2. Material number of your product (e.g. F.01U.321.917) 3. Serial number of the faulty product   4. Return reason code: R13 - Optical and/or lens issue (iris, zoom, focus, sensor, unsharp)  5. Detailed description: Lens-holder gap,  focus issue for the camera's image. Important: In case the unit was bought directly from Bosch, send the form to Central Technical Support Team so that they can afterwards send it towards the repair desk. Otherwise, if the unit was bought from distributor, please ask him to forward it directly to RMA Desk (see e-mail address in the RMA form). ... View more

Possible causes and solution(s)   Symptoms   During the authentication process with Bosch cameras to a RADIUS server, the event “5400 Authentication failed” occurs. Even that the certificates were generated, uploaded to camera, uploaded to server, in the authentication process in the last step, this message is displayed.   Solution   To be able to make the dot1.x work with the certificate, you have to modify the Certificate: the Enhanced Key Usage to only “Client Authentication” and add a Subject Alternative Name: your EAP identity note: According to RFC5216 the EAP-TLS Identity must be identical to the 'subjectAltName' field in the certificate Then, the Bosch camera should authenticate via 802.1x  Nice to know: How to setup Certificate based authentication with Bosch?  How to create CA signed certificates for cameras and distribute CA certificate in large systems    If the above recommendation doesn’t solve the failure, please provide the Central Technical Support team with the following: Wire-shark from port mirror where camera gets connected to First start the capture before plugin the camera to the switch Gather all used certificates + passwords if needed Camera Config file (pull at time off other logs) + passwords for service and loading Camera maintenance log Network diagram Configuration/settings + used certificates of authenticating server Install on the Wireshark PC a syslog server and configure printouts: syslog_dbg; eapol; ssl; this way the syslog server starts automatically collecting when camera gets connected to the switch and is in sync with the matching WireShark Are there other cameras that work with EAP-TLS? If yes, please let us know the model of the other camera that are working with these certificates. a screenshot showing the client and server certificates and its usage that has been assigned. Similar with: ... View more