T A L K S W I T C H I N S T A L L A T I O N
2 5
Figure 26: System Information window
1.9.6 Optimizing the system for networked use
TalkSwitch units have been designed to operate optimally when in a
networked state. Below are a few items that have been designed for better
network use.
Configuration settings
All units are cloned with identical settings. If a unit has disappeared off the
network (adapter unplugged, LAN disconnected, LAN failure, etc.), the
system can still handle the calls since it retains the configuration settings of
the missing unit. If an extension or a voice mailbox cannot be reached, the
caller hears a system prompt:
“The extension you are trying to reach is
currently unavailable, please try again later.”
Outgoing line hunt groups
When two or more units are on a LAN, the system tries placing calls out on
the same unit the call originates from. This avoids using a line across the
LAN on another unit, which helps to minimize the LAN traffic and optimizes
the opportunity for all inbound calls to connect across the LAN if required.
Auto attendants
There are a total of nine auto attendants that are shared by all units on the
LAN. When an auto attendant is recorded on any unit, it is automatically
copied to all other units on the LAN. This design minimizes LAN traffic and
provides functionality back-up in case a unit or units have disappeared off
the network (adapter unplugged, LAN disconnected, LAN failure, etc.). In
this event, all units can still answer inbound calls with the same auto
attendant messages.
Voicemail
All local extension and remote extension voicemail data is stored on the
unit where the extensions normally reside. For example, all greetings,
directory names and voicemail messages for extensions 121-128, 220-229
and mailboxes 420-429 are stored on the unit with unit ID 2. If a unit is