D 14049.01
07.2007 92
TANDBERG VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Text goes here
Introduction Getting
Started
System
Overview
System
Configuration
H.323 & SIP
Configuration
Registration
Control
Zones and
Neighbors
Call
Processing
Firewall
Traversal
Bandwidth
Control Maintenance Appe ndices
TANDBERG
ADMINISTRATOR GUIDE
TANDBERG VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Call
Processing
ENUM Dialing
Configuring DNS NAPTR Records
ENUM relies on the presence of NA PTR records, as defined by
RFC 2915 [7]. These are used to obtain an H. 323 or SIP URI
from an E.164 number.
The record format that the VCS s upports is:
;; order flag preference service regex
replacement
where:
order and preference determine the ord er in which
NAPTR records will be proc essed. The record with the
lowest order is processed firs t, with those with the lowest
preference being processed fir st in the case of matching
order.
flag determines the interpreta tion of the other fields
in this record. Only the value u (indi cating that this is a
terminal rule) is currently suppo rted, and this is mandator y.
service states whether this rec ord is intended to describe
E.164 to URI conversion for H.323 or for SI P. Its value must
be either E2U+h323 or E2U+SIP.
regex is a regular expression that d escribes the conversion
from the given E.164 number to an H.323 o r SIP URI.
replacement is not currently used b y the VCS and should
be set to . (i.e. the full stop character).
•
•
•
•
•
•
About DNS Domains for ENUM
ENUM relies on the presence of NA PTR records as defined
by RFC 2915 [7]. These provide the mapp ing between E.164
numbers and their SIP/H.323 URIs.
RFC 3761 [8], which is part of a suite of document s that
define the ENUM standard, sp ecifies that the domain fo r
ENUM - where the NAPTR recor ds should be located for
public ENUM deployments - is e164.ar pa. However, use of
this domain requires that your E.164 n umbers are assigned
by an appropriate national regul atory body. Not all countries
are yet participating in ENU M, so you may wish to use an
alternative domain for your NA PTR records. This domain
could reside within your corpo rate network (for internal us e
of ENUM) or it could use a public ENUM da tabase such as
http://www.e164.org.
ENUM Dialing for Incoming Calls
Prerequisites
In order for your locally registe red endpoints to be reached
using ENUM dialing, you must confi gure a DNS NAPTR record
that maps your endpoints’ E.164 numb ers to their SIP/H.323
URIs. This record must be locate d at an appropriate DNS
domain where it can be found by any sy stems attempting to
reach you via ENUM dialing.
Example
For example, the record:
IN NAPTR 10 100 “u” “E2U+h323” “!^(.*)$!h323:\1@
example.com!” .
would be interpreted as follows:
10 is the order
100 is the preference
u is the flag
E2U+h323 states that this record is for an H.323 URI
!^(.*)$!h323:\1@example.com! describes the
conversion:
! is a field separator
the first field represent s the string to be converted . In
this example, ^(.*)$ represents the entire E.164 number
the second field represent s the H.323 URI that will be
generated. In this example, h323:\1@example.com
states that the E.164 number will be c oncatenated with
@example.com. For example, 1234 will be mapped to
1234@example.com.
. shows that the replacement fiel d has not been used.
•
•
•
•
•
•
•
•
•
•
Non-terminal rules in ENU M are not currently suppor ted
by the VCS. For more information o n these, see section
2.4.1 of RFC 3761 [8],