AEQ PHOENIX MERCURY User Manual

AEQ PHOENIX MERCURY USER’S MANUAL ED. 07/14 V. 1.0 - 21/07/2014 Firmware Versions: CPU 4.10 / DSP 3.11 or higher Software

AEQ PHOENIX MERCURY 103. CONFIGURATION AND OPERATION OPTIONS DESCRIPTION. Configuration and operation of Phoenix MERCURY is carried out by means

AEQ PHOENIX MERCURY 11We can find “CALL” and ”ON AIR” buttons/indicators at the right, as well as the “SYNC” indicator and audio presence indicat

AEQ PHOENIX MERCURY 123.2. IP interface connection modes. In order to establish an IP communication, first we need to choose one among three avai

AEQ PHOENIX MERCURY 13- Proxy Provider: enables you to select the external SIP server with which the unit will work from a previously stored list

AEQ PHOENIX MERCURY 14 When you create a Call Book, these fields describing a contact can be modified in the Call Book that can be accessed from a

AEQ PHOENIX MERCURY 153.2.3. RTP Point to Point (RAW). This type of connection is selected when the connection over IP will be an RTP type link

AEQ PHOENIX MERCURY 16b) Multicast: it is also possible to send the audio stream to a special “multicast” address, for example, 239.255.20.8. If t

