9-20
41-001343-01 Rev 02, Release 3.2.2
Why does my phone display the “No Service” message?
The phone displays the “
No Service
” message if the SIP settings have not been set up correctly.
The Registrar server could be set to 0.0.0.0. A global value of 0.0.0.0 disables registration.
However, the phone is still active and you can dial using username@ip address of the phone.
The phone displays "
No Service
".
If the Registrar IP address is set to 0.0.0.0 for a per-line basis (i.e, line 1, line 2, etc.), then the
register request is not sent, the "
No Service
" message does not display, and the message waiting
indicator (MWI) does not come on.
Check that the "
Registrar Server
" IP address in the Aastra Web UI at
Advanced
Settings->Global SIP
is correct.
Check the "
sip registrar ip
" parameter in the configuration
files is correct.
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.