Mercury Communicator Unit (MCU)
Skip to main menu Skip to main content Skip to footer
Home chevron_right Products chevron_right Products By Name chevron_right Trilogy Mercury
Mercury Communicator Unit (MCU)
Clear-Com Marketing
/ Categories: Products, Trilogy Mercury System, Communicator Unit, SIP Connectivity

Mercury Communicator Unit (MCU)

Single User Operator Station

  • Multi-operator Station - Fully independent operation
  • True Peer-to-Peer Architecture –No single point of failure
  • Capable of running the latest versions of the Trilogy ES, DS and Core Software suites
  • Standards-based VoIP Connectivity
  • Ethernet connected using either Fiber SFP transceiver or RJ45 PoE
  • Point-to-Point calling
  • Multi-point conferencing
  • User configurable priority based routing of audio
  • SIP calling
  • Safety of flight sidetone suppression
  • Offline Configuration
  • Two additional AUX ports for RIB (radio) or AEB (panel) connections
  • Small compact form factor with two different mounting options
  • Compatible with other Mercury products (MCU, MMU and MIU)
  • Integrate any Clear-Com system over IP with LQ Series devices
  • Binaural headset operation
  • Independent LEMO connections for headset+PTT and additional PTT
  • Support for both Dynamic and Electret Microphones
Previous Article CC-400
Next Article Audio Expansion Board (AEB) (700-11-01)
Print
8183 Rate this article:
No rating
Item Code

Interface Option 1

750-30-01-17: MCU with 12-pin LEMO CIA link, Port 1 AEB, Port 2 RIB
750-30-01-11: MCU with 12-pin LEMO CIA link, Port 1 AEB, Port 2 AEB
750-30-01-77: MCU with 12-pin LEMO CIA link, Port 1 RIB, Port 2 RIB

Interface Option 2

750-30-02-17: MCU with XLR7-F CIA link, Port 1 AEB, Port 2 RIB
750-30-02-11: MCU with XLR7-F CIA link, Port 1 AEB, Port 2 AEB
750-30-02-77: MCU with XLR7-F CIA link, Port 1 RIB, Port 2 RIB

Interface Option 3

750-30-03-17: MCU with XLR7-M CIA link, Port 1 AEB, Port 2 RIB
750-30-03-11: MCU with XLR7-M CIA link, Port 1 AEB, Port 2 AEB
750-30-03-77: MCU with XLR7-M CIA link, Port 1 RIB, Port 2 RIB

Product Description Left
Description

The MCU (Mercury Communicator Unit) is a small form-factor device that can simultaneously function as a mission critical operator station, a host to numerous virtual panels and interact with a variety of SIP endpoints.

 

Operator Station Component

The MCU’s primary function is to provide support for single operator connectivity. With three variants of interface options, the MCU facilitates various connection options for headset + PTT, along with an additional 4-pin LEMO connector. The virtual control surface can be accessible through either the connection of a touch-screen (or non-touch) monitor directly to the MCU’s HDMI and USB ports on the rear of the unit or alternatively with the navigation of a browser to the IP address or hostname of the MCU.

 

Peer-to-Peer Architecture

The MCU is able to operate peer-to-peer, allowing each device to function in a fully independent manner, relying on no other resource to perform any of its functions. It also can seamlessly interface with other Mercury products (MCU, MMU and MIU), along with any SIP capable endpoints. As a result, the resilience of the Mercury system coupled with the ability to seamlessly integrate with the certified Mercury Cross Domain Solution enables the MCU to operate in any mission critical environment where security is paramount.

Product Description Right
Hosting of Virtual Panels

Up to 32 virtual panels can be hosted on a single MCU. The IP connected clients can run on either Windows, iOS or Android devices and have the ability to communicate with any resource that is available to the MCU, including other MCUs, MMUs or MIUs.

 

SIP Interfacing

