Centauri IV Manual - Home - MAYAH Communications · 14 Centauri IV Manual Copyright: 2008-2014...

Copyright: 2008-2014 Mayah Communications

Centauri IV Manual

MAYAH, CENTAURI, FLASHCAST are registered Trademarks. All other trademarks are acknowled with this.

CENTAURI IV User Manual as of System Softwareversion 4.9.1.45.Order-No.

Revision 03/2014

Copyright: 2008-2014 Mayah CommunicationsFor copying this manual, even by extract, an explicit written permission of Mayah Communication GmbH is required.

3Contents


List of Contents

0

Part I Introduction 8

................................................................................................................................... 81 Preface

................................................................................................................................... 82 Scope of Delivery

................................................................................................................................... 83 Environment and Operating Conditions

................................................................................................................................... 94 Connectors

................................................................................................................................... 125 Useful Accessories

Part II Useful Hints 14

................................................................................................................................... 141 Default IP settings

................................................................................................................................... 152 How to access the unit via FTP

................................................................................................................................... 163 How to start Web Remote

................................................................................................................................... 164 How to update the firmware

................................................................................................................................... 175 How to activate Keycodes

................................................................................................................................... 186 How to reset the unit

................................................................................................................................... 187 Boot Script

Part III Necessary settings for framedconnections 20

................................................................................................................................... 201 FlashCast technology (ISDN)

................................................................................................................................... 212 ISDN Compatibility List

................................................................................................................................... 223 FlashCast Plus technology (IP)

................................................................................................................................... 234 How to get a framed ISDN connection to ..

......................................................................................................................................................... 23another MAYAH codec

......................................................................................................................................................... 25SendIt 3 (ISDN)

......................................................................................................................................................... 25CDQPrima/CDQ1000/CDQ2000/CDQ2001/Telos Zephyr

......................................................................................................................................................... 27Telos Xstream

......................................................................................................................................................... 28Musictaxi VP Pro

......................................................................................................................................................... 29Musictaxi VP

......................................................................................................................................................... 30AETA Hifiscoop/AETA Scoopy/You Com Set 2

......................................................................................................................................................... 32AVT/PKI telephone

......................................................................................................................................................... 33a Glensound G.722 codec

......................................................................................................................................................... 34AVT Magic

......................................................................................................................................................... 35a MAYCOM Easycorder

......................................................................................................................................................... 36a normal telephone

......................................................................................................................................................... 37an APT-X codec

................................................................................................................................... 405 How to establish IP connections

......................................................................................................................................................... 40Configuration of Network Card(s)

......................................................................................................................................................... 40Unicast RTP

......................................................................................................................................................... 41Multicast RTP

......................................................................................................................................................... 42SDP Streaming

......................................................................................................................................................... 45SAP Streaming

......................................................................................................................................................... 46SIP connections

......................................................................................................................................................... 48MPEG Transport Stream

......................................................................................................................................................... 48IP Ports

Centauri IV Manual4


......................................................................................................................................................... 48IP Overhead

......................................................................................................................................................... 52Optimize IP Connections

......................................................................................................................................................... 53Forward Error Correction (FEC)

......................................................................................................................................................... 54Redundant Streaming

................................................................................................................................... 556 How to establish X.21/V.35 connections

......................................................................................................................................................... 55X.21 versus V.35

......................................................................................................................................................... 55X.21 clocking

......................................................................................................................................................... 56DTE versus DCE

......................................................................................................................................................... 56Mayah codec (DTE) to Mayah codec (DTE)

......................................................................................................................................................... 59MAYAH codec (DTE) to another X.21/V.35 codec

......................................................................................................................................................... 61MAYAH codec (DCE) to MAYAH codec (DTE) via crossover cable

................................................................................................................................... 637 How to establish ASI connections

......................................................................................................................................................... 63ASI Basics

Part IV Elements of Frontpanel Control 66

................................................................................................................................... 661 Preface

................................................................................................................................... 662 LED'S

......................................................................................................................................................... 66 Level LEDs

......................................................................................................................................................... 67Status LEDs

................................................................................................................................... 683 Keyboard

......................................................................................................................................................... 68Hot Keys

......................................................................................................................................................... 69Function Keys

......................................................................................................................................................... 69Arrow Keys

......................................................................................................................................................... 70Numeric Keypad

................................................................................................................................... 714 Window Structure and Key Control

................................................................................................................................... 715 Connect Menu

......................................................................................................................................................... 71Disconnect

......................................................................................................................................................... 71Connect

......................................................................................................................................................... 71Last

......................................................................................................................................................... 72Phonebook

......................................................................................................................................................... 72Session

......................................................................................................................................................... 72Interface

......................................................................................................................................................... 72FEC mode

......................................................................................................................................................... 73Subcodec

................................................................................................................................... 736 Status Menu

......................................................................................................................................................... 73Level Status

......................................................................................................................................................... 74Encoder Status

......................................................................................................................................................... 74Decoder Status

......................................................................................................................................................... 74Lines Status

................................................................................................................................... 747 Presets Menu

......................................................................................................................................................... 74New Session Entry

......................................................................................................................................................... 75Edit Session Entry

......................................................................................................................................................... 75Delete Session Entry

......................................................................................................................................................... 75New Phonebook Entry

......................................................................................................................................................... 76Edit Phonebook Entry

......................................................................................................................................................... 76Delete Phonebook Entry

......................................................................................................................................................... 76New Profile Entry

......................................................................................................................................................... 80Edit Profile Entry

......................................................................................................................................................... 80Delete Profile Entry

......................................................................................................................................................... 80New Settings Entry

......................................................................................................................................................... 80Save Settings Entry

......................................................................................................................................................... 80Rename Settings Entry

......................................................................................................................................................... 80Delete Settings Entry

................................................................................................................................... 818 Setup Menu

5Contents


......................................................................................................................................................... 81Audio Encoder

......................................................................................................................................................... 83Audio Decoder

......................................................................................................................................................... 84Audio Settings

.................................................................................................................................................. 84Audio In/Out

.................................................................................................................................................. 85Mixer

.................................................................................................................................................. 85Analog Levels

.................................................................................................................................................. 86Audio Settings

......................................................................................................................................................... 86Interface

.................................................................................................................................................. 86Communication Interface

.................................................................................................................................................. 87ISDN

.................................................................................................................................................. 89X.21

.................................................................................................................................................. 90Network

.................................................................................................................................................. 93WLAN

.................................................................................................................................................. 94Security

......................................................................................................................................................... 95Frontpanel

.................................................................................................................................................. 95Frontpanel

.................................................................................................................................................. 96Headphone

.................................................................................................................................................. 96Levelmeter

......................................................................................................................................................... 97Miscellaneous

.................................................................................................................................................. 97Subcodec

.................................................................................................................................................. 98Dualmode (ISDN)

.................................................................................................................................................. 98Multipoint

.................................................................................................................................................. 99Gateway

.................................................................................................................................................. 99Backup Mode

.................................................................................................................................................. 100Concealment

.................................................................................................................................................. 100Language

.................................................................................................................................................. 101Identification

.................................................................................................................................................. 101Versions

.................................................................................................................................................. 101Factory Default

.................................................................................................................................................. 102Timeouts

.................................................................................................................................................. 103BGAN

.................................................................................................................................................. 104Ancillary

.................................................................................................................................................. 105Time Settings

.................................................................................................................................................. 107G.711 Options

.................................................................................................................................................. 108Reboot

......................................................................................................................................................... 108Journal

......................................................................................................................................................... 109System Health

Part V Miscellaneous 112

................................................................................................................................... 1121 Other Manuals

................................................................................................................................... 1122 Most frequent ETSI ISDN Error Messages

................................................................................................................................... 1183 Ancillary Data Background

................................................................................................................................... 1214 GPIO Interface

................................................................................................................................... 1235 Backup feature

................................................................................................................................... 1256 Gateway feature

................................................................................................................................... 1277 Technical specifications

Index 129

Part

IIntroduction

8 Centauri IV Manual


1 Introduction

1.1 Preface

The concept of the audio gateways is a new dimension in quality, handling andflexibility at audio transmissions.

The CENTAURI family offers both analogue and digital audio (AES3) at up to96kHz sampling rates, with 24-bit resolution A/D and D/A converters. Codingalgorithms such as G.711, G.722, MPEG-1/2 Layer 2, MPEG-1/2 Layer 3, MPEG-2/4 AAC, AAC (HE), APT-X and Enhanced APT-X are all available, in addition toits’ ability to handle linear audio. All of which, combined with networking via IP/Ethernet, ISDN or X.21/V.35 provide a powerful solution for broadcast industry,recording studios or telecommunications services providers.

The most prominent features of CENTAURI IV:

· Gateway functionality enables the re-routing of audio received at oneconnection to the other, e.g. ISDN to IP.

· Backup functionality enables the fail-over functionality, i.e. if one connectionfails CENTAURI IV automatically switches to another connection, e.g. IP toISDN.

· IP Multicast / Multiple Unicast· Point-to-Multipoint over ISDN to reach up to 8 destinations in "send-only"

mode· Dual Codec functionality to easily split one stereo device into two fully

independent mono codecs· Multi-channel functionality (e.g. 5.1 transmission)· FTP support for configuration export/import operations· Cross-platform Web Remote Control

1.2 Scope of Delivery

The scope of delivery can vary. Please consult the packing list inside of CENTAURI IV package.

1.3 Environment and Operating Conditions

Attention!

Do not subject the device to damp (e.g. proximity to humidifiers etc.),heat (e.g. proximity to radiators, direct sunlight) or mechanical stress(e.g. shaking)! Make sure that the ventilation openings of the device arenot obstructed when the device is in operation, so that the air exchangenecessary for the cooling of the device is not hindered!

The detailed environment and operating conditions are to be found in thechapter Miscellaneous/Technical Specifications.

9Introduction


1.4 Connectors

Connectors on the front panel

Headphones: 1/4" (6.3 mm) stereo phone jack (TRS)

Connectors on the rear panel

a) Power connectorsBy default each CENTAURI IV is equipped with one power supply. Optionally theredundant power supply can be ordered for a hot-swap during operation. Powersupplies utilize IEC 60320-1 C13/C14 connectors.

b) Audio connectors· Analog input, Line In Level, 2 balanced XLR female· Analog output, Line Out Level, 2 balanced XLR male· AES/EBU In/Out/Sync In, DB9 (9 pin Sub-D) female

(see Useful Accessories for Adapter Order No.).· ADAT In/Out



b) Communication interfaces· Basic Ethernet port (100BASE-TX) for control or redundant streaming (LAN) · Additional Ethernet (100BASE-TX) for audio streaming (Ethernet Streaming)

· ISDN, 4x S0 BRIs

11Introduction


c) Optional communication interfaces· X.21/V.35 (1 port) can be pre-installed optionally instead of ISDN or LAN1

Interface

Note:The plugs for the X.21 connection are specific for MAYAH devices. Instead of theusual 15 contacts in two rows (SubD), the socket plugs on the rear of theCENTAURI III 3000/3001 has 26 contacts in three rows (HD). The socket plugscan thus be used either as V.35 or X.21 connection. A corresponding cable withthe necessary pin layout can be obtained from MAYAH.

· ASI Out can be pre-installed optionally instead of ISDN or LAN1 Interface

d) USB portsHere a USB storage device (e.g. USB stick) can be connected. It can be used e.g. as storage for emergency reset or re-configuration using a Boot Script (see Useful Hints/Boot Script).

e) GPIO · TTL I/O

The TTL I/O uses a DB25 female port.· Opto Input Relay Output

The Opto Input Relay Output uses a DB37 female port.



General Purpose Inputs and Outputs (GPIO) support 8x Opto In/ 8x Relay Out aswell as 5 TTL I/Os and can be used e.g. for far-end switching functionality. (seealso the Chapter GPIO Interface)

f) Ancillary Data Interface (RS-232) (Optional)This serial data interface enables transmission of any kind of serial data (e.g.RDS data) along the audio to the remote end. RS-232 can be used with optionalMAYAH RS232 USB Adapter.

g) Remote Control Interface (RS-232) (Optional)This serial data interface enables remote control of the CENTAURI IV from acomputer with a serial port. It may be useful if for any reason there's no IPconnectivity to the codec provided.

Note: For pin layout of the all appropriate interfaces please consult the interfacemanual from the MAYAH web-page at www.mayah.com/support/support-downloads.php

1.5 Useful Accessories

Original MAYAH CENTAURI IV accessories· CENTAURI IV AES/EBU DE9 to 3x XLR adapter (Order no K1040)· Redundant PSU AC or DC· CENTAURI IV RS232 USB Adapter

http://www.mayah.com/support/support-downloads.php


Part

IIUseful Hints



2 Useful Hints

2.1 Default IP settings

a) By default every CENTAURI IV has got the following IP settings:· LAN (positioned above the USB ports; by default only used for remote control)

- DHCP: off- Address: 10.0.0.10- Netmask: 255.255.255.0- Gateway: 255.255.255.255- DNS Server: 255.255.255.255

· LAN1 (positioned on the right of the back pane; by default only used for audiostreaming)- DHCP: off- Address: 10.0.1.10- Netmask: 255.255.255.0- Gateway: 255.255.255.255- DNS Server: 255.255.255.255

· If IP-address 255.255.255.255 is entered, it means that theservice or address is not in use

· If you want to control your CENTAURI IV in your LAN it must belocated in the same subnet as your PC i.e. when the digits of yourbinary net mask are '1' the referring digits of the IP address ofyour CENTAURI IV and your PC must be the same.Example:Net mask: 255.255.255.0 = 11111111 11111111 1111111100000000PC IP address: 192.168.1.56CENTAURI IV with IP address: 192.168.1.57 is located in thesame subnet, but 192.168.100.57 is not.

· If you want to use your CENTAURI IV with just one IP-address forboth streaming and control, as if it had only one Ethernetinterface, just configure both Ethernet cards identically. Bothstreaming and control will be available on the LAN interface.

b) Default IP PacketsizeAt current Firmware Version the default value is set to '1'.

· Usually there's no need to change this value. · Packet size '1' is not the real value but a signalling to the MAYAH

Codec to pick up an optimal packet size which is recommendedfor each type of algorithm by a corresponding RFC (if available).

· For MPEG-based audio compression algorithms the packet size is

15Useful Hints


often calculated to let only full MPEG Frames to fit in each IPpacket.

· For non-MPEG-based algorithms the packet size usuallycalculated to fit 4ms blocks.

c) Default IP ports

Basic default IP ports:· 5004 (Audio transmission, RTP)

- this port number +10 for each following subcodec- subcodec's audio port number +2 for FEC redundant data (rows)- subcodec's audio port number +4 for FEC redundant data (columns)

· 5005 (Network information, RTCP)- this port number +10 for each following subcodec

· 5060 (SIP)

Some other IP ports used by MAYAH devices:· 20 and 21 (FTP Data and control)· 23 (Telnet remote control)· 80 (HTTP for web-remote)· 123 (NTP)· 161 (SNMP control)· 162 (SNMP traps)· 2060 (UDP-based audio level information for remote control software)· 2061 (UDP scan)

Full list of the IP ports can be found in the Communication Reference Manual. Itcan be found in the 'Support/Downloads/Operating Manuals' area at www.mayah.com

2.2 How to access the unit via FTP

Each MAYAH unit provides an integrated FTP and Web server, so you canaccess them as soon as the device is reachable via IP and the IP address isknown.

FTP access should be performed only by an experienced user

Access CENTAURI IV system files

FTP access data for CENTAURI IV are by default: · Host: <IP addres of CENTAURI IV>· Username: Admin· Password: Power





2.3 How to start Web Remote

The Web Remote access data are by default: · Host: <IP address of CENTAURI IV>· Username: WebAdmin· Password: WebPower

Please consult the Web Remote 4 Manual for more details. It can be found on http://www.mayah.com/help

2.4 How to update the firmware

In some cases it can be necessary to update your CENTAURI IV. It can be doneusing a USB stick or using FTP. The update process should not be interrupted,otherwise the unit can be damaged.

The firmware update is provided by MAYAH as a single file with the file nameextension '.upd'. This file must be get ready on your computer before update.

The latest official firmware release can always be found on MAYAH's web site: www.mayah.com/updateThe latest Release Candidate can be found on MAYAH's FTP. Please visit support.mayah.com for more information (you may need to register and log-in).

a) Update via Web RemoteThis is one of the easiest ways to update the firmware of a CENTAURI IV. Starting from the Firmware 4.1.2.0 it is possible to do right in the menu 'SPECIAL/Firmware Update' of the web remote.Please consult the Web Remote 4 manual for details. The Web Remote 4manual can be downloaded in the 'Support/Downloads/Operating Manuals' areaat www.mayah.com

b) Update with a USB stick

· Download an Update file "*.upd"· Rename the file to "device.upd"· Put the file on a USB stick or SD card in the folder \Update\· Turn off your CENTAURI IV· Put the USB Stick in the corresponding slot on the device· Turn on the CENTAURI IV

Don't disconnect the update media from the device if "UpdateExtracting files" appears on an LCD screen or ALARM, CONNECTand FRAMED LEDs are lit up simultaneously!

If the "device.upd" file is not write-protected it will be deleted from thestorage media upon successful update

http://www.mayah.com/help

http://www.mayah.com/update


17Useful Hints


If the file is write-protected it may come to an Update "loop", soplease remove the storage media from device as soon as the LCDscreen shows "Update ... %" or LEDs are have started to blink.

c) Update by using FTP

· With a standard FTP client software access CENTAURI IV using thecredentials given in the chapter 'How to access CENTAURI IV via FTP

· Put the '.upd' File to the root directory of the unit ('/user/'), ensure that the filehas been transferred entirely and restart (switch off and on) the CENTAURIIV.

Note:FTP Upload takes about 4 minutes to upload the '.upd' file to CENTAURI IV. Afterthis a reboot / restart is required.

Update process description / Precautions during update

· Installation. The new firmware is installed automatically. Theprogress is shown by the text messages at the LCD screen and/or blinking of LEDs. After this step is completed successfullyanother reboot will occur automatically.

· First start of the new firmware. At this point some furtherupdate processes might occur without notice. These processesmust not be interrupted. On CENTAURI IV models without LCDscreen please allow at least 1 minute of normal operation (greenLED is on and not blinking) after the update. DO NOT SWITCHTHE CENTAURI IV OFF.

· Update finished. To make sure that all update processes arecompleted on CENTAURI IV without LCD screen, please ensurethat the unit is reachable via network. On units with LCD screen itis enough to wait until the start screen is displayed.

2.5 How to activate Keycodes

Keycodes are used to activate optional algorithms and functions of CENTAURIIV. Keycodes are provided by MAYAH Communications.

Keycodes can be set for each particular device by using Web Remote (menuitem SPECIAL/Keycodes).

Alternatively keycodes can be entered with the direct command 'sys_keycode<keycode>' by using Telnet session, boot script (see below) or any other controltype.



2.6 How to reset the unit

This operation should only be done by expert users. MAYAH is notresponsible for any possible risks or configuration losses in case ofmisuse of this function.

Upon factory reset the entire configuration of the device will be setback to the factory default values. Codec quality profiles, phone bookentries and all presets created by device users will be deleted!

There are three ways to bring the CENTAURI IV back to the factory defaults

a) via Front panel menu SETUP/Miscellaneous/Factory Default

b) via menu SPECIAL/Reset of the Web Remote Control.

c) via Telnet session to the CENTAURI IV typing the direct command 'sys_resetfactory'.

d) it is also possible to include the direct command 'sys_reset factory' in the BootScript file and apply the boot script as described in the next chapter of thismanual.

2.7 Boot Script

This feature should only be used by expert users for emergencysituations e.g. helpful emergency USB stick created by service staffto support non technical colleagues.

This configuration method can be particularly useful for CENTAURI IV modelswithout front panel controls in case that access data have been lost or device hasbecome unreachable via IP. A file named 'mayah-command-scripts.txt' can beused as a boot script if it is located in the root folder of a USB stick. A boot scriptcan contain a set of any direct commands (one command per line). Such directcommands are described in the Communication Reference Manual. Pleasecontact MAYAH for more information on this.

Just insert the USB stick and start device. All the direct commands will beexecuted after booting.

Example mayah-command-scripts.txt

ip_address 192.168.1.57ip_netmask 255.255.255.0

Description: This simple boot script sets the IP address of CENTAURI IV to'192.168.1.57' and the net mask to '255.255.255.0'.

http://www.mayah.com/company/contact.htm

Part

IIINecessary settings for framed connections



3 Necessary settings for framed connections

3.1 FlashCast technology (ISDN)

Remote versus localWhen encoder or decoder dependency is set to remote, CENTAURI IV usesFlashCast technology at ISDN and X.21/V35 connections. FlashCasttechnology means that the CENTAURI IV analyses the data stream for headeror inband information, and uses these information to emulate the other sidecodec.

· Please note that the "encoder / decoder dependency" settingsmentioned further in this manual are mostly relevant whencontrolling the CENTAURI IV on the front panel. When operatedby the Web Remote this parameter is a part of the codec profileand can be found in the drop-down menu "follows".

· At most connections "dependency" or "follows" should not bechanged from the default value ('remote').

When dependency is set to local then CENTAURI IV encode respectivelydecode the audio data according to the codec settings (see Setup/AudioEncoder [Decoder]) regardless if framing is reached or not.However, emulating codecs can mean different behaviour depending on thefact if CENTAURI IV communicate with codecs using either “handshake” ornot.Furthermore not all encoded audio data includes any header or inbandinformation which can be evaluated by FlashCast technology.

MPEG codecs using handshakeWhen a connection is established between codecs using handshake, alwaysthe codec which establishes the connection determines the parameter of theconnection. The most wide spread codecs using handshake are:· all MAYAH codecs (with dependency = remote)· Worldnet Tokyo· SendIt· Musictaxi· OpticodecFor instance:If CENTAURI IV(1) dials to CENTAURI IV(2), then CENTAURI IV(1)determines the quality of the transmission by its configuration.

MPEG codecs without handshakeMPEG codecs without handshake just pump out their audio data after theISDN connection is established regardless if they are called or if they initiatethe call.The most wide spread codecs without handshake:· CDQPrima· CDQ2000/2001

21Necessary settings for framed connections


