210-065 · Question #386
A customer is unable to receive calls on the EX90 endpoint, but can make outbound calls. The endpoint uses CUCM for call control and registration. If the engineer only has remote access to the EX90…
The correct answer is C. Check CUCM to see if the endpoint is registered D. Check the EX90 System Status. When an EX90 can make but not receive calls on CUCM, the first remote steps are confirming CUCM registration status and reviewing the endpoint's system health summary.
Question
A customer is unable to receive calls on the EX90 endpoint, but can make outbound calls. The endpoint uses CUCM for call control and registration. If the engineer only has remote access to the EX90 and CUCM, what are the next two troubleshooting steps? (Choose two.)
Options
- ACheck CUCM to see if the extension is in a reachable partition.
- BCheck CUCM to see if the endpoint has the correct Device Calling Search Space
- CCheck CUCM to see if the endpoint is registered
- DCheck the EX90 System Status
- ECheck EX90 DND Status via WebAdmin
How the community answered
(22 responses)- A5% (1)
- B5% (1)
- C73% (16)
- E18% (4)
Why each option
When an EX90 can make but not receive calls on CUCM, the first remote steps are confirming CUCM registration status and reviewing the endpoint's system health summary.
Partition reachability is a dial-plan routing concern relevant to whether CUCM can resolve a dialed number, not a registration or endpoint-state issue that would cause inbound-only failure on a device that can already make calls.
The Device Calling Search Space governs what destinations the endpoint is permitted to dial outbound - since outbound calls already succeed, the CSS is confirmed functional and is not the cause of the inbound failure.
Checking CUCM for endpoint registration is a foundational troubleshooting step - even though outbound calls work, a stale or partial registration entry in CUCM can prevent inbound call delivery, and the CUCM device registration page shows current state directly.
The EX90 System Status page, accessible remotely via WebAdmin, provides a consolidated health snapshot including registration state, DND status, and active diagnostics, making it the most efficient single view to identify why inbound calls are failing.
DND status is relevant to inbound call blocking, but checking it via the WebAdmin DND page is redundant when System Status (D) already surfaces DND along with broader endpoint health in one consolidated view.
Concept tested: CUCM endpoint registration verification and remote troubleshooting
Source: https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/213526-troubleshoot-cisco-telepresence-endpoint.html
Topics
Community Discussion
No community discussion yet for this question.