TLS 1.2 សម្រាប់ការដាក់ពង្រាយការសហការគ្នានៅក្នុងបរិវេណ
“
ព័ត៌មានអំពីផលិតផល
លក្ខណៈពិសេស៖
- Product Name: Unified Communications Manager
- Feature: Transport Layer Security (TLS) Setup
- Supported TLS Versions: 1.0, 1.1, 1.2
- Supported Devices: Conference bridges, Media Termination Point
(MTP), Xcoder, Prime Collaboration Assurance, Prime Collaboration
Provisioning, Cisco Unity Connection, Cisco Meeting Server, Cisco
IP Phones, Cisco Room Devices, Cloud services like Fusion
Onboarding Service (FOS), Common Identity Service, Smart License
Manager (SLM), Push REST service, Cisco Jabber and Webអតីតកម្មវិធី
clients, third-party applications
ការណែនាំអំពីការប្រើប្រាស់ផលិតផល
TLS Configuration Task Flow:
Step 1: Set Minimum TLS Version
Purpose: By default, Unified Communications Manager supports a
minimum TLS version of 1.0. If your security needs require a higher
version of TLS, reconfigure the system to use TLS 1.1 or 1.2.
Step 2: Set TLS Ciphers
Configure the TLS cipher options that Unified Communications
Manager supports.
Step 3: Configure TLS in a SIP Trunk Security Profile
Assign TLS connections to a SIP Trunk. Trunks that use this
គាំទ្រfile use TLS for signaling. You can also use the secure trunk to
add TLS connections to devices, such as conference bridges.
Step 4: Add Secure Profile to a SIP Trunk
Assign a TLS-enabled SIP trunk security profile to a SIP trunk
to allow the trunk to support TLS. You can use the secure trunk to
connect resources, such as conference bridges.
Step 5: Configure TLS in a Phone Security Profile
Assign TLS connections to a phone security profile. Phones that
use this profile use TLS for signaling.
Step 6: Add Secure Phone Profile to a Phone
Assign the TLS-enabled profile that you created to a phone.
Step 7: Add Secure Phone Profile to a Universal Device
គំរូ
Assign a TLS-enabled phone security profile to a universal
device template. If you have LDAP directory synchronization
configured with this template, you can provision phones with
security through the LDAP sync.
សំណួរដែលសួរញឹកញាប់ (FAQ)
Q: What products need to meet the minimum TLS requirement when
configuring Unified Communications Manager?
A: Products such as conference bridges, Media Termination Point
(MTP), Xcoder, Prime Collaboration Assurance, Prime Collaboration
Provisioning, Cisco Unity Connection, Cisco Meeting Server, Cisco
IP Phones, Cisco Room Devices, Cloud services like Fusion
Onboarding Service (FOS), Common Identity Service, Smart License
Manager (SLM), Push REST service, Cisco Jabber and Webអតីតកម្មវិធី
clients, along with other third-party applications need to meet the
minimum TLS requirement when configuring Unified Communications
អ្នកគ្រប់គ្រង។
“`
TLS Setup
· TLS Overview, on page 1 · TLS Prerequisites, on page 1 · TLS Configuration Task Flow, on page 2 · TLS Interactions and Restrictions, on page 7
TLS Overview
Transport Layer Security (TLS) provides secure and reliable signaling and data transfer between two systems or devices, by using secure ports and certificate exchange. TLS secures and controls connections among Unified Communications Manager-controlled systems, devices, and processes to prevent access to the voice domain.
TLS Prerequisites
Before you configure the minimum TLS version, make sure that your network devices and applications both support the TLS version. Also, make sure that they are enabled for TLS that you want to configure with Unified Communications Manager and IM and Presence Services. If you have any of the following products deployed, confirm that they meet the minimum TLS requirement. If they do not meet this requirement, upgrade those products:
· Skinny Client Control Protocol (SCCP) Conference Bridge · Transcoder · Hardware Media Termination Point (MTP) · SIP Gateway · Cisco Prime Collaboration Assurance · Cisco Prime Collaboration Provisioning · Cisco Prime Collaboration Deployment · Cisco Unified Border Element (CUBE) · Cisco Expressway
TLS Setup 1
TLS Configuration Task Flow
TLS Setup
· Cisco TelePresence Conductor
You will not be able to upgrade conference bridges, Media Termination Point (MTP), Xcoder, Prime Collaboration Assurance, Prime Collaboration Provisioning, Cisco Unity Connection, Cisco Meeting Server, Cisco IP Phones, Cisco Room Devices, Cloud services like Fusion Onboarding Service (FOS), Common Identity Service, Smart License Manager (SLM), Push REST service, and Cisco Jabber and Webex App clients along with other third-party applications.
Note If you are upgrading from an earlier release of Unified Communications Manager, make sure that all your devices and applications support the higher version of TLS before you configure it. For example, Unified Communications Manager and IM and Presence Services, Release 9.x supports TLS 1.0 only.
TLS Configuration Task Flow
Complete the following tasks to configure Unified Communications Manager for TLS connections.
នីតិវិធី
ជំហានទី 1
Command or Action Set Minimum TLS Version, on page 3.
គោលបំណង
By default, Unified Communications Manager supports a minimum TLS version of 1.0. If your security needs require a higher version of TLS, reconfigure the system to use TLS 1.1 or 1.2.
Step 2 (Optional) Set TLS Ciphers, on page 3.
Configure the TLS cipher options that Unified Communications Manager supports.
ជំហានទី 3
Configure TLS in a SIP Trunk Security Profile, នៅទំព័រ 3 ។
Assign TLS connections to a SIP Trunk. Trunks that use this profile use TLS for signaling. You can also use the secure trunk to add TLS connections to devices, such as conference bridges.
Step 4 Add Secure Profile to a SIP Trunk, on page 4.
Assign a TLS-enabled SIP trunk security profile to a SIP trunk to allow the trunk to support TLS. You can use the secure trunk to connect resources, such as conference bridges.
ជំហានទី 5
Configure TLS in a Phone Security Profile, នៅទំព័រ 5 ។
Assign TLS connections to a phone security profile. Phones that use this profile use TLS for signaling.
Step 6 Add Secure Phone Profile to a Phone, on page 5.
Assign the TLS-enabled profile that you created to a phone.
ជំហានទី 7
Add Secure Phone Profile to a Universal Device Template, Assign a TLS-enabled phone security profile to a universal
នៅទំព័រទី 6 ។
device template. If you have the LDAP directory
synchronization configured with this template, you can
provision phones with security through the LDAP sync.
TLS Setup 2
TLS Setup
Set Minimum TLS Version
Set Minimum TLS Version
By default, Unified Communications Manager supports a minimum TLS version of 1.0. Use this procedure to reset the minimum supported TLS version for Unified Communications Manager and the IM and Presence Service to a higher version, such as 1.1 or 1.2. Make sure that the devices and applications in your network support the TLS version that you want to configure. For details, see TLS Prerequisites, on page 1.
នីតិវិធី
ជំហានទី 1 ជំហានទី 2 ជំហានទី 3
Log in to the Command Line Interface. To confirm the existing TLS version, run the show tls min-version CLI command. Run the set tls min-version <minimum> CLI command where <minimum> represents the TLS version.
សម្រាប់អតីតample, run set tls min-version 1.2 to set the minimum TLS version to 1.2.
Note Until Release 15SU1, perform Step 3 on all Unified Communications Manager and IM and Presence Service Service cluster nodes.
Set TLS Ciphers
You can disable the weaker cipher, by choosing available strongest ciphers for the SIP interface. Use this procedure to configure the ciphers that Unified Communications Manager supports for establishing TLS connections.
នីតិវិធី
ជំហានទី 1 ជំហានទី 2
ជំហានទី 3
From Cisco Unified CM Administration, choose System > Enterprise Parameters. In Security Parameters, configure a value for the TLS Ciphers enterprise parameter. For help on the available options, refer to the enterprise parameter online help. Click Save.
Note All TLS Ciphers will be negotiated based on client cipher preference
Configure TLS in a SIP Trunk Security Profile
Use this procedure to assign TLS connections to a SIP Trunk Security Profile. Trunks that use this profile use TLS for signaling.
TLS Setup 3
Add Secure Profile to a SIP Trunk
TLS Setup
នីតិវិធី
ជំហានទី 1 ជំហានទី 2
ជំហានទី 3 ជំហានទី 4 ជំហានទី 5 ជំហានទី 6
ជំហានទី 7
From Cisco Unified CM Administration, choose System > Security > SIP Trunk Security Profile. Perform one of the following steps:
· Click Add New to create a new SIP trunk security profile. · Click Find to search and select an existing profile.
In the Name field, enter a name for the profile. Configure the Device Security Mode field value to Encrypted or Authenticated. Configure both the Incoming Transport Type and Outgoing Transport Type field values to TLS. Complete the remaining fields of the SIP Trunk Security Profile window. For help on the fields and their configuration, see the online help. Click Save.
Note This Note is applicable from Release 15SU2 onwards. When the minimum supported TLS version on Unified CM is set to 1.3, the trunks with Authenticated Device Security Mode will fail to connect with the destination.
Add Secure Profile to a SIP Trunk
Use this procedure to assign a TLS-enabled SIP trunk security profile to a SIP trunk. You can use this trunk to create a secure connection to resources, such as conference bridges.
នីតិវិធី
ជំហានទី ១ ជំហានទី ២ ជំហានទី ៣ ជំហានទី ៤ ជំហានទី ៥ ជំហានទី ៦
ជំហានទី 7
ជំហានទី 8
ជំហានទី 9
From Cisco Unified CM Administration, choose Device > Trunk. Click Find to search and select an existing trunk. For the Device Name field, enter a device name for the trunk. From the Device Pool drop-down list, choose a device pool. From the SIP Profile drop-down list, choose a SIP Profile. From the SIP Trunk Security Profile drop-down list, choose the TLS-enabled SIP Trunk Profile that you created in the previous task. In the Destination area, enter the destination IP address. You can enter up to 16 destination addresses. To enter additional destinations, click the (+) button. Complete the remaining fields in the Trunk Configuration window. For help with the fields and their configuration, see the online help. Click Save.
ចំណាំ
TLS Setup 4
TLS Setup
Configure TLS in a Phone Security Profile
If you are connecting the trunk to a secure device, you must upload a certificate for the secure device to Unified Communications Manager. For certificate details, see the Certificates section.
Configure TLS in a Phone Security Profile
Use this procedure to assign TLS connections to a Phone Security Profile. Phones that use this profile use TLS for signaling.
នីតិវិធី
ជំហានទី 1 ជំហានទី 2
ជំហានទី 3
ជំហានទី 4 ជំហានទី 5 ជំហានទី 6 ជំហានទី 7 ជំហានទី 8
From Cisco Unified CM Administration, choose System > Security > Phone Security Profile. Perform one of the following steps:
· Click Add New to create a new profile. · Click Find to search and select an existing profile.
If you are creating a new profile, select a phone model and protocol, and click Next.
Note If you want to use a universal device template and LDAP sync to provision security through the LDAP sync, select Universal Device Template as the Phone Security Profile ប្រភេទ។
បញ្ចូលឈ្មោះសម្រាប់អ្នកជំនាញfile. From the Device Security Mode drop-down list, select either Encrypted or Authenticated. (For SIP phones only) From the Transport Type, select TLS. Complete the remaining fields of the Phone Security Profile Configuration window. For help with the fields and their configuration, see the online help. Click Save.
Note This Note is applicable from Release 15SU2 onwards. If you set the Device Security Mode to Authenticated, the phones switch to a TLS version lower than 1.3 for registration.
When the minimum supported TLS version on the Unified CM is set to 1.3, the phones with Authenticated Device Security Mode will not register.
Add Secure Phone Profile to a Phone
Use this procedure to assign the TLS-enabled phone security profile to a phone.
Note To assign a secure profile to a large number of phones at once, use the Bulk Administration Tool to reassign the security profile for them.
TLS Setup 5
Add Secure Phone Profile to a Universal Device Template
TLS Setup
នីតិវិធី
ជំហានទី 1 ជំហានទី 2
ជំហានទី 3 ជំហានទី 4 ជំហានទី 5
ជំហានទី 6 ជំហានទី 7
From Cisco Unified CM Administration, choose Device > Phone. Perform one of the following steps:
· Click Add New to create a new phone. · Click Find to search and select an existing phone.
Select the phone type and protocol and click Next. From the Device Security Profile drop-down list, assign the secure profile that you created to the phone. Assign values for the following mandatory fields:
· MAC address · Device Pool · SIP Profile · Owner User ID · Phone Button Template
Complete the remaining fields of the Phone Configuration window. For help with the fields and their configuration, see the online help. Click Save.
Add Secure Phone Profile to a Universal Device Template
Use this procedure to assign a TLS-enabled phone security profile to a universal device template. If you have LDAP directory sync configured, you can include this universal device template in the LDAP sync through a feature group template and user profile. When the sync occurs, the secure profile is provisioned to the phones.
នីតិវិធី
ជំហានទី 1 ជំហានទី 2
ជំហានទី 3 ជំហានទី 4 ជំហានទី 5
ជំហានទី 6 ជំហានទី 7
From Cisco Unified CM Administration, choose User Management > User/Phone Add > Universal Device Template. Perform one of the following steps:
· Click Add New to create a new template. · Click Find to search and select an existing template.
For the Name field, enter a name for the template. From the Device Pool drop-down list, select a device pool. From the Device Security Profile drop-down list, select the TLS-enabled security profile that you created.
Note The Phone Security Profile must have been created with Universal Device Template as the device type.
Select a SIP Profile. Select a Phone Button Template.
TLS Setup 6
TLS Setup
TLS Interactions and Restrictions
ជំហានទី 8 ជំហានទី 9
Complete the remaining fields of the Universal Device Template Configuration window. For help with the fields and their configuration, see the online help.
Click Save. Include the Universal Device template in an LDAP directory synchronization. For details on how to set up an LDAP Directory sync, see the “Configure End Users” part of the System Configuration Guide for Cisco Unified Communications Manager.
TLS Interactions and Restrictions
This chapter provides information about the TLS Interactions and Restrictions.
TLS Interactions
Table 1: TLS Interactions
លក្ខណៈ
អន្តរកម្ម
Common Criteria mode
You can enable Common Criteria mode along with configuration of minimum TLS version. If you do so, the applications continue to comply with Common Criteria requirements and disable TLS 1.0 secure connections at application level. When the common criteria mode is enabled, you can configure the minimum TLS version as either 1.1 or 1.2 for the applications. For details on Common Criteria mode, see the ‘Compliance to Common Criteria’ topic of the Command Line Interface Reference Guide for Cisco Unified Communications Solutions.
TLS Restrictions
The following table highlights issues that you may run into when implementing Transport Layer Security (TLS) version 1.2 on legacy phones, such as 79xx, 69xx, 89xx, 99xx, 39xx, and IP Communicator. To verify whether your phone supports secure mode in this release, see the Phone Feature List Report in Cisco Unified Reporting. The feature restrictions on legacy phones and the workaround to implement the feature is listed in the following table:
Note The workarounds are designed to get the impacted feature functioning in your system. However, they do not guarantee TLS 1.2 compliance for that feature.
Table 2: Transport Layer Security Version 1.2 Restrictions
លក្ខណៈ
Legacy phones in Encrypted Mode
Legacy phones in Authenticated Mode
Restriction Legacy phones in Encrypted Mode do not work. There is no workaround.
Legacy phones in Authenticated Mode do not work. There is no workaround.
TLS Setup 7
TLS Restrictions
TLS Setup
លក្ខណៈ
ការដាក់កម្រិត
IP Phone services using secure URLs based on HTTPS.
IP Phone services using secure URLs based on HTTPS do not work.
Workaround to use IP Phone services: Use HTTP for all underlying service options. For example, corporate directory and personal directory. However, HTTP is not recommended as HTTP is not as secure if you need to enter sensitive data for features, such as Extension Mobility. The drawbacks of using HTTP include:
· Provisioning challenges when configuring HTTP for legacy phones and HTTPS for supported phones.
· No resiliency for IP Phone services.
· Performance of the server handling IP phone services can be affected.
Extension Mobility Cross EMCC is not supported with TLS 1.2 on legacy phones.
Cluster (EMCC) on legacy phones
Workaround: Complete the following tasks to enable EMCC:
1. Enable EMCC over HTTP instead of HTTPS.
2. Turn on mixed-mode on all Unified Communications Manager clusters.
3. Use the same USB eTokens for all Unified Communications Manager clusters.
Locally Significant Certificates (LSC) on legacy phones
LSC is not supported with TLS 1.2 on legacy phones. As a result, 802.1x and phone VPN authentication based on LSC are not available.
Workaround for 802.1x: Authentication based on MIC or password with EAP-MD5 on older phones. However, those are not recommended.
Workaround for VPN: Use phone VPN authentication based on end-user username and password.
Encrypted Trivial File Encrypted Trivial File Transfer Protocol (TFTP) configuration files គឺមិនមែនទេ។
Transfer Protocol (TFTP) supported with TLS 1.2 on legacy phones even with Manufacturer Installed
ការកំណត់រចនាសម្ព័ន្ធ files
Certificate (MIC).
មិនមានដំណោះស្រាយទេ។
CallManager certificate renewal causes legacy phones to lose trust
Legacy phones lose trust when the CallManager certificate is renewed. For example, a phone cannot get new configurations after renewing the certificate. This is applicable only in Unified Communications Manager 11.5.1
Workaround: To prevent legacy phones from losing trust, complete the following steps:
1. Before you enable the CallManager certificate, set the Cluster For Roll Back to Pre 8.0 enterprise parameter to True. By default, this setting disables the security.
2. Temporarily allow TLS 1.0 (multiple Unified Communications Manager reboots).
TLS Setup 8
TLS Setup
TLS Restrictions
លក្ខណៈ
ការដាក់កម្រិត
ការតភ្ជាប់ទៅ
TLS 1.2 connections to older versions of Unified Communications Manager that
non-supported versions of do not support the higher TLS version do not work. For example, a TLS 1.2 SIP
ស៊ីស្កូបង្រួបបង្រួម
trunk connection to Unified Communications Manager Release 9.x does not work
Communications Manager because that release does not support TLS 1.2.
You can use one of the following workarounds:
· Workaround to enable connections: Use nonsecure trunks, although this is not a recommended option.
· Workaround to enable connections while using TLS 1.2: Upgrade the non-supported version to a release that does support TLS 1.2.
Certificate Trust List (CTL) Client
CTL client does not support TLS 1.2.
You can use one of the following workarounds:
· Temporarily allow TLS 1.0 when using the CTL client and then move the Cluster to Common Criteria mode. Configure Minimum TLS to 1.1 or 1.2
· Migrate to the Tokenless CTL by using the CLI Command utils ctl set-cluster mixed-mode in Common Criteria mode. Configure Minimum TLS to 1.1 or 1.2
Address Book Synchronizer
មិនមានដំណោះស្រាយទេ។
Cisco Unified Communications Manager Ports Affected by Transport Layer Security Version 1.2 The following table lists the Unified Communications Manager Ports Affected By TLS Version 1.2:
Table 3: Cisco Unified Communications Manager Ports Applicable for Transport Layer Security Version 1.2
ពិធីសារពាក្យសុំ
Destination Cisco Unified Communications / Listener Manager Operating in Normal
របៀប
Cisco Unified Communications Manager Operating in Common Criteria Mode
Minimum Minimum Minimum Minimum Minimum Minimum
TLS
TLS
TLS
TLS
TLS
TLS
version 1.0 version 1.1 version 1.2 version 1.0 version 1.1 version 1.2
Tomcat HTTPS 443
TLS 1.0, TLS 1.1, TLS 1.2 TLS 1.1, TLS v1.2 TLS 1.2
TLS 1.1
TLS 1.1, TLS 1.2 TLS 1.2
SCCP – Signalling 2443 SEC – SIG Connection
Control Part (SCCP)
TLS 1.0, TLS 1.1, TLS 1.2 TLS 1.1, TLS 1.2 TLS 1.2
TLS 1.1
TLS 1.1, TLS 1.2 TLS 1.2
TLS Setup 9
TLS Restrictions
TLS Setup
Application Protocol Destination Cisco Unified Communications / Listener Manager Operating in Normal mode
Cisco Unified Communications Manager Operating in Common Criteria Mode
Minimum Minimum Minimum Minimum Minimum Minimum
TLS
TLS
TLS
TLS
TLS
TLS
version 1.0 version 1.1 version 1.2 version 1.0 version 1.1 version 1.2
CTL-SERV Proprietary 2444
TLS 1.0, TLS 1.1, TLS 1.2 TLS 1.1, TLS 1.2 TLS 1.2
TLS 1.1
TLS 1.1, TLS 1.2 TLS 1.2
Computer Quick
Telephony Buffer
Integration Encoding
(CTI)
(QBE)
2749
TLS 1.0, TLS 1.1, TLS 1.2 TLS 1.1, TLS 1.2 TLS 1.2
TLS 1.1
TLS 1.1, TLS 1.2 TLS 1.2
CAPF-SERV Transmission 3804 Control Protocol (TCP)
TLS 1.0, TLS 1.1, TLS 1.2 TLS 1.1, TLS 1.2 TLS 1.2
TLS 1.1
TLS 1.1, TLS 1.2 TLS 1.2
Intercluster Not
7501
Lookup applicable
សេវាកម្ម
(ILS)
TLS 1.0, TLS 1.1, TLS 1.2 TLS 1.1, TLS 1.2 TLS 1.2
TLS 1.1
TLS 1.1, TLS 1.2 TLS 1.2
Administrative Simple
XML
វត្ថុ
(AXL) Access
ពិធីការ
(SOAP)
8443
TLS 1.0, TLS 1.1, TLS 1.2 TLS 1.1, TLS 1.2 TLS 1.2
TLS 1.1
TLS 1.1, TLS 1.2 TLS 1.2
ខ្ពស់។
TCP
មាន-
ប្រូកស៊ី
(HA-Proxy)
9443
TLS 1.2 TLS 1.2 TLS 1.2 TLS 1.1 TLS 1.2 TLS 1.2
SIP-SIG
ពិធីសារផ្តួចផ្តើមសម័យ (SIP)
5061
TLS 1.0,
(configurable) TLS 1.1,
TLS 1.2
TLS 1.1, TLS 1.2
TLS 1.2
TLS 1.1
TLS 1.1, TLS 1.2 TLS 1.2
HA Proxy TCP
6971, 6972
TLS 1.2 TLS 1.2 TLS 1.2 TLS 1.1 TLS 1.1, TLS 1.2 TLS 1.2
ស៊ីស្កូ
HTTPS 8080,
Tomcat
8443
8443: TLS 8443: TLS 8443: TLS TLS 1.1 1.0, TLS 1.1, TLS 1.2 1.1, TLS 1.2 1.2
8443: TLS 8443: TLS 1.1, TLS 1.2 1.2
TLS Setup 10
TLS Setup
TLS Restrictions
ពិធីសារពាក្យសុំ
Destination Cisco Unified Communications / Listener Manager Operating in Normal
របៀប
Cisco Unified Communications Manager Operating in Common Criteria Mode
Minimum Minimum Minimum Minimum Minimum Minimum
TLS
TLS
TLS
TLS
TLS
TLS
version 1.0 version 1.1 version 1.2 version 1.0 version 1.1 version 1.2
ទុកចិត្ត
កម្មសិទ្ធិ 2445
ការផ្ទៀងផ្ទាត់
សេវាកម្ម
(TVS)
TLS 1.0, TLS 1.1, TLS 1.2 TLS 1.1, TLS 1.2 TLS 1.2
TLS 1.1
TLS 1.1, TLS 1.2 TLS 1.2
Instant Messaging and Presence Service Ports Affected by Transport Layer Security Version 1.2 The following table lists the IM and Presence Service Ports Affected By Transport Layer Security Version 1.2:
Table 4: Instant Messaging & Presence Ports Applicable for Transport Layer Security Version 1.2
Destination/Listener Instant Messaging & Presence Operating Instant Messaging & Presence Operating
in Normal mode
in Common Criteria mode
Minimum Minimum Minimum Minimum Minimum Minimum
TLS
TLS version TLS version TLS version TLS version TLS version
version 1.0 1.1
1.2
1.0
1.1
1.2
443
TLS 1.0, TLS 1.1, TLS 1.2
TLS 1.1
TLS 1.1, TLS 1.2
TLS 1.1, TLS 1.2
TLS 1.2
TLS 1.2
5061
TLS 1.0, TLS 1.1, TLS 1.2
TLS 1.1, TLS 1.2
TLS 1.2
TLS 1.1
TLS 1.1, TLS 1.2
TLS 1.2
5062
TLS 1.0, TLS 1.1, TLS 1.2
TLS 1.1, TLS 1.2
TLS 1.2
TLS 1.1
TLS 1.1, TLS 1.2
TLS 1.2
5280
TLS 1.0, TLS 1.1, TLS 1.2
TLS 1.1, TLS 1.2
TLS 1.2
TLS 1.1
TLS 1.1, TLS 1.2
TLS 1.2
8083
TLS 1.0, TLS 1.1, TLS 1.2
TLS 1.1, TLS 1.2
TLS 1.2
TLS 1.1
TLS 1.1, TLS 1.2
TLS 1.2
8443
TLS 1.0, TLS 1.1, TLS 1.2
TLS 1.1, TLS 1.2
TLS 1.2
TLS 1.1
TLS 1.1, TLS 1.2
TLS 1.2
TLS Setup 11
TLS Restrictions
TLS Setup
TLS Setup 12
ឯកសារ/ធនធាន
 |
Cisco TLS 1.2 for On Premises Collaboration Deployments [pdf] ការណែនាំអ្នកប្រើប្រាស់ TLS 1.2 for On Premises Collaboration Deployments, TLS 1.2, for On Premises Collaboration Deployments, Collaboration Deployments, Collaboration Deployments, Deployments |