Table of Contents
Advertisement
Avaya 1692 IP Conference Phone
Appendix E: Troubleshooting
If the 1692 connects to the defined file server, the reboot time will only take two minutes. If it
cannot connect to the file server, the reboot time will take 10 minutes.
Prior to Software release R1.1, configured values from factory testing were not cleared from
cache memory and may be seen. As such during a call server address discovery the previously
cached address may be seen, for example 30.60.0.202
If the 1692 display shows Discovering 30.60.0.202, this means the 1692 cannot find the ACM and
therefore reboots every 10 minutes. If using DHCP, update the ACM IP address. If the 1692 was
configured statically, update the IP address in the Call Server menu.
If displayed values differ from statically configured values or values contained in the DHCP
scope, the 1692 may have loaded the settings from cache memory stored from the last
successful power up/Avaya Communication Server registration.
When the DHCP x seconds screen displays, the 1692 has not yet found the DHCP server to
request an IP address. If using DHCP determine why the phone is not able to access the DHCP
server. If using static configuration, configure the phone IP address per instructions in the static
configuration section of this document.
The Error loading [MAC address] message shown below may occur if the 1692 phone cannot
connect to the configured file server. Enter the correct file server information as given in the static
configuration instructions above or determine why 1692 is not able to access the file server.
DHCP settings are loaded before the "Press * to program" option is displayed. This may explain
why configuration values are seen in the "Press * to program" menu straight out of the box or
after restoring factory defaults.
Issue 1, September 2010
Installation, Configuration and Software Upgrade Guide
30
Advertisement
Table of Contents
