114
D14049.05
February 2009
Grey Headline
(continued)
TANDBERG
VIDEO COMMUNICATIONS SERVER
ADMINISTRATOR GUIDE
Introduction
Getting started
Overview and
status
System
configuration
VCS
configuration
Zones and
neighbors
Call
processing
Bandwidth
control
Firewall
traversal
Appendices
Applications
Maintenance
ENUM dialing
ENUM dialing for outgoing calls
Adding and configuring ENUM zones
In order for locally registered endpoints to use
ENUM dialing, you must configure an ENUM
zone for each ENUM service used by remote
endpoints. To do this:
Go to the Zones page (
1.
VCS configuration >
Zones
.)
Click
2.
New
. You will be taken to the
Create
Zone
page.
Enter the zone
3.
Name
and select a
Type
of
ENUM
.
Click
4.
Create Zone
. The zone will be saved and
you will be taken to the
Edit Zone
page. See
the sections below for configuration options.
To create a new ENUM zone using the CLI:
xCommand ZoneAd
•
d
xConfiguration Zones Zone [1..200
•
]
Any number of ENUM zones may be
configured on the VCS.
You should configure at least one ENUM
zone for each DNS suffix that your endpoints
may use.
Normal zone pattern matching and
prioritization rules will apply to ENUM
zones.
Hop count
When placing a call dialed using ENUM, the
actual hop count used for the call will be the hop
count of the zone via which the call is eventually
placed once the alias has been resolved.
DNS suffix
The DNS zone that is to be queried for a
NAPTR record. This suffix is appended to the
transformed E.164 number in an attempt to find
a matching NAPTR record.
SIP mode
Determines whether or not SIP records will be
looked up for this zone.
H.323 mode
Determines whether or not H.323 records will
be looked up for this zone.
Configuring matches for ENUM zones
If you wish locally registered endpoints to be
able to make ENUM calls via the VCS, then at
a minimum you should configure an ENUM zone
with:
a match that has a
•
Mode
of
AlwaysMatch
a
•
DNS suffix
of
e164.arpa
(the domain
specified by the ENUM standard).
This will result in DNS always being queried for
all types of aliases, not just ENUMs. It will also
mean that ENUM dialing will only be successful
if the enterprise being dialed uses the
e164.
arpa
domain.
To ensure successful ENUM dialing, you must
configure an ENUM zone for each domain that
holds NAPTR records for endpoints that callers
in your enterprise might wish to dial.
Once these ENUM zones have been created, you
can filter the queries that are sent to each as
follows:
configure a match that has a
•
Mode
of
PatternMatch
use the
•
Pattern string
and
Pattern type
fields
to define the aliases that will trigger an ENUM
lookup.
Example
For example, you want to enable ENUM dialing
from your network to a remote office in the UK
where the endpoints’ E.164 numbers start with
44
. You would configure an ENUM zone on your
VCS that has a Match configured as follows:
Mode
•
of
PatternMatch
Pattern string
•
of
44
Pattern type
•
of
Prefix
.
This will result in an ENUM query being sent to
that zone only when someone dials a number
starting with
44
.
Configuring transforms for ENUM zones
You can configure transforms for ENUM zones
in the same way as any other zones (see
Zone
searching and transforming
for full information).
If there are any transforms configured for an
ENUM zone, these will be applied prior to the
number being converted to an ENUM domain.
Example
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 that
has a Match configured as follows:
Mode
•
of
PatternMatch
Pattern string
•
of
8(\d{4})
Pattern type
•
of
Regex
Pattern behavior
•
of
Replace
Replace string
•
of
44123123(\1)
With this configuration, it will be the resulting
string (i.e.
44123123xxxx
) that will then be
converted into an ENUM domain and queried for
via DNS.
To verify that you have configured your
outward ENUM dialing correctly, use the
Locate
tool (
Maintenance > Tools >
Locate
) to try and resolve an E.164 alias.
This can also be done using the CLI using
xCommand Locat
e
.
Configuring DNS servers
To configure the VCS with details of DNS servers
to be used when searching for NAPTR records:
System configuration > DNS
•
.
You will be taken to the
DNS
page.
xConfiguration IP DNS Serve
•
r
In order for endpoints registered to the
VCS to make outgoing calls using ENUM
dialing, you must configure at least one
DNS server for the VCS to query. For resilience,
you can specify up to five DNS servers.
The DNS server(s) configured using this
page are used as part of both the ENUM
dialing and URI dialing via DNS
processes.
Address 1 to
Address 5
Enter the IP address(es) of up to 5 DNS servers
that the VCS will query when attempting to
locate a domain.
