Brigade MDR 600 Series User manual

Network Connectivity SW&Infrastructure Manual 7035
Mobile Digital Recorder
MDR-641XX-X-XXX(XX)
MDR-644XX-X-XXX(XX)
MDR 600 Series Network Connectivity Software and Infrastructure Manual
(For Operators and Information Technology Professionals)
Please refer to www.brigade-electronics.com for most up-to-date data on all products

2
Table of Contents
1Introduction to MDR 600 Series Technology.........3
1.1Product Features......................................................3
2MDR Server Requirements and Installation ..........4
2.1MDR Server Requirements.......................................4
2.2MDR Server Installation............................................5
2.3MDR Server Configuration........................................8
2.3.1Port Configuration Tool ....................................8
2.3.2Server Control..................................................9
2.4Server Authorization...............................................11
2.5Hardware Communication Options.........................11
3MDR-Dashboard 6.0 Requirements & Installation
.............................................................................14
3.1MDR-Dashboard 6.0 Requirements........................14
3.2MDR-Dashboard 6.0 Installation.............................14
4Wi-Fi Configuration ..............................................16
4.1MDR Unit Configuration (Wi-Fi)..............................16
4.1.1Mobile Digital Recorder Requirements...........16
4.2MDR-Dashboard 6.0 Configuration (Wi-Fi).............17
4.2.1Logging into Server Mode (Wi-Fi) ..................18
4.2.2Connecting an MDR to MDR-Dashboard 6.0
(Wi-Fi) ............................................................19
5Mobile Network Configuration..............................20
5.1MDR Unit Configuration (Mobile Network)..............20
5.1.1Mobile Digital Recorder Requirements...........20
5.2MDR-Dashboard 6.0 Configuration (Mob. Net.)......22
5.2.1Logging into Server Mode (Mob. Net.)...........22
5.2.2Connecting an MDR to MDR-Dashboard 6.0
(Mobile Network)............................................23
6MDR-Dashboard 6.0 Operation ...........................25
6.1Vehicle State (Area 1).............................................25
6.2Type of operation (Area 2)......................................28
6.2.1Live View........................................................28
6.2.2Playback.........................................................29
6.2.3MDR Server ...................................................31
6.2.4Online MDR....................................................32
6.2.5HDD/SD and Local Files Playback.................33
6.2.5.1 Local Files Playback......................................33
6.2.5.2 HDD/SD Playback.........................................34
6.2.6Location Search .............................................37
6.2.7Evidence ........................................................39
6.2.7.1 Evidence Upload...........................................39
6.2.7.2 Evidence Centre............................................39
6.2.7.3 Browse Evidence...........................................40
6.3Message Centre (Area 3) .......................................42
6.4Fleet Status.............................................................42
6.5MDR Upgrade.........................................................43
6.6Fleet Statistics ........................................................44
6.7System Management..............................................46
6.7.1Home..............................................................46
6.7.2Fleet Management .........................................46
6.7.2.1 Quick Add .....................................................47
6.7.2.2 Fleet..............................................................47
6.7.2.3 Vehicle..........................................................47
6.7.2.4 User Role......................................................48
6.7.2.5 Driver File......................................................50
6.7.2.6 Batch upgrade equipment .............................51
6.7.3Live View (web)..............................................51
6.7.4Playback (web)...............................................53
6.7.5Evidence........................................................54
6.7.6Fleet Statistics................................................54
6.7.7System configuration (web)............................54
6.7.7.1 Map setting....................................................54
6.7.7.2 Units..............................................................55
6.7.7.3 Video setting..................................................55
6.7.7.4 Legend..........................................................55
6.7.7.5 Push Config...................................................55
6.7.7.6 SMTP service................................................56
6.7.7.7 Alarm linkage setting.....................................57
6.7.7.8 Alarm level setting.........................................57
6.7.7.9 Message Broadcast Setup.............................58
6.7.7.10 Authorization...........................................58
6.8Downloads and Alarm.............................................58
6.8.1Downloads .....................................................58
6.8.2Alarm Centre..................................................61
6.8.2.1 Alarm Search.................................................61
6.8.2.2 Alarm Settings...............................................61
6.9View Settings (Area 5)............................................62
6.9.1Map................................................................62
6.9.2Video..............................................................63
6.9.3Video/Map......................................................63
6.10 Real-Time Alarm Log (Area 6)..........................64
6.11 User and System settings (Area 4)...................64
7Mobile Apps.........................................................66
7.1iOS App..................................................................66
7.1.1iOS App Requirements ..................................66
7.1.2iOS App Push Certificate ...............................66
7.1.3iOS App Installation........................................66
7.1.4iOS App Operation.........................................67
7.2Android App............................................................69
7.2.1Android App Requirements............................69
7.2.2Android App Installation.................................70
7.2.3Android App Operation...................................70
8MDR Server 6.0 Advanced Features...................73
8.1Database Backup and Restore...............................73
8.1.1Database Backup...........................................73
8.1.2Database Restore..........................................74
8.2MDR Server Control ...............................................74
8.2.1Message Logs................................................75
8.2.2Video Monitoring Tool ....................................75
8.2.3License Tool...................................................76
8.3Evidence Migrate Tool............................................76
8.4Check Disk Tool .....................................................76
9Appendices..........................................................77
9.1Video Quality Table ................................................77
9.2Normal / Alarm Recording Parameters...................77
9.3Software Compatibility Matrix.................................77
9.4MDR-Dashboard 6.0 Silent Installation...................78
9.5Additional PowerShell Switches .............................78
10 Troubleshooting...................................................79
10.1 Mobile Network and Wi-Fi Troubleshooting ......79
10.2 Wi-Fi MDR Status Troubleshooting...................81
10.3 Mobile Network MDR Status Troubleshooting ..82
10.4 GPS MDR Status Troubleshooting ...................83
11 EU Declaration of Conformity ..............................84
12 Glossary...............................................................85
13 Disclaimer ............................................................86

