Avaya 3616 Installation And Configuration Manual page 41

Message
No SVP Response
No SVP Server
Not Installed!
Press End Call
Server Busy
SVP Service Rej.
System Locked
(with Busy Tone)
System Busy
(with Busy Tone)
555-301-107, Issue 1
July 2003
Description
The Avaya Voice Priority Processor is
not responding to requests from the
Wireless Telephone.
Wireless Telephone can't locate
Avaya Voice Priority Processor
Avaya Voice Priority Processor is not
working
No LAN connection at the Avaya
Voice Priority Processor
A required software component is
missing
Your call has ended
Wireless Telephone is attempting to
download from a TFTP Server that is
busy downloading other devices and
refusing additional downloads.
The Avaya Voice Priority Processor
has rejected a request from the
Wireless Telephone
Avaya Voice Priority Processor is
locked
Avaya Voice Priority Processor is
busy or out of resources
3616/3626 Wireless IP Telephone
Installation and Configuration Guide
Action
This may be caused by bad radio
reception or a problem with the
Avaya Voice Priority Processor. The
Wireless Telephone will keep trying
to fix the problem for 20 seconds,
and the message may clear by
itself. If it does not, the Wireless
Telephone will restart. Report this
problem to the system administrator
if it keeps happening.
IP address configuration of Avaya
Voice Priority Processor is wrong or
missing.
Check error status screen on Avaya
Voice Priority Processor.
Verify Avaya Voice Priority
Processor connection to LAN.
Check that all required software
files are on the TFTP server, if over-
the-air downloading is being used.
If the error repeats, contact Avaya
Technical Support.
Press the Power Off / End Call key
to return to standby mode.
None, the Wireless Telephone will
automatically retry the download
every few seconds.
The Wireless Telephone will restart
and attempt to re-register with the
Avaya Voice Priority Processor,
which should fix the problem.
Report to your administrator if it
keeps happening.
Try the call again later, system has
been locked for maintenance
All call paths are in use, try the call
again in a few minutes.
41