User's Manual

Avaya B179 SIP Conference Phone Installation and Administration Guide
25
Require client certicate
When set to On, the Avaya B179 rejects incoming secure SIP connec-
tions (TLS or SIPS) if the client does not have a valid certicate.
Verify server When the Avaya B179 is acting as a client (outgoing connections) us-
ing secure SIP (TLS or SIPS) it will always receive a certicate from the
peer. If Verify server is set to On, the Avaya B179 closes the connection
if the server certicate is not valid.
Certicate Here you can upload a certicate to the Avaya B179 to be used for TLS
or SIPS communication.
A certicate is a le that combines a public key with information
about the owner of the public key, all signed by a trusted third party.
If you trust the third party, then you can be sure that the public key
belongs to the person/organization named in that le. You can also
be sure that everything you decrypt with that public key is encrypted
by the person/organization named in the
certicate.
Root certicate The public key in the root certicate is used to verify other certicates.
A root certicate is only needed if you have selected client or server
verication.
A root certicate is signed by the same public key that is in the certi-
cate, a so-called “self-signed” certicate. A typical root certicate is
one received from a Certicate Authority.
Private key Here you can upload a private key to the Avaya B179 to be used for
TLS or SIPS communication.
A private key is one of the keys in a key-pair used in asymmetric
cryptography. Messages encrypted using the public key can only be
decrypted using the private key.
Private key password Password used for encryption of the private key, if it is encrypted.