3
1 Introduction to MDR 600 Series Technology
Brigade’s MDR-641 Series and MDR-644 Series are advanced Mobile Digital Recorders (MDRs) designed to record and playback 4+1 or 4+4
channels. The system uses Analog High Definition (AHD), Phase Alternating Line (PAL) or National Television System Committee (NTSC)
television systems. The resolution can be CIF, WCIF, HD1, WHD1, D1, WD1 or AHD (HD/720p or FULL HD/1080p). Information related to
recording parameters, alarms and trigger status can be recorded along with speed, location and G-Force data. In addition, data related to the
unit itself such as voltage and temperature are recorded and plotted graphically in MDR Software (MDR-Dashboard 6.0 and MDR-Player 6.0).
This information is called metadata.
Recordings can be searched, viewed and downloaded (clipped and saved locally) using MDR-Dashboard 6.0 software. This allows you to
access all the vehicle’s travel information, including route tracking. Recordings can be easily downloaded in three different ways: as a simple
audio/video MP4 file playable by consumer media players; as native proprietary format clips or as a password protected .exe file with an
embedded MDR-Player 6.0.
The main storage unit is a large capacity Hard Disk Drive (HDD) or Solid-State Drive (SSD). The secondary storage is an internal SD (Secure
Digital) card for sub-stream, HDD mirror (simultaneous) or alarm recording. The SD card stores video data and frame information only in chosen
image resolution and frame rate. This is useful in extreme scenarios where the primary storage media reaches its limitations (e.g. a HDD write
error during a collision). The SD card availability is model dependent.
Mobile network and Wi-Fi settings found in this manual relate to wireless products as described below. These features can be attained by
purchasing relevant MDR 600 Series units or upgrading standard MDR models with external 4G / Wi-Fi modules via rear panel Ethernet port.
To complete firmware upgrades, configuration imports/exports and video downloads, a USB bus-powered hub (minimum 2 ports) is required.
It is imperative that Brigade MDRs are fitted and commissioned by competent and trained technicians. The installers are responsible for the
correct setup of the overall system and must adhere to relevant regulations and legislation.
Warning:Prior to attempting this system setup, please ensure the MDR 600 Series Installation & Operation Guide is thoroughly read
and understood. Brigade will not be responsible for any failures due to incorrect installation or operation.
Ensure your anti-virus software has exclusions in place to allow the MDR software package to function properly.
Table 1: Software for MDR 600 Series Products:
WINDOWS PC SOFTWARE
MOBILE PHONE APPS
(1) MDR-Dashboard 6.0
(1) Brigade MDR 6.0 (Android)
(2) MDR-Player 6.0
(2) Brigade MDR 6.0 (iOS)
(3) MDR Server 6.0
1.1 Product Features
Table 2: Differences between MDR-641XX-X-XXX(XX) and MDR-644XX-X-XXX(XX).
MDR-641XX-X-XXX(XX)
MDR-644XX-X-XXX(XX)
500GB / 1TB / 2TB HDD or SSD with anti-vibration mounting (2TB
maximum)
500GB / 1TB / 2TB HDD or SSD with anti-vibration mounting (2TB
maximum)
SD Card not supported
Industrial grade 64GB (256GB maximum) internal SD card for
mirror, sub-stream and alarm recording
Simultaneous 5 channel recording up to
Analogue:
1080P @ 11fps (PAL) / (NTSC) for 4 channels
IP (direct connection only):
1080P @30fps for 1 channel
Simultaneous 8 channel recording up to:
Analogue:
1080P @ 11fps (PAL) / (NTSC) for 4 channels
IP (direct connection only):
1080P @30fps for 4 channels
IP (with direct connection and an extra 4-Port PON Switch)
1080P @ 30fps for 8 channels
5x Select video connectors typical to camera inputs with audio
8x Select video connectors typical to camera inputs with audio
Packed Weight: 2.9Kg
Packed Weight: 3.8Kg
Table 3: Features of MDR 600 Series
MDR 600 SERIES General Features
Internal anti-vibration mount for the HDD and embedded super-
capacitor for finalisation of recording after unexpected power
interruption (up to 10 seconds). Individual channel configurations for
recording resolution, frame rate and quality, display split 1/4/9 channels
and monitor margin adjustment
Pre-alarm recording 1-60 minutes and Post-alarm recording 0-1800
seconds. (0 to 30 minutes), Normal, Alarm or Timer recording modes
and flip vertical each channel, this will change live view (monitor) and
recorded data
Start-up time to recording is approximately 60 seconds (recommend
drivers to wait 3 minutes for recording to begin). Multiple LEDs for
diagnostic troubleshooting and flip doors for easy SIM/SD card access
Video quality selectable at 8 different quality levels for recording,
video/audio compression H.264/H.265 and operation log files for
troubleshooting and anti-tampering feature –using digital code
Operating temperature: -40˚C to +70˚C with SSD, -40˚C to +50˚C with
HDD. Built-in HDD heater heats up storage medium before start
recording. Threshold is 10°C
Alarm recordings configurable for trigger, speed, G-Force, video loss,
motion detection, blind detection, panic button, geo-fencing and SD
card/HDD errors
USB-A (2.0) interface on the Docking Station (DS) for downloads,
upgrades and configurations onto a USB flash drive (flash memory
only, maximum 16GB)
Low voltage protection with configurable shut-down delay minimum
restart voltage, ethernet. Mouse for configuration and recording/event
search and Shut-down delay configurable from 0 seconds to 24 hours
8.5-36V Power Input and I/O: 8x trigger input (trigger voltage 9V which
can be set to trigger at low/high); 2x trigger output (12V max. 200mA)
GPS for location monitoring and tracking with external antenna
MDR 641 SERIES Features
MDR 644 SERIES Features
5V Output max 1A load
12V Output max 1A load
10/100 6-pin VBV type connect able to transfer to RJ45 port via an
adapter cable. After transferred, it supports configuration, live view,
playback and video download via IE web browser
10/100 RJ45 port for configuration, live view, playback and video
download via IE web browser

