TANDBERG Compliance Appliance Deployment Manual
  1. Manuals
  2. Brands
  3. TANDBERG Manuals
  4. Software
  5. Compliance Appliance
  6. Deployment manual
TANDBERG Compliance Appliance Deployment Manual

TANDBERG Compliance Appliance Deployment Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Compliance Appliance™
Deployment Guide

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Compliance Appliance and is the answer not in the manual?

Questions and answers

Related Manuals for TANDBERG Compliance Appliance

Summary of Contents for TANDBERG Compliance Appliance

  • Page 1 Compliance Appliance™ Deployment Guide...
  • Page 2 TANDBERG Limited reserves the right to revise this documentation and to make changes in content from time to time without obligation on the part of TANDBERG Limited to provide notification of such revision or change. TANDBERG Limited provides this documentation without warranty, term, or...

  • Page 3: Table Of Contents

    Table of contents About this guide ....................1 1.1 Who is it for? ....................1 1.2 When to use it ....................1 1.3 More information? ..................1 1.4 Terminology ....................1 How the TCA enables compliance ................ 3 2.1 Scalable ......................3 2.2 Flexible ......................
  • Page 4 7.2 What is secure and what isn’t ..............19 Creating the policy file ..................20 8.1 Specifying which endpoints to record ............20 8.2 How the policy file directs these calls to the TCA ........20 8.3 Commented policy file (all calls recorded) ..........22 8.4 Route selected calls to TCA ...............

  • Page 5: About This Guide

    VCS systems by editing policy files. 1.2 When to use it Use this guide in combination with the Compliance Appliance Getting Started Guide and the Compliance Appliance Release Notes when you are installing a TCA. This guide will help you to work out how best to configure the TCA to meet an organization’s compliance needs.
  • Page 6 XGA – 1024x768 SXGA – 1280x1024 HD – 1280x720 Storage-attached network Network-attached storage TANDBERG Compliance Appliance™ transcode The process by which TCA decrypts (if necessary) then converts recordings to lower resolutions (if required) and copies a MPEG4 formatted file to external storage.

  • Page 7: How The Tca Enables Compliance

    TANDBERG have designed the TCA to be scalable, flexible, seamless and always on. These attributes make the TCA transparent to the users of the video conferencing network. Deployed correctly, the TCA provides a complete archive of all recorded conferences that can be stored in a range of resolutions.

  • Page 8: Licenses

    Release 1 of TCA supports 100 licenses, which means that it can record up to 50 point-to-point calls simultaneously. You need as many VCS non-traversal licenses as the number of TCA licenses. Your customer will need to discuss license arrangements with a TANDBERG sales representative.

  • Page 9: Defining The Compliance Policy

    3 Defining the compliance policy 3 Defining the compliance policy 3.1 What is a compliance policy? To deploy the TCA in an organization you first need to understand its compliance team’s policy. This is just a set of rules that define which conferences the team wants to record, how long they want to keep the recordings and in what resolution.

  • Page 10: Who: Which Endpoints To Record

    3.3 Who: which endpoints to record The first thing to do is define the number of endpoints that need to be recorded and where they are, both geographically and in terms of their position on the network. You may want to create a matrix that lists: each endpoint address the country it’s in (if relevant)

  • Page 11: How Many Tcas: What Resolution To Record

    4 mb/s has much higher bandwidth requirements than one running 10 calls from videophones at 384 kb/s. The TANDBERG Management System (TMS) provides a range of reports that can help you to work out the average and peak bandwidths of the organization.

  • Page 12: Storage

    4 Storage 4.1 What we mean by ‘storage’ The TCA has over a terabyte of internal disk space which it uses to store the recordings temporarily until it transcodes them to external storage. When we say storage we mean the disk space provided by a network-attached storage device (NAS) or storage-attached network (SAN) to which the TCA is attached over a LAN or WAN link.

  • Page 13: How Much Storage Do You Need

    4 Storage The recordings from these TCAs are also stored in different external storage locations. Viewing the recordings of the boardroom and New York endpoints requires access to the storage in Tokyo, while viewing all the other recordings requires access to the London storage. 4.3 How much storage do you need? The decisive factors affecting storage requirements are: the number of calls you are recording...
  • Page 14 MCU and MCU URI_destination URI_TCA ID number_unique call ID.mp4 if the MCU dialed the endpoint. If you are using a TANDBERG Codian MCU and ‘Use conference name as caller ID’ is set on the MCU then the outputted recording will be in the format of ConfName_endpointName.

  • Page 15: Recording Indicators: When To Play Them

    4 Storage TCA does not delete incomplete transcodes or any other files from storage; this is the responsibility of the storage administrator. 4.3.5 If external storage is unavailable If the TCA is unable to transcode for any reason (e.g. storage becomes full, link to the storage becomes unavailable) the TCA will keep recording until its internal storage is full.
  • Page 16 4.4.1 Setting recording indicators Using the TCA Administration Application you set whether or not to display them to the endpoints involved in a call. The Recording Indicator is a global setting per TCA, so if an organization wants some endpoints to display the indicators while others don’t, it will need separate TCAs. 4.4.2 Example: General Mortgage Bank GMB wants to remind its directors that the board meetings are being recorded.

  • Page 17: Optimizing Tca Performance

    5 Optimizing TCA performance 5 Optimizing TCA performance To avoid call latency or other quality issues you need to consider the network configuration, the location of the endpoints and the physical placement of the TCAs. 5.1 Efficient media streaming When it records a call, the TCA interposes itself between the endpoints, so it’s important that it be physically as close to the endpoints as possible.
  • Page 18 5.3.1 Example: General Mortgage Bank GMB has a number of factors to consider when deciding where to put their TCAs: their main data centre and long-term storage facility is in London most of their calls are made in London between two office buildings there their compliance policy requires boardroom conferences to be recorded in at least VGA resolution local Japanese regulations stipulate that calls involving Japanese citizens must be stored in Japan the dealers don’t want the recording indicator to play every time they make a quick call, but the...

  • Page 19: Implementing The Compliance Policy

    6 Implementing the compliance policy 6 Implementing the compliance policy 6.1 The VCS Policy File As we said before, when TCA records a conference, it interposes itself between the endpoints. To make this possible, the network needs to be able to identify which endpoints need to be recorded so it can direct them to the TCA.

  • Page 20: Neighboring A Tca Using Zones

    6.2.2 Example: General Mortgage Bank GMB has 48 endpoints it needs to record, so they need a way to identify these to the TCAs. The bank has a fairly high turnover of dealer staff, so making a list of their URIs is not practical. Instead, they opt to rename the trader endpoints with an identifier, so j.smith@uk.gmb.com becomes...
  • Page 21 6 Implementing the compliance policy 6.3.2 How the VCS and TCA work together TCA works in much the same way as a VCS in ‘traversal mode’ in which the actual media stream is routed through the VCS. Each endpoint is registered to a specific VCS which identifies the endpoint by its IP address and URI.

  • Page 22: Turning Off Recording

    You can also use zones to set priorities that determine the order in which TCAs are chosen to record a call from a particular endpoint. For example, if you have three TCAs in zones A, B and C, and an endpoint in ‘Zone A’.

  • Page 23: Security

    7 Security 7 Security 7.1 Redundancy If you only have one TCA and it becomes unavailable for whatever reason, then any calls made until it becomes available again will fail. As with any network technology, it is a good idea to have a second ‘redundant’...

  • Page 24: Creating The Policy File

    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.
  • Page 25 <address regex="URI|url-ID"> <taa:location clear="yes" regex="(.*)@([A-Z,a-z,0-9,.,-]+)([:;]*)(.*)" replace="CAREC.\1@\2.CAXXX\3\4"> For example, if the URI joe.smith.trader@tandberg.com was passed to the policy file, the taa:location regular expression would change it to carec.joe.smith.trader@tandberg.com.caxxx. The TCA would then automatically recognize this URI as needing to be recorded.

  • Page 26: Commented Policy File (All Calls Recorded)

    Take a well formed SIP address and surround the address with “CAREC” and “CAXXX”. The regular expression pointed to by “regex” splits the SIP address, taking into account addresses such as joe.smith@tandberg.com:5060;transport=tcp. Note that the domain can only contain alphanumerics, dots and dashes. It maybe that some domains have other valid characters that may be missed by this expression.
  • Page 27 8 Creating the policy file <otherwise> This section is for H.323 addresses. <taa:location clear="yes" regex="(.*)" replace="CAREC\1"> <proxy/> </taa:location> </otherwise> </address-switch> </otherwise> </address-switch> </not-present> <otherwise> If there was an originating address, we do the same as above. <address-switch field="destination"> <address regex="CAREC[.](.*)"> <proxy/>...

  • Page 28: Route Selected Calls To Tca

    8.4 Route selected calls to TCA This version of the file specifies two endpoints to be recorded: joe.smith.office@tandberg.com and david.andrews.office@tandberg.com. <?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" subfield="alias-type"> <address regex="TRANSPORTID"> <reject status="reject" reason="IP address dialing not allowed in CA mode"/>...
  • Page 29 <address regex="CAREC[.](.*)"> <!-- This rule is required to avoid an infinite policy loop repeatedly adding the CAZonePrefix --> <proxy/> </address> <address regex="joe.smith.office@tandberg.com|david.andrews.office@tandberg.com"> <!-- Start compliant destination address, route the destination to the TCA --> <address-switch field="destination" subfield="alias-type"> <address regex="URI|url-ID"> <!-- SIP addresses -->...
  • Page 30 <taa:location clear="yes" regex="(.*)@([A-Z,a-z,0-9,.,-]+)([:;]*)(.*)" replace="CAREC.\1@\2.CAXXX\3\4"> <proxy/> </taa:location> </address> <otherwise> <!-- H.323 addresses --> <taa:location clear="yes" regex="(.*)" replace="CAREC.\1"> <proxy/> </taa:location> </otherwise> </address-switch> <!-- End compliant origin address --> </address> <otherwise> <!-- Both ends non-compliant, just route normally --> <proxy/> </otherwise> </address-switch> </otherwise> </address-switch>...

  • Page 31: Deployment Scenarios

    9 Deployment scenarios 9 Deployment scenarios 9.1 Scenario 1 – basic deployment...

  • Page 32: Scenario 2 - Deployment Across A Wan

    9.2 Scenario 2 – deployment across a WAN...

  • Page 33: Scenario 3 - Deployment To Cater To Regional Variations In Regulations

    9 Deployment scenarios 9.3 Scenario 3 – deployment to cater to regional variations in regulations...

  • Page 34: Scenario 4 - Non-Participating Vcs

    9.4 Scenario 4 – non-participating VCS...

  • Page 35: Scenario 5 - External Organization

    9 Deployment scenarios 9.5 Scenario 5 – external organization...

  • Page 36: Scenario 6 - Vcs Cluster

    9.6 Scenario 6 – VCS cluster...

  • Page 37: Sample Tca Calculator

    10 Sample TCA calculator 10 Sample TCA calculator You can download this spreadsheet from www.tandbergnpd.com # SIP endpoints 20000 # H.323 endpoints # HD/Telepresence Call Speed (Kbs) Call Speed Call Speed 2048 Average Duration of call (hours) Average Duration of call Average Duration of call Resolution Resolution...

  • Page 38: Call Flow Within Tca

    11 Call Flow within TCA...

  • Page 39: Configuration Checklist

    Video Administrator Location Email Phone Storage Administrator Location Email Phone Network Administrator Location Email Compliance appliance details Appliance name IP address Physical location VCS Neighbour Recording resolution Transcoding resolution Transcoding bit rate Recording indicator? Attached storage Separate audio storage Endpoint pattern...
  • Page 40 Appliance name IP address Physical location VCS Neighbour Recording resolution Transcoding resolution Transcoding bit rate Recording indicator? Attached storage Separate audio storage Endpoint pattern Appliance name IP address Physical location VCS Neighbour Recording resolution Transcoding resolution Transcoding bit rate Recording indicator? Attached storage Separate audio storage Endpoint pattern...

Table of Contents