210-060 · Question #323
An administrator is troubleshooting an endpoint with TCP firmware, whose SIP Registration Status shows "Failed: 403 Forbidden" and must obtain information about the cause of the failure. Which two…
The correct answer is A. Endpoint>Diagnostics>Log Files>all.log. C. VCS>Maintenance>Diagnostics>Incident Reporting >View. To diagnose a SIP 403 Forbidden registration failure, an engineer must check both the endpoint diagnostic log and the VCS Incident Reporting tool to gather client-side and server-side context.
Question
An administrator is troubleshooting an endpoint with TCP firmware, whose SIP Registration Status shows "Failed: 403 Forbidden" and must obtain information about the cause of the failure. Which two menu locations must an engineer navigate? (Choose two).
Options
- AEndpoint>Diagnostics>Log Files>all.log.
- BVCS>Status>logs>Configuration Log
- CVCS>Maintenance>Diagnostics>Incident Reporting >View
- DEndpoint>Log Files>messages.log
- EVCS>Status>logs>Event Log
How the community answered
(46 responses)- A78% (36)
- B7% (3)
- D11% (5)
- E4% (2)
Why each option
To diagnose a SIP 403 Forbidden registration failure, an engineer must check both the endpoint diagnostic log and the VCS Incident Reporting tool to gather client-side and server-side context.
The endpoint's all.log under Diagnostics>Log Files contains detailed SIP transaction records including the 403 Forbidden response headers, which reveal the server-side rejection reason such as authentication failure or policy restriction.
The Configuration Log records changes made to VCS settings and does not contain real-time SIP signaling or registration transaction details.
VCS Incident Reporting captures a diagnostic snapshot at the time of a registration failure, storing server-side event data that explains why the 403 was issued, making it the authoritative source of server context for the error.
messages.log is not the correct path on the endpoint for SIP diagnostics; the primary endpoint diagnostic log accessed via the GUI is all.log under Endpoint>Diagnostics>Log Files.
The VCS Event Log records general system-level events but does not capture the detailed per-incident diagnostic snapshots provided by the Incident Reporting feature.
Concept tested: VCS and endpoint log locations for SIP 403 troubleshooting
Source: https://www.cisco.com/c/en/us/td/docs/telepresence/infrastructure/vcs/admin_guide/Cisco-VCS-Administrator-Guide-X8-n/Cisco-VCS-Administrator-Guide-X8-n_chapter_010111.html
Topics
Community Discussion
No community discussion yet for this question.