Specifications

Configuring Application Servers
4 – 2 ShoreTel, Inc.
• Maintenance—The system provides a web site accessible through ShoreWare
Director for maintenance of all the remote servers.
The distributed voice applications use a Remote TAPI Service Provider that relies on
the call control information from the main server. When you want to add reliability to
your remote server, consider using redundant network paths to the main server.
Distributed Voice Mail
The ShoreTel system uses Distributed Voice Mail (DVM) to provide greater voice mail
availability. Each ShoreWare remote server has an instance of the telephony platform
included, allowing voice mail and auto-attendant services to maintain full functionality
during WAN short-term outages. The enhanced DVM included with the ShoreWare
remote server allows users with mailboxes on the remote server to receive and pickup
voice mail messages without depending on WAN connectivity to the headquarters
server. The message waiting indicator (MWI) lights will correctly update with or
without WAN connectivity.
Additionally, incoming calls can still reach the automated attendant, access the dial-by-
name directory, and reach their intended local party during a WAN outage. If a party
cannot be reached directly due to a WAN outage and his or her call handling would
send unanswered calls to voice mail, the call is handled by the local voice mail server.
The caller hears a generic greeting including the intended party’s recorded name and
can leave a message. This message will be forwarded at a later time to the home voice
mail server for the addressee via SMTP.
Similarly, the enhanced DVM provides greater PCM availability during WAN outages. If
the WAN loses connectivity, users will retain full PCM functionality as long as there is a
DVM server at the same site as the users, the users voice mailboxes are on that server,
and the DVM server is managing the switch that manages the users’ phones.
Although each voice mail server is autonomous in delivering voice services, it still must
have connectivity to the configuration data stored on the headquarters server in order
to make configuration changes. Specifically, users on an isolated remote server would
not be able to change call handling modes or make other changes that require
modification to the configuration data on the headquarters server.
IP Phone Limitations/Requirements
Connectivity is required between the phone and the switch that is controlling the
phone (this will be referred to as “basic connectivity”). All aspects of the phone's
operation are functional when this basic connectivity exists, with the following
exceptions:
• Directory feature: In addition to basic connectivity, the directory feature also
requires connectivity between the switch and a headquarters (HQ) server or
distributed voice mail (DVM) server that controls that switch.
• Options features, Changes to Call Handling Mode (CHM), Wrap-Up: In addition
to basic connectivity, these features require connectivity between the switch and
an HQ server or DVM server that controls that switch. In addition, if the
aforementioned switch is a DVM server, connectivity is required between that
server and the HQ server. Further, connectivity between the DVM server and the
HQ server is required for successful writes to the database.
• Switch-to-switch extension monitoring: This condition exists when a
programmed button requires monitoring activity on an extension that is serviced
by a different switch than the one that controls the phone. In this instance, call the
user's switch A, and the monitored extension's switch B. Switch A is controlled by
server X, switch B is controlled by server Y. Servers X and Y may each be DVM or