Calls to a particular extension are not routing to voicemail. The user reaches the voicemail system from the handset by pressing the Messages button. Which configuration parameter causes this problem?

The correct answer is A. The voicemail pilot number for call forwarding is missing from the ephone-dn. In Cisco Unified CME, the Messages button works because the voicemail pilot is configured globally under the telephony-service (which is why direct access still works). However, automatic call forwarding to voicemail (on no-answer, busy, etc.) requires the voicemail pilot to be c

CME/SRST Gateway Technologies

Question

Calls to a particular extension are not routing to voicemail. The user reaches the voicemail system from the handset by pressing the Messages button. Which configuration parameter causes this problem?

Options

AThe voicemail pilot number for call forwarding is missing from the ephone-dn
BThe voicemail pilot number is missing from the call handling on Cisco Unity Express
CThe voicemail pilot number is missing from the telephony service configuration on Cisco UCME
DThe voicemail pilot number for call forwarding is missing from the ephone

How the community answered

(40 responses)

A
83% (33)
B
10% (4)
C
3% (1)
D
5% (2)

Explanation

In Cisco Unified CME, the Messages button works because the voicemail pilot is configured globally under the telephony-service (which is why direct access still works). However, automatic call forwarding to voicemail (on no-answer, busy, etc.) requires the voicemail pilot to be configured on each individual ephone-dn using the 'call-forward' command. If that forwarding pilot is missing from the ephone-dn, unanswered calls will not redirect to voicemail even though manual access works fine.

Topics

#CME#Voicemail Integration#Call Forwarding#ephone-dn

Community Discussion

No community discussion yet for this question.

Full 300-815 Practice