Table of Contents
Advertisement
CPL Reference
Text goes here
This Appendix gives details of the VCS's implementation of the CPL language and should be read
in conjunction with the CPL standard RFC 3880 (5).
The VCS supports most of the CPL standard along with some TANDBERG-defined extensions. It
<incoming>
does not support the top level actions
3880. Instead it supports a single section of CPL within a
When Administrator Policy is implemented by uploading a CPL script to the VCS, the script is
checked against an XML schema to verify the syntax. There are two schemas - one for the basic
CPL specification and one for the TANDBERG extensions. Both these schemas can be
from the web
interface. and used to validate your script before uploading to the VCS.
The following example shows the correct use of namespaces to make the syntax acceptable:
<?xml version="1.0" encoding="UTF-8" ?>
<cpl xmlns="urn:ietf:params:xml:ns:cpl"
xmlns:taa="http://www.tandberg.net/cpl-extensions"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:cpl cpl.xsd">
<taa:routed>
<address-switch field="destination">
<address is="reception@example.com">
<proxy/>
</address>
</address-switch>
</taa:routed>
</cpl>
Getting
System
Introduction
Started
Overview
D 14049.01
07.2007
<outgoing>
and
as described in RFC
<routed>
section.
viewed
System
H.323 & SIP
Registration
Configuration
Configuration
Control
Overview
address-switch node
The address-switch node allows the script to run different actions based on the source or
destination aliases of the call. It specifies which fields to match and then a list of address nodes
contains the possible matches and their associated actions.
The address-switch has two node parameters:
address
The address construct is used within an address-switch to specify addresses to match. It supports
the use of Regular Expressions (see
is=string
contains=string
subdomain-of=string
regex="regular expression"
All address comparisons ignore upper/lower case differences so
match fred,
freD
etc.
otherwise node
The otherwise node will be executed if the address specified in the address-switch was found
but none of the preceding address nodes matched.
not-present node
The not-present node is executed when the address specified in the address-switch was not
present in the call setup message. This form is most useful when authentication is being used.
With authentication enabled the VCS will only use authenticated aliases when running policy so
the not-present action can be used to take appropriate action when a call is received from an
unauthenticated user (see the example
Zones and
Call
Neighbors
Processing
70
TANDBERG
TANDBERG
VIDEO COMMUNICATION SERVER
VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
ADMINISTRATOR GUIDE
Field
and Subfield.
Regular Expression Reference
for further information).
Selected field and subfield exactly match the given string.
Selected field and subfield contain the given string.
Note: The CPL standard only allows for this matching on the
display subfield; however the VCS allows it on any type of
field.
tel
If the selected field is numeric (e.g. the
address subdomain-
then this matches as a prefix; so
of="555"
5556734
matches
etc.
If the field is not numeric then normal domain name
address subdomain-
matching is applied; so
of="company.com" matches
nodeA.company.com
Selected field and subfield match the given regular
expression.
address is="Fred"
call screening of unauthenticated
users).
Firewall
Bandwidth
Maintenance
Traversal
Control
subfield)
etc.
will also
Appendices
Appendices
Advertisement
Table of Contents
