Difference between revisions of "EBMDR-8 - Configuration"
From Zenitel Wiki
(→Redirection of DAK keys) |
|||
Line 10: | Line 10: | ||
== Redirection of DAK keys == | == Redirection of DAK keys == | ||
− | In general every user in AlphaCom has DAK tables for 20 DAK keys. | + | In general every user in AlphaCom has DAK tables for 20 DAK keys. When using more than one extension module, one have to "borrow" DAK tables from other, unused stations. |
DAK tables are "borrowed" by pointing to the other users in the DAK table of the ECPIR. This is done by using the symbol ">", followed by the '''physical''' number of the station from where we want to use the DAK table. Any free physical number in the range 1 to 552 can be used. However, it is recommended to use higher numbers to avoid conflicts if the system is expanded in the future. | DAK tables are "borrowed" by pointing to the other users in the DAK table of the ECPIR. This is done by using the symbol ">", followed by the '''physical''' number of the station from where we want to use the DAK table. Any free physical number in the range 1 to 552 can be used. However, it is recommended to use higher numbers to avoid conflicts if the system is expanded in the future. |
Revision as of 16:07, 2 February 2017
This article describes how to configure the AlphaCom when using the Call Panel ECPIR-3P together with the Expansion Module EBMDR-8. Up to 4 expansion modules can be attached to one ECPIR-3P.
Contents
Enable the use of the EBMDR-8 Module
The following setting under Users & Stations > Station Type in AlphaPro must be checked to fully support the expansion module.
Redirection of DAK keys
In general every user in AlphaCom has DAK tables for 20 DAK keys. When using more than one extension module, one have to "borrow" DAK tables from other, unused stations.
DAK tables are "borrowed" by pointing to the other users in the DAK table of the ECPIR. This is done by using the symbol ">", followed by the physical number of the station from where we want to use the DAK table. Any free physical number in the range 1 to 552 can be used. However, it is recommended to use higher numbers to avoid conflicts if the system is expanded in the future.
The actual DAK key configuration must be entered in the DAK table of the station to which the ECPIR DAK table is pointing:
Several ECPIR stations may redirect to the same DAK tables if they should use the same DAK layout.
LED Indications
The DAK keys on the ECPIR and on the button expansion panels have two LED's each. The two LED's (red and green) are controlled using the IND command in the Event Handler.
Call Request
To turn on the red LED, flashing fast, in the associated DAK key when a Call Request is received, create this event:
Outgoing Conversation
To turn on the green LED in the associated DAK key when an outgoing call is made, create this event:
Incoming Conversation
To turn on the green LED in the associated DAK key when an incoming call is received, create this event:
Door Status
An input of the IP station can be connected to a door magnet, providing indication on the DAK panel, showing if the door is open or closed.
Example:
To turn on the red LED in the associated DAK key when input 3 of the IP substation 159 is activated, create this event:
Action Command:
OWN r 105
IND %2.phy %2.dak(I%1.dir) 1 1
105 is the directory number of the ECPIR
Station faults
To turn on the red and green LED in the associated DAK key when a station is reported faulty, create this event:
Action Command:
OWN r 105
IND %2.phy %2.dak(I%1.dir) 1 1
IND %2.phy %2.dak(I%1.dir) 2 1
105 is the directory number of the ECPIR-3P