1. Manuals
  2. Brands
  3. AEQ Manuals
  4. Software
  5. PHOENIX MERCURY
  6. User manual

AEQ PHOENIX MERCURY User Manual

Hide thumbs
Table of Contents

Quick Links

AEQ
PHOENIX MERCURY
Firmware Versions:
Software Version:
USER'S MANUAL
ED. 11/12
V. 1.4 - 22/08/2013
CPU 3.80 / DSP 3.11 or higher
AEQ ControlPHOENIX 2.0 or higher
Table of Contents
loading

Summary of Contents for AEQ PHOENIX MERCURY

  • Page 1 PHOENIX MERCURY USER’S MANUAL ED. 11/12 V. 1.4 - 22/08/2013 Firmware Versions: CPU 3.80 / DSP 3.11 or higher Software Version: AEQ ControlPHOENIX 2.0 or higher...

  • Page 2: Table Of Contents

    1.1. General description......................4 1.2. Functional specifications....................4 1.3. Available encoding modes....................5 1.4. Compatibility with other AEQ codecs................. 5 1.5. Compatibility with other manufacturers’ codecs..............5 2. PHYSICAL DESCRIPTION OF THE UNIT................6 2.1. Description of the front panel..................... 6 2.2.
  • Page 3 6. TECHNICAL SPECIFICATIONS* ................... 39 7. A.E.Q. WARRANTY........................ 40 ANNEXE A: GENERAL CHARACTERISTICS OF ENCODING MODES........41 ANNEXE B: LIST OF AVAILABLE CODING ALGORITHMS IN PHOENIX MERCURY..42 ..43 ANNEXE C: PROTOCOLS ASSOCIATED WITH COMMUNICATIONS OVER IP NETWORKS C1.

  • Page 4: Introduction

    This specification was developed to guarantee compatibility between devices made by different manufacturers for professional quality audio contribution applications over IP networks. PHOENIX MERCURY enables its users to work with professional quality in mono, dual mono or in stereo format.

  • Page 5: Available Encoding Modes

    Sales Department or authorized AEQ distributors. 1.4. Compatibility with other AEQ codecs. The PHOENIX MERCURY offers its users the option of connecting with other AEQ equipment. It’s compatible with Phoenix MERCURY, STUDIO, VENUS, MOBILE, LITE, POCKET and PC in IP communications.

  • Page 6: Physical Description Of The Unit

    2. PHYSICAL DESCRIPTION OF THE UNIT. To understand how the PHOENIX MERCURY unit is wired and installed, you will first need to familiarize yourself with the connectors and other configurable elements that are present on the front and rear panels of the device.

  • Page 7: Description Of The Rear Panel And Connections

    (the left connector corresponds to L output and the right one corresponds to R output). XLR 3p Male-panel Pinout Pin 1 Ground Pin 2 + Output Pin 3 - Output 2.2.3. AES/EBU inputs/outputs (optional). The physical connector used is a DB15 female, with the following pinout: PHOENIX MERCURY...

  • Page 8: Aux Data Connector (+ Ip Reset)

    2.2.5. Ethernet port (LAN). PHOENIX MERCURY is equipped with an Ethernet port. Using this Ethernet port will enable you to connect the unit via IP to a LAN or WAN network and send audio over it. This port is also used to configure and manage the unit from one or several PCs using the remote control software.

  • Page 9: Usb Port

    Slave. This port can be connected to a USB port in a PC, permitting a data transmission speed of up to 480Mbps (USB 2.0), just for equipment maintenance purposes. IMPORTANT NOTE: Do not use this connector for any reason without the supervision of AEQ technical service personnel.

  • Page 10: Configuration And Operation Options Description

    3. CONFIGURATION AND OPERATION OPTIONS DESCRIPTION. Configuration and operation of Phoenix MERCURY is carried out by means of the application “AEQ ControlPHOENIX“ (AEQ Phoenix STUDIO, MERCURY and VENUS Audiocodecs Configuration and Control Software). The version that is provided together with the equipment can control only one unit per software instance.
  • Page 11 The “General” option is the most important of the ones associated to “CONFIG” button: you can configure the audio routing and levels from/to the equipment, the selected audio encoding algorithm, connection mode (from “INTERFACE” drop-down menu) and access to “Advanced” channel configuration and IP interface configuration (“I/F setup” button). PHOENIX MERCURY...

  • Page 12: Ip Interface Connection Modes

    It is important to know the details of each type of connection, so they are explained below. 3.2.1. PROXY SIP. This type of connection is selected when the Phoenix MERCURY is used working together with an external SIP server that will provide connection with remote unit through any network, even Internet, without knowing its IP address.

  • Page 13: Direct Sip

    Authentication: enables you to edit the password and security information for the user profile associated with the unit in the previously selected SIP server. By default, the data configured in this field in order to use AEQ server are the following: User: the “User Name”...
  • Page 14 IP modes (as defined in “INTERFACE“ drop-down menu), different contact entries must be created. You can access the IP configuration submenu for DIRECT SIP mode by clicking on “I/F Setup“ button, and that it is explained in section 6.1.4.2 of “AEQ ControlPHOENIX“ user’s manual. •...

  • Page 15: Rtp Point To Point (Raw)

    You can access the IP configuration submenu for RTP Raw mode by clicking on “I/F Setup“ button, and that it is explained in section 6.1.4.3 of “AEQ ControlPHOENIX“ user’s manual. The parameters to be configured are: FEC mode: this option allows you to configure whether FEC (Forward Error Correction) is used or not (there is a trade-off for a bigger binary rate).
  • Page 16 IP channel. Make sure that only one of the receiving equipments is enabled to transmit: Channel transmission activated Channel transmission inhibited NOTE: Please read the application notes published by AEQ regarding IP connectivity for more information on IP communications in particular scenarios. PHOENIX MERCURY...

  • Page 17: Nat Traversal

    Proxy SIP, if we use it). 3.3.2. Manual NAT: ”MANUAL (router configuration)”. This mode will be used when the Phoenix MERCURY is in a local network with shared Internet access, through a router that will work as NAT (Netword Address Translation). In order to use...
  • Page 18 6. RTP LOCAL PORT: read-only parameter that tells you the port of the IP interface of the unit as regards RTP, so that the latter can, in turn, convey this to the router or firewall administrator when it is configured. Usually the shown port is 5004. PHOENIX MERCURY...

  • Page 19: Auto 1 (Local Network Audio)

    2. STUN PORT: parameter that tells the unit the STUN server port assigned by the administrator. By default: 3478. NOTE: in this mode the Phoenix MERCURY behaves in the exact same way as the Phoenix Mobile unit when it is using a STUN server.

  • Page 20: Coding Profiles

    Adaptive Buffer Max: this is the maximum size of the reception buffer. When it is defined as adaptive, Phoenix MERCURY will start to shorten it from this value as the network´s transmission quality allows. If it is defined as FIXED, this max value will remain, as the buffer’s size won’t be varied during the connection.

  • Page 21: Ethernet Port Configuration

    Profiles can be added, modified or deleted in the “Encoding Profile Management (SIP)” screen, accessible from the “Tools“ menu in the upper Menu bar, described in paragraph 5.1.8 of “AEQ ControlPHOENIX” user’s manual. 3.6. Ethernet Port configuration.

  • Page 22: Rs-232 Ancillary (End To End Data Channel)

    After confirming, the equipment reboots and the communication re- establishes in approximately 15 seconds. If you have any doubts, please consult your IT network technician or directly contact the AEQ or authorized distributors’ technical support department. 3.7. RS-232 Ancillary (End to end data channel).

  • Page 23: Snmp Configuration

    You can access the configuration menu in “Configuration“ “Network”. AEQ PHOENIX Audiocodecs (Mercury, Venus and Studio) can connect to up to 3 SNMP clients, installed in remote PCs, by simply configuring their IP addresses in the “SNMP” tab of previous menu. Once one or more SNMP clients are connected and the corresponding “MIB”...
  • Page 24 (sysUpTime, sysContact, sysDescr, sysServices,…): Standard SNMP commands indicating things such as equipment's turn on time, etc. For more information, please check MIB-II specification RFC1213 (http://tools.ietf.org/html/rfc1213) For more information, please consult section 5.6 of this manual and section 6.5.1 of “AEQ ControlPHOENIX” application manual. PHOENIX MERCURY...

  • Page 25: Quickstart User's Guide

    4. QUICKSTART USER’S GUIDE. To gain a complete grasp of the PHOENIX MERCURY, we recommend reading the previous chapters and “AEQ ControlPHOENIX” user’s manual carefully. The paragraphs below describe the basic actions you will need to take to operate the equipment. If you need more detail, review the information given in the previous sections of this manual.

  • Page 26: Audio

    DB15 connector for digital outputs. • It is not necessary to define the kind of output, as Phoenix MERCURY offers all the outputs in both analog and digital (if option is installed) formats by default. 4.5. Establishing an IP communication.
  • Page 27 Press the green “Call” button on the screen, to make the call. • Repeat the process at the other end (because RTP is connection-oriented, you also need to connect to the IP of the other unit on both ends). PHOENIX MERCURY...

  • Page 28: Finalizing An Ip Communication In Rtp Mode

    “REGISTERED” indication will be shown and the call can be made; if not, “REGISTRATION_ERROR” indication appears: in that case, you must check the unit’s configuration as indicated in the following steps. • Enter “I/F Setup“ click “SIP Parameters”. PHOENIX MERCURY...
  • Page 29 “Authentication” data in the channel’s SIP parameters so they match those in the new server, as the ones by default are only for “AEQ”. Note that, in case you specify the SIP Server by its URL...

  • Page 30: Finalizing An Ip Communication In Proxy Sip Mode

    @, for example: “[email protected]” or [email protected]” @, for example: “[email protected]” or “[email protected]” (where 232.168.1.2. is AEQ SIP Server (“sip.aeq.es”) IP address ) @:, when SIP port is not 5060 (the one used by default in SIP SERVER mode). For example: “[email protected]:5061”...

  • Page 31: Receiving And Accepting An Ip Communication In Proxy Sip Mode

    Check that there is incoming audio: the “Tx“ indicator in the individual codec control window , in the general configuration screen and in the list view will change to green . • Go to general configuration screen and configure “INTERFACE” as “Net1 DIRECT SIP”: PHOENIX MERCURY...
  • Page 32 “Auto hang-up”: Automatic hang-up whenever audio packets are missed for a given time. “Permanent call”: Automatic redial to the last IP in case the connection is lost. • Return to the individual codec control window and click on “CALL“ button showing then the call screen: PHOENIX MERCURY...

  • Page 33: Finalizing An Ip Communication In Direct Sip Mode

    4.5.3.1. Finalizing an IP communication in DIRECT SIP mode. • In order to hang call, just click on “CALL” button in one of both codecs. A confirmation message will appear and the call will be disconnected after acceptance. PHOENIX MERCURY...

  • Page 34: Receiving And Accepting An Ip Communication In Direct Sip Mode

    If necessary, adjust the output levels in the “att” box at OUTPUTS block in “Configuration” ”General” screen. You can also make an additional adjustment from the windows you access by pressing “In gain” button in “ENCODER” green window and “Out gain” button in “DECODER” green window. PHOENIX MERCURY...

  • Page 35: Control Terminal Over Web Browser

    Microsoft Windows operating system). 5.1. Upgrading the equipment firmware. The unit PHOENIX MERCURY is supplied from the factory with the latest firmware versions available. However, firmware versions with new features may be released in the future, making it necessary to upgrade the equipment to be able to make use of these new functionalities.

  • Page 36: Configuring The Mac Address Associated With The Ethernet Interface

    4. To upgrade the codec, click on the UPGRADE option. 5. A user ID and password are requested (by default, both are aeq). After you have correctly entered these two items, the firmware upgrading screen will be displayed. 6. Check to see whether the versions displayed are the same as the firmware that is currently in effect.

  • Page 37: Technical Assistance Service And On-Line Manuals

    5.3. Technical Assistance Service and On-line manuals. Clicking on the “Support” tab in the upper part of the screen will take you to AEQ website, where you will find all the information you need to directly contact the AEQ Technical Assistance Service, as well as all the technical information and manuals regarding the unit.

  • Page 38: Status Menu

    If you follow that link, the text file will appear. Now you just need to right-click on it and select “Save as…” and browse a suitable destination folder (see the manual of the selected SNMP client). For more information, please consult section 3.8 of this manual and section 6.5.1 of “AEQ ControlPHOENIX” application manual. PHOENIX MERCURY...

  • Page 39: Technical Specifications

    211 x 44 x 170 mm; 8.30" x 1.75" x 6.70" * Characteristics are subject to change without prior notice. Protection and safety standards Marked CE. Electromagnetic compatibility in compliance with the European Union directive: EN 50081-1, EN 50052-2. PHOENIX MERCURY...

  • Page 40: Warranty

    AEQ will not be liable for the loss of information on disks that have been altered or are inaccurate, nor for any accidental damage attributable to the user or to persons handling the product.

  • Page 41: Annexe A: General Characteristics Of Encoding Modes

    IMPORTANT NOTE: AAC-LC and AAC-LD modes are optional, they are not available in the basic firmware version the unit is supplied with. For further information, please consult the AEQ Sales Department or authorized distributors. List of available coding algorithms in Phoenix MERCURY depending on the selected communication interface.

  • Page 42: Annexe B: List Of Available Coding Algorithms In Phoenix Mercury

    M / ST IMPORTANT NOTE: AAC-LC and AAC-LD modes are optional, they are not available in the basic firmware version the unit is supplied with. For further information, please consult the AEQ Sales Department or authorized distributors. List of available coding algorithms in Phoenix MERCURY depending on the selected communication interface.

  • Page 43: Annexe C: Protocols Associated With Communications Over Ip Networks

    IP networks for the PHOENIX MERCURY user and, as a result, the use of this equipment. The user interested in expanding his or her...

  • Page 44: C1.1.2. Disadvantages

    • Theoretically, priorities can be assigned to the packets in a given communication. Thus, a node can select, from its queue of packets waiting to be transmitted, the ones that have higher priority. PHOENIX MERCURY...

  • Page 45: C1.2.3. Disadvantages

    (although not their correction) and of disorder in the information received; and the advent of the port concept as an identifier of different logic connections over the same IP interface. For complete information on IP protocol, we recommend consulting: http://tools.ietf.org/html/rfc791 http://www.iana.org/assignments/port-numbers PHOENIX MERCURY...

  • Page 46: C2.1. Ip Addresses

    Graphic Comparison: Unicast vs. Multicast The effect that unicast transmission has on network resources is accumulative consumption. Each user who connects to a multimedia transmission consumes as many kilobits per second as the content encoding will permit. PHOENIX MERCURY...

  • Page 47: C3. Rtp Protocol

    C3.1. PHOENIX MERCURY default configuration. PHOENIX MERCURY is an IP audio coder that operates by using RTP over UDP in IP version By default, PHOENIX MERCURY is supplied from the factory with the following IP ports defined: 5004 for RTP and 5005 for RTCP if this protocol is used.

  • Page 48: C4.1. Working Modes

    C4.1. Working modes. With the PROXY SIP option activated in the PHOENIX MERCURY, when the unit is started up it will automatically connect and register itself in the SIP Proxy server configured in its memory, indicating its name (URI: name@domain) and position (IP address, ports…).

  • Page 49: C4.2. Possible Work Scenarios

    C4.2. Possible work scenarios. Depending on the type of network to which the PHOENIX MERCURY is connected, the codec will have one or another type of IP address available to it. PHOENIX MERCURY...

  • Page 50: C4.3. Phoenix Mercury Default Configuration

    See section NAT TRAVERSAL (3.1.5.2.4). C4.3. PHOENIX MERCURY default configuration. To simplify operating the unit, AEQ offers, at no additional cost, the services of 2 own SIP servers. PHOENIX MERCURY is supplied from the factory with both SIP servers preconfigured (“Configuration”...
  • Page 51 PHOENIX MERCURY includes a STUN client that sends a request to a STUN server. The STUN server then informs the client of its public IP and which port has been opened by NAT to permit incoming traffic to enter the client’s network. This information enables the PHOENIX MERCURY to identify its position within the SIP server.
  • Page 52 For complete information on the STUN protocol, we recommend consulting: http://tools.ietf.org/html/rfc3489 AEQ always has a PHOENIX unit available for test at “[email protected]” URI (IP address: 83.175.227.74, at the moment this manual was written) and its 2 SIP servers are also available at sip.aeq.es and sip2.aeq.es and with warranty that both work according to the official standard.

  • Page 53: Annexe D: Ports Used By Phoenix Equipment

    IPs of Phoenix units installed in that private network. In that case, remote unit will send its packets towards router IP (it’s a public IP) and the ports configured in router by means of Port Forwarding (these are public ports), not to each Phoenix ports (these are private ports). PHOENIX MERCURY...

  • Page 54: Annexe E: Application Notes Guide

    Each application note describes the way to configure each of the audiocodecs. When both ends are different (for instance, at one end there’s a Phoenix Mobile and at the other end a Phoenix MERCURY), different application notes should be followed in order to configure each one.

Table of Contents