Mirasys
From Zenitel Wiki
Contents
Introduction
The interface between AlphaCom and the Mirasys VMS, is based on EDO and event handler programming in the AlphaCom.
AlphaCom programming
UDP
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"'.