About Central_Support

 Important Do I need a license for the remote live stream of my camera in Remote Portal (Remote Connect)?   Question   Why the "Customer" user from the Bosch Remote Portal can see only few cameras in Video Security App?   Answer   Let's suppose that the "Customer" user should see 3 cameras in the Video Security App. When logging to the App, he can see only 2 of them. Why? This is because the "Administrator" user didn't grant rights to the "Customer" user to see the 3rd camera.   In the following example, we have 3 levels of users: Administrator: @ro.bosch.com Customer:  @gmail.com Technician: @yahoo.com  The "Administrator" user needs to login into the Bosch Remote Portal and grant the rights to the "Customer" user. 1. Login as Administrator in https://remote.boschsecurity.com/login > Go to the "Users" tab and click on the Customer row: 2. You will see that only 2 cameras out of 3 have been assigned to the "Customer" user.  Click on the "Services" tab and select "Remote Connect" option:   3. Identify the camera that was not assigned to the "Customer" user and click on it. 4. Click on the "Add Customer" button and fill in the details of the "Customer" user > Save 5.  The message that "the <customer name user> was successfully assigned to the system" will be displayed. 6. Now, the "Customer" user must do a refresh in the Video Security App and he will see all 3 cameras. ... View more

Bosch Remote Portal connects you to your Bosch Security devices from anywhere and lets you perform remote administration and maintenance anytime. In this article it is explained in a step-by-step guide how you can register Bosch IP cameras to Bosch Remote Portal.    Step-by-step guide   Option 1: Register your cameras through camera website   1. Open camera website in local network 2. Select Configuration 3. Navigate to Connectivity > Cloud services 4. In field Cloud-based services switch Operation to On and click Set button 5. Click Connect to Bosch Remote Portal button 6. Enter your user name and password of Bosch Remote Portal (Admin or Technician) 7. Agree to terms & conditions and click Connect > the camera appears in your account in Bosch Remote Portal. Notes: If an Administrator or Technician belongs to more than one (1) account in Remote Portal, he cannot register devices to Remote Portal, unless he configures the Default Commissioning Company in Remote Portal > User Settings > My Companies. The Default Commissioning Company gets activated for 12 hours, but another Default Commissioning Company can be selected earlier. In Firmware versions earlier than v.7.70 the camera can be registered to Remote Portal under Network > Advanced tab.   Option 2: Register your cameras through Configuration Manager (bulk commissioning)   1. Start Bosch Configuration Manager in the local network 2. Authenticate the camera(s) to be added to Bosch Remote Portal in "Devices" or "My Devices" list:     > Right click > click Set Session Authentication > enter service level user and password > click OK   3. (Multi-)Select the cameras to be registered to Bosch Remote Portal in "Devices" or "My Devices" tree 4. Select Connectivity tab and Cloud services sub tab 5. Switch Operation to On and click Save 6. Click Register button   7. Enter your user name and password of Bosch Remote Portal (Admin or Technician) and click Connect button 8. The cameras show ‘Registered’ and appear in your account in Remote Portal. Note: If an Administrator or Technician belongs to more than one (1) account in Remote Portal, he cannot register devices to Remote Portal, unless he configures the Default Commissioning Company in Remote Portal > User Settings > My Companies. The Default Commissioning Company gets activated for 12 hours, but another Default Commissioning Company can be selected earlier.   Note: If the cameras fails to become registered to Bosch Remote Portal, please visit the article Troubleshooting Camera Connectivity & Bosch Remote Portal.   Nice to know: For a better understanding of using the Bosch Remote Portal, we encourage you to join our online Training from Bosch Building Technologies Academy!     You can also refer to the following YouTube video where you will find the new features of the Project Assistant App (version 1.4), DNS configuration, camera overview page and the Remote Portal configuration. ... View more

