Grey Headline (continued)
URI Dialing
TANDBERG VIDEO COMMUNICATIONS SERVER ADMINISTRATOR GUIDE
URI Dialing for Outgoing Calls
Process
When a user places a call using URI dialing, they will typically dial an address in the form name@ example.com from their endpoint. Below is the process that is followed when a URI address is dialed from an endpoint registered with your VCS:
1.The VCS will check its own list of registrations, and those of its Alternates, to see if the address is registered locally.
2.If the address is not registered locally, the VCS will check all its zones to see if any of them are configured with either:
•an AlwaysMatch, or
•a PatternMatch with a pattern that matches the URI address.
These zones will then be queried in priority order for the URI.
3.If one or more of the zones that contain a match are neighbor zones, the neighbor will be queried for the URI. If the neighbor supports URI dialing, it may route the call itself.
4.If one or more of the zones that contain a match are DNS zones, this will trigger the VCS to attempt to locate the endpoint through a DNS lookup. It does this by querying the DNS server configured on the VCS for the location of the domain as per the DNS resolution process.
5.If the domain part of the URI address was resolved successfully using an H.323 Location SRV record (i.e. for _ h323ls) then the address returned is queried via an LRQ for the full URI address.
6.If the domain part of the URI address was resolved using an H.323 Call SRV record (i.e. for _ h323cs) or an A/AAAA record lookup then the call is routed directly to the IP address returned in that record. An exception to this is where the original dial string has a port specified (e.g. user@example.com:1720) in which case the address returned is queried via an LRQ for the full URI address.
7.If the domain part of the URI address was resolved successfully the request is forwarded to those address(es).
Configuring Matches for DNS Zones
If you wish locally registered endpoints to be able to place URI calls via the VCS, then at a minimum you should configure a DNS zone with a match that has a Mode of AlwaysMatch. This will result in DNS always being queried, but will mean it is queried for all aliases, not just URI addresses.
To filter the queries sent to the DNS server:
•configure a DNS zone with a match that has a Mode of PatternMatch
•use the Pattern string and Pattern type fields to define the aliases that will trigger a DNS query. For example, a match with a Pattern string of *@* and a Pattern type of Regex will mean that DNS is only queried for aliases in the form of typical URI addresses.
To set up further filters, configure the remaining matches in the same DNS zone. You don’t need to create new DNS zones unless you want to configure more than the maximum of 5 matches.
You should create separate DNS zones if you want to filter based on the protocol (SIP or H.323) or hop count to be used.
Introduction | Getting Started |
| Overview and |
| System |
| VCS |
| Zones and | Call | Bandwidth |
| Firewall |
| Maintenance |
| Appendices |
| Status |
| Configuration |
| Configuration |
| Neighbors | Processing | Control |
| Traversal |
|
| ||||
|
|
|
|
|
|
|
|
|
|
| |||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
D14049.03 |
|
|
|
|
|
|
|
| 115 |
|
|
|
|
|
|
| |
MAY 2008 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||
