Cisco TelePresence Video Communication Server Administrator's Manual page 245

contains=string Selected field and subfield contain the given string. Note that the CPL
subdomain-
of=string
regex="regular
expression"
All address comparisons ignore upper/lower case differences so address is="Fred" will also
match fred, freD and so on.
field
Within the address-switch node, the mandatory field parameter specifies which address is to
be considered. The supported attributes and their interpretation are shown below:
Field parameter
attributes
unauthenticated-
origin
authenticated-
origin
and
origin
originating-zone The name of the zone or subzone for the originating leg of the call. If the call
originating-user If the relevant Authentication Policy is Check credentials or Treat as
registered-
origin
destination
Cisco VCS Administrator Guide (X6.1)
standard only allows for this matching on the display subfield; however the
VCS allows it on any type of field.
If the selected field is numeric (for example, the tel subfield) then this matches
as a prefix; so
address subdomain-of="555" matches 5556734 and so on. If the field
is not numeric then normal domain name matching is applied; so
address subdomain-of="company.com" matches
nodeA.company.com and so on.
Selected field and subfield match the given regular expression.
SIP
The "From" and "ReplyTo"
fields of the incoming
message.
The "From" and "ReplyTo"
fields of the message if it
authenticated correctly (or
where the relevant
Authentication Policy is
Treat as authenticated),
otherwise not-present.
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".
authenticated this is the username used for authentication, otherwise not-
present.
If the call originates from a registered endpoint this is the list of all aliases it
has registered, otherwise not-present.
The destination aliases.
H.323
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.
The source aliases from the original LRQ or
ARQ that started the call if it authenticated
correctly (or where the relevant
Authentication Policy is Treat as
authenticated) otherwise not-present.
Because SETUP messages are not
authenticated, if the VCS receives a SETUP
without a preceding RAS message the origin
will always be not-present.
Reference material
Page 245 of 401