Where can be found the guide for Adding Mobile Video Service (MVS) to BVMS?
The attached manual provides information for Mobile Video Service (MVS) within Bosch Video Management System.
You can find: - how to configure the router and Internet Information Service (IIS) - how to add MVS to BVMS - user guide - some troubleshooting tips
This document can also be found online here.
... View more
The purpose of this article is to provide step by step instructions on how to successfully import video and storage devices from a DIVAR IP Recording Appliance to a Professional BVMS system while retaining all existing recorded video.
Note: This procedure should only be performed by a certified BVMS / VRM technician or installer
Prior to starting
BVMS 7.0 and VRM 3.60.0043, or newer, should be installed on all systems involved in the transfer.
A backup of the BVMS Elements file and config.xml from all VRMs involved should be made before starting the procedure.
BVMS Configuration Client should be accessible to the technician, or should be installed on the technician's laptop.
Note: Due to the usage of hardware IDs utilized by recording appliances, Bosch Configuration Manager can no longer be used in this scenario.
This article will simulate transferring devices and storage associated with a DIVAR IP 3000 Recording appliance (BVMS 7.0) to a VRM installed in a BVMS Professional installation:
Appliance IP address: 192.168.1.16
Video device: 192.168.1.59
Pro BVMS IP Address: 192.168.1.99
Video Device: 192.168.1.81
This is a field scenario where multiple appliances have been installed, and over time the system has grown to a point that a professional BVMS installation is put in place. This scenario provides the ability to leverage existing storage on the appliances, as well as retention of existing video.
A. Appliance system
There are several steps in preparing the system for migration, these should be performed in order.
1. Stop all recording on devices to be transferred:
In BVMS Configuration Client navigate to the “Cameras and Recording" Tab
Select the “VRM” menu.
In the “Recording” submenu select “No Recording” for all devices assigned to the appliance.
Save and Activate changes.
2. To verify recordings have been stopped, from the “Devices” menu in Configuration Client right click the appliances VRM and select “Show VRM Monitor”:
From the devices menu on the VRM Monitor page the “Active recordings” should read 0.
3. Preventing cross communications from the old system to migrated devices is critical once in they are in new system. The suggested work flow is as follows:
From the devices menu right click and “Remove” all video devices from the Appliance’s VRM.
Remove the Appliance’s storage from the VRM.
Save and Activate Changes.
Remove the VRM from the BVMS system, Save and Activate changes.
4. From the “Services” menu on the Appliance the following services should be stopped and modified:
Bosch Video Recording Manager (Primary and Secondary).
BVMS Central Server.
Service “Startup type” should be modified to either “Manual” or "Disabled”
B. BVMS Professional system
From the BVMS professional system, the first step is to add the legacy storage. Prior to performing this step there are certain technical aspects that may impact the migration and need to be considered.
Spans on the legacy storage have already been issued to the video devices that will be migrating into the new system.
To avoid span distribution issues, such as assigning the same span to multiple devices, one of two steps can be performed.
Add legacy devices and storage to a new “Storage Pool”.
“Default” migrated video devices prior to finalizing the migration.
In this technical brief the new “Storage Pool” method will be utilized.
To add a new “Storage Pool” right click the systems VRM:
Select “Add Pool”.
After adding the pool, right click and “Add iSCSI”.
From the “Add iSCSI Device” menu enter the appropriate information. In this example we assigned the name “migrated” to the legacy storage
Save and Activate changes.
⚠️ NOTE: If you are adding legacy storage to a common pool, DO NOT activate yet!
From the new systems VRM Monitor page you should see that there are now “Legacy recordings”.
These are the existing recordings of the cameras to be migrated.
5 To migrate video devices, after legacy storage had been added right click the new pool and select the “Scan for Encoders” sub menu:
From the “Scan Wizard” menu select all devices to be migrated.
Once devices have been added, Save and Activate changes.
Add devices to the Logical Tree and adjust “Profiles” and recording settings as needed”.
6 From the VRM Monitor page you should see the following:
Legacy recording should be 0 bytes. These recording should be re associated with the newly migrated cameras.
Total channels should reflect the new camera count of the system.
7 From BVMS Operator Client newly migrated devices, along with their legacy recordings, should be accessible.
... View more
There are different ways for a client to receive a multicast stream:
the client can connect to the camera and request a multicast stream. In this case you would see a connection in the dashboard.
If not checked, it requires at least one connected client to have the camera provide the stream into the multicast group. Clients who just joined would receive no stream if there is no client connected.
the client can join an existing multicast stream without connecting to the camera. It must know the multicast group. You would not see this client on the dashboard.
The streaming flag tells the camera if it should feed its stream into this multicast group, regardless of a connected client. This is an option if there are many, many clients possibly connecting to the same camera/stream.
There is no difference in data amount if streaming is checked or not as long as there is at least one multicast client connected to this multicast group.
Below you find a way how to pass a special connection string to request a multicast stream via RTSP from a BOSCH IP camera or IP encoder.
The following string triggers the connection to be multicast stream using the multicast IP and port that were predefined in the configuration before.
see device webpage --> Settings --> Network --> Multicasting
If you want to get the multicast stream on a specific IP and port (e.g. IP 220.127.116.11, port 1234) you can use following syntax:
rtsp://192.168.0.1/&multicast_video=1&mc_group_video=18.104.22.168&mc_port_video=1234 You can also use the RTSP SETUP command to enable multicast streaming. Note: Forwarding the RTSP port using RTSP SETUP command is supported with firmware 5.50 and later.
There is also a posibility to use SDP file:
You should configure the encoder to create cyclic I-frames, do not leave it on auto but set e.g. to 30.
Enter a multicast group address and set the streaming checkbox.
Then record the connection setup with Wireshark and save the relevant info as SDP file locally. Then, the payload type should be correct.
If necessary, edit the SDP file to match your intended multicast group address and port , and check the payload type which should be 35 for H.264.
There are two locations in the file for the payload type.
Then open the file in VLC.
The SDP file should look like this:
o=- 0 0 IN IP4 <ipaddress>
m=video 60010 RTP/AVP 35
c=IN IP4 22.214.171.124
Alternativly, there is an undocumented (thus untested and without guarantee that it is fully functional) feature in our devices that allows to download an SDP file:
http:// < ipaddress > /live.sdp?line=1&h26x=4 via browser and save it locally.
Edit the file as nessesary and open in VLC.
PDF: Please see also the attached PDF from year 2016 which is still of help these days
... View more
Related Products RPS 5.12 Overview Helps when encountering error 'SQL BPA Command line has encountered a problem and needs to close' when running the Windows Installshield Wizard for Microsoft SQL Server 2005 Express Edition Server Pack 3 (SP3). Issue If you open the Application Event Log in the event viewer after the failure, you can notice the error below: The error 29552 indicated in the MsiInstaller error means that the Upgrade Advisor (SQL tool used during setup) encountered a problem when dealing with Reporting Services. If you open the RS.log log file located under C:\Documents and Settings\Administrator\Application Data\Microsoft\SQL Server 2005 Upgrade Advisor\log, you can get more information about what leads the Upgrade Advisor to fail. This indicated that the BpaCmd.exe command line (called by the Upgrade advisor) failed because it couldn’t locate the file BPAClient.dll (causing the FileNotFoundException exception). Solution There is a simple workaround that you can use in order to achieve the setup of SQL Server 2005 Express Edition Service Pack 3 with success. Here are the steps of the workaround: Copy the BPAClient.dll file located under 'C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\BPA\bin' to: 'C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\BPA'. Run the SQL 2005 SP3 setup again. Notes
... View more
Related Products ReadykeyPRO Question What effect does losing communication with the server have on an access controller? Answer The ISC has its own memory, and it will run locally from its own database. The ISC itself will not be effectedÂ by a communication loss unless it runs out of transaction memory, or it operates any global functions. Any readers providing access without global anti-passback will not be effected. When the ISC has an upstream communication failure with the communication server and/or linkage server, global features will cease to function. This includes features such as Scheduler, Guard Tour, Global Anti-Passback, and Global Input/Outputs. If there is a failure upstream to the communication server from an ISC, the linkage server, global output server, and any other server service that requires activity from the offline access panel will not run any functions associated with the events from that panel (i.e. an e-mail will not be sent on an Access Granted from the ISC if the ISC is offline with the communication server).
... View more