300-820 · Question #94
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…
The correct answer is A. The dialplan must be redesigned to use the transforms to convert the alias into SIP URI format. The root cause is an alias format mismatch between how calls arrive and how endpoints are registered. The H.323 endpoint registered with a simple alias ('EndpointA'), but inbound calls likely arrive as SIP URIs (e.g., 'EndpointA@somedomain'). The current search rules cannot…
Question
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 "[email protected]" is also registered. How is this issue resolved?
Exhibit
Options
- AThe dialplan must be redesigned to use the transforms to convert the alias into SIP URI format
- BThe calls are failing because there are insufficient licenses. Additional licenses must be
- CThe current search rule does not match the call, so the search rule must be modified to include
- DCalling parties are placing calls with the wrong domain. End-users must be instructed not to
How the community answered
(37 responses)- A81% (30)
- B3% (1)
- C11% (4)
- D5% (2)
Explanation
The root cause is an alias format mismatch between how calls arrive and how endpoints are registered. The H.323 endpoint registered with a simple alias ('EndpointA'), but inbound calls likely arrive as SIP URIs (e.g., 'EndpointA@somedomain'). The current search rules cannot match these mismatched formats against the registered aliases. The solution is to use Expressway transforms in the dial plan to convert the incoming alias format into the format that matches the registered endpoint alias-for example, stripping the domain portion so a SIP URI resolves to the bare H.323 alias, or vice versa. This is a dial plan design problem, not a licensing issue (B), not a search rule match-scope issue alone (C), and not an end-user dialing behavior problem (D).
Topics
Community Discussion
No community discussion yet for this question.
