VOIP-500
Series Phone
Configuration and Operation Manual
Page
63
of
90
Copyright 2012 Talk-A-Phone Co.
• 7530 North Natchez Avenue • Niles, Illinois 60714 • Phone 773.539.1100 • [email protected] • www.talkaphone.com.
All prices and specifications are subject to change without notice. Talk-A-Phone, Scream Alert, WEBS and WEBS Contact are registered trademarks of Talk-A-Phone Co. All rights reserved.
Appendix B: Troubleshooting & Maintenance
Problem
Possible Causes & Corrective measures
Unable to access the
phone’s Web GUI
1.
The IP address being used in the Web browser is incorrect. Connect the
serial console and check the phone’s IP address.
2.
IP address of the phone is conflicting with another network device. Reassign
a new IP address to the phone.
3.
The phone’s Web server is not responding. Reboot the phone.
Unable to login to
the phone’s Web GUI
1.
The phone’s database is corrupt. Reset to factory default settings using the
Reset
button (Refer to
Error! Reference source not found.
Error!
ference source not found.
).IP address of the phone is conflicting with
another network device. Reassign a new IP address to the phone.
“
Call Placed
”
and
“Call Received”
LED
’s
are constantly
blinking
1.
The p
hone’s Ether
net link is down. Check the Ethernet connection.
2.
The phone is unable to register to a SIP Registrar. Check SIP settings.
3.
A firmware upgrade is in progress. Wait until the process is complete.
Unable to make
outgoing calls
1.
The Phone is not on the network. Check network settings.
2.
The destination is not reachable. Check SIP settings.
Unable to receive
incoming calls
1.
The Phone is not on the network. Check network settings.
2.
The Phone is off-hook. Check the hook switch status.
Not able to recognize
the DTMF codes
from remote side
1.
The p
hone’s DTMF settings are not compatible with remote side. Check the
DTMF settings of the remote side. It should be RFC 2833 compliant.
2.
The DTMF digit duration of the phone is not compatible with the remote
phone. Check the DTMF settings at the remote side. It should be RFC 2833
compliant.
