Page 1 PHOENIX MOBILE USER’S MANUAL ED. 10/11 V. 1.0 - 24/10/2011 Firmware Versions: Micro 4.40 / DSP 5.08 / FPGA 1.47 or higher PGA-01 POTS Module: Micro 1.05 PGA-03 ISDN Module: Micro 1.01 / TA 6.00...
Page 2: Table Of Contents
1.1. General overview..................... 1.2. Functional specifications.................. 1.3. Available encoding modes................1.4. Block diagram....................1.5. Compatibility with other AEQ codecs............... 1.6. Compatibility with other manufacturers’ codecs..........2. PHYSICAL DESCRIPTION OF THE UNIT..............2.1. Description of the front panel and connections..........10 2.1.1.
Page 3 5.6.1. Ending an ISDN communication............5.6.2. Reception and acceptance of an ISDN communication...... 72 5.7. Establishment of a GSM communication (USB interface)....... 5.7.1. Ending a GSM communication (USB interface)........5.7.2. Reception and acceptance of a GSM communication (USB………… interface)…………………………………………………………………… 73 PHOENIX MOBILE...
Page 4 E2. SPID’s (Service Profile Identification Numbers)..........104 E3. Line characteristics for the USA. Line request model........104 E4. Connecting the PHOENIX MOBILE to the ISDN line........104 ANNEXE F: 3G and GSM Communications..............105 ANNEXE G: Application notes guide................106 G1.
Page 5: Introduction
1. INTRODUCTION. 1.1. General overview. The PHOENIX MOBILE is an IP audio codec for mobile applications. It includes a digital mixer with four analog inputs, an optional LI-ION battery, a 3.5” multifunction display screen and a 12V DC battery charging power unit.
Page 6: Available Encoding Modes
MPEG-4 HE-AAC 32 Kbps mono 48 KHz** √ AEQ LD+ 128 Kbps mono 32 KHz mode is a proprietary mode, exclusive for AEQ Phoenix, which combines very high quality and low delay. ** AAC-LC and HE-AAC are optional modes. For more information, please consult AEQ Sales Department or authorized AEQ distributors.
Page 7 16.875 High AEQ LD+ 128 Kbps mono 32 KHz mode is a proprietary mode, exclusive for AEQ Phoenix, which combines very high quality and low delay. ** AAC-LC and HE-AAC are optional modes. For more information, please consult AEQ Sales Department or authorized AEQ distributors.
Page 8: Block Diagram
1.4. Block diagram. For further information, see complete diagrams in annexe B. PHOENIX MOBILE...
Page 9: Compatibility With Other Aeq Codecs
1.5. Compatibility with other AEQ codecs. The PHOENIX MOBILE offers its users the option of connecting with other AEQ equipments. It’s compatible with the PHOENIX STUDIO in IP communications. The POTS module enables its users to communicate with other devices that include telephone hybrids such as TH02-EX, TLE02, TLE02D MPAC, SWING and COURSE hybrid boards, in addition to offering the added possibility of a frequency extender.
Page 10: Physical Description Of The Unit
Common ground Pin 2 + Input Pin 3 - Input Pin 4 + Output Pin 5 - Output 2.1.2. Headphones 1 and 2 output (“HP 1“ and “HP 2“). ¼” TRS Jack connector. Asymmetrical connection. TRS Jack pinout PHOENIX MOBILE...
Page 11: Microphones 1 And 2 Input ("Mic1" And "Mic2")
The level of input signals MIC1, MIC2 y MIC/LINE and the level of output signals HP1 and HP2 are modifiable through the rotary encoders associated with each signal on the control surface. PHOENIX MOBILE...
Page 12: Description Of The Rear Panel And Connections
PGA-01, PGA-02, PGA- 03 or any other module AEQ may develop in the future. At the time this manual was written, PGA-01 POTS and PGA-03 ISDN communication modules are available.
Page 13: Left Additional Communication Module
PGA-01, PGA-02, PGA- 03 or any other module AEQ may develop in the future. At the time this manual was written, PGA-01 POTS and PGA-03 ISDN communication modules are available.
Page 14: Power Supply
The power switch (push button) is located on the left side of the unit. 2.2.6.2. Power supply / Battery charger. The AEQ PHOENIX MOBILE can be supplied with electric power from an external battery charger / power feed unit specifically designed for this purpose through the 12V DC-INPUT connector.
Page 15 Universal charger and power feed cable supplied Pinout of the mini-XLR 3p female battery charger connector: Connector viewed from the soldered part XLR 3P pinout Pin 1 Ground Pin 2 Pin 3 Not used PHOENIX MOBILE with battery PHOENIX MOBILE without battery PHOENIX MOBILE...
Page 16: Description Of The Control Surface
2.3. Description of the control surface. The following paragraphs describe the various functional areas that make up the control surface. PHOENIX MOBILE...
Page 17: Multifunction Display Screen And Navigation Keys
Also included are 2 keys to accept/cancel the current operations in the menus, and 2 keys to call/off-hook/hang-up telephone calls made or received by the user. 2.3.1.1. Battery charging indicator. For further information, please consult section 5.2 in this manual. PHOENIX MOBILE...
Page 18: On-Hook / Off-Hook Keys
Shows the configuration and operating menus, information on the connection and audio VU meters, which can measure input and output audio signals. The AEQ PHOENIX MOBILE includes a 240x320-pixel color TFT screen that displays the internal codec menu, which is accessed by using the set of keys located under display.
Page 19 (while negotiating with your phone provider the communication parameters and IP address), red (while PHOENIX MOBILE is registering into the SIP server) or blue (once the process, that may take up to 10 seconds, is completed).
Page 20 2.- Call status information section. In the idle state, only the time and the AEQ logo are displayed. When there is an outgoing or incoming call, the called or calling telephone number is displayed and, once the call is accepted, the information on the progress of the negotiation / synchronization of the call is shown.
Page 21 (only for POTS communications with HE-AAC encoding mode). All the fields here can be modified by using the ”Select” option. This screen is also accessible from the fast-access “CHN“ button on the control surface (this button is active only when you’re in the start-up screen). PHOENIX MOBILE...
Page 22: Alphanumeric Keypad
“#” (see section 4.2). It also allows DTMF (multifrequency) dialing tones to be generated. The keys backlighting blinks to notify the user of an incoming call when the buzzer (audible notification of calls) is OFF. 2.3.3. Function and routing keys and communication status LEDs. PHOENIX MOBILE...
Page 23: Audio Controls
The key placed above the encoder allows you to active/deactive the sending of signal to the Headphone 1 output (“HP1”). PHOENIX MOBILE...
Page 24 This selection is shown on the start-up screen. When you press again, the control returns to its normal functionality. The key placed above the encoder allows you to active/deactive the sending of signal to the Headphone 2 output (“HP2”). PHOENIX MOBILE...
Page 25: Ethernet Interface
2.4. Ethernet Interface. PHOENIX MOBILE is a portable encoder over IP, 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...
Page 26: Communications Module: Isdn
The connector used is a standard RJ45 connector for S interface and a standard RJ11 connector for U interface. 2.5.3. Other PGA communication modules. In this area, depending on market needs, when the time comes, other communication interfaces will be marketed for GSM, 3G, Wifi/Wimax, Bluetooth, etc. PHOENIX MOBILE...
Page 27: Usb Interface
2.6. USB Interface. The USB port of PHOENIX MOBILE allows you to connect a mobile phone (by means of mobile phone data cable and, depending on the unit edition, an USB B to USB A adapter or an USB Micro A to USB A adapter) in order to establish a GSM or 3G communication. When plugging a mobile phone, it will be automatically recognized by PHOENIX MOBILE.
Page 28: Batteries Pack
2.7. Batteries pack. The PHOENIX MOBILE is supplied by default with a battery charger / power supply and, as an option, can include a batteries pack of the Li-Ion type (3500 or 4000mAh / 7.4V), which will power the codec for an average of more than 2.5 hours in normal operating mode, with easy removal as an additional feature, and whose machining includes an integrated carrying handle.
Page 29: Basic Configuration Menu Description
Program channel, because no GSM communication can be established over Coordination channel. When you select “IP (3G)” option the data package connection through the mobile phone is activated automatically and when you change the selected interface it’s also automatically ended. PHOENIX MOBILE...
Page 30 Phone over POTS interface. When USB interface is associated with Coordination channel, only a 3G communication with G711 A-Law and G711 µ- Law algorithms can be established; no GSM communication can be established over that channel. PHOENIX MOBILE...
Page 31 Both channels are full-duplex, but Program is reserved for an encoded channel which will consequently be a high quality channel, while Coordination is a lower quality channel. By default, PHOENIX MOBILE is supplied from the factory with Ethernet interface associated with Program and right slot associated with Coordination.
Page 32: Advanced Menu Description
(“Select”), to enter the advanced menu of the unit. Menu access Advanced menu diagram The internal diagram of this main menu is detailed in the following paragraphs. Advanced menu organization diagram From this menu you can configure all of the operational parameters of the unit. PHOENIX MOBILE...
Page 33: Call Register
If the contact name is not in the internal phone book, it is identified as "Unknown". • Channel used for the communication: “Program” or “Coordination”. • Communication module over which the connection was established: IP or Phone (POTS, ISDN or GSM). • Information about date, time and length of the communication. PHOENIX MOBILE...
Page 34: Contacts
The system will ask for your confirmation. • Completely empty the phone book: Menu >> Advanced >> Contacts >> Options >> Delete All. This action eliminates all the contacts stored in the phone book. The system will ask for your confirmation. PHOENIX MOBILE...
Page 35: Audio Settings
4.3. Audio settings. The PHOENIX MOBILE is a complete router and digital audio mixer. Although its inputs and outputs (MIC, HP and AUX) are analog, the first and the last step is a 24-bit A/D and D/A converter with sampling frequency of 48KHz.
Page 36: Crosspoint
The internal matrix inputs that are available for each one of the outputs are: The send or crosspoint is established when ON and disabled when OFF. You can make this modification by pressing the key associated with the Select option in the screen. PHOENIX MOBILE...
Page 37 >> Output >> HP 1 and HP 2), you could configure the routing, for instance, the following way: Example of HP routing in custom-stereo mode The PHOENIX MOBILE units come from the factory configured with the following routing structure: •...
Page 38: Mixer
NOTE: Regardless of the level selected in this section, the routing will not take effect until the corresponding crosspoint is activated in the section Menu >> Advanced >> Audio settings >> Routing >> Crosspoint. The PHOENIX MOBILE units leave the factory configured with all the mixing factors at 100%. PHOENIX MOBILE...
Page 39: Input
(or unbalanced) signals. In professional applications, we recommend always to work with balanced signals. You can also access to this submenu by pressing the encoder associated with MIC1 or MIC2 on the control surface (see section 2.3.4). PHOENIX MOBILE...
Page 40: Mic/Line
(letting that signal pass to the internal digital mixing module inside the unit) and gain control (between 0dB and -80dB). 4.3.2.5. Default configuration. The PHOENIX MOBILE units leave the factory configured with the following parameters: • Offset of nominal gain adjustments at 0dB (Gain in “Input” menu).
Page 41: Hp1 And Hp2
0dB and -80dB. 4.3.3.4. Default configuration. The PHOENIX MOBILE units leave the factory configured with the following parameters: • Offset of nominal gain adjustments at 0dB (Gain in “Output” menu).
Page 42: Modules Config
Menu for configuring the optional communication modules. The access is Menu >> Advanced >> Modules Config.; it can also be accessed by pressing the quick access button “MOD” in the control surface (this button is active only from the start-up screen). Modules Config. menu PHOENIX MOBILE...
Page 43: Communication Interfaces Associated With Channels
“L1” or “L2” in order to indicate which one of the 2 B channels is associated with that channel (see section 3). By default, PHOENIX MOBILE is supplied from the factory with Ethernet interface associated with Program and right slot associated with Coordination.
Page 44: Configuration Of The Slot For The Isdn Module
Detail of ISDN menu “ISDN Configuration” menu allows to define the different options associated with the operation of the ISDN interface in the equipment, whereas “ISDN Parameters“ menu allows to form the different technical parameters associated with The ISDN standard interface. PHOENIX MOBILE...
Page 45 Protocol: Allows you to select EUROISDN or National-1. In USA in spite of several incompatible protocols between, thankfully exists a protocol standardized enough (named National-1) and that is in the habit of being available in all the plants. For more information, please consult annexe E. PHOENIX MOBILE...
Page 46 • MSN L2: The same for the line 2 (second B channel). Detail of ISDN Parameters submenu In case of doubt, AEQ recommends to consult with your carrier or service provider, and see annexe E in this manual. 4.4.2.2. [L].
Page 47: Communications
4.5. Communications. Menu for configuring the communication interfaces. The access is Menu >> Advanced >> Communications. PHOENIX MOBILE...
Page 48: Ethernet Interface Configuration
Typically, your mobile phone will be pre-configured with the operator’s APN (Access Point Name) in order to function in 3G; all you need to configure in the PHOENIX MOBILE is the user name and password requested by your operator in order to have access to 3G connection and the 3G network tye (UMTS or EV-DO).
Page 49: Sip Configuration
4.5.3.1. Parameters. This menu enables you to configure certain parameters associated with the SIP protocol implemented in the unit, as well as all of the STUN protocol parameters. For more information about both protocols, we recommend consulting annexe C. PHOENIX MOBILE...
Page 50 STUN Protocol Port: Identifier of the IP port over which you wish the STUN protocol to work, assuming it is activated. By default, PHOENIX MOBILE will be supplied from the factory with a perfectly valid port, ready to be used to establish communication.
Page 51: Proxy
This menu includes all configuration linked to the SIP Proxy, which will act as an intermediary in the communication, simplifying its establishment. To simplify the operation of the unit, AEQ offers without aftercost for Phoenix Mobile users the services of a proprietary SIP server, though 100% of the time can neither guarantee functioning nor make responsible for the disadvantages that it could suppose therefore the final user.
Page 52: Sap Config
IP: IP address of the SAP server, which will act as an intermediary in the communication, simplifying its establishment. If you have any doubts about this, consult your network administrator. By default, PHOENIX MOBILE will be supplied from the factory with a perfectly valid address, ready to be used to establish communication.
Page 53: Link Profiles
The access is Menu >> Advanced >> Link Profiles. PHOENIX MOBILE is an audio codec whose IP interface is absolutely compatible with the EBU- TECH 3326 standard formulated by the N/ACIP working group. This standard, originally...
Page 54 AAC-LC and HE-AAC are optional modes. For more information, please consult AEQ Sales Department or authorized AEQ distributors. ** AEQ LD+ 128 Kbps mono 32 KHz mode is a proprietary mode, exclusive for AEQ Phoenix, which combines very high quality and low delay.
Page 55: Add A New Profile To The List
• LOW DELAY: Comprehends a set of algorithms, prioritizing according to the required delay, the following way: AEQ LD+ 128 Kbps mono 32 KHz ITU G.711 A-Law mono ITU G.711 µ-Law mono MPEG-2 LII 64 mono 16 KHz • MPEG LII 128 Kbps: Comprehends the 128 Kbps MPEG LII family of algorithms, the...
Page 56: Editing A Profile On The List
The system will request confirmation of this action. 4.7. Applications. This is an advanced functions menu that includes the options for configuring the SAP option, the on-screen VU meters and the DLP option and RTP communication statistics. Applications menu PHOENIX MOBILE...
Page 57: Sap
From the list that is displayed in this menu, all you need to do is select an entry for which PHOENIX MOBILE will automatically tune in this transmission. All the communications logged in this SAP server are of the multicast type, which means that the user, who selects one of them for reception, must previously have confirmed that all the network sections linking the transmitter with the receiver implement multicast capabilities.
Page 58: Rtp Statistical
Delay Factor: indicates the delay between the arrival of an IP packet and the reading of that packet from the reception buffer. • Media Lost Rate: percentage of losses in transmitted IP packets that carry streaming application information. PHOENIX MOBILE...
Page 59: Maintenance
This option is shown only when there is a battery connected to the unit. It shows information regarding the battery in the unit. When the equipment is connected/disconnected from mains power, the information contained in this menu needs a few seconds to refresh the values. Detail of battery status PHOENIX MOBILE...
Page 60: Fw (Firmware) Version
Alarm Low Bat.: It indicates if the alarm associated with a low/critical available battery level is active or not. PHOENIX MOBILE will emit a warning when approximately 10 minutes of estimated battery charge remains and an alarm when one minute of available battery level remains.
Page 61: Diagnostics
SIP server, the unit NAT type, its private IP and its private audio port, as well as whether the call is made from Program channel or from Coordination channel. By default, this option (“SIP Diag. Headers”) is deactivated (OFF). Detail of Diagnostics menu PHOENIX MOBILE...
Page 62: Settings
The modification of any parameter is simply a matter of selecting the field to change with the navigator up and down arrows, pressing the Select option and changing the value that is displayed on the screen with the left and right navigator arrows. PHOENIX MOBILE...
Page 63: Local Config
Detail of Local Config 4.9.3. Ethernet Config. See section 4.5.1. 4.10. Users. You can access to PHOENIX MOBILE as Administrator user, with access to all the configuration options, or as Normal user, with restricted and configurable (by Administrator) access. Detail of Users menu...
Page 64 PHOENIX MOBILE is supplied from the factory configured to access as Administrator user when you turn on the unit. This way, the following options are displayed in “Users” menu: • Logout: allows you to leave Administrator user and access as Normal user. The system will ask for your confirmation.
Page 65: Quickstart User's Guide
If necessary, connect the auxiliary input/output using XLR-5p male connector. The setup of these Aux I/O can be done in Menu >> Advanced >> Audio settings >> Input >> Aux In and Menu >> Advanced >> Audio settings >> Output >> Aux Out. PHOENIX MOBILE...
Page 66: Communications Interface
ISDN module (see section 2.5.2). • GSM or 3G connection: Connect a mobile phone to USB port of PHOENIX MOBILE by means of mobile phone data cable and, depending on the unit edition, an USB B to USB A adapter or an USB Micro A to USB A adapter.
Page 67: Review Of The Configuration
• Check that the sends from the crosspoints have the desired level. If they do not, establish that level. The PHOENIX MOBILE units leave the factory configured with all the mixing factors at 100%. • Go to Channels configuration menu (see section 3) and check the communication modules associated with Program and Coordination.
Page 68: Establishment Of An Ip Communication (Ethernet Interface)
When “SIP Proxy” function is activated, the interface icon shown on the TFT screen will change to red background while PHOENIX MOBILE is registering into the SIP server, and finally blue once the register is completed correctly. When the unit has not been registered in the SIP server correctly, the message “Register Error”...
Page 69: Ending An Ip Communication (Ethernet Interface)
(see section 1.3). • Select communication destination manually introducing the number or by selecting a contact from the phone book): “Call to” and “Select contact”/”Enter number” in the channel basic configuration menu. PHOENIX MOBILE...
Page 70: Ending A Pots Communication
(it will light up on red). The automatic answering mode can be activated/deactivated in Menu >> Advanced >> Modules Config >> [R] or [L]: Slot POTS (depending on the slot in which the POTS module is physically installed) >> Off-Hook Mode. PHOENIX MOBILE...
Page 71: Establishment Of An Isdn Communication
You must select the same mode in both units in order to get a correct synchronization. 5.6.1. Ending an ISDN communication. • To end the communication, you need only to press the red button on the control surface. At the other end of the communication, the call will be automatically terminated. PHOENIX MOBILE...
Page 72: Reception And Acceptance Of An Isdn Communication
(Program) corner on the TFT screen. • Select the enconding mode: “Sel. codec" in the channel basic configuration menu. The available modes vary according to the selected channel (see section 1.3). PHOENIX MOBILE...
Page 73: Ending A Gsm Communication (Usb Interface)
Select the communication destination by manually introducing the number (the number of the mobile phone connected to the PHOENIX MOBILE that will receive the call or the number the POTS module is connected to in that other unit) or by selecting a contact from the phone book: “Call to”...
Page 74: Interface)
(Access Point Name) in order to function in 3G; all you need to configure in the PHOENIX MOBILE is the user name and password requested by your operator in order to have access to 3G connection and the 3G network tye (UMTS or EV-DO).
Page 75: Ending An Ip-3G Communication (Usb Interface)
IMPORTANT NOTE: The use of Phoenix Mobile with mobile phones connected through USB port is not supported nowadays by AEQ (although it may work in many cases), because there are compatibility problems with many phones that don’t follow strictly the required communication protocols, besides the low capacity of data transmission that GSM provides in order to send high quality encoded audio.
Page 76: Firmware Upgrading
In order to upgrade the firmware of the unit, this procedure must be followed: 1. Turn off PHOENIX MOBILE. 2. Connect PHOENIX MOBILE to the PC that will be use for upgrading process by means of a crossed cable from the PC´s network board to the PHOENIX MOBILE´s Ethernet port.
Page 77 2) Press “Send File” and check that the following message appears: “File: phxcpu.afu saved to memory”. Go back to previous menu. 3) Press “Upgrade” and check that PHOENIX MOBILE TFT screen shows the following message: “Warning. CPU upgrading!!!”. 4) Check that “UPGRADE OK” message appears in Internet Explorer and “Warning.
Page 78 2) Press “Send File” and check that the following message appears: “File: phxpotleft.afu saved to memory” (or “File: phxpotright.afu saved to memory”). Go back to previous menu. 3) Press “Upgrade” and check that PHOENIX MOBILE TFT screen shows the following message: “Warning. Module Left upgrading!!!” (or “Warning. Module Right upgrading!!!”).
Page 79: Technical Specifications
G.711, G.722, Mpeg Layer 2, AEQ LD+ and AAC (optional). PGA-01 POTS AEQ POTS and AAC (optional). PGA-03 ISDN G.711, G.722, Mpeg Layer 2 , AEQ LD+ and AAC (optional). Data and control interface Configurable USB 1.1: slave or master. 10 Base T LAN...
Page 80 Consumption 10.4VA. Batteries pack duration More than 2.5 hours in normal operation *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 MOBILE...
Page 81: Warranty
6.- AEQ shall under no circumstance and in no case be responsible for any type of damages, whether direct or indirect, derived from the use or the impossibility of using the product.
Page 82: Annexe A: Characteristics Of The Encoding Modes
For further information on this subject, consult: http://www.digitalpreservation.gov/formats/fdd/fdd000016.shtml 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 aspects.
Page 83 It is an extension of Low Complexity AAC (AAC-LC) optimized for low bit-rate applications such as audio streaming. Version 1 was standardized in 2003 by the MPEG group and was published under the aegis of MPEG-4 in the document ISO/IEC 14496-3, Amd.1:2003. PHOENIX MOBILE...
Page 84: Annexe B: Detailed Block Diagrams
ANNEXE B: Detailed block diagrams. Detailed block diagram of the analog audio part PHOENIX MOBILE...
Page 85 Detailed block diagram of the digital audio part PHOENIX MOBILE...
Page 86: Annexe C: Protocols Associated With Communication Over Ip Networks
IP networks for the PHOENIX MOBILE user and, as a result, the operation of this equipment. The user interested in expanding his or...
Page 87: C1.1.2. Disadvantages
(for example, in case one or more of the routers breaks down). 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 MOBILE...
Page 88: C1.2.3. Disadvantages
For all these reasons, the protocol selected to serve as a communication substrate in Real-time Applications is UDP. PHOENIX MOBILE...
Page 89: C2.1. Ip Addresses
(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,AEQ recommends consulting: http://tools.ietf.org/html/rfc791 http://www.iana.org/assignments/port-numbers IP Encapsulation C2.1.
Page 90: C2.2. Unicast Vs. Multicast
Management of the reception buffer in order to minimize the jitter effect introduced by the network. • Recovery of the reference clock based on information inserted by the transmitting equipment. • Test tools to permit the user to verify the bandwidth, the delay and estimated jitter in the connection. RTP header PHOENIX MOBILE...
Page 91: C3.1. Phoenix Mobile Default Configuration
C3.1. PHOENIX MOBILE default configuration. PHOENIX MOBILE is an IP audio coder that operates by using RTP over UDP in IP version 4. By default, PHOENIX MOBILE is supplied from the factory with the following IP ports defined: 5004 for RTP and 5005 for RTCP if this protocol is used.
Page 92: C4.1. Working Modes
C4.1. Working modes. With the SIP option activated in the PHOENIX MOBILE, 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).
Page 93: C4.2. Possible Work Scenarios
Link Profiles defined in each of the devices at the two ends of the connection circuit. C4.2. Possible work scenarios. Depending on the type of network to which the PHOENIX MOBILE is connected, the codec will have one or another type of IP address available to it.
Page 94 DIR IP PUBLICA ROUTER ROUTER DIR IP DIR IP PUBLICA INTERNET PUBLICA DIR IP DIR IP PRIVADA PRIVADA RED IP RED IP PRIVADA PRIVADA DIR IP DIR IP PRIVADA PRIVADA Notification from the server of the corresponding NATs detected PHOENIX MOBILE...
Page 95: C5.1. Phoenix Mobile Default Configuration
PHOENIX MOBILE 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 MOBILE to identify its position within the SIP server.
Page 96 RTP as a transport protocol. The SAP protocol is almost entirely based on multicast type transmissions, which makes it practically unviable in Internet environments, and limits its application to environments or sections of generally private networks with multicast features implemented. PHOENIX MOBILE...
Page 97: C6.1. Phoenix Mobile Default Configuration
We recommend activating the SIP, SAP and STUN options because they greatly simplify the operation of the unit, so that when the PHOENIX MOBILE is powered up and is connected to an IP network, it will automatically perform the following actions: •...
Page 98: Annexe D: Digital Level Processor (Dlp)
ANNEXE D: Digital Level Processor (DLP). The digital level processor (DLP) is an additional feature included in the PHOENIX MOBILE that was developed to improve the quality of the processed signal by modifying its level. According to the configuration, the DLP will make it possible to: increase the program signal level.
Page 99: D1. Add
Upper & Lower regions: Enables you to configure the processor attack and • release times for the two areas of action. Lower region: the region that is under the transition level. Upper region: the region that is above the transition level. PHOENIX MOBILE...
Page 100: D1.1. Upper & Lower Regions
Fields to be completed in a new DLP At the end of the process, PHOENIX MOBILE asks for your confirmation before recording the new DLP profile you have created in the internal memory. “Save” corresponds to the center navigator button.
Page 101: D1.2. Graphics Config
Basically, this is not useful. Transition Level: Transition level. This is a key point in DLP operation. The • transition level separates the point where you wish to distinguish a limiter from a compressor and / or expander. Options submenu PHOENIX MOBILE...
Page 102: D1.2.3. Example Of A Configuration
D3. Delete. This option enables you to eliminate the currently selected DLP profile. The system will ask for your confirmation. PHOENIX MOBILE...
Page 103: Annexe E: Connect Phoenix Mobile Into Isdn National-1
ISDN Terminal Adapter device to perform the tasks of establishing and maintaining connections through digital ISDN phone lines. The PHOENIX MOBILE has an ISDN Terminal Adapter for Basic links (BRI), which gives it a communications capacity of two independent 64 Kbps data channels.
Page 104: E1. Directory Numbers (Dn's)
- Two SPID numbers. - Two DNs E4. Connecting the PHOENIX MOBILE to the ISDN line. If the U interface is to be used (more common in the USA), the line will be connected to the RJ- 11 jack (6 pins) of the ISDN module using a 6-pin modular telephone cable (RJ-11 to RJ-11).
Page 105: Annexe F: 3G And Gsm Communications
ANNEXE F: 3G and GSM Communications. This annexe refers to USB communication interface of PHOENIX MOBILE. 3G is commonly used as a general word used to signify data transmission through a mobile link, like the one provided by a 3G modem or a mobile phone. This type of communication could be described, in very simple words, as an IP connection that uses a 3G link to the network.
Page 106: Annexe G: Application Notes Guide
Each application note describes the way to configure each of the audiocodecs. When both ends are different (for instante, at one end there’s a Phoenix Mobile and at the other end a Phoenix Studio), different application notes should be followed in order to configure each one.

AEQ PHOENIX MOBILE User Manual

Quick Links

Related Manuals for AEQ PHOENIX MOBILE

Summary of Contents for AEQ PHOENIX MOBILE

Table of Contents