Refer to the exhibit.

Calls to locally registered endpoints are failing. At present, there are two endpoints
registered locally to this Expressway. An H.323 endpoint with an alias of ''EndpointA'' is registered, and a SIP endpoint with an alias of ''EndpointB@pod1.local'' is also registered. How is this issue resolved?
Suggested Answer: A
Get Premium 300-820 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
28 comments · newest first
VA
Val
11 months ago
No way, they should just fix the domain issue instead!
HE
Hermila
11 months ago
Wait, are they really using pod1.local? That seems off.
BE
Belen
11 months ago
Agree, the search rule needs tweaking for SIP.
LA
Lavera
11 months ago
I think it's definitely a license problem.
AN
Andra
12 months ago
Sounds like a dialplan issue to me.
MA
Maira
12 months ago
I vaguely recall something about licenses affecting call routing, but I don't think that's the main issue here. Option B seems less likely to me.
DA
Dahlia
1 year ago
I feel like we practiced a similar question where domain issues caused call failures. Option D sounds familiar, but I'm not completely confident.
NA
Nancey
1 year ago
I'm not entirely sure, but I think we discussed how search rules can affect call routing. Could option C be the answer?
BR
Brandee
1 year ago
I remember something about transforming aliases into SIP URIs, so maybe option A is the right approach?
BA
Barbra
1 year ago
I'm pretty confident I can solve this one. The issue is clearly with the domain, so option D is the right answer. The users just need to be instructed to use the correct domain.
SE
Serina
1 year ago
Okay, the key here seems to be that the dialplan needs to be able to handle both H.323 and SIP endpoints. I think option A is the way to go - I'll need to look into how to set up the transforms and search rules properly.
LO
Louvenia
1 year ago
Hmm, I'm a bit confused by the different endpoint types and the domain issue. I'll need to make sure I understand the details before trying to solve this.
FA
Fabiola
1 year ago
This looks like a tricky one. I'll need to carefully review the information about the registered endpoints and the dialplan configuration to figure out the best approach.
SE
Serina
2 years ago
Option B is the answer, no doubt. More licenses are required, simple as that. Why complicate things?
TA
Tatum
2 years ago
Let's make sure to double-check the licenses before making any changes.
VE
Verlene
2 years ago
No, it's definitely just a licensing issue. We should focus on that.
LO
Louisa
2 years ago
But maybe we can also check if the dialplan needs to be redesigned.
SK
Skye
2 years ago
I think the issue is with the licenses, we need more of them.
HE
Hector
2 years ago
I believe the problem might also be with the calling parties using the wrong domain. Instructing them not to use pod1.local could solve the issue.
AN
Antonette
2 years ago
I agree with Pete. Using transforms and separate search rules for each format should help.
AL
Alison
2 years ago
A, B, C, or D? Looks like a classic case of 'choose the most correct answer' to me.
AR
Arlene
2 years ago
D) Calling parties are placing calls with the wrong domain. End-users must be instructed not to use the pod1.local domain as that is owned by the local system. Calls to any other domain would work.
RE
Reena
2 years ago
A) The dialplan must be redesigned to use the transforms to convert the alias into SIP URI format and then use separate search rules for each format that needs to be dialed within the local zone.
PE
Pete
2 years ago
I think the issue can be resolved by redesigning the dialplan to convert the alias into SIP URI format.
CH
Christiane
2 years ago
Wait, so they're using the 'pod1.local' domain? Somebody needs to tell the IT team to get their head out of the cloud.
ME
Meaghan
2 years ago
I think option A is the correct answer. The dialplan needs to be redesigned to handle the different alias formats.
CA
Carmela
2 years ago
User2: Yes, the dialplan needs to be redesigned to handle the different alias formats.
AH
Ahmed
2 years ago
User1: I think option A is the correct answer.