Home

TANDBERG User Manual

1. B Appendix Configuring LDAP Servers B 1 Microsoft Active Directory 2 2 2 2 2 000 a B27 OpenLDAP Go e 4 5 Soave ee bee ace eae eee we ae es BE C Approvals D Technical Specifications E Glossary TANDBERG Gatekeeper User Manual TANDBERG Gatekeeper User Manual TANDBERG Gatekeeper User Manual 1 Introduction This User Manual is provided to help you make the best use of your TANDBERG Gatekeeper The main features of the TANDBERG Gatekeeper are e Pv4 and IPv6 support e Supports up to 100 neighboring zones e Flexible zone configuration with prefix and suffix support e Secure firewall traversal of any firewall or NAT when used in conjunction with a TANDBERG Border Controller e Supports up to 2500 registered endpoints e Up to 500 concurrent calls e Up to 100 traversal calls in conjunction with a TANDBERG Border Controller e URI and ENUM dialing with DNS enabling global connectivity e Can be used to control the amount of bandwidth used both within the Gatekeeper zone and to neighboring Border Controllers and Gatekeepers e Can limit total bandwidth usage and set maximum per call bandwidth usage with automatic down speeding if call exceeds per call maximum e Can be managed with TANDBERG Management Suite 11 0 or newer or as a standalone system with RS 232 Telnet SSH HTTP and HTTPS e Embedded setup wizard on serial port for initial configuration Note that features may vary depending on software pac
2. N O Oo A O 9 Connect the supplied null modem RS 232 cable from Data 1 to a PC running a terminal program Start a terminal program and configure it to use the serial port with baud rate 115200 8 data bits no parity 1 stop bit no flow control Power on the unit if it is not already on You should see the unit display start up information After approximately 2 minutes you will get a login prompt Enter username admin and your password The default password is TANDBERG You will be prompted if you want to run the install wizard Type y and press Enter none login admin Password Run install wizard n y Specify the following a The password you want to use for your system See section 3 1 1 for account details b The IP address of the system c The IP subnet mask of the system d The IP default gateway of the system e The Ethernet speed f The local zone prefix if any you want to use for the zone controlled by this system g Whether you want to use SSH to administer the system h Whether you want to use Telnet to administer the system You will be prompted to login again You should see a welcome message like this TANDBERG Gatekeeper User Manual Welcome to TANDBERG Gatekeeper Release N5 0 SW Release Date 2006 06 15 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 Gatekeepe
3. This is an attribute that can be added to a key request The Enhanced Key Usage extension includes the Server Authentication object identifier again this forms part of the key request Issued by a CA that both the domain controller and the client trust Include the Active Directory fully qualified domain name of the domain controller in the common name in the subject field and or the DNS entry in the subject alternative name extension B 2 OpenLDAP B 2 1 Prerequisites These instructions assume that an OpenLDAP server has already been installed For details on installing OpenLDAP see the documentation at http www openlidap org The following examples use a standard OpenLDAP installation on the Linux platform For installations on other platforms the location of the OpenLDAP configuration files may be different See the OpenLDAP installation documentation for details 80 TANDBERG Gatekeeper 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 H 350 1 Directory services architecture for H 323 An LDAP schema to represent H 323 end points H 350 2 Directory services architecture for H 235 An LDAP schema to represent H 235 ele ments The schemas can be downloaded in Idif format from the web inte
4. 3 17 LinkAdd xCommand LinkAdd lt linkname gt lt nodel gt lt node2 gt lt pipe1l gt lt pipe2 gt Adds a new link to the link list 14 3 18 LinkDelete xCommand LinkDelete lt index gt Deletes the indexed link 14 3 19 Locate xCommand Locate Alias lt alias gt HopCount lt count gt Runs the Gatekeeper s location algorithm to locate the endpoint identified by the given alias searching locally on neighbors and on systems discovered through the DNS system Results are reported back through the xFeedback mechanism 14 3 20 OptionKeyAdd xCommand OptionKeyAdd lt key gt Adds a new option key 14 3 21 OptionKeyDelete xCommand OptionKeyDelete lt index gt Deletes the indexed option key 14 3 22 PipeAdd xCommand PipeAdd lt name gt lt totalmode gt lt total gt lt percallmode gt lt percall gt Adds and configures a new pipe 72 TANDBERG Gatekeeper User Manual 14 3 23 PipeDelete xCommand PipeDelete lt index gt Deletes the indexed pipe 14 3 24 RemoveRegistration xCommand RemoveRegistration lt regid gt Removes the specified registration 14 3 25 SubZoneAdd xCommand SubZoneAdd lt name gt lt address gt lt prefixlength gt lt totalmode gt lt total gt lt percallmode gt lt percall gt Adds and configures a new subzone name User assigned label for the subzone address IP address for the sub zone prefix Number of bits which must match for an IP ad dress to be in this subz
5. 37 71 DisconnectCall 71 FeedbackDeregister 71 FeedbackRegister 71 FindRegistration 72 LinkAdd 72 LinkDelete 72 Locate 72 OptionKeyAdd 72 OptionKeyDelete 72 PipeAdd 72 PipeDelete 73 RemoveRegistration 73 SubZoneAdd 73 SubZoneDelete 73 ZoneAdd 10 73 ZoneDelete 73 xConfiguration Authentication 26 Credential 57 Database 57 89 TANDBERG Gatekeeper User Manual 90 LDAP 57 Mode 57 Ethernet Speed 57 ExternalManager Address 57 Path 57 Gatekeeper Alternates 58 AutoDiscovery 58 CallRouted 58 CallsToUnknownIPAddresses 12 58 CallTimeToLive 58 DNSResolution 58 Downspeed 58 59 ForwardLocationRequests 59 LocalDomain 59 LocalPrefix 59 Policy 59 Registration 59 TimeToLive 59 Unregistered 59 HTTPS Mode 60 IP 6 Address 60 DNS 60 Gateway 60 SubnetMask 60 V6 60 LDAP Encryption 62 Password 62 Server 62 UserDN 62 Links Link 62 LocalDomain DomainName 29 30 NTP Address 63 Pipes Pipe 63 Services CallTransfer 37 Session TimeOut 64 SNMP CommunityName 64 Mode 64 SystemContact 64 SystemLocation 64 SSH Mode 64 SubZones DefaultSubZone 64 SubZone 65 TraversalSubZone 65 SystemUnit Name 66 Password 7 66 Telnet Mode 66 TimeZone Name 66 Traversal AllowMediaDirect 66 Registration 66 Zones TraversalZone 66 67 Zone 67 68 zones 10 xFeedback deregister 74 0 74 Register 37 Event 75 History 75 Status 74 75 xHistory call
6. 81 TANDBERG Gatekeeper User Manual Add the H 350 objects Create an Idif file with the following contents MeetingRoom1 endpoint dn commUniqueId commi ou h350 dc my domain dc com objectClass comm0bject objectClass h323Identity objectClass h235Identity commUniqueId comm1 h323Identityh323 ID MeetingRoom1 h323IdentitydialedDigits 626262 h235IdentityEndpointID meetingroom1t h235IdentityPassword mypassword Add the ldif file to the server using the command slapadd 1 lt ldif_file gt 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 235 credentials of id meetingroom and password mypassword which are used during authentication B 2 4 Securing with TLS The connection to the LDAP server can be encrypted by enabling Transport Level Security TLS on the connection To do this you must create an X 509 certificate for the LDAP server to allow the Gatekeeper to verify the server s identity Once the certificate has been created you will need to install the following three files associated with the certificate onto the LDAP server e The certificate for the LDAP server e The private key for the LDAP server e The certificate of the Certificate Authority CA that was used to sign the LDAP server s certificate All three files should be in PEM file format The LDAP server must be configured to use the certificate To do this edit etc op
7. A11 2004 e UL 60950 1 1st Edition e CSA 60950 1 03 83 TANDBERG Gatekeeper User Manual D Technical Specifications System Capacity 2500 registered traversal endpoints 100 traversal calls at 384 kbps 500 non 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 5 including Annex O ITU T H 235 ITU T H 350 Security Features IP Administration passwords Management via SSH and HTTPS Software upgrade via HTTPS and SCP System Management Configuration via serial connection Telnet SSH HTTP HTTPS Software upgraded via HTTP HTTPS and SCP Environmental Data Operation temperature 0 C to 35 C 32 F to 95 F Relative humidity 10 to 90 non condensing 84 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 Hardware Hardware MTBF 80 479 hours Power supply 250 Watt 90 264V full range 47 63 Hz Certification LVD 73 23 EC EMC 89 366 ECC TANDBERG Gatekeeper User Manual 85 TANDBERG Gatekeeper 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 Speci
8. Make sure that the mounting space is according to the Installation site preparations in section 2 2 1 3 Attach the brackets to the chassis on both sides of the unit 4 Insert the unit into a 19 rack and secure it with screws 2 4 Connecting Cables Power cable Connect the system power cable to an electrical distribution socket LAN cable Connect a LAN cable from the LAN 1 connector on the front of the unit to your network Null modem RS 232 cable Connect the supplied null modem RS 232 cable between the Bor der Controller s Data 1 connector and the COM port on a PC 2 5 Switching on the System To start the TANDBERG Gatekeeper make sure that the following has been done e The power cable is connected e The LAN cable is connected TANDBERG Gatekeeper 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 Gatekeeper Initial Configuration The TANDBERG Gatekeeper 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 The Gatekeeper has to be configured with a static IP address Consult your network administrator for information on which addresses to use To set the initial configuration do the following 1
9. Off gt Controls whether or not third party call transfer is enabled The Gatekeeper must also be operating in call routed mode 63 TANDBERG Gatekeeper User Manual 14 2 14 Session xconfiguration Session TimeOut lt 0 65534 gt Controls how long an adminstration session HTTPS Telnet or SSH may be inactive before the session is timed out A value of 0 turns session time outs off The default is 0 You must restart the system for changes to take effect 14 2 15 SNMP xconfiguration SNMP CommunityName lt name gt SNMP Community names are used to authenticate SNMP requests SNMP requests must have this password in order to receive a response from the SNMP agent in the Gatekeeper You must restart the system for changes to take effect xconfiguration SNMP Mode lt On Off gt Turn on off SNMP support You must restart the system for changes to take effect xconfiguration SNMP SystemContact lt name gt Used to identify the system contact via SNMP tools such as TANDBERG Management Suite or HPOpenvView You must restart the system for changes to take effect xconfiguration SNMP SystemLocation lt name gt Used to identify the system location via SNMP tools such as TANDBERG Management Suite or HPOpenView You must restart the system for changes to take effect 14 2 16 SSH xconfiguration SSH Mode lt Qn Off gt Enables disables SSH and SCP support You must restart the system for changes to take effect 14 2 17 S
10. Status a System Configuration Gatekeeper Configuration IP SNMP Misc Upgrade IP Configuration Configuration IP Etheret Speed Auto i IP Protocol fina yy IP Address foss o IP Subnet Mask pss2ss230 tala ahi effect the system must be restarted IP Gateway foss2 5 IPV6 Address IPV6 Gateway Address 1 10 44 8 7 Address 2 f o 0 0 Address 3 0 0 0 Address 4 0 0 0 5 Address 5 0 0 0 o Domain Date and Time Settings NTP Server 10 44 8 1 Server Status Active 10 44 8 1 123 Timezone Europe London zi oO Q 8 e Save Restart pe a gt a Figure 18 Configuring IP interface been used to locate the Gatekeeper Depending on which was used the received URI could be in one of three forms e user 10 0 0 1 e user srv record domain name e user a record domain name Each of these should be able to discover an endpoint registered as either user or user a record domain name On receipt of the URI the Gatekeeper will modify the URI by removing the and host if the host matches e The IPv4 or IPv6 address of the Gatekeeper e The system name of the system The Gatekeeper will then search for registrations which match either the modified URI or the modified URI with the LocalDomain DomainName appended 7 3 DNS Records URI dialing relies on the presence of records in the DNS information for the zone For preference SRV records should be used These specify the location of a server for
11. a particular protocol and domain Their format is defined by an Internet standard 3 as _Service _Proto Name TTL Class SRV Priority Weight Port Target 29 TANDBERG Gatekeeper User Manual The Gatekeeper supports two types of service record as defined by H 323 Annex O These are Location and Call with Service set to 3231s and h323cs respectively In our case _Service is defined by the H 323 protocol suite to be _h3231s and Proto is _udp Name corresponds to the host part of the H 323 URI When the Gatekeeper receives a request to call fred example com it will attempt to locate the destination using the DNS system if it cannot be found otherwise First the Gatekeeper will query for a Location SRV record to discover the authoritative Gatekeeper for the destination DNS zone If is not located the Gatekeeper will query for a Call SRV record and try to place the call to that address If no appropriate SRV record can be located the Gatekeeper will fall back to looking for an A or AAAA record for the domain If a record is found a call will be placed to that address If you intend to use URI dialing you should provide at least a Location SRV record it provides the most flexibility and the simplest configuration Call SRV records and A AAAA records are intended primarily for use by endpoints which cannot participate in a location transaction exchanging LRQ and LCF Configuration of a system for a company with the domain name example com
12. address gt lt address switch gt lt incoming gt lt cpl gt 11 4 3 Call Redirection Redirect all calls to user barney to voicemail lt cpl gt lt incoming gt lt address switch field destination gt lt address is barney gt lt location clear yes url barney voicemail gt lt proxy gt lt location gt lt address gt lt otherwise gt lt proxy gt lt otherwise gt lt address switch gt lt incoming gt lt cpl gt 43 TANDBERG Gatekeeper User Manual 12 Logging The Gatekeeper 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 12 1 Controlling what is logged You can control the verbosity with which the Gatekeeper logs information All events have an associated level in the range 1 3 Level 1 refers to high level events such as registration requests and call attempts Level 2 events are recorded for incoming and outgoing message H 323 LDAP etc excluding noisy messages such as H 460 18 keep alives and H 245 video fast updates Level 3 events include some of these noisy events By default logging is set to level 1 12 2 Event log format The event log is displayed in an extension of the UNIX syslog format date time host_name facility_name lt PID gt message_details date and
13. and IPv6 IPv4 and IPv6 dual stack behavior is controlled by the command xConfiguration IPProtocol lt Both IPv4 IPv6 gt or using the web page System Configuration IP shown in figure 3 3 4 Registration Before an endpoint can use the Gatekeeper it must first register with it There are two ways an endpoint can register e Automatically e Manually by specifying the IP address of the Gatekeeper You can disable automatic registration on the Gatekeeper See auto discovery in section 14 2 for more information When registering the endpoint registers with one or more of the following e One or more H 323 IDs e One or more E 164 aliases Users of other registered endpoints can then call the endpoint by using either the H 323 ID a URI an E 164 alias or one of the services It is recommended that you do not use aliases that reveal sensitive information Due to the nature of H 323 call setup information is exchanged in an unencrypted form TANDBERG Gatekeeper User Manual Overview System Status a System Configuration Gatekeeper Configuration IP SNMP Misc Upgrade IP Configuration Configuration IP Ethamet Speed Auto zi IP Protocol IPv4 j IP Address 10 44 8 30 For the settings to take effect the system must be restarted IP Subnet Mask 55 255 248 0 Eor promaire rE IP Gateway 10 44 8 254 IPV6 Address IPV6 Gateway DNS Address 1 i0 44 8 7 Address 2 f o 0 0 Address 3 f o 0 0 i Addres
14. connectivity In Figure 13 the endpoints in the enterprise register with the Gatekeeper whilst those in the branch and home office register with the Border Controller 21 TANDBERG Gatekeeper User Manual Enterprise Border ey MCU May ay Figure 13 Network Deployment with firewalls Enterprise Home Pipe Pipe Home Office Border Controller Traversal sub zone Home sub zone Cc Branch Branch Office Traversal Zone Branch sub zone Figure 14 Border Controller example configuration Figure 14 shows how the Border Controller could be configured for the deployment in Figure 13 The introduction of the firewalls means that there is no longer any direct connectivity between the Branch and Home offices All traffic must be routed through the Border Controller This is shown by the absence of a link between the Home and Branch subzones The Traversal Zone in Figure 14 represents the Enterprise Gatekeeper The Border Controller will consume bandwidth from the Traversal Zone for all calls placed to endpoints managed by the Enterprise Gatekeeper In this example we have assumed that there is no bottleneck on the link between the Border Controller and the Enterprise network so have not placed a pipe on this link If you want to limit the amount of traffic flowing through your firewall you could provision a pipe on this link The traversal subzone in Figure 14 may be used to control the amount
15. for Windows Server 2003 Enterprise Edition if you are not using this version of Windows your instructions may vary The following ITU specifications describe the schemas which are required to be installed on the Active Directory server H 350 Directory services architecture for multimedia conferencing An LDAP schema to repre sent endpoints on the network H 350 1 Directory services architecture for H 323 An LDAP schema to represent H 323 end points H 350 2 Directory services architecture for H 235 An LDAP schema to represent H 235 ele ments The schemas can be downloaded in Idif format from the web interface on the Gatekeeper To do this navigate to the Gatekeeper Configuration Files page and click on the links for the schemas Copy the downloaded schemas to the Active Directory server Open a command prompt and for each file execute the following command ldifde i c DC X lt ldap_base gt f filename ldf Where lt ldap_base gt is the base DN for your Active Directory server B 1 2 Adding H 350 objects Create the organizational hierarchy Open up the Active Directory Users and Computers MMC snap in Under your base DN right click and select New Organizational Unit Create an Organizational unit called h350 NOTE It is good practice to keep the H 350 directory in its own organizational unit to separate out H 350 objects from other types of objects This allows access controls to be setup which only allow the G
16. gt Controls the granularity of event logging with 1 being the least verbose 3 the most 62 TANDBERG Gatekeeper User Manual 14 2 10 NTP xconfiguration NTP Address lt IPAddr gt Sets the IP address of the NTP server to be used when synchronizing system time Accurate timestamps play an important part in authentication helping to guard against replay attacks 14 2 11 Option Key xConfiguration Option 1 64 Key lt optionkey gt Specify the option key of your software options xstatus system software configuration can be used to discover the existing options You must restart the system for changes to take effect 14 2 12 Pipes xconfiguration Pipes Pipe 1 100 Bandwidth Total Limit lt 1 100000000 gt Bandwidth associated with a pipe keyed by index xconfiguration Pipes Pipe 1 100 Bandwidth Total Mode lt None Limited Unlimited gt 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 lt 1 100000000 gt Per call bandwidth of a pipe xconfiguration Pipes Pipe 1 100 Bandwidth PerCall Mode lt None Limited Unlimited gt Whether or not a given pipe is enforcing per call bandwidth restrictions None corresponds to no bandwidth available xconfiguration Pipes Pipe 1 100 Name lt pipename gt Name for a pipe 14 2 13 Services xConfiguration Services CallTransfer Mode lt Qn
17. histories are listed in reverse chronological order of unregistration time 14 5 Feedback The feedback root command xfeedback is used to control notifications of Events and Status changes on the Gatekeeper A Feedback Expression describes an interesting event or change in status When a Feedback Expression is registered a notification will be displayed in the shell for each occurrence of the event described by that Expression Notifications will continue to be displayed for a given event until the Expression is deregistered To list all xfeedback commands type xfeedback To list all currently active feedback expressions type xfeedback list To register a feedback expression type xfeedback register lt expression gt To deregister the feedback expression with index jn type xfeedback deregister lt n gt To deregister all feedback expressions type xfeedback deregister 0 74 TANDBERG Gatekeeper User Manual xfeedback Register Status lt Calls Registrations gt Registers for feedback on changes in the chosen Status e g xfeedback Register Status Calls To register for all Status changes use xfeedback Register Status xfeedback Register History lt Calls Registrations gt Registers for feedback on History e g xfeedback Register History Calls To register for all History use xfeedback Register History xfeedback Register Event lt CallAttempt Connected Disconnected ConnectionFailure Registration Unregistration
18. is 31 TANDBERG Gatekeeper User Manual Overview System Status System Configuration amp Gatekeeper Configuration Gatekeeper Authentication Services Zones Traversa IZones SubZones Links Pipes Restrictions Credentials Files Gatekeeper Configuration Configuration Local prefix Call routed Auto discovery Calls to urknown IP addresses Allow calls from urregstered callers Fallback alias for urregstered caller destination Allow forwarding of location requests Allow DNS resolution aaqa A K Time to live seconds Call time to live seconds 5 DNS Suffix 2 DNS Suffix 3 DNS Suffix 4 CPL pdicy gt Downspeeding Allow downspeeding at total bandwidth limit Allow downspeeding at per call bandwidth limit F Local domain Domain name ENUM Allow ENUM resolution r DNS Suffix 1 fele4 arpa p ua pee I DNS Suffix 5 Figure 19 Setting the ENUM Zone order flag preference service regex replacement IN NAPTR 10 100 u E2U h323 h323 recipient example com order 10 and preference 100 determine the order in which NAPTR records will be processed Lowest order first with lowest preference being processed first in the case of matching order flag u determines the interpretation of the other fields in this record Only the value u is supported service states that this record is intended to describe E 164 to URI conversion for H 323 Its value must be E2U h32
19. might typically be e Arecord for box example com returns the IP address of the box e SRV record for h3231s _udp example com returns box example com e SRV record for h323cs _tcp example com returns box example com e System name set to box example com e LocalDomain DomainName Set to example com How you add the DNS records depends on the type of DNS server you are using Instructions for setting up two common DNS servers are given in Appendix A 30 TANDBERG Gatekeeper User Manual 8 ENUM dialing ENUM provides another DNS based dialing scheme Users dial an E 164 number a telephone number which is converted in to an H 323 URI by the DNS system The rules for URI dialing are then followed to place the call This allows you to retain the flexibility of URI dialing whilst having the simplicity of calling using just a number Before the DNS lookup can be performed the E 164 number must be transformed into a host name To do this the digits are reversed and separated by a dot similar to the way DNS PTR records are formed The DNS zone is then appended If an ENUM root of e 164 example com is being used and the dialled number is 47 67 125 125 then the transformed host name is 5 2 1 5 2 1 7 6 7 4 e164 example com RFC 3761 which defines the ENUM standard specifies that the DNS zone for ENUM is e164 arpa Use of this DNS zone requires that your E 164 numbers are assigned by an appropriate national regulatory body Not all countr
20. origin Match against the source aliases destination Match against the destination aliases original destination Match against the destination aliases If the selected field contains multiple aliases then the Gatekeeper will attempt to match each address node with all of the aliases before proceeding to the next address node i e an address node matches if it matches any alias 39 TANDBERG Gatekeeper 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 string h323 user 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 host For URI aliases this selects the domain name part If the alias is an IP address then this subfield is the complete address in dotted decimal form port For IP addresses this is the port number in deci mal tel For E 164 numbers this selects the entire string of digits alias type Gives a string representation of the type of alias The type is inferred from the format of the alias Possible types are Address Type Result URI url ID H 323 ID h323 ID Dialed Digits dialedDigits display Not defined for any alias types address The address construct is used within an address switch to specify addresses to matc
21. registration will be denied xconfiguration Gatekeeper Registration RestrictionPolicy lt None AllowList DenyList gt Policy in use to determine who may register with the system The default is None xconfiguration Gatekeeper TimeToLive lt 60 65534 gt The interval at which the system polls the endpoint in order to verify that it is still functioning Specified in seconds The default is 1800 seconds xconfiguration Gatekeeper Unregistered Caller Mode lt on off gt Specifies whether calls may be made by an unregistered endpoint Defaults to off xconfiguration Gatekeeper Unregistered Caller Fallback lt alias gt If the Gatekeeper receives a call setup containing no alias information place the call to this alias 59 TANDBERG Gatekeeper User Manual 14 2 5 HTTP HTTPS Command under the HTTP and HTTPS nodes control web access to the Gatekeeper xConfiguration HTTP Mode lt On Off gt Enables disables HTTP support You must restart the system for changes to take effect The default is On xconfiguration HTTPS Mode lt On Off gt Enables disables HTTPS support You must restart the system for changes to take effect The default is On If web access is required you are recommended to enable HTTPS and disable HTTP for improved security 14 2 6 IP Configuration of IP related parameters The TANDBERG Gatekeeper may be configured to use either IPv4 or IPv6 When entering IPv4 addresses dotted quad notation is used 127 0 0
22. the call to the unknown IP address without querying any neighbors The call setup would occur just as it would if the far end were registered directly to the local system Indirect upon receiving the call the Gatekeeper will query its neighbors for the remote address relying on the response from the neighbor to allow the ability for the call to be completed connecting through the routing rules as it would through the neighbor relationship Off this will not allow any endpoint registered directly to the Gatekeeper to call an IP address of any system not also registered directly to that Gatekeeper See 4 for further detail The default is Indirect xconfiguration Gatekeeper CallTimeToLive lt 60 65534 gt Interval in seconds at which endpoints are polled to verify that they are still in a call The default is 120 seconds xconfiguration Gatekeeper DNSResolution Mode lt OQn Off gt Determines whether or not DNS lookup of H 323 URI s is enabled on this system The default is On xconfiguration Gatekeeper Downspeed PerCall Mode lt On Off gt 58 TANDBERG Gatekeeper User Manual Determines whether or not the system will attempt to down speed a call if there is insufficient per call bandwidth configured to fulfill the request The default is On xconfiguration Gatekeeper Downspeed Total Mode lt Qn Off gt Determines whether or not the system will attempt to down speed a call if there is insufficient total bandwidth available
23. to fulfill the request The default is On xconfiguration Gatekeeper ForwardLocationRequests lt On Off gt Determines behavior on receipt of a location request LRQ from another Gatekeeper If set to on the Gatekeeper will first try to resolve the request locally If it cannot the request will be forwarded to neighbor Gatekeepers The default is On xconfiguration Gatekeeper LocalDomain DomainName DNS name of the domain that the Gatekeeper is responsible for Used when searching for matching endpoint registrations xconfiguration Gatekeeper LocalPrefix lt prefix gt Set the local zone prefix of the system xconfiguration Gatekeeper Policy Mode lt On Off gt Determines whether or not the CPL policy engine is active The default is On xconfiguration Gatekeeper Registration AllowList 1 1000 Pattern lt pattern gt 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 ConflictMode lt OQverwrite Reject gt Determines how the Gatekeeper will behave if an endpoint attempts to register aliases currently registered from another IP address The default is Reject xconfiguration Gatekeeper Registration DenyList 1 1000 Pattern lt pattern gt Specifies a pattern in the registration denied list If one of an endpoint s aliases matches one of the patterns in the DenyList the
24. without first switching the power OFF This product complies with directives LVD 73 23 EC and EMC 89 366 EEC Power must be switched off before power supplies can be removed from or installed into the unit Unpacking The TANDBERG Gatekeeper is delivered in a special shipping box which should contain the following components Gatekeeper unit Installation sheet User manual and other documentation on CD Rack ears and screws Kit with 4 rubber feet Cables Power cables One Ethernet cable One null modem RS 232 cable TANDBERG Gatekeeper User Manual 2 2 1 Installation site preparations e Make sure that the Gatekeeper is accessible and that all cables can be easily connected For ventilation Leave a space of at least 10cm 4 inches behind the Gatekeeper s rear and 5cm 2 inches on the sides e The room in which you install the Gatekeeper 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 e Do not place heavy objects directly on top of the Gatekeeper e Do not place hot objects directly on top or directly beneath the Gatekeeper Use a grounded AC power outlet for the Gatekeeper 2 3 Mounting The Gatekeeper comes with brackets for mounting in standard 19 racks Before starting the rack mounting please make sure the TANDBERG Gatekeeper is placed securely on a hard flat surface 1 Disconnect the AC power cable 2
25. xstatus Ethernet Speed Reports the currently active configuration of the Ethernet interface MacAddress The MAC address of the LAN 1 interface Speed The speed of the Ethernet link Reports Down if the link is down or not connected 53 TANDBERG Gatekeeper User Manual 14 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 Protocol Protocol used to communicate with the external manager URL URL used to communicate with the external manager 14 1 4 feedback xstatus Feedback xstatus Feedback n Returns all currently registered feedback expressions or the feedback expression at index n 14 1 5 IP xstatus IP Returns the active IP configuration of the system with IP address subnet mask and gateway If you have changed the IP configuration without rebooting xstatus IP will return the original settings currently in effect Address IP address SubnetMask IP subnet mask Gateway Default gateway DNS Server The DNS servers in use 14 1 6 LDAP xstatus LDAP Reports the status of any connection to an LDAP server 14 1 7 Links xstatus Links xstatus Links Link n Reports call and bandwidth information for all links on the system Name Name assigned to this link Calls A list of call in
26. 00000004 28 73 DNS Records 124000044 244860444008 Bea we ee wd 4 aoe ex 29 8 ENUM dialing 31 8 1 Configuring ENUM 0000 a 31 8 2 Configuring DNS NAPTR Records 0020 002 eee 31 9 Example Traversal deployments 33 9 1 Simple Enterprise deployment 200000 33 9 2 Enterprise Gatekeepers aoaaa ee 34 9 3 Dialing Public IP addresses 0 00000 eee ee 34 9 4 Neighbored enterprises 00000 35 9 5 URI dialing from within the enterprise 000000008 35 viii 10 Third Party Call Control 10 1 Placingacall 10 2 Transferringacall 10 3 Disconnectingacall 11 Call Policy 11 1 Making Decisions Based on Addresses 11 2 CPL Script Actions 11 3 Unsupported CPL Elements 11 4 CPL Examples 12 Logging 12 1 Controlling what is logged 12 2 Event log format 12 3 Event Levels 12 4 Logged Events 12 5 Remote Logging 13 Software Upgrade 13 1 Upgrading Using HTTP S 13 2 Upgrading Using SCP 14 Command Reference 14 1 Status 2 ee 14 2 Configuration 14 3 Command 14 4 History 22 0 0 2000 14 5 Feedback 14 6 Othercommands A Appendix Configuring DNS Servers A 1 Microsoft DNS Server anaa aaa A 2 Verifying the SRV record aaa aaa ee
27. 1 when using IPv6 addresses are entered in colon hexadecimal form 2001 db8 2AA FF FE9A 4CA2 xConfiguration IPProtocol lt Both IPv4 IPv6 gt Selects whether the Gatekeeper is operating in IPv4 IPv6 or dual stack mode xconfiguration IP Address lt IPAddr gt The IPv4 address of the system xconfiguration IP SubnetMask lt IPAddr gt The IPv4 subnet mask of the system xconfiguration IP Gateway lt IPAddr gt The IPv4 gateway of the system xconfiguration IP V6 Address lt IPAddr gt The IPv6 address of the system xconfiguration IP V6 Gateway lt IPAddr gt 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 lt IPAddr gt 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 If it fails to respond all DNS servers will be queried You must restart the system for changes to take effect xconfiguration IP DNS Domain Name lt name gt When attempting to resolve a domain name which is not fully qualified name will be appended to the domain name before the query to the DNS server is executed 60 TANDBERG Gatekeeper User Manual This parameter is only used when attempting to resolve server addresses such as LDAP servers NTP servers etc It plays no part in URI dialing see xconfiguration gatekeeper localdomain
28. 3 regex describes the conversion from the given E 164 number to an H 323 URI is a field separator The first part represents the entire E 164 number which is replaced with the second field recipient example com oo The last field of the NAPTR record replacement is not used and should be set to NOTE According to RFC 2915 NAPTR records may contain regex substitutions which are applied to the E 164 number to produce the H 323 URI This release of the Gatekeeper does not support this behaviour the NAPTR record is substituted for the E 164 number Once the DNS NAPTR for the ENUM lookup and SRV for the corresponding H 323 URI lookup are present ENUM dialing should be possible To verify your configuration you are recommended to use the lookup command to ensure that E 164 numbers can be resolved 32 TANDBERG Gatekeeper User Manual 9 Example Traversal deployments 9 1 Simple Enterprise deployment Enterprise Border Controller m e a Gar _ al MCU Gatekeeper Figure 20 Simple enterprise deployment Figure 20 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 A Border Controller is deployed on the public network to allow traversal across the firewalls Endpoints 1001 1002
29. 4 number In that case the Gatekeeper should be configured to strip prefixes before placing the Location Request A structured dial plan will minimize the number of location requests issued when a call is attempted but as described above still requires a fully connected mesh of all Gatekeepers and Border Controllers in your deployment A hierarchical dial plan can simplify this One Gatekeeper is nominated as the directory gatekeeper for the deployment All Border Controllers and public Gatekeepers are neighbored with it and vice versa There is no need to neighbor the Border Controllers and public Gatekeepers with each other Adding a new Border Controller or public Gatekeeper now only requires changing configuration on that system and the Directory Gatekeeper Failure of the directory gatekeeper could cause significant disruption to communications Con sideration should be given to the use of Alternate Gatekeepers section 3 6 for increased resilience Neighbors are added and zones configured through the command line interface using the xconfiguration zones family of command xCommand ZoneAdd or through the web interface Gatekeeper Configuration Zones as shown in Figure 4 The prefixes and suffixes described above are formed using patterns each zone may have up to 5 patterns assigned each of which may be defined as a prefix or a suffix Patterns are not used and not displayed on the web interface if the pattern match mode is set to alw
30. 6 8 60 IP address default 5 70 LDAP 25 27 54 57 62 over TLS 27 80 82 schema 79 servers 79 82 88 ldif 79 81 license 76 link 17 18 23 default 70 LocalPrefix 59 Location Request 87 logging event levels 45 lookup 32 LRQ 59 monitor alternate 58 NAPTR record 31 32 neighbor 31 neighbor gatekeeper 9 10 19 35 36 59 NTP 63 OpenLDAP see LDAP servers option key 63 password 5 7 66 default 5 7 recovery 7 pipe 18 19 22 63 prefix 10 RAS 12 87 registration restriction policy 24 69 time to live 59 release key 50 relkey 76 RestrictionPolicy 59 RFC 2782 29 RFC 2915 31 RFC 3164 49 RFC 3761 31 scp 64 upgrade using 51 52 serial cable 4 5 serial interface 7 serial port 2 5 7 SNMP 64 SRV record 32 ssh 5 7 64 66 subzone 17 18 21 64 65 default 17 23 64 TANDBERG Gatekeeper User Manual traversal 21 23 65 suffix 10 syslog 76 system name 29 30 TANDBERG Management Suite see TMS telnet 5 7 66 TLS 80 TMS 1 6 50 57 64 traversal call 87 unregistered endpoint 15 upgrade 50 52 URI dialing 9 10 hyperpage28 28 30 33 35 58 59 61 h323cs 15 29 h323ls 29 xCommand AllowListAdd 69 AllowListDelete 69 Boot 69 CallTransfer 37 69 CheckBandwidth 69 CredentialAdd 70 CredentialDelete 70 DefaultLinksAdd 70 DefaultValuesSet 70 DenyListAdd 70 DenyListDelete 71 Dial
31. 61 TANDBERG Gatekeeper User Manual 14 2 7 LDAP Parameters under the LDAP node control the Gatekeeper s communication with an LDAP server xconfiguration LDAP Encryption lt Off TLS gt Sets the encryption mode to be used on the connection to the LDAP server The default is Off xconfiguration LDAP Password lt password gt Sets the password to be used when binding to the LDAP server xconfiguration LDAP Server Address lt IPAddr gt Sets the IP address of the LDAP server to be used when making LDAP queries xconfiguration LDAP Server Port lt 1 65534 gt Sets the IP port of the LDAP server to be used when making LDAP queries xconfiguration LDAP UserDN lt userdn gt Sets the user distinguished name to be used when binding to the LDAP server 14 2 8 Links xconfiguration Links Link 1 100 Name lt linkname gt Specifies the name of a link in the list of links xconfiguration Links Link 1 100 Node1 Name lt nodename gt 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 lt nodename gt 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 lt pipename gt First pipe associated with a link xconfiguration Links Link 1 100 Pipe2 Name lt pipename gt Second pipe associated with a link 14 2 9 Log xConfiguration Log Level lt 1 3
32. ANDBERG Gatekeeper User Manual 14 2 4 Gatekeeper Commands under the Gatekeeper node control aspects of the systems operation relating to its operation as an H 323 gatekeeper xconfiguration Gatekeeper Alternates Monitor lt On Off gt Controls whether or not alternate gatekeepers are periodically interrogated to ensure that they are still functioning Non functional alternates will not receive Location Requests in order to prevent delays during call setup xconfiguration Gatekeeper Alternates Alternate 1 5 Address lt IPAddr gt Set the IP address of an alternate Gatekeeper Up to 5 alternates may be configured When the Gatekeeper receives a Location Request all alternates will also be queried xconfiguration Gatekeeper Alternates Alternate 1 5 Port lt IPAddr gt Set the IP port of an alternate Gatekeeper The default is 1719 xconfiguration Gatekeeper AutoDiscovery lt On Off gt xconfiguration Gatekeeper CallRouted lt Qn Off gt Specifies whether the Gatekeeper should operate in call routed mode Defaults to off Specifies whether or not the Gatekeeper responds to gatekeeper discovery requests from endpoints The default is On xconfiguration Gatekeeper CallsToUnknownIPAddresses lt Off Direct Indirect gt Specifies whether or not the Gatekeeper will attempt to call systems which are not registered with it or one of its neighbor gatekeepers It has three settings Direct this setting will allow the endpoint to make
33. Bandwidth ResourceUsage gt 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 ResourceUsage fields consist of e Registrations e MaxRegistrations e TraversalCalls e MaxTraversalCalls e TotalTraversalCalls e NontTraversalCalls e MaxNontTraversalCalls e TotalNonTraversalCalls 14 6 Other commands 14 6 1 About about About provides information about the software version installed on the system 14 6 2 Clear clear eventlog history Clears the event log or history of all calls and registrations 75 TANDBERG Gatekeeper User Manual 14 6 3 Eventlog eventlog eventlog n all Displays the eventlog containing information about past events which may be useful for diagnostic purposes n The number of lines from end of event log to dump all Dumps the whole event log 14 6 4 License license Provides access to the license terms of third party software incorporated in the product 14 6 5 Relkey relkey Displays the release key that this software has been installed with 14 6 6 Syslog syslog lt level gt ipaddr ipaddr Enables tracing to the console level Specifies the detail at which to trace 0 3 3 gives most logging ipaddr Specif
34. LDAP servers see Appendix B To configure the Gatekeeper to use the LDAP server directory during authentication issue the following commands xConfiguration Authentication Mode On xConfiguration Authentication Database LDAPDatabase The Gatekeeper 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 350 objects reside xConfiguration Authentication LDAP BaseDN Your base DN The Gatekeeper must also be configured with the location of the LDAP server and the security credentials required to gain access to the LDAP server The following commands are used to configure the LDAP server details xConfiguration LDAP Server Address ldap server address xConfiguration LDAP Server Port 389 xConfiguration LDAP UserDN Your user DN xConfiguration LDAP Password password The status of the connection between the Gatekeeper and the LDAP server can be verified using the command xstatus LDAP The details of the LDAP server can also be configured via the web interface on the Gatekeeper Configuration Gatekeeper page 6 2 3 Enforced dial plans lf LDAP authentication is in use you may control what aliases an endpoint is allowed to register with This allows you centralised control of your dial plan When an endpoint registers it presents a list of aliases it wishes to use Thes
35. NDBERG Gatekeeper User Manual Contents 1 Introduction 1 1 1 TANDBERG Gatekeeper Overview 0 0000 eee eee 2 2 Installation 3 2 1 POCAS e amp 2 2 2 4 Beg dbo ete ae ee a Pe Be ee es oa ee 3 2 2 Unpacking e 2 wc ee feo A ee bee Be Ga a 3 2 3 Mounting e iE a a aaa a aaae ee 4 2 4 Connecting Cables o aoaaa a a 4 2 5 Switching on the System aoa aaa a 4 2 6 Gatekeeper Initial Configuration ooa a e a 5 3 Getting started 7 3 1 System Administration 00 00000 cee ee 7 3 2 BACKUPS s e a de ear RRR ERG ee Bee ee eta tad a eee eS 8 3 3 IP Configuration 3 466442 4408448 bee te ee ee edd ba dewey x 8 3 4 Registration 2 2 0 0 ee 8 3 5 Neighbor Gatekeepers 00 0 ee 9 3 6 Alternate Gatekeepers naoa oa a a 11 3 7 Call signaliNg 22266466465 4454 aaa a a bee be ewe ee eee de A 12 4 Unregistered Endpoints 15 4 1 Calling from an unregistered endpoint 2 0000000 15 4 2 Calling to an unregistered endpoint 2 00 00000 ee 15 5 Bandwidth Control 17 5 1 Bandwidth Control and Firewall Traversal 000 a 21 5 2 Bandwidth Control Examples 00000 e eee eee 21 6 Registration Control 24 6 1 Registration Restriction Policy 00 0000 eee eee 24 6 2 Authentication ss 2 2 0 0 ee 25 7 URI Dialing 28 7 1 Making a call using URI dialing 2 2 00000000 28 7 2 Receiving a call using URI dialing 20
36. Pattern 5 Configuration Pattern Save Cancel v D A D io O D m Figure 16 Configuring registration restrictions Matching uses a simple form of wild card expansion 12345678 Exact match only 1234567 First 7 characters are an exact match last may be anything 123 123 followed by anything example com Any string ending with example com To set entries in the Allow and Deny lists use the following commands AllowListAdd AllowListDelete DenyListAdd DenyListDelete To view the entries in the allow and deny lists use the following commands 24 TANDBERG Gatekeeper User Manual xConfiguration Gatekeeper Registration AllowList xConfiguration Gatekeeper Registration DenyList 6 2 Authentication The TANDBERG Gatekeeper 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 Gatekeeper supports the ITU H 235 1 specification for authenticating the identity of network devices with which theGatekeeper communicates In order to verify the identity of a device the Gatekeeper needs access to the password infor mation This credential information may be stored in a local database on the Gatekeeper or obtained from an LDAP Directory Server 6 2 1 Authentication using a local database To configure the Gatekeeper to use the local database of credentials during auth
37. TANDBERG Gatekeeper User Manual Software version N5 0 D13381 05 This document is not to be reproduced in whole or in part without permission in writing from TANDBERG TANDBERG Gatekeeper 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 Nationally and internationally recognized trademarks and tradenames are the property of their respective holders and are hereby acknowledged Portions of this software are licensed under 3rd party licenses See the CD accompanying this product for details 3rd party license information may also be obtained from the Gatekeeper itself see the license command in section 14 6 for details Disclaimer The information in this document is furnished for informational purposes only is subject to change without prior notice and should not be construed as a commitment by TANDBERG ASA The information in this document is believed to be accurate and reliable however TANDBERG ASA assumes no responsibility or liability for any errors or inaccuracies that may appear in this document nor for any infringements of patents or other rights of third parties r
38. adable Examples e call attempt connected disconnected e registration attempt accepted rejected Logs of protocol messages sent and received Protocol keepalives are suppressed at Level 2 At logging level 3 keepalives are also logged Events logged at level 1 Event Description Eventlog Cleared Admin Session Start Admin Session Finish System Configuration Changed Policy Change Registration Requested Registration Accepted Registration Rejected An operator cleared the event log An administrator has logged onto the system An administrator has logged off the system An item of configuration on the system has changed The detail event parameter contains the name of the changed configuration item and its new value A policy file has been updated A registration has been requested A registration request has been accepted A registration request has been rejected The Reason event parameter contains the H225 cause code Optionally the Detail event pa rameter may contain a textual representation of the H 225 additional cause code 45 TANDBERG Gatekeeper User Manual Table 2 Level 1 Events continued Event Description 46 Registration Removed Call Answer Attempted Call Attempted Call Connected Call Disconnected Call Rejected Call Bandwidth Changed External Server Communication Failure System Start System Shutdown Application Start Application Failed License Limit Reached A r
39. ains a list of addresses H 323 IDs URLs and E 164 numbers which will be used as the destination of the call if a proxy node is executed The location node allows the location set to be modified so that calls can be redirected to different destinations At the start of script execution the location set is initialized to empty for incoming calls and to the original destination for outgoing calls The following attributes are supported on location nodes Clear yes no Specifies whether to clear the current location set before adding the new location The default is to append this location to the end of the set url string The new location to be added to the location set The given string can specify a URL user domain com H 323 ID or an E 164 number 11 2 2 proxy On executing a proxy node the Gatekeeper will attempt to forward the call to the locations specified in the current location set If multiple entries are in the location set then they are treated as different aliases for the same destination and are all placed in the destination alias field If the current location set is empty the call will be forwarded to its original destination It is important to note that when a proxy node is executed script execution stops immediately i e there is currently no support for the proxy outputs busy noanswer etc 11 2 3 reject If a reject node is executed the Gatekeeper stops any further script processing and rejects the current ca
40. al port To set an empty password type xconfiguration SystemUnit Password 14 2 19 Telnet xconfiguration Telnet Mode lt On Off gt Enables disables Telnet support For secure operation you should use ssh in preference to telnet You must restart the system for changes to take effect 14 2 20 TimeZone xconfiguration TimeZone Name lt timezone name gt Sets the local timezone Timezone names follow the POSIX naming convention e g Eu rope London or America New_yYork 14 2 21 Traversal xconfiguration Traversal Registration RetryInterval lt 1 65534 gt Sets the interval in seconds at which the gatekeeper will attempt to register with the Border Controller if its initial registration fails for some reason The default is 120 seconds xconfiguration Traversal AllowMediaDirect lt Qn Off gt Determines whether endpoints must route their media through the Gatekeeper or may if capable send media directly to the Border Controller 14 2 22 Zones Traversal zones control how the Gatekeeper communicates with a Border Controller which it is cooperating with to provide firewall traversal xconfiguration Zones TraversalZone Name lt name gt Sets the name of the traversal zone xconfiguration Zones TraversalZone Gatekeeper Address lt address gt Sets the IP address of the Border Controller that this system will register with 66 TANDBERG Gatekeeper User Manual xconfiguration Zones TraversalZone Gatekeeper HopCoun
41. an electrician Never install cables or any peripherals without first unplugging the device from it s power source Servicing vi Do not attempt to service the apparatus yourself as opening or removing covers may expose you to dangerous voltages or other hazards and will void the warranty Refer all servicing to qualified service personnel Unplug the apparatus from it s power source and refer servicing to qualified personnel under the following conditions If the power cord or plug is damaged or frayed If liquid has been spilled into the apparatus If objects have fallen into the apparatus If the apparatus has been exposed to rain or moisture If the apparatus has been subjected to excessive shock by being dropped If the cabinet has been damaged TANDBERG Gatekeeper User Manual If the apparatus seems to be overheated Ifthe apparatus emits smoke or abnormal odor lf the apparatus fails to operate in accordance with the operating instructions Accessories e Use only accessories specified by the manufacturer or sold with the apparatus Communication lines e Never touch uninstalled communication wires or terminals unless the telephone line has been disconnected at the network interface e Do not use communication equipment to report a gas leak in the vicinity of the leak e To reduce the risk of fire use only No 26 AWG or larger telecommunication line cord ISDN cables vii TA
42. another endpoint it presents the address it wants to call to the Gatekeeper using a protocol knows as RAS The Gatekeeper 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 164 alias is used the Gatekeeper looks for a match between the dialed address and the aliases registered by its endpoints If no match is found it may query other Gatekeepers and Border Controllers When dialing by H 323 URI the destination address resembles an email address The Gate keeper first follows the procedure for matching H 323 IDs If that fails it looks for a Gatekeeper or Border Controller responsible for the domain the part of the URI following the symbol and queries that device Dialing by IP address is necessary when the destination endpoint is not registered with a Gatekeeper or Border Controller If it is registered then one of the other addressing schemes should be used instead as they are more flexible From your registered endpoint dial the IP address of the endpoint you wish to call This requires that the Gatekeeper has xConfiguration Gatekeeper CallToUnknownIPAddresses correctly configured See section 4 2 12 TANDBERG Gatekeeper User Manual Figure 6 illustrates the process the Gatekeeper performs when receiving call requests When one endpoint calls another th
43. atekeeper read access to the BaseDN and therefore limit access to other sections of the directory Add the H 350 objects Create an Idif file with the following contents MeetingRoom1 endpoint dn commUniqueId commi ou h350 dc my domain dc com objectClass comm0bject 79 TANDBERG Gatekeeper User Manual objectClass h323Identity objectClass h235Identity commUniquelId comm1 h323Identityh323 ID MeetingRoom1i h323IdentitydialedDigits 626262 h235IdentityEndpointID meetingrooml h235IdentityPassword mypassword Add the ldif file to the server using the command ldifde i c DC X lt ldap_base gt f filename ldf This will add a single H 323 endpoint with an H 323 Id alias of MeetingRoom and an E 164 alias of 626262 The entry also has H 235 credentials of id meetingroom and password mypassword which are used during authentication B 1 3 Securing with TLS To enable Active Directory to use TLS you must request and install a certificate on the Active Directory server The certificate must meet the following requirements Be located in the Local Computer s Personal certificate store This can be seen using the Certificates MMC snap in Have the private details on how to obtain a key associated for use with it stored locally When viewing the certificate you should see a message saying You have a private key that corresponds to this certificate Have a private key that does not have strong private key protection enabled
44. ays or disabled 3 5 1 Search Order If a called alias matches a prefix or suffix zone a strong match is achieved A weak match is achieved if a zone is to be queried only because it has no pattern matching configured When an incoming call request is received a Gatekeeper will first search all of its registered endpoints If no match is found all strongly matching neighbor and traversal zones will be queried concurrently If the target is not found in any of the strongly matching zones all weakly matching neighbor zones will be queried then all weakly matching traversal zones Finally if a match has still not been found a DNS query may be attempted as described in section 7 TANDBERG Gatekeeper User Manual E Overview system Status s System Configuration Gatekeeper Configuration Gatekeeper Authentication Services Zones TraversalZones SubZones Links Pipes Restrictions Credentials Add New Zone Configuration Name Eam pe Gatekeeper 1 Address jok example com cet fi719 Gatekeeper 2 Address ort fi7is Gatekeeper 3 Address ort fi7is Gatekeeper 4 Address ort fi719 Gatekeeper 5 Address ort i719 s Ma Ws E Bi e Gatekeeper 6 Address ort i719 Hop Count fs Monitor On y Match 1 Mode Aways Maxi B S Match 2 2 Mode Disabled xj i Match 3 Mode Disabled v Match 4 Mode Disabled xj Q rae s Disabled z D oD Save Cancel Q Figure 4 Adding a new zone 3 6 Alternate Gatekee
45. cation through a firewall All signaling and media is routed through the Border Controller Zone See DNS Zone and Gatekeeper Zone 87 Index about 75 account administrator 7 root 8 ActiveDirectory see LDAP servers Admission Request 87 alias 8 9 24 87 AllowList 24 59 AllowListAdd 69 AllowListDelete 69 alternate gatekeeper 10 11 58 67 authentication 25 27 42 57 63 and CPL 39 credential 57 mode 57 backup 8 bandwidth control 17 23 Call Detail Record 13 call policy 39 43 59 Call Processing Language see CPL call routed 13 37 58 CDR see Call Detail Record 13 certificate 27 clear 75 CPL 39 examples 42 43 default enum zone 31 IP address 5 70 password 5 DefaultLinksAdd 23 DenyList 24 59 dial plan enforced 26 57 flat 10 hierarchical 10 structured 10 directory gatekeeper 10 DNS 6 10 28 31 36 58 59 SRV record 29 77 zone 87 domain local 9 down speed 19 58 59 E 164 10 12 31 87 ENUM 31 32 ethernet 57 event log 44 49 remote 49 verbosity 44 eventlog 76 external manager 54 57 feedback 54 74 75 firewall 21 87 gatekeeper discovery 6 8 58 zone 87 H 235 see also authentication 26 57 H 323 Annex O 30 ID 12 URI 12 H 350 26 see also LDAP H 460 18 19 44 hop count 67 68 http s 6 60 upgrade using 50 51 IP address 5 67 dialing 12 19 34 58 initial configuration 5 port 67 v4 8 60 v
46. der Controller this Gatekeeper is paired with This zone is automatically added for you The traversal subzone represents the Gatekeeper itself The traversal subzone allows you to control total and per call bandwidths passing through the Border Controller Unlike other subzones no endpoints will ever be registered in this subzone 5 2 Bandwidth Control Examples One possible configuration for the deployment in Figure 8 is shown in Figure 12 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 Enterprise Home Pipe Pipe Default Home sub zone sub zone Branch Pipe Branch sub zone Figure 12 Bandwidth control example There are no firewalls involved in the scenario shown in figure 8 so we can configure links between each of the offices Each link is then assigned two pipes representing the Internet connections of the offices at each end of the link A call placed between the Home Office and Branch Office will consume bandwidth in the home and branch subzones and on the home and branch pipe The enterprise s bandwidth budget will be unaffected by the call 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
47. dices for calls currently active on this link Bandwidth Total and per call bandwidth limits on this link together with bandwidth currently in use 54 TANDBERG Gatekeeper User Manual 14 1 8 NTP xstatus NTP Reports the status of any connection to an NTP server 14 1 9 Pipes xstatus Pipes xstatus Pipes Pipe n Reports call and bandwidth information for all pipes on the system 14 1 10 Registrations xstatus Registrations xstatus Registrations Registration n Returns a list of registered endpoints on the system or information about a specific registration 14 1 11 ResourceUsage xstatus ResourceUsage Reports information about the usage of system resources Registrations Number of currently active registrations MaxRegistrations Maximum number of concurrent registrations since system TraversalCalls Number of currently active traversal calls MaxTraversalCalls Maximum number of traversal calls since sys tem start TotalTraversalCalls Total number of traversal calls since system start NontraversalCalls Number of currently active non traversal calls MaxNontTraversalCalls Maximum number of non traversal calls since system start TotalNonTraversalCalls Total number of non traversal calls since sys tem start 14 1 12 SubZones xstatus SubZones Reports call and bandwidth information for all subzones on the system 55 TANDBERG Gatekeeper User Manual 14 1 13 SystemUnit xstatus SystemUnit Reports in
48. e Gatekeeper is involved in locating the called endpoint By default once the endpoint is located the Gatekeeper takes no further part in the call signaling By enabling call routed mode all call signaling will be routed through the Gatekeeper This is useful if you need accurate information about call start and stop times Call Detail Records CDRs may be extracted from the Gatekeeper event log NOTE Traversal calls are always call routed regardless of the setting of Call Routed Mode 13 TANDBERG Gatekeeper User Manual Receive Request from Endpoint One TANDBERG gatekeeper LRQ Search Algorithm z a Caio Success return LCF or ACF Go registered endpoint lt Failure return LRJ or ARJ Locally lt registered service lt V Found _ address es k P address gt literal Attempt to locate Call Signaling port using DNS A AAAA On local network _ Received k LCF Call signaling port located Indirect Feed URIs back in i Xx by Cee LRQ foreign priority order to a jatekeeper Location Search Alternates DNS SRV j i algorithm Yas onfigured _ ry A No o N 4 LRQ all Alternates is Ery ies es Empty candidale with hopcount 1 Q Siena set of URIs No Attempt to locate Perform E 164 URI foreign gatekeeper resolu
49. e may be used replaced by those in the H 350 directory or combined with those in the directory This behaviour is controlled by the command xConfiguration Authentication LDAP AliasOrigin lt LDAP Endpoint Combined gt By default the LDAP aliases will be used and those presented by the endpoint ignored If the AliasOrigin is set to LDAP but no aliases are present in the LDAP database for the endpoint which is registering then the endpoint s aliases will be used If AliasOrigin is set to Combined the endpoint will be registered with both the aliases which it has presented and those configured in the LDAP database 26 TANDBERG Gatekeeper User Manual 6 2 4 Securing the LDAP connection with TLS The traffic between the Gatekeeper and the LDAP server can be encrypted using Transport Layer Security TLS To use TLS the LDAP server must have a valid certificate installed so that the Gatekeeper can verify the server s identity For more information on setting up certificates using common LDAP servers see Appendix B LDAPS uses port 636 as its default communications port Using the terminal interface TLS can be enabled with the following command xConfiguration LDAP Encryption TLS TLS can also be enabled via the web interface using the Gatekeeper Configuration Gatekeeper page The Gatekeeper will now only communicate with the LDAP server using TLS To verify the identity of the LDAP server the certificate of the Certificate Authori
50. eeper shown in figure 7 There are three possible settings 15 TANDBERG Gatekeeper User Manual Direct this setting will allow the endpoint to make the call to the unknown IP address without querying any neighbors The call setup would occur just as it would if the far end were registered directly to the local system Indirect upon receiving the call the Gatekeeper will query its neighbors for the remote address relying on the response from the neighbor to allow the ability for the call to be completed connecting through the routing rules as it would through the neighbor relationship Off this will not allow any endpoint registered directly to the Gatekeeper to call an IP address of any system not also registered directly to that Gatekeeper See section 4 for further detail The default is Indirect When the Gatekeeper is used with a Border Controller for firewall traversal you will typically set CallsToUnknownIPAddresses to Indirect on the Gatekeeper and Direct on the Border Controller This will allow calls originating inside the firewall to use the Gatekeeper and Border Controller to successfully traverse the firewall This is described in more detail in section 9 3 TANDBERG Gatekeeper User Manual 5 Bandwidth Control The TANDBERG Gatekeeper allows you to control endpoints use of bandwidth on your network Figure 8 shows a typical deployment a broadband LAN where high bandwidth calls are acceptable a pipe to the inter
51. egistration 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 e Conflicting zones e Operator forced removal e Operator forced removal all registra tions removed An attempt to answer a call has been made A call has been attempted A call has been connected A call has been disconnected A call has been rejected The Reason event parameter contains a textual representation of the H 225 additional cause code The bandwidth of a call has changed Communication with an external server failed unexpectedly The event detail data should differentiate between no response and re quest rejected i e NACK rather than silence Servers concerned are e DNS LDAP servers Neighbor Gatekeeper NTP servers The operating system has started The operating system was shutdown The Gatekeeper has started Further detail may be provided in the event data detail field The Gatekeeper application is out of service due to an unexpected failure Licensing limits for a given feature have been reached The event detail field specifies the facility limits concerned Possible values for the detail field are e Non Traversal Call Limit Reached e Traversal Call Limit Reached Table 3 Events logged at level 2 Event Description Incoming Message An incoming message has been received TANDBERG Gatekeep
52. enldap slapd conf and add the following three lines TLSCACertificateFile lt path to CA certificate gt TLSCertificateFile lt path to LDAP server certificate gt TLSCertificateKeyFile lt path to LDAP private key gt The OpenLDAP daemon slapd must be restarted for the TLS settings to take effect For more details on configuring OpenLDAP to use TLS consult the OpenLDAP Administrator s Guide To configure the Gatekeeper to use TLS on the connection to the LDAP server you must upload the CA s certificate as a trusted CA certificate To do this navigate to the Gatekeeper Configuration Files page and upload the certificate 82 TANDBERG Gatekeeper User Manual C Approvals The product has been approved by various international approval agencies among others CSA 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 Gatekeeper Type number TTC2 02 complies with the following standards EMC Emission Radiated Electromagnetic Interference e EN55022 1994 A1 1995 A2 1997 Class A e FCC Rules and Regulations 47CFR Part 2 Part 15 e CISPR PUB 22 Class A EMC Immunity e EN 55024 1998 A1 2001 e EN 61000 3 2 2000 e EN 61000 3 3 1995 A1 2001 Electrical Safety e IEC 60950 1 edition 2001 e EN 60950 1 edition 2001
53. entication issue the following commands xConfiguration Authentication Mode On xConfiguration Authentication Database LocalDatabase Each credential in the local database has a username and a password To manage the credentials in the local database use the following commands xcommand CredentialAdd lt user name gt lt password gt xcommand CredentialDelete lt credential index gt To show the credentials in the local database use the command xConfiguration Authentication Credential The credential database can also be configured via the web interface on the Gatekeeper Configuration Credentials page Figure 17 Hioverview System Status System Configuration a Gatekeeper Configuration Gatekeeper Authentication erv s Zones TraversalZones SubZones Links Pipes Restrictions Credentials Files Add New Authentication Credential Configuration Name Password Save Cancel 1909949129 9YJ4ANVL Figure 17 Adding Authentication credentials 25 TANDBERG Gatekeeper User Manual 6 2 2 Authentication using an LDAP server The authentication information can be obtained from an LDAP server The directory on the LDAP server should be configured to implement the ITU H 350 specification to store H 235 credentials for devices that the Gatekeeper communicates with The directory should also be configured with the H 323 aliases of endpoints that will register with the Gatekeeper For instructions on how to configure common third party
54. er User Manual Event Description Outgoing Message 12 4 1 Event data An outgoing message has been sent 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 Description Applicable events Protocol Reason Service Message Type Specifies which protocol was used for the communication Valid values are TCP or UDP Textual string containing any rea son information associated with an event Specifies which protocol was used for the communication A service entry is one of H 225 H 245 NTPDNS LDAP Neighbor Gatekeeper Specifies the type of the mes sage Call Attempted Call Bandwidth Changed Call Connected Call Disconnected Call Rejected External Server Communi cation Failure Incoming Message Outgoing Message Policy Change Registration Accepted Registration Rejected Registration Removed Registration Requested e Call Rejected e External Server Communi cation Failure Registration Rejected e Registration Removed External Server Communi cation Failure e Incoming Message e Outgoing Message e Incoming Message e Outgoing Message 47 TANDBERG Gatekeeper User Manual Table 4 Event data continued Field Description Applicable events Src ip Specifies the source IP ad dress the IP address of the e Call Attempted device attempting to estab e Call Bandwidth C
55. er to e Proxy the call to its original destination e Redirect the call to a different destination e Reject the call The Gatekeeper will only execute scripts for source or destinations which are registered directly with the system The CPL script is uploaded via the Web interface under the Gatekeeper Configuration Files web page The execution of the CPL script is controlled by the setting xConfiguration Gatekeeper Policy Mode lt 0n 0ff gt Policy interacts with authentication section 6 2 If authentication is enabled on the local Gatekeeper and a call is received from a remote unauthenticated Gatekeeper the call s source aliases will be removed from the call request before it is passed to the policy engine This is because the unauthenticated source aliases could be forged and so should not be used for policy decisions in a secure environment The following sections give details of the Gatekeeper s implementation of the CPL language and should be read on conjunction with the CPL standard RFC 3880 5 11 1 Making Decisions Based on Addresses 11 1 1 address switch The address switch node allows the script to run different actions based on the source or destination aliases of the call The address switch specifies which fields to match and then a list of address nodes contains the possible matches and their associated actions The supported attributes on an address switch and their interpretation are as follows field
56. er with the address of a public DNS server 35 TANDBERG Gatekeeper User Manual e 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 That system is registered in DNS and is set up with all the other Border Controllers and Gatekeepers as neighbors When the master receives a URI dialing request for an endpoint it does not know about it will query its neighbors 36 TANDBERG Gatekeeper User Manual 10 Third Party Call Control The Gatekeeper provides a third party call control API which enables you to place calls or initiate a blind transfer of an existing call The API is provided through the command line interface 10 1 Placing a call xCommand Dial may be used to place a call between two endpoints A and B To initiate the call xCommand Dial A B This will return immediately and the Gatekeeper will attempt to place the call Like other asynchronous Gatekeeper commands progress information may be obtained by registering for feedback xFeedback Register status call 10 2 Transferring a call A call may be transferred with the command xCommand CallTransfer Call call_inde
57. ered to the TANDBERG Border Controller thereby allowing the Border Controller itself to relay the call to the endpoint on the public IP address e On the Border Controller configure Calls to unknown IP addresses to Direct This setting will allow the Border Controller to connect any call that it receives from the internal Gatekeeper out to systems on the public Internet e From Endpoint 1001 dial 213 228 193 162 9 4 Neighbored enterprises If two sites have deployed Border Controllers for firewall traversal the two Border Controllers may be neighbored to allow calls to be placed from one enterprise to another Neighboring will reduce call setup time compared to URI dialing described in section 7 The disadvantage of neighboring is that the Border Controllers have to be configured with each others addresses before the call can be made Gatekeeper and matching Border Controller are neighbored as described in section 9 1 Border Controller A and B are neighbored together either with or without prefixes 9 5 URI dialing from within the enterprise e Turn URI dialing OFF on the TANDBERG Gatekeeper You want to use the Border Controller to resolve any H 323 URI received e Ensure that DNS Resolution Mode is turned on at the TANDBERG Border Controller You want to use the Border Controller to resolve any H 323 URI received e Configure the local domain name on both the Gatekeeper and the Border Controller e Configure the Border Controll
58. erial interface once it has restarted e Login with the user name pwrec No password is required e You will be prompted for a new password The pwrec account is only active for one minute following a restart Beyond that time you will have to restart the system again to change the password Because access to the serial port allows the password to be reset it is recommended that you install the Gatekeeper in a physically secure environment TANDBERG Gatekeeper User Manual 3 1 2 Root Account The Gatekeeper 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 Backups You are recommended to maintain a backup of your Gatekeeper configuration Using the command line interface log on to the Gatekeeper as admin and type xConfiguration Save the resulting output to a file using cut and paste or some other means provided by your terminal emulator Pasting this information back in to the command line shell will restore your configuration 3 3 IP Configuration The Gatekeeper may be configured to use IPv4 IPv6 or both protocols If using both protocols the Gatekeeper will act as a gateway if necessary allowing calls to be made between an IPv4 only endpoint and an IPv6 only endpoint This behavior will use a traversal license for each call gatewayed between IPv4
59. ers stoves or other apparatus including amplifiers that produce heat e Do not place the product in direct sunlight or close to a surface directly heated by the sun Lightning e Never use this apparatus or connect disconnect communication cables or power cables during lightning storms TANDBERG Gatekeeper User Manual Dust Do not operate the apparatus in areas with high concentration of dust Vibration Do not operate the apparatus in areas with vibration or place it on an unstable surface Power connection and Hazardous voltage The product may have hazardous voltage inside Never attempt to open this product or any peripherals connected to the product where this action requires a tool This product should always be powered from an earthed power outlet Never connect attached power supply cord to other products In case any parts of the product has visual damage never attempt to connect mains power or any other power source before consulting service personnel The plug connecting the power cord to the product power supply serves as the main disconnect device for this equipment The power cord must always be easily accessible Route the power cord so as to avoid it being walked on or pinched by items placed upon or against it Pay particular attention to the plugs receptacles and the point where the cord exits from the apparatus Do not tug the power cord If the provided plug does not fit into your outlet consult
60. esulting from its use No license is granted under any patents or patent rights of TANDBERG ASA COPYRIGHT 2006 TANDBERG ASA TANDBERG Gatekeeper 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 s Environmental Policy Environmental stewardship is important to TANDBERG s culture As a global company with strong corporate values TANDBERG is committed to being an environmental leader and embracing technologies that help companies individuals and communities creatively address environmental challenges TANDBERG s environmental objectives are to Develop products that reduce energy consumption CO emissions and traffic congestion Provide products and services that improve quality of life for our customers Produce products that can be recycled or disposed of safely at the end of product life Comply with all relevant environmental legislation European Environmental Directives As a manufacturer of electrical and electronic equipment TANDBERG is responsible for compli ance with the requirements in the European Directives 2002 96 EC WEEE and 2002 95 EC ROHS The primary aim of the WEEE Directive and R
61. et in Europe after August 13th 2005 Please contact TANDBERG at recycling tandberg net and provide the following details for the product for which you would like to receive recycling information Model number of TANDBERG product Your company s name Contact name Address Telephone number E mail address Digital User Guides TANDBERG is pleased to announce that we have replaced the printed versions of our User Guides with a digital CD version Instead of a range of different user manuals there is now one CD which can be used with all TANDBERG products in a variety of languages The environmental benefits of this are significant The CDs are recyclable and the savings on paper are huge A simple web based search feature helps you directly access the information you need In addition the TANDBERG video systems now have an intuitive on screen help function which provides a range of useful features and tips The contents of the CD can still be printed locally whenever needed TANDBERG Gatekeeper 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 s Environmental Policy e TANDBERG s Research and Development i
62. fication 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 86 TANDBERG Gatekeeper User Manual E Glossary Alias The name an endpoint registers with the Gatekeeper Other endpoints can then use this name to call it ARQ Admission Request An endpoint RAS request to make or answer a call DNS Zone A subdivision of the DNS namespace example com is a DNS zone E 164 An ITU standard for structured telephone numbers Each telephone number consists of a country code area code and subscriber number For example TANDBERG s European Headquarters phone number is 47 67 125125 corresponding to a country code of 47 for Norway area code of 67 for Lysaker and finally 125125 to determine which phone line in Lysaker Gatekeeper Zone A collection of all the endpoints gateways and MCU s managed by a single gatekeeper LRQ Location Request A RAS query between Gatekeepers or Border Controllers to determine the location of an endpoint RAS Registration Admission and Status Protocol Protocol used between endpoints and Gatekeeper 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 communi
63. formation about the system as follows Product name Uptime SystemTime TimeZone LocalTime Software version Software name Software Build Release date Number of calls supported Number of registered endpoints and services supported Hardware serial number Hardware version 14 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 14 2 Configuration The configuration root command xconfiguration is used to set configuration settings To list all xconfiguration commands type xconfiguration To list all configuration data type xconfiguration To show a specific configuration value type xconfiguration name To show usage information for a specific configuration value type xconfiguration name To set a configuration element type xconfiguration name paraml valuel param2 value2 NOTE Remember to use the colon after naming the parameters 56 TANDBERG Gatekeeper User Manual 14 2 1 Authentication Configuration parameters relating to how an endpoint authenticates itself with the Gatekeeper xconfiguration Authentication Credential 1 1000 Name lt username gt Specifies the username of a credential in the local authentication database xconfiguration Authentication Credential 1 1000 Password lt password gt Specifies the password of a credential in the local authentica
64. g SCP do the following e Make sure the system is turned on and available on IP e 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 e Enter password when prompted e Copy the software image using SCP The target name must be tmp tandberg image tar gz e g 51 TANDBERG Gatekeeper User Manual scp s42000n40 tar gz root 10 47 8 247 tmp tandberg image tar gz e Enter password when prompted e Wait until the software has installed completely This should not take more than two minutes e Reboot the system After about four minutes the system will be ready to use 52 TANDBERG Gatekeeper User Manual 14 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 14 1 Status The status root command xstatus returns status information from the Gatekeeper To list all status information type xstatus Status is reported hierarchically beneath the status root It is possible to reduce the amount of information returned by xstatus by specifying a more detailed status command To list all xstatus commands available at the root level type xstatus 14 1 1 calls xstatus Calls xstatus Calls Call n Returns a list of active calls on the system or information about a specific call 14 1 2 ethernet xstatus Ethernet xstatus Ethernet MacAddress
65. h Please note that all address comparisons ignore upper lower case differences so lt address is Fred gt will match fred freD etc is string Selected field and subfield exactly match the given string contains string Selected field and subfield contain the given string Note The CPL standard only allows for this matching on the display subfield however the Gatekeeper allows it on any type of field subdomain of string If the selected field is numeric e g the tel sub field then this matches as a prefix so lt address subdomain of 555 gt matches 5556734 etc If the field is not numeric then normal do main name matching is applied so lt address subdomain of company com gt matches nodeA company com etc otherwise 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 40 TANDBERG Gatekeeper 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 Gatekeeper 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 11 4 11 2 CPL Script Actions 11 2 1 location As the CPL script runs it maint
66. h available xconfiguration SubZones SubZone 1 100 Bandwidth PerCall Limit lt 1 100000000 gt Per call bandwidth available on the indexed subzone xconfiguration SubZones SubZone 1 100 Bandwidth PerCall Mode lt None Limited Unlimited gt Whether or not the indexed subzone is enforcing per call bandwidth restrictions None corre sponds to no bandwidth available xconfiguration SubZones SubZone 1 100 Bandwidth Total Limit lt 1 100000000 gt Total bandwidth available on the indexed subzone xconfiguration SubZones SubZone 1 100 Bandwidth Total Mode lt None Limited Unlimited gt Whether or not the indexed subzone is enforcing total bandwidth restrictions None corresponds to no bandwidth available xconfiguration SubZones SubZone 1 100 Name lt subzonename gt Name of the indexed subzone xconfiguration SubZones SubZone 1 100 Subnet IP Address lt IPAddr gt IP to match an endpoint which belongs in this subzone xconfiguration SubZones SubZone 1 100 Subnet IP PrefixLength lt IPAddr gt Number of bits which must match for an IP address to belong in this subzone 65 TANDBERG Gatekeeper User Manual 14 2 18 SystemUnit xconfiguration SystemUnit Name lt name gt The name of the unit Choose a name that uniquely identifies the system xconfiguration SystemUnit Password lt password gt Specify the password of the unit The password is used to login with Telnet HTTP S SSH SCP and on the seri
67. hanged lish communications The e Call Connected source IP is recorded in the e Call Disconnected dotted decimal format num e Call Rejected ber number number number e External Server Communi or the IPv6 colon separated cation Failure format e Incoming Message e Outgoing Message e Policy Change e Registration Accepted e Registration Rejected e Registration Removed e Registration Requested Dst ip Specifies the destination IP ad As Src ip dress the IP address of the des tination for a communication at tempt The destination IP is recorded in the same format as Src ip Dst port Specifies the destination port As Src ip the IP port of the destination for a communication attempt Src port Specifies the source port the IP_ As Src ip port of the device attempting to establish communications Src Alias e f present the first H 323 e Registration Requested Alias associated with the e Call Attempted originator of the message e Call Connected e If present the first E 164 e Call Disconnected Alias associated with the e Call Rejected originator of the message e Call Bandwidth Changed e Incoming Message e Outgoing Message Included if event parameter relevant or available for message concerned 48 Table 4 Event data continued TANDBERG Gatekeeper User Manual Field Description Applicable events Dst Alias e If present the first H 323 e Registration Accepted Alias associated with the e Registration Removed
68. hould be removed from the alias before an LRQ is sent to the indicated zone 68 TANDBERG Gatekeeper User Manual 14 3 Command The command root command xcommand is used to execute commands on the Gatekeeper To list all xcommands type xcommand To get usage information for a specific command type xcommand lt commandname gt 14 3 1 AllowListAdd xCommand AllowListAdd lt allowed_alias gt Adds an entry to the allow list used by the registration restriction policy 14 3 2 AllowListDelete xCommand AllowListDelete lt index gt Removes the pattern from the allow list at the specified index 14 3 3 Boot xCommand Boot Reboots the Gatekeeper This takes approximately 2 minutes to complete 14 3 4 CallTransfer xCommand CallTransfer Call lt call_index gt Leg lt 1 2 gt Alias lt alias gt Attempts to transfer the call half identified by the call index and leg to the given alias Call and leg indices may be conveniently identified using xstatus calls 14 3 5 CheckBandwidth xCommand CheckBandwidth lt node1 gt lt node2 gt lt bandwidth gt lt calltype gt Diagnostic function for verifying bandwidth control Node1 Node2 are the case sensitive names of the nodes bandwidth the required bandwidth and calltype one of Traversal or NonTraversal 69 TANDBERG Gatekeeper User Manual 14 3 6 CredentialAdd xCommand CredentialAdd lt username gt lt password gt Adds the given username and password to
69. ies are yet participating in ENUM so it may be useful to use an alternative DNS zone for ENUM This could either be within your corporate DNS zone or could use a public ENUM database such as http www e164 org The DNS zone used for ENUM contains NAPTR records as defined by RFC 2915 These provide the mapping between E 164 numbers and H 323 URIs The Gatekeeper may be configured with up to 5 DNS zones to search for a NAPTR record It will iterate through them in order stopping when the first record is found 8 1 Configuring ENUM ENUM support is disabled by default In order to enable ENUM support on your Gatekeeper enter the command xConfiguration Gatekeeper ENUM Mode On You are provided by default with the global ENUM DNS zone e164 arpa If you wish to change this or add other DNS zones enter the command xConfiguration Gatekeeper ENUM DNSSuffix 1 5 lt zone_name gt The ENUM mode and zone may also be set using the web page Gatekeeper Configuration gt Gatekeeper shown in figure 19 If you have a number of Gatekeepers and Border Controllers neighbored together it is recom mended that ENUM support is enabled on only one of them If ENUM is enabled on more than one system call set up could become unpredictable 8 2 Configuring DNS NAPTR Records ENUM relies on the presence of NAPTR records as defined by RFC 2915 This is used to obtain an H 323 URI from the E 164 number The record format that the Gatekeeper supports
70. ionally the call may be rejected if it cannot be placed at the requested bandwidth This option is controlled through the web interface of the Gatekeeper by navigating to Gatekeeper Configuration Gatekeeper Figure 11 or through the following command line instructions Overview SystemStatus System Configuration a Gatekeeper Configuration Gatekeeper Authentication Services Zones TraversalZones SubZones Links Pipes Restrictions Credentials Files Gatekeeper Configuration Configuration Local prefix ys Call routed Auto dscovery Calls to unknown IP addresses Indirect gt Allow calls from urregstered callers Fallback alias for unregistered caller destination Allow forwarding of location requests ra Allow DNS resolution gt Time to live seconds pl Call time to live seconds 120 CPL policy gt Downspeeding Allow downspeeding at total bandwidth limit gt Allow downspeeding at per call bandwidth limit gt Figure 11 Configuring down speeding options 19 TANDBERG Gatekeeper User Manual xConfiguration Gatekeeper Downspeed PerCall Mode lt On Off gt xConfiguration Gatekeeper Downspeed Total Mode lt Qn Off gt 20 TANDBERG Gatekeeper User Manual 5 1 Bandwidth Control and Firewall Traversal When a Border Controller and Gatekeeper are being used to traverse a firewall an additional zone and subzone come into use The traversal zone is used to represent the zone containing the Bor
71. kage TANDBERG Gatekeeper User Manual 1 1 TANDBERG Gatekeeper Overview On the front of the Gatekeeper 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 Figure 1 Front panel of Gatekeeper The back of the Gatekeeper has a power connector a power switch and a serial port Data 2 for connecting to a PC Figure 2 Rear panel of Gatekeeper TANDBERG Gatekeeper User Manual Installation 2 1 2 2 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 Avoid using communication equipment other than a cordless type during an electrical storm There may be a remote risk of electrical shock from lightning Do not use communication equipment to report a gas leak in the vicinity of the leak The socket outlet shall be installed near to the equipment and shall be easily accessible Never install cables
72. ks Pipes Restrictions Credentials Files mi Add New Pipe 5 Configuration g Name Internet Connection Total bandwidth mode limited f Total bandwidth kbps 5000 Q Per call bandwidth mode limited vf Per call bandwidth kbps 1920 D 8 Save Cancel U D Figure 10 Configuring a pipe 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 Calls between zones or subzones consume bandwidth from each zone and any pipes on the link between them When a Gatekeeper is neighbored with another Gatekeeper or a Border Controller the neighbor is placed in its own zone This allows you to control the bandwidth used by calls to and from endpoints controlled by the other Gatekeeper Sometimes you may place and receive calls to Gatekeepers you are not neighbored with See section 7 These Gatekeepers and any unregistered endpoints reached by dialing their IP address are placed in the Default Zone If bandwidth control is in use there are two possible behaviors when a call cannot be placed at the bandwidth requested By default the call will be connected at a reduced bandwidth down speeding assuming that there is some bandwidth still available Opt
73. l you logout Session timeouts may be enabled using the xConfiguration Session TimeOut command To enter commands you should start a session and login with user name admin and your password The interface groups information in different commands xstatus Provides a read only interface to determine the current status of the system Information such as current calls and registrations is available through this command group xconfiguration A read write interface to set system configuration data such as IP address and subnet xcommand A miscellaneous group of commands for setting information or obtaining it xhistory Provides historical information about calls and registrations xfeedback An event interface providing information about calls and registrations A command reference is given in section 14 3 1 1 Administrator Account All administration requires you to log in to the administration account with a user name admin and a password The default password is TANDBERG which you are recommended to change as soon as possible Choose a strong password particularly if administration over IP is enabled The password can be changed on the web page System Configuration System or through the command line interface using the command xconfiguration systemunit password new_password If you forget your password it is possible to set a new password using the following procedure e Reboot the Gatekeeper e Connect to the Gatekeeper over the s
74. lectronic equipment TANDBERG Gatekeeper User Manual Operator Safety Summary For your protection please read these safety instructions completely before you connect the equipment to the power source Carefully observe all warnings precautions and instructions both on the apparatus and in these operating instructions Keep this manual for future reference Water and Moisture e Do not operate the apparatus under or near water for example near a bathtub kitchen sink or laundry tub in a wet basement near a swimming pool or in other areas with high humidity e Never install jacks for communication cables in wet locations unless the jack is specifically designed for wet locations e Do not touch the product with wet hands Cleaning e Unplug the apparatus from communication lines mains power outlet or any power source before cleaning or polishing Do not use liquid cleaners or aerosol cleaners Use a lint free cloth lightly moistened with water for cleaning the exterior of the apparatus e Unplug the apparatus from communication lines before cleaning or polishing Do not use liquid cleaners or aerosol cleaners Use a lint free cloth lightly moistened with water for cleaning the exterior of the apparatus Ventilation e Do not block any of the ventilation openings of the apparatus Never cover the slots and openings with a cloth or other material Never install the apparatus near heat sources such as radiators heat regist
75. ll 41 TANDBERG Gatekeeper User Manual 11 3 Unsupported CPL Elements The Gatekeeper 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 Gatekeeper will continue to use its existing policy e time switch e string switch e language switch time switch priority switch redirect e mail e log subaction e lookup remove location 11 4 CPL Examples 11 4 1 Call screening Only allow calls from users with authenticated source addresses See section 6 2 for details on how to enable authentication lt cpl gt lt incoming gt lt address switch field origin gt lt not present gt lt reject gt lt not present gt lt address switch gt lt incoming gt lt cpl gt 11 4 2 Selective Call Screening User fred will not accept calls from anyone at annoying com or from any unauthenticated users All other users will allow any calls lt cpl gt lt incoming gt lt address switch field destination gt 42 TANDBERG Gatekeeper User Manual lt address is fred gt lt address switch field origin subfield host gt lt address subdomain of annoying com gt lt reject gt lt address gt lt otherwise gt lt proxy gt lt otherwise gt lt not present gt lt reject gt lt not present gt lt address switch gt lt
76. 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 Endpoints 1001 1002 should register with the Gatekeeper Endpoint 1003 will register with the Border Controller Gatekeeper and Border Controller are configured to work together to provide firewall traversal If you wish to be able to call using URI dialing in this deployment then the following configuration is required e Enter the address of your DNS server on the Border Controller xConfiguration DNS Server Address dns_server_ip_address e Enable URI dialing on the Border Controller xConfiguration Gatekeeper DNSResolution Mode On e Ensure that URI dialing is disabled on the Gatekeeper This is because you wish calls to be routed from the private network to the Border Controller in order to traverse the firewall xConfiguration URI Dialing Mode Off In order to be able to receive calls placed to example com using URI dialing configure the following 33 TANDBERG Gatekeeper User Manual e Set example com as the domain name you are using on both the Gatekeeper and Border Controller e 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 7 3 9 2 Enterprise Gatekeepers When an enterprise has already deployed a Gatekeeper to ma
77. nage calls within the private network it may be desirable to deploy a traversal solution without having to alter the existing deployment In order to achieve this the TANDBERG Gatekeeper is neighbored with the existing enterprise Gatekeeper as shown in Figure 21 The Enterprise Gatekeeper is also neighbored with the TANDBERG Gatekeeper Enterprise A Bard Neighbori oraer eae N Controller Gatekeeper Gatekeeper Sy Bill EnterpriseA Figure 21 Neighboring with an enterprise gatekeeper The TANDBERG Gatekeeper and Border Controller are configured as described in section 9 1 in order to provide firewall traversal 9 3 Dialing Public IP addresses Figure 22 shows a private endpoint 1001 calling an endpoint on a public IP address In this case the public endpoint is not registered to a Gatekeeper and can only be reached using its IP address In order to successfully traverse the firewall it is necessary for the call to be relayed through the Border Controller the TANDBERG Gatekeeper should not attempt to place the call directly to the public endpoint 34 TANDBERG Gatekeeper User Manual Enterprise Border Controller MCU Gatekeeper 213 228 193 162 Figure 22 Dialing a public IP address In order to achieve this e 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 regist
78. net with restricted bandwidth and two satellite offices each with their own restricted pipes In order to utilize the available bandwidth efficiently the TANDBERG Gatekeeper allows you to model your network and bandwidth controls on individual components of the network Bandwidth controls may be set on a call by call basis and on a total concurrent usage basis Enterprise Gatekeeper Figure 8 Typical network deployment All endpoints registered with your Gatekeeper are part of its local zone As shown in Figure 8 the local zone can contain many different networks with different bandwidth limitations In order to model this the local zone is made up of one or more subzones When an endpoint registers with the Gatekeeper it is assigned to a subzone based on its IP address By default all endpoints registering with the Gatekeeper are assigned to the default subzone This is suitable if you have uniform bandwidth available between all your endpoints When you have differing bandwidth provision as in Figure 8 you should create a new subzone for each pool of endpoints Subzones are added and configured through the web interface on the Gatekeeper Configuration SubZones page Figure 9 or through the command line using the following commands xConfiguration SubZones SubZone 1 100 Name xConfiguration SubZones SubZone 1 100 Subnet IP Prefixlength xConfiguration SubZones SubZone 1 100 Subnet IP Address Subzones may be configu
79. ntact 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 13 1 Upgrading Using HTTP S To upgrade using HTTP S do the following e Point your browser at the IP address of the Gatekeeper You will be prompted for your user name and password e Enter admin as the user name and enter the password then press OK e Select the System Configuration tab and the upgrade section e Enter the release key and press Install Software You will get a new screen where you can upload the software image i Overview System Status System Configuration IP SNMP Misc Upgrade Software Upgrade System Information Software Version N3 0 Hardware Serial Number 37400040 Installed Options 0 non traversal calls 0 traversal calls 0 registrations Installed Option Keys Software Option Add Option Key Add Option Enter the option key in the Key field and press Add Option The system will validate the key and if valid a restart will Add Option be requested for the new option to take effect Install Software Release Key Software Upgrade Enter the release key in the Key field and press Install Software You will be presented with a new page Install Software where you select the software package file to upload e Browse to the file co
80. ntaining the software and press Install You should see a page indicating that upload is in progress 50 TANDBERG Gatekeeper User Manual p Overview System Status System Configuration 7 IP SNMP Misc Upgrade Software upload in progress Software upload in progress Please wait e When the upload is completed you should see the following Si Overview System Status System Configuration IP SNMP Misc Upgrade Software Ugrade Software Complete Software successfully upgraded The system should now be restarted for the new software to take effect Restat e Press Restart You should see a confirmation window j i Overview System Status System Configuration IP SNMP Misc Upgrade Restarting System Restart Next page should automatically be loaded after system has restarted Please Wait If no page has been loaded after 4 minutes press this link e The system will then perform a second reboot to restore system parameters After 3 4 minutes the Gatekeeper is ready for use 13 2 Upgrading Using SCP Using SCP you need to transfer two files to the Gatekeeper 1 A text file containing the release key 2 A file containing the software image NOTE Make sure you transfer the release key file before transferring the software image Also make sure you name the files exactly as described below NOTE The release key file should contain just the 16 character release key To upgrade usin
81. o endpoints in the same subzone consume resource from the subzone s allocation Subzone bandwidths are configured on the Gatekeeper Configuration SubZones page see Figure 6 for a screenshot of the configuration or using the following command line commands xConfiguration SubZones SubZone 1 100 Bandwidth Total Mode xConfiguration SubZones SubZone 1 100 Bandwidth Total Limit xConfiguration SubZones SubZone 1 100 Bandwidth PerCall Mode xConfiguration SubZones SubZone 1 100 Bandwidth PerCall Limit When calls are placed between endpoints in different subzones it is possible to control the bandwidth used on the link between them To do this create a pipe and configure it with the required bandwidth characteristics This pipe is then assigned to a link Calls traversing the link will now take the pipe s bandwidth allocation into consideration Pipes are created and configured on the Gatekeeper Configuration Pipes page Figure 10 or using the following command line commands xConfiguration Pipes Pipe 1 100 Name xConfiguration Pipes Pipe 1 100 Bandwidth Total Mode xConfiguration Pipes Pipe 1 100 Bandwidth Total Limit xConfiguration Pipes Pipe 1 100 Bandwidth PerCall Mode xConfiguration Pipes Pipe 1 100 Bandwidth PerCall Limit 18 TANDBERG Gatekeeper User Manual Overview SystemStatus s System Configuration a Gatekeeper Configuration eeper Authentication Services Zones TraversalZones SubZones Lin
82. oHS Directive is to reduce the impact of disposal of electrical and electronic equipment at end of life The WEEE Directive aims to reduce the amount of WEEE sent for disposal to landfill or incineration by requiring producers to arrange for collection and recycling The RoHS Directive bans the use of certain heavy metals and brominates flame retardants to reduce the environmental impact of WEEE which is land filled or incinerated TANDBERG has implemented necessary process changes to comply with the European RoHS Directive 2002 95 EC and the European WEEE Directive 2002 96 EC Waste Handling In order to avoid the dissemination of hazardous substances in our environment and to diminish the pressure on natural resources we encourage you to use the appropriate take back systems in your area Those systems will reuse or recycle most of the materials of your end of life equipment in a sound way TANDBERG Gatekeeper User Manual TANDBERG products put on the market after August 2005 are marked with a crossed out wheelie bin symbol that invites you to use those take back systems Please contact your local supplier the regional waste administration or http www tandberg net recycling if you need more information on the collection and recycling system in your area Information for Recyclers As part of compliance with the European WEEE Directive TANDBERG provides recycling information on request for all types of new equipment put on the mark
83. of traffic flowing through the Border Controller itself Because the Gatekeeper is only managing endpoints on the LAN its configuration is simpler as 22 TANDBERG Gatekeeper User Manual shown in Figure 15 Border Controller Default sub zone Traversal Zone Gatekeeper Traversal sub zone Figure 15 Gatekeeper example configuration All of the endpoints in the enterprise will be assigned to the default subzone The Traversal subzone controls traversal traffic flowing through the Gatekeeper whilst the Traversal Zone controls all traffic traversing the enterprise firewall and passing on to the Border Controller Both subzones and the Traversal zone are linked the link between the default subzone and the Traversal zone is used by endpoints which can send media directly to the Border Controller The other two links are used by endpoints using the Gatekeeper to traverse the firewall The Gatekeeper is shipped with Default and Traversal Zones and Default and Traversal subzones already configured They are also preconfigured with the links between these zones to allow calls to be placed You may delete or amend the default links if you need to model restrictions of your network The default links may be restored by running the command xCommand DefaultLinksAdd 23 TANDBERG Gatekeeper User Manual 6 Registration Control The TANDBERG Gatekeeper can control which endpoints are allowed to register with it T
84. one totalmode Determines whether bandwidth is controlled for this node None prevents any calls Limited im poses bandwidth limits Unlimited imposes no bandwidth limits 14 3 26 SubZoneDelete xCommand SubZoneDelete lt index gt Deletes the indexed subzone 14 3 27 ZoneAdd xCommand ZoneAdd lt name gt lt address gt Adds a new zone with the specified name and IP address E g xCommand ZoneAdd B 10 0 0 30 The zone is pre configured with a link to the default subzone and a pattern match mode of AlwaysMatch 14 3 28 ZoneDelete xCommand ZoneDelete lt index gt Removes the zone with the specified index 73 TANDBERG Gatekeeper User Manual 14 4 History The history root command xhistory is used to display historical data on the Gatekeeper To list all xhistory commands type xhistory To list all history data type xhistory To show a specific set of history data type xhistory lt name gt xhistory calls xhistory calls call lt n gt Displays history data for up to the last 255 calls handled by the Gatekeeper Call entries are added to the Call History on call completion Call histories are listed in reverse chronological order of completion time xhistory registrations xhistory registrations registration lt n gt Displays history data for up to the last 255 registrations handled by the Gatekeeper Registration entries are added to the Registration History on unregistration of H 323 entities Registration
85. per with no alias information The Gatekeeper may be configured to associate all such anonymous calls with a single destination alias This is achieved with the command xConfiguration Gatekeeper Unregistered Caller Fallback lt destination gt 4 2 Calling to an unregistered endpoint System Configuration Pal Gatekeeper Configuration B Overview System Status Gatekeeper Authentication Services Zones TraversalZones SubZones Links Pipes Restrictions Credentials File Gatekeeper Configuration Configuration Local prefix Call routed Auto dscovery Calls to unknown IP addresses Indirect wf Allow calls from urregstered callers Fallback alias for unregistered caller destination g Figure 7 Calling an unknown IP address Calls can be placed to an unregistered endpoint by dialing its IP address or using an H 323 URI if the DNS system has been appropriately configured If URI dialing is used DNS is queried for a call signaling address and if found the call is placed to that address See section 7 for details of how to configure the Call Signalling SRV Record It is sometimes undesirable for a system to place a call to an IP address directly Instead you may want a neighbor to place the call on behalf of the Gatekeeper You can configure this on the Gatekeeper using the command xConfiguration Gatekeeper CallsToUnknownIPAddresses lt Off Indirect Direct gt or using the web page Gatekeeper Configuration Gatek
86. pers Alternate Gatekeeper support is provided to increase the reliability of your deployment If one Gatekeeper 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 You should configure Alternates identically for all registration and call features such as authentication bandwidth control and policy If you do not do this endpoint behavior will vary unpredictably depending on which Alternate it is currently registered with Alternates should also be deployed on the same LAN as each other so that they may be configured with the same routing information such as local domain names and local domain subnet masks Each Gatekeeper may be configured with the IP addresses of up to five Alternates When an endpoint registers with the Gatekeeper it is presented with the IP addresses of all the Alternates If the endpoint loses contact with its initial Gatekeeper it will seek to register with one of the Alternates This may result in your endpoint community s registrations being spread over all the Alternates When a Gatekeeper receives a Location Request if it cannot respond from its own registration database it will query all of its Alternates before responding This allows the pool of registrations to be treated as if they were registered with a single Gatekeeper The Alte
87. r This is used to identify the Gatekeeper by the TAND BERG Management Suite See the xConfiguration SystemUnit command in sec tion 14 2 18 for more information on setting the name b Automatic discovery If you have multiple Gatekeepers in the same network you may want to disable automatic discovery on some of them See the xConfiguration Gatekeeper AutoDiscovery command in section 14 2 4 c The DNS server address and the domain name if the Gatekeeper will be con figured with hostnames instead of IP address or if URI dialing is required See xConfiguration IP DNS Server Address command in section 14 2 6 for more infor mation 12 Reboot the Gatekeeper by typing the command xCommand boot to make your new settings take effect 13 Disconnect the serial cable NOTE To securely manage the Gatekeeper you should disable HTTP and Telnet using the encrypted HTTPS and SSH protocols instead For increased security disable HTTPS and SSH as well using the serial port to manage the system NOTE If you do not have an IP gateway configure the Gatekeeper with an unused IP address that is valid in your subnet TANDBERG Gatekeeper User Manual 3 Getting started 3 1 System Administration To configure and monitor the TANDBERG Gatekeeper you can either use the web interface or a command line interface The command line interface is available over SSH Telnet and through the serial port By default administration sessions remain active unti
88. recipient of the message e Registration Rejected e If present the first E 164 e Call Attempted Alias associated with the e Call Connected recipient of the message e Call Disconnected e Call Rejected e Incoming Message e Outgoing Message e Call Bandwidth Changed Time A full UTC timestamp in All Events YYYY MM DD HH MM SS format Using this format permits simple ASCII text sort ing ordering to naturally sort by time This is included due to the limitations of standard syslog timestamps Level The level of the event as defined in section 12 3 All events In addition to the events described above a syslog info event containing the string MARK will be logged once an hour to provide confirmation that logging is still active 12 5 Remote Logging It is often convenient to collect all event logs in a single location A computer running a BSD style syslog server as defined in RFC3164 4 may be used as the central log server ensure that remote logging is enabled A Gatekeeper will not act as a central logging server for other systems The Gatekeeper should be configured with the address of the central log server xConfiguration Log Server Address server_address 49 TANDBERG Gatekeeper User Manual 13 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 Gatekeeper a valid Release key and software file is required Co
89. red with links joining them to each other and to other zones These links are used to calculate how a call is routed over the network and so which zones and subzones are involved If multiple routes are possible your Gatekeeper will select the one with the fewest links 17 TANDBERG Gatekeeper User Manual Hioverview SystemStatus System Configuration amp Gatekeeper Configuration Gatekeeper Authentication Services Zones TraversalZones SubZones Links Pipes Restrictions Credentials Files Add New SubZone Configuration Name Subnet 1 Address Prefix Len Subnet 2 Address Prefix Len Subnet 3 Address Prefix Len Subnet 4 Address T Prefix Len Re Subnet 5 Address Prefix Len 5 Total bandwidth mode Unlimited yf a Total bandwidth kbps Koon Per call inter bandwidth mode Unlimited yf Per call inter bandwidth kbps 192 O Per call intra bandwidth mode Unlimited y 2 Per call intra bandwidth kbps fizz D x B Save Cancel ge D a Figure 9 Configuring a SubZone Links may be configured through the web interface on the Gatekeeper 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 xConfiguration Links Link 1 100 Pipe1 Name xConfiguration Links Link 1 100 Pipe2 Name Each subzone may be configured with its own bandwidth limits Calls placed between tw
90. rface on the Gatekeeper To do this navigate to the Gatekeeper Configuration Files page and click on the links for the schemas Copy the downloaded schemas to the OpenLDAP schema directory etc openldap schemas commobject 1ldif etc openldap schemas h323identity 1ldif etc openldap schemas h235identity 1ldif Edit etc openldap slapd conf to add the new schemas You will need to add the following lines include etc openldap schemas commobject 1ldif include etc openldap schemas h323identity 1ldif include etc openldap schemas h235identity 1ldif The OpenLDAP daemon slapd must be restarted for the new schemas to take effect B 2 3 Adding H 350 objects Create the organizational hierarchy Create an Idif file with the following contents This example creates a single organisational unit to contain the H 350 objects dn ou h350 dc my domain dc com objectClass organizationalUnit ou h350 Add the ldif file to the server using the command slapadd 1 lt ldif_file gt This organizational unit will form the BaseDN to which the Gatekeeper will issue searches In this example the BaseDN will be ou h350 dc my domain dc com NOTE It is good practice to keep the H 350 directory in its own organizational unit to separate out H 350 objects from other types of objects This allows access controls to be setup which only allow the Gatekeeper read access to the BaseDN and therefore limit access to other sections of the directory
91. rnate Gatekeepers can be configured within the web interface of the Gatekeeper by navigating to Gatekeeper Configuration Gatekeeper Please see Figure 5 for a screenshot of a sample configuration 11 TANDBERG Gatekeeper User Manual System Configuration amp Gatekeeper Configuration Gatekeeper Authentication Services Zones TraversalZones SubZones Links Pipes Restrictions Credentials Files Overview System Status Gatekeeper Configuration Configuration Local prefix Call routed B Auto dscovery Calls to unknown IP addresses Indirect vf Allow calls from urragstered callers z Fallback alias for unregistered caller destination Allow forwarding of location requests gt Allow DNS resolution F Time to live seconds z Call time to live seconds 120 CPL paiicy gt Downspeeding Allow downspeeding at total bandwidth limit F Allow downspeedng at per call bandwidth limit je Local domain Domain name 5 ENUM Allow ENUM resolution i DNS Suffix 1 fele4 arpa DNS Suffix 2 DNS Suffix 3 DNS Suffix 4 z DNS Suffix 5 Alternate Gatekeepers oO Gatekeeper 1 IP address f 0 0 0 Port 1719 Gatekeeper 2 IP ackress f 0 0 0 Port 1719 Gatekeeper 3 IP adress f 0 0 0 Port i719 O Gatekeeper 4 IP address f 0 0 0 Port 1719 fat Gatekeeper 5 IP address pooo Port 1719 a p Moritor Alternates 3 B Oe D E Figure 5 Alternate Gatekeeper configuration 3 7 Call signaling When an endpoint wants to call
92. s 74 registrations 74 xStatus Calls 37 calls 69 Zone 87 zone 17 19 66 68 default 19 23 DNS 31 H 323 9 traversal 21 23
93. s 4 fo o 00 5 Address 5 0 0 0 o Domain Date and Time Settings NTP Server 10 44 8 1 Server Status Active 10 44 8 1 123 Timezone Europe London zi ae oO A EEC pe a gt Figure 3 Selecting IP Protocol By default if you attempt to register an alias which has already been registered with the system your registration will be rejected This helps you to identify when two users have a conflicting alias In some deployments an endpoint may frequently receive a new IP address causing unwanted registration rejections When it tries to register it may be rejected because the Gatekeeper still has a registration from its old IP address The Gatekeeper may be configured to allow an endpoint to overwrite the old IP address with the command xConfiguration Gatekeeper Registration ConflictMode lt Overwrite Reject gt Consult the endpoint documentation for information on how to configure it with a Gatekeeper NOTE When URI dialing is used to discover an endpoint the URI used is based on either the H 323 ID or the E 164 alias that the endpoint registered with The local domain is then added to this For more information on URI dialing see section 7 3 5 Neighbor Gatekeepers As you start deploying more than one Gatekeeper or Border Controller it is useful to neighbor the systems together so that they can exchange information about registered endpoints Each Gatekeeper or Border Controller forms an H 323 zone and is responsible for the endpoin
94. s continuously improving TANDBERG s prod ucts towards less use of environmentally hazardous components and substances as well as to make the products easier to recycle TANDBERG s products are Communication Solutions The idea of these solutions is to reduce the need for expensive time demanding and polluting transport of people Through people s use of 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 TANDBERG s policy is to make sure our partners produce our products with minimal influence on the environment and to demand and audit their compatibility according to applicable agreements and laws national and international Environmental Considerations Like other electronic equipment the TANDBERG Gatekeeper contains components that may have a detrimental effect on the environment TANDBERG works continuously towards eliminating these substances in our products e Printed wiring boards made of plastic with flame retardants like Chloride or Bromide e Component soldering that contains lead e Smaller components containing substances with possible environmental effect After the product s end of life cycle it should be returned to authorized waste handling and should be treated according to National and International Regulations for waste of e
95. s gives the program a new root directory which means that the configuration files may not appear where you expect them to be To see if this is the case on your system run ps aux grep named This will give the command line that named the BIND server was invoked with If there is a t option then the path following that is the new root directory and your files will be located relative to that root In etc named conf look for a directory entry within the options section This will give the directory in which the zone files are stored possibly relative to a new root directory In the appropriate zone section a file entry will give the name of the file containing the zone details For more details of how to configure BIND servers and the DNS system in general see 6 A 2 Verifying the SRV record There are a range of tools available to investigate DNS records One commonly found on Microsoft Windows and UNIX platforms is nslookup Use this to verify that everything is working 77 TANDBERG Gatekeeper User Manual as expected nslookup querytype srv h323ls _udp example com and check the output 78 TANDBERG Gatekeeper 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
96. t lt 1 255 gt Specifies the hop count to be used when originating an LRQ xconfiguration Zones TraversalZone Match 1 5 Mode lt AlwaysMatch PatternMatch Disabled gt The zone match mode determines when an LRQ will be sent to gatekeepers in the zone If the mode is set to AlwaysMatch the zone will always be queried If the mode is set to PatternMatch the zone will only be queried if the alias queried for matches the corresponding pattern If the mode is set to Disabled the zone will never be queried xconfiguration Zones TraversalZone Match 1 5 Pattern String lt pattern gt The pattern to be used when deciding whether or not to query a zone This is only used if the zone s match mode is set to AlwaysMatch xconfiguration Zones TraversalZone Match 1 5 Pattern Type lt Prefix Suffix gt Determines whether the pattern string being checked should appear at the beginning or end of an alias xconfiguration Zones TraversalZone Match 1 5 Pattern Behaviour lt Strip Leave gt 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 lt name gt An administrator specified name for the zone xconfiguration Zones Zone 1 100 Gatekeeper 1 6 Address lt address gt Specifies the IP addresses of the gatekeepers in the zone Multiple addresses allows support for alternate gatekeepers xconfiguration Zones Zone 1 100 Ga
97. t to src and dst joining them together 14 3 13 DisconnectCall xCommand DisconnectCall lt callid gt Disconnects the specified call 14 3 14 FeedbackRegister xCommand FeedbackRegister lt ID gt lt URL gt lt Expression gt 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 The following Expressions are valid Event Event CallAttempt Event Connected Event Disconnected Event ConnectionFailure Event Registration Event Unregistration Event Bandwidth Status Status Calls Status Registrations History History Calls History Registrations The following would be a typical use Back slashes are used to indicate continuation lines xCommand FeedbackRegister ID 1 URL http 10 1 1 1 SystemManagementService asmx Expression Event CallAttempt Status Registration FeedbackDeregister 14 3 15 FeedbackDeregister xCommand FeedbackDeregister lt ID gt Deregisters the specified Feedback Expression All registered Feedback Expressions may be removed with xCommand FeedbackDeregister 0 LinkAdd 71 TANDBERG Gatekeeper User Manual 14 3 16 FindRegistration xCommand FindRegistration lt alias gt Returns information about the registration associated with alias alias must be registered on the Gatekeeper on which the command is issued See also xCommand Locate 14
98. tekeeper 1 6 Port lt port gt Specifies the port on which the indexed gatekeeper is listening for RAS messages 67 TANDBERG Gatekeeper User Manual xconfiguration Zones Zone 1 100 HopCount lt count gt Specifies the hop count to be used when originating an LRQ xconfiguration Zones Zone 1 100 Monitor lt On Off gt If Zone monitoring is enabled an LRQ will be periodically sent to the zone gatekeeper If it fails to respond that gatekeeper will be marked as inactive xconfiguration Zones Zone 1 100 Match 1 5 Mode lt AlwaysMatch PatternMatch Disabled gt The zone match mode determines when an LRQ will be sent to gatekeepers in the zone If the mode is set to AlwaysMatch the zone will always be queried If the mode is set to PatternMatch the zone will only be queried if the alias queried for matches the corresponding pattern If the mode is set to Disabled the zone will never be queried xconfiguration Zones Zone 1 100 Match 1 5 Pattern String lt pattern gt The pattern to be used when deciding whether or not to query a zone This is only used if the zone s match mode is set to AlwaysMatch xconfiguration Zones Zone 1 100 Match 1 5 Pattern Type lt Prefix Suffix gt Determines whether the pattern string being checked should appear at the beginning or end of an alias xconfiguration Zones Zone 1 100 Match 1 5 Pattern Behaviour lt Strip Leave gt Determines whether the matched pattern s
99. the System Configuration IP page see Figure 18 for the IP Configuration screen If you want others to be able to reach you using URI dialing add a record to your DNS information as described in Appendix A Endpoints will typically register with the Gatekeeper without their domain name The Gatekeeper needs to match a request for fred example com to a registration for fred To do this it must be configured with the name of the domain in which its endpoints belong This is set using xConfiguration Gatekeeper LocalDomain DomainName lt name gt If URI dialing is being used in conjunction with firewall traversal DNSResolution Mode should only be enabled on the Border Controller and on any Gatekeepers on the public network The DNS records should be updated with the address of the Border Controller as the authoritative Gatekeeper for the enterprise This ensures that calls placed using URI dialing enter and leave the enterprise through the Border Controller allowing successful traversal of the firewall The LocalDomain DomainName should be set on both the Gatekeeper and the Border Controller Any Alternates should also have the same LocalDomain Domain Name 7 2 Receiving a call using URI dialing When a call is placed using URI dialing the Gatekeeper will receive a request containing the dialed URI in the form user host As described in section 7 3 several mechanisms could have 28 TANDBERG Gatekeeper User Manual Overview System
100. the local authentication database 14 3 7 CredentialDelete xCommand CredentialDelete lt index gt Deletes the indexed credential 14 3 8 DefaultLinksAdd xCommand DefaultLinksAdd Restores the factory default links for bandwidth control 14 3 9 DefaultValuesSet xCommand DefaultValuesSet Level lt level gt 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 e IP address subnet mask gateway and interface speed The default IP address is 192 168 0 100 e COM port baud rate speed data bits parity stop bits e SNMP community name and host address e system name e password e option key e release key Note that DefaltValuesSet will not add the links with which the system ships from the factory Use the DefaultLinksAdd command to do that Certificates and policy files are not removed 14 3 10 DenyListAdd xCommand DenyListAdd lt denied_alias gt Add an entry to the deny list This is used by the registration restriction policy 70 TANDBERG Gatekeeper User Manual 14 3 11 DenyListDelete xCommand DenyListDelete lt index gt Removes the pattern from the deny list at the specified index 14 3 12 Dial xCommand Dial callSrc lt src gt callDst lt dst gt Bandwidth lt bandwidth gt Places call halves ou
101. time represent the local time at which the message was logged host_name is the name of the system generating the log message facility the name of the program generating the log message will be tandberg for all messages originating from TANDBERG processes but will differ for messages from third party processes which are used in the Gatekeeper 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 The first two fields are always Field Example Description Time Time 2006 20 01 14 02 17 The UTC date and time at which the event was generated Event Event RegistrationRequest The event which caused the log message to be generated and the last field of the message is always the event level Field Example Description Level Level 1 The level of the event being logged 44 12 3 Event Levels TANDBERG Gatekeeper User Manual 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 Level Description Level 1 User Level 2 Protocol Level 3 Protocol Verbose 12 4 Logged Events The Events logged as are follows Table 2 Easily human re
102. tion database xconfiguration Authentication Database lt LocalDatabase LDAPDatabase gt Select between a local database and a remote LDAP repository for the storage of password information for authentication The default is LocalDatabase xconfiguration Authentication LDAP BaseDN lt S 0 255 gt The Distinguished Name to use when connecting to an LDAP server The default is an empty string xconfiguration Authentication LDAP AliasOrigin lt LDAP Endpoint Combined gt Specifies which aliases from the endpoint or the database should be used to register the endpoint Defaults to LDAP xconfiguration Authentication Mode lt On Off gt Whether or not to use H 235 authentication of calls and registrations The default is Off no authentication is required 14 2 2 Ethernet xconfiguration Ethernet Speed lt Auto 10half 10full 100half 100full gt Sets the speed of the Ethernet link Use auto to automatically configure the speed To get the current speed use xstatus Ethernet Speed You must restart the system for changes to take effect The default is Auto 14 2 3 ExternalManager xconfiguration ExternalManager Address lt IPAddr gt 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 lt path gt Sets the URL of the External Manager 57 T
103. tion using using DNS SRV ENUM algorithm A Faveni Ea No lt resemble E 164 gt Yes a address No Yes Yes AA di LRQ all alive strong A OON Araon ee on NE ea LR from Known 4 gistered EP mani AAS e lt GK received by and alias does gt gt that match the Alias recone nosar domain A Pte Receive Yes lt lt N Z am Lice 7 No y LRQ all weak PF ie LRQ all weak matching non gt lt Ra Na gt No matching Traversal Traversal Zones B Zones i4 Figure 6 Location decision flow diagram TANDBERG Gatekeeper User Manual 4 Unregistered Endpoints Although most calls are made between endpoints registered with a Gatekeeper or Border Controller it is sometimes necessary to place a call to or from an unregistered endpoint 4 1 Calling from an unregistered endpoint An unregistered endpoint can call an endpoint registered with the Gatekeeper If there are no firewalls between the unregistered endpoint and the called endpoint it is possible though not recommended to place the call by dialing the target endpoint s IP address A better way of placing the call from an unregistered endpoint is to pass the alias of the called endpoint to the Gatekeeper The Gatekeeper will then resolve the alias and place the call as normal Not all endpoints allow you to enter an alias and an IP address to which the call should be placed In that case you can simply place the call to the IP address of the Gatekee
104. ts within that zone The simplest approach is to assign each endpoint a unique alias and divide the endpoint registrations between the Gatekeepers and Border Controllers Each Gatekeeper or Border Controller is then configured with the addresses of all other Gatekeepers and Border Controllers When a system receives a call for an endpoint which is not registered with it will send out a TANDBERG Gatekeeper 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 large number of location requests An alternative deployment would use a structured dial plan endpoints are assigned an alias based on the system they are registering with Using E 164 aliases each Gatekeeper or Border Controller would be assigned an area code When the Gatekeepers and Border Controllers are neighbored together each neighbor is configured with its corresponding area code as a prefix That neighbor will now will only be queried for calls to numbers which begin with its prefix Ina URI based dial plan similar behaviour may be obtained by configuring neighbors with a suffix to match the desired domain name It may be desirable to have endpoints register with just the subscriber number the last part of the E 16
105. ty CA that issued the LDAP server with its certificate must be uploaded to the Gatekeeper To install the CAs certificate navigate to the Gatekeeper Configuration Files page and upload the CA certificate as a Trusted CA certificate 27 TANDBERG Gatekeeper User Manual 7 URI Dialing 7 1 Making a call using URI dialing If an alias is not located in the Gatekeeper 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 Without URI dialing you need to neighbor all the systems to each other This does not scale well as the number of systems grows It is also inconvenient for making one off calls to endpoints registered with previously unknown systems Using URI dialing you call using an H 323 URI which looks like an email address The destination Gatekeeper is found from the domain name the part after the in the same way that an email server is found The decision as to whether or not to use URI dialing is governed by the current state of xConfiguration Gatekeeper DNSResolution Mode lt On Off gt or using the web interface on the Gatekeeper Configuration Gatekeeper page You will also need to configure a DNS server for the systems to query This is set using xConfiguration IP DNS Server 1 Address lt address gt or using the web interface on
106. ubzones xconfiguration SubZones DefaultSubZone Bandwidth PerCall Limit lt 1 100000000 gt Per call bandwidth of the default subzone xconfiguration SubZones DefaultSubZone Bandwidth PerCall Mode lt None Limited Unlimited gt Whether or not the default subzone is enforcing total bandwidth restrictions None corresponds to no bandwidth available xconfiguration SubZones DefaultSubZone Bandwidth Total Limit lt 1 100000000 gt Total bandwidth available on the default subzone 64 TANDBERG Gatekeeper User Manual xconfiguration SubZones DefaultSubZone Bandwidth Total Mode lt None Limited Unlimited gt Whether or not the default subzone is enforcing per call bandwidth restrictions None corresponds to no bandwidth available xconfiguration SubZones TraversalSubZone Bandwidth PerCall Limit lt 1 100000000 gt Per call bandwidth available on the traversal subzone xconfiguration SubZones TraversalSubZone Bandwidth PerCall Mode lt None Limited Unlimited gt Whether or not the traversal subzone is enforcing per call bandwidth restrictions None corre sponds to no bandwidth available xconfiguration SubZones TraversalSubZone Bandwidth Total Limit lt 1 100000000 gt Total bandwidth available on the traversal subzone xconfiguration SubZones TraversalSubZone Bandwidth Total Mode lt None Limited Unlimited gt Whether or not the traversal subzone is enforcing total bandwidth restrictions None corresponds to no bandwidt
107. wo 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 to control which of those authenticated endpoints may register with a particular Gatekeeper 6 1 Registration Restriction Policy When an endpoint registers with your Gatekeeper it presents a list of aliases By default registration restriction policy is set to None In this state any endpoint may register The registration restriction policy can be configured using the following command xConfiguration Gatekeeper Registration RestrictionPolicy None AllowList DenyList or by using the web interface on the Gatekeeper Configuration Restrictions page see Figure 16 for a screenshot of the Registration Restrictions Configuration If the policy is set to AllowList only those endpoints with an alias which matches an entry in the AllowList may register Conversely if the policy is set to DenyList all endpoints may register unless they match an entry on the DenyList Allow lists and Deny lists are mutually exclusive only one may be in use at any given time Hoverview SystemStatus System Configuration a Gatekeeper Configuration Gatekeeper Authentication ei nes TraversalZones SubZones Links Pipes Restrictions Credentials Files Add New
108. x Leg leg index Alias dest call_index and leg_index are used to determine which call and participant is to be transferred These indices may be determined through inspection of the output of xStatus Calls The endpoint denoted by leg_index will be disconnected and replaced by the endpoint corre sponding to dest The Gatekeeper must be operating in call routed mode and call transfer must be enabled either with the command xConfiguration Services CallTransfer Mode lt OQn Off gt or through the web page Gatekeeper Configuration Services shown in figure 23 System Configuration s Gatekeeper Configuration ones TraversalZones SubZones Links Pipes Restrictions Credentials Files Service Configuration 3 Call Transfer Allow call transfer Figure 23 Enabling call transfer 10 3 Disconnecting a call An existing call may be disconnected by issuing the command xCommand DisconnectCall lt index gt 37 TANDBERG Gatekeeper User Manual where index is the call index as reported by xStatus Calls 38 TANDBERG Gatekeeper User Manual 11 Call Policy Your TANDBERG Gatekeeper 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 Gatekeeper executes the script to decide based on the source and destination of the call wheth
109. y up to 10 IP addresses to log information for all if none specified Setting syslog 0 will turn off tracing 76 TANDBERG Gatekeeper 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 1 Microsoft DNS Server It is possible to add the SRV record using either the command line or the MMC snap in To use the command line on the DNS server open a command window and enter dnscmd RecordAdd domain service_name SRV service_data Where domain is the domain into which you wish to insert the record service_name the name of the service you re adding and service_data the priority weight port and server providing the service as defined by RFC 2782 For example dnscmd RecordAdd example com _h323ls _udp SRV 1 0 1719 gatekeeper1 example com A 1 1 BIND8 amp 8 amp 9 BIND is a commonly used DNS server on UNIX and Linux systems Configuration is based around two sets of text files named conf which describes which zones are represented by the server and a selection of zone files which describe the detail of each zone BIND is sometimes run chrooted for increased security Thi

TANDBERG User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents