Skip to main content

Milestone

Daniel Crosby
Updated
 

Information

  • Manufacturer: Milestone (+44 (0) 1332 8693803)
  • Product:Milestone Native
  • Type:Video Management Software

Supported Features

Milestone Version Features
GetConfig (Standard) GetConfig Alarms GetConfig Associated Cameras Live Playback PTZ Presets

Multi-

View

 Audio Transmit Relays Alarms Post Alm Rec Ecare
XProtect Advanced VMS
Expert 2017 ✔ ✔  X ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔  ✔  ✔ 
2018 ✔ ✔ X ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔
Corporate 2013 ✔ X X ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔
2014 ✔ X X ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔
2016 ✔ X X  ✔  ✔  ✔ ✔ ✔  ✔  ✔  ✔  ✔  ✔
2017 ✔ X X  ✔  ✔  ✔ ✔ ✔  ✔  ✔  ✔  ✔  ✔
XProtect Professional VMS
Go Not Supported
Essential Not Supported
Express Not Supported
Express + This has not undergone the Sureview integration QA and certification process, however manufacturer states this system is compatible
Professional 2013 ✔ ✔ X ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔
2014 ✔ ✔ X ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔
2016 ✔ ✔ X ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔  ✔
2018 (R1) ✔ ✔ X ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔
2018 (R2) ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔
2018 (R3) ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔
+ This has not undergone the Sureview integration QA and certification process, however manufacturer states this system is compatible
Enterprise 2013 ✔ ✔ X ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔
2014 ✔ ✔ X ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔
2016 ✔ ✔ X ✔  ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ 

 

Milestone Husky NVR
Husky M10 Not Supported
Husky M20 This has not undergone the Sureview integration QA and certification process, however manufacturer states this system is compatible
Husky M30 This has not undergone the Sureview integration QA and certification process, however manufacturer states this system is compatible
Husky M50 This has not undergone the Sureview integration QA and certification process, however manufacturer states this system is compatible
Husky M500 This has not undergone the Sureview integration QA and certification process, however manufacturer states this system is compatible
Husky M550 This has not undergone the Sureview integration QA and certification process, however manufacturer states this system is compatible

Components and Communication

Component Location Outgoing communication Incoming communication
Milestone Router Service Milestone Server 443 TCP to Receiver Service 443 TCP from Device Plugin
Milestone Receiver Service Sureview Device Server N/A 443 TCP from Router Service
Milestone Device Plugin Sureview Device Server 443 TCP to Router Service N/A
Sureview Server Milestone Server 80 TCP (HTTP)
443 TCP (HTTPS)		 For video connections between Sureview and the Milestone software
Sureview Server Milestone Server 1237 TCP For alarm connections between Sureview and the Milestone software
Sureview Server Milestone Server 7563 TCP Data Transmission Port
Sureview Server Milestone Server (Corporate) 22331 TCP For alarm connections between Sureview and the Milestone Corporate software

External Configuration

The following are the steps required to configured this system to work with the Sureview.

Before you begin

Before you configure your Milestone system to work with Sureview make sure you have the following:

  • A fully licensed Milestone server.
  • An Sureview server running Device Server Service v1.1.0.6.
  • An Sureview server running Sureview Web v1.28.3.47 or newer.
  • Continuous Camera Recording.
  • You must be able to load the XML page (it must contain data & not be blank)
    http(s)://host:port/rcserver/systeminfo.xml
    e.g.: http://192.168.1.12/rcserver/systeminfo.xml

Milestone Continuous Camera Recording

Navigate to the camera to record 'Devices -> Camera 1 (camera name)'. Select the record tab and ensure that the "Recording" checkbox is selected:

mceclip0.png

Milestone Alarms

Please note that all alarms received from the Milestone Enterprise are in UTC format. The means that the Device Time that appears in Sureview (in the event details) will be UTC.

Milestone Enterprise Alarms

