183
D14049.07
March 2010
Grey Headline
(continued)
TANDBERG
VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Introduction
Overview and
status
System
configuration
VCS
configuration
Zones and
neighbors
Clustering and
peers
Call
processing
Bandwidth
control
Firewall
traversal
Appendices
Applications
Maintenance
CPL reference
As the CPL script is evaluated it maintains a list of addresses (H.323 IDs, URLs and E.164 numbers) which will be used as the destination of the call if a
proxy
node is executed. The
taa:location
node
allows the location set to be modified so that calls can be redirected to different destinations.
At the start of script execution the location set is initialized to the original destination.
The following attributes are supported on
taa:location
nodes. It supports the use of Regular Expressions (see the
Regular expression reference
Appendix for further information).
Clear = "yes" | "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.
url=string
The new location to be added to the location set. The given
string can specify a URL (e.g.
), H.323 ID or an
E.164 number.
priority=<0.0..1.0> | "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.
regex="<regular expression>" replace="<string>"
Specifies the way in which a location matching the regular
expression is to be changed.
location
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. 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
field
section.
The
message-regex
parameter allows a regular expression to be matched against the entire incoming SIP message.
Note that any rule containing a
message-regex
parameter will never match an H.323 call.
