TANDBERG Border Controller User Guide
Page 60 of 118
15.2.
Making Decisions Based on Addresses
15.2.1.
address-switch
The
address-switch
node allows the script to run different actions based on the source or
destination aliases of the call. The
address-switch
specifies which fields to match and then a list of
address nodes contains the possible matches and their associated actions.
The supported attributes on an
address-switch
and their interpretation are as follows:
Field
The mandatory field parameter specifies which address is to be considered. The supported attributes
and their interpretation are as follows:
Authentication Mode: On
Authentication Mode: Off
origin
The source aliases from the
original LRQ or ARQ that started
the call if it authenticated
correctly otherwise
not-present
.
Since SETUP messages are not
authenticated, if we receive a
SETUP without a preceding RAS
message the origin will always be
not-present
.
The source aliases from the
original LRQ or ARQ that started
the call. If a SETUP is received
without a preceding RAS message
then the origin is taken from the
SETUP.
unauthenticated-origin
The source aliases from the original LRQ or ARQ that started the call.
If a SETUP is received without a preceding RAS message then the
origin is taken from the SETUP.
authenticated-origin
The source aliases from the
original LRQ or ARQ that started
the call if 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
not-present
.
not-present
registered-origin
If the call originates from a registered endpoint this is the list of all
aliases it has registered, otherwise
not-present
originating-zone
The name of the zone or subzone for the originating leg of the call. If
the call originates from a Zone or Traversal 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”.
originating-user
The username used for
authentication.
not-present
destination
The destination aliases.
original-destination
The destination aliases.
If the selected field contains multiple aliases then the Border Controller 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.