· CDQ1000· Telos Zephyr· Telos Xstream· RoadrunnerFor Instance:If a CENTAURI IV is connected to a CDQPrima, then always the CDQPrimadetermines the settings of the connection. The CENTAURI IV emulates theCDQPrima and follows its settings.

MPEG codecs using J.52Generally the J.52 standard comprises two main features:· Inverse Multiplexing according to H.221 standard· Capability exchange according to H.221 and H.242 standardAt J.52 transmissions there is a capability exchange between both codecsafter connection is established. This capability exchange guarantees thatalways the maximum quality is used for encoding. This maximum quality isdetermined by the maximum quality which can decoded by the other codec.The most wide spread J.52 codecs are:· all MAYAH codecs· Worldnet Tokyo· AVT Telephone· AVT MagicFor instance:If a CENTAURI IV calls an AVT Magic using MPEG L2, it is possible that itreceives MPEG L3 audio data since this is the maximum quality betweenthese two codecs. If you want to know how to prevent this asymmetric coding,please consult How to get a framed ISDN connection to AVT Magic.

APT-X codecsThe APT-X data stream does not include any header or inband informationwhich can be evaluated by the FlashCast technology. Therefore CENTAURIIV must be configured properly for the APT-X transmission. You get more infoabout at How to get a framed ISDN connection to an APT-X codec.

4SB ADPCM codecsThe 4SB ADPCM data stream does not include any header or inbandinformation which can be evaluated by the FlashCast technology. Therefore CENTAURI IV must be configured properly for the 4SB ADPCM transmission.You get more info about at· How to get a framed ISDN connection to AETA Hifiscoop 3/AETA Scoopy/You

Com Set2· How to get a framed ISDN connection to Musictaxi VP Pro

3.2 ISDN Compatibility List

This is just a short survey of the extensive compatibility features of the CENTAURI IV. No guarantee for compatibility results can be given.



Legend:·: compatibleo: incompatible-: not implemented in foreign codec<space>: not tested yet or no need

Note :CENTAURI IV can support the following AAC algorithms:· AAC (MPEG2) / AAC (MPEG4), AAC (HE), AAC (DRM)Note 2:CENTAURI IV can support the following APT-X algorithms:· Standard APT-X, Standard APT-X no sync, Enhanced APT-X 16, 20 & 24 bit

3.3 FlashCast Plus technology (IP)

FlashCast® refers to an algorithmic process that MAYAH developed forbroadcasting-related applications. At the same time it can be used forinstallations and live events. FlashCast® Plus is a pure IP based procedure andthus contains the following IP elements that are highly relevant for broadcasting:



· Low latency en/decoding (see also "FlashCast algorithm")· Adaptation of buffers and bit rate, leading to high audio quality (see also

"AJC")· Automatic Packet Size Optimization (see also "Packet size")· Error protection (see also "FEC")· Error concealment (future option)

Thanks to FlashCast ® Plus, the full extent of the Audio-over-IP standard (EBUTech 3326) will be available, i.e. as a user you will benefit from the highinteroperability as well as from the high quality and low latency of MAYAHproducts. In addition, the plus variant contains further audio formats that are alsoimplemented in MAYAH codecs.

High level of codec compatibility provided within the FlashCast ® Plus technologyrelies on Session Initiation Protocol (SIP) in conjunction with RTP for the audiodata transport.

Compatibility with other vendors at Audio-over-IP (state: 03/2014)

See also the Chapter 'How to establish IP connections / SIP connections'.

3.4 How to get a framed ISDN connection to ..

3.4.1 another MAYAH codec

Symmetric G.711/G.722/MPEG connectionsSymmetric connections use the same transmission parameters for sending (i.e. encoding) and receiving (i.e. decoding).In this case the encoder and decoder dependency should be set to remoteand the IMUX format should be set to auto (see menu item Setup/AudioEncoder [Decoder]). If encoder and decoder follows remote the callingCENTAURI IV determines the parameters of this Centauri-Centauriconnection. Both CENTAURI’s communicate to each other by telegrams.These parameters are transmitted to the called Centauri after the ‘ISDN



answer delay’ timeout is expired (see menu item 'Setup/Interface/ISDN/Protocol/Answer Time'). This timeout starts when the first B-channel isestablished. Due to prevent that the parameters are sent out before all B-channels are established the ‘ISDN answer delay’ timeout should be set tomin. 3000 ms.Furthermore IMUX format auto means the following at a Centauri-Centauriconnection:· 1 B-channel transmission: No inverse multiplexing is used· 2 B-channel transmission: Musictaxi bonding is used· 3 to 6 B-channel transmission: J.52 inverse multiplexing is used

Asymmetric G.722/MPEG connectionsAsymmetric connections use different parameters for sending (i.e. encoding)and receiving (i.e. decoding).In this case the encoder and decoder dependency should be set to local andthe IMUX format should be set to auto (see menu item Setup/Audio Encoder[Decoder]). Furthermore the encoder settings of the calling Centauri should beused as the decoder settings of the called Centauri and vice versa.

Symmetric 4SB ADPCM connectionsConfiguration for mono 4SB ADPCM connections (see menu item Setup/Audio Encoder [Decoder]):· Encoder dependency: remote· Encoder sample rate: 32 kHz· Encoder bit rate: 128 kbit/s· Encoder mode: mono· Encoder IMUX format: auto· Decoder dependency: remote

Configuration for stereo 4SB ADPCM connections (see menu item Setup/Audio Encoder [Decoder]):· Encoder dependency: remote· Encoder sample rate: 32 kHz· Encoder bit rate: 256 kbit/s· Encoder mode: stereo· Encoder IMUX format: auto· Decoder dependency: remote

Symmetric APT-X connectionsIf one of the APT-X algorithms is used then the following codec configurationis necessary (see remote menu item Setup/Audio Encoder [Decoder]):· Encoder dependency: remote· Encoder bit rate: must be identical at both CENTAURI IV· Encoder mode: must be identical at both CENTAURI IV· Encoder IMUX format: APTX· Decoder dependency: remoteFurthermore the ancillary data format for encoder and decoder must be set tonone, left or right and it must be identical at both CENTAURI IV (see remote



menu item Setup/Ancillary Data).

3.4.2 SendIt 3 (ISDN)

SendIt just supports symmetric ISDN connections with MPEG L2 and MPEGL3 with 64 and 128 kbit/s. However, SendIt use the same telegramcommunication like it is used between two CENTAURI IV if dependency is setto remote. This means that the following CENTAURI IV settings should beused (see menu item Setup/Audio Encoder [Decoder]):· Encoder dependency: remote· Encoder IMUX format: auto· Decoder dependency: remoteFurthermore always the calling side determines the parameters of theconnection. i.e. if SendIt calls the CENTAURI IV then SendIt determines thetransmission parameters and if CENTAURI IV calls SendIt then theCENTAURI IV determines the transmission parameters.

3.4.3 CDQPrima/CDQ1000/CDQ2000/CDQ2001/Telos Zephyr

CENTAURI IV is fully compatible to all algorithms used by CDQPrima,CDQ1000, CDQ2000, CDQ2001 and Telos Zephyr except for algorithm CCSNcombined with sampling rate 24 kHz (with 48 kHz there are no problems).Thanks to FlashCast technology mostly just the following CENTAURI IVparameters must be set to reach a framed connection (see menu item Setup/Audio Encoder [Decoder]):· Encoder dependency: remote· Encoder IMUX format: auto· Decoder dependency: remoteGenerally CDQPrima, CDQ1000, CDQ2000, CDQ2001 and Telos Zephyr arecodecs which just pump out there audio data stream without anyhandshaking. This means that the CENTAURI IV always follows the settingsof these devices regardless of which codec side establishes the connection.

Symmetric G.722 connections (only CDQPrima/CDQ1000/Telos Zephyr)Recommended CENTAURI IV configuration (see remote menu item Setup/Audio Encoder [Decoder]):· Encoder dependency: remote· Encoder IMUX format: auto· Decoder dependency: remote

Generally there are two methods to get byte framing with G.722:· G.722 with H.221 inband signaling (G.722/H.221):

G.722/H.221 uses 1.6 kbit/s of the 64 kbit/s B-channel capacity for sendinginband information. This inband information can be evaluated for framing.

· G.722 with statistical framing (G.722/SRT):G.722/SRT (SRT = statistical recovery timing) evaluates statistically whereevery byte starts. However, this just works with real statistical signals (music,speech etc.) but not with non-statistical signals like sine waves.

CDQPrima and CDQ1000 support G.722/H.221 and G.722/SRT whereas



Telos Zephyr just supports G.722/SRT.The inband information of G.722/H.221 can be evaluated immediately byFlash Cast technology and therefore CENTAURI IV frames very quickly.G.722/SRT does not supply any information which can be detected by FlashCast technology but when the G.722 SRT timeout is expired CENTAURI IVswitches automatically to G.722/SRT. The G.722/SRT timeout starts runningafter an ISDN connection is established and stops if framing is reached. Bydefault the G.722/SRT timeout is set to 30 seconds (see menu item 'Setup/Miscellaneous/Timeouts/Stat.Framing'). This means that usually theCENTAURI IV needs 30 seconds to be framed to a G.722/SRT audio stream G.722/SRT framing can be fasten by the following CENTAURI IV settings (seeremote menu item Setup/Audio Encoder [Decoder]):· Encoder dependency: local· Encoder algorithm: G.722· Encoder sample rate: 16 kHz· Encoder bit rate: 64 kbit/s· Encoder mode: mono· Encoder IMUX format: J.52· Decoder dependency: remote

Symmetric MPEG L2/L3 connections up to 128 kbit/s (no H.221 inversemultiplexing)Recommended CENTAURI IV configuration (see menu item Setup/AudioEncoder [Decoder]):· Encoder dependency: remote· Encoder IMUX format: auto· Decoder dependency: remote

Symmetric MPEGL2 connections to CDQPrima using H.221 inversemultiplexingFor getting a framed connection between a CENTAURI IV and a CDQPrimawhich uses H.221 inverse multiplexing different CENTAURI IV configurationscan be used depending on which codec side establishes the calls.If CENTAURI IV calls a CDQPrima using H.221 inverse multiplexing thefollowing CENTAURI IVconfiguration must be used (see menu item Setup/Audio Encoder [Decoder]):· Encoder dependency: remote· Encoder algorithm: MPEG L2· Encoder bit rate: 384 kbit/s (even if less than 384 kbit/s are used)· Encoder IMUX format: CDQ/H.221· Decoder dependency: remoteIf a CDQPrima using H.221 inverse multiplexing calls a CENTAURI IV thenthe following configuration is also possible (besides the above mentioned):· Encoder dependency: remote· Encoder IMUX format: auto· Decoder dependency: remote

Asymmetric G.722/MPEG connections (not possible with CDQ1000)



Asymmetric connections use different parameters for sending (i.e. encoding)and receiving (i.e. decoding).In this case the CENTAURI IV should use the following configuration (seemenu item Setup/Audio Encoder [Decoder]):· Encoder dependency: local· Encoder algorithm: algorithm of the decoder of the other side codec· Encoder sample rate: sample rate of the decoder of the other side codec· Encoder bit rate: bit rate of the decoder of the other side codec· Encoder mode: mode of the decoder of the other side codec· Encoder IMUX format: auto· Decoder dependency: local· Decoder algorithm: algorithm of the encoder of the other side codec· Decoder sample rate: sample rate of the encoder of the other side codec· Decoder bit rate: bit rate of the encoder of the other side codec· Decoder mode: mode of the encoder of the other side codec

3.4.4 Telos Xstream

CENTAURI IV is compatible with the algorithms G.722, MPEG L2 and MPEGL3 to Telos Xstream. Compatibility with AAC and AAC (LD) is underinvestigation.

Symmetric G.722 connectionsRecommended CENTAURI IV configuration (see menu item Setup/AudioEncoder [Decoder]):· Encoder dependency: remote· Encoder IMUX format: auto· Decoder dependency: remote




Telos Xstream just supports G.722/SRT.G.722/SRT does not supply any information which can be detected by FlashCast technology but when the G.722 SRT timeout is expired CENTAURI IVswitches automatically to G.722/SRT. The G.722/SRT timeout starts runningafter an ISDN connection is established and stops if framing is reached. Bydefault the G.722/SRT timeout is set to 30 seconds (see menu item 'Setup/Miscellaneous/Timeouts/Stat.Framing'). This means that usually theCENTAURI IV needs 30 seconds to be framed to a G.722/SRT audio stream.G.722/SRT framing can be fasten by the following CENTAURI IV settings (seemenu item Setup/Audio Encoder [Decoder]):· Encoder dependency: local· Encoder algorithm: G.722



· Encoder sample rate: 16 kHz· Encoder bit rate: 64 kbit/s· Encoder mode: mono· Encoder IMUX format: J.52· Decoder dependency: remote

Symmetric MPEGL2/L3 connectionsRecommended CENTAURI IV configuration (see menu item Setup/AudioEncoder [Decoder]):· Encoder dependency: remote· Encoder IMUX format: auto· Decoder dependency: remote

Asymmetric G.722/MPEG connectionsAsymmetric connections use different parameters for sending (i.e. encoding)and receiving (i.e. decoding).In this case the CENTAURI IV should use the following configuration (seemenu item Setup/Audio Encoder [Decoder]):· Encoder dependency: local· Encoder algorithm: algorithm of the Xstream decoder· Encoder sample rate: sample rate of the Xstream decoder · Encoder bit rate: bit rate of the Xstream decoder· Encoder mode: mode of the Xstream decoder · Encoder IMUX format: auto· Decoder dependency: local· Decoder algorithm: algorithm of the Xstream encoder· Decoder sample rate: sample rate of the Xstream encoder· Decoder bit rate: bit rate of the Xstream encoder· Decoder mode: mode of the Xstream encoder

3.4.5 Musictaxi VP Pro

Musictaxi VP Pro just allows symmetric connections with the algorithmsG.722, MPEG L2, MPEG L3 and 4SB ADPCM. CENTAURI IV is fullcompatible to Musictaxi VP Pro except for 4SB ADPCM in stereo mode (with4SB ADPCM in mono mode there is no problem). With G.722, MPEG L2 andMPEG L3 connections the CENTAURI IV configuration· Encoder dependency: remote· Encoder IMUX format: auto· Decoder dependency: remoteguarantees framing since Mayah FlashCast technology makes a CENTAURIIV emulating a Musictaxi. At Musictaxi connections always the calling sidedetermines the parameters of the connection. Due to guarantee this it isrecommendable to use a different CENTAURI IV configuration if CENTAURIIV calls the Musictaxi.

CENTAURI IV establishes a G.722/MPEG connection to Musictaxi VP Pro



Recommended CENTAURI IV configuration (see menu item Setup/AudioEncoder [Decoder]):· Encoder dependency: local· Encoder algorithm: algorithm of the connection· Encoder sample rate: sample rate of the connection· Encoder bit rate: bit rate of the connection· Encoder mode: mode of the connection· Encoder IMUX format: musictaxi· Decoder dependency: remote

Musictaxi VP Pro establishes a G.722/MPEG connection to CENTAURI IVRecommended CENTAURI IV configuration (see menu item Setup/AudioEncoder [Decoder]):· Encoder dependency: remote· Encoder IMUX format: auto· Decoder dependency: remote

4SB ADPCM mono connectionWith 4SB ADPCM it makes no difference for the CENTAURI IV configurationif the CENTAURI IVcalls the Musictaxi VP Pro or vice versa.Recommended CENTAURI IV configuration (see menu item Setup/AudioEncoder [Decoder]):· Encoder dependency: remote· Encoder algorithm: 4SB ADPCM· Encoder sample rate: 32 kHz· Encoder bit rate: 128 kbit/s· Encoder mode: mono· Encoder IMUX format: auto· Decoder dependency: remote

3.4.6 Musictaxi VP

Musictaxi VP just allows symmetric connections with the algorithms G.722,MPEG L2 and MPEG L3. CENTAURI IV is fully compatible to Musictaxi VP. Inopposition to connections to Musictaxi VP Pro always the Musictaxi VPdetermines the parameters of the connection regardless of the fact if CENTAURI IV or Musictaxi calls.

CENTAURI IV establishes a G.722 connection to Musictaxi VPRecommended CENTAURI IV configuration (see menu item Setup/AudioEncoder [Decoder]):· Encoder dependency: remote· Encoder algorithm: G.722· Encoder sample rate: 16 kHz· Encoder bit rate: 64 kbit/s· Encoder mode: mono· Encoder IMUX format: musictaxi



· Decoder dependency: remoteMusictaxi VP must be set to ‘G.722 Standby’.

Musictaxi VP establishes a G.722 connection to CENTAURI IVRecommended CENTAURI IV configuration (see menu item Setup/AudioEncoder [Decoder]):· Encoder dependency: remote· Encoder algorithm: G.722· Encoder sample rate: 16 kHz· Encoder bit rate: 64 kbit/s· Encoder mode: mono· Encoder IMUX format: J.52· Decoder dependency: remote

MPEG connectionsWith MPEG connections it makes no difference for the CENTAURI IVconfiguration if the CENTAURI IV calls the Musictaxi VP or vice versa.Recommended CENTAURI IV configuration (see menu item Setup/AudioEncoder [Decoder]):· Encoder dependency: remote· Encoder IMUX format: auto· Decoder dependency: remote

3.4.7 AETA Hifiscoop/AETA Scoopy/You Com Set 2

CENTAURI IV can communicate with AETA Hifiscoop 3/AETA Scoopy/YouCom Set 2 with the algorithms G.722, MPEG L2, MPEG L3 (only Hifiscoop 3)and 4SB ADPCM mono mode. The configuration AETA Hifiscoop 3/AETAScoopy/You Com Set 2 must be identical to get framing.

G.722Generally there are two methods to get byte framing with G.722:· G.722 with H.221 inband signaling (G.722/H.221):



AETA Hifiscoop 3/AETA Scoopy/You Com Set 2 supports G.722/H.221 andG.722/SRT.

CENTAURI IV establishes a G.722 connection to AETA Hifiscoop 3/AETAScoopy/You Com Set 2Recommended CENTAURI IV configuration (see menu item Setup/AudioEncoder [Decoder]):· Encoder dependency: local· Encoder algorithm: G.722· Encoder sample rate: 16 kHz



· Encoder bit rate: 64 kbit/s· Encoder mode: mono· Encoder IMUX format: J.52· Decoder dependency: remote

AETA Hifiscoop 3/AETA Scoopy/You Com Set 2 establishes a G.722connection to CENTAURI IVRecommended CENTAURI IV configuration (see menu item Setup/AudioEncoder [Decoder]):· Encoder dependency: remote· Encoder algorithm: G.722· Encoder sample rate: 16 kHz· Encoder bit rate: 64 kbit/s· Encoder mode: mono· Encoder IMUX format: auto· Decoder dependency: remote

MPEG connectionsWith MPEG connections it makes no difference for the CENTAURI IVconfiguration if the CENTAURI IV calls the AETA Hifiscoop 3/AETA Scoopy/You Com Set 2 or vice versa.Recommended CENTAURI IV configuration (see menu item Setup/AudioEncoder [Decoder]):· Encoder dependency: remote· Encoder algorithm: algorithm of AETA Hifiscoop 3/AETA Scoopy/You Com

Set 2· Encoder sample rate: sample rate of AETA Hifiscoop 3/AETA Scoopy/You

Com Set 2· Encoder bit rate: bit rate of AETA Hifiscoop 3/AETA Scoopy/You Com Set 2· Encoder mode: mode of AETA Hifiscoop 3/AETA Scoopy/You Com Set 2· Encoder IMUX format: auto· Decoder dependency: remote

4SB ADPCM mono connectionWith 4SB ADPCM mono connections it makes no difference for the CENTAURI IV configuration if the CENTAURI IV calls the AETA Hifiscoop 3/AETA Scoopy/You Com Set 2 or vice versa.Recommended CENTAURI IV configuration (see menu item Setup/AudioEncoder [Decoder]):· Encoder dependency: remote· Encoder algorithm: 4SB ADPCM· Encoder sample rate: 32 kHz· Encoder bit rate: 128 kbit/s· Encoder mode: mono· Encoder IMUX format: micda· Decoder dependency: remote



3.4.8 AVT/PKI telephone

The CENTAURI IV is fully compatible to the old and the new AVT telephone.The following connections are possible to the old AVT telephone (also calledPKI telephone):· G.711· G.722The following connections are possible to the new AVT telephone· G.711 (bidirectional)· G.722 (bidirectional)· MPEG L2 (only in direction from CENTAURI IV to AVT telephone)· MPEG L3

Normal telephone connection to AVT telephoneWhen the AVT telephone establishes the call it must be switched to G.711mode.When the CENTAURI IV establishes the G.711 connection it must be told touse telephone instead of data service. This can be done by two ways:1) First possibility:Set CENTAURI IV to G.711 configuration (see menu item Setup/AudioEncoder [Decoder]):· Encoder dependency: remote· Encoder algorithm: G.711· Encoder sample rate: 8 kHz· Encoder bit rate: 64 kbit/s· Encoder mode: mono· Encoder IMUX format: auto· Decoder dependency: remote2) Second possibility:When a ‘-‘ is put in front of an ISDN number automatically a telephone callgets established.

G.722, MPEG L2 and MPEG L3 mono connectionsBoth CENTAURI IV and AVT telephone supports J.52. Therefore a framedconnection can be achieved with the following settings:· Encoder dependency: remote· Encoder algorithm: G.722, MPEG L2 or MPEG L3· Encoder bit rate: 64 kbit/s· Encoder mode: mono· Encoder IMUX format: auto· Decoder dependency: remoteHowever, with this configuration CENTAURI IV always receives MPEG L3audio data because of J.52 capability exchange. Furthermore it must beconsidered that the AVT telephone just can decode MPEG L2 but it cannotencode (i.e. transmit) MPEG L2.Therefore a symmetric G.722 connection between a CENTAURI IV and AVTtelephone can just be achieved with the following settings:· Encoder dependency: remote· Encoder algorithm: G.722



· Encoder sample rate: 16 kHz· Encoder bit rate: 64 kbit/s· Encoder mode: mono· Encoder IMUX format: J.52· Decoder dependency: local· Decoder algorithm: G.722· Decoder sample rate: 16 kHz· Decoder bit rate: 64 kbit/s· Decoder mode: mono

