Difference between revisions of "Mirasys"
From Zenitel Wiki
(Created page with "{{A}} ==Introduction== The interface between AlphaCom and the Mirasys VMS, is based on EDO and event handler programming in the AlphaCom. ==AlphaCom programming== ===UDP===...") |
|||
(7 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | {{ | + | {{AI}} |
==Introduction== | ==Introduction== | ||
− | The | + | The Mirasys VMS can be integrated with the ICX system or the AlphaCom system. The integration is based on EDO and event handler programming in the ICX/AlphaCom. |
− | ==AlphaCom | + | ==Licenses == |
− | ===UDP=== | + | 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 |
+ | |||
+ | ==ICX/AlphaCom configuration== | ||
+ | ===UDP Group=== | ||
Assign a UDP flag to all intercom stations with a camera, For instance: | Assign a UDP flag to all intercom stations with a camera, For instance: | ||
*UDP 1 | *UDP 1 | ||
Line 39: | Line 42: | ||
===Mirasys setup=== | ===Mirasys setup=== | ||
− | The Mirasys interface is programmed by including the | + | The Mirasys interface is programmed by including the file 'UDD4ZenitelAlpha.xml' in the directory 'program files/DVMS/DVR folder'. |
The contents of this file is project specific, as all directory numbers of intercom stations with a camera must be defined in this file. Please open the downloaded file in an ASCII text editor and put the appropriate directory numbers in the section 'array name="p1" params="EDOMessageParams"'. | The contents of this file is project specific, as all directory numbers of intercom stations with a camera must be defined in this file. Please open the downloaded file in an ASCII text editor and put the appropriate directory numbers in the section 'array name="p1" params="EDOMessageParams"'. | ||
+ | |||
+ | ==Vingtor-Stentofon cameras== | ||
+ | Video streams from the Vingtor-Stentofon cameras (CP-CAM and TCIV) can be accessed by Mirasys. For licensing of the required 'HTTPIPcapture-driver', please contact your Mirasys distributor. | ||
+ | ===TCIV=== | ||
+ | Settings for the TCIV camera in Mirasys are: | ||
+ | *http://IP_ADDRESS:8090/mjpg/video.mjpg | ||
+ | *fps: ~10 fps | ||
+ | *Codec: JPEG | ||
+ | ===CP-CAM=== | ||
+ | Settings for the CP-CAM camera in Mirasys are: | ||
+ | *http://IP_ADDRESS/mjpg/video.mjpg | ||
+ | *fps: ~10 fps | ||
+ | *Codec: JPEG | ||
+ | |||
+ | ==Sending commands from Mirasys to ICX or AlphaCom== | ||
+ | It is also possible to send commands to ICX or AlphaCom, for instance to start a voice message to an IP-speaker when a specific button on the Mirasys GUI is clicked. | ||
+ | ===Mirasys license=== | ||
+ | For this functionality the Mirasys VMS must have the license 'UniversalOutputDriver' in place. | ||
+ | ===ICX/AlphaCom=== | ||
+ | Program an event and event trigger to send the alarm message to the correct IP-speaker. For instance event trigger directory number 9595. | ||
+ | ===Mirasys=== | ||
+ | Mirasys uses the custom scripting capability of the ICX/AlphaCom. Program Mirasys to send the following http-command: | ||
+ | *http://<ICX or AlphaCom_IP-address>/cmd/call_handle.php?from=110&dial_digit=9595 | ||
+ | In this case it appears that the station with directory number 110 (operator station associated with the Mirasys GUI) has dialed 9595, which in turn triggers the specified event. | ||
+ | |||
[[Category:3rd party integration]] | [[Category:3rd party integration]] | ||
+ | [[Category: ICX-AlphaCom integration]] |
Latest revision as of 13:57, 24 October 2024
Contents
Introduction
The Mirasys VMS can be integrated with the ICX system or the AlphaCom system. The integration is based on EDO and event handler programming in the ICX/AlphaCom.
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
ICX/AlphaCom configuration
UDP Group
Assign a UDP flag to all intercom stations with a camera, For instance:
- UDP 1
- UDP text: Mirasys camera
Assign a UDP flag to all operator intercom stations, For instance:
- UDP 2
- UDP text: Mirasys operator
EDO port
Communication is based on EDO. Program an EDO port, for instance EDIO 1 as following:
- Port Type: TCP/IP client
- IP-address: The IP-address of the Mirasys server
- Port: 40000
- Keep Alive - Enabled
EDO events
The events below are examples, please modify/add as appropriate.
Conversation event - Outgoing
This event can be used to indicate to victor that 2 stations are connected in a conversation, or that the conversation has ended:
- Owner Type: stations With UDP: 1
- Event type: 8 - Conversation-Outgoing
- When Change To: ON or OFF
- When Related To: Stations With UDP 2 - In an AlphaNet set Node to 255
- Action Command: EDO 1 "Cam %1d %chg(ON,OFF)"
Conversation event - Incoming
This event can be used to indicate to victor that 2 stations are connected in a conversation, or that the conversation has ended:
- Owner Type: stations With UDP: 1
- Event type: 7 - Conversation-Incoming
- When Change To: ON or OFF
- When Related To: Stations With UDP 2 - In an AlphaNet set Node to 255
- Action Command: EDO 1 "Cam %1d %chg(ON,OFF)"
Mirasys setup
Mirasys license
The Mirasys VMS must have the license 'UniversalDataDriver' in place.
Mirasys setup
The Mirasys interface is programmed by including the file 'UDD4ZenitelAlpha.xml' in the directory 'program files/DVMS/DVR folder'. The contents of this file is project specific, as all directory numbers of intercom stations with a camera must be defined in this file. Please open the downloaded file in an ASCII text editor and put the appropriate directory numbers in the section 'array name="p1" params="EDOMessageParams"'.
Vingtor-Stentofon cameras
Video streams from the Vingtor-Stentofon cameras (CP-CAM and TCIV) can be accessed by Mirasys. For licensing of the required 'HTTPIPcapture-driver', please contact your Mirasys distributor.
TCIV
Settings for the TCIV camera in Mirasys are:
- http://IP_ADDRESS:8090/mjpg/video.mjpg
- fps: ~10 fps
- Codec: JPEG
CP-CAM
Settings for the CP-CAM camera in Mirasys are:
- http://IP_ADDRESS/mjpg/video.mjpg
- fps: ~10 fps
- Codec: JPEG
Sending commands from Mirasys to ICX or AlphaCom
It is also possible to send commands to ICX or AlphaCom, for instance to start a voice message to an IP-speaker when a specific button on the Mirasys GUI is clicked.
Mirasys license
For this functionality the Mirasys VMS must have the license 'UniversalOutputDriver' in place.
ICX/AlphaCom
Program an event and event trigger to send the alarm message to the correct IP-speaker. For instance event trigger directory number 9595.
Mirasys
Mirasys uses the custom scripting capability of the ICX/AlphaCom. Program Mirasys to send the following http-command:
- http://<ICX or AlphaCom_IP-address>/cmd/call_handle.php?from=110&dial_digit=9595
In this case it appears that the station with directory number 110 (operator station associated with the Mirasys GUI) has dialed 9595, which in turn triggers the specified event.