Free Cisco CLCEI 300-820 Actual Exam Questions - Question 7 Discussion
diagnostic logs, an engineer found that the destination pattern is “[email protected]:5061”, and
the call was dropped with a 404 response code from Expressway-C. The search rule intended for this
call-in Expressway-C is configured for Alias Pattern Match, Pattern type “Suffix,” and Pattern
“example.com”. How must the configuration be changed to allow the call?
Makes sense that the port is the issue here, since the suffix match won’t recognize "example.com:5061" as just "example.com". So, I’d pick B to create a transform on Expressway-C to strip the port number before matching. That way, the call gets routed correctly without changing UCM settings or policies.
B for sure, Expressway-C can’t match suffix with port included.
It’s B. The main issue is the port number in the destination pattern “[email protected]:5061” causing the suffix match to fail since the search rule only looks at “example.com” without ports. Stripping the port with a transform on Expressway-C lets the existing suffix pattern match work properly. Options A and D don’t address the port mismatch, and C’s about call policies on Expressway-E which isn’t where the problem originates here.
The search rule with suffix "example.com" won’t match when the port is included. So, adding a transform to strip the port number before matching makes sense here. B
C imo, the problem seems to be about allowing calls specifically on port 5061. The search rule on Expressway-C matches the domain but doesn't consider the port, so even if the suffix matches, the call is blocked because 5061 isn’t authorized. Adding a call policy rule on Expressway-E to explicitly permit calls to port 5061 would address this restriction. This approach targets the actual point of failure—the call being dropped due to policy—rather than just the pattern matching logic on Expressway-C.
This one’s tricky but the key is the mismatch caused by the port number in the destination pattern. Since the search rule looks for suffix “example.com” without the port, the call is rejected with 404. So changing the call policy list (D) to explicitly allow "example.com" including the port isn't really standard practice. Stripping off the port number with a transform (B) makes more sense because it aligns with how the rule matches. I’d go with B here—removing the port so the suffix match works as intended.
D imo, the call policy list might be blocking calls with port numbers included, so updating it to explicitly allow “example.com” with port 5061 could fix the 404 error.
Makes sense to me that the port number is messing with the pattern match since the suffix is just “example.com.” So removing the port from the dialed string would let the search rule apply properly. That points at B—creating a transform on Expressway-C to strip those port numbers before matching.
Option B makes sense here since the port number in the destination is causing the match to fail. Removing it should fix the issue.