MPEG stereo connectionsRecommended CENTAURI IV configuration (see menu item Setup/AudioEncoder [Decoder]):· Encoder dependency: remote· Encoder algorithm: MPEG L2 or MPEG L3· Encoder bit rate: 128 kbit/s· Encoder mode: joint stereo or stereo· Encoder IMUX format: J.52· Decoder dependency: remoteSince the AVT telephone does not support MPEGL2 for encoding CENTAURIIV just can receive MPEG L3 audio data. The setting IMUX format = J.52guarantees according to the J.52 standard that not both B-channels getsestablished at the same time.

3.4.9 a Glensound G.722 codec




Usually a Glensound G.722 codec just supports G.722/SRT.G.722/SRT does not supply any information which can be detected by FlashCast technology but when the G.722 SRT timeout is expired CENTAURI IVswitches automatically to G.722/SRT. The G.722/SRT timeout starts runningafter an ISDN connection is established and stops if framing is reached. Bydefault the G.722/SRT timeout is set to 30 seconds (see menu item 'Setup/Miscellaneous/Timeouts/Stat.Framing'). This means that usually theCENTAURI IV needs 30 seconds to be framed to a G.722/SRT audio stream.G.722/SRT framing can be fasten by the following CENTAURI IV settings (seemenu item Setup/Audio Encoder [Decoder]):· Encoder dependency: local· Encoder algorithm: G.722· Encoder sample rate: 16 kHz



· Encoder bit rate: 64 kbit/s· Encoder mode: mono· Encoder IMUX format: J.52· Decoder dependency: remote

3.4.10 AVT Magic

CENTAURI IV is fully compatible to AVT Magic with the algorithms G.722,MPEG L2 and MPEG L3. Furthermore CENTAURI IV and AVT Magicsupports J.52.

G.722 connectionRecommended CENTAURI IV configuration (see menu item Setup/AudioEncoder [Decoder]):· Encoder dependency: remote· Encoder algorithm: G.722· Encoder sample rate: 16 kHz· Encoder bit rate: 64 kbit/s· Encoder mode: mono· Encoder IMUX format: auto· Decoder dependency: remote

MPEG L2/L3 connections with 64 kbit/sAVT Magic always returns G.722 when the calling CENTAURI IV uses thefollowing configuration:· Encoder dependency: remote· Encoder bit rate: 64 kbit/s· Encoder IMUX format: auto· Decoder dependency: remoteWith this configuration the CENTAURI IV tells the AVT Magic by J.52capability exchange that its decoder supports G.722. In this case the AVTMagic always returns G.722 at 64 kbit/s connections to be compatible to otherG.722 codecs. Therefore the following CENTAURI IV configuration isnecessary to get a symmetric MPEGL2/L3 connection between a CENTAURIIV and AVT Magic.· Encoder dependency: remote· Encoder algorithm: MPEG L2/L3· Encoder bit rate: 64 kbit/s· Encoder IMUX format: J.52· Decoder dependency: local· Decoder algorithm: same as encoder algorithm· Decoder bit rate: 64 kbit/s· Decoder sample rate: same as encoder sample rateWith this configuration the CENTAURI IV pretend just to support the decodersettings (J.52 capability exchange) i.e. it forces the AVT Magic to send outaudio data corresponding to the CENTAURI IV decoder configuration.

MPEG L2/L3 connections with more than 64 kbit/s



With the following CENTAURI IV configuration a framed connection with theAVT Magic can be achieved:· Encoder dependency: remote· Encoder algorithm: MPEG L2/L3· Encoder IMUX format: auto· Decoder dependency: remoteHowever, with this configuration CENTAURI IV always receives MPEG L3audio data because of J.52 capability exchange. If MPEG L2 should bereceived by the CENTAURI IV it must pretend just to support MPEG L2.Therefore the following CENTAURI IV configuration is necessary for asymmetric MPEG L2 connection:· Encoder dependency: remote· Encoder algorithm: MPEG L2· Encoder sample rate: requested sample rate· Encoder bit rate: requested bit rate· Encoder IMUX format: J.52· Decoder dependency: local· Decoder algorithm: MPEG L2· Decoder sample rate: same as encoder sample rate· Decoder bit rate: same as encoder bit rate

Note:The J.52 capability exchange does not include the operational mode.Therefore the CENTAURI IV always follows the mode of the AVT Magic.Since with 64 kbit/s connections operational mode is mono it is stronglyrecommended that in this case the AVT Magic should be set to mono.

3.4.11 a MAYCOM Easycorder

The CENTAURI IV is compatible to the MAYCOM EASYCORDER with MPEGL2 provided Centauri software x.2.0.5 or later is used (x = 2 for CENTAURI Iand x > 2 for Centauri III, GANYMED 1102 and MERKII). MAYCOM Easycorder (software version 6.4B) only supports the bit rate of 64kbps.

Recommended CENTAURI IV configuration (see menu item Setup/AudioEncoder [Decoder]):· Encoder dependency: local· Encoder algorithm: MPEG L2· Encoder sample rate: 24 or 48 kHz (depends on the sample rate of the

EASYCORDER)· Encoder bit rate: 64 kbit/s· Encoder mode: mono· Encoder IMUX format: auto· Decoder dependency: local· Decoder algorithm: MPEG L2· Decoder sample rate: 24 or 48 kHz (depends on the sample rate of the

EASYCORDER)



· Decoder bit rate: 64 kbit/s· Decoder mode: mono

3.4.12 a normal telephone

Since CENTAURI IV has implemented the G.711 algorithm it can be used asa telephone hybrid i.e. it can call telephones and it can be called bytelephones.

A-law and µ-lawWorldwide two standards for digital telephony exists:· A-law: Non-linear PCM coding with 13 segments; used in Europe· µ-law: Non-linear PCM coding with 15 segments, used in North America and

JapanCENTAURI IV supports both standards but it must be set via menu item 'Setup/Miscellaneous/G.711 Options').

CENTAURI IV establishes a telephone connection to a telephoneFor telephone connections the ISDN service speech or telephony is usedwhereas for G.722, MPEG, APT and 4SB ADPCM connections the ISDNservice unrestricted digital info is necessary. Therefore the CENTAURI IVmust be told to establish telephone connections. This can be done by twoways:1) First possibility:Set CENTAURI IV to G.711 configuration (see menu item Setup/AudioEncoder [Decoder]):· Encoder dependency: remote· Encoder algorithm: G.711· Encoder sample rate: 16 kHz· Encoder bit rate: 64 kbit/s· Encoder mode: mono· Encoder IMUX format: auto· Decoder dependency: remote2) Second possibility:When a ‘-‘ is put in front of an ISDN number automatically a telephone callgets established.

A telephone calls a CENTAURI IVRecommended CENTAURI IV configuration (see menu item Setup/AudioEncoder [Decoder]):· Encoder dependency: remote· Encoder IMUX format: auto· Decoder dependency: remote



3.4.13 an APT-X codec

If the software options for APT-X algorithms are enabled then CENTAURI IVis fully compatible to nearly all APT codecs.

APT codecs and their options:

Legend:·: implementedo: not implementedDisclaimer:Mayah Communications disclaims any liability for the correctness of the APTcodec options table shown below.

Since APT algorithms do not have any header or inband information whichcan be evaluated by Mayah Flash Cast technology, it is mandatory that the CENTAURI IV follows the configuration of the other side APT codec.Generally the following CENTAURI IV configuration is recommended (seemenu item Setup/Audio Encoder [Decoder]):· Encoder dependency: remote· Encoder algorithm: APT-X algorithms used by the other side APT codec· Encoder sample rate: sample rate used by the other side APT codec· Encoder bit rate: bit rate used by the other side APT codec· Encoder mode: mode used by the other side APT codec· Encoder IMUX format: APT· Decoder dependency: remote

Special cases:a) MAYAH codec-MAYAH codec respectively MAYAH codec-WorldNetTokyo APT-X connectionIf on both sides codecs system software version 2.1.0.47 (or later) isimplemented then it is no more necessary to configure the called codec to theright APT-X settings. Using the codec settings (see menu item Setup/AudioEncoder [Decoder]) · Encoder dependency: remote· Encoder IMUX format: auto· Decoder dependency: remotethe calling CENTAURI IV will tell the other CENTAURI, MERKII or Tokyo theright APT-X parameters.b) Glensound GSGC6Configuration to get a framed connection to a Glensound GSGC6 using APT-



X:· Encoder dependency: local· Encoder algorithm: APT-X no sync. (i.e. Standard APT-X no sync.)· Encoder sample rate: 16 kHz· Encoder bit rate: 64 kbit/s· Encoder mode: mono· Encoder IMUX format: auto· Decoder dependency: local· Decoder algorithm: APT-X no sync. (i.e. Standard APT-X no sync.)· Decoder sample rate: 16 kHz· Decoder bit rate: 64 kbit/s· Decoder mode: monoc) Nica 64Configuration to get a framed connection to a Nica 64:· Encoder dependency: local· Encoder algorithm: APT-X (i.e. Standard APT-X with sync.)· Encoder sample rate: 16 kHz· Encoder bit rate: 64 kbit/s· Encoder mode: mono· Encoder IMUX format: auto· Decoder dependency: local· Decoder algorithm: APT-X (i.e. Standard APT-X with sync.)· Decoder sample rate: 16 kHz· Decoder bit rate: 64 kbit/s· Decoder mode: monod) Nica 128Configuration to get a framed connection to a Nica 128:· Encoder dependency: local· Encoder algorithm: APT-X no sync. (i.e. Standard APT-X no sync.)· Encoder sample rate: 32 kHz· Encoder bit rate: 256 kbit/s· Encoder mode: dual mono· Encoder IMUX format: APT· Decoder dependency: local· Decoder algorithm: APT-X no sync. (i.e. Standard APT-X no sync.)· Decoder sample rate: 32 kHz· Decoder bit rate: 256 kbit/s· Decoder mode: dual mono

Note to sample rate at APT-X algorithms:When APT-X algorithms are used then the sample rate is determined by the bitrate and the mode. The sample rate is calculated with the following formulas:ch:number of audio channels;1 for mono, 2 for stereobr: bit ratesr: sample rate· Standard APT-X no auto sync.:

sr = br / (ch * 4)



· Standard APT-X auto sync.:sr = br / (ch * 4)

· Enhanced APT-X 16 bit:sr = br / (ch * 4)





3.5 How to establish IP connections

3.5.1 Configuration of Network Card(s)

The general configuration of the electrical and optical network card of the CENTAURI IV can be done via menu item Setup/Interface/Network.

3.5.2 Unicast RTP

RTP is the recommended IP-transmission method between modern Audio-over-IP Codecs.

· RTP (=Realtime Transport Protocol) protocol bases on UDP (= UserDatagram Protocol). Therefore the RTP implementation of CENTAURI IV isan enhancement of the UDP implementation. In opposite to the pure UDPimplementation RTP allows packet reordering at the receiver side to eliminatethe .

· RTP supports the following features:- payload-type identification- sequence numbering- time stamping- source identification

· RTP is implemented according to rfc 3550 (www.ietf.org/rfc/rfc3550.txt).

a) Unidirectional RTP connectionsUnidirectional IP connections between two MAYAH Codecs can establishedby the following steps:Codec SettingsConfigure the codec settings via menu item Setup/Audio Encoder [Decoder](valid for both MAYAH Codecs):· Interface: IP· Encoder dependency: Remote· Decoder dependency: RemoteThe establishing MAYAH Codec determines the algorithm, the sample rate,the bit rate and the mode of the transmission.Establish ConnectionChoose 'Connect/Connect' menu or push the Express Dial Button to open theConnect-dialog:· Select interface to IP· Select RTP· Type in the IP-address of the other codec in the address field· Click the OK-button to establish connection

b) Bidirectional RTP connectionsThere are two ways to establish a bidirectional RTP connection:· Establish a unidirectional RTP connection on both MAYAH Codec· Use a special codec configuration on the establishing MAYAH CodecSpecial configuration on establishing MAYAH codec

http://www.ietf.org/rfc/rfc3550.txt



Configure the codec settings via menu item Setup/Audio Encoder [Decoder]:· Encoder dependency: remote· Decoder dependency: localSpecial configuration on non-establishing MAYAH codecConfigure the codec settings via menu item Setup/Audio Encoder [Decoder]:· Encoder dependency: remote· Decoder dependency: remoteNote:At such bidirectional RTP connections different settings for sending andreceiving can be used. The encoder settings determine which quality is sentwhereas the decoder settings determine which quality is received.

Please note that bidirectional RTP connections can only beterminated on the callee side. To be able to terminate a bidirectionalIP Audio connection on either side consider to use SIP Protocol. Seealso 'SIP connections'

c) Meaning of LED’s at RTP connections· Lit up Connect LED:

RTP sending CENTAURI IV· Lit up Framed LED:

RTP receiving CENTAURI IV

3.5.3 Multicast RTP

The basics of Multicast are described in Application Note No. 9 on Mayahwebsite.

Multicast RTP connections can be established between: · any MAYAH audio codecs

CENTAURI IV can be used as Multicast Sender and Multicast Receiver.· CENTAURI IV and other decoders (e.g. VLC, Quicktime Player, set-top-

boxes etc):CENTAURI IV is used as Multicast Sender.

How to establish Multicast RTP connection

a) Codec Settings of Multicast senderOn CENTAURI IV configure the codec settings via menu item Setup/AudioEncoder [Decoder]:· Encoder dependency: Remote· Decoder dependency: RemoteThe audio quality of the multicast stream is determined by the encodersettings of algorithm, sample rate, bit rate and mode of the Multicast sender.

b) Codec Settings of Multicast receiverOn CENTAURI IV configure the codec settings via menu item Setup/Audio

http://www.mayah.com/content/download/pdfs/appnotes/centauri/a_n_e_009.pdf



Encoder [Decoder]:· Encoder dependency: Remote· Decoder dependency: Remote

c) Establish Connection (Multicast sender)Choose 'Connect/Connect' menu or push the Express Dial Button to open theConnect-dialog:· Select interface to IP· Select protocol to RTP· Select Codec to Encoder· Type in the Multicast IP-address (e.g. 225.0.0.2)

Note: A special port can be selected by the optional suffix ‘:<port number>’ (e.g. 225.0.0.2:5004)

· Step to 'connect' to establish connection

d) Establish Connection (Multicast receiver)Choose 'Connect/Connect' menu or push the Express Dial Button to open theConnect-dialog:· Select interface to IP· Select protocol to RTP· Select Codec to Decoder· Type in the Multicast IP-address (e.g. 225.0.0.2)

Note: A special port can be selected by the optional suffix ‘:<port number>’ (e.g. 225.0.0.2:5004)

· Step to 'connect' to establish connection

3.5.4 SDP Streaming

SDP streaming Is a good way to stream to software players.

GeneralSDP stands for session description protocol. Such a SDP file includesinformation such as- type of media (audio, video etc.)- transport protocol (e.g. RTP)- coding format (algorithm, bit rate)- source IP address- destination IP address- used portThe player can download the SDP file from the CENTAURI IV and parse theSDP file to get connection info.More info about SDP can be found in rfc 2327 (www.ietf.org/rfc/rfc2327.txt).

Software players supporting SDP and tested with CENTAURI IV- VLC media player (version 0.8.2)- Quicktime (version 7.0.3)




a) Configuration steps on CENTAURI IV sideCodec settings· Interface: Net· Encoder dependency: Remote· Encoder algorithm: Algorithm supported by the other side codec

Note:Along with other MPEG Formats SDP streaming allows the CENTAURI IV tostream with AAC (MPEG4) and AAC (HE)Note 2:

· Decoder dependency: RemoteEstablish Connection via front panel controlsChoose 'Connect/Connect' menu or push the Express Dial Button to open theConnect-dialog:· Select interface to Net· Select HTTP· Type in the IP-address

Note:A specific port can be selected by the optional suffix ‘:<port number>’(e.g. 225.0.0.2:5004)Note 2:SDP connections can be unicast and multicast connections.

· Click the OK-button to establish connectionNote:The name of the SDP file depends on the selected sub codec:- sub codec 1: stream1.sdp- sub codec 2: stream2.sdp- sub codec 3: stream3.sdpetc.

b) Configuration steps on software player sideHow to establish such an SDP connection depends on the software player.Therefore please consult the referring manual. Just to give you examples here the steps to execute at VLC media player(version 0.8.2) and at Quicktime (version 7.0.3).VLC media player:· Step to menu item <File/Open Network Stream ..>· Select tab ‘Network’· Select radio button ‘HTTP/HTTPS/FTP/MMS’· Type in at URL edit field: <IP-address of CENTAURI IV>/<name of SDP

file>e.g.: 192.168.1.78/stream1.sdp

· Click the OK-button to establish connection



Quicktime:· Step to menu item <File/Open URL ..>· Select tab ‘Network’· Type in at ‘Enter an Internet URL to open’: http://<IP-address of CENTAURI

IV>/<name of SDP file> e.g.: http://192.168.1.78/stream1.sdp

· Click the OK-button to establish connection



3.5.5 SAP Streaming

SAP streaming is more or less an enhancement of SDP streaming (see SDPstreaming).

GeneralSAP stands for session announcement protocol. Same as SDP streaming(see SDP streaming) a SDP file is created but additionally the SDP informationis sent to the Multicast address 224.2.127.254. The SAP decoder retrieves theSDP information from this Multicast address (and not from the SDP Encoder).SAP announcements are sent on port 9875.There are two advantages of SAP streaming compared to SDP streaming:· Since the SDP file must not be retrieved from the encoder device,



unidirectional connections are sufficient (e.g. important for satellitetransmissions).

· At Multicast address 224.2.127.254 the SDP information of all SAP streamingencoders is available (and not just the SDP information of one device).

More info about SAP can be found in rfc 2974 (www.ietf.org/rfc/rfc2974.txt).

Configuration steps at CENTAURI IV encoderCodec settingsConfigure the codec settings via menu item Setup/Audio Encoder [Decoder]:· Interface: Net· Encoder dependency: Remote· Encoder algorithm: Algorithm supported by the other side codec

Note:Along with other MPEG Formats SDP streaming allows the CENTAURI IVto stream with AAC (MPEG4) and AAC (HE)

· Decoder dependency: RemoteEstablish ConnectionChoose 'Connect/Connect' menu or push the Express Dial Button to open theConnect-dialog:· Select interface to Net (IP)· Select protocol to SAP· Type in the IP-address (usually a multicast address, e.g. 225.0.0.2)· Step to 'connect' to establish connection

3.5.6 SIP connections

a) GeneralThe Session Initiation Protocol (SIP) has been developed by the IETF (= Internet Engineering Task Force) and is described in rfc 3261 (www.ietf.org/rfc/rfc3261.txt). This protocol can be used to establish, modify and terminatemultimedia sessions and is currently used in most Voice over IP (VoIP) andInternet telephony applications.

As a client-server protocol, SIP is similar to HTTP and SMTP (e-mail). Itsrequests and responses are text strings containing information about thesession that is to be established. SIP addresses are composed using a syntaxsimilar to e-mail addresses e.g. sip:[email protected].

The complete separation of signalling and transport layer (i.e. of connectiondata and media data), as implemented in SIP allows the user to establish aconnection in a unified way without prior knowledge of the exact location ofother participants and not depending on the nature of the transferred data.The SIP protocol can furthermore be used to let two devices auto-negotiatethe parameters (e.g. algorithm, sample rate,...) of the multimedia session.

The constantly growing acceptance of SIP - due to recent developments infields like Internet telephony and UMTS - guarantees for a steady growth and






expansion of infrastructure. Since SIP supports the negotiation of bandwidthreservation and reservation is needed for good quality Internet telephony,network providers will need to deploy mechanisms for bandwidth reservationin their networks – a critical need for all professional Audio-Over-IPapplications.

In addition SIP is also part of the “Next Generation Network (NGN)” as definedby the European Telecommunications Standards Institute (ETSI) and isthought to be a replacement for ISDN. Since ISDN will eventually disappear inmost countries the designated successor has been appointed: SIP.

Some specific advantages of SIP over pure RTP as a basis for professionalAudio-over-IP connections are:

· compatibility to standards-based IP codecs of other manufacturers· signalling of remote party's availability ('busy' or 'request timeout' for

unreachable destinations)· possibility to terminate connections on both sides

b) Configuration steps on CENTAURI IV side for a typical SIP connection

Codec settingsConfigure the codec settings via menu item Setup/Audio Encoder [Decoder]:· Interface: Net· Encoder dependency: Remote· Encoder algorithm: desired codec algorithm· Decoder dependency: RemoteEstablish ConnectionChoose 'Connect/Connect' menu or push the Express Dial Button to open theConnect-dialog:· Select protocol to 'SIP'· Select codec to 'both'· Type in the SIP address or IP-address · Select 'connect' to establish connection

· For more information on SIP basics please check MAYAH Audio-via-IP Compendium in the 'Support/Downloads/White Papers'area at www.mayah.com

· For test purposes MAYAH also provides a SIP + STUN server.Please read an Application Note #36 in the ''Support/Downloads/Application Notes' area at www.mayah.com for detailedinstructions

· Additional information on EBU Audio Contribution over IP (ACIP)standard can be obtained from the EBU web-site: http://tech.ebu.ch/groups/nacip



http://tech.ebu.ch/groups/nacip

http://tech.ebu.ch/groups/nacip



3.5.7 MPEG Transport Stream

Configuration steps on CENTAURI IV side

The easiest way to configure and establish MPEG TS is to use the Web Remote. Pleaseconsult the Web Remote 4 Manual in the 'Support/Downloads/Operating Manuals' area at www.mayah.com for further details.

More details on MPEG TS implementation in MAYAH Codecs can be found in an Application Note #34 in the 'Support/Downloads/Application Notes' area at www.mayah.com

3.5.8 IP Ports

a) RTP audio portsBy default the RTP audio ports are:· 5004 (RTP) and 5005 (RTCP)

Default ports for each following subcodec is calculated as +10.I.e. default RTP audio ports for Subcodec 2 are:· 5014 (RTP) and 5015 (RTCP)

etc.

RTP audio ports can be changed at establishing the connection by enhancingthe IP-address with the delimiter ‘:’ and the requested RTP port.For instance: 225.0.0.11:5670This establishes a connection to Multicast address 225.0.0.11 using the port5670.

b) TCP and UDP audio portsThe first UDP or TCP audio port is 2001 by default and it can be set by the directcommand ‘ip_audioport’.All the default IP ports of CENTAURI IV are listed in the appendix of theCommunication Reference Manual in the 'Support/Download/Operating Manuals'area of MAYAH web-site.

