AEQ PHOENIX MERCURY Page 3 User Manual Download

Page: 3 / 54

AEQ

PHOENIX MERCURY

5. CONTROL TERMINAL OVER WEB BROWSER. ................................................................. 35

5.1. Upgrading the equipment firmware.................................................................................. 35

5.2. Configuring the MAC address associated with the Ethernet interface. ........................... 36

5.3. Technical Assistance Service and On-line manuals........................................................ 37

5.4. Saving and loading configurations. .................................................................................. 37

5.5. Status menu. .................................................................................................................... 38

5.6. SNMP............................................................................................................................... 38

5.6.1. Getting the Phoenix Mercury MIB file. .................................................................. 38

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

ANNEXE C: PROTOCOLS ASSOCIATED WITH COMMUNICATIONS OVER IP NETWORKS

..... 43

C1. Circuit switching versus packet switching. ....................................................................... 43

C1.1. Circuit switching..................................................................................................... 43

C1.1.1. Advantages:............................................................................................. 43

C1.1.2. Disadvantages:........................................................................................ 44

C1.2. Packet switching.................................................................................................... 44

C1.2.1. Switching Modes. .................................................................................... 44

C1.2.2. Advantages:............................................................................................. 44

C1.2.3. Disadvantages:........................................................................................ 45

C2. IP Protocol. ....................................................................................................................... 45

C2.1. IP addresses.......................................................................................................... 46

C2.2. Unicast vs. Multicast.............................................................................................. 46

C3. RTP Protocol. ................................................................................................................... 47

C3.1. PHOENIX MERCURY default configuration. ........................................................ 47

C4. SIP Protocol...................................................................................................................... 47

C4.1. Working modes...................................................................................................... 48

C4.2. Possible work scenarios........................................................................................ 49

C4.3. PHOENIX MERCURY default configuration. ........................................................ 50

C5. STUN protocol. ................................................................................................................. 50

ANNEXE D: PORTS USED BY PHOENIX EQUIPMENT. ......................................................... 53

ANNEXE E: APPLICATION NOTES GUIDE. ............................................................................ 54

E1. Internet connection using standard cable access. ........................................................... 54

Application note NA0A. ................................................................................................... 54

Application note NA0B. ................................................................................................... 54

Application note NA0C. ................................................................................................... 54

Application note NA0D. ................................................................................................... 54

Application note NA0E. ................................................................................................... 54

Application note NA0F. ................................................................................................... 54

E2. Special applications using different kinds of Internet physical accesses, or point to point
connections. ............................................................................................................................ 54

Application note NA1....................................................................................................... 54

Application note NA2....................................................................................................... 54

Application note NA3....................................................................................................... 54

Application note NA4B. ................................................................................................... 54

Application note NA5....................................................................................................... 54

Summary of Contents for PHOENIX MERCURY

Page 1: ...AEQ 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: ... is no NAT 17 3 3 2 Manual NAT MANUAL router configuration 17 3 3 3 AUTO 1 local network audio 19 3 3 4 AUTO 2 local network audio 19 3 3 5 AUTO 3 audio over internet 19 3 3 6 AUTO 4 audio over internet 19 3 4 FEC modes and reception buffer configuration 19 3 5 Coding profiles 20 3 6 Ethernet Port configuration 21 3 7 RS 232 Ancillary End to end data channel 22 3 8 SNMP configuration 23 4 QUICKSTA...

Page 3: ...sadvantages 44 C1 2 Packet switching 44 C1 2 1 Switching Modes 44 C1 2 2 Advantages 44 C1 2 3 Disadvantages 45 C2 IP Protocol 45 C2 1 IP addresses 46 C2 2 Unicast vs Multicast 46 C3 RTP Protocol 47 C3 1 PHOENIX MERCURY default configuration 47 C4 SIP Protocol 47 C4 1 Working modes 48 C4 2 Possible work scenarios 49 C4 3 PHOENIX MERCURY default configuration 50 C5 STUN protocol 50 ANNEXE D PORTS US...

Page 4: ...s We recommend your reading this manual and AEQ ControlPHOENIX software user s manual before using the unit although chapter 4 offers a quickstart user s guide 1 2 Functional specifications Management of full duplex channels mono or stereo Inputs Stereo analog audio input 2 x XLR female 9Kohm Electronic balancing Line level Optional digital audio input DB15 connector AES EBU interface Outputs Anal...

