Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Avaya Exam 72301X Topic 5 Question 50 Discussion

Actual exam question for Avaya's 72301X exam
Question #: 50
Topic #: 5
[All 72301X Questions]

Refer to the exhibit.

After some system maintenance was completed over the weekend, a customer calling from the office states they hear a fast busy when trying to access their voicemail.

Avaya support verifies local network connectivity is up and Avaya Aura Messaging server is registering no alarms. A SIP trace displays a 404 Not Found error message.

Based on what is already working, to where can the issue potentially be isolated?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Leila
2 days ago
Network outage? Nah, that's too easy. Where's the fun in that? I bet it's a secret government conspiracy to keep us from leaving voicemails.
upvoted 0 times
...
Julieta
3 days ago
Interoperability testing? I thought we were troubleshooting a voicemail issue, not planning a surprise party for the IT team.
upvoted 0 times
...
Yen
6 days ago
Okay, let's think this through. If the local network is up and the server is not showing any alarms, the issue is most likely with the endpoint routing configuration. Time to dust off the old networking textbook.
upvoted 0 times
...
Andree
13 days ago
I'm not sure, but it could also be related to network outage.
upvoted 0 times
...
Gregoria
15 days ago
Hmm, a 404 Not Found error message? Looks like someone's web browsing history has found its way into the voicemail system.
upvoted 0 times
...
Rosamond
16 days ago
I agree with Ezekiel, it seems like a routing configuration issue.
upvoted 0 times
...
Ezekiel
18 days ago
I think the issue could be with the routing configuration.
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