Codec Tieline Gateway User Manual page 146

146 Gateway and Gateway 4 Manual v1.2
Important Notes:
· When a connection is dialed Tieline codecs normally use session data to configure
settings like the algorithm, connection bit rate and sample rate etc. Multicast
connections do not use session data and it is imperative that all codecs are configured
with the same connection settings prior to connecting, or they will not be able to join
multicast streaming sessions.
· Automatic or fixed jitter buffer settings can be adjusted on individual client codecs as
required. There is no jitter buffer setting on the server codec because it never receives
audio packets.
Multicast Server versus Multicast Client Programs
Two different types of multicast programs need to be created when multicasting:
· A multicast server program is used by the broadcasting codec to send multicast IP packets
to multicast routers on a network.
· A multicast client program is used by codecs to receive multicast IP audio packets.
A multicast server codec sends audio packets only and a multicast client codec receives audio
packets only. Codecs using the client program request multicast packets (sent from the server
codec), which are distributed by multicast routers.
Creating Multicast Server Programs
Important Notes: Before you start program configuration please note:
· Ensure all connection related settings like the port, algorithm, bit rate (etc) match on
both multicast server and client programs or they will not connect successfully.
· You cannot edit a program when it is currently loaded in the codec.
Lock a loaded custom program
·
cannot be unloaded by a codec dialing in with a different type of program. For
example, if a multistream program is not locked it will be unloaded by a mono or
stereo call.
· Some drop-down menus and settings may be greyed out intentionally depending on
features available.
· It is possible to save a program at several points throughout the program wizard and
use default settings to save configuration time.
· Always dial the multicast server codec connection first before connecting multicast
client codecs.
· Multicast client codecs will display return link quality (LQ) only. The Return reading
represents the audio being downloaded from the network locally. Multicast server
codecs do not display LQ readings.
· The default UDP audio port setting is 9000 for the first multicast, 9010 for the second
multicast and 9020 for the third multicast, and so on. E.g. if a client codec wishes
to receive multicast audio stream 2 then it must use audio port 9010. Default Tieline
Audio Stream ports are outlined in
· Use firmware higher than 2.8.xx in the Bridge-IT, Genie and Merlin families of codecs to
transmit auxiliary data.
· Relay functionality is available for multicast connections between Tieline codecs.
· It is not possible to connect to a G3 codec and receive multicast IP audio streams.
1. Open the HTML5 Toolbox Web-GUI and click Connect in the Menu Bar, then select Program
Manager to launch the Program Manager panel.
2. Click the New Program button to open the wizard and:
· Click in the text box to name the new program.
· Click the Mix drop-down arrow to associate a custom matrix mix with the program if required.
· Select a preferred Multicast Server program for the options available.
or multistream program in a codec to ensure it
Default Program Ports.
© Tieline Research Pty. Ltd. 2021