Page 5: ...ry mode exclusive for AEQ Phoenix which combines very high quality and low delay AAC LC and AAC LD are optional modes For more information please consult AEQ 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 POCKE...

Page 6: ...the status of the equipment s electrical power supply Off no power supply Green the unit is ON CALL LED Call status Blinking blue there is an incoming call Steady blue outgoing call or connected ON AIR audio presence LED Red ON AIR activated No audio is received from the remote codec Green ON AIR activated audio is received from remote codec Off ON AIR not activated When the unit starts up LED POW...

Page 7: ...t XLR 3p Female panel Pinout Pin 1 Æ Ground Pin 2 Æ Input Pin 3 Æ Input 2 2 2 Analog line stereo output XLR 3p male connector Balanced connection Two connectors for L R or independent mono channels 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 physi...

Page 8: ...ted over IP independently of the audio stream This same connector can be used to restore the default IP configuration in case that the unit can t be reached by the software after having been altered IP configuration is restored by turning the unit on while a bridge is present between pins 2 and 3 in this connector The default IP address is 192 168 1 84 2 2 5 Ethernet port LAN PHOENIX MERCURY is eq...

Page 9: ...CURY is a stationary IP audio codec fully compatible with the EBU TECH 3326 technical specification formulated by the EBU N ACIP working group which was developed to guarantee compatibility between different manufacturers in applications for contributing professional quality audio over IP networks For further information consult http tech ebu ch docs tech tech3326 pdf The connector is an RJ45 for ...

Page 10: ...in chapter 6 of AEQ ControlPHOENIX user s manual The screen corresponding to PHOENIX MERCURY is as follows The left zone shows the general communications channel status CONNECTED OK REGISTERING etc as well as the remote equipment s name in case it is connected We can click on this area in order to show a window that provides all the details of the channel Channel status OFF AIR ON AIR INTERFACE in...

Page 11: ... is possible to open up to two vumeter windows this is useful for example to check the correct audio transmission between two units that are connected and controlled by the application If you try to open a third vumeters window the first one will be closed Click on the right top cross in order to close a vumeters window The represented vumeters correspond from left to right to audio transmitted to...

Page 12: ...r phoenixMaster sip aeq es o unit_name SIP_server _IP for instance phxme_231 232 168 1 2 or phoenixMaster 232 168 1 2 where 232 168 1 2 is the AEQ s SIP server sip aeq es o unit_name SIP_server _IP Port when the SIP port of SIP server is not the 5060 SIP Standard port the identifier must include the used port for instance phxme_231 sip aeq es 5061 When you create a Call Book these fields describin...

Page 13: ...e IP port selected to transmit audio at origin over IP Minimum value 1 024 Maximum value 65 534 Usually recommended value 5004 o Adaptive Fixed and Adaptive buffer max this option allows you to configure the type and maximum size of reception buffer See section 3 4 o Symmetric RTP this option allows you to force the local unit to send audio to the same IP and port from which it is receiving audio ...

Page 14: ...es with NAT routers firewalls Each one of those modes is suitable for a different scenario For instance when the units that are establishing communication are in the same local network the internal working way will be different than when it s done through the Internet See more details in section 3 3 of this manual The rest of options to be configured are o FEC mode this option allows you to config...

Page 15: ...mended value 5004 o Adaptive Fixed and Adaptive buffer max this option allows you to configure the type and maximum size of reception buffer See section 3 4 o Symmetric RTP this option allows you to force the local unit to send audio to the same IP and port from which it is receiving audio The destination port specified when making the call will be ignored when we receive packets from the remote e...

Page 16: ...nfiguration screen Net1 or Net2 Once we have properly configured a RTP Raw channel we can add replicas or parallel streams which are only IP port pairs we want to send the audio to Note that FEC can be individually activated provided that it was enabled and configured in the general channel configuration see section 3 4 or it can also be disabled for certain replicas if you want If the list is emp...

