The trunk error 'the FQDN configured for your gateway is missing from CN or SAN' is resolved by making sure the certificate CN or SAN contains the FQDN or SRV configured on the trunk.

Checked 2026-09-25

Vendor
Cisco
Product
Webex Calling
Subsystem
certificate-based trunk TLS
Deployment
multi-tenant
Region
not restricted
Release range
current as of 2026-09-25
Checked
2026-09-25

Sources

Cite this note

APA

WarmTransfer. (2026, September 25). Troubleshooting a Webex Calling Local Gateway: source note webex-local-gateway-troubleshooting-err-fqdn-cn-san. WarmTransfer. https://warmtransfer.net/knowledge/claims/webex-local-gateway-troubleshooting-err-fqdn-cn-san

BibTeX

@misc{warmtransfer-claim-webex-local-gateway-troubleshooting-err-fqdn-cn-san,
  title  = {Troubleshooting a Webex Calling Local Gateway: source note webex-local-gateway-troubleshooting-err-fqdn-cn-san},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/claims/webex-local-gateway-troubleshooting-err-fqdn-cn-san},
  note   = {Source note webex-local-gateway-troubleshooting-err-fqdn-cn-san, checked 2026-09-25}
}

Read in context