
Grey Headline (continued)
CPL Reference
TANDBERG VIDEO COMMUNICATIONS SERVER ADMINISTRATOR GUIDE
address-switch
field
Within the
| Authentication Mode: On |
| Authentication Mode: Off |
|
Field | SIP | H.323 | SIP | H.323 |
origin | The "From" and "ReplyTo" fields of the | The source aliases from the original | The "From" and "ReplyTo" fields of the | The source aliases from the original LRQ |
| message if it authenticated correctly, | LRQ or ARQ that started the call if | incoming message. | or ARQ that started the call. If a SETUP |
| otherwise | it authenticated correctly otherwise |
| is received without a preceding RAS |
|
|
| message then the origin is taken from | |
|
| are not authenticated if we receive a |
| the SETUP. |
|
| setup without a preceding RAS message |
|
|
|
| the origin will always be |
|
|
The "From" and "ReplyTo" fields of the | The source aliases from the original LRQ | The "From" and "ReplyTo" fields of the | The source aliases from the original LRQ | |
| incoming message. | or ARQ that started the call. If a SETUP | incoming message. | or ARQ that started the call. If a SETUP |
|
| is received without a preceding RAS |
| is received without a preceding RAS |
|
| message then the origin is taken from the |
| message then the origin is taken from |
|
| SETUP. |
| the SETUP. |
The "From" and "ReplyTo" fields of the | The source aliases from the original |
|
| |
| message if it authenticated correctly, | LRQ or ARQ that started the call if |
|
|
| otherwise | it authenticated correctly otherwise |
|
|
|
| empty. Since SETUP messages are not |
|
|
|
| authenticated if we receive a setup |
|
|
|
| without a preceding RAS message the |
|
|
|
| origin will always be |
|
|
The name of the zone or subzone for the originating leg of the call. If the call originates from a Neighbor, Traversal Server or Traversal Client zone then this will equate to | ||||
| the zone name. If it comes from an endpoint within one of the local subzones this will be the name of the subzone. If the call originates from any other locally registered | |||
| endpoint this will be "DefaultSubZone". In all other cases this will be "DefaultZone". |
| ||
The username used for authentication. |
|
|
| |
| If the call originates from a registered endpoint this is the list of all aliases it has registered, otherwise |
| ||
destination | The destination aliases. |
|
|
|
| The destination aliases. |
|
|
|
If the selected field contains multiple aliases then the VCS will attempt to match each address node with all of the aliases before proceeding to the next address node i.e. an address node matches if it matches any alias.
Introduction | Getting Started |
| Overview and |
| System |
| VCS |
| Zones and |
| Call |
| Bandwidth |
| Firewall |
| Maintenance | Appendices |
| Status |
| Configuration |
| Configuration |
| Neighbors |
| Processing |
| Control |
| Traversal |
| ||||
|
|
|
|
|
|
|
|
|
|
|
| |||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
D14049.03 |
|
|
|
|
|
|
|
| 173 |
|
|
|
|
|
|
| ||
MAY 2008 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|