4
Reading Mobile Caddy Unit (MCU) requires an ancillary MDR-MCU-R-
01 to transfer SATA connector to USB 3.0 which allows directly
connect to a Windows™ operating computer.
USB-B (3.0) interface on the Mobile Caddy Unit (MCU) for displaying
video recordings on a Windows™ operating system using MDR-
Dashboard 6.0
Built-in G-Sensor and 1x EIA/TIA 232 (RS232) for optional Remote
Status & Interface Panel to provide buzzer functionality (RS232 –
RS485 transfer is needed).
Built-in G-Sensor, Audible Buzzer and 1x EIA/TIA 485 (RS485) for
optional Remote Status & Interface Panel
2 MDR Server Requirements and Installation
MDR Server 6.0 is required software that runs on the Windows Server. This software enables an MDR unit to connect to the Windows Server.
MDR Server controls the assignment of ports and its functionalities.
Note: This software runs on a Yearly Licence and Authentication. When the Yearly Licence is nearing the expiration date (1st
Dec every year), please visit Brigade’s website (www.brigade-electronics.com)to download the new license file. This file needs to be
copied onto the Windows Server running MDR Server 6.0. Copy this file to the following path C:\Program Files (x86)\MDR
Server\TransmitServer and overwrite the existing version. For Authentication, please contact Brigade support to obtain
available auth file. Without an auth file, the server provides 1 month trial with 20 vehicle connectivity in maximum.
2.1 MDR Server Requirements
To use mobile network and Wi-Fi connectivity features, networking expertise are required for implementation. The mobile network server is
accessed by the MDR externally through a public IP (Internet Protocol) address. The Wi-Fi server is accessed by the MDR using a Wi-Fi
network. This setup requires all devices (Server, Client and MDR) to be connected to a shared network. Client refers to MDR-Dashboard 6.0 or
BRIGADE MDR 6.0 mobile apps. It is better for customers to use both network connectivity options to achieve different goals, live camera
capabilities of mobile networks and the low data cost of downloading video data over Wi-Fi.
Warning: If you have two separate MDR Server 6.0 software installations, video and metadata stored on each server is NOT linked.
Table 4: The minimum requirements below for MDR Server 6.0 with 1-10 MDR units
COMPONENT
MINIMUM REQUIREMENTS
CPU (Central Processing Unit)
Quad Core –2.2 GHz (Intel Xeon) or greater
RAM (Random Access Memory)
8GB or greater
Requested HDD space for software installation
10 GB required, 40 GB or more recommended (depending on the
number of MDRs connected at one instant and the features used). Each
MDR requires an additional 250MB of storage
Video
Super VGA or higher video card and monitor
Operating System
Windows Server 2012 R2 Standard or greater
Framework
Microsoft .Net Framework v3.5 SP1 version must be installed on both
server and client**
Wireless Adaptor
Wireless Access Point 802.11 b/g/n
**Client refers MDR-Dashboard 6.0 software
Table 5: The Recommended requirements below for MDR Server 6.0 with >10 MDR units <100
COMPONENT
RECOMMENDED REQUIREMENTS
CPU (Central Processing Unit)
8 Core/16 Threads or greater
RAM (Random Access Memory)
12GB
Requested HDD space for software installation
10 GB required, 150 GB or more recommended (depending on the
number of MDRs connected at one instant and the feature used)
Video
Super VGA or higher video card and monitor
Operating System
Windows Server 2012 R2 Standard 32\64bit
Framework
Microsoft .Net Framework v3.5 SP1 version must be installed on both
server and client**
Wireless Adaptor
Wireless Access Point 802.11 b/g/n
**Client refers MDR-Dashboard 6.0 software
Warning:The limitations to view several MDR video data feeds at one instant would be dependent on network speed, mobile network
coverage, Windows Server’s HDD (Hard Drive Disk) and RAM (Random Access Memory) capacity.