c) SAP portSAP announcements are sent on port 9875. You can get more info about SAPat SAP streaming.

For some more ports see also the Chapter 'Default IP Settings'

3.5.9 IP Overhead

a) GeneralAt IP-transmissions the data stream consists of· Payload (pure audio data e.g. one or more MPEG frame)· IP Overhead




http://www.mayah.com/content/download/pdfs/manuals/communication-reference_man.pdf



b) IP Overhead in BytesThe IP overhead in Byte is at :

UDP46 Byte consisting of:· IEEE802.3: 18 Byte· IP: 20 Byte· UDP: 8 Byte

RTP58 Byte consisting of:· IEEE802.3: 18 Byte· IP: 20 Byte· UDP: 8 Byte· RTP: 12 ByteNote:The RTP header is 12 Byte and not 16 Byte long since no contribution sourceidentifiers are used.

MPEG TS over UDP50 Byte consisting of:· IEEE802.3: 18 Byte· IP: 20 Byte· UDP: 8 Byte· MPEG TS Header: 4 Byte

MPEG TS over RTP62 Byte consisting of:· IEEE802.3: 18 Byte· IP: 20 Byte· UDP: 8 Byte· RTP: 12 Byte· MPEG TS Header: 4 Byte

c) IP Overhead percentage calculation

UDP If the packet size mode is set variable then the payload is also rounded to thenext full audio frame (MPEG) or audio block.

Here some examples for IP overhead calculation at UDP connections with



variable packet size:

The following diagram shows the percentaged IP overhead at - Algorithm: MPEG L3- Sample rate: 48 kHz- UDP- packet size = 180 Byte (default value)- packet size mode: var (default value)



RTPSimilar to UDP calculation but it must be considered that the size of allheaders is 58 Byte instead of 46 Byte.Example:Algorithm: MPEG L2Sample rate: 48 kHzBit rate: 256 kbit/sFrame length = 256/48 * 144 Byte = 768 ByteIP Overhead = ((768 Byte + 58 Byte)/768 Byte –1) * 100 % = approx. 7.6%

MPEG TSEach MPEG TS packet is 188 Byte long and consist of· payload: 184 Byte· MPEG TS Header: 4 Byte

Theoretical optimum overhead at MPEG TS over UDP transmissionThe optimum (i.e minimum) overhead is reached if· every MPEG frame just needs one packet (and therefore the overhead just

must be sent once for every frame)· frame length = 184 ByteThen the IP overhead is calculated to:IP Overhead = ((184 Byte + 50 Byte)/184 Byte -1 ) * 100 % = approx. 27.2 %Real overheadSince the real MPEG frame length is usually different to 184 Byte and CENTAURI IV cannot transport part of two frames in a MPEG TS frame, thereal overhead is usually much bigger then the theoretically optimum one.

Example 1 ("bad" overhead):Algorithm: MPEG L3Sample rate: 48 kHzBit rate: 128 kbit/sFrame length: 128/48 * 144 Byte = 384 Byte



Frame length of 384 Byte means that 3 MPEG TS packets are necessary totransport one frame. This means:IP Overhead = ((3*(MPEG TS packet + All other overheads))/384 Byte) – 1) *100 % = ((3*(188 Bytes + 46 Byte)/384 Byte –1) + 100% = approx.82.8%Example 2 ("good" overhead): Algorithm: MPEG L3Sample rate: 44.1 kHzBit rate: 56 kbit/sFrame length: 56/44.1 * 144 Byte = 183 ByteFrame length of 183 Byte means that just one MPEG TS packets is necessaryto transport one frame. This means:IP Overhead = (((MPEG TS packet + All other overheads))/183 Byte) – 1) *100 % = (((188 Bytes + 46 Byte)/183 Byte –1) + 100% = approx. 27.9 %

3.5.10 Optimize IP Connections

Problems at IP-audio-connections between IP audio codecs can be solved bythe following actions:· Setting up the AJC (Automatic Jitter Compensation)· Manually increasing the IP audio delay on the decoder side· Manually adapt packet size · Adapt transfer rate and duplex mode· Use Type of service or other Quality of Service methods

a) Increasing the IP audio delay on the decoder sideThe IP audio delay can be set from 0 ms (default) up to 5000 ms at menuitem Setup/Interface/Network. Increasing the audio delay means that first allreceived audio data is buffered before it is decoded. Such buffering helps toprevent audio interruptions and distortions caused by a network jitter. Thebigger the receive buffer the more reliable the audio IP transmissions is. Onthe other hand the audio delay increases.

b) Adapt transfer rate and duplex modeSometimes interruptions or distortions of IP audio transmissions are causedby improper auto sensing of the network equipment (switch, hub , router etc.).In this case the transfer rate and the duplex mode should be changed ‘auto’ tothe settings of the network. This can be at menu item Setup/Interface/Network. Example:With some network switches it is useful to change· transfer rate from ‘auto’ to ‘100 Mbit/s’· duplex mode from ‘auto’ to ‘half’ or 'full'

c) Adjust Quality of ServiceCENTAURI IV supports several Quality of Service (QoS) methods, includingType of Service (ToS), Differentiated Service (Diff.Serv.) and VLAN tagging.



Basic info and how to set the ToS is described in an Application Note #20 inthe 'Support/Downloads/Application Notes' area at www.mayah.com.

d) Adapt IP packet sizeSometimes interruptions and distortions of IP transmissions are caused by thefact that the upload and/or download capacity is too small. Therefore it shouldbe considered the required bandwidth for data transmission can besignificantly higher than the actual algorithm bit rate due to the IP overhead.More details about IP overhead can be found in chapter IP Overhead.Usually the bigger packet size is the smaller the IP overhead is. However,there is one restriction:If the payload (audio data) plus the IP overhead is bigger than max. possiblepacket size value allowed by the CENTAURI IV network card (i.e. 1,514 Byteat electrical CENTAURI IV Ethernet card), then the rest of the payload iswritten to next packet. This can cause very big IP overheads.

e) IP packet size modeThe IP packet size mode can be set at menu item Setup/Interface/Network to:

· variable (default)This means that the payload is rounded to the next full frame or audio blockAdvantage:No fractional audio frames or blocks in the IP packetsDisadvantage:With algorithms with no fixed frame length (e.g. AAC) it can happen that themax. possible packet size is exceeded.

· fixedThis means that IP payload is exactly the same as the packetsize value setin menu item Setup/Interface/Network (i.e. it is not rounded to the next fullaudio frame or audio block).Advantage:Even with algorithms with variable frame length the packet size is fixed.Disadvantage:IP packet can have fractional audio frames or audio blocks.

· sync.Same as fixed but additionally packets are transmitted in synchronizedintervals.Advantage:Same as with fixed but additionally adaption to network equipment whichhas got problems with unsynchronized packets.Disadvantage:Same as with fix.

3.5.11 Forward Error Correction (FEC)

a) GeneralIn real life IP transmissions IP packets can be lost since· routers discard them since they are damaged· routers discard them since other traffic has got higher priority· different routing




FEC provides the possibility of error correction by adding redundant data.Thereby smooth decoding of audio data can be provided at the cost of higherbandwidth requirements and increased delay.

For more background information on FEC please consult the Application Note No. 31 in the 'Support/Downloads/Application Notes'area at www.mayah.com

b) Configuration steps on CENTAURI IV side

CENTAURI IV uses five presets with the optimal FEC matrix sizes for differentapplications: · 'lowest delay'· 'low delay'· 'middle delay'· 'low bitrate'· 'high security'

These presets can be activated either using Front Panel controls in the menu 'Connect/FEC mode' or by using Web Remote. Please consult the WebRemote 4 Manual for further Details. It can be found on http://www.mayah.com/help

· The IP ports for FEC redundant data are equivalent to the used IPaudio port plus 2 for the row data and plus 4 for the column data(only used with 'high security' preset).E.g. for default IP audio atthe port 5004 the FEC with 'high security' preset will betransmitted at the port 5006 and 5008

· FEC is only applied to the encoder. IP audio decoder in the up-to-date MAYAH devices is always 'listening' to the data on the FECports

· Third party devices which do not support FEC would not beaffected and still could decode the original IP audio streamwithout being able to benefit from FEC redundant data

3.5.12 Redundant Streaming

This is a special feature of the MAYAH Codecs with two separate Ethernetinterfaces.

Data transmissions via an IP network could suffer from packet loss and or packetcorruption. To reduce the risk of packet loss and to increase the reliability of aconnection CENTAURI IV is capable of doubling the IP stream to send it via asecondary network interface to physically separated networks. With thisredundancy the total error rate can be reduced significantly. In contrary with theFEC techniques, the unique Redundant Streaming technology by MAYAH allows

http://www.mayah.com/content/download/pdfs/appnotes/general/a_n_e_031.pdf






error reduction in both involved networks by factor 10x while introducing noadditional processing delay at all.

Please note that the primary stream is sent via the Ethernet interface which isnormally used for audio transmission (labeled LAN1). Redundancy stream will besent via the Ethernet interface which is also used for control tasks (labeled LAN). See also Chapter 'Introduction/Connectors' .

Attention should be paid to the correct network configuration, including address,netmask, gateway (if necessary) for both interfaces.

Currently Redundant Streaming on CENTAURI IV can only be configured byusing the Web Remote. Please consult the Web Remote 4 Manual for moredetails. It can be found on http://www.mayah.com/help

· Redundant Streaming feature only works with RTP protocol· The IP port for the redundancy connection is equivalent to the

primary RTP audio port plus 1000. E.g. default RTP port for audiostreaming is 5004, hence the redundancy connections will bedone via the port 6004.

For more details on Redundancy Streaming implemented by MAYAH you mayalso check an Application Note No. 28 in the Support/Downloads section atwww.mayah.com

3.6 How to establish X.21/V.35 connections

3.6.1 X.21 versus V.35

The CENTAURI IV X.21/V.35 protocol can be set via menu item Setup/Interface/X.21.X.21 and V.35 are both synchronous transmission standards. However, X.21uses balanced signal and handshake lines whereas V.35 has got balancedsignal lines but unbalanced handshake lines. Therefore the range of V.35cables is undefined whereas X.21 allows cable length up to 1 km.Furthermore the voltage levels of X.21 and V.35 are different.The pin layout of CENTAURI IV X.21 and V.35 (plus pin layouts ofmiscellaneous cables) is described in the CENTAURI interface manual atchapter 1.5. This interface manual can be found at www.mayah.com/content/download/pdfs/manuals/centauri-interface_eng.pdf.

3.6.2 X.21 clocking

CENTAURI IV X.21/V.35 clocking can be set via menu item Setup/Interface/X.21.CENTAURI IV X.21/V.35 interface supports three clock interfaces. If theseclocking interfaces are used for input or output clocking depends on theselected mode.


http://www.mayah.com/content/download/pdfs/appnotes/general/a_n_e_028.pdf

http://www.mayah.com

http://www.mayah.com/content/download/pdfs/manuals/centauri-interface_eng.pdf




The default clocking for DTE mode is T4T1T4 whereas for DCE mode T2T4.The meaning of the different clockings are described in the CENTAURIinterface manual at chapter 1.5.2. This interface manual can be found at www.mayah.com/content/download/pdfs/manuals/centauri-interface_eng.pdf.

3.6.3 DTE versus DCE

CENTAURI IV supports for X.21/V.35 DTE and DCE mode. This mode can beset via menu item Setup/Interface/X.21.DTE (= Data Terminal Equipment) means that CENTAURI IV gets its clockingfrom the dedicated X.21/V.35 line. Usually this is the standard mode.DCE (= Data Circuit Equipment) means that CENTAURI IV supplies theclocking for the X.21/V.35 dedicated line. Usually this is not the standardmode but e.g. it can be used to connect two CENTAURI IV back to back viaX.21.

3.6.4 Mayah codec (DTE) to Mayah codec (DTE)

When two MAYAH codecs are connected via a dedicated X.21/V.35 lineusually both devices use DTE mode i.e. the clock is supplied by the dedicatedX.21/V.35 line.

a) Cables

Standard X.21 DTE cable:





Standard V.35 DTE cable:

:

b) Configuration of X.21 interfaceThe X.21 interface settings can be configured via menu item Setup/Interface/X.21.The following settings are recommended for X.21:· X.21 mode: DTE· X.21 clocking: T4 or T4T1T4· X.21 protocol: X.21The following settings are recommended for V.35:· X.21 mode: DTE· X.21 clocking: T4 or T4T1T4· X.21 protocol: V.35

c) Configuration of Codec SettingsThe codec settings can be configured via menu item Setup/Audio Encoder[Decoder].

Configuration for MPEG transmissions:· Interface: X.21/V.35· Encoder dependency: Local (first MAYAH codec) and Remote (second

MAYAH codec)· Encoder bit rate: clock rate of X.21/V.35 line



· Decoder dependency: RemoteNote:Unlike with ISDN and IP connections at X.21/V.35 transmissions there is nosignalling when the network layer is established. Therefore there is noinitiation point to start the normal telegram exchange between CENTAURI IVset to remote. Thus the dependency of one CENTAURI IV must be set tolocal to pump out audio data all the time. The CENTAURI IV set to local alsodetermines the algorithm, the sample rate and the mode.

Configuration for G.722 and APT-X transmissions:· Interface: X.21/V.35· Encoder dependency: Local (on both MAYAH codec)· Encoder algorithm: Must be identical on all involved encoders and

decoders· Encoder sample rate: Must be identical on all involved encoders and

decoders· Encoder bit rate: clock rate of X.21/V.35 line· Encoder mode: Must be identical on all involved encoders and decoders· Decoder dependency: Local (on both MAYAH codec)· Decoder algorithm: Must be identical on all involved encoders and

decoders· Decoder sample rate: Must be identical on all involved encoders and

decoders· Decoder bit rate: clock rate of X.21/V.35 line· Decoder mode: Must be identical on all involved encoders and decoders

d) Establish X.21/V.35 ConnectionChoose 'Connect/Connect' menu or push the Express Dial Button to open theConnect-dialog:· Select the interface to X.21/V.35· Select the X.21/V.35 port to:

Port 1: Audio data stream is sent and received via X.21/V35 port 1 or Port 2: Audio data stream is sent and received via X.21/V35 port 2 or Port 1 & 2: Audio data stream is sent out via X.21/V35 port 1 and 2simultaneously (i.e. two audio data streams via two dedicated lines) or IMUX Port 1 & 2: One audio data stream is split and sent out via X.21/V.35 port 1 and 2 using CCS inverse multiplexing.

· Click the OK-button to establish connectionNote:Usually port 1 is selected.Note 2:



The X.21/V.35 connection must be established on both MAYAH codecs.

e) Disconnect X.21/V.35 ConnectionJust press the DISCONNECT button.Note:The X.21/V.35 connection should be disconnected on both MAYAH codecs.

f) Auto reconnect of X.21/V.35 connectionsAs long as a X.21/V35 connection is not disconnected the CENTAURI IVlooks for the appropriate clocking on the X.21/V.35 line all the time. Thismeans that a switched off X.21/V35 line is detected automatically by CENTAURI IV as soon as it is re-activated.

g) Meaning of LED’s at X.21/V.35 connections· Blinking Connect LED:

Bit rate of CENTAURI IV and clock rate of X.21/V.35 line does notcorrespond.

· Lit up Connect LED:Clock rate of X.21/V.35 line is detected.

· Lit up Framed LED:Framed X.21/V.35 connection

3.6.5 MAYAH codec (DTE) to another X.21/V.35 codec

When a MAYAH codec is connected via a dedicated X.21/V.35 line to anothercodec usually both devices use DTE mode i.e the clock is supplied by thededicated X.21/V.35 line.

a) Cables

identical to previous chapter

b) Configuration of X.21 interface

identical to previous chapter

c) Configuration of Codec SettingsThe codec settings can be configured via menu item Setup/Audio Encoder[Decoder].

Configuration for MPEG transmissions:· Interface: X.21/V.35· Encoder dependency: Remote· Encoder bit rate: clock rate of X.21/V.35 line· Decoder dependency: Remote

Configuration for G.722 and APT-X transmissions:· Interface: X.21/V.35



· Encoder dependency: Local· Encoder algorithm: Must be identical on all involved encoders and


decoders· Encoder bit rate: clock rate of X.21/V.35 line· Encoder mode: Must be identical on all involved encoders and decoders· Decoder dependency: Local· Decoder algorithm: Must be identical on all involved encoders and


decoders· Decoder bit rate: clock rate of X.21/V.35 line· Decoder mode: Must be identical on all involved encoders and decoders

d) Establish X.21/V.35 ConnectionChoose 'Connect/Connect' menu or push the Express Dial Button to open theConnect-dialog:· Select the interface to X.21/V.35· Select the X.21/V.35 port to:

Port 1: Audio data stream is sent and received via X.21/V35 port 1 or Port 2: Audio data stream is sent and received via X.21/V35 port 2 or Port 1 & 2: Audio data stream is sent out via X.21/V35 port 1 and 2simultaneously (i.e. two audio data streams via two dedicated lines) or IMUX Port 1 & 2: One audio data stream is split and sent out via X.21/V.35 port 1 and 2 using CCS inverse multiplexing.

· Click the OK-button to establish connectionNote:Usually port 1 is selected.

e) Disconnect X.21/V.35 ConnectionJust press the DISCONNECT button

f) Auto reconnect of X.21/V.35 connectionsAs long as a X.21/V35 connection is not disconnected the MAYAH codeclooks for the appropriate clocking on the X.21/V.35 line all the time. Thismeans that a switched off X.21/V35 line is detected automatically by theMAYAH codec as soon as it is re-activated.




Bit rate of CENTAURI IV and clock rate of X.21/V.35 line does notcorrespond.

· Lit up Connect LED:Clock rate of X.21/V.35 line is detected.

· Lit up Framed LED:Framed X.21/V.35 connection

3.6.6 MAYAH codec (DCE) to MAYAH codec (DTE) via crossover cable

Since MAYAH codecs support DCE- and DTE-mode it is possible to simulatean X.21 dedicated line between two MAYAH codecs without having a realdedicated X.21 line. For this just one MAYAH codec must be set to DCE modeto supply the clock. Furthermore a special DCE-DTE cable is necessary.

a) Cables

X.21 DCE-DTE crossover cable:

b) Configuration of X.21 interfaceThe X.21 interface settings can be configured via menu item Setup/Interface/X.21The following settings are recommended for the first MAYAH codec (DCE-MAYAH codec):· X.21 mode: DCE· X.21 clocking: T2T4· X.21 protocol: X.21The following settings are recommended for the second MAYAH codec (DTE-MAYAH codec):· X.21 mode: DTE· X.21 clocking: T4· X.21 protocol: X.21

c) Configuration of Codec SettingsThe codec settings can be configured via menu item Setup/Audio Encoder[Decoder].The following settings are recommended for the first MAYAH codec (DCE-



MAYAH codec):

Configuration for MPEG transmissions:The following settings are recommended for the first MAYAH codec (DCE-MAYAH codec):· Interface: X.21/V.35· Encoder dependency: Local· Encoder bit rate: clock rate to be tested· Decoder dependency: RemoteThe following settings are recommended for the second MAYAH codec (DTE-MAYAH codec):· Interface: X.21/V.35· Encoder dependency: Remote· Encoder bit rate: encoder bit rate of the DCE- MAYAH codec· Decoder dependency: RemoteConfiguration for G.722 and APT-X transmissions:· Interface: X.21/V.35· Encoder dependency: Local (on both MAYAH codec)· Encoder algorithm: Must be identical on all involved encoders and


decoders· Encoder bit rate: clock rate of X.21/V.35 line (i.e. encoder bit rate of DCE-

MAYAH codec)· Encoder mode: Must be identical on all involved encoders and decoders· Decoder dependency: Local (on both MAYAH codec)· Decoder algorithm: Must be identical on all involved encoders and


decoders· Decoder bit rate: clock rate of X.21/V.35 line (i.e. encoder bit rate of DCE-

MAYAH codec)· Decoder mode: Must be identical on all involved encoders and decoders

d) Establish X.21 ConnectionChoose 'Connect/Connect' menu or push the Express Dial Button to open theConnect-dialog:· Select the interface to X.21/V.35· Select the X.21/V.35 port to:

Port 1: Audio data stream is sent and received via X.21/V35 port 1 or Port 2: Audio data stream is sent and received via X.21/V35 port 2

· Click the OK-button to establish connectionNote:Usually port 1 is selected.Note 2:



The X.21 connection must be established on both MAYAH codecs.

e) Disconnect X.21/V.35 ConnectionJust press the DISCONNECT button.Note:The X.21 connection should be disconnected on both MAYAH codecs.

f) Auto reconnect of X.21/V.35 connectionsAs long as a DCE-MAYAH codec is connected it also supplies a clock for theDTE-MAYAH codec. The DTE-MAYAH codec looks for this clocking on itsX.21 port as long as it is connected. This means that the DTE-MAYAH codecreconnects automatically to the DCE-MAYAH codec.


the Bit rate of the DCE-MAYAH codec and the DTE-MAYAH codec does notcorrespond.

· Lit up Connect LED:After connection the bit rate of the DCE-MAYAH codec and the DTE-MAYAH codec corresponds.

· Lit up Framed LED:Simulated X.21/V.35 connection is framed.

3.7 How to establish ASI connections

3.7.1 ASI Basics

ASI stands for Asynchronous Serial Interface.In CENTAURI IV an optional ASI card can be used to stream MPEG TS

Mechanical and electrical specificationASI uses BNC connectors terminated with 75 Ohms. The signalling level is800 mV peak to peak. Maximum cable length of the BNC cables is 300meters.

Bit structureEvery Byte is wrapped by a start and stop bit. i.e. a start bit is sent, followedby eight data bits and terminated by a stop bit. Such a 10 bit structure is alsocalled 8B10 coding.

ClockingASI uses SDI clock described in SMPTE 259M i.e. a 27 MHz clock multipliedby 10bits. This means a maximum brutto bit rate of 270 Mbps.If lower bit rates are used then padding bits fill up the 270 Mbps.

Applications· STL (Studio Transmission Line)· SNG (Satellite News Gathering) and ENG (Electronic News Gathering)· SPTS (= single program transport stream)



· MPTS (= multiple program transport stream)

OthersCompeting standard is SMPTE 305M (SDTI).

