TANDBERG Border Controller User Manual Software version Q3.0 D13691.
TANDBERG Border Controller User Manual 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.
TANDBERG Border Controller User Manual Environmental Issues Thank you for buying a product which contributes to a reduction in pollution, and thereby helps save the environment. Our products reduce the need for travel and transport and thereby reduce pollution. Our products have either none or few consumable parts (chemicals, toner, gas, paper). Our products are low energy consuming products.
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.
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.
TANDBERG Border Controller User Manual Contents 1 Introduction 1.1 TANDBERG Border Controller Overview . . . . . . . . . . . . . . . . . . . . . . . 1 2 2 Installation 2.1 Precautions . . . . . . . . . . . . . . . 2.2 Unpacking . . . . . . . . . . . . . . . . 2.3 Mounting . . . . . . . . . . . . . . . . 2.4 Connecting Cables . . . . . . . . . . . 2.5 Switching on the System . . . . . . . . 2.6 Border Controller Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TANDBERG Border Controller User Manual 9.4 Logged Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.5 Remote Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 39 10 Software Upgrade 10.1 Upgrading Using HTTP(S) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.2 Upgrading Using SCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 40 41 11 Command Reference 11.1 Status . . . . . . 11.2 Configuration . .
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 ExpresswayTM 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.
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. The serial port (Data 1) is for connection to a PC, and power on is indicated by the Light Emitting Diode (Power) being lit.
TANDBERG Border Controller User Manual 2 Installation 2.1 Precautions • Never install communication equipment during a lightning storm. • Never install jacks for communication cables in wet locations unless the jack is specifically designed for wet locations. • Never touch uninstalled communication wires or terminals unless the communication line has been disconnected at the network interface. • Use caution when installing or modifying communication lines.
TANDBERG Border Controller User Manual 2.2.1 Installation site preparations • Make sure that the Border Controller is accessible and that all cables can be easily connected. • For ventilation: Leave a space of at least 10cm (4 inches) behind the Border Controller’s rear and 5cm (2 inches) on the sides. • The room in which you install the Border Controller should have an ambient temperature between 0◦ C and 35◦ C (32◦ F and 95◦ F) and between 10% and 90% non-condensing relative humidity.
TANDBERG Border Controller User Manual Then switch the power switch button on the back of the unit to ‘1’. 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. The IP address, subnet mask and gateway must be configured before use.
TANDBERG Border Controller User Manual Welcome to TANDBERG Border Controller Release Q3.0 SW Release Date: 2006-01-02 OK 10. Login with username admin and your password. 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. (b) Automatic discovery.
TANDBERG Border Controller User Manual 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. Session timeouts may be enabled using the xConfiguration Session TimeOut command.
TANDBERG Border Controller User Manual 3.1.2 Root Account The Border Controller provides a root account with the same password as the admin account. This account should not be used in normal operation, and in particular system configuration should not be conducted using this account: use the admin account instead. 3.2 Registration Before an endpoint can use the Border Controller it must first register with it. There are two ways an endpoint can register: • Automatically.
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; one call attempt can result in a flood of location requests. With 3 interconnected systems, an unknown alias can result in 28 LRQs, with 4 systems some 50,000 LRQs will be generated.
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. Alternates share responsibility for their endpoint community: an individual endpoint may be registered with any one of the Alternates.
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. The destination address can take several forms: IP address, H.323 ID, E.164 alias or a full H.323 URI. When an H.323 ID or E.
TANDBERG Border Controller User Manual 12 Figure 3: Location decision flow diagram
TANDBERG Border Controller User Manual 3.6 Firewall Traversal The Border Controller works with the TANDBERG Gatekeeper, TANDBERG Expressway endpoints 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 designated ports on the border controller and return traffic from those ports.
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.
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 xConfiguration xConfiguration xConfiguration xConfiguration Links Links Links Links Links Link Link Link Link Link [1..100] [1..100] [1..100] [1..100] [1..
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. Each link may have up to two pipes associated with it. This is useful for modeling two sites, each with their own broadband connection to the Internet backbone.
TANDBERG Border Controller User Manual 4.2 Bandwidth Control Examples One possible configuration for the deployment in Figure 4 is shown in Figure 8. Each of the offices is represented as a separate subzone, with bandwidth configured according to local policy. The enterprise’s leased line connection to the Internet, and the DSL connections to the remote offices, are modelled as separate pipes.
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. All of the endpoints in the enterprise will be assigned to the default subzone.
TANDBERG Border Controller User Manual Figure 11: Gatekeeper example configuration network.
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.
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. The Border Controller supports the ITU H.235 [1] specification for authenticating the identity of network devices with which theBorder Controller communicates.
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. This should be specified as the Distinguished Name (DN) in the directory under which the H.
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 Controllers to call each other. Without URI dialing, you need to neighbor all the systems to each other. This does not scale well as the number of systems grows.
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.
TANDBERG Border Controller User Manual 7 Example Traversal deployments 7.1 Simple Enterprise deployment Figure 15: Simple enterprise deployment Figure 15 shows a typical enterprise deployment. Endpoints 1001, 1002 and a Gatekeeper are deployed on a private network, separated from the public network by a firewall and NAT. Endpoint 1003 is on a separate private network, perhaps a home worker on an DSL connection.
TANDBERG Border Controller User Manual • Set example.com as the domain name you are using on both the Gatekeeper and Border Controller. • Update the DNS entry for example.com with an A record representing the Border Controller and an SRV record which returns the Border Controller’s A record as described in section 6.1 7.
TANDBERG Border Controller User Manual Figure 17: Dialing a public IP address In order to achieve this: • Within the Gatekeeper configuration — set ”Calls to unknown IP addresses” to Indirect. This setting will force the Gatekeeper to forward calls to any IP address it does not have locally registered to the TANDBERG Border Controller, thereby allowing the Border Controller itself to relay the call to the endpoint on the public IP address.
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. URI dialing will send all queries for a particular domain to the same Border Controller. If you want to have URI dialing covering multiple Border Controllers, nominate one as the master.
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).
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 user host port tel alias-type display For all alias types the address-type subfield is the string h323 For URI aliases this selects the username part. For H.323 ID’s it is the entire ID and for E.164 numbers it is the entire number.
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). 8.2 8.2.
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. • time-switch • string-switch • language-switch • time-switch • priority-switch • redirect • mail • log • subaction • lookup • remove-location 8.
TANDBERG Border Controller User Manual
8.4.3 Call Redirection Redirect all calls to user ”barney” to voicemail.TANDBERG Border Controller User Manual 9 Logging The Border Controller provides logging for troubleshooting and auditing purposes. The event log may be viewed from the command line by using the eventlog command, specifying the number of lines to display. Alternatively the web page System Status → Event Log may be used. 9.1 Controlling what is logged You can control the verbosity with which the Border Controller logs information. All events have an associated level in the range [1-3].
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. Table 1: Event levels 9.4 Level Level 1 (User) Description Easily human readable.
TANDBERG Border Controller User Manual Table 2: Level 1 Events (continued) Event Registration Removed Description A registration has been removed by the gatekeeper/border controller. The Reason event parameter specifies the reason why the registration was removed.
TANDBERG Border Controller User Manual Table 3: Events logged at level 2 Event Incoming Message Outgoing Message 9.4.1 Description An incoming message has been received An outgoing message has been sent Event data Each Event will have associated data fields. Fields are listed below in the order in which they appear in the log message. Table 4: Event data Field Protocol Description Specifies which protocol was used for the communication.
TANDBERG Border Controller User Manual Table 4: Event data (continued) Field Src-ip Description Applicable events Specifies the source IP address (the IP address of the • Call Attempted device attempting to estab• Call Bandwidth Changed • Call Connected lish communications). The source IP is recorded in the • Call Disconnected dotted decimal format: (num• Call Rejected • External Server Communiber).(number).(number).(number) cation Failure or the IPv6 colon separated format.
TANDBERG Border Controller User Manual Table 4: Event data (continued) Field Dst-Alias Description Applicable events • If present, the first H.323 Alias associated with the recipient of the message • If present, the first E.164 Alias associated with the recipient of the message Time Level 9.5 A full UTC timestamp in YYYY/MM/DD-HH:MM:SS format. Using this format permits simple ASCII text sorting/ordering to naturally sort by time. This is included due to the limitations of standard syslog timestamps.
TANDBERG Border Controller User Manual 10 Software Upgrade Software upgrade can be done in one of two ways: 1. Using a web browser (HTTP/HTTPS). 2. Using secure copy (SCP). NOTE To upgrade the Border Controller, a valid Release key and software file is required. Contact your TANDBERG representative for more information.
TANDBERG Border Controller User Manual • When the upload is completed you should see the following: • Press Restart. You should see a confirmation window: • The system will then perform a second reboot to restore system parameters. After 3–4 minutes, the Border Controller is ready for use. 10.2 Upgrading Using SCP Using SCP you need to transfer two files to the Border Controller: 1. A text file containing the release key. 2. A file containing the software image.
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.
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. To list all status information, type: xstatus Status is reported hierarchically beneath the status root.
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 Protocol URL 11.1.4 IP address of the external manager. Protocol used to communicate with the external manager. URL used to communicate with the external manager.
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 xstatus Registrations xstatus Registrations Registration n Returns a list of registered endpoints on the system or information about a specific registration. 11.1.
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. Also shows status of the zone as a whole and the status of each gatekeeper in the zone. 11.
TANDBERG Border Controller User Manual xConfiguration Authentication Credential [1..1000] Name: Specifies the username of a credential in the local authentication database. xConfiguration Authentication Credential [1..
TANDBERG Border Controller User Manual xConfiguration Gatekeeper Alternates Alternate [1..5] Address: 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. xConfiguration Gatekeeper Alternates Alternate [1..5] Port: Set the IP port of an alternate Border Controller. The default is 1719.
TANDBERG Border Controller User Manual Determines whether or not the CPL policy engine is active. The default is On. xConfiguration Gatekeeper Registration AllowList [1..1000] Pattern: Specifies a pattern in the registration allowed list. If one of an endpoint’s aliases matches one of the patterns in the AllowList, the registration will be allowed. xConfiguration Gatekeeper Registration DenyList [1..1000] Pattern: Specifies a pattern in the registration denied list.
TANDBERG Border Controller User Manual The IPv4 gateway of the system. xConfiguration IP V6 Address: The IPv6 address of the system. xConfiguration IP V6 Gateway: The IPv6 gateway of the system. All the IP commands listed above require a system restart before they take effect. xConfiguration IP DNS Server [1..5] Address: Sets the IP address of the DNS servers to be used when resolving domain names. Normally only the first DNS server will be queried for address resolution.
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: Specifies the second node of a link. A node name may be either a Zone name or a SubZone name. xConfiguration Links Link [1..100] Pipe1 Name: First pipe associated with a link. xConfiguration Links Link [1..100] Pipe2 Name: Second pipe associated with a link.
TANDBERG Border Controller User Manual Whether or not a given pipe is enforcing total bandwidth restrictions. None corresponds to no bandwidth available. xConfiguration Pipes Pipe [1..100] Bandwidth PerCall Limit: <1..100000000> Per call bandwidth of a pipe. xConfiguration Pipes Pipe [1..100] Bandwidth PerCall Mode: Whether or not a given pipe is enforcing per-call bandwidth restrictions. None corresponds to no bandwidth available. xConfiguration Pipes Pipe [1..
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: Whether or not the default subzone is enforcing total bandwidth restrictions. None corresponds to no bandwidth available. xConfiguration SubZones DefaultSubZone Bandwidth Total Limit: <1..
TANDBERG Border Controller User Manual xConfiguration SubZones SubZone [1..100] Bandwidth Total Mode: Whether or not the indexed subzone is enforcing total bandwidth restrictions. None corresponds to no bandwidth available. xConfiguration SubZones SubZone [1..100] Name: Name of the indexed subzone. xConfiguration SubZones SubZone [1..100] Subnet IP Address: IP to match an endpoint which belongs in this subzone. xConfiguration SubZones SubZone [1..
TANDBERG Border Controller User Manual xConfiguration Traversal UDPProbe KeepAliveInterval: Interval with which a UDP channel should be refreshed. RetryInterval: xConfiguration Traversal TCPProbe Interval with which a failed attempt to establish a TCP channel should be repeated. xConfiguration Traversal TCPProbe RetryCount: Number of attempts at re-establishing a failed TCP channel.
TANDBERG Border Controller User Manual xConfiguration Zones TraversalZone [1..100] Match [1..5] Pattern Behaviour: 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: An administrator specified name for the zone. xConfiguration Zones Zone [1..100] Gatekeeper [1..6] Address: Specifies the IP addresses of the gatekeepers in the zone.
TANDBERG Border Controller User Manual xcommand ? To get usage information for a specific command, type xcommand ? 11.3.1 AllowListAdd xCommand AllowListAdd Adds an entry to the allow list, used by the registration restriction policy. 11.3.2 AllowListDelete xCommand AllowListDelete Removes the pattern from the allow list at the specified index. 11.3.3 Boot xCommand Boot Reboots the Border Controller. This takes approximately 2 minutes to complete. 11.3.
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 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.
TANDBERG Border Controller User Manual 11.3.12 FeedbackRegister xCommand FeedbackRegister Registers for notifications on the event or status change described by the Expression. Notifications are sent in XML format to the specified URL. Up to 15 Expressions may be registered for each of 3 feedback IDs.
TANDBERG Border Controller User Manual 11.3.17 OptionKeyAdd xCommand OptionKeyAdd Adds a new option key. 11.3.18 OptionKeyDelete xCommand OptionKeyDelete Deletes the indexed option key. 11.3.19 PipeAdd xCommand PipeAdd Adds and configures a new pipe. 11.3.20 PipeDelete xCommand PipeDelete Deletes the indexed pipe. 11.3.21 RemoveRegistration xCommand RemoveRegistration Removes the specified registration. 11.3.
TANDBERG Border Controller User Manual 11.3.23 SubZoneDelete xCommand SubZoneDelete Deletes the indexed subzone. 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. 11.3.
TANDBERG Border Controller User Manual To show a specific set of history data, type: xhistory xhistory calls xhistory calls call 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.
TANDBERG Border Controller User Manual xFeedback Register Event/ 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.
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 [ipaddr] [ipaddr] Enables tracing to the console. level ipaddr Specifies the detail at which to trace. 0-3, 3 gives most logging. Specify up to 10 IP addresses to log information for, all if none specified. Setting syslog 0 will turn off tracing.
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. It is assumed that an A record already exists for gatekeeper1.example.com. If not, you will need to add one. A.
TANDBERG Border Controller User Manual as expected. nslookup -querytype=srv h323ls. udp.example.com and check the output.
TANDBERG Border Controller User Manual B B.1 B.1.1 Appendix: Configuring LDAP Servers Microsoft Active Directory 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.
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 -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. The entry also has H.
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 represent endpoints on the network. H.350.1 Directory services architecture for H.323 - An LDAP schema to represent H.323 endpoints. H.350.2 Directory services architecture for H.235 - An LDAP schema to represent H.235 elements.
TANDBERG Border Controller User Manual Add the H.
TANDBERG Border Controller User Manual C Approvals The product has been approved by various international approval agencies, among others: UL and 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.
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) System console port 2 x COM ports (front and rear), RS-323 DB-9 connector 2 x USB (disabled) ITU standards ITU-T H.323 version 4 including Annex O ITU-T H.460.18, H.460.19 ITU-T H.235 ITU-T H.
TANDBERG Border Controller User Manual Physical Dimensions Height: 4.35 cm (1.72 inches) Width: 42.6 cm (16.8 inches) Depth: 22.
TANDBERG Border Controller User Manual References [1] ITU Specification: H.235 Security and encryption for H-Series (H.323 and other H.245based) 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.
TANDBERG Border Controller User Manual E Glossary Alias The name an endpoint registers with the Border Controller. Other endpoints can then use this name to call it. ARQ, Admission Request An endpoint RAS request to make or answer a call. E.164 An ITU standard for structured telephone numbers. Each telephone number consists of a country code, area code and subscriber number.
Index about, 63 ActiveDirectory, see LDAP servers Admission Request, 75 alias, 8, 75 AllowList, 20, 49 AllowListAdd, 57 AllowListDelete, 57 alternate gatekeeper, 9–10, 48, 56 authentication, 21–22, 32, 47, 51 and CPL, 29 credential, 47 mode, 47 bandwidth control, 14–19 call policy, 29–33, 48 Call Processing Language, see CPL certificate, 22 clear, 63 CPL, 29 examples, 32–33 default IP address, 5, 58 DefaultLinksAdd, 19 DenyList, 20, 49 dial plan flat, 9 hierarchical, 9 structured, 9 directory gatekeeper, 9
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 time to live, 49 release key, 40 RestrictionPolicy, 49 RFC 2782, 23 RFC 3164, 39 scp, 52 upgrade using, 41–42 serial cable, 4, 5 serial interface, 7 serial port, 2, 5–7 SNMP, 52 ssh, 5–7, 52, 54 subzone, 14–15, 17, 52–54 default, 14, 18, 53 traversal, 16–18, 53