Page 17: ...mentation and manuals work on this NAT configuration menu For additional information see ANNEXE C5 The NAT traversal options of a codec are accessed by following this sequence from the involved individual codec control window Configuration Æ General Æ I F Setup Æ NAT Traversal Next we will describe the operation without NAT and the other five modes supported by Phoenix MERCURY 3 3 1 Operation with...

Page 18: ... that it can include the said IP in its SIP messages The router or firewall administrator must tell you the value of this parameter For instance 212 170 180 177 4 SIP PUBLIC PORT parameter that will tell Phoenix which public port it will have corresponding to its local SIP port The router or firewall administrator must tell you the value of this parameter in order to make the required port forward...

Page 19: ...e used mainly when you wish to put two units in communication with each other through the Internet working with no Proxy DIRECT SIP mode or using the Proxy SIP provided by AEQ sip aeq es PROXY SIP mode The two configuration parameters available on screen for this mode are 1 STUN SERVER parameter that tells the unit the STUN server that will be used On the Internet there is multitude of public STUN...

Page 20: ...t audio is compromised as the buffer size reaches the network maximum jitter value At this point just increase the buffer a little bit to have some margin In high quality PCM connections you can start using highest quality modes 48KHz 24 bits mono or stereo only if required and if you can t obtain the desired quality and or estability no noises present and good delay you can lower quality progress...

Page 21: ...cs have several tens of encoding algorithms ir order to have the higher compatibility with other equipments When a communication is established using SIP signalling the codec negotiates the use of the first compatible encoding algorithm included in a list called SIP CODEC PROFILE That s why you should put these algorithms in order of preference Each one of the stored entries includes an alphanumer...

Page 22: ... to translate alphanumeric URL identifiers into IP addresses Once those parameters are configured and after pressing the Apply button a confirmation window will appear 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 technica...

Page 23: ...Audio detection event at Channel 1 s input phxCh1NoRxAudioAlarm Audio detection event at Channel 1 s output phxCh1NoAudioSyncAlarm Sync event at Channel 1 while connected phxCh1CallEndAlarm Call ended on Channel 1 due to incoming RTP traffic loss phxOtherAlarm Other alarms see name Fail to register in SIP PROXY server etc coldStart alarm Starting from unit off This is an standard SNMP alarm it app...

Page 24: ...h1TxAudio Ch1 s audio input indicator status Indicates the status of the virtual LED indicating audio presence according to the corresponding configurated parameters phxCh1RxAudio Ch1 s audio output indicator status Indicates the status of the virtual LED indicating audio presence according to the corresponding configurated parameters phxCh1OnAir Ch1 s ON AIR option activated or not phxCh1Synced C...

Page 25: ...ED is on steadily and LAN is blinking See section 2 1 of this manual The unit is ready to be used 4 3 Setting up a computer to control the unit Connect to the same network a computer with AEQ ControlPHOENIX software installed Follow what s indicated in chapter 3 of the application s user manual Steps 1 and 2 are not applicable to Phoenix MERCURY and step 3 only applies when controlling remote equi...

Page 26: ...for analog outputs and optional 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 4 5 1 Establishing an IP communication in RTP mode Ensure that the equipment is powered up and controlled by the software Establish the ...

Page 27: ... for all incoming calls or only those corresponding to a predefined caller o Auto hang up Automatic hang up whenever audio packets are missed for a given time o 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 Enter the IP address of the remote unit either manually or ge...

Page 28: ...ODER green window NOTE In order to make calls to multiple destinations please consult section 3 2 3 1 of this manual 4 5 1 1 Finalizing an IP communication in RTP mode To finalize the communication simply press the CALL button in the individual codec control window and then confirm Repeat the process in the unit at the other end 4 5 2 Establishing an IP communication in PROXY SIP mode Ensure that ...

Page 29: ...es useful to overcome NAT routers The same screen allows you to configure the type and size of the receiving buffer and FEC parameters as a function of the IP network quality so we have the shortest delay while audio cuts are minimized or eliminated in poor quality networks see paragraph 3 4 of this manual in order to select the optimal buffer configuration depending on your application Return to ...

Page 30: ...n SIP SERVER mode For example phxme_231 sip aeq es 5061 VERY IMPORTANT equipment s_name must not be longer than 19 characters Press the green Call button on the screen to make the call You can observe the changes of status from OK to CONNECTED and synchronized Verify that the SYNC LED beneath the CALL button is lighted in green to indicate that the communication has been successfully established P...

