Matrix: Eclipse-PiCo & E32 High Speed link Capabilities

Matrix: Eclipse-PiCo & E32 High Speed link Capabilities

Eclipse-Pico and E-32 matrices maybe linked by using the high speed link forming two linked 36 port matrices
The high speed link is NOT recommended for new installations as it provides a limited functionality. Customers are recommended to link Eclipse-Pico (E-32) matrices using normal trunking functionality.

Eclipse-PiCo & E32 High Speed link Capabilities
Port Types
Full duplex audio connections may be established and be non-blocking between any of the following.  •Panels (all Eclipse-PiCo supported panels)
•4-Wire ports
•4-wire FOR-22 ports
•2-wire CCI-22 ports
•Tel-14
Tel-14 Control
•Off Hook
A TEL-14 on the partner Eclipse-Pico system can only be taken off-hook by the activation of a remote Control. This requires a key to activate a Control Macro.
•Dialling
It is only possible to dial on the other E-PiCo TEL-14 by the activation of a Control Macro to perform a speed dial or by using an ICS-2003E as this panel has on-board DTMF generation.
•Incoming call signalisation
The TEL-14 based routing function based on DTMF decode will work across systems.
A TEL-14 based incoming call can also be routed across systems using the local advanced settings based routing to a fixed group containing one or more ports form another system.
Panel Interface
•Labels
The labels displayed for labels on the other frame, accessed via intelligent linking are as follows.
•Label updates
When a port label is updated the configuration need only be downloaded to the owning system. Once committed this system will send the updated label list to the any linked system.
•Label display modes
The alias display will not be prefixed with the “system number”.
In V4.2 the above mechanism will only be supported for port labels (i.e. 4 wires and all supported panel types).
•Key soft assignment
Labels from the partner Eclipse-PiCo can be assigned to keys the current panel via the soft assignment screens. Access to this functionality will be limited using sort groups just as for the local labels.
Fixed Groups
•Local fixed group
A fixed group may be formed from ports on any of the systems in the linked set. When a fixed group is formed in this fashion multiple trunk requests will be involved. This will result in a latency increment of approx 30ms per remote member.
•Remote fixed groups
A fixed group on another system can be accessed only by the activation of a route. This activation will result in a single trunk request and therefore normal intelligent linking latency responses will be achieved.
•Signalisation
When a fixed group is accessed, all panel members of the group will display the incoming call tally on the reply key. This tally will not be seen on the key if the receiving panel has a dedicated key to the fixed group.
Conferences
Note – In this document the terms Party-line and Conference are synonymous.
•Permanent Conferences
If ECS is used to form a conference from ports on multiple systems a permanent conference is used. This is permanently mixed between systems. Panels/4-Wires on each Eclipse-PiCo can be either permanent or temporary members.
•Temporary membership
If a panel, interface or direct port is a temporary member of a conference the desired routing (depending on talk / listen status) will only be in place when the key or route is active.
•Permanent membership
If a panel, interface or direct port is made a permanent member of a conference the desired routing is permanently in place to/from (depending on talk / listen status) all other permanent and currently active temporary members.
•Conferences on the other E-PiCo
A conference on the other system can be accessed only by the activation of a Route. This activation will result in a single trunk request and therefore normal intelligent linking latency responses will be achieved.
•Talk/Listen/Both
The access to a conference can be tagged as talk, listen or both.
IFB Operation
IFB operation between the two linked Eclipse-PiCos is supported by control macros.
Control Macros are a sales option. Access to Control Macro editor is restricted unless the customer has paid a license fee.
•Remote IFB Caller
To allow a panel on Frame1 to call an IFB on Frame 2, the user should create a dummy port on Frame 2 with the “Prevent reply key signalisation” option
checked, as well as an empty control.
The user should then assign a key on the panel on Frame1 to the IFB port on Frame 2, and stack the empty control onto the same key. A control macro should then be created, attached to the empty control, which uses the RouteToIfbOn() function to route from the dummy port to the IFB. When the key is activated the dummy route will cause the IFB dim to occur.
•Remote IFB Source
To allow a source on Frame1 to be added to an IFB on Frame2, the user should create a dummy port on Frame2 with the “Prevent reply key signalisation” option checked, as well as a route from the remote IFB source to the local dummy port. The user should then create a forced listen from the dummy port to the IFB in Local Advanced.
A control macro should then be created, attached to a dummy crosspoint to force the route from the remote IFB source to the local dummy crosspoint to be active at all times.
ISO Operation
Calls to the other frame’s ISOs are not supported across the High Speed Link.
Signalisation
•In use tally
Not supported between High Speed Linked systems for any audio construct.
•Incoming call tally
When a panel is called as a result of a route being made off a control or key press, the caller will be placed on the reply key. The entry on the reply key will always be the calling panel or 4 wire (as opposed to fixed group etc.) When a temporary member joins a conference no updates to the reply keys of the current members will be made.
•Reply Key
When a panel is called as a result of a route being made off a control or key press, the caller will be placed on the reply key. The entry on the reply key will always be the calling panel or 4 wire (as opposed to fixed group etc.)
When a temporary member joins a conference no updates to the reply keys of the current members will be made.
•Busy tally
Not supported between High Speed Linked systems for any audio construct.
•VOX present indication
Not supported between High Speed Linked systems for any audio construct.

CAN'T FIND YOUR ANSWER? CLICK HERE TO CONTACT SUPPORT


This solution was provided by Clear-Com via a question submitted to us by customers like you. If you wish to share with us a new solution or update an old one, please follow this link..


The information on this page is owned by Clear-Com and constitutes Clear-Com’s confidential and proprietary information, may be used solely for purposes related to the furtherance of Clear-Com’ business and shall not be disclosed, distributed, copied or disseminated without Clear-Com’s prior written consent. Click Here for Clear-Com's privacy statement.