5
2.2 MDR Server Installation
Establish the IP address and MAC
address of the Windows Server.
➢IP address of Wi-Fi Server
➢IP address of Mobile Network
Server
Wi-Fi: Connect the router to the Wi-Fi
Windows Server with an ethernet cable
or Wi-Fi network.
Mobile Network: Contact the IT
department to setup port forwarding on
to the Windows Server as shown in
below:
Command Prompt Window Figure 1
Table 6: Port Forwards List and Services List
Port Forwards List
#
PORT NAME
PORT
NUMBER
(HTTP)
PORT
NUMBER
(HTTPS)
PORT FUNCTION (CLIENT REFERS TO MDR-
DASHBOARD 6.0 / BRIGADE MDR 6.0 APP)
CORRESPONDING
PROCESS
(1)
FileZilla Server
21;
3001~3100;
For FTP server, retrieve related configurations when
remote upgrade is used.
FileZilla server.exe
(2)
WCMS5REACT
3113
23113
For Evidence Centre playback
node.exe
(3)
Message Service
5556
MDR registration, will be used when uploading MDR to
server and issues commands from server
MessagerServer.exe
(4)
Client Balance
7264
Balance the load for clustering servers - (for future
clustering of servers) –specify this port when logging in –
creates initial connection. Has login authentication and
return IP address and ports to client.
ServiceProxy.exe
(5)
NgnixBroker
8081
28081
Reverse proxy (solve security issues raised by
customers); Read metadata from MongoDB; Invoke page
action via web services, such as evidence centre, ADS
etc.,
NgnixBroker.exe
12040
22040
12055
22055
(6)
Client Access Service
12020
Transfer request from client and return message
(online/offline status, real-time GPS and others) from
server
ClientAccessService.exe
(7)
Server playback service
12045
For server playback function
ServiceSTPlay.exe
(8)
HttpSdkService
12047
22047
Https SDK
HttpSdkService.exe
(9)
EvidenceStoreService
12048
File storage service, N9M2.0 (Gen 2) evidence data,
N9M2.0 (Gen 2) remote setting web resources
EvidenceStoreService.ex
e
(10)
Proxy Server (Remote
Setting) Client Data
12050
22050
For the remote config (within MDR-Dashboard 6.0)
feature –from Server to Client
HttpProxyServerNP.exe
(11)
Proxy Server (Remote
Setting) Device Data
12051
For the remote config (within MDR-Dashboard 6.0)
feature –from MDR to Server
HttpProxyServerNP.exe
(12)
WCMS5
12056
22056
For supporting web service.
node.exe
(13)
Media Server
8090
28090
For the live view function on the web client.
media_service.exe
12060
22060
12061
22061
12062
22062
12063
22063
(14)
Evidence Service
12065
Upload evidence from MDR, handle evidence, and any
other feature related to evidence centre.
EvidenceService.exe
(15)
MDR4 Streaming Media
Server
12091
Video streaming data transmission for MDR 400 Series.
To retrieve video streaming from MDR and dispatch to
client after receiving the live view request from client.
DVRGTService.exe
(16)
MDR5 Streaming Media
Server
12092
Video streaming data transmission for MDR 500 Series.
To retrieve video streaming from MDR and dispatch to
client after receiving the live view request from client.
DVRGTService.exe
(17)
Transmit Server
17891
Video streaming data transmission for Clients. To retrieve
video streaming from MDR and dispatch to client after
receiving the live view request from client.
DVRGTService.exe
Additional Services List (Does not require Port Forwarding)
(1)
MySql5.5
3307
To store basic data
MySql5.5.exe
(2)
Client Access Service
9528
Transfer request from client and return message
(online/offline status, real-time GPS and others) from
server
ClientAccessService.exe
(3)
AdsServer
7857~7861
For auto-download function.
ADSServer.exe
(4)
DVRGTService
10001
Video streaming data transmission. To retrieve video
streaming from MDR and dispatch to client after receiving
the live view request from client.
DVRGTService.exe
(5)
CenterManageService
12000
For internal process message management
ServiceDAMgr.exe
12003
(6)
Redis Service
12004
Cache online status, GPS, alarm and other data
redis-server.exe
(7)
Message Service
12012
Alarms push from MessageService to AlarmService
MessagerServer.exe
(8)
OnlineServer
12035
For online statistics service. Collect MDR online
information.
ServiceOLStatistivs.exe
(9)
ARMSRestServer
12044
Read black box data from MonggoDB
ARMS.RestServer.exe
(10)
BaseDataServer
12046
java basic data query
BaseDataServer.exe