Page 31: ...s status can last for an extremely short time o CONNECTED Verify that the SYNC LED beneath the CALL button is lighted in green to indicate that the communication has been successfully established Press the ON AIR button to allow the transmission of full duplex audio for that channel Send audio from one equipment to another verifying that the Tx and Rx audio presence indicators change to green If n...

Page 32: ...or eliminated in poor quality networks see paragraph 3 4 of this manual in order to select the optimal buffer configuration depending on your application Return to the general configuration screen check that the selected coding algorithm in the green ENCODER area is correct or otherwise click on Select codec to change it There are several pre defined profiles containing several particular algorith...

Page 33: ...in use For example phxme_ 231 172 25 32 11 5061 VERY IMPORTANT equipment s_name must not be longer than 19 characters Press the green Call button on the screen to make the call You can observe the changes of status from OK to CONNECTED and synchronized Verify that the SYNC LED beneath the CALL button is lighted in green to indicate that the communication has been successfully established Press the...

Page 34: ...lternatively on the Accept button in the incoming calls window The screen will show the status of the call o CONNECTING depending on the network status this status can last for an extremely short time o SYNCHRONIZING depending on the network status this status can last for an extremely short time o CONNECTED Verify that the SYNC LED beneath the CALL button is lighted in green to indicate that the ...

Page 35: ...Service via electronic mail sat aeq es IMPORTANT NOTE If the MICRO CPU of the equipment is upgraded part of its configuration may be modified specifically the part having to do with the MAC addresses URIs the SIP Proxy Server Users and the associated Passwords It is important to make a note of these codec parameters before upgrading in order to reconfigure them afterwards The entire Phoenix MERCUR...

Page 36: ... 11 In the Internet browser go to the UPGRADE section and ensure that all the firmware versions installed in your codec are now the correct ones 12 Power the unit down and up 5 2 Configuring the MAC address associated with the Ethernet interface From this menu the MAC addresses associated with the Ethernet interface can be edited because of the consequences this action could have the address shoul...

Page 37: ...reen 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 5 4 Saving and loading configurations In the MAINTENANCE section see section 5 2 in the lower part of the screen you will see the CONFIGURATION MEMORY option from which you can save the cu...

Page 38: ...the list of units managed by the client it is necessary to have access to its MIB file Management Information Base that describes its SNMP capabilities alarms it can generate accepted commands manufacturer information etc 5 6 1 Getting the Phoenix Mercury MIB file The MIB file corresponding to the unit can be downloaded from the Web interface without installation of any additional software In orde...

Page 39: ...e 64 128Kbps Mode Mono Stereo Dual JStereo MS Stereo Frequency response 0 5dB 20Hz 20KHz Sampling rate Analog I O A D D A converter 24 bit Sigma Delta 48 kHz max Communication interface Standard IP interface RJ 45 Ethernet Port LAN 10 100 base T Standard IP interface Compatibility Fully compliant N ACIP EBU Tech 3326 Standard IP interface SIP Signaling Compliant with EBU Tech 3326 recommendation S...

Page 40: ... of products to be repaired or replaced in application of this warranty No product returns that do not comply with these terms will be accepted 3 AEQ will repair a factory defective product to include the labour required to perform the repair work provided that the failure is caused by defects in the materials design or labour The repair shall be done in AEQ s Technical Assistance Service offices ...

Page 41: ...ding modes with sampling rates of 48 32 or 24KHz and 128kbps encoding modes with sampling rates of 32 and 48KHz Bandwidth 10KHz to 15KHz For further information on this subject consult ISO IEC 11172 3 and ISO IEC 13818 3 AEQ LD AEQ proprietary mode based on the previous AEQ LD Extend mode that combines the low delay offered by G 722 with the greater bandwidth of the MPEG modes optimizing these two...

Page 42: ...6 24 32 48 M ST MST 128 24 32 48 M ST 192 24 32 48 M ST AAC LC 256 48 M ST 32 48 MONO 64 48 M ST MST 96 48 M ST MST 128 48 M ST 192 48 M ST AAC LD 256 48 M ST 768 32 M ST 1152 48 M ST 1024 32 M ST 1536 48 M ST 1280 32 M ST 2M 48 M ST 1536 32 M ST PCM 2 4M 48 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 f...

