Line Hunt Call Answering - Tieline Merlin PLUS User Manual

124 Merlin PLUS User Manual v2.0
Fuse-IP Enabled & no tunnel created
8. Double-check all settings on both the server and client codecs if the message Started,
dialing server... persists after turning Fuse-IP On.
Important Notes:
·
Data is sent by the codec over the newly created 'tunnel' as soon as Fuse-IP is
enabled, even if a connection has not been configured and dialed. Depending on the
number of interfaces being used, the codecs may transmit and receive up to 24MB of
data per hour at each end of the link.
·
The codec remembers the Fuse-IP enabled/disabled state on power up.
·
For additional stability it is recommended that a fixed jitter buffer is configured when
streaming using Fuse-IP. The actual jitter buffer depth should account for the difference
in delay between the interfaces and the maximum jitter experienced. To determine the
jitter over each link you can connect and stream audio over each interface separately
and look at the jitter reading displayed on the Connection Statistics screen.
·
Use a dotted quad IPv4 address when configuring the Fuse-IP Server Address.
23.4

Line Hunt Call Answering

The codec supports line hunt call answering, whereby you can create line hunt groups for multiple
incoming callers on a first come, first served basis. This is ideal for separating groups of inputs and
outputs between different studios or stations.
As an example, when creating a program which supports connecting six mono audio streams,
select Line Hunt as the routing type. Then select Group 1 for the first three audio streams, to
route outgoing and incoming calls via inputs and outputs 1 to 3. These physical inputs and outputs
on the codec can be routed to a particular studio or station.
Fuse-IP enabled & tunnel created
© Tieline Pty. Ltd. 2017