nerdexam
Cisco

300-085 · Question #281

A customer's user tests voicemail functionality on a newly installed Cisco Unity Connection cluster and notices that the MWI function is not working properly. The user hears the greeting and can…

The correct answer is A. Review the MWI extensions of the created port group on the newly installed Cisco Unity E. Review the port group configuration, and check whether the option "Enable Message Waiting. When MWI lamps fail to illuminate on Cisco Unity Connection, the MWI extension values in the port group and the 'Enable Message Waiting Indicator' option are the primary configuration points to verify.

Cisco Unity Connection

Question

A customer's user tests voicemail functionality on a newly installed Cisco Unity Connection cluster and notices that the MWI function is not working properly. The user hears the greeting and can leave messages, but the MWI lamp on the phone is still switched off. Which two should a systems engineer check, in order to find the MWI configuration errors? (Choose two.)

Options

  • AReview the MWI extensions of the created port group on the newly installed Cisco Unity
  • BCheck whether the MWI service is activated and running in the Service Management section on
  • CCheck whether the search space of the created port group contains the route pattern for MWI
  • DCheck whether the voicemail ports on Cisco Unified Communications Manager are properly
  • EReview the port group configuration, and check whether the option "Enable Message Waiting

How the community answered

(49 responses)
  • A
    76% (37)
  • B
    12% (6)
  • C
    8% (4)
  • D
    4% (2)

Why each option

When MWI lamps fail to illuminate on Cisco Unity Connection, the MWI extension values in the port group and the 'Enable Message Waiting Indicator' option are the primary configuration points to verify.

AReview the MWI extensions of the created port group on the newly installed Cisco UnityCorrect

Each port group in Cisco Unity Connection must have correctly configured MWI On and MWI Off extensions that match the extensions defined in Cisco Unified CM - if these extensions are missing or incorrect, Unity Connection cannot send the MWI activation signal to CUCM to light the lamp.

BCheck whether the MWI service is activated and running in the Service Management section on

Because users can already hear greetings and leave messages successfully, basic connectivity and core services are confirmed operational, making a stopped MWI service an unlikely root cause in this scenario.

CCheck whether the search space of the created port group contains the route pattern for MWI

The port group search space controls partition reachability for outbound calls and is less directly tied to MWI lamp failures than missing MWI extensions or the disabled MWI option.

DCheck whether the voicemail ports on Cisco Unified Communications Manager are properly

Voicemail port configuration on CUCM affects call routing to Unity Connection, but since greetings and message recording are working, port-level connectivity has already been confirmed functional.

EReview the port group configuration, and check whether the option "Enable Message WaitingCorrect

The 'Enable Message Waiting Indicator' option must be explicitly checked in the port group settings - if it is disabled, Unity Connection will never send MWI notifications to CUCM regardless of all other configuration being correct.

Concept tested: Cisco Unity Connection MWI port group configuration and extensions

Source: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/15/administration/guide/b_15cucsag/b_15cucsag_chapter_0101.html

Topics

#MWI#port group#message waiting indicator#Unity Connection troubleshooting

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 300-085 Practice