20
8 Creating the policy file
The policy file provides the rules that determine how each VCS identifies calls from compliant
endpoints that need to be recorded and chooses a TCA to record calls.
This section contains three examples of policy files for a number of different TCA deployments:
the
Commented policy file (all calls recorded)
contains comments that explain what each section of the
file is doing and is an example of a file that sends every call the VCS receives to the TCA for
recording
the
Route selected calls to TCA
file is an example of a file that sends calls made from a specific set of
defined endpoints.
The easiest way to configure a policy file is to make a copy of an existing VCS policy file and modify it
using an XML editor.
Important
: before editing the VCS policy file, make a backup of the original. If you
subsequently need to switch the TCA off, you can upload the original file back to the VCS.
8.1 Specifying which endpoints to record
As we discussed in section
6.2 Using patterns to identify compliant endpoints
, you can use the policy file to
define the specific subsets of endpoints that you want to record.
To use patterns, the endpoints in question must contain an common identifying element (e.g. the word
‘trader’ in
joe.smith.
trader
@tandberg.com
) that makes them distinct from the rest. You then specify the
pattern or patterns you want to record in the
address
regular expression section of the policy file.
You can specify whether either the origin endpoint or the destination endpoint is the one that needs to
be recorded using the address switch field. In the example below the file is specifying that all URIs of
destination endpoints (as opposed to origin) containing the expression ‘trader’ must be recorded:
<address-switch field="destination">
<address regex="CAREC[.](.*)">
</address>
<address regex=".*[email protected]">
To stipulate multiple patterns, separate them with a pipe symbol (|). Note that if you specify an E164
number it takes precedence over an H.323 address.
See the
VCS User Guide
for more information about control files.
8.2 How the policy file directs these calls to the TCA
In section
6.3.2 How the VCS and TCA work together
, we talked about how the VCS changes the URI of the
endpoint to send it to the TCA by adding the prefix ‘carec’ and the suffix ‘caxxx’.
Summary of Contents for Compliance Appliance
Page 1: ...Compliance Appliance Deployment Guide...
Page 31: ...9 Deployment scenarios 27 9 Deployment scenarios 9 1 Scenario 1 basic deployment...
Page 32: ...28 9 2 Scenario 2 deployment across a WAN...
Page 34: ...30 9 4 Scenario 4 non participating VCS...
Page 35: ...9 Deployment scenarios 31 9 5 Scenario 5 external organization...
Page 36: ...32 9 6 Scenario 6 VCS cluster...
Page 38: ...34 11 Call Flow within TCA...
Page 41: ......