Grey Headline (continued)
Introduction
TANDBERG VIDEO COMMUNICATIONS SERVER ADMINISTRATOR GUIDE
Call Processing Diagram
One of the functions of the VCS is to route calls to their appropriate destination, based on the address or alias received from a locally registered endpoint or neighbor zone.
There are a number of steps involved in determining the destination of a call, and some of these steps can involve transforming the alias or redirecting the call to other aliases. It is important to understand the process before setting up your dial plan so you can avoid circular references.
Search Process
The process followed by the VCS when attempting to locate a destination endpoint is shown in the diagram opposite.
1. | The user enters into their endpoint the alias or address of the |
| destination endpoint. This can be in a number of different |
| formats. |
2. | The destination address is sent from the caller’s endpoint to |
| its local VCS (i.e. the VCS to which it is registered). |
3. | The VCS applies any Local Zone transforms to the alias. |
4. | The VCS applies any Administrator Policy to the (transformed) |
| alias. If this results in a new alias, the process starts |
| again, with the new alias checked against the Local Zone |
| transforms. |
5. | The VCS applies any User Policy to the alias. If the alias is a |
| FindMe name, the process will start again; all the resulting |
VCS receives alias (from locally registered endpoint or neighbour zone)
|
|
|
|
|
|
|
|
|
|
|
|
| YES |
|
|
|
Does the alias |
|
|
|
|
|
|
|
|
|
|
|
|
| |||
|
|
|
|
|
| Apply Local Zone |
|
|
| |||||||
match a Local Zone |
|
| YES |
|
|
|
|
| ||||||||
|
|
|
| Transform |
|
|
| |||||||||
Transform pattern? |
|
|
|
|
|
|
|
|
| |||||||
|
|
|
|
|
|
| ||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
| ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NO |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||||
Is Administrator Policy |
|
|
|
|
|
| Apply Administrator |
|
|
| ||||||
|
| YES |
|
|
|
|
| |||||||||
enabled? |
|
|
|
|
| Policy |
|
|
| |||||||
|
|
|
|
|
|
|
|
|
| |||||||
|
|
|
|
|
|
|
|
|
| |||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NO |
|
|
|
|
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
| NO |
|
|
|
|
| |||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
| Is the alias a FindMe |
|
| ||||
Is User Policy enabled? |
| YES |
|
|
| YES | ||||||||||
|
|
|
| name? |
| |||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
| ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
NO
YES
Has the alias been
amended?
Route call to new
alias(es) listed in the FindMe configuration
| aliases will be checked against Local Zone transforms and |
| Administrator Policy. |
6. | The VCS then checks all its local registrations and those |
| of its Alternates for the alias, placing the call if the alias is |
| found. |
7. | If the alias is not found locally, the VCS will then query its |
| zones, in priority order, to see if any of them can find the |
| alias. If the alias matches an ENUM zone, this may return |
| a URI. If so, the process starts again; the URI is checked |
| against any Local Zone transforms, Administrator Policy and |
| User Policy. |
8. | If the alias is found by one of the neighbor zones, the call will |
| be placed to that zone. |
Search Local Zone |
|
and Alternate | NO |
registrations |
|
|
|
|
|
| Search Zones |
|
Has the alias been found? |
| NO |
|
| ||
|
|
| (in order of priority) |
| ||
|
|
|
|
|
| |
|
|
|
|
| ||
|
|
|
|
|
|
|
YES
Place call
Does the alias
match an ENUM zone that has returned a URI?
Introduction | Getting Started |
| Overview and |
| System |
| VCS |
| Zones and | Call | Bandwidth |
| Firewall |
| Maintenance |
| Appendices |
| Status |
| Configuration |
| Configuration |
| Neighbors | Processing | Control |
| Traversal |
|
| ||||
|
|
|
|
|
|
|
|
|
|
| |||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
D14049.03 |
|
|
|
|
|
|
|
| 92 |
|
|
|
|
|
|
| |
MAY 2008 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|