To establish an ASI connection create an MPEG TS Session, e.g. by using the WebRemote and choose ASI as an interface instead of IP.

Part

IVElements of Frontpanel Control



4 Elements of Frontpanel Control

4.1 Preface

All CENTAURI IV have signal level display on the unit front. AdditionallyCENTAURI IV of type 3001 have a display and a keyboard. CENTAURI IV oftype 4000 can only be controlled via IP or RS232 (e.g. via Web remote controlor terminal connection).

CENTAURI IV offers both analogue and digital audio (compliant with AES/3) atup to 96kHz sampling rates, with 24-bit resolution A/D and D/A converters.Coding algorithms such as G.711, G.722, MPEG-1/2 Layer 2, MPEG-1/2 Layer3, MPEG-2/4 AAC, AAC (LD), AAC (HE), APT-X and Enhanced apt-X areavailable, in addition to its ability to handle linear audio. All of which, combinedwith networking via IP, ISDN or X.21/V.35 (optional)

The biggest improvements to the very successful CENTAURI I are:· The Gateway functionality· The Backup functionality· The Point to Multipoint functionality· The Dual Codec functionality· The Multi channel functionality (e.g. 5.1 transmission)

Please send technical questions regarding the CENTAURI IV and its front panelto [email protected].

4.2 LED'S

4.2.1 Level LEDs

By the LED level meter you will receive notice about the signal strength of the

mailto:[email protected]

67Elements of Frontpanel Control


incoming and/or outgoing signal. Which level to display can be configured viafront panel menu item SETUP/FRONTPANEL/ LEVELMETER.

When Input level is selected the bottom LED of a corresponding column lights uporange even if no audio is there to signal the Input availability.

4.2.2 Status LEDs

The CENTAURI IV has three status LED columns. You are getting informedabout the system health of the system, regarding the Encoder, Decoder or thestatus of the CENTAURI IV.

· Connectlights up when a connection is (being) established to another codec and/orwhen encoder is active

· Activitylights up when there's active connection running

· Framed lights up when a synchronized connection is established to another codec

· ISDN / IP / X21 / E1indicates the currently active interface (E1 is obsolete)

· Powerindicates that the CENTAURI IV is turned on

· AlarmLights up in case of an error (e.g.: too hot, fan error, voltage error).

· Alarm blinking when an update failed and the CENTAURI IV System software was damaged

· Dual Codecindicates if this function is activate

· Multipt/castindicates if this function (Point-to-Multipoint) is activate

· Gateway



indicates if this function (Point-to-Multipoint) is activate· Backup

indicates if this function (Point-to-Multipoint) is activate

4.3 Keyboard

4.3.1 Hot Keys

The hot keys F1 to F4 can be freely programmed by assigning scripts. Such ascript consists of one are more direct commands as described in theCommunication Reference manual (link: www.mayah.com/content/download/pdfs/manuals/communication-reference_man.pdf). The script can be created with any ASCII editor (e.g. Windows notepad).Each command must be written in a new line.The script must have the following names:· F1.CAF: Script hot key F1· F2.CAF: Script hot key F2· F3.CAF: Script hot key F3· F4.CAF: Script hot key F4To validate the scripts they must be copied in the CENTAURI IV flash memoryinto the folder ACTIONS. This can be done by FTP-access to the CENTAURI IV.The FTP access data is by default:· Host: <IP-address of codec>· User-ID: Admin· Password: Power

http://www.mayah.com/content/download/pdfs/manuals/communication-reference_man.pdf)

http://www.mayah.com/content/download/pdfs/manuals/communication-reference_man.pdf)



4.3.2 Function Keys

Express Dial Key This dialog button allows you, where ever you are in the menu, to access the dialmenu, and establish a connection.

Disconnect KeyThis dialog button allows you, where ever you are in the menu, to access thespeed dial menu and hang up an existing connection.

Phone book KeyThis dialog button allows you, where ever you are in the menu, to access thephonebook, choose one and dial it.

Head phone Key This dialog button allows you, where ever you are in the menu, to access theheadphone configuration and change the volume or the source to listen at.

4.3.3 Arrow Keys

With the UP/DOWN keys you navigate through the complete menu.

With the RIGHT-key you activate the chosen field and get the submenu. Insome menus, you will get to the ENTER-mode (e.g., IP address, PhoneNumber)



With the LEFT-key you delete in the ENTER-mode or get a submenu back.

With the GLOBE-key you activate the chosen field and get the submenu. Insome menus, you will get to the ENTER-Modus (like RIGHT-key).

4.3.4 Numeric Keypad

With the numeric keypad you can enter names, phone numbers orIP-addresses.

The input is similar to mobile phones. Just press a key as often until the neededchar is shown:Assigned key 1: 1 . : /Assigned key 2: 2 A a B b C c Assigned key 3: 3 D d E e F fAssigned key 4: 4 G g H h I iAssigned key 5: 5 J j K k L lAssigned key 6: 6 M m N n O oAssigned key 7: 7 P p Q q R r S sAssigned key 8: 8 T t U u V vAssigned key 9: 9 W w X x Y y Z zAssigned key 0: 0 <SPACE>Assigned key *: * + Assigned key #: # @

Hint:By pressing 1 or 9, you can jump to the start/end of a long selective list.



4.4 Window Structure and Key Control

The window structure and the key controls follow these rules:

The current window title is at the top left ( "Analog Levels"). It is displayedinverted. The action description is found to the right of the window title. In Figure1 the request is SELECT ITEM, since no selection has been made. As soon as

one of the list items is selected with the arrow keys and activated by pressing ,its name appears in the title bar (see Figure 2). This list item now reacts to thekey input. In order to leave this list item and save the setting made, one must

press .

After pressing the key in phone book or communication profile, the OK orCANCEL dialogs appear. In this the OK icon is pre-selected and furnished with a

thicker outline (see Figure 3). Pressing the key again gives positiveconfirmation of the whole dialog in this case.In all other dialogs the (also altered) setting is immediately taken over from the

dialog with .If in the case of phone book or communication profile dialogs you leave the dialogwithout making any changes, i.e. you want to quit the dialog, then press and

select the Cancel icon. When you now press the dialog is closed without being

saved or changed. To cancel all other dialogs it is sufficient to press .If an arrow pointing up and/or down appears in a display, there are then otherlines above or below the lines shown that you can shift up or down using and

and then bring onto the display.

4.5 Connect Menu

4.5.1 Disconnect

This dialog enables to terminate a connection.

4.5.2 Connect

This dialog enables to establish a connection (IP, ISDN, X.21/V.35) depending onthe selected interface. Therefore the appearance of this dialog can vary.

4.5.3 Last

This dialog enables to reestablish the last dialed connection from the list of theten last connections actively established from this device.

Note: If there is a phone book entry was used then the transmission will be establishedwith the exact parameters of the phone book entry. If the previous connection



was established directly then the repeating connection will be established overthe same network and with the current codec quality settings.

4.5.4 Phonebook

This dialog enables to dial a phone book entry.

A CENTAURI IV phone book entry will start following macros in the background:· Setting the encoder parameter according to a codec profile entry · Setting the decoder parameter according to a codec profile entry · Choosing an interface (IP, ISDN, X.21/V.35, LOOP or other) · Accomplishing a connection (optional) if an IP address, a number (ISDN) or a

port (X.21/V.35) is entered

Note:If no IP-address, number or port is entered a phone book entry works as an autoconfiguration script.

4.5.5 Session

This dialog enables to establish a streaming session.

More info about sessions can be found in chapter Presets Menu/New SessionEntry.

4.5.6 Interface

This dialog selects which Communications Interface is to be used. The usualoptions are:· ISDN (if available)· X.21/V.35 (if available)· Net (for IP connections)· Loop

Note:The bit rate for ISDN connections must be divisible by 64

4.5.7 FEC mode

- enables to set the FEC mode (= Forward Error Correction) for RTP/IPconnections.



More info about FEC can be found in chapter Necessary settings for framedconnections/How to establish IP connections/Forward Error Correction.

4.5.8 Subcodec

The CENTAURI IV family can run more than 1 internal codec (so calledsubcodec) for the following situations:· CENTAURI IV 5000 can run up to 32 subcodecs for IP transmission· CENTAURI IV 4000 can run up to 4 subcodecs for IP transmission· CENTAURI IV 3001 can run 2 subcodecs in

- Dual mode - Gateway Mode- Backup Mode

Although CENTAURI IV supports more than 1 sub codecs only one user interfaceis available. This setting lets the user select which sub codec the input and thedisplay applies to.

4.6 Status Menu

4.6.1 Level Status

The first status dialog shows the following audio levels referring to full scale in dB(from top to bottom):· left encoder level (i.e. left channel of audio input)· right encoder level (i.e. right channel of audio input)· left decoder level (i.e. left channel of audio output)· right decoder level (i.e. right channel of audio output)

Furthermore the following info's are given:

a) Selected interface (at bottom)

b) If a connection is active or not (at bottom). When a connection is active then the IP-address, the number (ISDN) or the port(X.21/V.35) is displayed.

c) Info about synchronization state of digital audio input (at top left). - means that a digital audio clock is detected- means that a digital audio clock is detected and CENTAURI IV locks to it



4.6.2 Encoder Status

The second status dialog can be reached with key when the level status isshown. At an active connection here the encoder coding settings are shown.

4.6.3 Decoder Status

The third status dialog can be reached with key when the encoder status isshown. At an active connection here the decoder coding settings are shown.

4.6.4 Lines Status

The fourth status dialog can be reached with key when the decoder status isshown. At an active ISDN or X.21/V.35 connection here the connection times ofthe B-channels (ISDN) or the ports (X.21/V.35) are displayed. This dialog is notvisible if the interface is set to IP or loop.

4.7 Presets Menu

4.7.1 New Session Entry

This dialog enables to create a new session entry. The following IP sessions canbe created and established via Front panel:· MPEG TS· DVB· DMBGeneral informations about sessions can be found in chapter Necessary settingsfor framed connections/How to establish IP connections/MPEG Transport Stream.

The following parameters can be set:

a) Session name:The maximum length of a session name is 256 characters.

b) Session mode:The session mode can be selected to:· MPEG TS (see also chapter MPEG Transport Stream)· DMB (= Digital Media Broadcast)If session mode is set to ‘unused’ the session is inactive.

c) Sub codec:Here the sub codec is selected. Every sub codec number stands for a different



destination i.e. it is assigned to a different elementary streamNote:· CENTAURI IV 5000 supports up to 32 sub codecs.· CENTAURI IV 4000 supports up to 4 sub codecs.· CENTAURI IV 3001 supports up to 2 sub codecs.· CENTAURI III 3000/3001 supports up to 2 sub codecs.· CENTAURI III 4000 supports up to 8 sub codecs.· CENTAURI II, GANYMED 1102, MERKII 3000/3001 supports up to 2 sub

codecs.· CENTAURI II 4000/4001 supports up to 4 sub codecs

d) Destination:One destination can be set for every sub codec of a session. It can be set to:· current setting (i.e. last IP connection)· phone book entry

4.7.2 Edit Session Entry

This dialog enables to modify an existing session entry.

4.7.3 Delete Session Entry

Choose a session entry by using the UP/DOWN keys and confirm its deletion

with the key.

4.7.4 New Phonebook Entry

This dialog enables to create a new phone book entry. Up to 256 phone bookentries can be made.


Name: The maximum length of a name you can enter are 256 chars. The displaycan show about 16 chars.

Settings: Complete Centauri IV settings chosen here.

Interface: The used communication interface is chosen here.

EncProfile: The encoder settings of this phone book entry are chosen here.



DecProfile: The decoder settings of this phone book entry are chosen here.

Direction: The Direction between Codecs chosen here.

Dest: Depending the chosen interface the entry may vary:

· IP: Enter the IP-Address or SIP-Address. For UDP-connections an 'u', forTCP-connections a 't', for SIP-connections 'sip':, for SDP-connections 'http://'and for SAP-connections 'sap://' must precede the IP-address. Since RTP isdefault at RTP no prefix is necessary.

· ISDN: Up to 8 ISDN-Numbers can be entered here · X.21/V.35: These connection possibilities are given:

- Connection via Port 1: Please enter 1 at ‚1’- Connection via Port 2: Please enter 2 at ‚2’- Sending the signal via Port 1 and 2: Enter 1 at ‚1’ and 2 at ‚2’

4.7.5 Edit Phonebook Entry

This dialog enables to modify an existing phone book entry.

4.7.6 Delete Phonebook Entry

Choose the designated phone book entry by using the UP/DOWN keys andconfirm with the RIGHT key.

4.7.7 New Profile Entry

This dialog enables to create a new profile entry . Up to 256 profile entries can bemade. Profiles are used in phone book entries as encoder or decoder settings.




a) NameThe profile name can be selected with a max. length of 20 chars. We suggestthat the name is based on the settings of the profile entry.For instance:Name "auto/l3/32/mono/64"Auto states the IMUX FormatL3 states the algorithm (e.g. MP3)32 states the sample rate (e.g. 32 kHz)mono states the mode (e.g. mono)64 states the bit rate (e.g. 64 kbit/s)

Using this name convention, will give you the most needed information in thename.

b) TypeSets the algorithm of the profile:· G.711· G.722· MPEGL2· MPEGL3· AAC (MPEG4)· AAC (MPEG2)· AAC (LD); optional· AAC (HE)· Linear· DAT (Linear 12 bit)· FCA (FlashCast); optional· 4SB ADPCM; optional· Std. APT-X sync; optional· Std. APT-X no; optional· Enh. APT-X 16 (enhanced APT-X with 16 bit); optional· Enh. APT-X 20 (enhanced APT-X with 20 bit); optional· Enh. APT-X 24 (enhanced APT-X with 24 bit); optional· AES/EBU transparent

c) Sample rateSets the sample rate of the profile



d) Bit rateSets the bit rate of the profile

e) ModeSets the mode of the profile to one of the following:Standard:· mono· dual mono· stereo· joint stereoMultichannel Audio (optional):Multichannel can be used with all APT-X algorithms, linear, AAC (MPEG4) andAAC (HE) provided the referring additional function is enabled. Multi channelaudio applies ADAT interface.· 4 Channels· 4 Channels (2CPE):

4 audio channels in CPE mode are used. CPE (= Channel Pair Element)means that a front and rear audio channel pair is encoded. This mode is justavailable for AAC (MPEG4) and AAC (HE).

· 4 Channels (MPEG):4 audio channels are used. In this context MPEG means that a center, a right,a left and a rear audio channel is encoded. This mode is just available forAAC (MPEG4) and AAC (HE).

· 6 Channels:· 8 Channels:

f) Dependency:Choose between 'Remote' or 'Local'

Remote means that the CENTAURI IV will use FlashCast-Technology.

FlashCast Technology means at ISDN:CENTAURI IV/CENTAURI IV and CENTAURI IV/SendIt-ConnectionsThe connecting CENTAURI IV will assign the transmission parameter.

CENTAURI IV/None-Mayah-Codec ConnectionsThe CENTAURI IV will analyse the data stream and emulate the receiver. Ifnecessary changes in the parameters will be done automatically and adjustedbest possible.

For most of the connections REMOTE will be the right choice.

g) FormatThe inverse multiplexing format (IMUX format) of the profile can be set here to:· Auto· CDQ/H.221· Musictaxi· J.52· Micda



· APTXInverse multiplexing is needed in ISDN connections to synchronize theB-channels. If the IMUX format is set to Auto, usually CENTAURI IV uses thecorrect IMUX format.

Exception 1:If a CENTAURI IV establishes a connection to a CDQPrima using algorithmMPEG L2 and the line format is H.221 thenCENTAURI IV must be configuredwith:Algorithm: MPEGL2Bit rate: 384 kbit/s (even if a lower bit rate is set on the CDQPrima)IMUX Format: CDQ/H.221

Exception 2:If you dial to a APT-X codec then the IMUX format must be set APTX.

h) AncillarymodeDefines how the Encoder and Decoder embeds the ancillary data in the audiodata stream. Following settings are possible:· Auto· TS

i) ProtectionThis option handles the activation and deactivation of the encodersCRC-protection. It works with different parameters for MPEG algorithms.(CRC= Cycle Redundancy Check)Three parameter can be set:0: default1: off2: on

j) Profile Audio TypeSets the audio type (i.e. source for Encoder and destination for Decoder) to oneof the following:· Analog· TOSlink (i.e. optical digital input)· AES/EBU (i.e. balanced electrical input)· ADAT (ADAT interface, uses optical TOSlink port)

With ADAT the following channel combinations are possible:· Standard:

2 channels: ADAT12, ADAT34; ADAT56 .. ADAT2324· Multi channel:

4 channels: ADAT14, ADAT586 channels: ADAT168 channels: ADAT18



4.7.8 Edit Profile Entry

This dialog will edit an existing profile entry. Details regarding the possiblechanges are shown in New Profile Entry.

4.7.9 Delete Profile Entry

This dialog will delete an existing profile entry. Choose the profile entry you want

to delete and press the key.

4.7.10 New Settings Entry

This dialog enables to create a new Settings entry.

Settings including the complete configuration of Centaur IV.

4.7.11 Save Settings Entry

This dialog enables to save a new Settings entry.

4.7.12 Rename Settings Entry

This dialog enables to rename a existing Settings entry.

4.7.13 Delete Settings Entry

This dialog enables to delete a existing Settings entry.



4.8 Setup Menu

4.8.1 Audio Encoder

The content of the dialog choice will vary the given situation. That meansthat the CENTAURI IV just shows parameters which are adjustable.

a) Encoder Type- sets the algorithm to:· G.711· G.722· MPEGL2· MPEGL3· AAC (MPEG4)· AAC (MPEG2)· AAC (LD); optional· AAC (HE)· Linear· DAT (Linear 12 bit)· 4SB ADPCM; optional· FCA (FlashCast); optional· Std. APT-X sync; optional· Std. APT-X no; optional· Enh. APT-X 16 (enhanced APT-X with 16 bit); optional· Enh. APT-X 20 (enhanced APT-X with 20 bit); optional· Enh. APT-X 24 (enhanced APT-X with 24 bit); optional· AES/EBU transparent

b) Encoder Sample ratesets sample rate

c) Encoder Bit ratesets bit rate

d) Encoder Mode- sets the audio mode to:· Mono · Dual Mono · Stereo · Joint Stereoor



· a Multichannel mode (optional)

Multichannel can be used with all APT-X algorithms, linear, AAC (MPEG4)and AAC (HE) provided the referring additional function is enabled. Multichannel audio applies ADAT interface.· MC4: 4 audio channels are used.· MC4 CPE: 4 audio channels in CPE mode are used. CPE (= Channel Pair

Element) means that a front and rear audio channel pair is encoded. Thismode is just available for AAC (HE) and AAC (MPEG 4).

· MC4 MPEG: 4 audio channels are used. In this context MPEG means that acenter, a right, a left and a rear audio channel is encoded. This mode is justavailable for AAC (HE) and AAC (MPEG 4).

· MC6: 6 audio channels are used.· MC8: 8 audio channels are used.

e) Encoder Dependency- sets the Encoder dependency to either:· Remote· LocalRemote means that the CENTAURI IV will use FlashCast-Technology.Remote FlashCast Technology means at ISDN:· CENTAURI IV/CENTAURI IV and CENTAURI IV/SendIt-Connections

The connecting CENTAURI IV will assign the transmission parameter.· CENTAURI IV/None-Mayah-Codec Connections

The CENTAURI IV will analyse the data stream and emulate thereceiver. If necessary changes in the parameters will be doneautomatically and adjusted best possible.

For most of the connections REMOTE will be the right choice.

f) Encoder (IMUX) Format- sets the Encoder IMUX (Inverse Multiplexer) format to:· Auto· J.52· CDQ/H.221· MICDA· APTX· Musictaxi

Inverse Multiplexing is vital for the correct synchronization of the multipleB-channels used in an ISDN transmission. If the IMUX format is set toAuto then CENTAURI automatically uses the correct IMUX format.

Exception 1:If a CENTAURI IV is to establish a connection to a CDQ Prima set toMPEG L2 and the line format is H.221 then Centauri must be configuredwith:Algorithm: MPEGL2Bit rate: 384 kbit/s (even, if the Prima uses a smaller bit rate) IMUX Format: CDQ/H.221



Exception 2:If you dial to a APT-X codec then the IMUX format must be set to APTX.

g) Encoder Ancillary dataGenerally there are two possibilities to transmit ancillary data:· Ancillary data transfer inside of the coded audio

In this case the ancillary data is transported inside of the audio stream. It justworks with all MPEG algorithms (MPEG L2, MPEG L3, AAC) and all APT-Xalgorithms. The following selections are possible for:MPEG L2:- Auto- CCS- J.52- Musictaxi- BarcoAll other MPEG algorithms:- AutoAPT-X algorithms:- None- Left- Right

· Ancillary data transfer with help of an extra ancillary data stream (calledTS)This just works with RTP/IP transmissions but with all algorithms. In this casethe ancillary data format must be set to TS.

h) ProtectionThis option handles the activation and deactivation of the encodersCRC-protection. It works with different parameters for MPEG algorithms.(CRC= Cycle Redundancy Check)Three parameter can be set:0: default1: off2: on

4.8.2 Audio Decoder

The content of the dialog choice will vary the given situation. That meansthat the CENTAURI IV just shows parameters which are adjustable.

Most of the settings are identical with Audio Encoder



4.8.3 Audio Settings

4.8.3.1 Audio In/Out

Audiosettings can be configurate on the Webremote Setup/Audio.

a) Audio In- sets the audio input source to one of the following:· Analog· AES/EBU digital (i.e. balanced electrical input) [DB-9F]· ADAT digital (ADAT interface also uses optical port) [TOSlink]

With ADAT the following channel combinations are possible:Standard with 2 channels:ADAT12, ADAT34, ADAT56 .. ADAT232Multi channel· 4 channels: ADAT14, ADAT58· 6 channels: ADAT16· 8 channels: ADAT18

b) Audio Out- sets the audio output to use one of the following:· Analog· AES/EBU digital (i.e. balanced electrical output) [DB-9F]· ADAT digital (ADAT interface also uses optical port) [TOSlink]

With ADAT the following channel combinations are possible:Standard with 2 channels:ADAT12, ADAT34, ADAT56 .. ADAT232Multi channel· 4 channels: ADAT14, ADAT58· 6 channels: ADAT16· 8 channels: ADAT18

Note:When Analog or AES/EBU is selected as audio output then automatically theaudio signal is also output at the other two interfaces (i.e. at all audio outputsexcept for ADAT).



4.8.3.2 Mixer

a) Mixer

In Mono mode this selects which audio channel is used.

· Left: Only the left audio signal is used· Right: Only the right audio signal is used· Mixed: Left and Right audio signal is used (L+R-6 dB)

4.8.3.3 Analog Levels

- enables you to set the max. analog input level (i.e. level before the A/Dconverter) respectively the max. analog output level (i.e. level behind the D/Aconverter).These levels are also called clipping levels.

a) In-OutUsing IN the input level can be changed. Using OUT the output level can bechanged. Both levels can be separately adjusted.

b) LevelThe minimum value is 0 dBu. The maximum value depends of the implementedaudio card and may have following values: · 18 dBu· 22 dBu.

Using ADJUST the user can adjust the needed value with the up/down keys.Besides ADJUST the standard values 15 dBu and 18 dBu can be selecteddirectly.



4.8.3.4 Audio Settings

Here some miscellaneous (but rarely used) audio settings can be done.

a) ADAT/AES MasterThis item activates or deactivates the ADAT Mastermode. Turned off CENTAURI IV digital audio is be clocked via the ADAT input interface (opticalTOSlink interface) if a clock is supplied to this interface. Turned on theCENTAURI IV acts as the clock generator for ADAT audio interface. By default itis turned off.

b) All SRC's offThis item enables to switch off all internal sample rate converters of CENTAURIIV. The internal sample rate converters just must be switched off (i.e. this itemmust be set to 'on') when algorithm AES/EBU transparent (optional) is used. Usually and by default the sample converters must be switched on (i.e. this itemis set to 'off') for proper operation of CENTAURI IV.

c) AES/EBU out profThis item enables or disables professional mode for AES/EBU output. By defaultprofessional AES/EBU output is disabled.

d) Digital Out Sync.defines the AES/EBU output clock source. If an ‘internal’ source is selecteddifferent sample rates can be chosen.

4.8.4 Interface

4.8.4.1 Communication Interface

With this dialog the used Communication Interface can be selected to:· Net (Ethernet Interface for IP transmissions)· ISDN (if ISDN card is installed)· X.21 (if X.21/V.35 card is installed)



· Loop

Note:At ISDN the bit rate must be divisible by 64.

4.8.4.2 ISDN

This dialog enables to configure the ISDN settings of CENTAURI IV. Thisselection is just available if an ISDN card is installed.

a) ChannelThe item enables to set the MSN and/or the SPID for every available B-channel(usually 4 or 8 B-channels are available).

MSN (= Multiple subscriber number)In this field the MSN (D-channel protocol DSS1 or VN4) or the ID (all other D-channel protocols) is entered.The most common reason to use a MSN are:· Multiple ISDN devices using the same ISDN service uses one ISDN bus (e.g.

CENTAURI IV and telephone are connected to the same ISDN bus)· CENTAURI IV is connected to a PBX (=Private Branch Exchange)Note:If a CENTAURI IV is connected directly to an ISDN DSS1 S0 bus and no other

device shares this ISDN bus then no MSN's must be entered. 'Directly' meansthat no PBX is used.Note 2:At D-channel protocols NI1 and 5ESS an ID must be assigned for every B-channel.

SPID (=Service Profile Identifier)SPID's are only in use with the D-channel protocol NI1 and 5ESS in NorthernAmerica. At these two protocols it is mandatory to assign every B-channel aseparate SPID. Please ask the local ISDN provider for further details.



b) Protocol

This item enables to select the D-channel protocol to:· DSS1 (Europe)· NI1 (North America)· 5ESS (North America· Jate (Japan· VN (obsolete French national protocol; usually replaced by DSS1)· AUSTEL (obsolete Australian national protocol; usually replaced by DSS1)Furthermore this item enables to set:Active layer 1 mode- determines whether ISDN Layer 1 stays active all the time, or not.When CENTAURI IV is used in the Netherlands, this value should definitely beset to ON.Answer time- defines the ‘telegram’ interval (used in ISDN connections) - in milliseconds. Thecalled CENTAURI IV sends out its ‘telegram’ 10 times till the ISDN answer delayexpires. The default value is 5,000 ms.

c) PBX (=Private Branch Exchange)

PBX and PBX digitsWhen CENTAURI IV is connected to a PBX or ISDN switch, it is often necessaryto add a number for external access (e.g. 9). PBX digits determines the numberof digits BEFORE the 'additional preceding PBX number' becomes valid.For example:- PBX: 9- PBX digits : 5Entered number: 1234 Dialed number: 1234Entered number: 01234 Dialed number: 901234PredialSometimes it is necessary to use a special provider to guarantee the quality ofthe ISDN service or the carriage of ISDN calls through a Gateway. Usually aspecial provider can be selected by dialing a special call-by-call number beforethe normal number.This Predial Number precedes EVERY dialled number (Direct dial or Phone



book).National- determines how a national call is shown.For example:- National: 0- identification of national call: 811551762- number displayed: 0811551762International- determines how an international call is shown.For example:- international: 00- identification of international call: 49811551762- number displayed: 0049811551762

d) Redials

Redials- defines the number of Redials which will be attempted.A Redial will occur if the other party cannot be reached either through being busy,if there’s no response, or if the other party disconnects/drops the call.Redial wait- sets the interval time between the redial attempts (in seconds).

e) Delay- sets the audio delay applied to the ISDN interface. The maximum value is 5,000ms.Increasing this value can make ISDN connections more stable, by providing alarger (longer) buffer. For instance the audio delay buffer can compensate jitter.

4.8.4.3 X.21

This dialog enables to configure the X.21/V.35 settings of CENTAURI IV. Thisselection is just available if an X.21/V.35 card is installed.

a) Interface- selects if X.21/V.35 port 1 or 2 (if available) should be configured.



b) Mode- sets the X.21/V.35 port Mode to either DTE or DCE.In DTE (Data Terminal Equipment) mode, CENTAURI IV receives its clockinginformation from the network - or a dedicated line. In DCE (Data Circuit Equipment) mode, CENTAURI IV itself supplies the clockinginformation.In most cases, the DTE mode will be used.

c) Clocks- sets the clocking format of the X.21/V.35 port. In DTE mode, T4 clocking is usually used. In DCE mode, T2T4 clocking is most commonly used.The meaning of the different clocks is described in the Interface Manual (link: www.mayah.com/content/download/pdfs/manuals/centauri-interface_eng.pdf).

d) Protocol-selects the fixed line’s connection protocol to either X.21 or V.35 format.

e) DualportWhen set to 'yes' then the data stream is delivered parallel to both ports.

f) Delay- sets the audio delay applied to the X.21/V.35 interface. The maximum value is5,000 ms.Increasing this value can make X.21/V.35 connections more stable, by providinga larger (longer) buffer. For instance the audio delay buffer can compensate jitter.

4.8.4.4 Network

This dialog enables to configure one of both network cards of CENTAURI IV. Iftwo network cards are installed then the first one is responsible for remotecontrol, the second one for audio over IP.




a) Interface- selects the network card to configure.

b) DHCP- sets DHCP to Client or Off

c) Address- sets the IP address for the appropriate interface. (e.g. 192.168.10.50)

d) Netmask- sets the subnet mask for the appropriate interface. (e.g. 255.255.255.0)

e) Gateway- sets the IP address of the default network Gateway (for the appropriateinterface).

f) DNS Server- sets the IP address of the DNS (= Domain Name System) server for theappropriate interface.

g) SNMP Server- sets the IP address of the SNMP (= Simple Network Management Protocol)manager. This address will be used as the destination for the SNMP traps.

h) Transferrate- defines the transfer rate (speed) for the appropriate network interface, to either:· Auto (i.e. auto-sensing the network data rate)· 10 Mbit/s· 100 Mbit/s

i) Duplex- selects the operating mode for the appropriate interface as:· Auto (i.e. auto-sensing of duplex mode)· Half· Full

j) SNMP TrapsThe CENTAURI IV can handle SNMP Traps according to SNMP versions 1.0,1.1, 2.0, 2.1

k) Packetsize- defines the packet size of the IP datagrams used. The maximum value is 1,514bytes.

l) Packetsizemode- selects the mode how CENTAURI IV creates IP packets. There are threepossibilities:· variable (default)

This means that the payload is rounded to the next full frame or audio block



Advantage:No fractional audio frames or blocks in the IP packetsDisadvantage:With algorithms with no fix frame length (e.g. AAC) it can happen that themax. possible packet size is exceeded.

· fixedThis means that IP payload is exactly the same as the packet size value set atitem packetsize (i.e. it is not rounded to the next full audio frame or audioblock).Advantage:Even with algorithms with variable frame length the packet size is fix.Disadvantage:IP packet can have fractional audio frames or audio blocks.

· sync.Same as fixed but additionally packets are transmitted in synchronizedintervals.Advantage:Same as with fixed but additionally adaptation to network equipment whichhas got problems with unsynchronized packets.Disadvantage:Same as with fixed.

m) Audio Delay- sets the audio delay applied to the IP interface. The maximum value is 5,000ms. Increasing this value can make IP connections more stable, by providing alarger (longer) buffer. For instance the audio delay buffer can compensate jitterproblems.

o) SIP (Session Initiation Protocol)- configures all the parameters of SIP session. More details about about SIP canbe found in chapter Necessary settings for framed connection/How to establish IPconnections/IP connections.

GlobalproxyHere the global proxy must be entered. The global proxy is responsible for howSIP requests and messages are handled.In this field an IP-address or a URL can be entered.This setting is optional.

StunserverA STUN server (= Simple Transversal of UDP Through NATs) is necessary that aclient behind a NAT or NATs can find its public IP address. NAT stands for N



etwork Address Translation.The public IP address is necessary since the SIP device on the other end needsthis info to find the local client.In this field an IP-address or an URL can be entered.This setting is optional.

Account IdHere the SIP registration profile can be selected.

Account activeJust an active profile cause an registration. However, only an inactive profile canbe changed.Therefore at a new profile first ‘Active’ must be set to 'off'. After all registrationinfo is entered ‘Active’ must be set to 'on' to validate the registration.

Account RegistrarThe Registrar is the SIP registration server which resolves the SIP address to areal IP address. The SIP client must register itself to a Registrar first before it canuse its service. In this field an IP-address or an URL can be entered.The registration comprises the following access data:- Name- Password- Phone Number (just necessary for a few registrars)

Account PhonenrHere the phone number of the registration access data can be entered (max. 256chars). This access data is just necessary for a few registrars.

Account UsernameHere the name of the registration access data can be entered (max. 256 chars).

Account PasswordHere the password of the registration access data can be entered (max. 256chars).

p) FECEnables to set the FEC mode (= Forward Error Correction) for RTP/IPconnections.

More info about FEC can be found in chapter Necessary settings for framedconnections/How to establish IP connections/Forward Error Correction.

4.8.4.5 WLAN

This dialog enables to configure the Wlan settings of CENTAURI IV. CompatibleWlan dongles are optional available by MAYAH.



4.8.4.6 Security

In this dialog security settings for· Dial protection· ISDN service protection can be set

a) Dial Protection

Manual Accept- determines how Incoming connections are accepted.· auto:

Accepts all calls that are permitted by 'Dial in protection ISDN' and/or 'DialProtection IP' automatically

· manual: Accepts all calls manually

· dbpos: Accepts all calls that are permitted by 'Dial in protection ISDN' and/or 'DialProtection IP' manually

· dbneg:Accepts all calls that are not permitted by 'Dial in protection ISDN' and/or 'DialProtection IP' manually, the others are accepted automatically

Dial Protection ISDNWhen 'Dial Protection ISDN' is set to On, only connections from ISDN numberswhich are stored in the Phone book will be accepted according to rules of ManualAccept.

Dial Protection IPWhen 'Dial Protection IP' is set to On, only connections from IP addresses whichare stored in the Phone book will be accepted according to rules of ManualAccept.

b) ISDN Service protection



Here you can set which ISDN services may accept calls.

Note:Ex-factory, the default ‘enabled’ services are::· Speech· Unrestricted dig. info· Restricted dig. info· 3.1 kHz audio· 7 kHz audio· Telephony· 7 kHz telephonyYou are strongly advised NOT TO CHANGE these Enabled services, as thiscan restrict the ISDN functionality of your CENTAURI IV codec.

4.8.5 Frontpanel

4.8.5.1 Frontpanel

This dialog enables to configure the back light and the contrast of the LCD-display of CENTAURI IV front panel.



a) Backlight- select if LCD back light is switched on or off.

b) Contrast- sets the LCD brightness of the LCD display. Depending on CENTAURI IVhardware '30' or '38' are the most recommendable values.

4.8.5.2 Headphone

This dialog enables to set the source and the volume of the headphone output.

a) Source- selects the headphone source to:· Analog Input· Analog Output· Digital Input· Digital Output

Note:If a left or right item is selected the referring mono signal can be listened on both

ears.

b) Volume- sets the headphone volume.

You can also set the volume of the headphone with volume button.

4.8.5.3 Levelmeter

This dialog determines what audio levels are displayed on the 8 LED level metersof the front panel.

· None:No audio levels are displayed

· InOut:(default value)



Different audio levels for sub codec 1 are shown:- 4 audio input channels (row 1-4)- 4 audio output channels (row5-6)- Left Audio input on row 1- Right audio input on row 2- Left audio output on row 5- Right audio output on row 6

· In:Different audio input levels for sub codec 1 are shown:- 8 audio input channels (row 1-8)- Left Audio input on row 1- Right audio input on row 2

· Out:Different audio output levels for sub codec 1 are shown:- 8 audio output channels (row 1-8)- Left Audio output on row 1- Right audio output on row 2

· INOUT2:Different audio levels for sub codec 1 and 2 are shown:- Left and right audio input channel of sub codec 1 (row 1-2)- Left and right audio output channel of sub codec 1 (row 3-4)- Left and right audio input channel of sub codec 2 (row 5-6)- Left and right audio output channel of sub codec 2 (row 7-8)

· IN4: Different audio input levels for sub codec 1, 2, 3 and 4 are shown:- Left and right audio input channel of sub codec 1 (row 1-2)- Left and right audio input channel of sub codec 2 (row 3-4)- Left and right audio input channel of sub codec 3 (row 5-6)- Left and right audio input channel of sub codec 4 (row 7-8)

· OUT4: Different audio output levels for sub codec 1, 2, 3 and 4 are shown:- Left and right audio output channel of sub codec 1 (row 1-2)- Left and right audio output channel of sub codec 2 (row 3-4)- Left and right audio output channel of sub codec 3 (row 5-6)- Left and right audio output channel of sub codec 4 (row 7-8)

4.8.6 Miscellaneous

4.8.6.1 Subcodec

The CENTAURI IV family can run more than 1 internal codec (so called subcodec) for the following situations:· CENTAURI IV 5000 can run up to 32 sub codecs for RTP/IP transmissions· CENTAURI IV 4000 can run up to 4 sub codecs for RTP/IP transmissions· CENTAURI IV 3001 can run two sub codecs in

- Dual mode - Gateway Mode- Backup Mode



Although CENTAURI IV supports two individual sub codecs only one userinterface is available. This setting lets the user select which sub codec the inputand the display applies to. The setting is only active when one of the aboveapplications is active too.

4.8.6.2 Dualmode (ISDN)

With ISDN CENTAURI IV can be used as two separate mono codecs. However,the following restrictions will apply:· Maximum sample rate: 32 kHz· Mode: mono

This setting defines on which B-channel the ‘second (sub) codec’ starts tocommunicate.For example:‘Dual mode on B-channel = 2’ means that B-channel 1 is assigned to the first(sub)codec and all other B-channels are assigned to second one.If dual mode at B-channel = 0 then dual mode is de-activated, and CENTAURI IVfunctions as a single codec, without the above restrictions.Note:Dual mode just can be set if the communication interface of both sub codecs isset to ISDN. If this is not true dual mode can not be set or does not work properlypending on the system software version.Note 2:Dual mode can not be used if one the following features is active:· Multipoint· Gateway· Backup Mode

The convinient way of establishing Dual Mode connections is offered in the WebRemote. Please read the Web Remote 4 manual for more details. It can be found on http://www.mayah.com/help

4.8.6.3 Multipoint

- determines which return Channel is used on a Point-to-Multipoint transmission. [Using ISDN, Point-to-Multipoint means that a CENTAURI IV codec can transmitone audio signal out to multiple ISDN destinations. However, with Point-to-Multipoint (PMP) CENTAURI IV just can decode one return channel. This optionallows you to define which of the return paths you wish to use.]PMP functionality works with any of the following ISDN-capable codecs:· MAYAH CENTAURI and C11 family




· MAYAH MERKII· Worldnet Tokyo· Millennium 2· CDQPrima· CDQ2000/2001Note:Even negative return channels can be selected. A negative return channel meansthat all multi point locations still receive the audio but the central CENTAURI IVdoes not decode any audio.Note 2:Multipoint can not be used if one the following features is active:· Dual mode· Gateway· Backup Mode

4.8.6.4 Gateway

- enables to configure the gateway feature of the CENTAURI IV. Gatewayfunctionality means that CENTAURI IV will route received audio from oneinterface to another (e.g. MPEGL2 audio received at ISDN is sent out asMPEGL3 audio over IP). The following parameters can be selected:· off: Gateway functionality is disabled· current setting: Routing to last established connection· phone book: Routing to a phone book entry

Note:A general description of the CENTAURI IV gateway feature can be found atchapter Miscellaneous/Gateway.Note 2:Gateway feature can not be used if one the following features is active:· Dual mode· Multipoint· Backup Mode

4.8.6.5 Backup Mode

- enables to configure the backup feature of the CENTAURI IV . Backup featuremeans that CENTAURI IV establishes automatically another connection ifframing is lost. The following parameters can be selected:· off: Backup mode is disabled· current setting: Backup to last established connection· phone book: Routing to a phone book entryFurthermore the Backup time can be set via Setup/Miscellaneous/Timeouts.Note:A general description of the CENTAURI IV backup feature can be found atchapter Miscellaneous/Backup.Note 2:Backup mode can not be used if one the following features is active:· Dual mode



· Multipoint· Gateway

4.8.6.6 Concealment

Here are the possible settings for Error Concealment.

a) Disabled No error concealment

b) Sine waveSine wave with an amplitude a = 0.71* int_max and frequency f = 440 Hz

c) Zero substitutionZero substitution / pass through

d) Packet repeat (with merging)Very fast with more or less poor quality

e) BURG -4 Extrapolation using Burg's prediction filterExtrapolation using Burg's prediction filter with: lambda = 0.86, p = 100, N =N_max, excitation of filter withmultiple times mirrored residual (transient has to be removed before!)Fast with fairly good quality

f) BURG -5 Extrapolation using Burg's prediction filterSame as BURG -4, but: lambda = 0.8, p = 200Fast with fairly good quality

g) BURG -6 Extrapolation using Burg's prediction filterSame as BURG -4, but: lambda = 0, p = 1000, if N_max < 2 * p -> p = N_max / 2Relative slow with good quality

h) BURG -7 Extrapolation using Burg's prediction filterSame as BURG -4, but: lambda = 0, p = 1000, N = G + pRelative slow with good quality

4.8.6.7 Language

- selects the front panel language to either:· English· Spanish· German



4.8.6.8 Identification

Identification dialog comprises the following items:

a) IDHere the name of the CENTAURI IV is displayed and can be changed. This canbe useful on transmission between MAYAH devices, since this name will bedisplayed on the remote side as connection partner ID

b) SNHere the CENTAURI IV serial number is displayed. Since usually the serialnumber of the CENTAURI IV is the MAC (= Media Access Control) address ofthe first network card it is impossible to edit this serial number. If no Serialnumber is displayed, it’s possible that no Ethernet card was detected during bootup. In this case the ALARM LED of the CENTAURI IV will light up.

4.8.6.9 Versions

- displays the versions of the different software of CENTAURI IV.

For the regularCENTAURI IV user just the system version is important. Thesystem version displays the firmware state.

4.8.6.10 Factory Default

- enables to reset miscellaneous parameters of CENTAURI IV to factory defaultvalues. The following selection can be made:· All (resets all categories listed below)· System· Encoder· Decoder· ISDN (if ISDN card is available)· Audio· IP· X21 (if X.21/V.35 card is available)· Common



· Phone book· Profile· SNMPTrap· EventAction· TTLOutput· Timeouts· Regulation· Frontpanel· Session· Ports

In the appendix of the Communication Reference manual (link: www.mayah.com/content/download/pdfs/manuals/communication-reference_man.pdf) it is described what parameters are really reset.

Note:Since reset parameters are lost if they are not saved before please handle thisitem with care.

4.8.6.11 Timeouts

The following timeouts can be set:

a) Disconnect:- defines the period (in seconds) after which a connection is dropped, if no validframing is achieved. Ideally, it should be set higher than the G.722 SRT timeoutvalue – its default value is 45 seconds.

b) Stat. framing- defines the G.722 ‘timeout’ (measured in seconds).Generally, there are two methods to synchronize G.722 data streams. Generally, there are two methods of determining the ‘octet-start’ (byte-start) inG.722 data streams. They are:· G.722 with H.221 (in-band signalling)

H.221 uses a small amount of the data capacity (i.e.1.6 kbit/s of 64 kbit/s) totransmit the synchronization information in-band.[Although G.722/H.221 is a recommended EBU standard, it’s not verywidespread!]

· G.722 SRT (Statistical Recovery Timing)Synchronization requires finding the start bit of every G.722 octet, and isreached by evaluating the data pattern of the signals statistically. We DON’T





recommend that you use a pure sine wave signal whilst trying to achievesynchronization, using G.722 coding!

CENTAURI IV codecs will auto-detect a G.722/H.221 data-stream since theyevaluate the H.221 in-band signalling information. However, as G.722 SRTsignals do not have such signalling, CENTAURI IV only switches to the G.722SRT setting when the ‘G.722 timer’ expires and framing has yet to be achieved.This G.722 timer starts once the first ISDN line is connected.It is recommended that the G.722 SRT timeout be set to ~30 Seconds. This valueis high enough not to interrupt any auto-detection process, but should still beacceptable for framing up.

