Swapping/Adding/Deleting Avpps - Avaya 3641 Installation, Configuration And Administration

Part A: Avaya Voice Priority Processor
4.

Swapping/Adding/Deleting AVPPs

Whenever an AVPP is removed from the system, Wireless IP Telephones that are using the
AVPP will be affected and calls may be lost. If the removal of the AVPP is intentional, the
administrator should lock and idle the system prior to removing an AVPP.
Load balancing enables a locked AVPP Server to distribute idle handsets to

other AVPP Servers in the cluster. Existing calls will not be interrupted and the
AVPP Server will become idle once all calls are ended and idle phones are
transferred to another AVPP Server.
Adding an AVPP
A new AVPP is detected within two seconds of being added to the system
(booted/configured/connected). When detected, any Wireless IP Telephone not active in a
call will eventually be forced to reboot and check in again. Any Wireless IP Telephone in a
call will immediately switch to the AVPP that should provide its "timing" function. This
switch should not be noticeable to the user since it is similar to a normal handoff between
access points. When the Wireless IP Telephone ends the call, it will eventually be forced
to reboot and check in again. Only a few handsets at a time are rebooted to prevent
excessive check in traffic on the network. Handsets scheduled to be rebooted can still
make calls and will be rescheduled for reboot when the call is ended.
Removing an AVPP
The preferred method for removing an AVPP Server from an active system is to first lock
the AVPP Server. When an AVPP Server is locked for removal from the system, load
balancing enables the locked AVPP Server to distribute idle handsets to other AVPP
Servers in the cluster. Active calls will not be interrupted. The locked AVPP Server will
become idle once all calls are ended and idle handsets are registered to other AVPP
Servers. Once all handsets have been moved---as evidenced by the number of Telephones
in Use on the Network Status screen---the idle AVPP Server may be unplugged and removed
from the system.
During this process, there is a short period where a handset registered on a locked AVPP
Server may attempt to initiate a call before it is re-registered to another AVPP Server on a
locked AVPP Server. In this case, if there is an unlocked AVPP Server in the cluster, the
AVPP Server will tell the handset to reboot. As it reboots, the handset will check-in with
an available AVPP Server and the user may then start a call. Handsets registered on
unlocked AVPP Servers are not affected.
Of course if a system only has one AVPP Server, no calls will be possible until the removed
AVPP Server is replaced.
AVPP Server failure
If an AVPP Server becomes unable to manage calls or fails, any handset in an active call
registered to that AVPP Server loses service (and any calls) and will reboot within 30
seconds. However, upon initiating a new call, the handset will locate another Server and
will be able to make new calls. After rebooting, the handset will register with another
AVPP (if there is one available) and be able to make new calls. Handsets not registered on
the failed AVPP may experience a few seconds of disruption in audio but are otherwise
unaffected.
28 Avaya Voice Priority Processor, Avaya 3641/3645 Wireless IP Telephone, Handset Administration Tool