Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| vendors:cisco:uc:cube:media-proxy [2026/10/22 10:13] – [Importing Certs into Router Trust Pool] gerardorourke | vendors:cisco:uc:cube:media-proxy [2026/10/27 11:45] (current) – [Importing Certs into Router Trust Pool] gerardorourke | ||
|---|---|---|---|
| Line 842: | Line 842: | ||
| ==== Importing Certs into Router Trust Pool ==== | ==== Importing Certs into Router Trust Pool ==== | ||
| + | <alert type=" | ||
| < | < | ||
| Line 849: | Line 850: | ||
| < | < | ||
| - | Not all certs need to be imported! | + | So you can see just CN of each certificate - use the following: |
| - | Test again by reimporting default | + | < |
| - | We should see a %SIP-5-TLS_CONNECTION: | + | |
| + | **Note - the only cert that we found that is needed to be imported into the trustpool, is the immediate parent cert of the SIP endpoint we were trying to connect to.** | ||
| + | |||
| + | Reference: https:// | ||
| + | < | ||
| + | < | ||
| + | |||
| + | //**The PKI Trustpool Management feature is enabled by default and uses the built-in CA certificate bundle in the PKI trustpool, which receives automatic updates from Cisco. Perform this task to manually update certificates in the PKI trustpool if they are not current, are corrupt, or if certain certificates need to be updated.**// | ||
| + | |||
| + | SUMMARY STEPS | ||
| + | To remove auto updates attempts to Cisco CA bundle which is enabled by default: | ||
| + | < | ||
| + | conf t | ||
| + | crypto pki trustpool policy | ||
| + | no cabundle url http:// | ||
| + | </ | ||
| + | |||
| + | <alert type=" | ||
| ===== Troubleshooting TLS / Certificate issues ===== | ===== Troubleshooting TLS / Certificate issues ===== | ||