6
(11)
FileManagementService
12049
File storage service, and determine file storage path
FileManagementService.
exe
(12)
Apache2.2
12054
Invoke page action via web services, such as evidence
centre, ADS etc.,
httpd.exe
(13)
Alarm Service
12125
Push real-time alarm and GPS to ClientAccessService
AlarmService.exe
(14)
media_service
12198~12203
For the preview function on the web side
media_service.exe
(15)
FileZilla Server
14147
For FTP server, retrieve related configurations when
remote upgrade is used.
FileZilla server.exe
(16)
N/A
20000
For MDR server control tool
DVRServerCtrl.exe
(17)
Monggodb
27017
To store user's old meta data
mongod.exe
(18)
Monggodb_3.2
27018
To store metadata
mongod.exe
(19)
WCMSRunning
54321
For devices upgrade
WCMS.Running.exe
(20)
HttpSdkService
65531
Https SDK
HttpSdkService.exe
(21)
ARMStorageServer
N/A
For parsing meta data and writing into MongoDB.
ARMS.StorageServer.exe
(22)
DVRRTService
N/A
MDR-Dashboard guard service. To switch on/off services,
and reboot services automatically after suspension.
DVRRTService.exe
(23)
PushService
N/A
For APP alarm push function
PushService.exe
(24)
CmdServer
N/A
Panic Button alarm configuration strategy command
issuance, and configuration is obtained from the database
regularly and issuance
CmdServer.exe
(25)
CommandDispatch
N/A
Instruct issued service
CommandDispatch.exe
(26)
EvidenceCmdServer
(EvidenceReportService)
N/A
Strategy service, N9M2.0 evidence upload
EvidenceReportService.e
xe
(27)
EvidenceAnalyService
N/A
Evidence analysis service, transcoding evidence video
data, generating relevant evidence files
EvidenceAnalyService.ex
e
(28)
TaskPlanService
N/A
Scheduled task service, regularly delete evidence black
box, video data
TaskPlanService.exe
(29)
WCMSWebCenterService
N/A
For remote upgrade function and upload MDR
automatically
WCMS.Server.WindowsS
ervice.exe
Note: Ports differs depend on choosing HTTPS method or not.
Wi-Fi: An example of a router page is shown in Wireless Router Settings
Figure 2. The router login page is accessed using the factory settings. You
may find the router IP, username and password underneath the router,
alternatively contact the manufacturer. Once logged into the router, setup the
wireless network. MDR units are compatible with WPA/WPA2-PSK,
WPA2_Enterprise or WEP encryption.
Wi-Fi: Wireless Router Settings Figure 2 shows an example of a wireless
network created. The SSID (Service Set Identifier) is MDRServer and
WPA-PSK security has been used. When entering the SSID into the MDR
unit, this is case sensitive. It is advised to create SSIDs without spaces to
avoid any typing errors on the MDR.
Wi-Fi: When using an access point no port forwarding is required on a basic
network. If you want to access the Wi-Fi server remotely you will need to port
forward to the Wi-Fi MDR Server from your firewall (a static public IP address
is required).
Mobile Network: The Windows Server should have a static public IP
address. The IP address is 192.168.14.193 (in this example). This can be
permanently assigned using the server’s MAC address.
It is recommended to use a newly built or clean Windows Server.
Wireless Router Settings Figure 2
Warning:If this device is used to host other software that uses SQL, we
do not recommend installing MDR Server 6.0 on the same Windows
Server.
MDR Server Icon Figure 3
Before starting the MDR Server installation, ensure Microsoft .Net Framework
v3.5 SP1 is installed on your Windows Server.
Right-click the installation file found in MDR Server Icon Figure 3 and RUN
AS ADMINISTRATOR. You may be prompted to back up any data if they
have previously installed MDR Server software on this Windows Server.
Choose the language for the software, as shown in MDR Server Language
Setup Figure 4. Give the software a few minutes to prepare the setup.
Warning:The same language used for the server software install must
be used for the client software.
The installation window as shown in MDR Server Installation Figure 5 will be
displayed. Click NEXT to begin the installation.
By default, the MDR Server will be installed in C:\Program Files (x86)\MDR
Server 6.0 path, and cannot be customised.
MDR Server Language Setup Figure 4

