210-060 · Question #56
Which configuration causes PSTN users to experience a fail tone for every other call when trying to reach a particular number on Cisco Unified CME?
The correct answer is B. Duplicate ephone-dn is not assigned to the ephone. In Cisco Unified CME, a duplicate ephone-dn provides a second line appearance for the same DN; if that duplicate is not assigned to an ephone, every other inbound call has no device to land on and receives a fail tone.
Question
Which configuration causes PSTN users to experience a fail tone for every other call when trying to reach a particular number on Cisco Unified CME?
Options
- Aephone-dn is not assigned to the ephone.
- BDuplicate ephone-dn is not assigned to the ephone.
- Cephone is not registered.
- Dephone does not exist for the ephone-dn.
How the community answered
(30 responses)- A3% (1)
- B77% (23)
- C7% (2)
- D13% (4)
Why each option
In Cisco Unified CME, a duplicate ephone-dn provides a second line appearance for the same DN; if that duplicate is not assigned to an ephone, every other inbound call has no device to land on and receives a fail tone.
If the primary ephone-dn is not assigned to any ephone, all calls to that number would fail rather than only every other call.
An ephone-dn configured with 'dual-line' or as a duplicate shares the same directory number across two line instances. When the second (duplicate) ephone-dn is not assigned to an ephone, the first call succeeds on the primary DN while the second call finds no ephone for the duplicate DN and fails, producing the alternating fail-tone symptom described.
An unregistered ephone would cause all calls to fail consistently, not in an alternating pattern.
If no ephone exists for the ephone-dn, every call would fail, not just every other one.
Concept tested: Cisco CME duplicate ephone-dn line assignment
Source: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucme/admin/configuration/guide/cmeadm/cmedn.html
Topics
Community Discussion
No community discussion yet for this question.