210-060 · Question #313
A customer is unable to receive calls on the EX90 endpoint, but can made outbound calls. The endpoint uses CUCM for call and registration. If the engineer only has remote access to the EX90 and…
The correct answer is A. Check CUCM to see if the extension is in a reachable partition D. Check EX90 DND Status via WebAdmin. When an endpoint can place but not receive calls, the most targeted remote troubleshooting steps are verifying the CUCM partition reachability and checking whether Do Not Disturb is enabled on the endpoint.
Question
A customer is unable to receive calls on the EX90 endpoint, but can made outbound calls. The endpoint uses CUCM for call 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 the EX90 System Status
- CCheck CUCM to see if the endpoint is registered
- DCheck EX90 DND Status via WebAdmin
- ECheck CUCM to see if the endpoint has the correct Device Calling Search Space
How the community answered
(29 responses)- A72% (21)
- B17% (5)
- C3% (1)
- E7% (2)
Why each option
When an endpoint can place but not receive calls, the most targeted remote troubleshooting steps are verifying the CUCM partition reachability and checking whether Do Not Disturb is enabled on the endpoint.
If the calling party's Calling Search Space cannot reach the partition containing the EX90's directory number, inbound calls will fail while outbound calls succeed, making partition reachability a primary CUCM-side check for one-way call failure.
Checking EX90 System Status provides general hardware and network diagnostics but does not directly reveal why inbound calls fail while outbound calls succeed.
Confirming registration is a valid initial step, but since the endpoint can make outbound calls it is already confirmed as registered with CUCM, making this step redundant given the symptom.
Do Not Disturb (DND) enabled on the EX90 causes the endpoint to reject or silently ignore incoming calls while still allowing outbound calls, and this status is directly verifiable via the endpoint's WebAdmin interface without requiring physical access.
The Device Calling Search Space on the endpoint controls which partitions the device can call outbound, not which partitions can reach the device inbound, so it does not explain the inability to receive calls.
Concept tested: TelePresence endpoint inbound call failure - DND and partition troubleshooting
Source: https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200253-Troubleshoot-Cisco-Unified-CM-Call-Routi.html
Topics
Community Discussion
No community discussion yet for this question.