Non-terminal rules in ENUM are not currently supported by the VCS. For more information on these, see
section 2.4.1 of RFC 3761.
For example, the record:
IN NAPTR 10 100 "u" "E2U+h323" "!^(.*)$!h323:\1@example.com!" .
would be interpreted as follows:
n 10 is the order
n 100 is the preference
n u is the flag
n E2U+h323 states that this record is for an H.323 URI
n !^(.*)$!h323:\1@example.com! describes the conversion:
l ! is a field separator
l the first field represents the string to be converted. In this example, ^(.*)$ represents the entire E.164
number
l the second field represents the H.323 URI that will be generated. In this example,
h323:\1@example.com states that the E.164 number will be concatenated with @example.com. For
example, 1234 will be mapped to 1234@example.com.
n . shows that the replacement field has not been used.
Cisco VCS Administrator Guide (X8.1.1) Page 216 of 507
Dial plan and call processing
About ENUM dialing
To Next Page
Loading...