7
MDR Server Installation Figure 5
MDR Server Declaration Figure 6
The next step is to select the MDR Server features. MDR Server Install Folder
Setup Figure 8 shows the services that are available. Please ensure that ALL
services are ticked to be installed.
Click INSTALL to start the installation. Close other software during this
process.
MDR Server Install Mode Figure 7
MDR Server Install Folder Setup Figure 8
The setup status is displayed on screen. See MDR Server Setup Status
Figure 10. You will see various services being installed; this period is
dependent on your server configuration. In general, allow approximately 15
minutes for your MDR Server installation.
Click FINISH to complete the final step of the installation. See MDR Server
Install Completion Figure 9.
MDR Server Install Completion Figure 9
MDR Server Setup Status Figure 10

8
2.3 MDR Server Configuration
2.3.1 Port Configuration Tool
After installing MDR Server, the port
configuration tool will be automatically opened,
which is used mainly to manage an MDR
Server’s ports and IP address.
Do not change the default ports. If you have
already used these ports on your network,
please assign different ports in your other
software.
Warning: Streaming Media Server IP MUST
be a STATIC PUBLIC IP address
of the Mobile Network Server
(Firewall in some cases).
HTTPS method can be enabled by ticking the
option “Use Https”. HTTPS requires ports
change, please refer to above port forward and
service table.
Note: Brigade does not provide HTTPS
certificate, which must be applied by individual
user because it is bounded to dedicated server
domain names.
After obtain HTTPS certificate, rename Keys
following rules below:
Public key of SSL certificate: certificate.pem
private key of SSL certificate: privatekey.pem
Put both keys to folder: C:\Program Files
(x86)\MDR Server\ngnix\keys.
Then restart the WCMS5 Service to make it
effective.
Speed and temperature units can also
be changed within this tool.
Brigade recommends to not change any of
these ports unless these ports are already
being used by another software.
GPS data that is uploaded to the server can
be retained for a defined period.
Video data including Evidence upload and
Auto-Download records can be retained for a
defined period, range from 0 ~ 1000 (days). If
exceed the time setting, the oldest records will
be erased automatically. Put 0 means records
will be saved for unlimited time.
Port Configuration Tool Figure 11
HTTPS Keys Figure 12

