Codec Tieline Gateway, Руководство пользователя

Страница: 46 / 306

46 Gateway and Gateway 4 Manual v1.2
© Tieline Research Pty. Ltd. 2021
How does it work?
Using a simple HTML5 web-browser interface, engineers can log in and register their codecs with
TieLink. Simply name your codec (e.g. BAYFM Studio A) and complete the registration details.
Once registered, a codec will automatically connect to TieLink each time it connects to the internet:
1. TieLink automatically detects a codec’s IP address and NAT routing information. Seconds
later the codec address book populates with all codecs in the network, or a subset of
codecs in an authorized call-group.
2. The registered codec will appear in the address books of all other codecs registered with
TieLink and connected to the internet. Call-groups can be created to customize the number
of codecs visible to users and engineers within large networks.
3. Users can easily view the online or offline status of all codecs in a group and whether it is
connected or disconnected.
Manage Call Groups Easily
Whether you are running a large network with hundreds of IP codecs, or a small station with just a
few, the TieLink Traversal Server and Toolbox software makes connecting over IP networks a simple,
no-fuss task for non-technical broadcast personnel.
For networks with large numbers of devices, it is easy to create sub-groups and configure a codec
to follow a specific group, e.g. news or sports. All of the codecs in your network are secure and
cannot be seen by other users unless they have permission to join the network, or a specific codec
call-group. See Configuring TieLink Settings for more information.
Programs
A Program configures a Tieline codec to send or receive one or more Audio Streams based upon
the particular application the codec is being used for at any given time. The attributes of the audio
stream and associated connections are embodied within a program when it is created, including the
configuration, dialing and answering parameters. By default, Tieline codecs send proprietary session
data when connecting to each other in order to establish, manage and terminate connections. When
a connection between two codecs is established:
1. The dialing codec sends session data including information about how the codec receiving
the call should be configured.
2. Once the answering codec receives session data it sends an acknowledgment to the dialing
codec and streaming can commence.
For example, if you configure a stereo program on the dialing codec using Opus encoding at
128kbps with specific jitter settings, this will be configured on the dialing codec when it connects. It
is also possible to
lock a loaded program in a codec to ensure the currently loaded program cannot
be unloaded by a codec dialing in with different program settings. For example, if your routing
requirements require the codec at the studio to always connect in mono, simply load and lock a
mono program in the codec. Generally programs will be up or down-mixed by the answering codec
to match the loaded program type where possible. In some situations incompatible program types
will be rejected.
Defining Audio Streams within Programs
Each audio stream within a program can be defined separately and contain a variety of settings
relating to the number of connections (e.g. primary and backup) and the number of destinations to
which each audio stream is distributed. Each audio stream is capable of being configured to include