eclipse hx system networking eclipse hx matrices

Eclipse HX SystemNetworking Eclipse HX Matrices

► Networking matrices together allows 2 or more different studios, OB Vans or sites to share the same facilities and appear as one large transparent system. External 4-wires appearing on the MCR system can be transferred over the network to another studio system for use in a production.

► The network can be inside one building / campus / across cities or worldwide. Simply linking a OB Van to the Studio matrix forms a network.

► Networked systems allow operators to intelligently “SEE “ who is calling them from the remote matrix and not just hear the audio.

► Trunk lines are setup between the matrices and the intercom panels are simply configured to have keys that access other panels / 4wires on the remote system

Ethernet data

Trunk lines

NETWORKED MATRICES OVERVIEW

All networked systems must have► Ethernet LAN (IP) connection to all matrices in the network to transfer data

► Trunk Lines (analogue or digital) to carry the audio between the matrices ► The number of trunk lines needed depends on the number of simultaneous conversations

(average of 5-8 is required per matrix)LAN or WAN applications ► Analogue 4wire trunk lines – used across both LAN & WAN► Digital E1/T1 trunk lines - used across both LAN & WAN► IP trunk lines (Voice2 or 3rd party unit) - used across both LAN & WAN► Fibre trunk lines using the E-FIB card (distance 5-10Km) - used across LAN ► Madi trunk lines using E-Madi card – used across LAN► IVC-32 IP Trunk lines or IP Direct linking - used across both LAN & WAN

NETWORKED MATRIX LINKS

Trunk Lines (analogue or digital)

Ethernet LAN


The network topology can be ► Ring ► Star► Mesh

Fibre rings can also have other copper or digital trunk lines branching of a spur

All topologies use trunk forwarding methods to find the best possible route between systems even if there is no direct connection or a path is down

Up to 64 matrices can be networked together using any network connection.

The trunk lines not only support point to point calls but also conference (partyline) and group calls.

Trunk lines may even be reserved for use by a particular panel / 4wire

RING

STAR

MESH

NETWORKED MATRIX LINKS


1. Create map for system 1 and declare the MVX ports to be used as trunk lines in the matrix hardware screen

2. Create map for system 2 and declare the MVX ports to be used as trunk lines in the matrix hardware screen. Make sure system 2 has a different IP address to system 1

3. Click Save Project. Go to the “systems” screen and join the trunk lines together.

► Connect the audio crossover cables between the matrices

4. Place keys from the remote matrix onto your local panels

5. Download map to both systems – making sure that each matrix has a different IP address

SETUP ANALOGUE TRUNK LINES


Matrix A, Matrix B,

Ethernet data

1. Create map for system 1 and declare the fibre card and the number of trunk lines per card in the matrix hardware screen

2. Create map for system 2 and declare the fibre card and the number of trunk lines per card in the matrix hardware screen. Make sure system 2 has a different IP address to system 1

3. Click Save Project. Go to the “systems” screen and join the fibre cards together.

► Connect the fibre cable between the matrices

4. Place keys from the remote matrix onto your local panels

5. Download map to both systems – making sure that each matrix has a different IP address

SETUP FIBRE TRUNK LINES


IVC-32 IP Directs and Trunks The Eclipse IVC-32 cards allow

directs and trunks over IP network infrastructure. All IP trunks and directs can be compared directly to 4-wire trunks and directs. They consist of:

A single duplex audio channel A known start point and end point Links have to be made over IP before

the trunk/direct can be used. One side calls the other to set up the

link and is known as the caller. The other side receiving the call checks and decides if it can set up the link – this is the recipient.

IP NETWORK

IVC-32 IP CONNECTION (AUDIO ONLY)

ETHERNET DATA (CPU CARD)

IVC-32 IP DIRECTS AND TRUNKS

Configuring an IP Trunk In the Cards and Ports screen, for each of the IVC-32 cards, right click on the card

and select Card Properties. From the IVC-32 Card Properties screen, enter valid IP addresses and gateways for

the card. In the Cards and Ports screen, select the trunk port. From the properties list, select IP Port Options, and enter valid settings for the

Network Connection, Audio Codec and VOIP Caller.

Repeat for any matrices in the linked set you wish to link over IP (1 port per trunk link, point to point).