Page 43: ...e this appendix is not intended to be a reference document for all the relevant technical matters it should at least serve to give its readers an initial contact with these subjects that will ease the assimilation of the new working method over IP networks for the PHOENIX MERCURY user and as a result the use of this equipment The user interested in expanding his or her knowledge of some or all of ...

Page 44: ...essage to be sent into an arbitrary number of packets of the same size to which a header and the originating and destination addresses are added as well as control data that will then be transmitted through different communication media between temporary nodes until they reach their destination This switching method is the one that is used in today s IP networks It has emerged to optimize transmis...

Page 45: ...r any mechanism to determine whether a packet reaches its destination and only provides security by means of checksums to cover its headers and not the transmitted data For example since it gives no guarantee that the packet will reach its destination it could arrive damaged in the wrong order with respect to other packets duplicated or simply not arrive If reliability is needed it is provided by ...

Page 46: ...tly due to the poor management that has traditionally been applied to the available IP addresses they are a scarce highly costly resource Private addresses that are only valid in a closed section of the IP network typically corporate and not subject to free access with only one point of connection to the Internet called a gateway constituted by a router C2 2 Unicast vs Multicast Unicast is the tra...

Page 47: ...ng http tools ietf org html rfc1889 http tools ietf org html rfc1890 http tools ietf org html rfc3550 http tools ietf org html rfc3551 http tools ietf org html rfc3711 C3 1 PHOENIX MERCURY default configuration PHOENIX MERCURY is an IP audio coder that operates by using RTP over UDP in IP version 4 By default PHOENIX MERCURY is supplied from the factory with the following IP ports defined 5004 for...

Page 48: ...iences that this may produce for the end user The unit leaves the factory preconfigured with the parameters required to work with the resources of any of these 2 SIP servers SIP makes use of elements called proxy servers to help route the requests toward the user s current location authenticate users to give them service enable call routing policies to be implemented and contribute added capabilit...

Page 49: ...fier and through the use of the SIP protocol makes it unnecessary to know more data regarding the called device than its URI During the establishment of the communication phase the encoding algorithm is negotiated simultaneously based on the Link Profiles SIP Codec Profiles defined in each of the devices at the two ends of the connection circuit C4 2 Possible work scenarios Depending on the type o...

Page 50: ...e network and the public one 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 Æ General Æ INTERFACE Net1 SIP Proxy based Æ I F Setup Æ SIP Parameters Æ Proxy Provider defined as...

Page 51: ...d 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 This protocol is used in AUTO3 and AUTO4 NAT TRAVERSAL modes see section 3 1 5 2 4 Registration in a STUN Server Notification from the server of the corresponding NATs detected ...

Page 52: ...deo and text traffic over the Internet but does not enable communication to be established when the devices at the ends of the communication circuit are behind NAT routings This is why STUN is customarily used in these applications to permit communication to be established The connection with the STUN server is normally made through port 3478 by means of UDP The STUN server can then provide the cl...

Page 53: ...it may vary remote control protocol only when Phoenix must be connected to PC and PC is not in its network Port depends on PC not on Phoenix 2 Input permissions in router firewall Phoenix unit will have to be able to receive packets from units installed out of the private network Therefore firewall will have to allow that packets sent to Phoenix unit IP to the following ports are received UDP 161 ...

Page 54: ...ed to Phoenix Mobile Application note NA0C Phoenix MERCURY Studio or Venus audiocodec connected to a LAN together with other IP equipments connected to Internet by means of a router with NAT that can be configured or we have access to the Network Manager SIP call using AEQ SIP Proxy Application note NA0D Same case as NA0C but adapted to Phoenix Mobile Application note NA0E Same case as NA0C but ca...

Search results

Summary of Contents for PHOENIX MERCURY

Reviews:

Related manuals for PHOENIX MERCURY

Brands by name

Popular brands

AEQ PHOENIX MERCURY, User Manual

Search results

Summary of Contents for PHOENIX MERCURY

Reviews:

Related manuals for PHOENIX MERCURY

Brands by name

Popular brands