CCTV control by relays (RCO) when using Call Request

Situation

When a master station is receiving Call Requests from a substation, a relay should be activated to control a CCTV switch. Each substation has a dedicated relay output for this purpose. When scrolling the queue, the relay assosiated to the seleceted station should be activated. In this way the picture on the monitor will follow the queue navigation on the master station.

When answering the call request the relay must remain active during the conversation. Any new call requests received during conversation should not influence on the active relay. When the conversation is cancelled, and there are still calls in queue, the relay assosiated to the first station in queue should be activated.

Solution

The master station should use the 763x codes for queue navigation. These directory numbers should be assigned to DAK keys. A number of station types can be used for call queuing. Depending on the station type in use, the station should be prepared for call queue operation:

• TouchLine station
• DualDisplay station
• CRM IV station

Include all substations with cameras in UDP group 2.

The Event Handler is used to control the RCO's which operate the relays. In the examples below the logical address of the RCO is equal to the physical number of the substation. E.g. if station on physical number 5 is calling, RCO #5 will be operated.

An UDD is used to store the conversation status of the master station. 0 = no conversation, 1 = conversation. The index of the UDD is equal to the physical nymber of the master station. The UDD is checked when new call requests arrive (when the 'New Current Mail' - ON is triggered). If there is a conversation active when a new call request cames in, there should be no RCO operations.

In AlphaPro, [Exchange and System] -> [Events], press [Insert] and create the following events:

---

Event 1 - When a conversation in made from the master station to the substation, set the conversation status in the UDD. A 0,1 sec. timer is started, when it expires the RCO is activated. The timer is neccessary due to a timing issue between the New Current Mail - OFF event and the Conversation Outgoing - ON event.

Event Owner:	The Master Station (or a UDP group of master stations)
Event type:	08 - Conversation Outgoing
Subevent:	0
When change to:	ON
When related to:	UDP 2
Action:	WUDD %1.phy 1
	$ST L%1.dir W1 L%2.phy

---

Event 2 - Set the RCO when the 0.1 sec. timer expires:

Event Owner:	The Master Station (or a UDP group of master stations)
Event type:	21 - Event Timeout
Subevent:	0
When change to:	ON
When related to:	All
Action:	RCO %2.dir ON

---

Event 3 - When the conversation between the master and substation cancels, reset the conversation status (UDD), switch off the RCO, and activate the MAILQ_NAVIG command. This command will step to the first in the queue, and re-trigger the '23 - New Current Mail' event:

Event Owner:	The Master Station (or a UDP group of master stations)
Event type:	08 - Conversation Outgoing
Subevent:	0
When change to:	OFF
When related to:	UDP 2
Action:	WUDD 1 0
	RCO %2.phy OFF
	$MAILQ_NAVIG L%1.dir 2

---

Event 4 - When receiving a Call Request or scrolling the queue, and the station is not in conversation, activate the RCO:

Event Owner:	The Master Station (or a UDP group of master stations)
Event type:	23 - New Current Mail
Subevent:	0
When change to:	ON
When related to:	UDP 2
Action:	IF %udd(%1.phy)
	STOP
	ENDIF
	RCO %2.phy ON

---

Event 5 - When a queue entry is deleted or scrolled away from, switch off the RCO:

Event Owner:	The Master Station (or a UDP group of master stations)
Event type:	23 - New Current Mail
Subevent:	0
When change to:	OFF
When related to:	UDP 2
Action:	RCO %2.phy OFF

---