Enum Dialing For Incoming Calls - Cisco TelePresence Administrator's Manual

You can configure transforms for ENUM zones in the same way as any other zones (see the
zone transform process section for full information).
Any ENUM zone transforms are applied before the number is converted to an ENUM domain.
For example, you want to enable ENUM dialing from your network to endpoints at a remote site using a prefix
of 8 followed by the last 4 digits of the remote endpoints' E.164 number. You would configure an ENUM zone
on your VCS and then an associated search rule with:
Mode of Alias pattern match
n
Pattern string of 8(\d{4})
n
Pattern type of Regex
n
Pattern behavior of Replace
n
Replace string of 44123123(\1)
n
With this configuration, it is the resulting string (44123123xxxx) that is converted into an ENUM domain
and queried for via DNS.
To verify you have configured your outward ENUM dialing correctly, use the
Tools > Locate) to try to resolve an E.164 alias.

ENUM dialing for incoming calls

For your locally registered endpoints to be reached using ENUM dialing, you must configure a DNS NAPTR
record that maps your endpoints' E.164 numbers to their SIP/H.323 URIs. This record must be located at an
appropriate DNS domain where it can be found by any systems attempting to reach you by using ENUM
dialing.
About DNS domains for ENUM
ENUM relies on the presence of NAPTR records to provide the mapping between E.164 numbers and their
SIP/H.323 URIs.
RFC 3761, which is part of a suite of documents that define the ENUM standard, specifies that the domain
for ENUM - where the NAPTR records should be located for public ENUM deployments - is e164.arpa.
However, use of this domain requires that your E.164 numbers are assigned by an appropriate national
regulatory body. Not all countries are yet participating in ENUM, so you may want to use an alternative
domain for your NAPTR records. This domain could reside within your corporate network (for internal use of
ENUM) or it could use a public ENUM database such as http://www.e164.org.
Configuring DNS NAPTR records
ENUM relies on the presence of NAPTR records, as defined by
H.323 or SIP URI from an E.164 number.
The record format that the VCS supports is:
order flag preference service regex replacement
where:
order and preference determine the order in which NAPTR records are processed. The record with the
n
lowest order is processed first, with those with the lowest preference being processed first in the case of
matching order.
Cisco VCS Administrator Guide (X7.2)
Dial plan and call processing
Locate tool (Maintenance >
RFC 2915. These are used to obtain an
Search and
Page 209 of 498