This example builds on the example from the
previous page. The previous example caters for
number-only dial strings, however H.323 IDs do
not have to be purely numeric; they can contain
alphanumeric (letters and digits) characters.
This example follows the same model as the
previous example — a pre-search transform
and two search rules to ensure that endpoints
can be reached whether they have registered
with an H.323 ID or a full URI — but uses
a different regex (regular expression) that
supports alphanumeric characters.

Explanation

The pre-search transform (example, below)
takes any alphanumeric dial string (such as
123abc) and appends the domain used in your
deployment to ensure that calls made by SIP
and H.323 endpoints result in the same URI.
Search rules (right) for the Local Zone then
ensure that both the E164 ID and full URI are
searched for, so that endpoints can still be
reached whether they have registered with
an H.323 ID (123abc) or a full URI (123abc@
domain):

•

The first search rule takes any aliases in the
format string@domain and transforms them
into the format string.

•

To ensure that any endpoints that have
actually registered with an alias in the format
string@domain can also still be reached, a
second search rule must be configured at
a lower priority that places calls to string@
domain without transforming the alias.