9
2.3.2 Server Control
After installing MDR Server, the
Server Control program usually
automatically start running, if not,
go to the MDR SERVER folder
as shown in MDR Server Menu
Figure 13.
To access the MDR Server
Control window, you can click on
MDR Server Control or right-
click the MDR Server icon. As
shown in Displaying MDR Server
Control Figure 16.
Now, click the OPEN/HIDE
WINDOW option as shown in
Accessing MDR Server Control
Window Figure 14.
If the software is not open, ensure
it is RUN AS
ADMINISTRATOR as shown
in MDR Server Control Menu
Figure 19.
Use the following steps to ensure
MDR Server always runs as
administrator.
➢Right-click MDR Server
(MDR Server Right click
menu Figure 15) then click
Properties.
➢Go to the Compatibility
tab, under Privilege
Level, tick Run this
program as
administrator. See
Privilege Level Figure 17.
Click Apply to ensure all
changes are saved.
MDR Server Menu Figure 13
Accessing MDR Server Control Window Figure 14
MDR Server Right click menu Figure 15
Displaying MDR Server Control
Figure 16
Privilege Level Figure 17
Once the window opens as shown in MDR Server Control
Window Figure 18, click CONFIGURE then CONFIGURE
MESSAGE SERVER.
The window shown in MDR Server Message Server
Configuration Figure 20 will be displayed. The following
configuration is used:
➢Server IP: 127.0.0.1 (loopback IP address of server)
➢Server Port: 5556
MDR Server Control Window Figure 18
MDR Server Control Menu Figure 19
Note: If not all MDR Server services are running (MDR Server
Control Window Figure 18). There are a few steps to
attempt to fix this issue:
➢Exit the MDR Server control window and run the
application as administrator. See MDR Server Control
Menu Figure 19.
➢Ensure that the MDR Server installation is not expired
–check Brigade website for the latest license files.
➢Install the Microsoft .NET Framework 3.5.
MDR Server Message Server Configuration Figure 20

