When a customer calls voicemail to retrieve their messages they hear ''Hello, to access your mailbox...''
instead of the users named followed by ''please enter your password...''.
After troubleshooting you discover that the Caller ID is not being sent correctly, therefore Avaya Aura
Messaging (AAM) is not able to identify the correct mailbox associated with the station number calling into
AAM.
How can this problem be fixed?
Suggested Answer: C
Get Premium 72301X Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
28 comments · newest first
JE
Jenelle
9 months ago
D could work too, but it feels like a workaround rather than a fix.
LI
Lilli
9 months ago
A seems simpler, but might not cover all cases.
PO
Polly
9 months ago
I agree, but C could be more comprehensive. It updates multiple headers.
AH
Ahmed
9 months ago
I think option B is the best. It directly addresses the caller ID issue.
TH
Theola
9 months ago
Wait, the caller ID can mess up voicemail? That's wild!
ME
Merilyn
9 months ago
D) makes sense, but is it really necessary?
MI
Micheline
10 months ago
C) sounds complicated, not sure it’s worth it.
LY
Lynelle
10 months ago
I think B) is more straightforward.
JO
Johnna
10 months ago
Haha, I bet the person who wrote this question has dealt with this issue before.
EV
Eve
10 months ago
D looks good, but I'm not sure about the public-unknown-numbering part.
DE
Detra
10 months ago
I'd go with C. Modifying the SIP headers is the way to go.
HE
Helene
10 months ago
I feel like option C might be overcomplicating things. I thought the simpler solutions were usually preferred unless absolutely necessary.
GU
Gussie
11 months ago
A) is the quickest fix for CLID issues.
TU
Tu
11 months ago
Option B seems like the most straightforward solution.
KA
Karon
11 months ago
I’m a bit confused about the difference between options A and D. Both seem to involve changing numbering, but I can't recall the specifics.
AR
Artie
11 months ago
Option A is a bit too simple, I think the problem requires a more comprehensive fix.
SC
Scot
11 months ago
I remember practicing a similar question where we had to modify the CLID format, so I’m leaning towards option B.
AN
Antonio
12 months ago
I think the issue is definitely related to the Caller ID not being sent correctly, but I'm not sure which option directly addresses that.
BR
Brent
12 months ago
This is a good one. I'd start by verifying the trunk group configuration and then look at the AAM web GUI options to see if I can find a caller ID modification rule that fits the problem.
BR
Brittni
1 year ago
I think option C might be the best solution. Configuring a DigitConversionAdapter in Session Manager to update the CLID format seems like the most comprehensive fix.
IZ
Izetta
1 year ago
Hmm, I'm a bit confused. Is the issue with the trunk group configuration or the Caller ID format? I'm not sure if option A or D is the right approach here.
DE
Dean
1 year ago
Okay, the key here is that the Caller ID is not being sent correctly to AAM. I think option B might be the way to go - using the AAM web GUI to create a caller ID modification rule.
FR
Francisca
1 year ago
This seems like a tricky one. I'll need to carefully review the options and think through the troubleshooting steps.
PE
Pearlene
7 months ago
Let's analyze each option before deciding.
KA
Kayleigh
7 months ago
We should consider the trunk group issue as well.
OZ
Ozell
8 months ago
I agree, but option C sounds interesting too.
LA
Lashawna
8 months ago
I think option B could be the best choice.
RO
Rory
8 months ago
This is definitely a tricky situation.