c) Remote control- sets the remote control timeout (in seconds). This timeout refers to any win socket IP control connection (Telnet). It determineswhen CENTAURI IV release automatically an idle Telnet control connection. '0'means that this timeout is deactivated. For instance this parameter can be helpfulwhen the telnet remote control session (also established by CENTAURI windowsremote control software) was temporarily interrupted by a faulty switch our routerbut CENTAURI IV still 'thinks' it is IP remote controlled. If remote control timeoutis set to '0' CENTAURI IV does not release the remote control port . If it is set to100 seconds then a new remote control session can established when thetimeout is expired.

d) Backup time- sets the backup time as used by the Backup mode (in milliseconds).Backup time is the time the backup event (= framing lost) must minimum lastbefore the backup connection defined in the menu Backup Mode is established.

4.8.6.12 BGAN

The Broadband Global Area Network (BGAN), is a global Satellite IP Networkusing portable terminals. Centauri IV is connected to a terminal via Ethernetinterface, just like to any other Ethernet switch.

In this menu the BGAN mode can be activated or deactivated.

MAYAH Audio Codecs support the following terminals:

· Thrane & Thrane: Explorer 500, 700· Addvalue Communications: Wideye Sabre 1, Wideye Sabre Ranger· Hughes Network Systems: 9201, 9250, 9350

Most BGAN Terminals are also DHCP Servers, so it is recommended to enablethe DHCP function on your Centauri IV.

Note:For most BGAN Terminals and subscriptions the following configuration optionscan be left empty, use them only if you know what you are doing.



In this menu it is also possible to predefine the following parameters for a BGANconnection:· PIN· APN· Password

The PIN, APN and password – if needed – should be entered and saved bypressing OK before the BGAN Mode is set to 'on'.

For more information on BGAN functionality please consult the Application Note32 on MAYAH's web site.

4.8.6.13 Ancillary

This dialog enables to configure the [DB9-M] ancillary data port on the rear sideof CENTAURI IV. The ancillary format is set at Setup/Audio Encoder and Setup/Audio Decoder.More detailed info about ancillary data transfer can be found at Miscellaneous/Ancillary Data Background.

The following items can be set:

a) Baudrate- defines the baud rate of the Ancillary data port.The following baud rates are allowed:· 1,200· 2,400· 3,600· 4,800· 9,600· 14,400· 19,200· 38,400· 56,00· 57,600· 115,200Note:This setting only specifies the maximum physical value, NOT the actual amountof ancillary data sent inside the audio data stream.

b) Databits- sets the number of bits used to represent one single “character” of data.



The following are permissible values:· 8· 7· 6· 5

c) Parity- sets the parity bit (used for error detection in a digital transmission path).Definition of parity:A technique to test the integrity of digital data by checking an extra bit that holdsa 0 or 1, depending if the data is an even number of 1 bits or an odd number of 1bits.The following parity values are permissible:· None· Odd· Even

d) Stop Bits- sets the number of Stop bits (used to indicate the end of a byte).The following values are permissible:· 1· 2

e) Handshake- sets the mode of ancillary (auxiliary) data handshaking.Handshaking means that signals are transmitted back and forth to control (i.e. tostart and stop) the transmission.The following values are possible:· None· Xon/Xoff· RTS/CTS· DSR/DTR

4.8.6.14 Time Settings

This dialog enables to set· Date & Time: setting of time, date and the referring format manually· Timezone: configuration data for synchronization with a NTP server

a) Date & Time



For date the following formats can be selected:· D.M.Y:

- Day-Month-Year - e.g. 08.01.2008 for 8th of January 2008- usually used in Mid Europe

· M/D/Y:- Month/Day/Year- e.g. 01/08/2008 for 8th of January 2008- Middle Endian format- used in USA

· Y-M-D:- Year-Month-Day- e.g. 2008-01-08 for 8th of January 2008- International date format according to ISO 8601- this is the most logic data format since chronological order corresponds toalphabetical one

For time format it can be selected between· 24 hour format· 12 hour AM/PM format

b) Timezone- sets parameters necessary for time synchronization with a NTP (= Network Time Protocol) server.How such a time synchronization works with CENTAURI IV is described inapplication note 21 (link: www.mayah.com/content/download/pdfs/appnotes/centauri/a_n_e_021.pdf).The following parameters can be setBias:The bias is the difference, in minutes, between Coordinated Universal Time(UTC) and local time. All translations between UTC and local time are based onthe following formula: UTC = local time + biasStandard:

The standard date specifies a system time structure that contains a date andlocal time when the transition from daylight saving time to standard time occurs





on this CENTAURI IV. If this date is not specified, the month member in thesystem time structure must be zero. If this date is specified the 'day light date'value in the time zone structure must also be specified. To select the correct dayin the month set the year member to zero, the 'day of week' member to anappropriate weekday (usually Sunday), and the day member to a value in therange 1 through 5. Using this notation the last Sunday in October can bespecified (5 is equal to "the last").Daylight:

The daylight date specifies a system time structure that contains a date and localtime when the transition from standard time to daylight saving time occurs on this CENTAURI IV. If this date is not specified, the month member in the system timestructure must be zero. If this date is specified the 'standard date' value in thetime zone structure must also be specified. To select the correct day in the monthset the year member to zero, the 'day of week' member to an appropriateweekday, and the day member to a value in the range 1 through 5. Using thisnotation the last Sunday in March can be specified (5 is equal to "the last"). Save:- saves the time zone settings in the internal file 'timezone.dat' and validatesthem immediately. Otherwise changes of time zone settings becomes valid atnext start of CENTAURI IV.

4.8.6.15 G.711 Options

This dialog enables to set miscellaneous parameters for G.711 use (ISDNtelephony):


a) G.711North America/Japan and Europe use a different coding method for ISDNtelephony.Thus, the following alternatives are available:· A-law (as used in Europe – uses non linear PCM, with 13 segments)· µ-law (as used in USA and Japan – also non-linear PCM; but 15 segments)Note:If G.711 law is not set properly then strong disturbances occurs at G.711



transmissions.

b) G.711 levelSometimes G.711 signals (i.e. normal telephone signals) are over modulated andtherefore their too high audio levels can cause distortions. Therefore G.711attenuation can be set to:· 0 dB (no attenuation)· 6 dB· 12 dB

c) G.711 ISDN serviceHere the service used for G.711 calls are set. It can be selected between· Speech (default and standard)and· Telephony

4.8.6.16 Reboot

- soft reboots the CENTAURI IV by executing the direct command 'sys_reboot'. Ahard reboot can be done by using the power switch on the rear side.However, the result of soft reboot and hard reboot is the same.

4.8.7 Journal

This item shows the connections of your CENTAURI IV as listed in the internallog files· logact.txtand· logold.txtThe detailed connection info can be shown by selecting an entry with the cursor

keys and confirming the selection with the -key. Note:If you wish to delete the journal please connect to CENTAURI IV via FTP anddelete the files 'LOGACT.TXT' and 'LOGOLD.TXT'. Deleting these files via the



front panel is impossible. The FTP access data is by default:· Host: <IP-address of CENTAURI IV>· User ID: Admin· Password: PowerNote 2:Detailed log file information can be shown with help of CENTAURI IV web remoteat menu item 'SPECIAL/Log files'.

4.8.8 System Health

- informs about the system health of the CENTAURI IV.

The following parameters are shown:

a) Temp- informs about the system temperature (the temperature inside chassis of CENTAURI IV). If temperature is too high (usually > 60 °C) then an alarm israised.

b) CPU CPU performance in MHz

c) MemRAM memory in MB

d) FanRevs per minute of the CPU fan. If this value is too low then an alarm is raised.

e) Flash- indicates the capacity of the user partition of the internal CENTAURI IV Flashcard. The user partition is assigned to drive D.

f) Free- indicates the amount of free space on the user partition of the CENTAURI IVFlash card.

g) VoltagesIf one of the voltages is out of tolerances 'NOT OK' is shown and an alarm israised.

Part

VMiscellaneous



5 Miscellaneous

5.1 Other Manuals

· CENTAURI (all types) Interface Manual- describes all the CENTAURI IV audio- and communication-interfaces (e.g.ISDN, X.21, Ethernet etc.). It can be found at www.mayah.com/content/download/pdfs/manuals/centauri-interface_eng.pdf.

· CENTAURI IV Communication Reference Manual- comprises the whole CENTAURI IV command set. Furthermore, itdescribes in general how CENTAURI IV can be controlled via RS232 andIP. It can be found at www.mayah.com/content/download/pdfs/manuals/communication-reference_man.pdf.

· Web Remote 4 manual- describes the configuration and usage of various MAYAH Codecs,including CENTAURI IV via Web Remote Version 4. It can be found at www.mayah.com/content/download/pdfs/manuals/mayah-webremote_manual_eng.pdf

5.2 Most frequent ETSI ISDN Error Messages

A list of most frequent ETSI ISDN Error messages/Clear Codes (in hex):

$3301: Disconnect or broken lineISDN layer 1 failure (no ISDN line is detected). It was impossible to send andreceive message between the Mayah codec and the ISDN switching exchangesince there is no physical connection detected. Possible reasons:

- faulty ISDN cable- disconnected ISDN cable- incorrectly wired ISDN socket- incorrectly terminated network

$3302: Protocol error layer 2Failure in the data link layer. One possible reason was that the Mayah codecs’ D-channel protocol does notcorrespond to that of the ISDN switching exchange (see also menu item 'Setup/Inteface/ISDN' ).

$3303: Protocol error layer 3Failure in the network layer. One possible reason was that the Mayah codecs' D-channel protocol does notcorrespond to that of the ISDN switching exchange (see also menu item 'Setup/Inteface/ISDN' ).

$3480: Normal call clearingThis is no error! It just means that the CENTAURI IV receives a disconnect




http://www.mayah.com/content/download/pdfs/manuals/mayah-webremote_manual_eng.pdf

http://www.mayah.com/content/download/pdfs/manuals/mayah-webremote_manual_eng.pdf

113Miscellaneous


from the network according ETS 300 102-1/Q.9331.

$3481: Unallocated (unassigned) numberThis cause indicates that the destination, requested by the calling user cannotbe reached because, although the number is in a valid format, it is notcurrently assigned (allocated).

$3482: No route to specified transit networkThis cause indicates that the equipment sending this cause has received arequest to route the call through a particular transit network which it does notrecognize. The equipment sending this cause does not recognize the transitnetwork either, because the transit network does not exist or because thatparticular transit network, while it does exist, does not service the equipmentwhich is sending this cause. This cause is supported on a network-dependentbasis.

$3483: No route to destinationThis cause indicates that the called user cannot be reached because thenetwork through which the call has been routed does not serve the destinationdesired. This cause is supported on a network-dependent basis.

$3486: Channel unacceptableThis cause indicates the channel most recently identified is not acceptable tothe sending entity for use in this call.

$3487: Call awarded and being delivered in an established channelThis cause indicates that the user has been awarded the incoming call, andthat the incoming call is being connected to a channel already established tothat user for similar calls (e.g. packet-mode X.25 virtual calls).

$3490: Normal call clearingThis cause indicates that the call is being cleared because one of the usersinvolved in the call has requested that the call be cleared.

$3491: User busyThis cause is used when the called user has indicated the inability to acceptanother call.

$3492: No user respondingThis cause is used when a user does not respond to a call establishmentmessage with either an alerting or connect indication within the prescribedperiod of time allocated.

$3493: No answer from user (user alerted)This cause is used when a user has provided an alerting indication but has notprovided a connect indication within a prescribed period of time.

$3495: Call rejectedThis cause indicates that the equipment sending this cause does not wish toaccept this call, although it could have accepted the call because the



equipment sending this cause is neither busy nor incompatible.

$3496: Number changedThis cause is returned to a calling user when the called party numberindicated by the calling user is no longer assigned.

$349a: Non-selected user clearingThis cause indicates that the user has not been awarded the incoming call.

$349b: Destination out of orderThis cause indicates that the destination indicated by the user cannot bereached because the interface to the destination is not functioning correctly.The term "not functioning correctly" indicates that a signalling message wasunable to be delivered to the remote user; e.g. a physical layer or data linklayer failure at the remote user, user-equipment off-line, etc.

$349c: Invalid number formatThis cause indicates that the called user cannot be reached because thecalled party number is not in a valid format or is not complete.

$349d: Facility rejectedThis cause is returned when a facility requested by the user cannot beprovided by the network.

$349e: Response to STATUS ENQUIRYThis cause is included in the STATUS message when the reason forgenerating the STATUS message was the prior receipt of a STATUSENQUIRY message.

$349f: Normal, unspecifiedThis cause is used to report a normal event only when no other cause in thenormal class applies.

$34a2: No circuit/channel availableThis cause indicates that there is no appropriate circuit/channel presentlyavailable to handle the call.

$34a6: Network out of orderThis cause indicates that the network is not functioning correctly and that thecondition is likely to last a relatively long period of time; e.g. immediatelyreattempting the call is not likely to be successful.

$34a9: Temporarily failureThis cause indicates that the network is not functioning correctly and that thecondition is not likely to last a long period of time; e.g. the user may wish to tryanother call attempt almost immediately.

$34aa: Switching equipment congestionThis cause indicates that the switching equipment generating this cause isexperiencing a period of high traffic.

115Miscellaneous


$34ab: Access Information discardedThis cause indicates that the network could not deliver access information tothe remote user as requested; i.e. a user-to-user information, low layercompatibility, high layer compatibility or sub address as indicated in thediagnostic.

$34ac: Requested circuit/channel not availableThis cause is returned when the circuit or channel indicated by the requestingentity cannot be provided by the other side of the interface.

$34af: Resources unavailable, unspecifiedThis cause is used to report a resource unavailable event only when no othercause in the resource unavailable class applies.

$34b1: Quality of service unavailableThis cause is used to report that the requested quality of service, as defined inthe ITU-T recommendation X.213, cannot be provided (e.g. throughput ortransit delay cannot be supported).

$34b2: Requested facility not subscribedThis cause indicates that the requested supplementary service could not beprovided by the network because the user has not completed the necessaryadministrative arrangements with its supporting network.

$34b9: Bearer Capability not authorizedThis cause indicates that the user has requested a bearer capability which isimplemented by the equipment which generated this cause but the user is notauthorized to use.

$34ba: Bearer Capability not presently availableThis cause indicates that the user has requested a bearer capability which isimplemented by the equipment which generated this cause but which is notavailable at this time.

$34bf: Service or option not available, unspecifiedThis cause is used to report a service or option not available event only whenno other cause in the service or option not available class applies.

$34c1: Bearer capability not implementedThis cause indicates that the equipment sending this cause does not supportthe bearer capability requested.

$34c2: Channel type not implementedThis cause indicates that the equipment sending this cause does not supportthe channel type requested.

$34c5: Requested facility not implementedThis cause indicates that the equipment sending this cause does not supportthe requested supplementary service.



$34c6: Only restricted digital information bearer capability is availableThis cause indicates that one equipment has requested an unrestricted bearerservice but that the equipment sending this cause only supports the restrictedversion of the requested bearer capability.

$34cf: Service or option not implemented, unspec.This cause is used to report a service or option not implemented event onlywhen no other cause in the service or option not implemented class applies.

$34d1: Invalid call reference valueThis cause indicates that the equipment sending this cause has received amessage with a call reference which is not currently in use on the user-network interface.

$34d2: Identified channel does not existThis cause indicates that the equipment sending this cause has received arequest to use a channel not activated on the interface for a call. For example,if a user has subscribed to those channels on a primary rate interfacenumbered from 1 to 12 and the user equipment or the network attempts to usechannels 13 to 30 this cause is generated.

$34d3: A suspended call exists, but this call identity does notThis cause indicates that a call resume has been attempted with a call identitywhich differs from that in use for any presently suspended call(s).

$34d4: Call identity in useThis cause indicates that the network has received a call suspend request.The call suspend request contained a call identity (including the null callidentity) which is already in use for a suspended call within the domain ofinterfaces over which the call might be resumed.

$34d5: No call suspendedThis cause indicates that the network has received a call resume request. Thecall resume request contained a call identity information element whichpresently does not indicate any suspended call within the domain of interfacesover which calls may be resumed.

$34d6: Call having the requested call identity has been clearedThis cause indicates that the network has received a call resume request. Thecall resume request contained a call identity information element which onceindicated a suspended call; however, that suspended call was cleared whilesuspended (either by network timeout or by the remote user).

$34d8: Incompatible destinationThis cause indicates that the equipment sending this cause has received arequest to establish a call which has a low layer compatibility, high layercompatibility or other compatibility attributes (e.g. data rate) which cannot beaccommodated.

117Miscellaneous


$34db: Invalid transit network selectionThis cause indicates that a transit network identification was received, which isof an incorrect format.

$34df: Invalid message, unspecifiedThis cause is used to report an invalid message event only when no othercause in the invalid message class applies.

$34e0: Mandatory information element is missingThis cause indicates that the equipment sending this cause has received amessage which is missing an information element which must be present inthe message before that message can be processed.

$34e1: Message type non-existent or not implementedThis cause indicates that the equipment sending this cause has received amessage with a message type it does not recognize either because this is amessage not defined or defined but not implemented by the equipmentsending this cause.

$34e2: Message not compatible with call stateThis cause indicates that the equipment sending this cause has received amessage such that the procedures do not indicate that this is a permissiblemessage to receive while in the call state, or a STATUS message wasreceived indicating an incompatible call state.

$34e3: Information element non-existent or not implementedThis cause indicates that the equipment sending this cause has received amessage which includes information elements not recognized because theinformation element identifier is not defined or it is defined but notimplemented by the equipment sending the cause. However, the informationelement is not required to be present in the message in order for theequipment sending the cause to process the message.

$34e4: Invalid information element contentsThis cause indicates that the equipment sending this cause has received aninformation element which it has implemented; however, one or more fields inthe information element are coded in such a way which has not beenimplemented by the equipment sending this cause.

$34e5: Message not compatible with call stateThis cause indicates that a message has been received which is incompatiblewith the call state.

$34e6: Recovery on timer expiryThis cause indicates that a procedure has been initiated by the expiry of atimer in association with error handling procedures.

$34ef: Protocol error, unspecifiedThis cause is used to report a protocol error event only when no other causein the protocol error class applies.



$34ff: Inter working, unspecifiedThis cause indicates that there has been inter working with a network whichdoes not provide causes for actions it takes; thus the precise cause for amessage which is being sent cannot be ascertained.

5.3 Ancillary Data Background

a) GeneralSome audio transmissions also require the transfer of additional informationdata. This additional information data is called ancillary data or auxiliary data. Such ancillary data can be for instance RDS (= Radio Data System). TheCENTAURI IV supports the transfer of ancillary data by two ways:· Ancillary data transfer inside of the coded audio· Ancillary data transfer with help of an extra ancillary data stream (called

TS)Note:Just to prevent misunderstandings it must be emphasized that the CENTAURIIV just transport the pure ancillary data but it cannot create, encode or decodesuch ancillary data e.g. CENTAURI IV is not a RDS encoder or RDS decoder.Ancillary data inside of the coded audioSome of coding algorithms implemented in CENTAURI IV supports thetransport of ancillary data inside of the audio data stream. These codingalgorithms are:· All MPEG algorithms (i.e. MPEG L2, MPEG L3, MP3 Pro, all AAC algorithms)· All APT-X algorithmsAt MPEG algorithms the ancillary data format must be set to the followingparameters (depending on the codec on the other side):· Auto· CCS (for ancillary data compatibility to CCS codecs and if MPEG L2 bit

rates >= 192 kbps are used)· J.52· Musictaxi· Barco (especially for ancillary data compatibility to RE codecs).At APT-X algorithms the ancillary data format must be set to the followingparameters (depending on the codec on the other side):· Left· RightAdvantage:This method is supported by all communication interfaces of CENTAURI IV (e.g. IP, ISDN, X.21, V.35 etc.).Disadvantage:It just runs with the above listed coding algorithms.Note:A deeper view inside this matter is also supplied by application note 15 onMayah Website (www.mayah.com/content/download/pdfs/appnotes/centauri/a_n_e_015.pdf)

Ancillary data transfer with help of an extra ancillary data stream (called



119Miscellaneous


TS)Ancillary data can also be transported in an extra IP stream. For this theancillary data format must be set to ‘TS’. This feature is supported by systemsoftware version 3.2.0.4 (or later).Advantage:All coding algorithms supports ancillary data by TS.Disadvantages:· Ancillary data by TS just works with IP/RTP· Increase of IP overhead.

b) PortResponsible for ancillary data is the USB Interface located on the rear side of CENTAURI IV. It can be used with RS232-USB Adapter. The physicalparameters of this port can be set in menu item 'Setup/Miscellaneous/Ancillary'. Note:The physical parameters (e.g. baud rate) are just the parameters of the RS232hardware and mainly they are important for hardware connected to CENTAURI IV. However, the selected baud rate is just the max. possible onebut usually the really transmitted ancillary data baud rate is much lower.Actually reached ancillary data baud rates are listed below.

c) CableThe ancillary data cable used by CENTAURI IV is just a RS232 cross cablebut in opposite to the remote cable the handshake pins should not be bridged.Especially if the ancillary data is transported inside of the audio data and highancillary baud rates should be reached, handshake (especially RTS/CTS) isstrongly recommended.

Pin layout of CENTAURI IV ancillary data cable:

d) Max. Reached Ancillary Baud rateThe max reached ancillary bit rate (abr) depends on· how big is one ancillary data block transported in one audio frame (MPEG

algorithms) respectively in one audio block (non MPEG algorithms). Thisparameter is called ancillary block size (as) and it is measured in Bytes.



· Duration of one audio frame or block. This parameter is called frameinterval (fi) and it is measured in ms.

· how many frames respectively audio blocks are located in one IP packet.This is important since one IP packet can contain several audio frames (oraudio blocks) but just one ancillary data block. This parameter is called number of frames (nf).Just at IP this parameter is different to 1.

The ancillary bit rate bit rate is calculated to:

abr = data volume/time to get samples = (as * 8)/(fi * nf)

At MPEG algorithms the frame interval (fi) depends on the samples per frame(sf) and the sample rate (sr). It is calculated to:

fi = sf/sr=> abr = (as * sr * 8)/(sf * nf)

Furthermore at MPEG algorithms the samples per frame varies at the differentcoding algorithms:· MPEG L2, MPEG L3: 1152· AAC (MPEG 2), AAC (MPEG 4), AAC (HE): 1024· AAC (LD): 480