10
➢Check the MDR Server IP in MDR Server Message
Server Configuration Figure 20. Click SAVE on the
configuration of the Message Server window.
➢Restart the Windows Server.
➢If none of the above steps work, reinstall the software.
A brief description of the select MDR Server Control service is shown in the table below.
(1) Server Control: manages all services. It can restart
automatically everyday (setting).
(2) Message Service: creates TCP connection from server to MDR.
Manages client software login states and registers MDR states.
Transports commands from server to MDR and writes GPS/alarm
data into mongodb using MDR5 protocol.
(3) Transmit Service: forwards media data from MDR to client
software using transmit port.
(4) WCMSWebCenterService: supports MDR-Dashboard 6.0 remote
firmware batch upgrades.
(5) Apache: Invoke page action via web services, such as
evidence centre, ADS etc.,
(6) Mongodb: Mongo Database service, for storing GPS, alarm data
and metadata from MDR 500 (MYSQL used for MDR 400).
(7) Mongodb_3.2: To store black box data
(8) ADS: Auto Download System is used to avoid too many MDR-
Dashboard 6.0 connections to one Windows Server.
(9) ClientBalance: If there are more than 1 MDR Server
installations on different servers, it keeps MDR Server in
balance by assigning which clients connect to which server
(10) n9m_proxy: Works as a proxy server to set MDR parameters
remotely.
(11) ARMSStorageSever: Stores metadata (from auto download
function) into mongodb.
(12) ARMSRestServer: Analyses metadata file path (from auto
downloads) in MYSQL database.
(13) ServiceSTPlay: For MDR-Dashboard 6.0 remote playback
server data.
(14) AlarmService: For alarm service program, used internally.
(15) CommandDispatch: For transmit command
(16) ClientAccessService: For sending MDR online/offline messages to
clients. For MDR-Dashboard 6.0 to receive MDR online/offline
messages. For transporting orders from MDR-Dashboard 6.0 to
MDR.
(17) Redis Service: Buffers MDR online/offline information for
mobile app queries.
(18) PushService: For pushing alarms to mobile apps.
(19) OnlineServer: Manages MDR online/offline messages and
updates clients with this information.
(20) CmdServer: commands sent to MDR Server.
(21) WCMSRunningService: For supporting MDR-Dashboard 6.0
remote firmware batch upgrades. Adds vehicles automatically
to MDR-Dashboard 6.0.
(22) CenterManageService: For updating center data to related MDR-
Dashboard 6.0.
(23) HttpSdkService: For enable web interface access
(24) EvidenceAnalyService: For analyse and create evidence items.
(25) FTPServer: Works as FTP server for saving data (video,
snapshots, firmware etc.).
(26) WCMS5: For supporting web client.
(27) WCMS5REACT: For supporting web evidence centre
playback features
(28) Mysql: Database for storing basic data such as vehicle and fleet
information.
(29) EvidenceRcvServer: Receiving and transmitting Evidence
files from server
(30) ServiceSTMgr: Save live view footage to server.
(31) ServiceSTWorker: Execute saving liveview to server folder.
(32) rm_media_service: For web client liveview and playback.
(33) EvidenceCmdServer: For managing evidence item uploading.
(34) EvidenceStoreService: For saving evidence item and data.
(35) FileManagementService: For managing different file save to
different paths.
(36) TaskPlanService: Support delete GPS data and video data on
time.
(37) NginxBroker: Reverse proxy for web functionality
(38) BasedataServer: Basic data inquiry (Java)
Double-click on MESSAGE SERVICE as shown in MDR Server
Control Window Figure 18. This will open another window which
shows the current state of the network. See MDR Server Message
Logs View Figure 22.
In MDR Server Message Logs View Figure 22, the IP addresses
of the connected clients are shown in the left column. This
includes the server loopback address. If an MDR has been
configured correctly it will appear online in the right column.
Note: IP addresses are assigned dynamically by the mobile
network. In addition, the MDR toggles the mobile network
periodically if no activity is detected.
MDR Server has a prompt message that will appear on the
Windows Server to inform the system administrator that the MDR
Server is nearing its expiration date. See MDR Server Expiry
Prompt Figure 21.
The system administrator will need to download a new 1-year
license file from Brigade’s website. Copy this file to the following
path C:\Program Files (x86)\MDR
Server\TransmitServer. It will overwrite the existing license
file.
MDR Server Expiry Prompt Figure 21
MDR Server Message Logs View Figure 22