Refer to the exhibit. A network engineer is attempting to register a Cisco TelePresence endpoint to a Cisco VCS. What is the most likely cause of this failure?

Question

Exhibit

Options

• AThe lab.local SIP domain is not configured in the Cisco VCS allow list for registration.
• BThe Cisco VCS failed to bind to the LDAP server, which is where the lab.local SIP domain is
• CThe lab.local SIP domain does not exist on the Cisco VCS.
• DThe endpoint does not have the proper port assignments configured for SIP signaling.
• EThe endpoint uses the TCP protocol and the Cisco VCS is configured to allow only TLS for SIP

• B
  12% (2)
• C
  82% (14)
• E
  6% (1)

Explanation

For a Cisco TelePresence endpoint to successfully register with a Cisco VCS, the SIP domain portion of the endpoint's URI (in this case, lab.local) must be explicitly configured as an allowed SIP domain on the VCS under Configuration > Domains. If the VCS does not recognize the domain, it will reject the registration request outright, producing the failure shown in the exhibit. This is one of the most common registration failures in VCS deployments. The other options are less likely: the allow list (A) controls which specific URI patterns can register but the domain issue is more fundamental; an LDAP bind failure (B) would affect a different authentication path; port misconfiguration (D) would typically produce a connectivity timeout rather than a rejection; and TLS-only enforcement (E) would produce a transport mismatch error, not a domain error.

No community discussion yet for this question.