Trilogy Communications Gemini User Manual

Download

Short Form User Guide

ISSUE 0.60

TRILOGY COMMUNICATIONS LIMITED

26 Focus Way

Andover

Hampshire

SP10 5NY

United Kingdom Telephone: +44 (0) 1264 384000 Fax: +44 (0) 1264 334806

www.trilogycomms.com

Short Form User Guide

Page 2 of 60 Trilogy Communications

The Copyright of the information and drawings in this document is the property of Trilogy Communications Limited of Andover, Hampshire and is neither to be reproduced in whole or in part, nor disclosed to a third party, without the prior written consent of Trilogy Communications Limited.

The information in this document has been carefully compiled and checked for accuracy. However, Trilogy Communications Limited accepts no responsibility for inaccuracies which may occur and, further, reserves the right to make changes to specification or design without prior notice.

Comments or correspondence concerning this manual should be addressed to the Publications Manager at the address given at the front of this User Guide.

DOCUMENT NUMBER 70090622.docx ISSUE 0.60

Issue

Date

Reason for Change

Approved

0.35

17 June 2011

Corrected typos

0.40

17 January 2012

Roles and Administrators

0.45

24 January 2012

Non-disruptive changes

0.50

30 January 2012

Updated screen grabs

0.60

14 May 2014

Password change

Short Form User Guide

Page 3 of 60 Trilogy Communications

Introduction ........................................................... 5

Before You Start ................................................ 5

Getting Started ...................................................... 6

Gemini Matrix .................................................... 6

Introduction to Gateway, the System Configuration

Editor ..................................................................... 8

Gateway Operational Methodology .................. 9

Tutorial 1: Configuring a Simple System .............. 11

Configuration – First Steps .............................. 12

Enterprise Editor .............................................. 12

Domain Editor .................................................. 12

Subscribers ...................................................... 14

Panel Editor ..................................................... 15

Upload and Restart the Configuration ............. 18

Control Panels ...................................................... 19

Panel Keys and Tallies ...................................... 19

The Panel Display ............................................. 20

Shift Mode ....................................................... 20

Loudspeaker Volume ....................................... 20

Rotary Encoders (RENs) ................................... 20

Assignable Features ......................................... 21

‘Cut’ Switch Features ....................................... 22

Extra Panel Features ........................................ 22

Tutorial Two – Understanding More Complex

Functions ............................................................. 23

Before You Start .............................................. 23

Permanent Crosspoints, or “Fixed Routes” ..... 23

Groups ............................................................. 24

Conferences, and Production Talkback ........... 26

.Production Talkback Conference – Operation

..................................................................... 27

IFBs .................................................................. 29

What Does This All Mean? ........................... 31

Dimming .......................................................... 32

Mirror Dimming ........................................... 32

Dimming Locations ...................................... 32

Configuring a System with more than one Matrix34

Before You Start ............................................... 34

Introduction to Systems With More Than One

Gemini Matrix .................................................. 34

High Speed Link (HSL) ................................... 34

Network ....................................................... 34

Tutorial 3 –Creating a Gemini Ring .................. 35

Configuration Changes ..................................... 36

Configuring a Multi-site System ........................... 37

Before You Start ............................................... 37

Introduction to Systems Operating over Multiple

Sites .................................................................. 37

High Speed Link (HSL) ................................... 37

Network ....................................................... 38

Network Audio ............................................. 38

Gateways and Routers ................................. 39

Tutorial 4 –Gemini Systems on Two Domains .. 39

Configuration Changes ................................. 40

Configuring a Gemini System for multiple

administrators ...................................................... 41

Introduction ..................................................... 41

Launching the Roles and Administrators Editor

......................................................................... 41

Creating Roles .................................................. 41

Creating Administrators ................................... 43

Associating Roles and Administrators .............. 44

Non-Disruptive Changes ...................................... 45

Introduction ..................................................... 45

Making changes ............................................... 45

Short Form User Guide

Page 4 of 60 Trilogy Communications

Appendix 1 – Basic Troubleshooting ................... 47

Appendix 2 – Key Types ....................................... 48

Appendix 3 - Interfacing to Mercury ................... 49

Interfacing to Mercury Hosts ........................... 49

Appendix 4 – Soft Panels ..................................... 50

Virtual Panels ................................................... 50

Patch Panels ..................................................... 51

Appendix 5 - POTS Telephony.............................. 52

Appendix 6 - Commander/Orator ........................ 54

Appendix 7 – A Basic Introduction to GPIO ......... 56

GPI -> Route ..................................................... 58

Route->GPO ..................................................... 58

Route->Route................................................... 58

Appendix 8 – Introduction to SIP ......................... 59

Appendix 9 – Comparison of Control Panel

Facilities ............................................................... 60

Short Form User Guide

Page 5 of 60 Trilogy Communications

Introduction

Gemini is a flexible intercom system, built on the concept of a de-centralised, scalable platform of 32 port matrices, each with IP connectivity. The 20 kHz audio performance is preserved both internally and over a Gemini network of up to 256 ports using a proprietary High Speed Link (HSL) using standard Cat 5 or fibre-optic connections. This approach eliminates the single point of failure associated with a traditional large matrix system, and the use of a dual redundant ring of audio and IP failsafe routing, ensures that Gemini delivers ultra-resilient performance.

Gemini’s flexible design is suited to every application ranging from small single studios to the largest multi-studio complex. Using Gemini’s seamless IP interfacing, a network can be expanded almost limitlessly both in terms of system size and geographic location via LAN, WAN or Satellite. Connectivity for both traditional and IP enabled intercom panels is provided, together with support for telephony, with intelligent interfacing to analogue and SIP enabled phone systems, as well as portable devices.

This document is provided to guide the system administrator through the configuration of typical systems, starting with a simple single-matrix system and culminating in a multi-matrix, multisite distributed system using IP connectivity.

Appendices are provided covering more advanced, but less commonly used functionality.

Before You Start

This guide assumes that the Gemini system, including any control panels, has been installed correctly, and that the Gateway configuration and database software is installed. The PC or laptop that has the Gateway software, and the Gemini matrix, should be connected to an IP Network.

Ports 1 - 32 High Speed Link + High Speed Link -

LAN

GPI

Fault Loop Alarm

Commander/Orator Networking Camera Mix/DA

Aux – Beltpack DC Power

32 IP Channels

Gateway

Configuration Editor

It may be useful to refer to other Gemini documentation

for more detailed information on the topics covered in this guide.

 Gemini Implementation Guide (document

70090620)

 Gateway Configuration Guide (document

70090621)

These documents are available on the product CD shipped with your system, or directly from Trilogy.

The Gemini Matrix

Refer to the Gemini Implementation Guide.

Short Form User Guide

Page 6 of 60 Trilogy Communications

Getting Started

Gemini Matrix

Apply power to your Gemini Matrix. It will take a short while to boot up and will then show the main menu.

The front panel display is equipped with a touchscreen, so no keyboard or mouse is required to configure the unit.

Press the SETTINGS button, followed by the SETUP button and check the IP Address, Subnet Mask and Database Server IP address have been configured.

Now launch a web browser programme on a PC connected to the same network as the Gemini matrix, and with an IP address in the same subnet – it might be most convenient to use the PC that runs the Gateway configurations software.

Type the IP address of the Gemini Matrix in the address bar and, if all the IP addresses have been entered correctly, a status page will be displayed.

“BACK” button. Returns to previous

menu.

“HOME” button. Returns to top menu.

STATUS menu. Allows the status of the

software, power supplies, fan, LAN and

HSL connections to be checked, and software revisions to be reported.

TOOLS menu. Audio monitoring, GPI

testing and monitoring, panel status and route information. Also allows the system

to be reset.

SETTINGS menu. Setup of IP addresses, “EDH” address and keypad click on/off.

INFO menu. Shows which option modules are fitted, as well as basic wiring

The name assigned to this Gemini matrix

The IP address of the matrix must be in the same range – or subnet – as that of the PC running the Gateway Software. For example, the PC might have IP address 192.168.10.10 (subnet mask 255.255.255.0) and the matrix perhaps 192.168.10.100. G

iven those IP

addresses, the Gemini matrix would have the Database Server IP address set to match that of the PC.

The addresses should have been configured

during system installation. Refer to the Gemini Implementation Guide.

Status and Alarm Indicator

Short Form User Guide

Page 7 of 60 Trilogy Communications

At this point, take time to explore the various tabs presented on the status screens, but do not be concerned about any error messages at this time. It is recommended not to make any changes yet.

The pages refresh automatically approximately every 10 seconds.

It is worth checking that the Gemini matrix is reporting an “EDHS” address of 0.1.1 (EDHS, and the relevance of this, will be explained later).

The default password for both the “admin” and

“debug” Settings pages is:

trilogy

At this point, the Gemini System is installed, connected and operational. Should it NOT be

operational, a short troubleshooting guide is available as Appendix 1.

Short Form User Guide

Page 8 of 60 Trilogy Communications

Introduction to Gateway, the System Configuration Editor

Gateway is the software application used to configure the Gemini system.

A “configuration” is all of the information needed for the matrix system to operate as required: IP addresses so they can communicate; declarations of the panels and other audio devices that are connected; what the panel keys should do; groups and conference functionality; and so on.

The configuration is stored in a set of database tables on a PC acting as a server. This database server may be the same one as that on which the Gateway editor is run, but it need not be.

The database is of a client/server design and is managed by a Windows service named “Trilogy Database Supervisor”. This service is loaded automatically every time the PC starts up, and it then runs in the background.

The client/server design means that multiple “clients” can connect simultaneously while the supervisor manages the reading and submission of data to and from the database, and provides file “locking” to prevent two clients attempting to change data at the same time.

In the context of Gemini, “clients” include the Gemini configuration editor itself as well as the Gemini matrices and any soft panels in use.

The Gateway Editor and Database Supervisor should already have been installed on a PC or laptop that is connected to the same network as the Gemini Matrix.

A small graphical application is also provided as part of the installation. This allows you to monitor the current status of the database and to perform routine maintenance and troubleshooting. It will launch automatically at start up. When it is run, a small additional icon will be displayed in the Windows system tray adjacent to the clock. On double clicking the icon, the database supervisor will be displayed.

This applications is available via the Start Menu and is called “DatabaseSupervisorGui.exe”

Start up the Gateway Editor on the PC.

If all is well, the Database Supervisor should now show that both the Gateway Editor and the Gemini Matrix are connected and operational.

A similar form is available by clicking the “Active Clients” button in the main Gateway editor window – this is described in Tutorial 1, as part of uploading and restarting the system to run a new configuration.

DB Supervisor icon

The default top level Administrator is:

Admin

The default password is:

trilogy

Short Form User Guide

Page 9 of 60 Trilogy Communications

Gateway Operational Methodology

Gateway has a number of principle areas within the main application window

