Cisco Cisco Expressway 维护手册
subdomain-
of=string
of=string
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.
regex="regular
expression"
expression"
Selected field and subfield match the given 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
attributes
SIP
H.323
unauthenticated-
origin
origin
The "From" and "ReplyTo"
fields of the incoming
message.
fields of the incoming
message.
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 call. If a SETUP is received without a preceding RAS
message then the origin is taken from the SETUP.
authenticated-
origin
origin
and
origin
The "From" and "ReplyTo"
fields of the message if it
authenticated correctly (or
where the relevant
Authentication Policy is Treat
as authenticated), otherwise
fields of the message if it
authenticated correctly (or
where the relevant
Authentication Policy is Treat
as authenticated), otherwise
not-present
.
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
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 Expressway receives a SETUP without a preceding RAS
message the origin will always be
message the origin will always be
not-present
.
originating-zone
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. In all
other cases this will be "DefaultZone".
neighbor, traversal server or traversal client zone then this will equate to the zone name. In all
other cases this will be "DefaultZone".
originating-user
If the relevant Authentication Policy is Check credentials or Treat as authenticated this is the
username used for authentication, otherwise
username used for authentication, otherwise
not-present
.
registered-
origin
origin
If the call originates from a registered endpoint this is the list of all aliases it has registered,
otherwise
otherwise
not-present
.
destination
The destination aliases.
original-
destination
destination
The destination aliases.
Note that any Authentication Policy settings that apply are those configured for the relevant zone according to the
source of the incoming message.
source of the incoming message.
If the selected field contains multiple aliases then the Expressway will attempt to match each address node with all of
the aliases before proceeding to the next address node, that is, an address node matches if it matches any alias.
the aliases before proceeding to the next address node, that is, an address node matches if it matches any alias.
Subfield
Within the address-switch node, the optional subfield parameter specifies which part of the address is to be
considered. The following table gives the definition of subfields for each alias type.
considered. The following table gives the definition of subfields for each alias type.
If a subfield is not specified for the alias type being matched then the
not-present
action is taken.
address-
type
type
Either
h323
or
sip
, based on the type of endpoint that originated the call.
247
Cisco Expressway Administrator Guide