TANDBERG Gatekeeper User Manual page 43

TANDBERG Gatekeeper User Manual
Figure 19: Setting the ENUM Zone
;; order flag preference service regex replacement
IN NAPTR 10 100 "u" "E2U+h323" "!^.*$!h323:recipient@example.com!" .
order(10) and preference(100) determine the order in which NAPTR records will be processed:
Lowest order first, with lowest preference being processed first in the case of matching order.
flag (u) determines the interpretation of the other fields in this record. Only the value u is
supported.
service states that this record is intended to describe E.164 to URI conversion for H.323. Its
value must be E2U+h323.
regex describes the conversion from the given E.164 number to an H.323 URI. ! is a field
separator. The first part: ˆ.*$ represents the entire E.164 number which is replaced with the
second field: recipient@example.com
The last field of the NAPTR record, replacement, is not used and should be set to "." .
NOTE According to RFC 2915, NAPTR records may contain regex substitutions which are
applied to the E.164 number to produce the H.323 URI. This release of the Gatekeeper does not
support this behaviour: the NAPTR record is substituted for the E.164 number.
Once the DNS NAPTR (for the ENUM lookup) and SRV (for the corresponding H.323 URI
lookup) are present, ENUM dialing should be possible. To verify your configuration, you are
recommended to use the lookup command to ensure that E.164 numbers can be resolved.
32