Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco Exam 300-810 Topic 1 Question 89 Discussion

Actual exam question for Cisco's 300-810 exam
Question #: 89
Topic #: 1
[All 300-810 Questions]

Refer to the exhibit.

Refer to the exhibit A collaboration engineer is troubleshooting an issue with MWIs not working for SIP-integrated Cisco Unity Connection users on Cisco UCM Calls to the Cisco Unity Connection work. but MWIs do not light This problem affects all users on the system Which action resolves the issue?

Show Suggested Answer Hide Answer
Suggested Answer: D

The scenario describes an issue where Message Waiting Indicators (MWIs) aren't lighting up for SIP-integrated Cisco Unity Connection users, even though calls reach voicemail. This points towards a configuration problem with MWI notifications on Cisco UCM.

A) Modify the SIP Trunk Security Profile on Cisco UCM:While SIP trunk security is important, it likely wouldn't affect MWI functionality in this case.

B) Increase the Delay Between Requests timer on Cisco Unity Connection:This setting might be used for other purposes but wouldn't directly address MWI notification issues on Cisco UCM.

C) Assign a Calling Search Space to the SIP Trunk on Cisco UCM:Calling Search Space defines call routing, not MWI notification.


Contribute your Thoughts:

Kris
6 months ago
This question is making me thirsty. Anyone else want to grab a coffee after the exam?
upvoted 0 times
...
Linwood
6 months ago
I'm going with D. Configuring the Message Waiting Numbers just makes the most sense to me for this problem. It's like turning the lights on, you know?
upvoted 0 times
...
Domonique
6 months ago
Hmm, I'm not sure about this one. Maybe B? Increasing the Delay Between Requests timer on Cisco Unity Connection could help with the timing issue.
upvoted 0 times
...
Mohammad
6 months ago
D is the way to go. If the MWIs are not lighting up, it's likely due to an issue with the message waiting numbers on the Cisco UCM side.
upvoted 0 times
Jospeh
5 months ago
Yeah, configuring the message waiting numbers on Cisco UCM should resolve the issue.
upvoted 0 times
...
Golda
5 months ago
I think D is the correct option.
upvoted 0 times
...
...
Marlon
6 months ago
I think the answer is D. Configuring the Message Waiting Numbers on Cisco UCM seems like the most logical solution to fix the issue with MWIs not lighting up.
upvoted 0 times
Lelia
5 months ago
Assigning a Calling Search Space to the SIP Trunk on Cisco UCM could be another solution to consider.
upvoted 0 times
...
Reynalda
5 months ago
I think increasing the Delay Between Requests timer on Cisco Unity Connection might also help.
upvoted 0 times
...
Malinda
5 months ago
I'm not sure, maybe we should also consider modifying the SIP Trunk Security Profile on Cisco UCM.
upvoted 0 times
...
Lyndia
5 months ago
I agree, that does sound like it would resolve the problem.
upvoted 0 times
...
Brynn
6 months ago
I think the answer is D. Configuring the Message Waiting Numbers on Cisco UCM seems like the most logical solution to fix the issue with MWIs not lighting up.
upvoted 0 times
...
Ilda
6 months ago
I agree, configuring the Message Waiting Numbers on Cisco UCM should resolve the issue.
upvoted 0 times
...
...
Sunny
6 months ago
I disagree, I believe the correct answer is D) Configure the Message Waiting Numbers on Cisco UCM.
upvoted 0 times
...
Clemencia
6 months ago
I think the answer is A) Modify the SIP Trunk Security Profile on Cisco UCM.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77