e) Max. Reached Ancillary Baud rate at transport inside of audio dataIt must be considered that usually audio data has got priority to ancillary data.Therefore the below listed values are just the max. ones and additionallyancillary data can also be delayed.

Table of max. reached ancillary baud rates at transport inside of audio data:

121Miscellaneous


f) Max. Reached Ancillary Baud rate at transport with help of an extra TSstreamHere the ancillary data block has got a size of 30 Byte.

Table of misc. ancillary data rates at TS format and packet size = 1 frame

g) Bit rate versus Baud rateSince often ancillary data is transported on asynchronous serial lines a start bitand stop bit must be added to every byte to reach synchronization. Thereforethe ancillary data baud rate is 20% higher than the ancillary data bit rate.

h) Configuration steps on Configuration steps on CENTAURI IV sideThe ancillary data can be set via menu item 'Setup/Miscellaneous/Ancillary'and the transmission format of Ancillary Data can be set via menu item 'Setup/Audio Encoder [Decoder]' or as part of the Codec Profile via menu item 'Presets/Profile Entry' and 'Setup/Profiles' in the Web Remote.

5.4 GPIO Interface

GeneralThe CENTAURI IV has got · Opto Input Relay Output

The Opto Input Relay Output uses a DB37 female port.

The GPIO feature of CENTAURI can be used in two different ways:· Far end switching

The states of the inputs (i.e low or high) are transmitted to outputs of the otherside CENTAURI. The transmission of these states is done inside of theancillary data transport. This feature enables to switch on/off far end devices,LEDs etc.

· Event Action ProgrammingOne of the powerful features of CENTAURI is the event actionprogramming. The event action programming allows an advanced users toadapt the CENTAURI to their needs. How event action works is generallydescribed in Application Note No. 4 on Mayah Website (www.mayah.com/content/download/pdfs/appnotes/centauri/a_n_e_004.pdf).The GPIO interfaces can also be used in event action programming. Forinstance it is possible to control special functionality of CENTAURI just byopen or close external switches. A good example for this is described inApplication Note No. 3 on Mayah Website (www.mayah.com/content/






download/pdfs/appnotes/centauri/a_n_e_003.pdf).

All the GPIO outputs can be set with the CENTAURI command ‘TTL_IO’. Thedirect commands of CENTAURI are described in the CommunicationReference Manual (www.mayah.com/content/download/pdfs/manuals/communication-reference_man.pdf).

The Opto Input Relay Output interface has got 8 inputs and 8 outputs. Its pinlayout is shown below.There are three good reasons for using the optional Opto Input Relay Outputcard:· 8 additional inputs and outputs are available for event action programming

and far end switching· The relays are capable of switching much higher loads (1A at 24V) than

the TTL outputs which can sink only 4 mA or source just 1 mA· Opto inputs and relay outputs are potential-free

Pin layout of CENTAURI IV Opto Input Relay Output interface:

Simple schematic how Opto Input works:




123Miscellaneous


5.5 Backup feature

One of the features of CENTAURI IV is the backup feature. It is implementedidentical with the CENTAURI III.

a) GeneralBackup means that CENTAURI IV establishes automatically a fail over linewhen the main line loses framing. Furthermore while fail over line is active stillthe main line is watched. CENTAURI IV switches automatically back to mainline when it reaches framing state.

In backup mode CENTAURI IV runs two sub codecs whereas the first subcodec is responsible for the main line and the last sub codec (usually subcodec 2) is responsible for the fail over line.

Since backup feature runs two sub codecs it is similar to the gateway feature.However, the main difference is that at backup the last sub codec is activewhen the first sub codec is not(!) framed whereas at gateway feature the lastsub codec is active when the first sub codec is framed.

b) Parameters to setFor Backup mode two parameters must be set:Backup timeThe backup time determines in ms how long the main line must be unframedsince it is switched to the fail over line. Furthermore the backup time is alsothe fallback time from backup connection to main connection.Backup connectionThe backup connection can be:· The last connectionor· A phone book entry (recommended)Note:To prevent that any little framing toggle causes a switching to the backup line,it is recommendable to set the backup time to minimum 2,000 ms. Thisguarantees a stable backup behaviour.Note 2:When in the backup scenario a X.21/V.35 transmission is involved then theminimum backup time must be 3,000 ms.



c) RestrictionsTheoretically any kind of transmission can be backed up with any other kind oftransmission. However, there are a few restrictions:· If the backup line uses IP then IP/RTP must be used· X.21/V.35 connections cannot be backuped with another X.21/V.35

connection· Backup mode cannot be used if gateway mode, dual codec mode or

point to multipoint (PMP) is active

d) ConsiderationsIn the following considerations it assumed that the backup line uses subcodec 2.Last ISDN B-channelsSince there is no special parameter to determine which B-channels areassigned to sub codec 1 (main line) and sub codec 2 (backup line) in backupmode the last available B-channels are automatically assigned to sub codec2. This means:· At ISDN backup phone book entries the last ISDN numbers must be used e.g.

with a bit rate of 128 kbps the numbers must be assigned to #7 and #8.· Accordingly at such backup scenario the ISDN cable must be connected to

the last S0 port of the ISDN card.Different IP ports at the sub codecsAt RTP different sub codecs use different RTP ports (see also chapter Necessary settings for framed connections/How to establish IP connections/IPPorts). However, when the backup connection should be established to subcodec 1 of another Mayah codec then the port 5004 must be used. Thereforeat the backup phone book entry the IP address must look like this: <IP-address of other side codec>:5004e.g. 88.217.252.72:5004

e) Useful hints

Independent testing of main line and backup lineIt is strongly recommended to test independently the main line connection andthe backup line connection i.e. test of both connections with inactive backupmode. However, the notes of item 3 and 4 should be considered.Backup mode on both Mayah codecsWhen backup line is established between the same two Mayah codecs whichare responsible for the main line then even on the none establishing Mayahcodec the backup mode should be switched on. The used backup phone bookentry should be identical to the one of the establishing Mayah codec but withtwo changes:· backup time should be about 1,000 ms less· no numbers or IP addresses in the backup phone book entryConfigurationThe backup mode can be configured via menu item Setup/Others.

125Miscellaneous


5.6 Gateway feature

One of the features of CENTAURI IV is the gateway feature. It's implementedidentically with CENTAURI III.

a) GeneralGateway feature of CENTAURI IV means that audio received via onecommunication interface can be rerouted to another communication interfacee.g. audio received via ISDN can be IP multicasted in a LAN.

In gateway mode CENTAURI IV runs two sub codecs. When the connection ofthe sub codec 1 is framed then the gateway connection on the last sub codec(usually sub codec 2) is established automatically.

Since gateway feature runs two sub codecs it is similar to the backup feature.However, the main difference is that at backup the last sub codec is activewhen the first sub codec is not(!) framed whereas at gateway feature the lastsub codec is active when the first sub codec is framed.

b) Parameters to setFor Gateway mode two kind of parameters must be set:Gateway connectionThe gateway connection is the connection to which the audio received by subcodec 1 is routed to.It can be:· The last connectionor· A phone book entry (recommended)Audio interfacesThe audio is internally routed via the audio interfaces. Therefore the audiooutput of sub codec 1 must be identical to the audio input of the gateway subcodec (usually sub codec 2) i.e. in case of gateway mode uses a phone bookentry the audio type of the encoder profile of this phone book entry must bethe same as the audio output of sub codec 1. Therefore very often thefollowing configuration is used:· Audio output of sub codec 1: adat12· Audio type of encoder profile of gateway phone book entry: adat12When audio should also be routed back then the audio input of sub codec 1must correspond to the audio type of decoder profile of the gateway phonebook entry.Note:The audio is routed in an non-decoded state i.e. even in gateway mode subcodec 1 first decodes the audio before it routes it to the gateway sub codec(usually sub codec 2). This means that even in gateway mode no trans codingis used and therefore every gateway audio routing means one more codinggeneration.

c) RestrictionsTheoretically any kind of transmission can be routed to any other kind oftransmission. However, there are a few restrictions:



· If the gateway sub codec uses IP then IP/RTP must be used· X.21/V.35 connections cannot be routed to another X.21/V.35 connection· Gateway mode cannot be used if backup mode, dual codec mode or

point to multipoint (PMP) is active

d) ConsiderationsIn the following considerations it assumed that the gateway sub codec is subcodec 2.Last ISDN B-channelsSince there is no special parameter to determine which B-channels areassigned to sub codec 1 (main line) and sub codec 2 (gateway line) ingateway mode the last available B-channels are automatically assigned to subcodec 2. This means:· At ISDN gateway phone book entries the last ISDN numbers must be used e.

g. with a bit rate of 128 kbps the numbers must be assigned to #7 and #8.· At a gateway scenario using ISDN for sub codec 2 the ISDN cables must

be connected to the last S0 ports of the ISDN card.Different IP ports at the sub codecsAt RTP different sub codecs use different RTP ports (see also chapter Necessary settings for framed connections/How to establish IP connections/IPPorts). This means that e.g. sub codec 2 uses port 5014 by default. However,when the gateway connection should be established to sub codec 1 of anotherMayah codec then port 5004 must be used. Therefore at the gateway phonebook entry the IP address must look like this: <IP-address of other side codec>:5004 e.g. 88.217.252.72:5004

e) Useful hintsIndependent testing of main line and gateway lineIt is strongly recommended to test independently the main line connection andthe gateway line connection i.e. test of both connections with inactive gatewaymode. However, the notes of item 3 and 4 should be considered.No ancillary data transferBy default the ancillary data is not routed together with audio.

f) ConfigurationThe gateway mode can be configured via menu item Setup/Gateway.

127Miscellaneous


5.7 Technical specifications

Analog Audio Specifications

Connections Gold-plated Neutrik® 3-pin XLR

Input: socket

Output: plug

A/D converter 24 bit sigma-delta

Sampling rates 32, 44.1, 48 and 96 kHz

Input impedance >25 kOhm, symmetrical

Output impedance <100 Ohm, symmetrical

Clipping level / output level Input: +18.0 dBu

Output: +18 dBu

Harmonic distortion <0.005% at 1 kHz

Signal-to-noise ratio >96 dB (unweighted) >99 dB (weighted)

Cross-talk attenuation >100 dB

L/R phase difference <0.5°

Coding algorithms Linear (12-24 bit)ISO/MPEG 1, 2, 2.5 Layer IIIISO/MPEG 1, 2 Layer IICCITT G.722CCITT G.711AAC (MPEG-2)AAC (MPEG-4) HE-AACv2 (MPEG-4)APT-X (standard and enhanced)FCA (MAYAH FlashCast®, low bit rate / low delayalgorithm)

optional: 4SB ADPCM

IP/Ethernet Interface Specification

Network cards 2x Ethernet 10/100/1000 (2x RJ45 or 1x RJ45 & 1xfiber optic connector)

Modes Half-Duplex, Full-Duplex, auto

Protocols SIP, RTP, UDP, SDP, RTCP, TCP, HTTP, NTP,FTP, Telnet, SNMP

Applications Separate Streaming and Control, RedundantStreaming

ISDN Interface Specification

Network Interface Cards 4x ISDN BRI (S0)

Number of B channels Up to 8

Data rates Layer III: 8 to 320 kb/s in steps of 8 kb/s

Layer II:8, 16, 24, 32, 40, 48, 56, 64, 80, 96, 112,128, 144, 160, 192, 224, 256, 320 and 384 kb/s

G.722: 48, 56 and 64 kb/s



Ancillary Data Channel (RS232)

Connector RS232 USB Adapter

Baudrate 1200, 2400, 4800, 9600, 19200, 38400, 57600 and115200 Baud

Mode 8 data bits, 1 stop bit

Handshake Not needed

GPIO interfaces

Connectors 8x Opto In/Relay Out (1x DB37 socket), 5x TTLIn/Out (1x DB25 socket)

Function Status indication, event/action scripting

Control interfaces

Front Panel Keyboard 16 keys with cursor, dial, function and status keys

Front Panel Level Meters Normal and clip LEDs

Remote control and monitoring Integrated Web Remote, Telnet, SNMP, RS232

Interfaces RS232 (USB Adapter) or IP Ethernet (RJ-45)

General

Environmental conditions

Storage temperature -40 to +70° C (-40 to +158° F)

Operating temperature 5 to +45° C (41 to +113° F)

Relative moisture 20 to 80%, non-condensing

Electromagnetic compatibility EN 55022, EN 55024, EN 61000-6

Power supply 90 to 250 VAC, 47 to 65 Hz, <60 Watt

Dimensions and weight

Height 2U (3.5 in., 8.89 cm)

Width Rack mount: 19 inches (48.26 cm)

Table version: 17,13 inches (43.48 cm)

Depth 12.99 inches (33.0 cm)

Net weight About 17.64 lbs. (8 Kg)

Index 129


Index

- µ -µ-law 107

- 2 -224.2.127.254 45

- 3 -3G/UMTS card 12

- 5 -5ess 87

- A -Activating SIP registration 90

ADAT Mastermode 86

AEQ 3001 21

AEQ 5001 21

AES/EBU Adapter 12

AES/EBU transparent 86

AETA Hifiscoop 21, 30

AETA Scoopy 21, 30

AEV Millennium 21

A-law 107

Analog Levels 85

Ancillary baud rate 104

Ancillary data 104

Ancillary Data Background 118

Ancillary Data Baudrates 118

Ancillary data bits 104

Ancillary handshake 104

Ancillary parity 104

Ancillary stop bits 104

APT-X codec 21, 37

Arrow Keys of Frontpanel 69

ASI Basics 63

Audio Decoder 83

Audio delay ip 90

Audio Destination 84

Audio Encoder 81

Audio In/out 84

Audio Levels 73

Audio routing 125

Audio Source 84

Austel 87

Auxillary Data 118

AVT Magic 21, 34

AVT Telefon 21

AVT telephone 32

- B -Backlight 95

Backup 99, 123

Backup Mode 99

BCF 37

Bias 105

Bootscript 18

Browser 16

- C -CDQ1000 21, 25

CDQ2000 21, 25

CDQ2001 21, 25

CDQ2012 21

CDQPrima 21, 25

Centronics Port 121

CF card 12

Communcation Interface 86

Compatibility list 21

Configuration network card 40

Connect 71

Connectors 9

Contrast 95

Cursor Keys of Frontpanel 69

- D -Date format 105

DCE 56, 89

D-channel depending settings 87

D-channel-protocol 87

Decoder Bit rate 83

Decoder dependency 83

Decoder format 83

Decoder mode 83

Decoder Protection 83

Decoder sample rate 83

Centauri IV Manual130


Decoder signal 83

Decoder Status 74

Decoder stream 83

Decoder type 83

Default IP settings 14

Delete Phonebook Entry 76

Delete Profile Entry 80

Delete Session Entry 75

dialtone 87

Disconnect 71

Disconnect timeout 102

DMB 74

DNS Server 90

Domain Name System 90

Download firmware 16

DRT128 37

DSS1 87

DTE 56, 89

DTE versus DCE 56

DTE/DCE 56

DTS 48

Dual Ethernet 14

Dual IP 14

Dual mode 98

Dualmode 98

Duplex mode 90

Duplex mode adaption 52

- E -EBU N/ACIP 46

Edit Phonebook Entry 76

Edit Profile Entry 80

Edit Session Entry 75

emergency USB stick 18

Encoder bandwidth 81

Encoder Bit rate 81

Encoder dependency 81

Encoder format 81

Encoder mode 81

Encoder Protection 81

Encoder sample rate 81

Encoder signal 81

Encoder Status 74

Encoder stream 81

Encoder type 81

Environment and Operational Conditions 8

- F -Factory Default 101

Factory defaults 18

Failover 99, 123

FEC 14, 53

FEC mode 72

Firmware 101

Firmware update 16

FlashCast technology and different kind of codecs 20

Forward Error Correction 53

Frontpanel Backlight 95

Frontpanel Contrast 95

Frontpanel language 100

Frontpanel LED'S 66, 67

Frontpanel Preface 66

FTP access 15, 68

Function Keys of Frontpanel 69

- G -G.711 attenuation 107

G.711 law 107

G.711 options 107

G.711 service 107

G.722 SRT timeout 102

Gateway 90, 99, 125

General Purpose Input/Ouput 121

Get dialtone 87

Glensound G.722 codec 33

Glensound GSGC6 37

GPIO 121

- H -Headphone source 96

Headphone volume 96

Hot Keys of Frontpanel 68

How to get a framed ISDN connection to a APTcodec 37

How to get a framed ISDN connection to aGlensound G.722 codec 33

How to get a framed ISDN connection to a MAYAHISDN codec 23

How to get a framed ISDN connection to a normaltelephone 36

How to get a framed ISDN connection to AETAHifiscoop/AETA Scoopy/You Com Set 2 30

Index 131


How to get a framed ISDN connection to AVT Magic 34

How to get a framed ISDN connection to AVTtelephone 32

How to get a framed ISDN connection toCDQPrima/CDQ2000/CDQ20017Telos Zephyr 25

How to get a framed ISDN connection to MAYCOMEASYCORDER 35

How to get a framed ISDN connection to MusictaxiVP 29

How to get a framed ISDN connection to MusictaxiVP Pro 28

How to get a framed ISDN connection to SendIt 25

How to get a framed ISDN connection to TelosXstream 27

- I -ID 87

Identification 101

Interface 72

IP 90

IP Address 90

IP audio delay 90

IP Overhead 48

IP packet size 14, 90

IP packetsize mode 90

IP Ports 14, 48

IP-Address 90

ISDN 87

ISDN compatibility list 21

ISDN error $3301 112















ISDN error $349a 112

ISDN error $349b 112

ISDN error $349c 112

ISDN error $349d 112

ISDN error $349e 112

ISDN error $349f 112

ISDN error $34a2 112



ISDN error $34aa 112

ISDN error $34ab 112

ISDN error $34ac 112

ISDN error $34af 112

ISDN error $34b1 112



ISDN error $34ba 112

ISDN error $34bf 112

ISDN error $34c1 112




ISDN error $34cf 112

ISDN error $34d1 112







ISDN error $34db 112

ISDN error $34df 112

ISDN error $34e0 112







ISDN error $34ef 112

ISDN error $34ff 112

ISDN Error messages 112

ISDN-protocol 87

- J -Jate 87

Jitter compensation 52

Journal 108

- K -Key Control 71



Keycodes 17

- L -Language 100

Last connection 71

Level LED's 66

Level Status 73

Levelmeter mode of frontpanel 96

Lines Status 74

Log Files 108

- M -MAC address 101

Mask Display 71

MAYAH codec (DTE) to another x.21/V.35 codec 59

MAYAH codec (DTE) to MAYAH codec (DCE) viacrossover cable 61

MAYAH codec (DTE) to MAYAH codec (DTE) 56

mayah-command-scripts.txt 18

MAYCOM EASYCORDER 21, 35

MPEG Transport Stream 48

MPEG TS 48, 74

MPEG TS sessions 74

MSN 87

Multicast RTP 41

Multiple subscriber number 87

Multipoint 98

Musictaxi VP 21, 29

Musictaxi VP Pro 21, 28

- N -Name 101

Netmask 90

Network 90

Network card 90

Network interface 90

Network Transferrate 90

New Phonebook Entry 75

New Profile Entry 76

New Session Entry 74

New start 108

NI1 87

Nica128 37

Nica64 37

NTP 105

Numeric Keypad of Frontpanel 70

NXL 37

- O -Optical Inputs 121

Optimize IP Connections 52

Optional algorithms 17

Other manuals 112

- P -packetsize 90

Packetsize adaption 52

Packetsize mode 90

Parallel Port 121

Parity 104

PBX 87

PC card FTP access 15

PC memory card 12

PCR 48

Phoebook 72

PID 48

PKI Telefon 21

PKI telephone 32

PMP 98

Point-to-Multipoint 98

Predial No. 87

Preface 8

Prodys Pronto 21

Prolink/DSM100 37

PSI 48

PTS 48

- Q -Quicktime 42

- R -Rack mount kit 12

RE 661 21

Reboot 108

Redial 71

Redundant power supply 12

Relay Outputs 121

Remote Control 16

Reset 18

rfc 2327 42

Index 133


rfc 2733 53

rfc 2974 45

rfc 3261 46

rfc 3550 40

Roadrunner 21

RPSU 12

RS232-USB Adapter 12

RTP (Multicast) 41

RTP (Unicast) 40

- S -S/N 101

Sample rate converter 86

SAP 45

SAP streaming 45

Scope of Delivery 8

Scripts 68

SD card FTP access 15

SD memory card 12

SDHC memory card 12

SDP 42

SDP streaming 42

Security 94

SendIt 25

Serial number 101

Session 72

session announcement protocol 45

Session description protocol 42

Session initiation protocol 46

Sessions 74

SIP 46

SIP Global Proxy 90

SIP ID 90

SIP Registrar 90

SIP registration access name 90

SIP registration access password 90

SIP registration access phonenumber 90

SIP registration activation 90

SIP registration profile 90

SIP STUN Server 90

SNMP Manager 90

Software versions 101

SPID 87

SRC switch off 86

Status LED's 67

Sub codec 97

Subcodec 14, 48, 73, 97

Subnet mask 90

System Health 109

System reset 18

System software version 101

- T -Technical specifications 127

telephone hybrid 21, 36

Telos Xstream 27

Telos Zephyr 25

Time outs 102

Time settings 105

Timeouts 102

TOS 52

Transfer rate adaption 52

TS 118

TTL I/O 121

TTL Input/Output 121

Type of Service 52

- U -Unicast RTP 40

Update firmware 16

USB stick FTP access 15

USB storage media 12

Useful Accessories 12

Useful hints 14

- V -V.35 89

V.35 connection 56, 59, 61

Versions 101

VLC media player 42

VN4 87

- W -Web Remote 16

WLAN card 12

WorldNet Chicago 37

WorldNet Milano 37

WorldNet Rio 37

WorldNet Tokyo 37

- X -X.21 89



X.21 clocking 55

X.21 connection 56, 59, 61

X.21 versus V.35 55

- Y -You Com Reporter Set 21

You Com Set 2 21

You Com Set2 30

Centauri IV Manual - Home - MAYAH Communications · 14 Centauri IV Manual Copyright: 2008-2014...

Documents

Transcript of Centauri IV Manual - Home - MAYAH Communications · 14 Centauri IV Manual Copyright: 2008-2014...