Alarm Management Configuration: Add a 3rd party camera   Bosch Alarm Management supports to connect 3rd party cameras from version 2.11.0 and later. Depending on the 3rd party cameras’ capabilities, there are different ways of adding such cameras to Bosch Alarm Management.   Overview: 1. Add 3rd party cameras with VX Cloud Agent app  1.1 Axis platforms ARTPEC-5, ARTPEC-6 & -7  1.2 Vivotek Schubert platform 1.3 Connectivity  2. Add 3rd party ONVIF cameras 2.1 Port forwarding  2.2 Add 3rd party ONVIF camera  2.3 Alarm Management ONVIF compatibility 3. Video Control   Step-by-step guide   1. Add 3rd party camera with VX Cloud Agent app 1.1 Axis platforms ARTPEC-5, ARTPEC-6 & -7   For these Axis cameras, the VX Cloud Agent app needs to be installed in the camera to establish the connection to Bosch Alarm Management. The Access Token authenticates the connection from the camera to Alarm Management. Please perform the following steps: 1. In the local network, find the related camera with AXIS IP Utility. 2. Open the camera's website 3. Select Settings 4. Select Apps (1) 5. Select "AXIS Video Motion Detection" app (2), start the app (3) and configure motion detection (4)   6. Add and install the "VX Cloud Agent" app. Note: currently there are different app versions available depending on camera platform and connection w/o and w/ proxy. 7. Open Alarm Management Configuration, add a 3rd Party camera, select VX Cloud Agent App 8. Then copy the Access Token. Note: Proxy connection is only recommended for corporate managed networks in critical industry with restrictive outgoing firewall rules and without need for load-balancing video connections. Proxy connection is not recommended for large-scale installations. 9. In Axis camera Settings > Apps > VX Cloud Agent app a. Select Allow reverse port forwarding (1) and Apply default settings (1) b. Unselect checkbox Ignore cloud settings (2) c. Add user name (3), password (3) and Access Token (3) and click Save (4). 10. Then Start the VX Cloud Agent app (5).   11. In Alarm Management Configuration, configure Recording Mode and Cloud Storage. Now your AXIS camera is set and you should be able to see video from the camera in the Alarm Management Live View.    1.2 Vivotec Schubert platform   For Vivotek Schubert cameras, the VX Cloud Agent app needs to be installed in the camera to establish the connection to Bosch Alarm Management. The Access Token authenticates the connection from the camera to Bosch Alarm Management. Please perform the following steps: 1. When you have connected a new camera to your router, you need to open its web interface - just type in the local IP address of your new camera in a web browser - you can find this local IP address (usually in format 192.168.x.x) in your router among other connected devices.   2. When you have opened the camera’s web interface, you need to activate it first by setting up a password:   3. Login to the camera using the password and navigate to Configuration > Applications > Package management and upload the application package:   4. Wait until installation ends and refresh the page. You will see “VXG Cloud Agent“ appeared in the Package list. Click on it to open the app settings page:   5. Open Alarm Management Configuration, add a 3rd Party camera, select VX Cloud Agent App   6. Then copy the Access Token. Note: Proxy connection is only recommended for corporate managed networks in critical industry with restrictive outgoing firewall rules and without need for load-balancing video connections. Proxy connection is not recommended for large-scale installations.                           7. Then go back to the camera’s app settings page and enter the following information: Access token - the one you have copied on the Dashboard Camera login & password - your camera credentials   8. Save changes. 9. In Alarm Management Configuration, configure Recording Mode and Cloud Storage. Now your Vivotek camera is set and you should be able to see video from the camera in the Alarm Management Live View. ________________________________________ Was tested with the following camera models: M1045-LW, M1054, M3045-V, M3065-V, P3227-LV.   1.3 Connectivity Outgoing connections usually are not blocked by a router, however in a corporate network with proxy server, firewall, etc. involved, the IT dept might open the needed ports. The following domains and ports are used for connectivity:   Notes: Proxy connection is only recommended for corporate managed networks in critical industry with restrictive outgoing firewall rules and without need for load-balancing video connections. Proxy connection is not recommended for large scale installations.   2. Add 3rd party ONVIF camera 2.1 Port forwarding   To add a 3rd party ONVIF camera to Bosch Alarm Management, port forwarding needs to be configured for each camera in the Internet router. The following ports need to be forwarded: HTTPS port (default 443) for communication optional HTTP port (default 80), if the camera does not support https RTSP port (default 554) for video streaming Note: To change the used ports from default, if requested by the customer, please refer to the camera’s manual. Example: Public IP = 62.225.116.122 Public domain: mydomain.com External HTTPS port to be used = 15000 External RTSP port to be used = 15001 Camera’s LAN address = 192.168.2.43 Camera’s HTTPS port = 443 (default) Camera’s RTSP port = 554 (default) Port forwarding with public IP address:     HTTPS: In the router, forward public 62.225.116.122:15000 -> to internal 192.168.2.43:443     RTSP: In the router, forward public 62.225.116.122:15001 -> to internal 192.168.2.43:554 Port forwarding with public domain:     HTTPS: In the router, forward public mydomain.com:15000 -> to internal 192.168.2.43:443     RTSP: In the router, forward public mydomain.com:15001 -> to internal 192.168.2.43:554 To configure port forwarding is individual per router manufacturer and model. Please refer to the router’s manual.   2.2 Add 3rd party ONVIF camera   Please perform the following steps: 1. Open Alarm Management Configuration, navigate to Accounts > Sites > Devices. 2. Add a 3rd party camera, select ONVIF (via Port Forwarding) 3. Enter device name, host (public IP address or domain), HTTPS and RTSP ports, and camera credentials (user name and password). Note: Some camera brands need to configure an ONVIF user to activate ONVIF communication. Please refer to the related camera manual. 4. Click Add. 5. Then configure Recording Mode and Cloud Storage. Note: Pre-alarm recording is not available for ONVIF cameras. Now your 3rd Party ONVIF camera is set and you should be able to see video from the camera in the Alarm Management Live View.   2.3 Alarm Management ONVIF compatibility   Basically all ONVIF Profile S and T compatible cameras can be connected to the VX Platform (see https://www.onvif.org/conformant-products/), supporting minimum: H.264 base or main profile G711 or AAC audio encoding ONVIF motion events in case of event recordings & alarms, when the camera supports the Real-time Pull-Point Notification Interface http and/or https A quick test in one of our demo cloud accounts on the compatibility for a certain camera model, firmware version specific configuration (stream, recording, local system, etc.) network router settings image quality and bandwidth needs gives results within minutes.    3. VX Video Control The HTML5 Video Control provides the following functionality for live video and playback.   Live mode details: 4: Enable Audio Verification from the camera and control the volume 5: Enable and confirm audio-back to perform Audio Intervention. Audio Intervention disabled:  Audio Intervention enabled: > allow audio-back:  9: Settings: Preferred format: o WebRTC: low delay (UDP) - for audio and PTZ control - might be not available in corporate network o HLS: bit-rate adaptive streaming (TCP) - no audio, no PTZ control o JPEG: JPEG polling   Dewarping o Off o On (e.g. for fisheye camera) 11: Display in-window PTZ control   Playback mode details: 1: Calendar: Days with recordings are displayed in a circle Click to select the date 4: Enable audio playback from the recordings and control the volume. 7: Select pre- and post alarm recording to be exported. 9: Settings: Speed: o Replay speed   ... View more

