Avaya J169 Installing And Administering page 130

H.323
Hide thumbs Also See for J169:
Table of Contents

Advertisement

Administering your phone
Parameter name
TLS_SECURE_RENEG
TLSSRVR
TLSSRVRVERIFYID
TLS_VERSION
UDT
VPNALLOWTAGS
May 2018
Default value
Description and value range
Communication Manager, set this value to 81 which is the
port required for HTTPS downloads rather than the using
the default.
0
Specifies whether a TLS session should be terminated if
the peer does not support secure renegotiation. Valid
values are:
• 0: TLS secure renegotiation is not required from peer.
• 1: TLS secure renegotiation is required from peer.
" " (Null)
IP addresses or DNS Names of HTTPS file servers used
to download deskphone files. Dotted decimal or DNS
format, separated by commas. Valid values are 0-255
ASCII characters, including commas.
0
Specifies whether the identity of a TLS server is checked
against its certificate. The identity of the server is
checked with the common name or subjectAltName fields
in the server certificate. Valid values are:
• 0: Identity of a TLS server is not checked against its
• 1: Identity of a TLS server is checked against its
0
Controls the TLS version that is used for all TLS
connections. Valid values are:
• 0: TLS versions 1.0, 1.1, and 1.2 are supported with
• 1: TLS 1.0 and TLS 1.1 are not supported. Only TLS
10
Specifies the Unsuccessful Discovery Timer (UDT) in
minutes. UDT is the time that the phone perform
discovery with list of gatekeepers configured and after
which the phone will reboot if no gatekeeper from the list
is discovered. Valid values are 10 to 960.
0
Specifies whether 802.1Q tags (controlled by L2Q
parameter) can be used in VPN mode. Valid values are:
• 0: Tags not allowed in the VPN mode.
• 1: Tags allowed in the VPN mode.
Installing and Administering Avaya J169/J179 IP Phone H.323
Comments on this document? infodev@avaya.com
certificate.
certificate. The validation of server identity is applicable
for IPSec VPN with certificate based authentication
(using NVSGIP), Backup/restore over HTTPS (using
BRURI), HTTPS file server (using TLSSRVR), WML
browser (using WMLHOME), H.323 over TLS signaling
(using MCIPADD).
TLS v1.2 as default.
v1.2 and higher are permitted.
Table continues...
130

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

J179

Table of Contents