CHAPTER 2 |
30
INSTALLATION AND CONFIGURATION
STUDIO NAME
allows you to name the studio. This is the name that will show up in the lists available in the VSets, Consoles
and VX show profiles.
AUTO ANSWER FIXED LINES
enables auto answer for fixed lines in the studio. When this is enabled, fixed lines will be
automagically placed on its corresponding hybrid after the first ring. Because end-of-call messaging occurs when the caller
hangs up and the VX responds accordingly to these signals, auto-answered fixed lines can theoretically be completely
unattended. This is extremely useful with IFB and Intercom applications.
LOCKLESS CONFERENCING
refers to Selectable lines. Checking this box bypasses the traditional telos “button mashing”
workflow by allowing the user to conference lines without locking them first.
When a number is entered into the
FIXED CHANNELS
and
SELECTABLE CHANNELS
fields (and click apply), you’ll see a
set of fields appear to configure these channels. Whenever we say the word “hybrid,” one of these FIXED or SELECTABLE
CHANNELS is what we are talking about. Enter the name you would like to use for the hybrid in the
NAME
field. The
CHANNEL
field is where the Livewire channel number or the AES67 multicast address is entered. The drop-down box allows
you to specify between Livewire Live Stereo, Livewire Standard Stereo, or AES67 Multicast streams. The
ENABLE
checkbox
activates or deactivates the hybrid.
ADVANCED RECIEVE
activates a field where you can enter a Livewire channel number or AES67 multicast IP address for
audio being sent back to the caller. This is for setting up a manual mix-minus or backfeed to the caller. In a typical Axia
environment, the console engine will automatically create and send the VX backfeed audio (to the caller) to the VX engine
using the same channel as the VX source (from the caller). In this case, the Advanced Receive checkbox remains unchecked.
However, if you want to connect the VX to another brand console via an xNode, check the box. “From source” should be
selected at the dropdown box and enter the LW channel number of the desired xNode source. This is the audio that goes
back to the caller, it should be a Mix-Minus or “clean feed” (in other words, the caller’s audio is not being sent back to the
caller via the VX).
Note that when you assign Livewire channels to outputs, Livewire streams will start to flow on the LAN network port. Livewire
streams system and network consume resources as soon as they are defined with a type and channel number.
It is suggested that you assign Livewire channel numbers according to App-note “Livewire Channel
numbering. Livewire channels must be unique and should not start with “1, 2, 3...”. Channel
numbering is completely flexible, but we recommend to always use the last byte of the device’s IP
address as the first 3 digits of that device’s output stream numbers. For example, if our VX’s IP
address is 192.168.2.200, the first channel in the first studio will be 20001. This way, you can always
be sure what the IP address of the device is that is creating a stream on a specific channel number.
Remember that in a Livewire environment, Livewire channels carry audio in two directions, so both send and receive are
covered at once. ‘Live Stereo’ should usually be chosen as the Mode to keep the delay as low as possible. Standard stereo or
mono can be used for Program on Hold or IFB feeds where a few extra ms of delay is inconsequential.
PROGRAM ON HOLD
is the audio a caller will hear when placed on hold from the VX in this studio. Since only one of the two
Livewire audio directions is needed, you can choose which is appropriate for your studio set-up. From Source is the usual. In
most situations, the program on hold is the feed from the consoles main program buss.
You must configure a Program on Hold feed for each studio. It could be a generic program or air feed
but if no working channel is assigned calls on hold may drop after 30-60 seconds. This is due to the
fact that some PBXs, Trunks, and some endpoints will hear silence and will disconnect thinking the
call was lost. It’s also a “best practice” to feed Program on Hold feeds “Pre-Delay” to minimize
confusion for those on hold.