Go to 'Events and Output' -> Go to Hardware lnput Events -> Right Click and Select 'Add New Input Event'
mceclip1.png
 
From here Select the Hardware device you wish to alarm with, and select the event to trigger the alarm:
mceclip2.png
 
To setup the area for 'Motion Detection Alarms' -> Right click on 'Camera' -> Navigate to 'Camera Properties' -> Click on 'Motion Detection'. Within the motion detection window the sensitivity and detection zones for triggering alarms can be modified. Adjust these settings as required and click 'Ok'.
3.jpg

After making all the changes, click on the below button (which is on the top left corner) to save and apply all the changes (or close the client application to save and apply changes).
mceclip3.png
 

Milestone Corporate External Alarms

 Go to 'Rules and Events' -> Right click on 'Events' -> Click 'Add User-defined Event...'
mceclip4.png
 
Enter a name for your event.
 Alarm2.png
 
Go to 'Alarms' -> 'Alarm Definitions' -> Right click 'Alarm Definitions' -> Click 'Add New ...'
Alarm3.png
 
You will then be able be given numerous options to configure your alarm. Start with giving your new alarm a name.
 Alarm4.png
 
You can then choose the triggering event which will activate this alarm. This can link to multiple events. To to this start by selecting "External Events" in the drop down menu. You can then select the event which you just created in the previous steps.
 RelatedCameraImage.png
 
You can then add a related camera which will link to all of the source events. If the Milestone server is running Milestone Corporate 2018 r2 or higher then these cameras will be associated with their alarms within Sureview.
 
Once you have finished configuring the alarm, click the save button located within the toolbar.
 
 

Sureview Configuration

The following are the steps required to configured this integration in the Sureview interface.

Before you begin

Before you configure Sureview to work with Milestone make sure you have the following:

  • Open ports on your Sureview server
  • Username and password of your Milestone account
  • Playback requires continuous recording to be setup on the Milestone device.
  • If using Basic Authentication you must enter authmode=basic; into the Authentication and Cameras field prior to Get Config
  • Basic Authentication must use a HTTPS connection (port 443 by default)

Details for the following are listed below.

Device Setup - GetConfig

Field Value
Host The external IP address of the device provided by the installer
Port The web port for the Milestone software. (Default 80)
Username Your Milestone username (See image below)
Password Your Milestone password (See image below)
Authentication and Cameras Any configuration parameters you wish to include. (See parameters section for more detail)

 

BasicAuthImage.png

The image above shows the login page for the Milestone management client, you must use the same credentials in Sureview as you would use here.

mceclip0.png

 

Site Syncing

Site Syncing will allow for Sureview to automatically get the configuration from your Milestone server and add it into Sureview.

Go to Sync Setup, Sync Systems, Add the Sync System. Adding the device is the same as mentioned in device setup.

mceclip1.png

Title

Name of your sync system

Device Type

The type of Milestone Server you would like to sync.

IP/Host

The external address of the server.

Port

The web port for the Milestone software. (Default 80)

Username

 Your Milestone username.

Password

 Your Milestone password.

Authentication & Cameras

 The authentication mode will need set here (See parameters section for more detail).

Once the device has been added to Site Syncing you will need to Go to Setup, Edit Sites, Device, Location, Edit Details, Site Syncing, Add Sync Settings. In the Identifier field enter the details based on what you want to sync. Parameters can be found below. 

mceclip2.png

 Extra Value / Parameters / Authentication & Cameras

Extra value text is used to provide parameter suggestions for notification sending notification through site monitor and creating notification templates. Parameters are then used as flags to enable or disabled functionality when sending a notification.

The extra value parameters supported by Sureview are displayed in the table below.

Parameter

Extra Value Text

Example
Engine Name Syncing/GetConfig

Engine=(Engine Name);

Engine=North Building;
Device Prefix Syncing/GetConfig

Prefix=(Device Name Prefix);

 Prefix=North;
