An engineer is investigating failing incoming calls that are expected to connect. The engineer notices that the failed calls all have a port number of 5060 at the end of the URI. The search rules are configured in a way that they do not expect a port to be included. Which configuration allows the routing of this call?
The correct configuration involves transforming the pattern string in such a way that the port number is removed, ensuring the URI matches the search rules that do not expect a port to be included. The pattern string provided in option A, *(.*)@example.com(:5060)? correctly matches URIs with or without the port number 5060, and the transformation removes the port, allowing the routing rules to function correctly.
A seems correct. The statement says routing is in place for URIs without a port, only A correctly strips the port so that the resulting URI can be routed.
It's "A" The question is saying "do not expect" a port. It's saying to strip the port off the end. So A is the correct one
The correct configuration to allow routing of calls with a port number of 5060 at the end of the URI would be: D. * transform with a pattern string of “(.*)@example.com(:5060)?" replace a string of \<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="261766435e474b564a430845494b">[email protected]</a>\2 This configuration uses a regular expression to capture the URI with or without the port number (:5060). Then, it replaces it with the captured part (\<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="f2c3b2978a939f829e97dc919d9f">[email protected]</a>) and appends the port number (\2), if present, ensuring that the call routing accommodates URIs with or without the port number specified.