...
In both cases the goal is to avoid MITM (Man In The Middle) attacks and simply to identify the server's identity without possible mistakes. In case number 1 the certificate identifies the server in order to Administration Web Interface. In case number 2 Asterisk or 2 it works the same way for the Secure VoIP service.
So we need to install a proper certificate for the HTTPS interface's hostname and then we have to bind it to the HTTPS service to in order to have a "closed padlock" web connection without warnings or exception to be added by the user.
Quite the same behaviour stands for the SIP interface, although in this case the PrivateGSM is the client and it's not going to be connected to the SIP/TLS service unless a proper certificate is issued.
| Warning |
|---|
Please consider that the certificates are strictly bounded to the name they are released for, so you make sure you assigned via DNS the proper name to the IP where the service is published |
| Info |
|---|
You can load as many certificates as you need and then assign one of them to one of the two above services, as it suites you better. |
After you're done, just press the "Update" button.
...