TANDBERG D14049.04 Network Card User Manual


 
126
D14049.04
JULY 2008
Grey Headline (continued)
TANDBERG VIDEO COMMUNICATIONS SERVER
ADMINISTRATOR GUIDE
Introduction Getting Started
Overview and
Status
System
Conguration
VCS
Conguration
Zones and
Neighbors
Call
Processing
Bandwidth
Control
Firewall
Traversal
Appendices
Applications Maintenance
ENUM Dialing
ENUM Dialing for Outgoing Calls
Conguring 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 congure an ENUM zone with:
a match that has a
Mode of AlwaysMatch
a
DNS sufx of e164.arpa (the domain specied by the ENUM standard).
This will result in DNS always being queried for all 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 congure 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 lter the queries that are sent to each as
follows:
congure a match that has a
Mode of PatternMatch
use the
Pattern string and Pattern type elds to dene the aliases that will trigger an ENUM
lookup.
Example
For example, you want to enable ENUM dialing from your network to a remote ofce in the UK where
the endpoints’ E.164 numbers start with 44. You would congure an ENUM zone on your VCS that
has a Match congured as follows:
Mode
of PatternMatch
Pattern string
of 44
Pattern type
of Prex.
This will result in an ENUM query being sent to that zone only when someone dials a number
starting with 44.
Conguring Transforms for ENUM Zones
You can congure 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 congured 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 prex of 8 followed by the last 4 digits of the remote endpoints’ E.164 number. You would
congure an ENUM zone on your VCS that has a Match congured 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 conguration, 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 congured your outward ENUM dialing correctly, use the
xCommand Locate command to try and resolve an E.164 alias.