Device Group Syncing/GetConfig DeviceGroup=(Device Group Name);

DeviceGroup=Group1;

DeviceGroups=Group1,Group2,Group3;

Alarm Prefix Syncing/ GetConfig

AlarmPrefix=(Alarm Name Prefix)

AlarmPrefix=Alarm;

AlarmPrefix=Alarm Number *;
Use Camera Host

UseCameraHost=(true/false)

UseCameraHost=false;
Authentication Mode

AuthMode=(Authentication Mode)

AuthMode=Windows;

AuthMode=Basic;

 

Engine Name Syncing/GetConfig
Description Milestone engines can be synced using their name as found in Milestone. Multiple engines are NOT currently supported. Engines can be found in Milestone as “Recording Servers”.
Instructions (Get Config)

Find the recording server within Milestone that you would like to import and simply use its name with this option within the Server ExtraValue.
Instructions (Sync) Find the recording server within Milestone that you would like to sync and simply use its name with this option within the SyncIdentifier.
Example Engine=SureviewDEVUK;

EngineNameImage.png

 

Device Prefix Syncing/GetConfig
Description

Sureview allows you to sync all devices across all engines with a specific prefix name.
Instructions (Get Config) Enter the prefix of the device name which you would like to import. This will import all devices which contain given prefix in every engine on the Server.
Instructions (Sync) Enter the prefix of the device name which you would like to sync. This will sync across all engines which contain devices with the given prefix.
Example Prefix=DET;

 

Device Group Syncing/GetConfig
Description Sureview can sync from the Device Group from within Milestone. Device groups can be found in Milestone under “Devices”. The image below shows the camera device groups.
Instructions (Get Config) Sureview can sync on one or multiple Device Groups. Multiple device groups can be imported by comma separating them in the Server ExtraValue. If you import a parent device group all sub device groups will be synced also.
Instructions (Sync) Sureview can sync on one or multiple Device Groups. Multiple device groups can be synced by comma separating them in the SyncIdentifier. If you sync on a parent device group all sub device groups will be synced also.
Example

DeviceGroup=Axis;

DeviceGroups=Chickens,Axis,Foxes;

DeviceGroupImage.png

Alarm Prefix Syncing/GetConfig
Description It is possible to sync the events within Milestone, this will attempt to match the prefix value to any Milestone Event names. An example of where these can be found is shown in the image below.
Instructions (Get Config)

Enter the prefix of which you would like to import into the Server ExtraValue. You can use the wildcard character (*) in here to bypass any unknown characters.

If no AlarmPrefix is entered into the extra value then no external events will be added to Sureview.
Instructions (Sync)

Enter the prefix of which you would like to sync into the SyncIdentifier. You can use the wildcard character (*) in here to bypass any unknown characters

If no AlarmPrefix is entered into the sync identifier then no external events will be added to Sureview.
Example

AlarmPrefix=Tom;

AlarmPrefix=Arran * cam;

AlarmPrefix=*;

 

Note: Milestone events will not trigger in Sureview if they are not assigned to an alarm in Milestone. You can achieve this by following this guide.

EventsImage.png

 

Receiver Service

The Milestone Native integration uses a dedicated service to receive alarms from Milestone servers. The service needed for alarm support is the Milestone Native Receiver. The receiver service uses (by default) TCP ports 1237(Professional/Enterprise) and 22331(Corporate) to maintain a constant connection to the server, this allows the service to receive alarms from milestone as they are raised.

Alarm Auto-Acknowledge

There is an option to disable alarm auto-acknowledgement within the alarm receiver. This will stop the receiver from automatically taking the alarm from the Milestone XProtect smart client and allows you to manage the alarms from there. This is configurable in the Milestone native receiver config file.

AutoAckImage.png

Milestone Receiver Health Check

