Difference between revisions of "Milestone XProtect - Professional and Enterprise"
From Zenitel Wiki
| (47 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ | + | {{AI}} |
| + | {{obsolete}} | ||
| + | For integration with Milestone, please see: | ||
| + | * [[Milestone XProtect - ICX-AlphaCom Integration]] | ||
| + | * [[Milestone XProtect - IC-Edge Integration]] | ||
| − | The integration of | + | ---- |
| + | |||
| + | The integration of ICX/AlphaCom with Milestone XProtect software enables video stream routing under control of commands issued by ICX/AlphaCom. The interface uses the standard matrix functionality which is part of Milestone XProtect VMS. This article describes how to integrate the ICX/AlphaCom with the [http://www.milestonesys.com/ Milestone] XProtect Professional and Enterprise 2014 (8.6c) version.<br> | ||
Integration with the [[Milestone XProtect - Expert and Corporate|Expert and Corporate versions]] of XProtect is described in a separate article. | Integration with the [[Milestone XProtect - Expert and Corporate|Expert and Corporate versions]] of XProtect is described in a separate article. | ||
| − | [[Image:Milestone config example.png|thumb|400px|AlphaCom and Milestone integration]] | + | [[Image:Milestone config example.png|thumb|400px|ICX/AlphaCom and Milestone integration]] |
==Features== | ==Features== | ||
The integration allows cameras to be connected to monitors on call and call request events, including changes to the viewed camera when the guard scrolls through the call request queue on the intercom station. | The integration allows cameras to be connected to monitors on call and call request events, including changes to the viewed camera when the guard scrolls through the call request queue on the intercom station. | ||
| + | When a master station receives [[Call Request]] from a substation, and when a call is made to the substation, action strings are sent from the ICX/AlphaCom to the Milestone system using the [[EDO|EDO port]]. Using the [[Event Handler]], a few simple events allows control of cameras located in association with a substation. When scrolling the call queue, commands related to the selected station is transmitted, allowing the video on the monitor to follow the queue navigation on the master station. | ||
| − | + | If any new call requests are received while in conversation, this will not influence on the active image. When the conversation is cancelled, and there are still calls in the queue, the image associated to the first station in queue will be displayed. | |
| − | + | ==Licenses == | |
| − | + | * When used with the ICX System, the following license is required in the ICX in order to enable the EDO port: 1002602400 - ILI-IF Interface enabling | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Default TCP port usage == | == Default TCP port usage == | ||
| − | * TCP port 1234: Between AlphaCom and the Milestone XProtect Server | + | * TCP port 1234: Between ICX/AlphaCom and the Milestone XProtect Server |
* TCP port 80: Between the Server and the Smart Client | * TCP port 80: Between the Server and the Smart Client | ||
* TCP port 12345: Used for transferring Matrix-triggered images from the Server to the Smart Client view | * TCP port 12345: Used for transferring Matrix-triggered images from the Server to the Smart Client view | ||
[[Image:Milestone config example 2.png|left|thumb|500px|Example: Server and the Smart Client are running on the same PC (i.e. same IP address)]] | [[Image:Milestone config example 2.png|left|thumb|500px|Example: Server and the Smart Client are running on the same PC (i.e. same IP address)]] | ||
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
| − | |||
== Milestone XProtect configuration == | == Milestone XProtect configuration == | ||
| − | |||
It is assumed that a Milestone XProtect system is already installed and up and running. | It is assumed that a Milestone XProtect system is already installed and up and running. | ||
| Line 41: | Line 36: | ||
# A wizard offers you several ways of detecting and adding cameras. Follow the instructions and consult the Milestone documentation if required. | # A wizard offers you several ways of detecting and adding cameras. Follow the instructions and consult the Milestone documentation if required. | ||
| − | [[File: | + | [[File:AddNewCamera.PNG|left|thumb|500px|Adding a new camera to the Milestone system]] |
| + | <br style="clear:both;" /> | ||
| + | |||
| + | ==== Adding the camera of the Turbine Video Station, TCIV ==== | ||
| + | Follow these steps to add the integrated camera of the [[Turbine Video Settings]] to Milestone system: | ||
| + | # Start the Milestone '''Management Application''' software | ||
| + | # Expand the '''Advanced Configuration''' folder, and right click '''Hardware Devices''', and select '''Add New Hardware Device'''. | ||
| + | # A wizard offers you several ways of detecting and adding cameras. Select '''Manually specify the hardware to add''' | ||
| + | # Select '''Driver''' to be "Universal Driver" | ||
| + | # Enter the '''IP-address''' of the camera, and '''Port''' to 8090 | ||
| + | # Enter "admin" as '''User Name''' and "1234" as '''Password''' | ||
| + | # Press '''Next''' multiple times to complete the wizard | ||
| + | |||
| + | [[File:AddCPCAM.PNG|left|thumb|500px|Adding the TCIV camera]] | ||
| + | <br style="clear:both;" /> | ||
| + | |||
| + | After the camera has been added, you need to change the video properties: | ||
| + | # Expand the '''Camera and Storage Information''' folder, right click the camera, and select '''Properties''' | ||
| + | # Select '''Camera Settings''', and set: | ||
| + | ## '''Codec''': JPEG | ||
| + | ## '''Streaming mode''': HTTP | ||
| + | ## '''Delivery mode''': Multipart stream | ||
| + | ## '''Retrieval mode''': Streaming | ||
| + | ## '''Connection URI''': <nowiki>mjpg/video.mjpg</nowiki> | ||
| + | |||
| + | [[File:AddTCIV.PNG|left|thumb|500px|Video settings for the TCIV camera]] | ||
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
| − | + | Finally the microphone must be disabled in the camera settings. Without this setting, the video image might not appear in the Smart Client. | |
| + | # In the '''Advanced Configuration''' folder, expand the '''Hardware Devices''', locate the camera and then expand the camera folder. | ||
| + | # Select the microphone, and uncheck the enabled checkbox. | ||
| + | |||
| + | [[File:MilestoneTCIV Mic.PNG|left|thumb|500px|Disable microphone for the TCIV camera]] | ||
| + | <br style="clear:both;" /> | ||
| − | + | ==== Adding the camera of the IP Video Station, model 1401110100 ==== | |
| + | Follow these steps to add the integrated CP-CAM camera of the [[IP Video Door Station|IP Video Station, model 1401110100]] to Milestone system: | ||
# Start the Milestone '''Management Application''' software | # Start the Milestone '''Management Application''' software | ||
# Expand the '''Advanced Configuration''' folder, and right click '''Hardware Devices''', and select '''Add New Hardware Device'''. | # Expand the '''Advanced Configuration''' folder, and right click '''Hardware Devices''', and select '''Add New Hardware Device'''. | ||
| Line 59: | Line 85: | ||
After the camera has been added, you need to change the video properties: | After the camera has been added, you need to change the video properties: | ||
| − | # Expand the '''Camera and Storage''' folder, right click the camera, and select '''Properties''' | + | # Expand the '''Camera and Storage Information''' folder, right click the camera, and select '''Properties''' |
# Select '''Camera Settings''', and set: | # Select '''Camera Settings''', and set: | ||
## '''Codec''': JPEG | ## '''Codec''': JPEG | ||
| Line 65: | Line 91: | ||
## '''Delivery mode''': Multipart stream | ## '''Delivery mode''': Multipart stream | ||
## '''Retrieval mode''': Streaming | ## '''Retrieval mode''': Streaming | ||
| − | ## '''Connection URI''': <nowiki> | + | ## '''Connection URI''': <nowiki>mjpg/video.mjpg</nowiki> |
| − | [[File:CPCAM Settings.PNG|left|thumb|500px|Video settings for the CP-CAM]] | + | [[File:CPCAM Settings.PNG|left|thumb|500px|Video settings for the CP-CAM camera]] |
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
| + | |||
| + | Finally the microphone must be disabled in the camera settings. Without this setting, the video image might not appear in the Smart Client. | ||
| + | # In the '''Advanced Configuration''' folder, expand the '''Hardware Devices''', locate the camera and then expand the camera folder. | ||
| + | # Select the microphone, and uncheck the enabled checkbox. | ||
| + | |||
| + | [[File:MilestoneDisableMic.PNG|left|thumb|500px|Disable microphone for the CP-CAM camera]] | ||
| + | <br style="clear:both;" /> | ||
| + | |||
| + | ==== Adding the camera of the IP Video Station, model 1401110200 ==== | ||
| + | The [[IP Video Door Station - 1401110200|IP Video Station, model 1401110200]] has an integrated Axis camera which can be added to the to Milestone system. Follow these steps: | ||
| + | # Start the Milestone '''Management Application''' software | ||
| + | # Expand the '''Advanced Configuration''' folder, and right click '''Hardware Devices''', and select '''Add New Hardware Device'''. | ||
| + | # A wizard offers you several ways of detecting and adding cameras. Select '''Scan for hardware''', then '''Next''' | ||
| + | # In the list of Manufacturers you might select Axis as the only choice, as this will speed up the detection process. | ||
| + | [[File:AddAxisCamera.PNG|left|thumb|500px|Axis camera discovered]] | ||
| + | <br style="clear:both;" /> | ||
| + | |||
| + | :5. Press '''Next''' and '''OK''' until the wizard completes, then press '''Save''' to store the added camera | ||
===The Matrix function=== | ===The Matrix function=== | ||
| Line 83: | Line 127: | ||
# Click '''Add''', then '''OK''' to save the settings. | # Click '''Add''', then '''OK''' to save the settings. | ||
| − | [[File: | + | [[File:AddMatrix.PNG|left|thumb|500px|Adding a Matrix recipient]] |
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
| Line 98: | Line 142: | ||
=== Generic Events === | === Generic Events === | ||
| − | |||
==== Adding Generic Events ==== | ==== Adding Generic Events ==== | ||
| − | Generic events allow you to trigger actions in the Milestone XProtect event server by sending simple strings from the AlphaCom XE via the IP network to the Milestone event server. In AlphaCom the [[Event Handler]] is used to generate strings transmitted via the [[EDO|EDO port]]. In this article the string is on the format "CamXXX", where XXX is the directory number of the station associated with the camera. Using the directory number as a part of the string is convenient, as it simplifies the event handler programming in AlphaCom. But the syntax of the string is freely programmable. | + | Generic events allow you to trigger actions in the Milestone XProtect event server by sending simple strings from the ICX/AlphaCom XE via the IP network to the Milestone event server. In ICX/AlphaCom the [[Event Handler]] is used to generate strings transmitted via the [[EDO|EDO port]]. In this article the string is on the format "CamXXX", where XXX is the directory number of the station associated with the camera. Using the directory number as a part of the string is convenient, as it simplifies the event handler programming in ICX/AlphaCom. But the syntax of the string is freely programmable. |
Examples: | Examples: | ||
| Line 123: | Line 166: | ||
To add Generic Events from the Management Client, do the following: | To add Generic Events from the Management Client, do the following: | ||
| − | # In the Milestone '''Management Application''' software, expand the '''Advanced Configuration''' folder, and double click '''Generic Events''' | + | # In the Milestone '''Management Application''' software, expand the '''Advanced Configuration''' folder, expand '''Events and Output''' and double click '''Generic Events''' |
# Select '''Add''' at the button of the window to create a new event | # Select '''Add''' at the button of the window to create a new event | ||
# In the '''Event name''' field, enter a descriptive name for the event, e.g. '''Cam107'''. | # In the '''Event name''' field, enter a descriptive name for the event, e.g. '''Cam107'''. | ||
| − | # In the '''Event substring''' field, enter the actual string, as received from AlphaCom. E.g. '''Cam107'''. | + | # In the '''Event substring''' field, enter the actual string, as received from ICX/AlphaCom. E.g. '''Cam107'''. |
# Select the '''Add''' button next to the "Event substring" field. | # Select the '''Add''' button next to the "Event substring" field. | ||
| Line 133: | Line 176: | ||
==== Creating event rules ==== | ==== Creating event rules ==== | ||
| − | Rules have to be created, saying that when the Milestone event server receives a generic event from the AlphaCom, the video from a certain camera should pop up in a certain Smart Client. To define actions on events follow these steps: | + | Rules have to be created, saying that when the Milestone event server receives a generic event from the ICX/AlphaCom, the video from a certain camera should pop up in a certain Smart Client. To define actions on events follow these steps: |
# In the Milestone '''Management Application''' software, expand the '''Advanced Configuration''' folder, and double click '''Matrix''' | # In the Milestone '''Management Application''' software, expand the '''Advanced Configuration''' folder, and double click '''Matrix''' | ||
| Line 146: | Line 189: | ||
==== Testing Generic Events ==== | ==== Testing Generic Events ==== | ||
| − | One can test that the generic events are operational with a small program called [[Downloads#Useful_Tools|Generic Event tester]]. This makes to possible to verify the Milestone configuration, totally independent of the AlphaCom. | + | One can test that the generic events are operational with a small program called [[Downloads#Useful_Tools|Generic Event tester]]. This makes to possible to verify the Milestone configuration, totally independent of the ICX/AlphaCom. |
* '''Host''': Enter "localhost" if the GenericEventTester is running on the same computer as the Milestone server. If the GenericEventTester is running on a remote computer, enter the IP address of the Milestone server. | * '''Host''': Enter "localhost" if the GenericEventTester is running on the same computer as the Milestone server. If the GenericEventTester is running on a remote computer, enter the IP address of the Milestone server. | ||
| Line 156: | Line 199: | ||
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
| − | ==AlphaCom configuration== | + | ==ICX/AlphaCom configuration== |
=== Configure the Master station for Call Queueing=== | === Configure the Master station for Call Queueing=== | ||
A number of different station types can be used for call queuing. The station should use the [[Mail Queue Operation|763x codes]] for queue navigation. These directory numbers should be assigned to [[DAK]] keys. The station should be prepared for call queue operation, how to do this depends on the station type used: | A number of different station types can be used for call queuing. The station should use the [[Mail Queue Operation|763x codes]] for queue navigation. These directory numbers should be assigned to [[DAK]] keys. The station should be prepared for call queue operation, how to do this depends on the station type used: | ||
| Line 173: | Line 216: | ||
* Enable '''Connect at AlphaCom write, disconnect after each write''' | * Enable '''Connect at AlphaCom write, disconnect after each write''' | ||
| − | The Milestone XProtect Server is by default using TCP port 1234 for generic events. If required this port number can be modified from | + | The Milestone XProtect Server is by default using TCP port 1234 for generic events. If required this port number can be modified from the '''Management Application''' software. Expand the '''Advanced Configuration''' folder, and click '''Events and Outputs'''. Here the port number can be changed if required. |
'''Note!''' You might have to open TCP port 1234 in the Windows firewall of the computer running the Milestone server. | '''Note!''' You might have to open TCP port 1234 in the Windows firewall of the computer running the Milestone server. | ||
| − | + | * '''Windows 7:''' Start > Control Panel > Windows Firewall > Advanced settings > Inbound rules > New Rule > Port > Select port type '''TCP'''. Specific local ports: '''1234''' > Enable '''Allow the connection'''. Name: Milestone. | |
| + | * '''Windows XP:''' Start > Control Panel > Windows Firewall > Exceptions tab > Add Port: Select port type '''TCP'''. Name: Milestone. Port number: '''1234''' | ||
| + | |||
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
| Line 183: | Line 228: | ||
'''UDP Groups:''' | '''UDP Groups:''' | ||
* Include all substations with cameras in [[UDP group]] 2. | * Include all substations with cameras in [[UDP group]] 2. | ||
| − | + | ||
'''Event Handler configuration:'''<br> | '''Event Handler configuration:'''<br> | ||
The [[Event Handler]] is used to transmit commands through the EDO port to the Milestone IP Video system. | The [[Event Handler]] is used to transmit commands through the EDO port to the Milestone IP Video system. | ||
| Line 316: | Line 361: | ||
== Related links and articles == | == Related links and articles == | ||
* [{{SERVER}}/alphawiki/downloads/GenericEventTest.exe Generic_Event_tester] | * [{{SERVER}}/alphawiki/downloads/GenericEventTest.exe Generic_Event_tester] | ||
| − | * | + | * Integration with the [[Milestone XProtect - Expert and Corporate|Expert and Corporate versions]] of Milestone XProtect |
| − | |||
| − | [[Category: | + | [[Category:Discontinued Products]] |
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 07:51, 16 August 2022
|
This product is discontinued! |
For integration with Milestone, please see:
The integration of ICX/AlphaCom with Milestone XProtect software enables video stream routing under control of commands issued by ICX/AlphaCom. The interface uses the standard matrix functionality which is part of Milestone XProtect VMS. This article describes how to integrate the ICX/AlphaCom with the Milestone XProtect Professional and Enterprise 2014 (8.6c) version.
Integration with the Expert and Corporate versions of XProtect is described in a separate article.
Contents
Features
The integration allows cameras to be connected to monitors on call and call request events, including changes to the viewed camera when the guard scrolls through the call request queue on the intercom station.
When a master station receives Call Request from a substation, and when a call is made to the substation, action strings are sent from the ICX/AlphaCom to the Milestone system using the EDO port. Using the Event Handler, a few simple events allows control of cameras located in association with a substation. When scrolling the call queue, commands related to the selected station is transmitted, allowing the video on the monitor to follow the queue navigation on the master station.
If any new call requests are received while in conversation, this will not influence on the active image. When the conversation is cancelled, and there are still calls in the queue, the image associated to the first station in queue will be displayed.
Licenses
- When used with the ICX System, the following license is required in the ICX in order to enable the EDO port: 1002602400 - ILI-IF Interface enabling
Default TCP port usage
- TCP port 1234: Between ICX/AlphaCom and the Milestone XProtect Server
- TCP port 80: Between the Server and the Smart Client
- TCP port 12345: Used for transferring Matrix-triggered images from the Server to the Smart Client view
Milestone XProtect configuration
It is assumed that a Milestone XProtect system is already installed and up and running.
Adding new cameras
Adding cameras in general
- Start the Milestone Management Application software
- Expand the Advanced Configuration folder, and right click Hardware Devices, and select Add New Hardware Device.
- A wizard offers you several ways of detecting and adding cameras. Follow the instructions and consult the Milestone documentation if required.
Adding the camera of the Turbine Video Station, TCIV
Follow these steps to add the integrated camera of the Turbine Video Settings to Milestone system:
- Start the Milestone Management Application software
- Expand the Advanced Configuration folder, and right click Hardware Devices, and select Add New Hardware Device.
- A wizard offers you several ways of detecting and adding cameras. Select Manually specify the hardware to add
- Select Driver to be "Universal Driver"
- Enter the IP-address of the camera, and Port to 8090
- Enter "admin" as User Name and "1234" as Password
- Press Next multiple times to complete the wizard
After the camera has been added, you need to change the video properties:
- Expand the Camera and Storage Information folder, right click the camera, and select Properties
- Select Camera Settings, and set:
- Codec: JPEG
- Streaming mode: HTTP
- Delivery mode: Multipart stream
- Retrieval mode: Streaming
- Connection URI: mjpg/video.mjpg
Finally the microphone must be disabled in the camera settings. Without this setting, the video image might not appear in the Smart Client.
- In the Advanced Configuration folder, expand the Hardware Devices, locate the camera and then expand the camera folder.
- Select the microphone, and uncheck the enabled checkbox.
Adding the camera of the IP Video Station, model 1401110100
Follow these steps to add the integrated CP-CAM camera of the IP Video Station, model 1401110100 to Milestone system:
- Start the Milestone Management Application software
- Expand the Advanced Configuration folder, and right click Hardware Devices, and select Add New Hardware Device.
- A wizard offers you several ways of detecting and adding cameras. Select Manually specify the hardware to add
- Select Driver to be "Universal Driver"
- Enter the IP-address of the camera, and Port to 80
- Enter "admin" as User Name and "1234" as Password
- Press Next multiple times to complete the wizard
After the camera has been added, you need to change the video properties:
- Expand the Camera and Storage Information folder, right click the camera, and select Properties
- Select Camera Settings, and set:
- Codec: JPEG
- Streaming mode: HTTP
- Delivery mode: Multipart stream
- Retrieval mode: Streaming
- Connection URI: mjpg/video.mjpg
Finally the microphone must be disabled in the camera settings. Without this setting, the video image might not appear in the Smart Client.
- In the Advanced Configuration folder, expand the Hardware Devices, locate the camera and then expand the camera folder.
- Select the microphone, and uncheck the enabled checkbox.
Adding the camera of the IP Video Station, model 1401110200
The IP Video Station, model 1401110200 has an integrated Axis camera which can be added to the to Milestone system. Follow these steps:
- Start the Milestone Management Application software
- Expand the Advanced Configuration folder, and right click Hardware Devices, and select Add New Hardware Device.
- A wizard offers you several ways of detecting and adding cameras. Select Scan for hardware, then Next
- In the list of Manufacturers you might select Axis as the only choice, as this will speed up the detection process.
- 5. Press Next and OK until the wizard completes, then press Save to store the added camera
The Matrix function
With Matrix — an integrated solution for distributed viewing of video — you can send video from any camera on a network operating your system to Matrix recipients. A Matrix recipient is basically a computer capable of displaying Matrix-triggered video. There are two kinds of Matrix recipients: computers running a dedicated Matrix Monitor application and computers running the XProtect Smart Client.
Adding a Matrix recipient
To add an Matrix recipient, do the following:
- In the Milestone Management Application software, expand the Advanced Configuration folder, and double click Matrix
- In the Name field, enter a descriptive name for the Matrix recipient.
- In the Address field enter the IP address or the host name of the required Matrix recipient
- In the Port field enter the port number used by the Matrix recipient installation. Default is 12345.
- In the Password field enter the Matrix recipient's password, e.g. 12345.
- Enable "Matrix recipient is a Smart Client".
- Click Add, then OK to save the settings.
Setting the Smart Client to work as a matrix recipient
To make the Smart Client work as a matrix recepient, do the following steps:
- Start the Smart Client application and select the tab Setup
- In the Views pane, right click on the Private view and add New Group.
- Once the new group is created, right click and add New View and select the dimensions wanted. E.g. 4:3, 1x1.
- In the System Overview pane, drag and drop the Matrix item to the main window.
- While the main window is in focus, scroll down and click the button Connection Settings in the Properties pane, and enter port number 12345 and the same password as you entered in the Matrix setup in the Management Application.
Generic Events
Adding Generic Events
Generic events allow you to trigger actions in the Milestone XProtect event server by sending simple strings from the ICX/AlphaCom XE via the IP network to the Milestone event server. In ICX/AlphaCom the Event Handler is used to generate strings transmitted via the EDO port. In this article the string is on the format "CamXXX", where XXX is the directory number of the station associated with the camera. Using the directory number as a part of the string is convenient, as it simplifies the event handler programming in ICX/AlphaCom. But the syntax of the string is freely programmable.
Examples:
| EDO string | Camera | Event name | Station dir.no |
|---|---|---|---|
| Cam107 | Entrance | Cam107 | 107 |
| Cam108 | Backdoor | Cam108 | 108 |
| Cam109 | Corridor | Cam109 | 109 |
| CamOff | All | CamOff | All stations |
The "CamOff" event is used to disconnect cameras from the Smart Client when there is no conversations and the call queue is empty.
To add Generic Events from the Management Client, do the following:
- In the Milestone Management Application software, expand the Advanced Configuration folder, expand Events and Output and double click Generic Events
- Select Add at the button of the window to create a new event
- In the Event name field, enter a descriptive name for the event, e.g. Cam107.
- In the Event substring field, enter the actual string, as received from ICX/AlphaCom. E.g. Cam107.
- Select the Add button next to the "Event substring" field.
Creating event rules
Rules have to be created, saying that when the Milestone event server receives a generic event from the ICX/AlphaCom, the video from a certain camera should pop up in a certain Smart Client. To define actions on events follow these steps:
- In the Milestone Management Application software, expand the Advanced Configuration folder, and double click Matrix
- Select Matrix Event Control
- Right-click the Matrix recipient and select 'Generic', then select one of the predefined Generic events
- Now right-click the event to select which action should take place when the event occurs. Here, select 'Connect'.
- Right-click the action to select which camera to apply the action on
- Repeat step 3 to 5 for every camera
Testing Generic Events
One can test that the generic events are operational with a small program called Generic Event tester. This makes to possible to verify the Milestone configuration, totally independent of the ICX/AlphaCom.
- Host: Enter "localhost" if the GenericEventTester is running on the same computer as the Milestone server. If the GenericEventTester is running on a remote computer, enter the IP address of the Milestone server.
- Port: The port number used by the Milestone event server for Generic Events. Default is 1234.
- Event: The generic event string, e.g. Cam107 or CamOff, as defined in the "Expression" field of the Generic Event.
- Press Send Tcp to send the event string to Milestone. The actions as defined by the Rules should now be executed.
ICX/AlphaCom configuration
Configure the Master station for Call Queueing
A number of different station types can be used for call queuing. The station should use the 763x codes for queue navigation. These directory numbers should be assigned to DAK keys. The station should be prepared for call queue operation, how to do this depends on the station type used:
TCP/IP Communication setup
In AlphaPro, Exchange & System -> Serial Ports, the EDO 1 port must be configured to communiate with the computer running the Milestone XProtect server:
- Port type: TCP/IP Client
- IP address: The IP address of the Milestone XProtect event server
- Port: 1234
- Enable Connect at AlphaCom write, disconnect after each write
The Milestone XProtect Server is by default using TCP port 1234 for generic events. If required this port number can be modified from the Management Application software. Expand the Advanced Configuration folder, and click Events and Outputs. Here the port number can be changed if required.
Note! You might have to open TCP port 1234 in the Windows firewall of the computer running the Milestone server.
- Windows 7: Start > Control Panel > Windows Firewall > Advanced settings > Inbound rules > New Rule > Port > Select port type TCP. Specific local ports: 1234 > Enable Allow the connection. Name: Milestone.
- Windows XP: Start > Control Panel > Windows Firewall > Exceptions tab > Add Port: Select port type TCP. Name: Milestone. Port number: 1234
Event Handler configuration
UDP Groups:
- Include all substations with cameras in UDP group 2.
Event Handler configuration:
The Event Handler is used to transmit commands through the EDO port to the Milestone IP Video system.
In AlphaPro, go to Exchange and System -> Events, press Insert and create the following events:
Event 1 - An UDD is used to store the busy/free status of the master station. 0 = free, 1 = in conversation. The index of the UDD is equal to the physical number of the master station. The UDD is checked when call requests are received or deleted. If the station is in use, cameras should not be turned on (i.e. no commands should be transmitted).
| Event Owner: | The Master Station |
| Event type: | 08 - Conversation Outgoing |
| When change to: | ON or OFF |
| When related to: | All |
| Action: | WUDD %1.phy %chg(1,0) |
Event 2 - When a conversation is made from the master station to a substation w. camera, transmit command "CamXXX" to the IP Video system, where XXX = the directory number of the substation.
| Event Owner: | The Master Station |
| Event type: | 08 - Conversation Outgoing |
| Subevent: | 0 |
| When change to: | ON |
| When related to: | Stations w. UDP, Id: 2 |
| Action: | EDO 1 "Cam%2.dir" |
Event 3 - When the conversation between the master and any station cancels, switch off the camera ("CamOff"), and activate the MAILQ_NAVIG command. The MAILQ_NAVIG command will step to the first in the queue, and re-trigger the '23 - New Current Mail' event.
| Event Owner: | The Master Station |
| Event type: | 08 - Conversation Outgoing |
| Subevent: | 0 |
| When change to: | OFF |
| When related to: | All |
| Action: | EDO 1 "CamOff" |
| $MAILQ_NAVIG L%1.dir 2 |
Event 4 - When receiving a Call Request or scrolling the queue, and the master station is not busy, activate the camera assosiated with the selected substation.
| Event Owner: | The Master Station |
| Event type: | 23 - New Current Mail |
| Subevent: | 0 |
| When change to: | ON |
| When related to: | Stations w. UDP, Id: 2 |
| Action: | IF %udd(%1.phy) |
| STOP | |
| ENDIF | |
| EDO 1 "Cam%2.dir" |
Event 5 - The Priority Mail Present - OFF event is triggered when the queue of the master station is empty. The queue can become empty because the delete code 7630 has been dialled, in that case the cameras should be turned off. Or the queue can become empty because of call back to the last substation in queue, in that case we want the camera to remain on until the conversation is cancelled. We start a 0.5 second timer, and check if the master station is in conversation when the timer times out:
| Event Owner: | The Master Station |
| Event type: | 06 - Priority Mail Present |
| When change to: | OFF |
| Action: | $ST L%1.dir w5 L9999 |
Event 6 - Half a second after the queue was empty, check if the station is in conversation, if not switch off the camera:
| Event Owner: | The Master Station |
| Event type: | 21 - Event Timeout |
| Subevent: | 0 |
| When change to: | ON |
| When related to: | Directory number: 9999 |
| Action: | IF %udd(%1.phy) |
| STOP | |
| ENDIF | |
| EDO 1 "CamOff" |
Related links and articles
- Generic_Event_tester
- Integration with the Expert and Corporate versions of Milestone XProtect