TANDBERG D13691.03 User Manual
  1. Manuals
  2. Brands
  3. TANDBERG Manuals
  4. Controller
  5. D13691.03
  6. User manual
TANDBERG D13691.03 User Manual

TANDBERG D13691.03 User Manual

Border controller
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
TANDBERG Border Controller

User Manual

Software version Q3.0
D13691.03
This document is not to be reproduced in whole or in part without permission in writing from:

Advertisement

Table of Contents
loading

Related Manuals for TANDBERG D13691.03

Summary of Contents for TANDBERG D13691.03

  • Page 1: User Manual

    TANDBERG Border Controller User Manual Software version Q3.0 D13691.03 This document is not to be reproduced in whole or in part without permission in writing from:...

  • Page 2: Trademarks And Copyright

    Trademarks and copyright Copyright 1993-2006 TANDBERG ASA. All rights reserved. This document contains information that is proprietary to TANDBERG ASA. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form, or by any means, electronically, mechanically, by photocopying, or otherwise, without the prior written permission of TANDBERG ASA.

  • Page 3: Environmental Issues

    TANDBERG’s products, the environment will benefit from less use of polluting transport. TANDBERG’s wide use of the concepts of outsourcing makes the company itself a company with a low rate of emissions and effects on the environment.

  • Page 4: Operator Safety Summary

    TANDBERG Border Controller User Manual Operator Safety Summary For your protection, please read these safety instructions completely before operating the equipment and keep this manual for future reference. The information in this summary is intended for operators. Carefully observe all warnings, precautions and instructions both on the apparatus and in the operating instructions.
  • Page 5 TANDBERG Border Controller User Manual – If the apparatus has been subjected to excessive shock by being dropped, or the cabinet has been damaged – If the apparatus fails to operate in accordance with the operating instructions.

  • Page 6: Table Of Contents

    Contents 1 Introduction 1.1 TANDBERG Border Controller Overview ..... . . 2 Installation 2.1 Precautions ........
  • Page 7 TANDBERG Border Controller User Manual 9.4 Logged Events ........

  • Page 8: Introduction

    TANDBERG Border Controller User Manual 1 Introduction This User Manual is provided to help you make the best use of your TANDBERG Border Controller. A Border Controller is a key component of TANDBERG’s Expressway firewall traversal solution. Used in conjunction with a TANDBERG Gatekeeper or TANDBERG traversal enabled endpoints it allows calls to be made into and out of a secured private network.

  • Page 9: Tandberg Border Controller Overview

    TANDBERG Border Controller User Manual 1.1 TANDBERG Border Controller Overview On the front of the Border Controller there are three LAN interfaces, a serial port (Data 1) and an LED showing the power status of the system. The LAN 1 interface is used for connecting the system to your network, LAN interface 2 and 3 are disabled.

  • Page 10: Installation

    Power must be switched off before power supplies can be removed from or installed into the unit. 2.2 Unpacking The TANDBERG Border Controller is delivered in a special shipping box which should contain the following components: Border Controller unit Installation sheet...

  • Page 11: Mounting

    2.3 Mounting The Border Controller comes with brackets for mounting in standard 19” racks. Before starting the rack mounting, please make sure the TANDBERG Border Controller is placed securely on a hard, flat surface. 1. Disconnect the AC power cable.

  • Page 12: Border Controller Initial Configuration

    On the front of the chassis you will see the Power LED being lit. 2.6 Border Controller Initial Configuration The TANDBERG Border Controller requires some configuration before it can be used. This must be done using a PC connected to the serial port (Data 1) or by connecting to the system’s default IP address: 192.168.0.100.
  • Page 13 11. Review other system settings. You may want to set the following: (a) The name of the Border Controller. This is used to identify the Border Controller by the TANDBERG Management Suite. See the xConfiguration SystemUnit command in section 11.2.17 for more information on setting the name.

  • Page 14: Getting Started

    3 Getting started 3.1 System Administration To configure and monitor the TANDBERG Border Controller you can either use the web interface or a command line interface. The command line interface is available over SSH and Telnet, or through the serial port. The interface is the same using all three access methods. By default administration sessions remain active until you logout.

  • Page 15: Registration

    Consult the endpoint documentation for information on how to configure it with a Gatekeeper. NOTE Only traversal enabled endpoints can register with a TANDBERG Border Controller. All other registration requests will be rejected. Traversal enabled endpoints include all TANDBERG Expressway endpoints and third party endpoints which support the ITU H.460.18 and H.460.19...
  • Page 16 TANDBERG Border Controller User Manual Location Request to all the other Gatekeepers and Border Controllers on the system. Whilst conceptually simple, this sort of flat dial plan does not scale very well: adding or moving a Gatekeeper requires changing the configuration of every Gatekeeper and Border Controller;...

  • Page 17: Alternate Border Controllers

    TANDBERG Border Controller User Manual Figure 1: Adding a new zone 3.4 Alternate Border Controllers Alternate Border Controller support is provided to increase the reliability of your deployment. If one Border Controller becomes unavailable, perhaps due to a network or power outage, another will be used as an Alternate.

  • Page 18: Call Control

    TANDBERG Border Controller User Manual Figure 2: Alternate Border Controller configuration 3.5 Call Control When an endpoint wants to call another endpoint it presents the address it wants to call to the Border Controller using a protocol knows as RAS. The Border Controller tries to resolve this address and supplies the calling endpoint with information about the called endpoint.
  • Page 19 TANDBERG Border Controller User Manual Figure 3: Location decision flow diagram...

  • Page 20: Firewall Traversal

    TANDBERG Border Controller User Manual 3.6 Firewall Traversal The Border Controller works with the TANDBERG Gatekeeper, TANDBERG Expressway end- points and other endpoints which support the ITU H.460.18 and H.460.19 standards. In order to successfully traverse a firewall, the firewall is required to allow initial outbound traffic to des- ignated ports on the border controller and return traffic from those ports.

  • Page 21: Bandwidth Control

    TANDBERG Border Controller User Manual 4 Bandwidth Control The TANDBERG Border Controller allows you to control endpoints’ use of bandwidth on your network. Figure 4 shows a typical deployment: a broadband LAN, where high bandwidth calls are acceptable, a pipe to the internet with restricted bandwidth, and two satellite offices, each with their own restricted pipes.
  • Page 22 TANDBERG Border Controller User Manual Figure 5: Configuring a SubZone Links may be configured through the web interface on the Border Controller Configuration Links page, or through the command line using the following commands: xConfiguration Links Link [1..100] Name xConfiguration Links Link [1..100] Node1 Name xConfiguration Links Link [1..100] Node2 Name...

  • Page 23: Bandwidth Control And Firewall Traversal

    TANDBERG Border Controller User Manual xConfiguration Pipes Pipe [1..100] Bandwidth PerCall Mode xConfiguration Pipes Pipe [1..100] Bandwidth PerCall Limit Pipes may be shared between one or more links. This is used to model the situation where a site communicates with several other sites over the same broadband connection to the Internet.

  • Page 24: Bandwidth Control Examples

    If we now modify our deployment to include firewalls between the offices, we can use the firewall traversal capability of the TANDBERG Gatekeeper and Border Controller to maintain connectivity. In Figure 9, the endpoints in the enterprise register with the Gatekeeper, whilst those in the branch and home office register with the Border Controller.
  • Page 25 TANDBERG Border Controller User Manual Figure 9: Network Deployment with firewalls Figure 10: Border Controller example configuration The traversal subzone in Figure 10 may be used to control the amount of traffic flowing through the Border Controller itself. Because the Gatekeeper is only managing endpoints on the LAN, its configuration is simpler as shown in Figure 11.
  • Page 26 TANDBERG Border Controller User Manual Figure 11: Gatekeeper example configuration network. The default links may be restored by running the command: xCommand DefaultLinksAdd...

  • Page 27: Registration Control

    TANDBERG Border Controller User Manual 5 Registration Control The TANDBERG Border Controller can control which endpoints are allowed to register with it. Two separate mechanisms are provided: a simple Registration Restriction Policy and an authentication process based on user names and passwords. It is possible to use both mechanisms at once: authentication to verify an endpoint’s identity from a corporate directory and registration restriction...

  • Page 28: Authentication

    TANDBERG Border Controller User Manual 5.2 Authentication The TANDBERG Border Controller can use a user name and password based challenge-response scheme to permit registrations. For details of how to configure your endpoint with the appropriate information, please consult your endpoint manual.
  • Page 29 TANDBERG Border Controller User Manual To configure the Border Controller to use the LDAP server directory during authentication issue the following commands: xConfiguration Authentication Mode: On xConfiguration Authentication Database: LDAPDatabase The Border Controller needs to be configured with the area of the directory which will be searched for the communication device information.

  • Page 30: Uri Dialing

    TANDBERG Border Controller User Manual 6 URI Dialing If an alias is not located in the Border Controller’s list of registrations, it may attempt to find an authoritative Gatekeeper through the DNS system. URI dialing makes it easier for endpoints registered with different Gatekeepers or Border Con- trollers to call each other.
  • Page 31 TANDBERG Border Controller User Manual Figure 14: Configuring IP interface In our case Service is defined by the H.323 protocol suite to be h323ls and Proto is udp. Name corresponds to the host part of the H.323 URI. How you add the SRV record depends on the type of DNS server you are using. Instructions for...

  • Page 32: Example Traversal Deployments

    Controller is deployed on the public network to allow traversal across the firewalls. Endpoints 1001, 1002 may be any H.323 compliant endpoint. They will use the TANDBERG Gatekeeper to provide firewall traversal. Endpoint 1003 must be a TANDBERG endpoint which provides firewall traversal.

  • Page 33: Enterprise Gatekeepers

    In order to achieve this, the TANDBERG Gatekeeper is neighbored with the existing enterprise Gatekeeper as shown in Figure 16. The Enterprise Gatekeeper is also neighbored with the TANDBERG Gatekeeper.

  • Page 34: Neighbored Enterprises

    7.5 URI dialing from within the enterprise This diagram shows a deployment to support URI dialing to other enterprises. Turn URI dialing OFF on the TANDBERG Gatekeeper. You want to use the Border Controller to resolve any H.323 URI received.
  • Page 35 TANDBERG Border Controller User Manual From an endpoint in enterprise A, dial the full H.323 URI. For example, Ben@EnterpriseB.com. Border Controller B is registered in DNS as responsible for enterprise B and will receive the incoming call and route it accordingly.

  • Page 36: Call Policy

    TANDBERG Border Controller User Manual 8 Call Policy Your TANDBERG Border Controller allows you to set up policy to control which calls are allowed and even redirect selected calls to different destinations. You specify this policy by uploading a script written in the Call Processing Language (CPL). Each time a call is made the...
  • Page 37 TANDBERG Border Controller User Manual subfield The following table gives the definition of subfields for each alias type, if a subfield is not specified for the alias type being matched then the not-present action will be taken. address-type For all alias types the address-type subfield is the...

  • Page 38: Cpl Script Actions

    TANDBERG Border Controller User Manual 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 Border Controller 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 example in section 8.4).

  • Page 39: Unsupported Cpl Elements

    TANDBERG Border Controller User Manual 8.3 Unsupported CPL Elements The Border Controller does not currently support the following elements that are described in the CPL RFC. If an attempt is made to upload a script containing any of the following elements an error message will be generated and the Border Controller will continue to use its existing policy.
  • Page 40 TANDBERG Border Controller User Manual <address is="fred"> <address-switch field="origin" subfield="host"> <address subdomain-of="annoying.com"> <reject/> </address> <otherwise> <proxy/> </otherwise> <not-present> <reject/> </not-present> </address-switch> </address> </address-switch> </incoming> </cpl> 8.4.3 Call Redirection Redirect all calls to user ”barney” to voicemail. <cpl> <incoming> <address-switch field="destination">...

  • Page 41: Logging

    Border Controller product. For all messages logged from the tandberg process the message details field is structured to allow easy parsing. It consists of a number of human-readable name=value pairs, separated by a space.

  • Page 42: Event Levels

    TANDBERG Border Controller User Manual 9.3 Event Levels Events are classified by importance as detailed in the table below. Level 1 is considered the most important. The system has a configured logging level. Events of level numerically equal to and lower than the configured logging level are recorded in the event log.
  • Page 43 TANDBERG Border Controller User Manual Table 2: Level 1 Events (continued) Event Description Registration Removed A registration has been removed by the gate- keeper/border controller. The Reason event parameter specifies the reason why the regis- tration was removed. This is one of: Authentication change Conflicting zones...
  • Page 44 TANDBERG Border Controller User Manual Table 3: Events logged at level 2 Event Description Incoming Message An incoming message has been received Outgoing Message An outgoing message has been sent 9.4.1 Event data Each Event will have associated data fields. Fields are listed below in the order in which they appear in the log message.
  • Page 45 TANDBERG Border Controller User Manual Table 4: Event data (continued) Field Description Applicable events Src-ip Specifies the source IP ad- dress (the IP address of the Call Attempted device attempting to estab- Call Bandwidth Changed lish communications). Call Connected source IP is recorded in the...

  • Page 46: Remote Logging

    TANDBERG Border Controller User Manual Table 4: Event data (continued) Field Description Applicable events Dst-Alias If present, the first H.323 Registration Accepted Alias associated with the Registration Removed recipient of the message Registration Rejected If present, the first E.164 Call Attempted...

  • Page 47: Software Upgrade

    NOTE To upgrade the Border Controller, a valid Release key and software file is required. Contact your TANDBERG representative for more information. NOTE Configuration is restored after performing an upgrade but we recommend that you make a backup of the existing configuration using the TANDBERG Management Suite before performing the upgrade. 10.1 Upgrading Using HTTP(S) To upgrade using HTTP(S), do the following: Point your browser at the IP address of the Border Controller.

  • Page 48: Upgrading Using Scp

    Make sure the system is turned on and available on IP. Upload the release key file using scp to the /tmp folder on the system e.g. scp release-key root@10.47.8.247:/tmp/release-key Enter password when prompted. Copy the software image using SCP. The target name must be /tmp/tandberg-image.tar.gz, e.g. scp s42100q30.tar.gz root@10.47.8.247:/tmp/tandberg-image.tar.gz...
  • Page 49 TANDBERG Border Controller User Manual Enter password when prompted. Wait until the software has installed completely. This should not take more than two minutes. Reboot the system. After about four minutes the system will be ready to use.

  • Page 50: Command Reference

    TANDBERG Border Controller User Manual 11 Command Reference This chapter lists the basic usage of each command. The commands also support more advanced usage, which is outside the scope of this document. 11.1 Status The status root command, xstatus, returns status information from the Border Controller.
  • Page 51 TANDBERG Border Controller User Manual 11.1.3 externalmanager xstatus ExternalManager Returns information about the external manager. The External Manager is the remote system (such as the Tandberg Management System (TMS)) used to manage the endpoints and network infrastructure. Address IP address of the external manager.
  • Page 52 TANDBERG Border Controller User Manual 11.1.8 NTP xstatus NTP Reports the status of any connection to an NTP server. 11.1.9 Pipes xstatus Pipes xstatus Pipes Pipe n Reports call and bandwidth information for all pipes on the system. 11.1.10 Registrations...

  • Page 53: Configuration

    TANDBERG Border Controller User Manual 11.1.13 SystemUnit xstatus SystemUnit Reports information about the system as follows: Product name Uptime Software version Software name Release date Number of calls supported Number of registered endpoints and services supported Hardware serial number 11.1.14 Zones xstatus Zones Reports the call and bandwidth information for all zones on the system.
  • Page 54 ExternalManager Address: <IPAddr> Sets the IP address of the External Manager. The External Manager is the remote system(such as the TANDBERG Management System (TMS)) used to manage endpoints and network infrastructure. xConfiguration ExternalManager Path: <path> Sets the URL of the External Manager.
  • Page 55 TANDBERG Border Controller User Manual xConfiguration Gatekeeper Alternates Alternate [1..5] Address: <IPAddr> Set the IP address of an alternate Border Controller. Up to 5 alternates may be configured. When the Border Controller receives a Location Request, all alternates will also be queried.
  • Page 56 HTTP for improved security. 11.2.6 IP Configuration of IP related parameters. The TANDBERG Border Controller may be configured to use either IPv4 or IPv6. When entering IPv4 addresses, dotted quad notation is used: 127.0.0.1, when using IPv6 addresses are entered in colon hexadecimal form: FE80::2AA:FF:FE9A:4CA2.
  • Page 57 TANDBERG Border Controller User Manual The IPv4 gateway of the system. xConfiguration IP V6 Address: <IPAddr> The IPv6 address of the system. xConfiguration IP V6 Gateway: <IPAddr> The IPv6 gateway of the system. All the IP commands listed above require a system restart before they take effect.
  • Page 58 TANDBERG Border Controller User Manual Specifies the first node of a link. A node name may be either a Zone name or a SubZone name. xConfiguration Links Link [1..100] Node2 Name: <nodename> Specifies the second node of a link. A node name may be either a Zone name or a SubZone name.
  • Page 59 Turn on/off SNMP support. You must restart the system for changes to take effect. xConfiguration SNMP SystemContact: <name> Used to identify the system contact via SNMP tools such as TANDBERG Management Suite or HPOpenView. You must restart the system for changes to take effect. xConfiguration SNMP SystemLocation: <name>...
  • Page 60 TANDBERG Border Controller User Manual 11.2.16 Subzones xConfiguration SubZones DefaultSubZone Bandwidth PerCall Limit: <1..100000000> Per call bandwidth of the default subzone. xConfiguration SubZones DefaultSubZone Bandwidth PerCall Mode: <None/Limited/Unlimited> Whether or not the default subzone is enforcing total bandwidth restrictions. None corresponds to no bandwidth available.
  • Page 61 TANDBERG Border Controller User Manual xConfiguration SubZones SubZone [1..100] Bandwidth Total Mode: <None/Limited/Unlimited> Whether or not the indexed subzone is enforcing total bandwidth restrictions. None corresponds to no bandwidth available. xConfiguration SubZones SubZone [1..100] Name: <subzonename> Name of the indexed subzone.
  • Page 62 Traversal zones control how the Border Controller communicates with a Gatekeeper which it is cooperating with to provide firewall traversal. xConfiguration Zones TraversalZone [1..50] Name: <name> Sets the name of the TANDBERG Gatekeeper which is allowed to connect to this Border Controller. xConfiguration Zones TraversalZone [1..100] HopCount: <count>...

  • Page 63: Command

    TANDBERG Border Controller User Manual xConfiguration Zones TraversalZone [1..100] Match [1..5] Pattern Behaviour: <Strip/Leave> Determines whether the matched pattern should be removed from the alias before an LRQ is sent to the indicated zone. xConfiguration Zones Zone [1..100] Name: <name>...
  • Page 64 TANDBERG Border Controller User Manual xcommand ? To get usage information for a specific command, type xcommand <commandname> ? 11.3.1 AllowListAdd xCommand AllowListAdd <allowed alias> Adds an entry to the allow list, used by the registration restriction policy. 11.3.2 AllowListDelete xCommand AllowListDelete <index>...
  • Page 65 TANDBERG Border Controller User Manual 11.3.7 DefaultLinksAdd xCommand DefaultLinksAdd Restores the factory default links for bandwidth control. 11.3.8 DefaultValuesSet xCommand DefaultValuesSet Level <level> Resets system parameters to default values. Level 1 will reset most parameters. There are currently no level 2 parameters, so setting that level has the same effect as setting level 1. Level 3 resets all level 1 and 2 parameters as well as the following: IP address, subnet mask, gateway and interface speed.
  • Page 66 TANDBERG Border Controller User Manual 11.3.12 FeedbackRegister xCommand FeedbackRegister <ID> <URL> <Expression> Registers for notifications on the event or status change described by the Expression. Notifica- tions are sent in XML format to the specified URL. Up to 15 Expressions may be registered for each of 3 feedback IDs.
  • Page 67 TANDBERG Border Controller User Manual 11.3.17 OptionKeyAdd xCommand OptionKeyAdd <key> Adds a new option key. 11.3.18 OptionKeyDelete xCommand OptionKeyDelete <index> Deletes the indexed option key. 11.3.19 PipeAdd xCommand PipeAdd <name> <totalmode> <total> <percallmode> <percall> Adds and configures a new pipe.

  • Page 68: History

    11.3.24 TraversalZoneAdd xCommand TraversalZoneAdd Creates a new traversal zone, allowing a TANDBERG Gatekeeper to connect to the Border Controller. Up to 50 such zones may be created. The new zone is pre-configured with a link to the traversal subzone and with a pattern match mode of AlwaysMatch.

  • Page 69: Feedback

    TANDBERG Border Controller User Manual To show a specific set of history data, type: xhistory <name> xhistory calls xhistory calls call <n> Displays history data for up to the last 255 calls handled by the Border Controller. Call entries are added to the Call History on call completion. Call histories are listed in reverse chronological order of completion time.

  • Page 70: Other Commands

    TANDBERG Border Controller User Manual xFeedback Register Event/<CallAttempt/Connected/Disconnected/ConnectionFailure/Registration/ Unregistration/Bandwidth/ResourceUsage> Registers for feedback on the occurrence of the chosen Event, e.g.: xFeedback Register Event/CallAttempt To register for all available Events, use: xFeedback Register Event Registering for the ResourceUsage event will return the entire ResourceUsage structure every time one of the ResourceUsage fields changes.
  • Page 71 TANDBERG Border Controller User Manual 11.6.4 Relkey relkey Displays the release key that this software has been installed with. 11.6.5 Syslog syslog <level> [ipaddr] [ipaddr] Enables tracing to the console. level Specifies the detail at which to trace. 0-3, 3 gives most logging.

  • Page 72: A Appendix: Configuring Dns Servers

    TANDBERG Border Controller User Manual A Appendix: Configuring DNS Servers In the examples below, we set up an SRV record to handle H.323 URIs of the form user@example.com These are handled by the system with the fully qualified domain name of gatekeeper1.example.com which is listening on port 1719, the default registration port.
  • Page 73 TANDBERG Border Controller User Manual as expected. nslookup -querytype=srv h323ls. udp.example.com and check the output.

  • Page 74: B Appendix: Configuring Ldap Servers

    TANDBERG Border Controller User Manual B Appendix: Configuring LDAP Servers B.1 Microsoft Active Directory B.1.1 Prerequisites These comprehensive step by step instructions assume that Active Directory is installed. For details on installing Active Directory please consult your Windows documentation. The following instructions are for Windows Server 2003 Enterprise Edition, if you are not using this version of Windows, your instructions may vary.

  • Page 75: Openldap

    TANDBERG Border Controller User Manual objectClass: h323Identity objectClass: h235Identity commUniqueId: comm1 h323Identityh323-ID: MeetingRoom1 h323IdentitydialedDigits: 626262 h235IdentityEndpointID: meetingroom1 h235IdentityPassword: mypassword Add the ldif file to the server using the command: ldifde -i -c DC=X <ldap base> -f filename.ldf This will add a single H.323 endpoint with an H.323 Id alias of MeetingRoom1 and an E.164 alias of 626262.
  • Page 76 TANDBERG Border Controller User Manual B.2.2 Installing the H.350 schemas The following ITU specification describes the schemas which are required to be installed on the LDAP server: H.350 Directory services architecture for multimedia conferencing - An LDAP schema to repre- sent endpoints on the network.
  • Page 77 TANDBERG Border Controller User Manual Add the H.350 objects Create an ldif file with the following contents: # MeetingRoom1 endpoint dn: commUniqueId=comm1,ou=h350,dc=my-domain,dc=com objectClass: commObject objectClass: h323Identity objectClass: h235Identity commUniqueId: comm1 h323Identityh323-ID: MeetingRoom1 h323IdentitydialedDigits: 626262 h235IdentityEndpointID: meetingroom1 h235IdentityPassword: mypassword Add the ldif file to the server using the command: slapadd -l <ldif file>...

  • Page 78: C Approvals

    Nemko. According to their Follow-Up Inspection Scheme, these agencies also perform production inspections at a regular basis, for all production of TANDBERG’s equipment. The test reports and certificates issued for the product show that the TANDBERG Border Controller, Type number TTC2-02, complies with the following standards.

  • Page 79: D Technical Specifications

    TANDBERG Border Controller User Manual D Technical Specifications System Capacity 500 registered traversal endpoints 100 traversal calls 100 zones Option keys may restrict the system to a lower capacity than specified above. Ethernet Interfaces 3 x LAN/Ethernet (RJ-45) 10/100 Base-TX (2 disabled)
  • Page 80 TANDBERG Border Controller User Manual Physical Dimensions Height: 4.35 cm (1.72 inches) Width: 42.6 cm (16.8 inches) Depth: 22.86 cm (9 inches) 1U rack mounted chassis Power supply 90 264V full range @47 63 Hz Certification LVD 73/23/EC EMC 89/366/ECC...
  • Page 81 TANDBERG Border Controller User Manual References [1] ITU Specification: H.235 Security and encryption for H-Series (H.323 and other H.245- based) multimedia terminals [2] ITU Specification: H.350 Directory services architecture for multimedia conferencing [3] http://www.ietf.org/rfc/rfc2782.txt [4] http://www.ietf.org/rfc/rfc3164.txt [5] http://www.ietf.org/rfc/rfc3880.txt [6] DNS and BIND Fourth Edition Albitz and Liu, O’Reilly and Associates, ISBN: 0-596-00158-4...

  • Page 82: E Glossary

    Border Controller to register and place calls. Traversal call An H.323 call which uses a Border Controller. The Border Controller cooperates with the endpoint or TANDBERG gatekeeper to allow communication through a firewall. All signalling and media is routed through the Border Controller.
  • Page 83 Index about, 63 firewall, 13, 16, 75 ActiveDirectory, see LDAP servers gatekeeper discovery, 6, 8, 48 Admission Request, 75 alias, 8, 75 H.235, 21, see also authentication, 47 AllowList, 20, 49 H.323 AllowListAdd, 57 ID, 11 AllowListDelete, 57 alternate gatekeeper, 9–10, 48, 56 URI, 11 authentication, 21–22, 32, 47, 51 H.350, see also LDAP, 22...
  • Page 84 TANDBERG Border Controller User Manual OpenLDAP, see LDAP servers option key, 51, 75 password, 5, 54 default, 5, 7 recovery, 7 pattern, 61 pipe, 15–17, 51–52 PortRegistration, 45, 63, 75 prefix, 9 RAS, 11, 75 registration restriction policy, 20, 57...

Table of Contents