In the Layout screen, drag the trunk links as required. The direction of the drag creates the link as Caller to Recipient.

Note: Right clicking on the link and the ports allow you to change caller, network connection type and flip ports.


Configuring an IP direct In the Cards and Ports screen, for each of the IVC-32 cards, right click on the card and

select Card Properties. From the IVC-32 Card Properties screen, enter valid IP addresses and gateways for the

card. In the Cards and Ports screen, select the direct port. From the properties list, select IP Port Options.


For the caller IVC-32 card, select the VOIP Caller checkbox. The other card will be the caller.

Enter the IP address of the recipient’s IVC-32 card into the caller’s Remote IP Address so it can make setup the call.

Enter a unique User ID and Password set which matches for caller and recipient to identify the port it is linking to.

Note: The following settings can be ignored: Local User ID/Password can be ignored for caller Remote IP and User ID/Password can be ignored for recipient Once set up, the IP Direct ports will behave in the same manner as all other Direct

ports As each caller can point to a unique IP address, IP directs on one IVC-32 can link to

32 different destination devices. IP directs cannot link back to a direct on the same card, but can link to other cards on the same Eclipse matrix.


If a caller is not reachable: The caller tries three times to establish call After it stops trying, a low level background routine checks to see if it’s reachable

again Calls will start to try again if the background routine sees the recipient

Calls can be refused by the receiver, if: The caller is trying to use a non-existent user name The caller is using the wrong password The caller is not the expected port type (for example, Trunk calling a Panel) The call is refused three times, the caller stops calling


Configuring an IVC-32 redundant card You can add an IVC-32 Redundant Card that provides fail-over redundancy for one or

more IVC-32 Cards in the matrix.

Note: You can only configure IVC-32 redundant cards up to the number of IVC-32 Cards in the matrix.

To add an IVC-32 Redundant In Hardware > Cards and Ports, navigate to an available slot number (marked

Empty). Do either of the following: Double click the slot. Right click the slot and select Set Card Type. A drop-down menu is displayed, listing the available card types. Select the IVC-32

(Redundant) card.


The card properties for the IVC-32 (Redundant) card

Allow you to specify which IVC-32 to provide redundancy for:

The following combinations of IVC-32 Cards and IVC-32 Redundant Cards are possible:

One IVC-32 Card and one IVC-32 Redundant Card - the redundant card provides backup for the only card in the system

Two IVC-32 Cards and one IVC-32 Redundant Card - you can either set the redundant card to provide redundancy backup for both IVC-32 Cards in event of failure, or specify that it is only backing up a particular card.


Two IVC-32 Cards and two IVC-32 Redundant Cards - you must specify which redundant card is providing redundancy for which IVC-32 card. It is not possible to have two redundant cards providing backup for the same IVC-32 Card.

Three IVC-32 Cards and one IVC-32 redundant card - you can either set the redundant card to provide redundancy backup for all IVC-32 Cards in event of failure, or specify that it is only backing up a particular card.

An IVC-32 Card will fail-over to the IVC-32 Redundant Card under the following conditions:

All configured VoIP ports are unconnected for longer than 90 seconds. The IVC-32 Card is detected as absent from the VME backplane.


When a failover is detected, the following steps occur: The Config card checks to see if there is a redundant card configured to take over

from the failed card. If not then the card is placed into an error state and nothing else happens.

If a redundant card is configured then the failed card is placed into an error state. All port numbers and timeslots are turned over to the redundant card. The failed card has its IP details cleared. The IP address is changed to

169.254.0.<slotNum> and resets. The redundant card takes on the failed card’s pervious IP address and resets. On start-up the redundant card is placed into the Initialising state and finally into the

Running States. The failed card stays in the Error state. The redundant card now establishes all VoIP calls that were previously configured on

the failed card.

Once the switch over process has started the redundant card starts accepting and making VoIP connections within 40 seconds.


► Network two matrices together

► Build a Group with remote members

► Build a Conference / Partyline that can be accessed by panels on both matrices

► Build a Route with a remote destination

► Activate a Remote relay

HANDS ON DEMOSTRATION


Ethernet data

Trunk lines

Thank you!

eclipse hx system networking eclipse hx matrices

Documents