The tree view list in the left hand pane is the main navigational tool within Gateway.

Where an entry has an arrow next to it, the tree may be expanded to show “children” of the parent.

To access a basic editor, single click on the required item. For example, to edit “Host 1.1” simply click once on the “Host 1.1” symbol in the tree view.

To access an advanced editor, double click on the symbol as appropriate

The selected editor will then appear in the Main Window to the right.

“MENU” button. Accesses all

menus such as “FILE” and “TOOLS”

Name of the current configuration,

and configuration version number

A tree view list of configured

functionality and

devices, and quick access to the main Gateway editor

tools.

Main Editor window.

“Standard” editors cover the majority of day-to-day activities for a system that is already configured and running “Advanced

” editors are needed during initial system

configuration and, later, for some more complex functions.

Click to launch the “Active Clients” window to connect to Gemini

system. The colour shows if the onscreen configuration has changed. GREEN in sync

RED - out of sync

Short Form User Guide

Page 10 of 60 Trilogy Communications

Once an editor is selected, a variety of editing methods are supported, depending on the activity being undertaken such as: drop-down selection boxes; “either/or” selection (or “radio” buttons); text entry; or drag-and-drop. These will be explained as necessary in the later section describing the configuration of a simple Gemini system. You can also right-click within many forms to call up a selection list.

Many editors have navigation buttons allowing quick access to the next “record” (for example, the next panel connected to the host). This tool bar also has “accept” and “reject” change buttons – note that any changes made are automatically accepted when you move on to edit something else, so if you want to reject a change made, you must click on the reject cross. A “refresh data” button at the end reloads the information stored in the database for that editor page should there be any doubt as to whether the page is current or not.

It is also useful to know that every menu item or button has a “tool tip”: if the mouse cursor is allowed to hover over a button, a brief explanation will appear.

Many editors also have “add” and “delete” buttons allowing, for example, an entire Gemini matrix unit to be added or deleted from the configuration. This tool bar also has a “grid options” button that allows, for example, displayed data to be exported (for documentation purposes, for example)

An example of “radio buttons”

A “tool tip” showing that the

circular arrow means “Refresh

Data”

Short Form User Guide

Page 11 of 60 Trilogy Communications

Tutorial 1: Configuring a Simple

System

This tutorial will walk through the initial configuration of a simple Gemini system.

It is recommended that you read all the preceding chapters first, to ensure you are familiar with the basic operational philosophy of the Gateway configuration editor, as well as making sure your Gemini matrix is operational, and that both are succesfully connected to the database supervisor.

A “Simple” system, or enterprise, for the purposes of this guide, means:

 A single Gemini matrix, or host in a single

domain

 No HSL audio connections  No use of IP audio

The tutorial will walk through the creation of a completely new configuration from scratch, including the addition and configuration of control panels and 4-wire ports – subscribers - and then we will upload the configuration to the matrix, restart the configuration on the system, and check that everything is working correctly.

Further sections in this guide explain control panels themselves covering:

 Key Operation  Tallies  “cut” switch functionality  The rotary encoder control, or “REN”

There are also more advanced tutorials explaining

 Fixed Crosspoints  Groups  Conferences and Production Talkback  IFBs  Dimming.

Enterprise; Domain; Host; Subscriber –

what’s that all about?

Since a Gemini system can comprise many

elements –

individual Gemini matrices,

perhaps installed over several sites, with a

large

number of control panels and other

audio devices – with the added complexity of

an IP network,, as well as the High Speed Link, it is necessary to have a numbering

system within Gemini that uniquely identifies all these elements.

The system employed is kn

own as the

“e.d.h.s” system:

 e=enterprise and is used to represent the

complete system. At present “e” is

always 0, but the adoption of “e” allows

for future expansion to assist interoperability between completely

different broadcasters, for example.

 d=domain

. A domain is a convenient

collection of devices, usually in the same

physical location, such as “studio 1”. They can be used to logically separate devices for convenience, but are also

essential when it comes to IP networks: this will be explained later

 h=host

where a host is an individual

Gemini matrix (or a Mercury device such as an “MIU”)

 s=subscriber

which, like a telephone

subscriber, is at the end of the line – the actual device used by the operator, such as a control panel, or an audio port.

Short Form User Guide

Page 12 of 60 Trilogy Communications

The Advanced Host Editor can also be

used to mark the host as “offline” – useful if a host will be added later, to avoid error messages in the meantime.

Configuration – First Steps

Start the Gateway configuration editor.