In Cloud-based Services, different 'Actions' can be configured for automatic processing as well as manual action for the operators (Alarm Agents). There are 2 different options how an action is processed: An 'Automatic Action' is processed automatically when the related Service Scenario is performed. An 'Intervention Action' is executed manually by an operator from the Cloud-based Service Operator Interface. This note shows available actions in Cloud-based Services and provides a step by step instruction to configure these actions.   Step-by-step guide   1. Send e-mail "Send e-mail" sends an e-mail notification to the configured recipient(s). The action can be used as manual action for the operators (Intervention Action). The content of the alarm email can be configured to the customer's needs.   To configure a "Send e-mail" action, perform the following steps: 1. Open Cloud-based Services Configuration website (/config), log in as Integrator or Config Agent. 2. Enter the related Account. 3. Click tab 'Actions'. 4. Click '+' button to add an action. 5. Give the action a descriptive name and select 'Email'. 6. Type recipients, CC's, mail subject and message. Use the pull down to enter environment variables to the e-mail text. 7. Click 'Create'. 8. Add the action to a Service Scenario for processing.   2. Execute PTZ Command   "Execute PTZ Command" starts an auxiliary command on a Pan-Tilt-Zoom (PTZ) camera. The action can be used for automatic processing (Automatic Action) as well as manual action for the operators (Intervention Action). Note the available auxiliary commands in the camera’s manual. To configure an "Execute PTZ Command" action, perform the following steps: 1. Open Cloud-based Services Configuration website (/config), log in as Integrator or Config Agent. 2. Enter the related Account. 3. Click tab 'Actions'. 4. Click '+' button to add an action. 5. Give the action a descriptive name and select 'Execute PTZ Command'. 6. Select PTZ camera, select auxiliary command and type the command No. 7. Click 'Create'. 8. Add the action to a Service Scenario for processing   3. Go to PTZ Preposition "Go to PTZ Preposition" moves a Pan-Tilt-Zoom (PTZ) camera to a preposition. The action can be used for automatic processing (Automatic Action) as well as manual action for the operators (Intervention Action). The prepositions (shots) need to be configured via the Device Page upfront. To configure a "Go to PTZ Preposition" action, perform the following steps: 1. Open Cloud-based Services Configuration website (/config), log in as Integrator or Config Agent. 2. Enter the related Account. 3. Click tab 'Actions'. 4. Click '+' button to add an action. 5. Give the action a descriptive name and select 'Go to PTZ preposition'. 6. Select PTZ camera and type the preposition No. 7. Click 'Create'. 8. Add the action to a Service Scenario for processing.   4. Play Audio on Device "Play Audio on Device" replays an audio file directly from the device's loudspeaker. The action is intended to perform standard audio interventions without the need for the operator (alarm agent) to talk. "Play Audio on Device" can be used for automatic processing (Automatic Action) as well as manual action for the operators (Intervention Action). Audio files need to be prepared and installed by CBS development. If you want to use your own audio files, please get in contact with technical support. To configure a "Play Audio on Device" action, perform the following steps: 1. Open Cloud-based Services Configuration website (/config), log in as Integrator or Config Agent. 2. Enter the related Account. 3. Click tab 'Actions'. 4. Click '+' button to add an Action. 5. Give the Action a descriptive name and select 'Play audio on device'. 6. Select the audio device and select the audio file. 7. Click 'Create'. 8. Add the action to a Service Scenario for processing.   5. Switch Relay "Switch Relay" switches a relay of one or more IP devices. The action can be used for automatic processing (Automatic Action) as well as manual action for the operators (Intervention Action). To configure a "Switch Relay" action, perform the following steps: 1. Open Cloud-based Services Configuration website (/config), log in as Integrator or Config Agent. 2. Enter the related Account 3. Click tab 'Actions'. 4. Click '+' button to add an action. 5. Give the action a descriptive name and select 'Relay'. 6. Select activation mode and select one or more relays to switch. 7. Click 'Create'. 8. Add the action to a Service Scenario for processing.   6. Notify Monitoring Center and Log Event Both action types "Notify Monitoring Center" and "Log Event" are obsolete and can not be used in a Service Scenario.  See also: How to add a user to Remote Alert service in Remote Portal? ... View more

Very often, it is easier to troubleshoot most Access Management System (AMS) problems when logging is enabled. By default, this option is disabled in AMS. These steps will detail how to enable logging for AMS.   Step-by-step guide    Log into the AMS server or client with administrative privileges 2     Click on the “Configuration” option 3     Next select the “Options” selection 4     Select the “Debug logfiles” option 5     Now check the “DMS, Terminal and MAC name” under the (Technicians) column. Leave the options under the (Support) column Unchecked unless specifically directed to. 6     In order for the logs to be available, the AMS server PC will need to be rebooted 7     After the AMS server is rebooted, reproduce the issue and it should now be listed in the log files for engineering to evaluate.    The log files are typically located in the C:\ProgramData\Bosch\Sicherheitssysteme\Access Management System\Logs ... View more