IP Phone Release Notes 2.3
New Features in Release 2.3
Certificate Validation
Certificate validation is enabled by default. Validation occurs by checking that the certificates are well formed and signed by one of the certificates in the trusted certificate set. It then checks the expiration date on the certificate, and finally, compares the name in the certificate with the address for which it was connected.
If any of these validation steps fail, the connection is rejected. Certificate validation is controlled by three parameters which you can configure via the configuration files, the IP Phone UI, or the Aastra Web UI:
•https validate certificates - Enables/disables validation
•https validate hostname - Enables/disables the checking of the certificate commonName against the server name.
•https validate expires - Enables/disables the checking of the expiration date on the certificate.
User Interface
Certificate Rejection
When the phone rejects a certificate, it displays, "Bad Certificate" on the LCD.
Configuring HTTPS Server Certificate Validation via the Configuration Files
Use the following parameters to configure HTTPS server certificate validation for the IP Phones using the configuration files.
Parameter– | Configuration Files | aastra.cfg, <mac>.cfg |
https validate certificates | IP Phone UI | |
|
| Configuration |
Validate Certificates |
| Cert |
(in Web UI) | Aastra Web UI | Advanced |
|
| |
Description | Enables or disables the HTTPS validation of certificates on the phone. | |
| When this parameter is set to 1, the HTTPS client performs validation on | |
| SSL certificates before accepting them. | |
| Note: If you are using HTTPS as a configuration method, and use a self | |
| signed certificate, you must set this parameter to “0” (disabled) before | |
| upgrading to Release 2.3 of the IP Phones. | |
|
|
|
Format | Boolean |
|
|
|
|
Default Value | 1 (enabled) |
|
|
|
|
Range | 0 (disabled) |
|
| 1 (enabled) |
|
|
|
|
Example | https validate certificates: 0 |
|
|
|
|
24 |