To be sure we’re working with a new, blank configuration, click the menu button and select the File menu and the choose New (refer to the section entitled “Gateway Operational Methodology” if you’re not sure where the menu button is.

Click Yes when asked if you’re sure you want to create a new configuration – although if another administrator has been working on a configuration is might be worth saving their work first – this can be done from the same File menu by choosing Save.

Enterprise Editor

Now single click the very top entry in the tree view (in the left hand pane of the editor) – it will be labelled Config<date> where <date> is today’s date. This opens up the Enterprise Editor, and we can give our new configuration a name – for example “Tutorial 1” and perhaps the description could be “Simple Gemini system configuration “.

No other changes are needed at the Enterprise level.

Domain Editor

Next, expand the tree view relating to Domains by clicking the arrow to the left, to reveal that the configuration has, by default, created a single domain called “Domain1. Expand the tree associated with Domain1 - the default configuration also includes 2 Gemini hosts – Host

1.1 and Host 1.2.

Single click on the Domain 1 element of the tree view to open the Domain editor.

Since this configuration only requires a single Gemini mattrix, Host 1.2 can be deleted if required by selecting the row it is shown on and clicking the “minus” button, which looks like this

Short Form User Guide

Page 13 of 60 Trilogy Communications

USEFUL TIP

When you have entered the first

“octet” (192 in this example) you can

move to the next field (where we’ll

enter 168 in this example) by

 Either pressing the tab key on the

keyboard

 or, since this is an IP address that

is separated by a a dot (or “full

stop”, or a “period”), you can press the “dot” key on the

keyboard

Port is the term used to describe the

physical connection on the back of the

Gemini matrix to which a panel, for

example, is connected.

Host 1.1 (the 1.1 means domain 1, host 1, as determined by the e.d.h.s numbering scheme), can be renamed if wished by clicking the name field associated with this host and entering your own name – perhaps “Gemini Matrix1” – along with a comment if so required.

The most important field to configure is the IP address. Without this being entered, the database supervisor will not be able to locate the correct Gemini matrix on the IP network.

The IP address must match the IP address given to the Gemini we’re configuring – this should have been noted in the earlier sections. For the purposes of this document, 192.168.10.100 will be used

Once the IP address is entered, it is good practice to click the tick in the navigation tool bar –

although changes will be saved automatically if you navigate away from this editor. Once confirmed, the IP address entered will also appear next to the host in the grid view.

The final step is to make sure that the Gemini Matrix itself is configured with the correct number of ports, of the correct type. You will need to refer to the shipping information or installion records if you are not sure exactly what your matrix is equipped with: this tutorial assumes just 8 ports.

Click on the “Type” field, and a list of possible host types will be presented: select an 8, 16, 24 or 32 port Gemini matrix as appropriate.

You may see a warning that changing the host type, or number of ports, will require subscribers to be added or removed – this is OK, so select Yes to proceed.

The actual port types for the matrix will almost certainly be correct, the default being “AEB”, or “Audio Expansion Board”, which support analogue control panels and 4-wire audio. In the event your matrix has other modules fitted, please refer to the full system documentation.

We now need to configure the subscribers to be the correct type.

Short Form User Guide

Page 14 of 60 Trilogy Communications

TIP: you can resize the width of

columns in the same manner as you can with spreadsheets –

move the

cursor to

the divider line between

column headings and either drag it to the required width, or double click it to automatically resize the column to a width appropriate to the length of the text entered.

Subscribers

Single click the host (Gemini Matrix1 in this example) in the tree view to launch the standard subscriber editor.

Click in the Type field for every port of your matrix and select the correct type from the drop down menu, according to your installation.

The two most commonly used port types are Panel and 4-wire. The different types of panels available, and their main differences are explained later, and virtual panels and patch panels are described in Appendix 4 – Soft Panels.

For each subscriber, a name should be entered. This name will be used on control panel displays when keys are assigned to speak or listen to the subscriber - it is worth bearing in mind that the majority of trilogy panels support 5 character labels, so choose appropriate abbrevations

By default, the labels are “H1S1” or similar, representing “Host 1, Subscriber 1”.

The Long Name is used on panels that support labels longer than the default 5 characters

It is good practice, although not essential, to enter a Description for each subscriber – this would typically be a full explanation of the subscriber including, perhaps, its location in the studio.

It is not necessary to enter text in the Lstn Label (the ”Listen” label) field.

For this tutorial, assign the first 4 ports as panels, and the second as 4-wires, labelling them like this:

The final task, before we have a basic, but functional, configuration is to add keys to panels.

What is a 4-Wire port?

“4-wire” is the term given to a simple audio source that has a balanced audio input and

balanced audio output. Balanced audio requires a pair of wires, each carrying the

audio signal but with opposite polarity – in electronic terms this means the signal can be received with minimum chance of electrical interference. Two pairs –

one pair for the

input and one for the output – results in “4 wires”. 4-wires carry no signalling information: they

are just audio. This means they cannot inherently cause a tally to illuminate on a control panel when the 4-wire audio source is speaking.

However, two basic mechanisms do exist to allow tallying:

 Audio presence detection  General Purpose Input/Outputs, or GPIO

These are briefly described in Appendix 7 – A Basic Introduction to GPIO.

Short Form User Guide

Page 15 of 60 Trilogy Communications

TIP: if you right-click in the tree view, menu options allow you to fully

expand, or fully coll

apse, the tree

view.

Panel Editor

Ensure the tree view on the left is fully expanded to show the configured subscribers.

Single click on the first of your panels to launch the panel editor.

There are a variety of methods provided for the configuration of panel keys, principally:

 Drag and drop within the panel editor  Dialogue box, then selection from lists. This is

selected by clicking within the KEY LABEL area to cause the “ellipsis” button to be displayed, then clicking the button to show the dialogue.

The LABEL of the selected target

Displayed key targets can be “dragged and

dropped” from the Available Targets palette

area to required key location above.

PAGE selection

Bin: drag keys

from the panel to

remove them

from the current layout.

COPY tools

Choose the type of target currently displayed,

e.g. panels, conferences. Each button has a

tool-tip.

Non-disruptive changes

Navigation tools

Roles and Administrators

File Management

KEY MODE: e.g. speak, listen etc.

Short Form User Guide

Page 16 of 60 Trilogy Communications

To configure panel keys, there are 3 main steps:

1. Choose the KEY TARGET TYPE: panel, 4-

wire, conference etc

2. Choose the actual KEY TARGET (for

example “panel 1” or “4-wire 1)”

3. Choose the key KEY MODE. The most

widely used are the first 4 choices from the menu, or a “QRS”:

 Speak. This key operates as a latching

speak key if you briefly press the key, otherwise it is a momentary speak, making a speak route only for the duration of the keypress. The upwards and downwards action of a lever-action key is identical

 Latching Speak. This key will always be a

momentary speak if the key is pressed downwards, and is always latching in the upwards direction.

 Listen. With a latching/momentary

operation the same as the speak key, but listening rather than speaking. generally not used for communications with panels, but useful for 4-wires.

 Speak/listen. Has the

latching/momentary characteristics of the speak key, but the downwards motion is for speaking and the upwards motion for listening.

 QRS. The QRS is a “quick response” key

that allows a reply to the most recent incoming call to be made without first having to locate the specifically configured key for that caller on the panel.

Now configure keys as required for the panels in your system. It is useful to note:

 Panel-to-panel intercom almost always

uses speak keys, with no need for corresponding listen keys at panels.

 Communications with 4-wires almost

always need a listen keys, but may need a speak/listen key.

 Gateway will automatically choose a

speak key for panel targets, and a listen key for 4-wire targets.

TIP: start typing a name in the

Available Targets window, and the

available targets will be filtered to match the text entered.

Key Types

Gemini offers an array of key types, all

of which may be selected from the

dialogue that pops up.

An explanation of all the available key types is given in Appendix 2 – Key Types.

TIP: if a non-graphical “grid” (i.e.

spreadsheet-like) editor is preferred, use the advanced panel editor.

For this tutorial, at the very least assign speak keys on the Director

panel to speak to Sound, and vice versa.

Short Form User Guide

Page 17 of 60 Trilogy Communications

Note that a second or “shift” page is also available, doubling the number of key targets that a given panel may have – the 2 pages available can be easily selected may have – the two pages available can be easily selected within Gateway

Before proceeding now is a good time to make a back up of the configuration. Do this by selecting File then Save Configuration from the menu button.

At this point, the Configuration, although basic, is functional and will work. Before learning

about more advanced functionality we will upload the configuration to the Gemini Matrix and

run it, to make sure it works.

NOTE: this operation is just taking a

copy of the data and saving it in a zip file. The configuration data is held within the database, managed by the database supervisor and is always up to date, so does not need to be saved via this file action.

Short Form User Guide

Page 18 of 60 Trilogy Communications

TIP: there is a preferences menu

accessible from the setup menu (use the menu button). From there you can set an option to cause an uploaded

configuration to always be

immediately run once the upload is

completed, rather than having to

confirm it each time.

Upload and Restart the Configuration

Click the Active Clients icon at the top right of the Gateway window. As well as showing any client that is connected to the database supervisor, there are two actions available from the tools on the left of the dialogue:

1. Upload – this sends the new

configuration to the host(s), but does not restart the system. The system continues to run its current configuration

2. Restart – the uploaded configuration is

activated. A short period of system disruption will occur before the new configuration runs.

Select Upload. Once this process has completed, a dialogue will ask you to confirm that you wish to “go live” with the configuration – click on Yes. The system will then restart and the new configuration will be running.

Check the keys on your panel(s) to confirm that they are, indeed, as configured: assuming so, you have successfully completed tutorial one, and are now able to configure a simple Gemini system.

The configuration created during the tutorial is

available on the product CD, called “Tutorial1_finished.trilogy”

Tutorial two will cover the use of Groups and Conferences, Production Talkback, IFBs and dimming, but we will now take a quick look at control panels to understand how they operate.

Short Form User Guide

Page 19 of 60 Trilogy Communications

Control Panels

This section explains the functionality available on Gemini intercom panels. The follow topics are covered:

 Panel Keys and Tallies  Panel Display  Working in the ‘Shift’ Mode  Loudspeaker Volume  Panel Encoders  Assignable Features  Cut Switch Features  Extra Panel Features

Panel Keys and Tallies

All keys on panels connected to the Gemini system are configured on a key-by-key basis, using the Gateway configuration software.

The function of a panel key can be either: Listen; Speak; Listen and Speak; IFB; or a Phone key type.

Each panel key can also be programmed to either be latching (the function remains active when the key is momentarily pressed) or momentary (the function is only active whilst the key is pressed).

Associated with each key are two Tally lamps; one red and one yellow:

 The red lamp indicates when you are speaking  The yellow lamp indicates when you are

listening.

The yellow lamp has a further function to indicate when there is an audio 4 wire source present at the panel. If the signal presence option is enabled in the Gateway advanced panel editor, the yellow lamp will flash at a medium rate if the audio is present and the key is not selected to listen to the source.

To listen to the source, a key type with a listen function should be assigned in the Gateway editor. The key is pressed up to listen, and the yellow tally will go solid yellow to indicate you have selected the audio source.

Panels Currently Supported by Gemini

 700-30-50B 24 lever key, 2U panel.  700-31-00B 16 lever key, 2U panel.  700-31-51B 16 lever key plus dial-pad 2U

panel.

 700-33-00B 32 lever key, 2U panel.  700-41-xx 8 lever key desktop panel.  700-42-01 8 button Callstation.  700-42-50B 1U, 10-lever key panel fitted

with 5 character LED displays.

 700-45-00B 8 button vacuum fluorescent

display, 1U panel.

 700-46-00B 10 button, LC key, 1U panel.  700-37-00 30 button, 2U touch-screen

panel.

 700-47-00 20 key, desktop touch-screen

panel.

A table comparing the panels in more details is provided in Appendix 9 – Comparison

Short Form User Guide

Page 20 of 60 Trilogy Communications

TIP: Gateway has a User Label

function available in the Advanced Panel Editor. This allows the label on a key of a specific panel to be different to the generic speak or listen label entered in the basic editor.

NOTE: The Advanced Panel Editor can

be used to set a “minimum” level or “hold off” to prevent the volume being inadvertently reduced to zero.

The Panel Display

The five-character label shown on the display next to each key shows the key’s assigned target – either the destination that will be spoken to, for a speak key, or the source that will be listened to, for a listen key.

Shift Mode

If you press the panel’s ASSIGN/SHIFT key downwards, a yellow lamp next to the Shift label indicates that you are in shifted page mode and a second page of keys becomes available.

To return to the main page, simply press the ASSIGN/SHIFT key DOWN again.

Note that the shifted keys can have a totally different set of functions to the main page, for example; Key 1 on the main page could be a speak key to, for example, the Director whereas Key 1 on the shifted page could be a listen and speak key to Camera 1.

Loudspeaker Volume

The knob on the panel with the VOL legend controls the loudspeaker or headset volume.

Rotary Encoders (RENs)

The Rotary Encoders or RENs are the knobs that are provided with a single red LED on the front panel.

By default, when you select a listen key to a 4 wire on the panel, or receive an incoming call, the lamp next to the encoder will light for ten seconds. This allows the user to adjust the listening level of the source audio to a preferred level.

The REN is also used during locally assignable functions.

Short Form User Guide

Page 21 of 60 Trilogy Communications

NOTE:

 It is possible to reassign more

than one key on a panel.



Locally assigned keys are not

stored on the system, so if the

system is rebooted, all local

assignments are cleared.

 The yellow tally on the ASSIGN

key will remain ON to indicate that a key or keys have been reassigned on the panel.

Assignable Features

A useful feature of the standard panel is the ability to locally reassign keys on the panel. This feature can be barred on a key by key basis from the Gateway software if required.

To reassign a key: -

 Press the Assign/Shift key UPWARDS. The

Assign lamp will now flash.

 Choose the key you wish to reassign by

pressing DOWN on that key. The red and yellow tally lamps will flash simultaneously.

 Use the encoder to choose the reassign

option, the choices are as follows:

 TYPE> Allows the user to change the key type

assigned for the key selected.

 SUBS> This option allows the operator to

assign the key to another subscriber or port on the system. When selected, the display shows the first available port. Scroll through the port list using any REN. Continue through the list until the target appears, e.g. DIR for Director. Press the key DOWN to select this target as the new key assignment.

 GRP> Allows the operator to assign the key to

another Group assigned in the Gateway editor.

 CONF> Allows the operator to assign the key

to another Conference assigned in the Gateway editor.

 IFB> Allows the operator assign the key to

another IFB assigned in the Gateway editor.

 PHN> Allows the operator to assign the key to

another Phone Group assigned in the Gateway editor.

 RTE> Allows the operator to assign the key to

another Route assigned in the Gateway editor.

 CLR> Allows the operator to clear the key

target.

 RLD> This option Reloads the panel’s key

assignments back to those originally configured from the Gateway editor.

 ME?> Displays the panel name as assigned in

the Gateway editor.

 EXIT> Exit the key assignment menu.

Short Form User Guide

Page 22 of 60 Trilogy Communications

‘Cut’ Switch Features

Depending on the panel type the CUT switch on the front panel can be either configured from the Gateway Panel Advanced Editor or via DIP switches accessed via the top cover of the panel.

As standard the Cut switch is set to mute the panel microphone when the switch is depressed (the cut switch will illuminate when engaged). Where configuration via Gateway is possible, you can set the cut switch, instead, to:

 No panel microphone cut, or  Headset changeover. In this mode, pressing the cut switch will mute the panel loudspeaker and switch

between the panel and headset microphone. Note that the headset earpieces will be active at all times.

If the panel has the dip switches on the top edge of the panel the following modes can be set: -

DIP 1

DIP 2

DIP 3

No Action

OFF

CUT activated

OFF

LS cut only

OFF

Mic cut only

OFF

LS and Mic Cut

X=”don’t care”; the position of the switch is not important

Extra Panel Features

On the rear of the standard Trilogy panel range are connectors to allow access to extra features within the panel. These include local logic inputs and outputs, footswitch connection and audio inputs and outputs. Please refer to the Gemini Implementation Guide for further details.

Short Form User Guide

Page 23 of 60 Trilogy Communications

CREATING THE STARTING

CONFIGURATION FOR TUTORIAL TWO

Create:

 A single Enterprise (called Tutorial 2)  A single domain (called Domain 1)  Single Gemini Matrix (called Gemini

Matrix 1

) with an IP address that

matches the Gemini matrix of your system

 Ports 1-4 as panels, labelled:

1. DIR

2. SND

3. PA

4. PROD

 Ports 5-8 as 4-wires labelled:

5. CAM01

6. CAM02

7. FM

8. PGM

Tutorial Two – Understanding

More Complex Functions

Before You Start

This tutorial presumes the existence of a basic configuration with panels and 4-wires declared. It was created during Tutorial 1 and is available on the product CD as “Tutorial2_start.trilogy”, or you may create it following the list on the right.

Permanent Crosspoints, or “Fixed Routes”

The Routes Editor allows for complex conditional control of audio routes, often using GPIO. This functionality is briefly covered in

Appendix 7 – A Basic Introduction to GPIO, but a common requirement is a simple permanent crosspoint: a route that exists at all times. This is accomplished in Gateway using a “fixed route”.

To add a fixed route, invoke the Basic Routes Editor by single clicking Routes in the tree view.

A fixed route is added very simply:

 Add a route entry using the add button  select the required source in the Source

column

 select the required destination in the

Destination column

 Ensure the checkbox in the column headed

Fixed is checked.

The default label given to the route created is the source label followed by the destination label, separated by a double colon. This can be edited if required, but route labels rarely appear on panels.

Short Form User Guide

Page 24 of 60 Trilogy Communications

Groups

A Gemini Group is a convenient method of providing “one-to-many” communication: the ability to speak to multiple destinations simultaneously from a single panel key.

Groups can also be used to listen to multiple sources (“many-to-one”) and, if wished, “many-tomany” communication.

By default, two Groups are added to a new configuration.

To add more Groups, invoke the Basic Group Editor by a single click on the top entry of the Group list in the tree view (labelled Groups). Use the “add” button to create more Groups as required.

Starting with the “Tutorial2_start.trilogy” configuration, we will now explore Group configuration by invoking the Basic Group Editor.

Expand the Group tree view on the left so that the default Group is shown and single click the first group, named by default GRP1 to access the Group Editor

“TARGETS” – the audio

destinations that CALLERS will communicate with – the group “MEMBERS”

“CALLERS” – the audio sources that will communicate

with the TARGETS.

This side is “read only” and simply shows panels that

have keys assigned

to the group

members.

Short Form User Guide

Page 25 of 60 Trilogy Communications

Groups and IP channels Later tutorials cover systems comprising more than 1 Gemini matrix and the use of IP audio

between sites, or in the event that the High Speed Link fails. Note that a group call uses one IP channel for every target in the list that is on a different host to the calling panel.

Groups comprise two lists: Targets; and Callers.

Targets are added to the Group using the Basic Group Editor, whereas Callers are inferred and displayed within the editor when panel keys are assigned to the group.

Edit the group as follows:

 Name “ALL”  Long Name “Call All”  Comment “Director’s Call All”  Add ports 2 through 8 as targets.

Now edit panel 1 (DIR) by single clicking on the tree view entry for that panel, and add a key on the panel targeting this group by selecting the Group symbol from the available targets list. The tutorial assumes this is on key 5, but the actual key is not important.

Return to the Basic Group Editor by single clicking on the ALL group in the tree view, and you will observe that the Director’s panel is now listed in the Callers window.

When the Director presses the speak key that targets the ALL group, audio routes will be established from the Director’s panel to all 7 other subscribers added as targets.

If wished, you can upload this configuration and restart the Gemini Matrix to see the Group in operation.

TIP: If you want to select 2 or more

items from a selection dialogue, you can use the standard Windows multiselect method by using the shift or control keys

If a listen were assigned instead, the

Director would be able to listen to multiple sources – this is normally only used to listen to 4-wires rather than panels of course.

Short Form User Guide

Page 26 of 60 Trilogy Communications

Production Talkback (PTB)

Production Talkback is the name often given to the communications function used during programme making, allowing the Director to speak directly to the cameras, sound

desk, etc, without having to press a key to speak – he has an “open microphone”.

Operators who listen to the Director via Production Talkback may be provided with the ability to speak back to the production talkback if required, but this

privilege need not be granted.

Conferences, and Production Talkback

A Gemini Conference is a convenient method of providing “many-to-many” communication: the ability for multiple panel operators to speak and/or listen to many 4-wires and for panel operators to communicate with each other simultaneously, using a single key per panel.

Compared to Groups, there is greater flexibility in the way conference participants interact making them especially useful for Production Talkback.

By default, two Conferences are added to a new configuration.

To add more Conferences, invoke the Basic Conference Editor by a single click on the top entry of the Conference list in the tree view (labelled Conferences). Use the “add” button to create more Conferences as required.

Starting with the “Tutorial2_start.trilogy” configuration, we will now explore Conference configuration by invoking the Basic Conference Editor.

Expand the Conference tree view on the left so that the default Conference is shown and single click the first conference, named by default CNF1 to access the Conference Editor

“4-WIRE MEMBERS”

– 4-

wires can be

added or removed

from the conference here, and for each 4-

wire the speak

and/or listen mode set..

“Panel members” –

the panels that have

keys targeting the conference, along with their speak

and/or listen mode.

This side is “read only” and simply shows panels that have keys assigned

to the conference.

Short Form User Guide

Page 27 of 60 Trilogy Communications

Conferences comprise two lists: 4-Wires; and Panels.

4-wires are added to the Conference using the Basic Conference Editor, whereas Panels are displayed for convenience within the editor when panel keys are assigned to the conference.

Edit the conference as follows:

 Name “PTB”  Long Name “Production Talkback”  Comment “Production Talkback”  Add 4-wire ports 5 through 8  Edit the “Mode” for the Floor Manager to be

“Listen”

 Edit the “Mode” for Programme Sound to be

“Speak”

Now edit panel 1 (DIR) by single clicking on the tree view entry for that panel, and add a key on the panel targeting this conference by selecting the Conference symbol from the available targets list. The tutorial assumes this is on key 6, but the actual key is not important.

 Change the key type to “default speak,

default listen”

Repeat for the other 3 panels in this configuration, but change the key types as follows:

 Sound and Production panels to default listen,

momentary speak

 PA panel to default listen

Return to the Basic Conference Editor by single clicking on the PTB conference in the tree view, and you will observe that all the panels are now listed in the Panel Members window, and their speak/listen modes are displayed.

TIP: If you want to select 2 or more

items from a selection dialogue, you can use the standard Windows multiselect method by using the shift or control keys

Short Form User Guide

Page 28 of 60 Trilogy Communications

Production Talkback Conference – Operation

In summary, the PTB we’ve configured has the following speak/listen modes:

 Panels

 Director Default Listen/Default Speak  Sound Default Listen/Momentary Speak  PA Default Listen  Producer Default Listen/Momentary Speak

 4-wires

 Cameras Speak/Listen  Floor Manager Listen  PGM Sound Speak

When the configuration is uploaded and started, Cameras and Programme Sound, being 4-wires, will immediately be contributing to the PTB conference. Usually the camera operators will have a push-to-talk button so their audio will not actually be contributing to the conference at this time, but the audio route (or “crosspoint”) will be made in the Gemini matrix

The Director’s panel has a key that defaults to speaking and listening – the director will have an open microphone and will be able to speak to all listening members without having to push the key and, likewise, will be listening to anyone who speaks back to PTB.

Sound, PA and the Producer panels all have default listen keys and will be being able to hear PTB without having to select a key.

Sound and the Producer panels have the ability to speak back to PTB with a momentary key.

Floor Manager (4-wire) can only listen to PTB, whereas Programme Sound is simply a permanent contributor to PTB

If wished, you can upload this configuration and restart the Gemini Matrix to see the Conference in operation.

NOTE: Conferences and IP

channels

Later tutorials cover systems comprising more than 1 Gemini

matrix and the use of

IP audio

between sites, or in the event that the High Speed Link fails.

Note that a conferences uses IP multicast rather than unicast,

meaning only a single IP channel is used from a speaking member to all other listening members. This is much more efficient than Groups.

IMPORTANT NOTE.

Gemini Conferences, by default,

limis the number of members that may simultaneously speak to two.

This can be changed by invoking

the Advanced Conference Editor.

Short Form User Guide

Page 29 of 60 Trilogy Communications

WHAT IS AN IFB?

An IFB –

or Interrupted Feedback (sometimes

known as interrupted foldback)- is an intercom circuit that consists of a 4-wire feed sent to a destination which can then be interrupted and replaced by a different audio feed.

Typical usage might be that the destination port

is an earpiece worn by a presenter, with programme sound normally being fed to it, which may then be interrupted when the director or producer wishes to speak to the

presenter.

The audio feed can either be interrupted

completely or simply attenuated – dimmed – to a lower level.

IFBs

By default, a single IFB is added to a new configuration.

To add more IFBs, invoke the Basic IFBs Editor by a single click on the top entry of the IFB list of the tree view (labelled IFBs). Use the “add” button to create more IFBs as required.

Starting with the “Tutorial2_start.trilogy” configuration, we will now explore IFB configuration by invoking the Basic IFB Editor.

Expand the IFB tree view on the left so that the default IFB1 is shown and single click it to access the IFB Editor.

IFBs are often daunting at first, so we will configure this IFB and then explain how it will operate in practice.

“SOURCES” – the

audio feeds (inputs)

that are usually

routed to the DESTINATIONS, and

that will be interrupted.

“DESTINATIONS” – the audio outputs

the SOURCES are

usually routed to

until interrupted.

A list of sources that

will interrupt audio

routed from the

sources to the destinations.

When sources are

added here, they will

cause an interrupt whenever, and

however, a route is

made from the

interrupt source to the destinations.

Interrupts can be panels, or GPIO

triggers.

Determines whether

sources

, when

interrupted

are cut or dimmed and, if dimmed, by how

many decibels

This is a list of panels that have keys assigned to target

the IF

B directly, rather than indirectly through having been added

to the interrupts list

Diagrammatic representation of an IFB action

The IFB level is an advanced function that provides a priority

system. When an interrupt trigger occurs, not only is the source port interrupted, but also any interrupt sources of lower priority than the interrupting source will be cut or dimmed too.

Short Form User Guide

Page 30 of 60 Trilogy Communications

First, we will add a key on the Producer’s panel (port 4 of the tutorial configuration) targeting IFB1. Do this via the basic panel editor, selecting the IFB symbol from the available targets list. The tutorial assumes this is on key 5, but the actual key is not important.

Similarly, add a speak/listen key on the Sound (SND) panel to speak to the Floor Manager (FM)

Select the IFB Basic Editor again. You will now see that the IFB Key Interrupts window now lists the Producer panel.

It is good practice to give the IFB a long name – such as, for this example, Floor Manager IFB.

Configure the following:

 IFB Source as Port 8 (Programme sound, or

PGM)

 IFB Destination as Port 7 (Floor Manager, or

FM)

 Interrupts as Director (DIR) and Sound (SND)

– you will need to choose the Add Interrupt option when adding them, rather than GPI or

GPO

 Change the level of the Director’s interrupt to

Level 2

Short Form User Guide

Page 31 of 60 Trilogy Communications

What Does This All Mean?

Referring to the IFB1 screen:

 Normally, programme sound (the IFB Source

is being fed to the floor manager audio output (the IFB Destination).

 It is not necessary to make this route

in any other way – declaring the IFB source and destination in the editor causes the route to be made when the configuration is run.

 The Producer panel has a key targeted at IFB1.

If this key is pressed to speak to IFB1, the Producer panel audio will replace the programme sound audio the floor manager was hearing.

 The Sound panel has a key targeted directly at

the floor manager. If this key is pressed, to speak to the FM, the Sound panel’s audio will replace the programme sound audio the floor manager is hearing.

 The Director does not currently have a key

targeting either IFB1, or the FM directly. However, by including this panel as an IFB Interrupt, we can ensure that if a key were to be assigned to the IFB or FM - perhaps by locally re-assign at the panel itself -then it would be an IFB interrupt trigger

 If the Director speaks to the Floor Manager,

because it is declared as a Level 2 trigger, not only would the source (programme sound) be cut, the lower priority Sound panel would also be cut, and could not speak to the FM while the Director was speaking.

If wished, you can upload this configuration and restart the Gemini Matrix to see the IFB in actual operation.

What is the difference between “Interrupts”

and “IFB Key Interrupts”?

 Sources added as “interrupts”

relate to

routes made directly to the associated IFB destination (FM in this example). If the IFB destination is changed there will either be

no IFB action, or keys will need to be

reconfigured as well.

 Keys targeted at the IFB itself will act as

triggers regardless of what actual ports are configured in the IFB as destinations. The

destinations can be changed without

having to reconfigure IFB-related keys on panels)

Best practice is to target keys directly at the

IFB.

Short Form User Guide

Page 32 of 60 Trilogy Communications

Dimming

Gemini provides two main dimming techniques to control howlround:

1. Mirror dimming

2. Dimming Locations

Mirror Dimming

Howlround only occurs when a full duplex communication path exists between two panels, and the Gemini software automatically detects this scenario.

If detected, attenuation is automatically applied to both audio routes. The attenuation is very effective at eliminating the feedback and therefore prevents howlround.

This type of dimming is also called “mirror dimming”,

By default, 12dB of attenuation is applied to the audio route, but this can be adjusted if required using the Advanced Panel Editor. The Basic Host Editor can also be used to alter dimming values on a per-subscriber basis.

Dimming Locations

Gemini uses Dimming Locations to deal with the complex scenario where 3 or more panels are causing the howlround condition.

A Dimming Location is an area, or a room, within the installation where 2 or more panels are in close proximity and might be the cause of the complex howlround situation described in the callout.

What causes howlround?

Howlround is the unwanted howling noise that can occur when a microphone picks up sound from the speaker that the microphone is feeding. On stage this is because the microphone is too close to the loudspeaker.

In a talkback system, howlround occurs when the audio

from the microphone on one panel is received at

another panel and then picked up by that panel’s microphone and fed back to the original panel. An infinite feedback loop is created, and howlround is the result.

Talkback systems are particularly prone to howlround since there are often occasions when “full duplex” communications occurs. This can be when two panels both have latched-on speak keys to each other, or it can be just for a brief moment when one the speak key on one panel has not quite been released before the other panel replies.

There is a third, more complex situation, where

howlround can occur. This is when there are two panels in close physical proximity, and audio from one of those panels’ speakers is picked up by the other, close, panel. If that audio is then conveyed to a remote panel and picked up by it’s microphone, and sent back to the first panel, a feedback loop involving all three panels can

occur.

Mirror dimming. This term is derived from the

traditional crosspoint diagrams that were used to depict talkback systems. Sources and destinations provide the axes of an X-Y grid, and symbols are used to depict crosspoint at the intersection of a source and destination

The two crosspoints that represent

the Director

connected to Sound and vice versa, are the mirror of each other about a diagonal line. “Mirror Dimming” is the automatic application of attenuation when those “mirror crosspoints” are detected.

Directo r 

Sound 

Produc er

CAM1

CAM2

Floor

Prog Snd

Directo r

SoundPAProduc er

CAM1

CAM2

Floor

Prog Snd

SOURC ES

DESTINATIONS

Short Form User Guide

Page 33 of 60 Trilogy Communications

The following rules apply to Dimming Locations:

 Panels within a Dimming Location must all

belong to the same Gemini matrix

 A panel may only belong to 1 Dimming

Location;

 A Dimming Location can be configured as a

‘Master Location’. Panels within a master location are those which will not have routes dimmed when the complex howlround scenario occurs (i.e. it is panels in non-master locations that will have their audio dimmed)

 When any panel in a non-master Dimming

Location speaks to any panel in the “master” Dimming Location, and any panel in the master Dimming Location is already speaking to any panel in the non-master Dimming Location B, then all audio routes from panels in the master location to those in the non- master location will be dimmed.

In the scenario depicted here, if Panel A is speaking to Panel C, then when Panel C speaks to Panel B, it is the route from Panel A to Panel C that is dimmed.

To use Dimming Locations:

 Add Dimming Locations using the Advanced

Enterprise Editor

 Choose the host that the dimming locations

will belong to

 Ensure that check box is selected for Master

locations – those locations where routes to panels are not to be dimmed.

 Use the Basic Host Editor to assign panels to

the dimming locations.

In the example here, the Director and PA are in a Master Location, and the Sound panel in a different location. If the Director is speaking to Sound, and Sound speaks to the PA, the route from the Director to Sound will be dimmed.

Non - Master

Location

Master

Location

Short Form User Guide

Page 34 of 60 Trilogy Communications

Configuring a System with more

than one Matrix

Before You Start

This section assumes that the Gemini system, including any control panels, has been installed correctly, and that the Gateway configuration and database software is installed. The PC or laptop that has the Gateway software, and the Gemini matrices, should be connected to an IP Network.

It is highly recommended that you complete Tutorial 1, to gain a thorough understanding of the configuration of a simple single-matrix Gemini system as well as the Gateway editor itself.

Introduction to Systems With More Than One Gemini Matrix

High Speed Link (HSL)

The key to systems using more than one Gemini Matrix is the High Speed Link, or “HSL”.

The HSL provides the bidirectional, low latency mechanism for transporting audio channels between Gemini matrices. For enhanced resilience, the HSL may be connected as a redundant ring, either using conventional CAT5/CAT6 cable for up to 100 metres or over unrestricted distances via an optical fibre link. This ensures that the system is tolerant of a break in any segment of the linkwith no loss of audio traffic between the matrices.

Further resilience may be provided by use of IP audio, but this is covered in a later section.

Nevertheless, an IP network between Gemini matrices is a necessity, since it is used for all realtime data communications between the matrices.

Network

Gemini is designed to connect to any 10/100baseTX Ethernet network with provision to support both static & DHCP IP addresses.

Matrices can be connected over LAN, WAN, Internet & satellite on standards based IP architecture. Typically, the system operates on networks and WAN segments that include other video, data & voice traffic. It uses 'heartbeats' to ensure network robustness and supports IEEE

802.1p prioritised packet switching, IEEE 802.1q VLAN 12 bit identifiers and RFC2474 Differentiated Services to allow precise network control of traffic.

When considering network requirements for Gemini operation over IP, be aware that you will need to open ports UDP 2076 & UDP 2077 if the network has firewall protection between the Gemini hosts.

Short Form User Guide

Page 35 of 60 Trilogy Communications

Tutorial 3 –Creating a Gemini Ring

This tutorial will use as its starting point the configuration that has been created during tutorials 1 and 2. It is available on the product CD as Tutorial3_start.trilogy. We will assume that the system comprises 2 matrices.

Both Gemini Matrices should have had their IP address configured as described in Tutorial 1, and it is recommended that you use a Web Browser to confirm that both matrices are operational and the network is connected correctly.

It is also imperative that both matrices have correct E.D.H. addresses: the first should be 0.1.1 and the second 0.1.2.

Launch the Gateway Configuration Editor and click the “Active Clients” button and confirm that both Gemini units are showing.

EDHS - Enterprise, Domain, Host,

Subscriber

Since a Gemini system can comprise many

elements –

individual Gemini matrices, perhaps installed over several sites, with a large number of control panels and other

audio devices – with the added complexity of an IP network as well as the High Speed Link, it is necessary to have a numbering system

within Gemini that uniquely identifies all

these elements.

The system employed is known as the

“e.d.h.s” system:

 e=enterprise and is used to represent the

complete system. At present “e” is

always 0, but the adoption of “e” allows

for future expansion to assist interoperability between completely

different broadcasters, for example.

 d=domain

. A domain is a convenient

collection of devices, usually in the same

physical location, such as “studio 1”.

They c

an be used to logically separate

devices for convenience, but are also

essential when it comes to IP networks: this will be explained later

 h=host

where a host is an individual

Gemini matrix (or a Mercury device such as an “MIU”)

 s=subscriber which, like a telephone

subscriber, is at the end of the line – the actual device used by the operator, such as a control panel, or an audio port.

Short Form User Guide

Page 36 of 60 Trilogy Communications

Configuration Changes

 Launch the Advanced Enterprise Editor by

double clicking the name of this Enterprise at the top of the tree view on the left (“Tutorial

3” if you’re using the configuration from the product CD) and select the tab labelled

Gemini Rings. Add a single Gemini Ring by clicking the “add” button, calling it, for example, “Gemini Ring 1”.

 Launch the Basic Domain Editor by expanding

the tree view and single clicking on Domain 1

 Name the second Gemini Host

“Gemini Matrix2”

 Edit the IP address of the second

Gemini Host to match that assigned to the matrix via its front panel.

 Select “Gemini Ring 1” for both hosts

using the column at the far right of the grid.

 Launch the Basic Host Editor for Gemini

Matrix2, by single clicking its entry in the treeview. Add subscribers as required: for the purposes of this tutorial we will simply add a single panel on port 1, leaving the default label “H2S1” (Host 2, panel 1) to prove that the HSL is working.

 Launch the Basic Panel Editor and add a key

on the Director panel on the first Gemini matrix in the ring, targeting our new panel H2S1 and, likewise, a key on panel H2S1 targeting the Director panel.

 Upload and restart the configuration and

check that the Director panel can speak to H2S1 and vice versa.

Note: you may need to change the host “type” to match the Gemini matrix actually installed

The two-matrix Gemini System is now operational. The configuration created in this tutorial is

available on the product CD as Tutorial3_finished.trilogy

Short Form User Guide

Page 37 of 60 Trilogy Communications

Configuring a Multi-site System

Before You Start

It is highly recommended that you complete both Tutorial 1 and Tutorial 3, to gain a thorough understanding of the configuration of a simple single-matrix Gemini system as well as the Gateway editor itself.

Introduction to Systems Operating over Multiple Sites

High Speed Link (HSL)

Within a given building, audio is most effectively transported between Gemini matrices using the High Speed Link, or “HSL”.

The HSL provides the bidirectional, low latency mechanism for transporting audio channels between the required Gemini units. For enhanced resilience, the HSL may be connected as a redundant ring, either using conventional CAT5/CAT6 cable for up to 100 metres or over unrestricted distances via an optical fibre link. This ensures that the system is tolerant of a break in any segment of the link, with no loss of audio traffic between the matrices.

When an installation spans multiple sites, it can prove impractical to run a fibre or CAT5/CAT6 cable between sites.

Gemini is equipped with an Ethernet interface as standard – IP is used for all real-time data communications between the matrices – and by the addition of an appropriate hardware module, audio, too, can be sent over the network.

The IP network can also be used to send audio between Gemini matrices within a single site. This is most often used for “fail safe” redundancy should the HSL interconnects fail or run out of capacity.

Short Form User Guide

Page 38 of 60 Trilogy Communications

Network

Gemini Matrices can be connected over LAN, WAN, Internet & satellite on standards based IP architecture. Typically, the system operates on networks and WAN segments that include other video, data & voice traffic. It uses 'heartbeats' to ensure network robustness and supports IEEE

802.1p prioritised packet switching, IEEE 802.1q VLAN 12 bit identifiers and RFC2474 Differentiated Services to allow precise network control of traffic.

When considering network requirements for Gemini operation over IP, be aware that you will need to open ports UDP 2076 & UDP 2077 if the network has firewall protection between the Gemini hosts.

Compared to the earlier tutorials, the two new network considerations are Network Audio and Gateways and Routers.

Network Audio

Bandwidth profiles allow selection of a variety of audio compression codecs along with control of the way the audio is carried in an IP packet. Gemini provides 20 preset “coding profiles” that combine these parameters to provide a specific IP payload, ranging from 10kbps to 100kbps, allowing audio quality, network bandwidth and latency to be optimised for any given network.

Simplistically:

 On a Local Area Network, especially if it is

dedicated to Gemini, G.722 using 10ms of audio per IP packet gives the highest quality, lowest latency audio.

 On a Wide Area Network, especially if the

network is shared with other traffic, G.729 is a great compromise.

 Where bandwidth is severely compromised –

perhaps over a satellite link – G.723 is the only viable option.

Audio CODECs

G.711 is a Pulse code modulation (PCM) of voice

frequencies on a 64kbit/s channel. G.711 uses a sampling rate of 8kbit/s. Non-uniform quantization with 8 bits is used to represent each sample, resulting in a 64kbit/s bit rate.

Pros

: Designed to deliver precise

transmission of speech, very low

processing overheads.

Cons: Poor network efficiency

G.722 is a wideband speech codec operating at

64kbit/s. Technology of the codec is based on split band ADPCM.

Pros: useful in fixed network voice over IP applications, whe

re the required

bandwidth is typically not prohibitive. A

significant improvement in speech quality over G.711, with a small

encoding delay of <3ms.

Cons: not ideal over WAN.

G.723.1 is a speech codec that compresses voice

audio in 30ms frames. An algorithmic look-ahead of 7.5ms duration means that total algorithmic delay is 37.5ms.

Pros:

very high compression whilst

maintaining high quality audio. Cons: computationally intensive; 37.5ms encoding delay. Not well-suited to music or sound effects

G.726 is an

ADPCM speech codec for the

transmission of voice at rates of (usually) 32kbit/s.

Pros: Uses 32kbits which is half the rate of G.711 codec and hence increasing the usable network capacity by 100%. Used

on international trunks in the phone

network. Cons: Not well-suited to music or sound effect.

Packet Size

Gemini allows either 10ms, 20ms or 30ms of audio to be sent in each IP packet. Very simply, the more audio that is sent, the fewer the packets that need to be sent, so network efficiency is increased, but

latency also increases as more audio must be

accumulated before it is sent.

The combination of CODEC –

and the implicit

algorithmic delay for each type - and Packet Size, is the predominant factor determining latency.

Short Form User Guide

Page 39 of 60 Trilogy Communications

Gateways and Routers

Gemini Matrices in earlier tutorials were on the same IP subnet – the IP addresses were in the same “range”.

This means in practice that the network devices readily “see” each other. A network message may be sent out directly to the destination IP address, and the network switching topology allows it to reach its intended destination with ease.

Once network devices are connected by a wide area network, it is highly likely that each site has its own IP address range: it’s own subnet. If an IP message is sent from a device on one subnet to a device on a different subnet, the basic network switching devices do not know where to route the packets.

The IP networking device used to discover how to route packets in this scenario is a “router”. Router functionality is outside the scope of this tutorial, but suffice it to say that as long as the IP address of the router itself is known, packets will be able to traverse between subnets.

The router is often known as a “gateway”, as it provides a gateway to other subnets. In essence, the network device makes a decision as to whether the IP packet is to be sent to a device on it’s own subnet. If not, the packet is sent to the router – to the gateway IP address – instead.

Tutorial 4 –Gemini Systems on Two Domains

This tutorial will use as its starting point the configuration that has been created during tutorial

3. It is available on the product CD as Tutorial4_start.trilogy. This tutorial assumes that the system one site has 2 matrices and the system at the other site has just one.

All Gemini Matrices should have had their IP address configured as described in Tutorial 1, and it is recommended that you use a Web Browser to confirm that all matrices are operational and the network is connected correctly.

Unless the network and the routers are

configured correctly, it is extremely unlikely that

this tutorial will prove successful.

It is also imperative that the matrices have correct E.D.H. addresses:

 Site One: the first matrix should be 0.1.1 and

the second 0.1.2.

 Site Two: the matrix should be 0.2.1.

Launch the Gateway Configuration Editor and click the “Active Clients” button to confirm that all Gemini units are present.

Short Form User Guide

Page 40 of 60 Trilogy Communications

NOTE: The default label for this

subscriber is H1S1 because this matrix is the first host of this domain.

Configuration Changes

 Launch the Basic Domains Editor by single

clicking on the tree view entry labelled “Domains”. Add a new domain by clicking the “add” button.

 It is a good idea to give the domains a

meaningful name that relates to the sites themselves: we’ll use Site1 and Site2.

 Enter the gateway IP addressed – the

IP addresses of the routers – for each domain, along with the correct subnet mask for each.

 Launch the Basic Domain Editor for Site2 by

single clicking the Site2 entry in the tree view.

 Add hosts – Gemini Matrices – as

appropriate for Site 2. For the purposes of this tutorial we will add a single 8 port Gemini host and leave it with its default name “Host 2.1”.

 Give the new Gemini Host the correct

IP address.

 Launch the Basic Host Editor for Gemini Host

2.1, by single clicking its entry in the tree view. Add subscribers as required: for the purposes of this tutorial we will simply add a single panel as port 1.

 Edit the default panel label from

“H1S1” (Host 1, panel 1) to be “H3S1”.

 Launch the Basic Panel Editor and add a key

on the Director panel on the first Gemini matrix in the ring, targeting our new panel

H3S1 and, likewise, a key on new panel H3S1 targeting the Director panel.

 Upload and restart the configuration and

check that the Director panel can speak to H3S1 and vice versa

The two-site matrix Gemini System is now operational. The configuration created in this tutorial is

available on the product CD as Tutorial4_finished.trilogy

Short Form User Guide

Page 41 of 60 Trilogy Communications

Configuring a Gemini System for Multiple Administrators

Introduction

The default set-up for a system using Gemini and Gateway is for a single system administrator to have overall control of the configuration management, whether this consists of a single Gemini frame, or multiple frames arranged in a complex network. Although this may be suitable for smaller installations, it is unlikely to be appropriate for a large, multi-studio arrangement. In such instances, the Gateway “Roles and Administrators” feature can be used to create multiple administrators and grant them control over segments of the Gemini network. In this section we will examine this feature and demonstrate a typical example.

Launching the Roles and Administrators Editor

The Roles and Administrators Editor is only available to the top level system administrator. When the top level administrator has logged in, an additional “lock” icon is displayed on the toolbar at the top right corner of the screen. As explained in earlier sections, the credentials for the top level administrator are Admin | gemini.

When the Gateway Configuration Editor is first installed, only the top level system administrator is provided: no roles or additional administrators are present. Our first task is to create a number of roles based on a Gemini network encompassing two studios. The example below shows a new configuration with two Gemini hosts named Studio A and Studio B.

Creating Roles

Firstly we will create three new roles:

• Senior Administrator

• Studio A administrator

• Studio B administrator

After logging in as the top level administrator, switch to the Roles and Administrators editor by pressing the lock icon on the toolbar. Click the green “+” icon to create a new role. Highlight this new role by clicking on the name in the centre of the circle, and then edit the name of the role within the text box by double-clicking in the top row.

Short Form User Guide

Page 42 of 60 Trilogy Communications

Repeat this operation until three roles have been created as shown below.

Highlight the Senior Administrator role by clicking on the name in the centre of that circle: the circumference of the circle changes to black to indicate that the role is currently highlighted. The permissions allocated to this new role are indicated in the tree view on the left side of the screen: where permission has been granted, a green tick is shown adjacent to a Host. The permissions currently granted to the Senior Administrator are appropriate (see image above).

Repeat this process for the Studio A and Studio B administrators and un-check the permission boxes for each one as appropriate. These are shown after adjustment (below) for Studio A.

Short Form User Guide

Page 43 of 60 Trilogy Communications

Creating Administrators

The next stage is to create a number of administrators and then to assign them to specific roles. Each administrator is simply a set of login credentials plus a description but they have no authority or permissions until assigned to a role. To create a new administrator, click on the green “+” icon in the lower pane of the Editor. Enter the details of each new administrator in the edit box and press the tick when complete. To edit it all correct the details of an administrator, highlight the list entry and click the edit button on the administrator's toolbar.

The screen below shows six new administrators -- they are not currently assigned to any roles.

Short Form User Guide

Page 44 of 60 Trilogy Communications

Associating Roles and Administrators

The final step is to assign the operators to specific roles. To do this, simply highlight an administrator from the list and drag the cursor into the appropriate role “circle”.

The following rules and conditions apply:

• each role may have one or more administrators

• each administrator may be assigned to one or more roles

• a role without any administrators serves no purpose

• an administrator who is not assigned to any roles also serves no purpose

The screen below shows the six administrators who have now been assigned to specific roles in the configuration of the Gemini network. The number in the centre of each roll circle indicates the number of administrators currently assigned to that role. Position the mouse cursor over the centre of the circle to see a list of the names of current administrators in that role.

NOTE: if additional hosts are added later, they are automatically added to every current role with the

permissions set to on. Although these settings may be appropriate for the overall system

administrator, minor roles such as Studio A and Studio B (above) must be edited to remove these

new hosts as appropriate.

Short Form User Guide

Page 45 of 60 Trilogy Communications

Non-Disruptive Changes

Introduction

In previous sections we have discussed the mechanism for making changes and updates to the Gemini configuration. To re-cap, changes are made using the Gateway configuration editor and then uploaded to any connected Gemini and Mercury hosts. The upload process is non-disruptive: that is, there is no effect whatsoever on the operation of the system, control panels or currently active conversations. Following the upload, the system must be restarted for the changes to take effect. The restart process is disruptive: all control panels are reset in order to load the new key layout and all conversations are halted.

The time taken to carry out each process depends on both the size and complexity of the system plus the power of the PC which is running the Database Supervisor application. As a guideline, allow 20 seconds for the upload plus a further 10 seconds to restart.

A second mechanism is provided within Gateway which allows minor changes to be made with minimal disturbance to the production or broadcast. Typically changes take less than five seconds to take effect and only the keys which have been edited on an individual panel will change.

Making changes

The graphical panel editor form is used to make non-disruptive changes to control panels. To view this form, single click on a control panel from the tree menu on the left side of the screen. A typical form is shown below.

Note the status of the system as indicated by the toolbar and icons at the top right-hand corner of the screen.

Short Form User Guide

Page 46 of 60 Trilogy Communications

The barrel is green, indicating that the

configuration seen in Gateway is “in sync” with that running on the Gemini system.

The disc is blue, indicating that the

configuration seen in Gemini has been saved to disc.

Best practice is to ensure that both these conditions are met prior to making any non-disruptive changes.

Now edit the panel layout by either dragging and dropping existing keys or adding new keys from the palette. When you have completed the edits, press the tick button on the toolbar within the editor. Your edits are now committed to the database and the supervisor application will immediately process these changes and compile new data for this control panel. To send the revised key layout to the control panel, press the green “ball” indicator on the panel editor form.

Only the key positions which are affected by any changes in Gateway will be updated. All other key locations on the panel and any current calls or routes associated with those keys will not be affected. Changes made in Gateway take precedence over changes made locally by a panel operator (where allowed). If a panel operator has made a local change and the system administrator makes a subsequent change via Gateway, the original change will be discarded.

Only the panel which is currently visible will be updated. If you make changes to a panel, commit those changes to the database and then move to a different screen of Gateway, your changes will not be actioned but will be stored until either:

 You return to the same panel and complete the process by pressing the green “ball”, OR you carry out a

full upload and re-start procedure.

Re-arrange existing keys or add

additional keys from the palette.

Press the tick to commit the changes to

the database.

Press the green “ball” to send the

revised key layout to the panel.

Short Form User Guide

Page 47 of 60 Trilogy Communications

Appendix 1 – Basic Troubleshooting

This appendix provides a few basic tips should initial attempts to prove a Gemini system operational not be successful.

 Check that the Gemini unit is powered up, and has an Ethernet cable plugged in. Obvious, but worth

checking.

 Check IP addresses.

 Check the IP address assigned to the Gemini Matrix by looking at its front panel as explained in

the Getting Started section.

 Check the IP address of the PC running Gateway.

 Are they both in the same subnet? Simplistically, for most installations, this means that

the IP addresses look pretty much the same, except for the last part: for example

192.168.10.100 and 192.168.10.200 are in the same subnet: 192.168.20.100 and

192.168.10.200 are NOT in the same subnet.

 Make sure the subnet masks are correct. Again, typical systems (but not all) will have a

subnet mask 255.255.255.0 – but, generally, if both the PC and the Gemini Matrix have the same subnet mask, it’s probably correct.

 Use Gateway’s View Active Clients dialogue to confirm what is connected to the database

supervisor

 Use “PING” from the Gateway PC to make sure the network is connected. “PING” is available

from the command prompt of Windows PCs. In Vista and Windows 7, you can simply type “cmd” in the “search programs and files” dialogue from the start button, and click it when presented. Then type “ping 192.168.10.100” (or whatever the IP address of the Gemini matrix is) and make sure there’s a response. If not, there’s a cabling, network, firewall, or IP address issue and the best option is to discuss with the system installer.

 From the web browser connection to the Gemini Matrix, look at the log messages for clues.

Short Form User Guide

Page 48 of 60 Trilogy Communications

Appendix 2 – Key Types

The key types available in the Gemini System are as follows.

Key Type Description

Operates as a latching speak key if you briefly press the key, otherwise it is a momentary speak, making a speak route only for the duration of the keypress. The upwards and downwards action of a lever-action key is identical.

A momentary speak if the key is pressed downwards, and is always latching in the upwards direction.

A latching/momentary operation, the same as the speak key, but listening rather than speaking. Generally not used for communications with panels, but useful for 4-wires.

Has the latching/momentary characteristics of the speak key, but the downwards motion is for speaking and the upwards motion for listening.

Operates as a latching key making both speak and listen routes if you briefly press the key,

otherwise it is a momentary action, making the routes only for the duration of the keypress. The upwards and downwards action of a lever-action key is identical.

A speak key that only ever has a momentary action, making a speak route only for the duration of the keypress. The upwards and downwards action of a lever-action key is identical.

Operates like the Speak/Listen key, with the downward motion speaking, upwards listen, and a choice of momentary or latching depending on the duration of the key press. However, when the speak route is made, the listen route is temporarily suspended for the duration of the speak route.

As per Speak/Listen, with the downwards motion for speaking and the upwards motion for listening, but only the listen action will latch if pressed briefly.

As the standard Speak key, but the key defaults to being on – i.e. the speak route made – when the system starts.

As the standard Listen key, but the key defaults to being on – i.e. the listen route made – when the system starts.

As per Listen/momentary speak, except the listen route defaults to on when the system starts.

A “quick response” key that allows a reply to the most recent incoming call to be made without first having to locate the specifically configured key for that caller on the panel. The reply may be latched or momentary depending on the length of the key press.

As per QRS (Speak) except the speak route can only ever be momentary.

The speak and/or listen and momentary/latching characteristics of “fast” keys are identical to their

“non-fast” versions, but differ in the way the route is established; they are really only relevant on long latency networks, such as IP-over-Satellite. When a key is pressed, there are a few message exchanges between Hosts to negotiate the route and make sure each matrix has sufficient routing resources to make the route. On most IP networks the delay resulting from any network latency is negligible (just a few milliseconds) and can be ignored. On a network with high latency, the delay can be appreciable – over satellite a message will take at least 550ms to arrive. If a response is required, the delay from pressing a key to the route being made will be well over 1 second. Fast keys work around this by pre-negotiating the matrix resources required and reserving audio channels – the audio route is essentially pre-made, although no audio is flowing. When a key Is pressed, all that is needed is to make a local audio route to allow the audio to flow. A single message is then sent to confirm the audio is being sent: by the time the audio arrives, so does the message, so the remote tally indicator showing the audio route generally lights at the same time as audio is heard.

Short Form User Guide

Page 49 of 60 Trilogy Communications

Appendix 3 - Interfacing to Mercury

The Gemini Matrix is an evolution of the Mercury product line, sharing a significant commonality in the underlying software, especially in relation to IP encapsulation of audio and the inter-host message structure.

Simplistically, a Mercury host can communicate with a Gemini Host seamlessly, with audio being carried between them using IP.

Note that the fundamental audio bandwidth of the Mercury system is at best 7kHz (when 16kHz sampling is used), compared to Gemini which uses 48kHz sampling to provide full broadcast quality.

Mercury offers a number of host types:

 The “Mercury Interface Unit” or MIU. The MIU, a rack mounted 2U chassis, is similar to the Gemini

Matrix in some ways, in that it can accept a variety of I/O modules. Those currently available are:

 Audio Expansion Board (“AEB”) providing 8 channels of analogue audio, along with data

channels for control panels.

 Telephony Expansion Boards (“TEBs”, providing 4 channels of FXO, FXS or E&M depending on

the module chosen.

 E1, providing a convenient way of carrying up to 30 channels of audio between MIU’s over

2km of either CAT5, or a pair of co-ax cables.

 Radio Interface Board (“RIB”) providing 8 channels of audio I/O plus PTT and COR interfaces

allowing easy connection to most common radio systems such as VHF, UHF or Tetra. Mercury provides extensive functionality for radio systems, including noise filtering, squelch suppression, CTCSS tones etc.

 “Mini Mercury Unit (“MMU”). This is a smaller desktop-sized MIU, with a 4 port capacity. It offers a

pair of headset channels, plus a pair of 4-wire/panel interface ports.

 PCI cards. Available in two different sizes depending on the number of simultaneous audio channels

required, these cards allow a PC running Microsoft Windows to become a standalone Mercury Host. The PC will usually run a Virtual Panel as the user interface, but both cards will also support a single control panel, such as a desktop panel, if required.

 USB interface unit. Serving the same idea as the PCI cards, but intended for PC’s that have no PCI

slots, such as laptop computers.

Interfacing to Mercury Hosts

Using the Basic Domain Editor, Mercury hosts can be added in exactly the same way as Gemini Matrices. It will also be necessary to invoke the Advanced Host Editor (by doubling clicking the relevant host in the tree view) to configure the option modules that have been fitted

Once the Host is declared, the remaining configuration is conducted in the same manner as a Gemini Matrix.

Short Form User Guide

Page 50 of 60 Trilogy Communications

Appendix 4 – Soft Panels

Gemini provides two “soft” panels: a Virtual Panel and a Patch Panel.

Virtual Panels

The Virtual Panel, or “VP” provides a control panel functionality from a PC. It can make use of a Mercury PCI card, or USB device, or it can be a panel declared as a Gemini matrix subscriber.

Audio I/O can be from the 3.5mm headset jacks on a PCI card or USB interface box, from a 4-wire port of a Gemini matrix, or from the headset connector on the front of the Gemini matrix itself.

All keytypes are supported, providing the VP with the same functionality as a physical control panel device, but with a control surface on the PC. A VP is configured within Gateway in the same manner as a standard control panel, with sources assigned as required.

The VP offers user-configurable key layout with as many button rows and columns as are required. The preferences menu allows key rows and columns to be labelled, as well as “indicators” added to show the status of GPIO signals, for example.

Short Form User Guide

Page 51 of 60 Trilogy Communications

Patch Panels

A patch panel is a variant virtual panel that is useful when an operator needs to select or deselect audio routes in real-time, and visual status of which routes are currently active is beneficial.

Gateway is used to determine the audio sources and destinations that will appear on the panel (Note: the Advanced Panel Editor must be used to configure path panels).

The Patch Panel itself allows the operator to choose which sources and destinations are displayed, as required, and routes may be created on demand. Currently made routes are displayed on the panel.

Short Form User Guide

Page 52 of 60 Trilogy Communications

Appendix 5 - POTS Telephony

Gemini uses a Mercury host to provide POTS telephony functionality. As described in Appendix 3 - Interfacing to Mercury, Gateway is used to declare Mercury hosts, as well as the Telephone Expansion Boards (TEBs) that

are fitted to it, in the same manner as for a Gemini Matrix.

TEBs only support 8kHz sample rate CODECS. When a Mercury host with a TEB is added to the configuration, Gateway will display a warning, and will also prevent G.722 CODECs from being selected. If a G.722 CODEC has already been selected, a G.711 CODEC will be automatically chosen

The Basic Host Editor is used to add the 4 ports of telephony (in this example, 4 FXO ports)

The Advanced Host Editor may need to be invoked to change the line termination from the default “CTR21” as used in the UK, to 600R or 900R, or the Japanese standard. This is done on the General tab.

The TEB port also incorporates echo cancellation, to deal with echoes originating from the telephone line. The Audio tab of the Advanced Host Editor can be used to change this if required.

Once the telephone ports are defined on the host, keys may be assigned to them on panels in the same way as keys to any other subscriber type. The key type will default to a Phone Action type, the only type valid for phone ports. This key operates as a combined speak/listen key in the downwards direction – deselecting the speak/listen also acts to “hang up” the call – and provides a “place on hold” action in the upwards direction. It also invokes a keypad to make outgoing calls.

The final area to be configured is found by accessing the Basic Phone Number editor.

FXO, FXS and E&M

FXO stands for “Foreign eXchange Office and

is a term from the world of telephony used to

describe a port that connects to a remote

telephone exchange. In practice this means you plug a telephone line into an FXO port.

FXO stands for “Foreign eXchange Subscriber,

and describes a port that connects to a remote telephone subscriber: you plug a

telephone handset into it.

E&M stands for “Ear & Mouth or Ear & Magnet and describes a port that is used to

connect two telephone

exhanges together.

Audio is carried as 4-

wire balanced audio

(although 2-

wire interfaces do exist) with

basic ground and 48V DC signalling on the E and M wires (very simplistically: the M-leador mouth-lead - is signalled when one end wants to speak, and it is acknowledged by the E-lead, or ear-lead, once it is listening).

Short Form User Guide

Page 53 of 60 Trilogy Communications

Phone Numbers entered here may be assigned to

panels individually (using the Panel Advanced Editor) and used as speed-dials for outgoing calls made from panels.

Phone Sets allow a list of panels to be grouped

together. An incoming call made using Phone Controls can be made to the Phone Set so that all panels in the set will ring

Phone Controls allow an incoming call to be made to a caller-determined destination.

When the TEB answers the call, a short period of silence is heard by the caller. During this period, DTMF digits entered by the.caller will be used to direct the call to the intended recipient. In this example “123” will direct the call to the Director panel, and “500” to Phoneset1 (to call multiple panels, for example). If no DTMF is detected within a few seconds, the incoming call is routed to any panel with a key targeting the phone line in questions.

SIP Numbers. These are

the same as Phone

Numbers but used for SIP calls as described in

Appendix 8 –

Introduction

to SIP

Short Form User Guide

Page 54 of 60 Trilogy Communications

Appendix 6 - Commander/Orator

Interfacing a Commander or Orator system to Gemini is relatively straightforward. It is covered in depth in the full System Guide; what follows is a brief summary of the steps that are required. A configuration called “Commander Interfacing.trilogy” is available on the product CD to illustrate the principle.

A Commander system connects to a Mercury Interface Unit, which then acts as a gateway between the Commander system and the Gemini matrices in the system.

The steps required are as follows.

 Add a Commander/Orator host to the

relevant domain using the Basic Domains Editor

 Using the Basic Host Editor (single click

the Commander host in the tree view) to add “remote targets”. Remote targets are the–ports that have been declared in the Commander/Orator system, using its PathFinder configuration software, as available for Commander Networking. There are two port types that can be selected: panel; or 4-wire.

 The MIU that the Commander system is

connected to should be checked using the Advanced Host Editor (double click the relevant Gemini Matrix in the tree view).

 Make sure that the “Cmdr

System” number matches that declared within PathFinder.

 The Commander host in Gateway must

now be configured using the Advanced Host Editor (double click the relevant

Commander System in the tree view).

 define the “Parent Host” and the

COMM port of the MIU that the Commander system is physically connected to. This is done on the “Cmdr/Orator Hosts” tab.

Short Form User Guide

Page 55 of 60 Trilogy Communications

 Declare the start and finish

“networking” ports of the MIU – those ports that are connected to Commander/Orator network ports. This is done on the “Cmdr/Orator Ports” tab. “Trunked” ports can be declared here (see full System Documentation). Note that these ports will now show in the subscriber list for the MIU.

 Commander ports (subscribers)

can now be assigned to Gemini panels in the same manner as any other Gemini subscriber type

Short Form User Guide

Page 56 of 60 Trilogy Communications

Refer to the Implementation Guide for electrical

and installation information, etc.

Appendix 7 – A Basic Introduction to GPIO

The Gemini Matrix is fitted with a GPIO (General Purpose Input/Output) module, equipped with

 16 General Purpose Inputs (GPIs) – a

contact closure to ground “asserts” the GPI

 16 General Purpose outputs (GPOs) –

opto-isolated using low resistance bidirectional mosfet outputs

To make use of GPIO they must first be added to the configuration using the Advanced Host Editor - GPIO tab, and adding (up to) 16 “Standard GPI” and (up to) 16 “Standard GPO”.

There is a second class of GPIO known as Audio (VOX) Inputs and Audio (VOX) Outputs. These provide GPI event triggers if the audio at a matrix input or output exceeds a software adjustable level. They are useful for 4-wire ports to show that the source is speaking, otherwise there would be no “listen” tally displayed at panels.

Once declared, the GPIO Processes editor is used to configure GPIO functions.

Create statements that cause

GPI to control a route

Create statements that cause a

GPO to be controlled by a route

Create statements that cause a

route to be controlled by a route

Short Form User Guide

Page 57 of 60 Trilogy Communications

To use GPIO Functions it is first necessary to declare audio routes (i.e. crosspoints) that will cause, or be controlled by, GPIO functions. This is done using the Basic Route Editor.

In this example 3 routes have been declared and should be self-explanatory. The default label for a route is of the form source::destination and is rarely displayed on panel displays so they are usually left with the default text. The “Fixed” attribute is used to permanently make the route (a “fixed crosspoint”).

Once the routes are declared, the Basic GPIO Processes editor is used to define the GPIO functionality. The following 3 examples are available in a configuration on the product CD called “GPIO Functionality.trilogy”.

These statements are described below.

Short Form User Guide

Page 58 of 60 Trilogy Communications

GPI -> Route

 If GPI GII-0.1.1:1 is ON (i.e. asserted) the route CAMO1 to PTB is to be MADE and GPO GIO-0.1.1:1 is to be

MADE (i.e. asserted). The responsibility for this action rests with Gemini Matrix1

This type of function might be used if CAM01 has a push-to-talk switch which, when pressed, is required to make an audio route from the camera to the production talkback conference. A GPO is also triggered which might be used to illuminate a warning tally in the studio

Route->GPO

 If the route DIR to FM is MADE then GPO GIO-0.1.1:2 is to be MADE (i.e. asserted). The responsibility for

this action rests with Gemini Matrix1.

This type of function might be used if the Floor Manager’s beltpack has a tally light that can be illuminated by a GPIO signal.

Route->Route

 If the route DIR to FM is MADE then the route from PGM to FM is NOT to be MADE (i.e.it is inhibited). The

responsibility for this action rests with Gemini Matrix1.

This type of function might be used if the Floor Manager’s programme sound fed is to be interrupted when the Director speaks (although this is more effectively done using an IFB

)

Priority is an advanced

function: refer to the full documentation.

Short Form User Guide

Page 59 of 60 Trilogy Communications

Appendix 8 – Introduction to SIP

SIP is a natural extension to POTS telephony, as described in Appendix 5 - POTS Telephony. It is recommended that you read that Appendix before continuing here

Gemini handles SIP calls in exactly the same was as it handles FXO/FXS/E&M telephone calls – the major difference is that there is no physical phone port on the matrix.

Instead, Gemini uses “virtual” phone ports, named

SIP Connections. These are added using the Basic SIP Connection editor.

Once created, SIP connections are then targeted by phone keys in the same manner as keys may be targeted at TEB ports.

As with POTS phones, SIP connections allow for phone controls, allowing callers to direct their call to specific recipients using DTMF, and speed dial, entered using the Basic Phone Controls editor, allowing rapid outgoing calls:

Note that SIP calls, in the most simple case, may only be made to pre-defined SIP numbers: this is because SIP phones have “numbers” that may involve IP addresses, and have associated passwords: these cannot readily be entered from a Gemini control panel.

To overcome this restriction, it will be necessary for Gemini to be configured to “register” with an external “SIP Gateway” or perhaps a “SIP PBX”.

That is outside the scope of this brief introduction – please refer to the full system documentation.

SIP

stands for “Session Initiation Protocol,

and is the protocol most commonly used for Voice-over-IP (VoIP) telephony.

It is used to set-up and tear-down calls, in

much the same way as a POTS phone

communicates with a telephone exchange by

going on and off hook, but is not used to actually carry audio between the parties

involved in the call.

Gemini supports SIP inherently, so Gemini panels may place and receive calls directly

with external SIP-enabled subscribers, such as IP-phones.

Short Form User Guide

Page 60 of 60 Trilogy Communications

Appendix 9 – Comparison of Control Panel Facilities

700

-30-50 24 lever key panel.

700

-31-00 16 lever key panel.

700

-31-51 16 lever key plus dial-pad panel.

700

-33-00 32 lever key panel.

700

-41-xx 8 lever key desktop panel.

00-42-01 Callstation. 700-42-50 10 lever key with LED displays

700

-45-00 8 button VFD panel.

700

-46-00 10 button LCD panel.

700

-37-00 30 button touch-screen panel.

700

-47-00 20 key desktop touch-screen panel.

Number of switches 24 16 16 32 8 8 10 8 10 30 20 Form factor (D=desktop) 2U 2U 2U 2U D D 1U 1U 1U 2U D

Display type (1=LCD, 2=LED, 3=VFD, 4=Touch-screen).

1 1 1 1 1 1 2 3 1 4 4

Power Supply (IN=internal, X=external) IN IN IN IN IN X IN IN IN X X Comprehensive audio inputs and outputs.

√

†2

√ √

†3

√ √ √ √ √

Local logic inputs and outputs

√

√ √ √

†3

√ √ √ √ √

Remote control footswitch

√

√ √ √

†3

√ √ √ √ √

Conversion from Commander / Orator range †1

√

†1

√ √

†1

√ √ √ √

Software re-programmable (upgrade)

√

√ √ √ √ √ √ √ √ √ √

Fitted front panel microphone

√

√ √ √ √ √ √ √ √ √ √

Built in loudspeaker

√

√ √ √ √ √ √ √ √ √ √

Headset connector

√

√ √ √ √ √ √ √ √ √ √

Notes:

†1 –

Panels originally purchased to operate with Commander or Orator may be factory converted to operate

with Gemini. Other panels shown above may be converted on site

†2 – Destailed information on the audio facilities available from this model is provided in the Implementation

Guide.

†3 – These facilities are available internally but are not provided externally unless requested at time of

purchase. Please contact Trilogy for more information

Trilogy Communications Gemini User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual