Aastra Telecom 41-001343-02 ユーザーズマニュアル

ページ / 876
Troubleshooting Solutions
 
9-13
41-001343-02 REV04 – 05.2014
Why does my phone display "Bad Encrypted Config"?
The IP phone displays "Bad Encrypted Config" because encrypted configuration files are enabled but the decryption 
process has failed. Specific cases where decryption fails are:
Reason
The site-specific password in security.tuz does not match the password used to encrypt the <mac>.tuz or aastra.tuz files.
Fix
Encrypt the .cfg files to .tuz using the correct password, or replace the security.tuz with the correct encrypted file.
Reason
Neither of the <mac>.tuz and aastra.tuz files are present on the configuration server (TFTP/FTP/HTTP).
Fix
Create the encrypted files using anacrypt.exe and copy them to the configuration server.
Reason
The encrypted <mac>.tuz or aastra.tuz file is encrypted using a different version of anacrypt.exe than the phone 
firmware.
Fix
Run "anacrypt.exe -v" and confirm that the correct version is reported, compared to the phone firmware version.
Why is my phone not receiving the TFTP IP address from the DHCP Server?
For DHCP to automatically populate the IP address or qualified domain name for the TFTP server, your DHCP server must 
support Option 66. Option 66 is responsible for forwarding the TFTP server IP address or domain name to the phone 
automatically. If your DHCP server does not support Option 66, you must manually enter the IP address or qualified 
domain name for the TFTP server into your IP phone configuration.
Additionally, the phone may not be receiving the TFTP IP address if there are other DHCP servers within the same broad-
cast domain providing different Option 66 (TFTP server) settings. See 
 for more information on 
option precedence.
For procedures on configuring the TFTP server using the IP phone UI and the Aastra Web UI, see Chapter 4, the section, 
on
For specific protocol parameters you can set in the configuration files, see Appendix A, the section,