The milestone native receiver supports health checks via a web interface. Navigating to the page in a browser will allow the user to observe what milestone connections are currently running and if any issues have occurred in them. To navigate to the page, simply open a browser and enter the ip address of your Sureview server plus the web interface port (by default 18089). This web interface port can be altered in the Milestone native receiver config file:
 
 AvigilonWebPort.png
 
 
Navigating to the interfaces page (SureviewServerIP:18089) shows the following page:
HealthCheckImage.png
 
 The image above is of servers that are successfully connected. 
 
Selected any of the servers (simply select the row) will show the following dialog. This dialog contains the latest messages received from the service along with the time of the message and the last successful heartbeat.
 
 conntectdialogmilestone.png
 
Below is how the interface and dialog appears if a connection is lost:
disconnectedMilestone.png
 
You may need to add a URL ACL for the port under the Service account - See Service Account Domain User
 

Troubleshooting

Milestone can GetConfig but not connect to live

It is possible to setup cameras in the Milestone software without a associated NAT address, because of this the situation can occur where the cameras hostname is local and therefore inaccessible from an external/different server. To resolve the you can set Sureview to connect to the cameras based on the servers ip address rather than the cameras hostname.

To invoke this setting simply add the following to the Authentication and Cameras field of the device:

UseCameraHost=false;

If you are running multiple Milestone servers you may need to open the web port between these servers. By Default this is port 80

Relay On/Off is not working

The milestone native integration only supports relay pulse. If the Sureview device you are using is setup to use on|off functionality you can switch it to pulse in the sites setup.

Milestone Enterprise and Professional Relays are not working correctly

Outputs (relays) in the milestone software have to be referenced to the hardware device/camera they belong to. Ensuring the output refers to the correct camera can be done as follows:

With a hardware device added.

Right click hardware output (in events and output) and select add new output:

one_.png

If your desired output is already in the list, ensure that it is under the correct device (highlighted in blue - This shows output 1 belongs to hardware device 1). If you require a new output, select the device you wish to use a output on and select Add (highlighted in red):

 two.png

 Right click the camera of the hardware device (in this example, hardware device 1) and select properties:

three.png

 From the properties menu select Output. Ensure that the output is associated with the camera (Highlighted in blue). Ensure that the output device is also contained in the manual activation section (highlighted in red).

four.png

 

Milestone will not connect for Alarms

It is possible for the Milestone device to not allow connection for alarm receiving. This can be seen in the health check interface mentioned above. A site in this state will constantly say "Connecting"

The cause of this is that Central has not been enabled inside Milestone.

To enable this log into the Milestone Management Application and Select Advanced Configuration>Central

Tick Enable Central

Central_Tick.png

 

I am getting alarms like: Lost connection to device - ********** lost alarm connection.

If you are seeing this error followed by a reconnected message constantly, this usually indicates that the Milestone Event Server's Hard Disk space is either full or almost full

Cannot sync to Milestone

If you cannot sync to Milestone, or it syncs infinitely, it may be caused by the presence of a Professional slave server on the site. Should this be down, the systeminfo.xml may not be operational

Triggered events are not showing in Sureview

If you cannot see your triggered event within Sureview it maybe because it is not assigned as a source to a alarm on the Milestone server. There is a guide to do this can be found here.

 

Sync and Getconfig is missing cameras

Try manually deleting the cached "SystemInfo" xml files to force a refresh. To do this go to the ImmixCloud\Devices\MilestoneNative folder and delete all the "SystemInfo.xml" files (there will be multiple and they will have guids in the filename)

Live Cameras Not Working

Action 'DeviceConnect()' took too long

Check the systeminfo.xml file from the device servers
http(s)://host:port/rcserver/systeminfo.xml

If the xml is taking longer to load than the device timeout it can cause a timeout error and the camera's won't load.   Download the file manually and add it to the Milestone Device folder on all device tier servers.

If the xml file doesn't load at all Sureview won't be able to connect to the cameras (see the "Before you begin" section) - This is a key pre-requisite. 

Related articles

Comments

0 comments

Please sign in to leave a comment.