A professional monitors a secure cloud communications network with connected servers, devices, and certificates.
Webex administrators should check their SIP infrastructure’s certificate trust stores before Cisco moves affected connections to new certificate chains. Cisco’s November 12, 2026 advisory covers Edge Audio, SIP video meeting joins through Expressway or supported session border controllers, and Hybrid Calling for Webex Devices. Connections can fail if the equipment cannot validate Webex’s new chain.

A professional monitors a secure cloud communications network with connected servers, devices, and certificates. What is changing—and what is not​

Cisco attributes the migration to the Chrome Root Program’s phaseout of the Client Authentication extended key usage, or clientAuth, in newly issued public TLS certificates. Webex’s replacement certificates will retain both serverAuth and clientAuth. Cloud-registered video devices joining meetings directly do not need this trust-store update.

The administrator checklist​

Cisco’s instructions are specific:

  • Verify that the trust store serving the affected SIP connection contains IdenTrust Public Sector Root CA 1 and DigiCert Assured ID Root G2.
  • Add missing roots using instructions for the equipment and software version.
  • Keep IdenTrust Commercial Root CA 1 and other certificates existing connections require.
  • Confirm both required roots are present on the equipment itself afterward.

For identification, Cisco’s separate supported-root directory lists these SHA-1 certificate fingerprints:

Required rootCisco-listed fingerprint
IdenTrust Public Sector Root CA 1ba29416077983ff4f3eff231053b2eea6d4d45fd
DigiCert Assured ID Root G2a14b48d943ee0a0e40904f3ce0a4c09193515d3f

That directory corroborates the certificate identities; it does not establish that either root is installed on an organization’s Expressway or SBC.

Avoid an unnecessary certificate replacement​

For these covered connections, Webex will still accept customer-equipment certificates containing only serverAuth, provided other requirements are met. Other services using that equipment may impose different requirements. Cisco gives no specific cutover date in this advisory.

The practical takeaway: treat this as a targeted infrastructure trust check, not a blanket desktop remediation project. After changes, administrators should test the affected calling and meeting paths—not merely confirm that certificate files were uploaded. That validation recommendation follows directly from Cisco’s warning that failed chain validation can interrupt Edge Audio, SIP meeting joins, or Hybrid Calling.

 

References

  1. Webex Moves SIP Connections to New Certificate Chains - UC Today UC Today 2026-11-16T09:45:08.109000+00:00
  2. What Root Certificate Authorities are Supported for Calls to Cisco Webex Audio and Video Platforms? help.webex.com