210-065 · Question #339
An administrator is troubleshooting an endpoint whose SIP Registration Status shows "Failed: 403 Forbidden" and must obtain information about the cause of the failure. To which two menu locations…
The correct answer is B. Endpoint > Diagnostics > Log Files > all.log E. VCS > Status > logs > Event Log. A SIP 403 Forbidden registration failure can be investigated by examining the endpoint's all.log file and the VCS Event Log, which together capture SIP signaling details and server-side registration events.
Question
An administrator is troubleshooting an endpoint whose SIP Registration Status shows "Failed:
403 Forbidden" and must obtain information about the cause of the failure. To which two menu locations must an engineer navigate? (Choose two.)
Options
- AEndpoint > Log Files > messages.log
- BEndpoint > Diagnostics > Log Files > all.log
- CVCS > Maintenance > Diagnostics > Incident Reporting > View
- DVCS > Status > logs > Configuration Log
- EVCS > Status > logs > Event Log
How the community answered
(19 responses)- A26% (5)
- B58% (11)
- C5% (1)
- D11% (2)
Why each option
A SIP 403 Forbidden registration failure can be investigated by examining the endpoint's all.log file and the VCS Event Log, which together capture SIP signaling details and server-side registration events.
The path Endpoint > Log Files > messages.log does not reflect the correct navigation structure on Cisco TelePresence endpoints; diagnostic log files are accessed under Diagnostics > Log Files, not a top-level Log Files menu.
The all.log file at Endpoint > Diagnostics > Log Files contains detailed SIP signaling traces including the full 403 Forbidden response and any accompanying reason headers, giving direct technical insight into why the endpoint's registration was rejected by the server.
VCS > Maintenance > Diagnostics > Incident Reporting > View displays automatically generated incident reports for system faults, not individual SIP registration failure events or their specific response codes.
The VCS Configuration Log records administrator-made configuration changes to the VCS, not SIP signaling events or endpoint registration authentication failures.
The VCS Event Log at VCS > Status > logs > Event Log records each registration attempt along with the resulting SIP response code, making it the correct VCS location to confirm the 403 error and identify the policy or authentication rule that triggered it.
Concept tested: Troubleshooting SIP 403 Forbidden via VCS and endpoint logs
Source: https://www.cisco.com/c/en/us/support/docs/unified-communications/telepresence-video-communication-server-vcs/115789-sip-reg-fail-vcs-00.html
Topics
Community Discussion
No community discussion yet for this question.