AEQ PHOENIX MERCURY 173.3. NAT TRAVERSAL. NAT Traversal is a set of tools used by the equipment in order to surpass the NAT (Network Address Tran

AEQ PHOENIX MERCURY 18 1. SIP LOCAL IP: read-only parameter that tells you the IP of the IP interface of the unit as regards SIP, so that the lat

AEQ PHOENIX MERCURY 197. RTP PUBLIC IP: parameter that will tell the unit which public IP will correspond to the RTP of its IP interface, so that

AEQ PHOENIX MERCURY 2CONTENTS 1. INTRODUCTION...

AEQ PHOENIX MERCURY 20• LOWEST: generates a 40% higher binary rate and produces a 575ms additional delay. • LOW: generates a 50% higher binary r

AEQ PHOENIX MERCURY 21 However, when the interface is set up to work in any of the SIP modes, particular coding algorithms won’t be selected and c

AEQ PHOENIX MERCURY 22The parameters to be configured are: - Enable DHCP: enables the activation or deactivation of the automatic configuration

AEQ PHOENIX MERCURY 233.8. SNMP configuration. This unit can be remotely managed using SNMP (Simple Network Management Protocol) using one of the

AEQ PHOENIX MERCURY 24- phxCh1TxAudioThreshold (Audio threshold for channel 1's input) - phxCh1TxAudioInterval (Audio interval for channel

AEQ PHOENIX MERCURY 254. QUICKSTART USER’S GUIDE. To gain a complete grasp of the PHOENIX MERCURY, we recommend reading the previous chapters and

AEQ PHOENIX MERCURY 264.4. Audio. Section 2.2 of this manual describes in detail the physical connections at the back panel of the unit, but the

AEQ PHOENIX MERCURY 27 The same screen allows you to configure the type and size of the receiving buffer and FEC parameters as a function

AEQ PHOENIX MERCURY 28• You can monitor the status of the call on the screen: o CALLING. o CONNECTING (depending on the communication interfac

AEQ PHOENIX MERCURY 29 Check the SIP server configuration (“Proxy Provider”). Select one that is already configured from the list, for example the

AEQ PHOENIX MERCURY 35. CONTROL TERMINAL OVER WEB BROWSER. ...35 5.1. Upgrading the

AEQ PHOENIX MERCURY 30 Enter the IP address of the remote unit, either manually or getting it from the buttons: By clicking here, the last URI

AEQ PHOENIX MERCURY 314.5.2.2. Receiving and accepting an IP communication in PROXY SIP mode. If the IP interface is correctly configured and aut

AEQ PHOENIX MERCURY 32 • Enter “I/F Setup“ and click on “SIP Parameters”. Check that the “User Name” and “Display name” are configured. User name

AEQ PHOENIX MERCURY 33 Enter the IP address of the remote unit, either manually or getting it from the buttons: By clicking here,

AEQ PHOENIX MERCURY 344.5.3.2. Receiving and accepting an IP communication in DIRECT SIP mode. If the IP interface is correctly configured and au

AEQ PHOENIX MERCURY 355. CONTROL TERMINAL OVER WEB BROWSER. The Phoenix MERCURY includes a WebServer that enables you to execute numerous functio

AEQ PHOENIX MERCURY 364. To upgrade the codec, click on the UPGRADE option. 5. A user ID and password are requested (by default, both are aeq).

AEQ PHOENIX MERCURY 37 5. Modify the value in the MAC field associated with the Ethernet interface. 6. Press the “Apply” button. 7. Wait for

AEQ PHOENIX MERCURY 385.5. Status menu. By means of IP Status menu you can monitor some statistical parameters regarding the connection status of

AEQ PHOENIX MERCURY 396. TECHNICAL SPECIFICATIONS* Audio Inputs and Outputs Analog line input 2 x XLR female. 9Kohm. Electronic balancing. Line

AEQ PHOENIX MERCURY 41. INTRODUCTION. 1.1. General description. El AEQ PHOENIX MERCURY STUDIO is a multiformat, multi-algorithm audiocodec desi

AEQ PHOENIX MERCURY 407. A.E.Q. WARRANTY. AEQ warrants that this product has been designed and manufactured under a certified Quality Assurance S

AEQ PHOENIX MERCURY 41ANNEXE A: General characteristics of encoding modes. G.711: ITU encoding standard for processing audio signals in the huma

AEQ PHOENIX MERCURY 42ANNEXE B: List of available coding algorithms in Phoenix MERCURY. CODEC RATE (Kbps)Fs (KHz) Mode G.711 Ley A 64 8 MONO

AEQ PHOENIX MERCURY 43ANNEXE C: Protocols associated with communications over IP networks. Communication over IP networks differs notably from th

AEQ PHOENIX MERCURY 44• The circuit is fixed. Because a physical circuit is specifically dedicated to the communication session in question, once

AEQ PHOENIX MERCURY 45C1.2.3. Disadvantages: • Greater complexity of the intermediate switching devices, which need to have higher speed and gre

AEQ PHOENIX MERCURY 46C2.1. IP addresses. An IP address is a number that logically and hierarchically identifies an interface of a device in a ne

AEQ PHOENIX MERCURY 47C3. RTP Protocol. RTP are the initials of Real-time Transport Protocol. It is a transport level protocol used for the trans

AEQ PHOENIX MERCURY 48One of the objectives of SIP was to contribute a set of processing functions to apply to calls and capacities present in the

AEQ PHOENIX MERCURY 49 SIP protocol operation diagram. Phase 1: Registration. Phase 2: Search for the call

AEQ PHOENIX MERCURY 51.3. Available encoding modes. We recommend consulting ANNEXE A to see a detailed description, as well as additional informa

AEQ PHOENIX MERCURY 50• Static public IP addresses offer the ideal situation, since they guarantee that the IP interface of the codec will always

AEQ PHOENIX MERCURY 51PHOENIX MERCURY includes a STUN client that sends a request to a STUN server. The STUN server then informs the client of its

AEQ PHOENIX MERCURY 52The response further enables the STUN client to determine the type of NAT being used, since different NAT types handle incom

AEQ PHOENIX MERCURY 53ANNEXE D: Ports used by PHOENIX equipment. When Phoenix unit is installed in a private IP network and you want to establish

AEQ PHOENIX MERCURY 54ANNEXE E: Application notes guide. This index tries to give users guidance on selecting the most advisable application note

AEQ PHOENIX MERCURY 55ANNEXE F: Additional information. NOTE: This equipment complies with the limits for a Class A digital device, pursuant to

AEQ PHOENIX MERCURY 62. PHYSICAL DESCRIPTION OF THE UNIT. To understand how the PHOENIX MERCURY unit is wired and installed, you will first need

AEQ PHOENIX MERCURY 72.2. Description of the rear panel and connections. 2.2.1. Analog line stereo input. XLR - 3p female connector.

AEQ PHOENIX MERCURY 8 DB15 connector pinout identification - Pin 1: AES_IN+ - Pin 9: AES_IN- - Pin 2: N/A - Pin 10: N/A - Pin 3: N/A

AEQ PHOENIX MERCURY 9Physically, the connector is RJ45 10/100 BT, with the following pinout. RJ45 connector pinout 2.2.6. USB Port. The USB p