SIP endpoints can only make calls in the form of
URIs - for example name@domain. If the caller
does not specify a domain when placing the
call, the SIP endpoint automatically appends
its own domain to the number that is dialed. So
if you dial 123 from a SIP endpoint, the search
will be placed for 123@domain. If the H.323
endpoint being dialed is registered as 123, the
VCS will be unable to locate the alias 123@
domain and the call will fail.
If you have a deployment that includes both
SIP and H.323 endpoints that register using a
number, you will need to set up the following
pre-search and zone transforms. This will let
users place calls from SIP and H.323 endpoints
to H.323 endpoints registered using their H.323
E164 number only.

Explanation

The pre-search transform (example, below)
takes any number-only dial string (such as 123)
and appends the domain used in endpoint AORs
and URIs in your deployment. This ensures 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 number and full URI
are searched for, so that endpoints can still be
reached whether they have registered with an
H.323 number (123) or a full URI (123@domain):

•

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

•

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