Each MCU can use up to 64 of the shared DSP resources to intercommunicate with any SIP enabled endpoint, either through a SIP server, PBX or directly point-to-point using a SIP URI.

Technical Specifications Left

AUX 1 & 2

RJ45 connectors for RIB (Radio) or AEB (panel) connections

Interface Option 1

LEMO 12-pin connector compatible with plug FGG3B.312.CLAD10 used for dynamic or electret headsets, PTT & GPIO operation

Interface Option 2

XLR 7 Female
7 Pin Female XLR connector used for dynamic or electret headsets, PTT & GPIO operation

Interface Option 3

XLR 7 Male
7 Pin Male XLR connector used for dynamic or electret headsets, PTT & GPIO operation

AUX PTT Connector

4-pin Lemo socket of type 1B used for AUX PTT

AUX Mic Inputs

Two 3.5mm jacks used for electret headset in conjunction with AUX PTT

Networking

Power-over-Ethernet (PoE) enabled
10/100/1000BaseTX Ethernet Port and pluggable SFP supporting an optional Gigabit
Ethernet 1000Base-SX multimode or single mode transceiver

USB

3 USB type A ports (two 2.0 & one 3.0) used for connection of a mouse, keyboard or external storage device.

Tone Generation

Up to 4 tones can be injected into any audio mix

Technical Specifications Right

AUX 1 & 2

RJ45 connectors for RIB (Radio) or AEB (panel) connections

Interface Option 1

LEMO 12-pin connector compatible with plug FGG3B.312.CLAD10 used for dynamic or electret headsets, PTT & GPIO operation

Interface Option 2

XLR 7 Female
7 Pin Female XLR connector used for dynamic or electret headsets, PTT & GPIO operation

Interface Option 3

XLR 7 Male
7 Pin Male XLR connector used for dynamic or electret headsets, PTT & GPIO operation

AUX PTT Connector

4-pin Lemo socket of type 1B used for AUX PTT

AUX Mic Inputs

Two 3.5mm jacks used for electret headset in conjunction with AUX PTT

Networking

Power-over-Ethernet (PoE) enabled
10/100/1000BaseTX Ethernet Port and pluggable SFP supporting an optional Gigabit
Ethernet 1000Base-SX multimode or single mode transceiver

USB

3 USB type A ports (two 2.0 & one 3.0) used for connection of a mouse, keyboard or external storage device.

Tone Generation

Up to 4 tones can be injected into any audio mix

Mark as DiscontinuedNo
Rank9999
IsActiveTest

More links

Please login or register to post comments.

Why Choose Trilogy Mercury?

Flexible Architecture with Seamless Integration

Mercury by Trilogy is built for long-term adaptability, offering native interoperability with SIP/VoIP and legacy systems to protect your existing investments. Its modular design supports system expansion as your needs evolve, while Mercury Interface and Communicator Units provide 64 dynamically allocated IP audio channels per host. These channels enable simultaneous, enterprise-wide communication across globally distributed networks—ensuring your teams stay connected, wherever they are.

Scalable Communication for any Scenario

Mercury supports point-to-point, group, and conference calls, offering flexible communication options for diverse needs. When deployed on multicast-enabled networks, Mercury enables efficient bandwidth usage for large-scale conferencing with hundreds of users. It also allows IP audio channels to be reserved for static audio trunks or emergency communications, ensuring reliability when it matters most.

Retail Warehouse Communications

Cashiers, Operations and the Warehouse are all connected via an IP network on which audio can be delivered. At Customer Checkout, cashiers POS stations are outfitted with Trilogy Virtual panels. Labeled with key personnel throughout the retail store, a cashier can contact anyone quickly and efficiently. The virtual panels are managed through a Trilogy MIU device in the Operation Team’s control room. There, users can communicate with other team members using the virtual panel on their PCs. An LQ-4W2 IP interface allows a connection to the Warehouse where pickers use a DX410 wireless system to roam throughout the RF coverage area to gather product and deliver it to the customer at the front of the store.

View Diagram