Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
Reference material
Cisco VCS Administrator Guide (X7.2)
Page 352 of 498
The following attributes are supported on taa:location nodes. It supports the use of
.
Clear = "yes" |
"no"
"no"
Specifies whether to clear the current location set before adding the new location. The
default is to append this location to the end of the set.
default is to append this location to the end of the set.
url=string
The new location to be added to the location set. The given string can specify a URL
(for example, user@domain.com), H.323 ID or an E.164 number.
(for example, user@domain.com), H.323 ID or an E.164 number.
priority=<0.0..1.0>
| "random"
| "random"
Specified either as a floating point number in the range 0.0 to 1.0, or random, which
assigns a random number within the same range. 1.0 is the highest priority. Locations
with the same priority are searched in parallel.
assigns a random number within the same range. 1.0 is the highest priority. Locations
with the same priority are searched in parallel.
regex="<regular
expression>"
replace="<string>"
expression>"
replace="<string>"
Specifies the way in which a location matching the regular expression is to be
changed.
changed.
source-url-for-
message=string
message=string
Replaces the From header with the specified string. Note that this will override any
User Policy that may have been applied.
User Policy that may have been applied.
rule-switch
This extension to CPL is provided to simplify Call Policy scripts that need to make decisions based on both
the source and destination of the call. A taa:rule-switch can contain any number of rules that are tested
in sequence; as soon as a match is found the CPL within that rule element is executed.
the source and destination of the call. A taa:rule-switch can contain any number of rules that are tested
in sequence; as soon as a match is found the CPL within that rule element is executed.
Each rule must take one of the following forms:
<taa:rule-switch>
<taa:rule origin="<regular expression>" destination="<regular expression>" message-
regex="<regular expression>">
<taa:rule authenticated-origin="<regular expression>" destination="<regular
expression>" message-regex="<regular expression>">
<taa:rule unauthenticated-origin="<regular expression>" destination="<regular
expression>" message-regex="<regular expression>">
<taa:rule registered-origin="<regular expression>" destination="<regular expression>"
message-regex="<regular expression>">
<taa:rule originating-user="<regular expression>" destination="<regular expression>"
message-regex="<regular expression>">
<taa:rule originating-zone="<regular expression>" destination="<regular expression>"
message-regex="<regular expression>">
</taa:rule-switch>
The meaning of the various origin selectors is as described in the
section.
The message-regex parameter allows a regular expression to be matched against the entire incoming SIP
message.
message.
Note that any rule containing a message-regex parameter will never match an H.323 call.
proxy
On executing a proxy node the VCS attempts to forward the call to the locations specified in the current
location set. If multiple entries are in the location set then this results in a forked call. If the current location
set is empty the call is forwarded to its original destination.
location set. If multiple entries are in the location set then this results in a forked call. If the current location
set is empty the call is forwarded to its original destination.
The proxy node supports the following optional parameters: