technical description of tandberg mcu with … description of tandberg mcu with software version d3...

Technical Description of TANDBERG MCU with software version D3

D12925 Rev. 03 1

Technical Description of TANDBERG MCU

with software version D3

TANDBERG

D12925 Rev. 03


D12925 Rev. 03 2

Table of contents 1 INTRODUCTION ............................................................................................................................................ 5

2 PRODUCT DESCRIPTION............................................................................................................................ 6 2.1 SOFTWARE VERSIONS..................................................................................................................................... 6 3 OPERATION AND USER INTERFACE ...................................................................................................... 6

4 MCU INTERFACES & FEATURES ............................................................................................................. 7 4.1 NETWORK INTERFACES AND FEATURES ......................................................................................................... 7

4.1.1 Mixed ISDN and IP Conferences.............................................................................................................. 8 4.1.2 Multiple conferences................................................................................................................................. 8 4.1.3 PRI E1/T1 ISDN ....................................................................................................................................... 8

4.1.3.1 ISDN numbers ................................................................................................................................................. 8 4.1.3.2 PRI E1/T1 ISDN.............................................................................................................................................. 9

4.1.4 Ethernet / LAN Interface (H.323) ........................................................................................................... 11 4.1.4.1 Quality of Service features (QoS) .................................................................................................................. 11 4.1.4.2 Automatic selection of H.323 or H.320 outgoing calls.................................................................................. 12 4.1.4.3 IP adaptive bandwidth management .............................................................................................................. 12 4.1.4.4 Dynamic playout buffering ............................................................................................................................ 12 4.1.4.5 Asymmetrical media capabilities ................................................................................................................... 12 4.1.4.6 Diagnostic tools for IP ................................................................................................................................... 13 4.1.4.7 Latency & Jitter ............................................................................................................................................. 13 4.1.4.8 Layer 4 Ports used in H.323 meetings ........................................................................................................... 13 4.1.4.9 IP packet sizes ............................................................................................................................................... 14 4.1.4.10 Intelligent Packet Loss Recovery (IPLR) ...................................................................................................... 14

4.1.5 LEDs Description ................................................................................................................................... 15 4.1.5.1 Description of PRI Alarms ............................................................................................................................ 15

4.1.6 Intelligent Call Management (ICM) ....................................................................................................... 16 4.1.7 MCU Capacity ........................................................................................................................................ 17

4.1.7.1 MCU Capacity – typical scenarios................................................................................................................. 18 4.1.8 Dial Profiles............................................................................................................................................ 18 4.1.9 Secure Conference (Encryption)............................................................................................................. 19

4.1.9.1 Number of encrypted sites (software option 16+16)...................................................................................... 20 4.1.9.2 Number of encrypted sites (software option 8+8).......................................................................................... 20

4.1.10 MCU control (H.231/H.243).............................................................................................................. 20 4.1.10.1 H.243 Password............................................................................................................................................. 21

4.2 AGGREGATION STANDARDS ......................................................................................................................... 22 4.2.1 BONDING............................................................................................................................................... 22

4.2.1.1 ISDN channel set-up...................................................................................................................................... 22 4.2.2 H.221 ...................................................................................................................................................... 22 4.2.3 H0 ........................................................................................................................................................... 22

4.3 RS232 INTERFACE/APPLICATION PROGRAMMABLE INTERFACE (API) ......................................................... 23 4.3.1 API commands ........................................................................................................................................ 23

4.4 VIDEO FEATURES ......................................................................................................................................... 24 4.4.1 Optimised Video Compression................................................................................................................ 24

4.4.1.1 The ITU standard H.263 provides ................................................................................................................. 24 4.4.1.2 The ITU standard H.264 ................................................................................................................................ 24

4.4.2 Video Formats ........................................................................................................................................ 25 4.4.3 Asymmetric Video Formats..................................................................................................................... 25 4.4.4 Best Impression....................................................................................................................................... 25

4.4.4.1 Dynamic/Auto Layout switching ................................................................................................................... 25 4.4.4.2 Automatic Resolution switching.................................................................................................................... 27 4.4.4.3 Video Transcoding ........................................................................................................................................ 28

4.4.5 Duo Video ............................................................................................................................................... 29


D12925 Rev. 03 3

4.4.5.1 Duo Video Interoperability with other vendors ............................................................................................. 29 4.4.6 Custom pictures ...................................................................................................................................... 30

4.5 AUDIO FEATURES ......................................................................................................................................... 31 4.5.1 Audio levelling/ Automatic Gain Control (AGC).................................................................................... 31 4.5.2 Telephone Noise Suppression ................................................................................................................. 31 4.5.3 Custom Sounds........................................................................................................................................ 31 4.5.4 Entry/Exit tones ...................................................................................................................................... 31 4.5.5 Muting of audio ...................................................................................................................................... 31 4.5.6 Telephony................................................................................................................................................ 32 4.5.7 Allow G.728 ............................................................................................................................................ 32 4.5.8 Audio Compression Algorithms .............................................................................................................. 32

4.6 SYSTEM MANAGEMENT................................................................................................................................ 33 4.6.1 Ethernet/LAN Interface........................................................................................................................... 33 4.6.2 Platform Requirements ........................................................................................................................... 33 4.6.3 Protocols Supported ............................................................................................................................... 34 4.6.4 System Management Functionality ......................................................................................................... 34

4.6.4.1 Remote software upgrades using FTP: .......................................................................................................... 34 4.6.4.2 Management using a standard Web-browser: ................................................................................................ 34 4.6.4.3 Management using a standard Telnet-client: ................................................................................................. 35 4.6.4.4 Management using a terminal connected to the RS232 port:......................................................................... 35

4.6.5 Security ................................................................................................................................................... 35 4.6.5.1 HTTPS, TLS/SSL.......................................................................................................................................... 35 4.6.5.2 Disable Services............................................................................................................................................. 36 4.6.5.3 Security Alert................................................................................................................................................. 36 4.6.5.4 Authentication of Remote Management System – (Telnet Challenge) .......................................................... 36

4.6.6 Layer 4 ports used by the system ............................................................................................................ 37 5 MISCELLANEOUS FEATURES................................................................................................................. 38 5.1 DISTRIBUTED MCUS .................................................................................................................................... 38 5.2 PHONE BOOK ................................................................................................................................................ 39

5.2.1 Group Entries ......................................................................................................................................... 39 5.3 MAXIMUM MEETING DURATION.................................................................................................................... 39 5.4 FILE SYSTEM (FTP) ...................................................................................................................................... 39

5.4.1 Picture files............................................................................................................................................. 40 5.4.2 Sound files............................................................................................................................................... 40 5.4.3 Other files ............................................................................................................................................... 40

6 ENVIRONMENTAL ISSUES....................................................................................................................... 41 6.1 TANDBERG’S ENVIRONMENTAL POLICY ................................................................................................... 41 6.2 ENVIRONMENTAL CONSIDERATIONS............................................................................................................. 41 7 PRODUCT APPROVALS............................................................................................................................. 42 7.1 CONNECTION OF TELE-TERMINAL EQUIPMENT ............................................................................................ 42 7.2 EMC EMISSION - RADIATED ELECTROMAGNETIC INTERFERENCE................................................................ 42 7.3 EMC IMMUNITY........................................................................................................................................... 42 7.4 ELECTRICAL SAFETY .................................................................................................................................... 42 7.5 EMC IMMUNITY........................................................................................................................................... 42 7.6 NEBS APPROVAL ......................................................................................................................................... 43 8 PRODUCT RELIABILITY........................................................................................................................... 43

9 TECHNICAL SPECIFICATION OF TANDBERG MCU......................................................................... 44 9.1 MECHANICAL INFORMATION......................................................................................................................... 44 9.2 PACKAGING .................................................................................................................................................. 44 9.3 OPERATING TEMPERATURE AND HUMIDITY ................................................................................................. 45


D12925 Rev. 03 4

9.4 STORAGE AND TRANSPORT TEMPERATURE .................................................................................................. 45 9.5 SYSTEM POWER CONSUMPTION ................................................................................................................... 45 10 TECHNICAL SPECIFICATION SHEET ................................................................................................... 46


D12925 Rev. 03 5

1 Introduction The TANDBERG MCU is a Multipoint Control Unit designed for connecting up to 16 videoconferencing endpoints and 16 telephones (i.e. 32 sites in total) in the same meeting giving all participants the same high quality video and/or audio as if they were connected in a point-to-point meeting. The MCU implements the ITU-T H.320 standard for video compression and a combination of H.221 and BONDING for communication on up to 30 ISDN B-channels as well as ITU-T H.323 v.4 standard for communication up to 2 Mbps over IP networks. The TANDBERG MCU is ‘configurationless’ in the sense that no extensive knowledge is required for installation and maintenance. All features are included in the MCU – thus, there is no additional hardware required to use any of the inbuilt features. All features of the TANDBERG MCU are based on standards set by the ITU-T. The TANDBERG MCU is best utilised when used together with TANDBERG Management Suite (TMS) and TANDBERG Scheduler, since they have incorporated features like Graphical monitoring and Scheduling (Optional). Major features supported:

• Up to three separate and independent conferences • Mixed ISDN/IP conferences • Best Impression (i.e. a variety of picture layouts) • Custom video formats (e.g. XGA video resolution) • Full implementation of Downspeeding • Secure Conference (AES Encryption) • Duo Video • Up to 16 videoconferencing endpoints + 16 telephones • Support for TANDBERG Scheduler and TMS - TANDBERG Management Suite -

(Optional) • The ITU-T standard H.264 video compression algorithm


D12925 Rev. 03 6

2 Product Description

The TANDBERG MCU is built on a standard 19-inch rack mounted chassis of only 1U in height.

2.1 Software Versions There are two software options for the TANDBERG MCU; differentiated by maximum possible number of sites:

• 8 video endpoints + 8 telephone endpoints (i.e. total of 16) • 16 video endpoints + 16 telephone endpoints (i.e. total of 32)

Upgrading from the standard version 8+8 to the optional 16+16 is easily done by entering Software Option keys inserted e.g. via the MCU’s web interface.

3 Operation and User Interface The TANDBERG MCU is normally controlled via the web interface, but any user may schedule meetings on the MCU by using the TANDBERG Management Suite (TMS) or the TANDBERG Scheduler. The TANDBERG MCU can also be controlled via Telnet (or the RS232 port) by using a comprehensive set of API commands1. This enables the MCU to be controlled by a different user interface, such as an AMX or Crestron control systems. For information on how to operate the system, please see the documents TANDBERG MCU User Manual or TANDBERG MCU API supplied with the system.

1 Please, refer to document ‘TANDBERG MCU API’ (D12930)


D12925 Rev. 03 7

4 MCU Interfaces & Features Extensive use of industry standard interfaces and connectors ensure effortless integration of external equipment with the TANDBERG MCU. These interfaces can easily be controlled via one of the intuitive user interfaces.

4.1 Network Interfaces and Features Network Interfaces 4 x PRI (RJ-45 Jack) Primary Rate (G.703) Interfaces 2 x Ethernet (RJ-45 Jack) LAN interfaces (10/100 Mb)2

• 4 x PRI (RJ-45 jack) Primary Rate (G.703) interface for transmission speeds from 56

kbps up to 2 Mbps (1.5 Mbps PRI/T1). • 2 x Ethernet (RJ-45 jack) Local Area Network interface (10/100Mb) for transmission

speeds up to 2 Mbps2.

2 Only Ethernet port no. 1 is used in software version D3 (Ethernet port no.2 is for future use).

2 LAN ports 4 ISDN PRI ports 1 RS232 port

4 Fans Power connector + Power switch


D12925 Rev. 03 8

4.1.1 Mixed ISDN and IP Conferences The MCU allows for using both ISDN and IP networks in same conference. In addition, telephone sites (IP or ISDN) can also be included in the same conference. The maximum IP, ISDN and mixed mode capacity is described in chapter 4.1.7. All conferences may use the normal features of TANDBERG products such as Duo Video, Encryption etc.

4.1.2 Multiple conferences The TANDBERG MCU may run three separate videoconferences at the same time. The meetings will be independent of each other as long as no resource restrictions apply (i.e. bandwidth/number of sites). Note: If the MCU is not registered to a Gatekeeper it is only possible to dial into conference number 1 (via H.323).

4.1.3 PRI E1/T1 ISDN

4.1.3.1 ISDN numbers The PRI lines connected to the MCU should have at least one number each, to allow dial in from ISDN. Number Range Start: If the PRI line has a range of numbers, the start number should be entered in the Number Range Start field. The number range must be inclusive. All numbers in the range may be used by the MCU for callback numbers, so the local ISDN switch must route all of these numbers to the configured PRI. It is only necessary to enter the digits indicating the range. If the range is 67828669 to 67828699, then just enter 8669. Maximum amount of digits is 24. Number Range Stop: The last number in the PRI number range is entered in the Number Range Stop. If the range is 67828669 to 67828699, then just enter 8699. PRI Trunk Grouping: When Trunk Grouping is enabled, PRI 2, 3 and 4 will use the same number range as specified for PRI 1.


D12925 Rev. 03 9

4.1.3.2 PRI E1/T1 ISDN The PRI interface may require an external CSU depending on the network layout. ‘Cable Length’ in the PRI set-up menu specifies the distance from the MCU to the CSU or last repeater. A CSU should not be required if the system is within 200 m (655 ft) of the last repeater depending on the PRI cable quality. The TANDBERG MCU supports the PRI protocols AT&T Custom, National ISDN and ETSI (Euro ISDN). The AT&T and National protocols will give a total of (23*4) = 92 channels while the ETSI protocol will give a total of (30*4) = 120 channels. Within these protocols the following switches are supported: Switches Protocols supported

4ESS (AT&T) AT&T Custom 5ESS (AT&T) AT&T Custom and National ISDN3 DMS250 (Nortel) National ISDN DMS100 (Nortel) National ISDN (Any switch) ETSI (Euro ISDN)

Channel hunting is provided for outgoing calls. The feature is normally used when the number of channels needs to be specified. When no value is specified for low or high channel, they default to 1 (low), 23 (high US) and 30 (high Europe). Default search is from high to low. Pinout of PRI E1/T1 Interface:4 NOTE: TANDBERG recommends always using category 5 cabling.

3 Dependent on the configuration of the switch 4 The cable of use should be a straight through configuration.

PRI Pinout 1 TIP RX 2 RING RX 4 RING TX 5 TIP TX


D12925 Rev. 03 10

PRI T1 (US only): Network Service Facility (NSF) can be configured as blank/no value (i.e. NSF not used – default) or any value between 0 and 31, to describe the service facility on the PRI/T1 line. AT&T Service code (ref.1)

Service

0 Disable 1 SDN (Including GSDN) 2 Toll Free Megacom (800) 3 Megacom 6 ACCUNET Switched Digital Service (incl. Switched Digital International) 7 Long Distance Service (incl. AT&T World Connect) 8 International Toll Free Service (1800) 16 AT&T MultiQuest 23 Call Redirection Service Sprint Service code (ref.2)

Service

MCI Service code (ref.2)

Service

0 Reserved 1 VNET/Vision 1 Private 2 800 2 Inwatts 3 PRISM1, PRISMII, WATS 3 Outwatts 4 900 4 FX 5 DAL 5 TieTrunk Ref. 1: AT&T TR 41459 Specification, June 1999, page 76 Ref. 2: Ascend Multiband Plus-T1/PRI, User Documentation, Page 6-8


D12925 Rev. 03 11

4.1.4 Ethernet / LAN Interface (H.323) The TANDBERG MCU have two RJ-45 jacks5 for the Ethernet interface (manual or automatic detection of 10/100Mb) and supports call rates from 56 kbps up to 2 Mbps. The ITU-T standard H.323 v4 protocol is implemented in the TANDBERG MCU. The following features are specifically relevant for this network interface:

4.1.4.1 Quality of Service features (QoS)

4.1.4.1.1 IP precedence IP precedence is a classification of packets from 0 (low priority) to 7 (high priority). The values 6 and 7 are typically reserved for congestion control. IP precedence helps a router select what kind of traffic to prioritise. By means of queue mechanisms, it can select which packets to send first and which to throw away. Some information/traffic is time critical while other is not, and classification is used to differentiate this traffic. One may set separate IP precedence for Signalling, Audio, Video and Data (values 1 – 7) as well as turn IP precedence off. The auto setting uses the following values for IP precedence:

Signalling=6 Audio/Video=4 Data=3 (e.g. FECC commands)

This means that in auto, IP precedence has the value 6 (i.e. signalling value) while both audio and video value is 4; data value is 3. Setting the IP precedence value in system’s menu is actually setting the signalling value. The audio/video and data values are changed accordingly in respect to the signalling value (i.e. audio/video value = - 2; data value = - 3).

4.1.4.1.2 Diffserv

Diffserv is an extension of IP precedence, where one can set values from 0 to 63 (63=Highest priority).

5 Ethernet port no.2 is not used in software version D3.


D12925 Rev. 03 12

4.1.4.1.3 IP type of service (TOS) TOS helps a router select a routing path when multiple paths are available. Delay- tells router to minimize delay Throughput- tells router to maximize throughput Reliability- tells router to maximize reliability Cost- tells router to minimized cost Off- Turns TOS off

4.1.4.1.4 Resource-Reservation Protocol (RSVP)

RSVP is a protocol that allows the TANDBERG MCU to request the network to reserve the bandwidth needed for the IP meeting.

4.1.4.2 Automatic selection of H.323 or H.320 outgoing calls

• IP address or E.164 number dialling. • Automatic selection based on network address type or predefined prefixes.

4.1.4.3 IP adaptive bandwidth management • The MCU never produces more traffic than needed, for better utilization of network

resources. Most of the data sent in a videoconference is video data. Thus, by incorporating smart video algorithms, the codec sends no more video data than necessary. Little movement in the picture gives low bit rate; while a lot of movement gives higher bit rate.

• The MCU regulates outgoing and incoming media bit rates by means of flow control signalling.

An example of this is automatic adjustment of total bandwidth used when DuoVideo is opened.

4.1.4.4 Dynamic playout buffering

Shapes the incoming data for better playout and re-sequencing of packet delivered out of order. This ensures better lip sync.

4.1.4.5 Asymmetrical media capabilities

Audio and video protocols can be fully asymmetrical. E.g., the TANDBERG MCU can send H.263 and receive H.261 at the same time.


D12925 Rev. 03 13

4.1.4.6 Diagnostic tools for IP

Q.931 To show Q.931 trace during a conference you need to issue the command syslog on. One can get traces for RAS, Q.931 and H.245 with this command. It is a complex trace and requires an extensive knowledge in H.323 signalling to be understood.

Ping Ping is used to see if the MCU is able to reach a specific IP-address, using a mechanism in IP called ICMP. If the MCU is unable to register to its gatekeeper, or if it is unable to dial a specific endpoint, one can use ping to see if there is at least an IP-route to the gatekeeper or to the endpoint. In case you have problems, one would first ping the default gateway, then the gatekeeper, and then the other endpoint.

Traceroute Traceroute does exactly that; it traces the route an IP-packet takes to reach its destination and displays all router hops. Traceroute is very useful for seeing exactly where there is a routing-problem in the IP-network, and for checking where transport-delay is introduced.

4.1.4.7 Latency & Jitter Latency is defined as the time between a node sending a message and receipt of the message by another node. The TANDBERG MCU can handle any value of latency- however, the higher the latency, the longer the delay in video and audio. This may lead to conferences with undesirable delays causing participants to interrupt and speak over each other. Jitter is defined as the difference in latency. Where constant latency simply produces delays in audio and video, jitter can have a more adverse effect. Jitter causes packets to arrive out of order or at the wrong times, which again leads to packet loss. TANDBERG MCU can manage packets with jitter up to 100ms. If excessive packet loss is detected, the TANDBERG MCU will downspeed the connection until acceptable packet loss is achieved.

4.1.4.8 Layer 4 Ports used in H.323 meetings The following tables describes what layer 4 ports are being used by the system when call is made on an H.323 network.

MCU meetings + Duo Video Function Port Type Gatekeeper Discovery (RAS) 1719 UDP Q.931 Call Setup Range 5555—5587 TCP H.245* Range 5555—5587 TCP Video Range 2326—2837 UDP Audio Range 2326—2837 UDP Data/FECC Range 2326—2837 UDP


D12925 Rev. 03 14

4.1.4.9 IP packet sizes

Audio The system automatically selects the most favorable IP packet size for audio. Depending on the network conditions, the system will send 20 ms or 40 ms of audio in each packet, thus:

• G.711 – 160/320 bytes per packet • G.728 – 40/80 bytes per packet • G.722 – 160/320 bytes per packet • G.722.1 (24 kbps) – 60/120 bytes per packet • G.722.1 (32 kbps) – 80/160 bytes per packet

Video The TANDBERG MCU is sending maximum 1450 bytes of video per packet. Note: In addition, the system needs to add the following header information for each of the audio and video packets above: 20 bytes IP-header, 8 bytes UDP-header and 12 bytes RTP-header (i.e. 40 bytes in total). Packet loss: Packet loss is displayed in the conference overview of the MCU. The number shown is the average of audio- and video- packets that are lost during the last 2 seconds.

4.1.4.10 Intelligent Packet Loss Recovery (IPLR)

IPLR is an ITU standard based packet loss compensation for H.323 that improves received video into the TANDBERG MCU. IPLR supports all video protocols and resolutions that TANDBERG MCU already has implemented and is compatible with all terminals and Gateways. IPLR is a special algorithm developed at TANDBERG that will make efforts to reconstruct the lost packets and reduce the visual effects caused by packet losses. • If the MCU experiences packet loss from an endpoint, it will ask the endpoint to handle

packet loss. This requires Intelligent Packet Loss Recovery functionality on the endpoint. • If an endpoint experiences packet loss from the MCU, the MCU encoder will not start

IPLR since this would affect the received video quality for all other endpoints.


D12925 Rev. 03 15

4.1.5 LEDs Description The TANDBERG MCU has 24 LEDs (Light Emitting Diodes) on the front panel, each giving various information as shown below.

4.1.5.1 Description of PRI Alarms A PRI cable consists of four wires (2 pairs of wires): One pair for Transmit (TX) and one pair for Receive (RX) signals. Red Alarm Red alarm or Loss of signal (LOS) means that there is no signal and thus no framing info received. (This has same effect as pulling out the PRI cable). Yellow Alarm Yellow alarm or Remote Alarm Indicator (RAI) means that the MCU is receiving framing info, but in this framing info the other side tells the MCU that it is not reading the MCU’s transmitted framing info. Typically, this may be a broken connector in the TX part of the MCU PRI cable. This could also indicate weak or noisy signal in the TX part of the MCU PRI cable.


D12925 Rev. 03 16

Blue Alarm Blue alarm means that network on the far side of the CSU is unavailable. Scenario: TANDBERG MCU is connected via a CSU (i.e. a NT ‘Network Termination’) as follows:

MCU–cable A–CSU–cable B–Network If a CSU loses framing/sync from the network (example: a bad cable B), it shall no longer send valid framing out on cable A towards the MCU. Instead it transmits "Blue Alarm". Seen from the MCU receiving blue alarm, this means that the network on the far side of the CSU is unavailable.

4.1.6 Intelligent Call Management (ICM) By using TANDBERG's inbuilt Intelligent Call Management (ICM), MCU conferences can be made from data rates of 56 kbps up to 2 Mbps via ISDN networks. ICM is a highly sophisticated feature provided by the TANDBERG MCU that e.g. makes the connection between two sites more reliable and safe. If the ISDN network drops channels during a meeting, the conference will not shut down but adjust to the remaining number of available channels6. This ability is called ‘Downspeeding’ and is in accordance to the BONDING Mode 1 standard. Downspeeding will take place in the following situations: a) When sites are entering the conference with a lower bandwidth than what is defined in that particular conference’s set-up.

In this case, the MCU will receive different call rates from the connected sites, but will transmit the call rate of the site with lowest call rate capabilities.

b) When a site is loosing a channel.

In this case the MCU will still receive different call rates from the connected sites, but will transmit the call rate of the site with lowest call rate capabilities. If the site loosing a channel is disconnected, the MCU will automatically send out the call rate initially set up for that conference.

6 If one of the connected sites does not support downspeeding, this site will drop out of the call and this call needs to be set up again.


D12925 Rev. 03 17

4.1.7 MCU Capacity The total capacity of the MCU is defined by the following three rules. RULES:

I. Software version defines maximum number of sites: 8+8 -> Maximum 8 video sites and maximum 8 telephones 16+16 -> Maximum 16 video sites and maximum 16 telephones

II. Total system bandwidth of the MCU is 7680 kbps (IP and ISDN) regardless of software version. The maximum bandwidth used for ISDN calls is depending on the number and type of PRI's installed:

a) The maximum bandwidth for ISDN E1 is 7680 kbps (120x64 kbps, if all 4

PRI's are installed).

b) The maximum bandwidth for ISDN T1 is 5888 kbps (92x64 kbps, if all 4 PRI's are installed).

III. In addition, each call has a Call Weight depending on bandwidth and encryption as follows:

Video sites: Bandwidth 64 128 192 256 320 384 512 768 1152 1472 1920Non-encr. 37 40 41 42 44 46 54 62 80 88 110 Encrypted 53 59 60 61 68 73 84 111 N/A N/A N/A Telephone sites: Bandwidth Telephone Non-encr. 11 Encrypted N/A

The sum of the Call Weights cannot exceed 845. (Users will be prevented from setting up calls that exceeds this limit). Example of call weight calculation: If the MCU has made 6 calls at 768 kbps, 4 calls at 384 kbps, and 4 encrypted calls at 192 kbps the calculation will be: 6x62 + 4x46 + 4x60 = 796. Since 796 is less than 845, this will be OK.


D12925 Rev. 03 18

4.1.7.1 MCU Capacity – typical scenarios

In the table below some typical capacity scenarios are listed (they can be derived by the calculation above): Bandwidth Non-encrypted

(Max. no. of video sites + telephone sites) IP & E1

Non-encrypted (Max. no. of video sites + telephone sites) T1 only

Encrypted (Max. no. of video sites)

128 kbps 16 + 16 16 + 16 14 256 kbps 16 + 15 16 + 15 13 384 kbps 16 + 9 15 + 2** 11 512 kbps 15 + 0* 11 + 4** 10 768 kbps 10 + 0* 7 + 8** 7 1472 kbps (1.5Mbps)

5 + 5 4 + 0** N/A

1920 kbps (2Mbps) 4 + 0* 3 + 2** N/A *) Limited by the maximum capacity 7680 kbps, see rule II a) above. **) Limited by the maximum capacity 5888 kbps, see rule II b) above

4.1.8 Dial Profiles The TANDBERG MCU can be programmed to use different Dial Profiles. Dial Profile consists of a name and a prefix. Example: If 0 (zero) is needed to call outside a location, create a prefix called ‘external’ with prefix set to 0. Also, to differentiate between ISDN numbers/E.164 Alias the ‘Dial Profiles’ shall be extended to support selection of ‘ISDN’ & ‘H.323’.


D12925 Rev. 03 19

4.1.9 Secure Conference (Encryption) The TANDBERG MCU has built-in encryption of audio, video and data for both H.323 meetings (based on ITU standard H.235) and H.320 (based on ITU standard H.233 and H.234) meetings. The administrator decides- when setting up the conference- whether or not a conference shall be in encrypted mode or in unencrypted mode. It is not possible to change the mode after the conference is set up. The encryption algorithms used in the TANDBERG system are: - The Data Encryption Standard (DES) with a 56 bits session key - The Advanced Encryption Standard (AES) with a 128 bits session key Although there are small differences between H.323 and H.320, a typical set-up of a secure call can be defined as follow: 1. Establishment of a common shared secret and selection of an encryption algorithm. 2. Exchange of the keys according to the common shared secret and the selected encryption

algorithm. 3. Start the encryption. The establishment of the common shared secret is done through the computation of the Diffie-Hellman (DH) algorithm. The DH method uses primes numbers of 512 bits length for DES and 1024 bits for AES. The shared secret is then used as a key for the selected encryption algorithm which encrypts "the session keys". When the session is collected by the remote end, encryption of the audio, video and data channels can start. The encryption will be established automatically when all endpoints in the conference supports encryption with automatic key generation (and the conference is set up for encryption mode of operation). Encryption is supported for meetings up to 768 kbps and the TANDBERG feature DuoVideo. Note: For an encrypted conference, all endpoints must support encryption (AES or DES). - If encryption mode is set to Auto, the MCU accepts both AES and DES encryption. - The MCU administrator can also force the MCU to require only e.g. AES encryption. In this case, all participants must have AES in order to join the conference. If a site entering an encrypted conference does not support encryption, a picture will be shown, informing that the conference requires encryption. If a site connected to an encrypted conference start sending unencrypted data, that site will be taken out of the conference.


D12925 Rev. 03 20

4.1.9.1 Number of encrypted sites (software option 16+16)

Bandwidth video sites (in kbit/s) 128 256 384 512 768

Number of encrypted sites 14 13 11 10 7 The above table shows the maximum number of sites and at what meeting bandwidth, a conference can be encrypted with MCU 16+16 software option.

4.1.9.2 Number of encrypted sites (software option 8+8)

Bandwidth video sites (in kbit/s) 128 192 256 320 384 512 768

Number of encrypted sites 8 8 8 8 8 8 7 The above table shows the maximum number of sites and at what bandwidth, a conference can be encrypted with MCU software option 8+8.

4.1.10 MCU control (H.231/H.243) For controlling the TANDBERG MCU conference the following options are implemented:

• H.243 MCV Take Floor This feature is used by any of the connected sites. I.e. any site may Request floor to broadcast their video to all sites, and Release floor to go out of broadcast mode (applicable for both ISDN and IP meetings).

• Assigning Floor This feature is used by the administrator of the MCU. I.e. The administrator may decide which site’s video shall be broadcasted to all participants.

Terminal Site naming: The TANDBERG MCU also supports site naming (on ISDN and IP).

Thus, if the connected sites also support site naming, a transparent line of the broadcaster’s site name will be displayed (for approx. 10 seconds) on all other sites every time the TANDBERG MCU switches broadcasting site. To view the sites connected to the conference, the quick keys may be used on the EPs remote control.


D12925 Rev. 03 21

4.1.10.1 H.243 Password H.243 password (TCS-1) is supported by the system when using ISDN as network for the conferences. This feature allows you to have a meeting password set in the MCU. In that case, all endpoints must give this password to the MCU to join the conference. The password must be numerical. There are three ways of entering this MCU password: 1) Password entered together with the MCU number E.g. with MCU number=207987654 and password=1234, the number to dial by the endpoints will be 207987654*1234. 2) Password prompted after the MCU is called (sound or picture prompt) In this case, the TANDBERG MCU sends a TCS-1 message to the terminal right after the terminal has called the MCU. When the endpoint (telephone or video) receives this message, it will prompt the user for the password (sound or picture prompt). 3) Password prompted after the MCU is called (DTMF tones) The endpoints may also insert the password via their remote control (DTMF) to get access to the MCU. Note: Using DTMF tones is the only way to enter a protected meeting from a site connecting on IP network. If password is correct, the MCU will join the system to the conference; if not correct the system will not be connected.


D12925 Rev. 03 22

4.2 Aggregation Standards ISDN Aggregation H.221 Frame Structure from 64 (56*) kbps to 128 kbps ISO 13871 BONDING, Mode 1 from 64 (56*) kbps to 2 Mbps H0 One 384 kbps channel

4.2.1 BONDING • ISO 13871, BONDING Mode 1 for bit rates from 56 kbps up to 2 Mbps (1 to 30 channels). • The maximum relative delay difference between B-channels is 0.5 second (i.e. to compensate

for different routing of channels). The following are the standard bandwidths on H.320:

30ch – 24 – 23 – 18 – 12 – 8 – 6 – 5 – 4 – 3 – 2 – 1 4.2.1.1 ISDN channel set-up The following is a description of how the ISDN channels are set up. Incoming & Outgoing MCU calls: Normally the MCU will set up only 1 channel from PRI 1 and build up the channels starting from the 'bottom' of the last PRI in use. This will ensure that the MCU always have available channels on the first PRI number (which normally should be the MCUs main number). The TANDBERG MCU supports simultaneous dial in to the same conference on ISDN.

4.2.2 H.221 • For bit rates from 56 kbps up to 128 kbps (1 or 2 channels). • The maximum relative delay difference between the 2 B-channels is 0.6 second.

4.2.3 H0 H0 is an ITU defined 384 kbps service available for ISDN PRI. The TANDBERG MCU supports H0 that is defined as a group of 6 ISDN channels multiplexed to provide one 384 kbps channel. H0 may have a shorter connection time, since there is only one channel to set up. This service is sometimes called Switched 384 or ISDN H0.


D12925 Rev. 03 23

4.3 RS232 Interface/Application Programmable Interface (API) Data Standards Data TANDBERG Dynamic Data Channel (DDC) Modem Standard modem commands Data Interfaces 1 x Data port, RS-232 (9-pin D-sub), Up to 115200 Baud for Data & Control

The RS232 port on the TANDBERG MCU is implemented as Digital Circuit Terminating Equipment (DCE). The connectors used are female 9-pin D-subs and the pin-out is shown in table below.

Signal Name Direction Pin number Carrier detect, CD From DCE 1 Receive data, RXD From DCE 2 Transmit data, TXD To DCE 3 Data terminal ready, DTR From DCE 4 Signal ground, GND 5 Data set ready, DSR From DCE 6 Ready to send, RTS To DCE 7 Clear to send, CTS From DCE 8 Ring indicator, RI From DCE 9

Note: The API commands may also be accessed via Telnet, through the MCU’s Ethernet connection.

4.3.1 API commands Please refer to the document ‘TANDBERG MCU API’ (D12930) for details. The RS232 port is used for local software upgrades, local control and diagnostics. Also, refer to ‘TANDBERG SNMP’ (D12190) for SNMP implementation.


D12925 Rev. 03 24

4.4 Video Features The TANDBERG MCU supports the ITU video standards H.261, H.263, H.263+ and H.264.

4.4.1 Optimised Video Compression

4.4.1.1 The ITU standard H.263 provides • Optimised compression and decompression of video at lower bandwidths. • A sharper picture than provided by H.261. • Improved contrast and enhanced clarity of the finer details within an image. • Improved motion handling that removes the characteristic blocking that tends to occur during

normal H.261 movement. • 4xCIF/4xSIF live video

4.4.1.2 The ITU standard H.264 Provides considerably better video quality at lower bandwidths. It has been developed with strong TANDBERG participation in joint workgroups of ITU-T and ISO. H.264 is based on the ISO standard MPEG-4. The TANDBERG MCU supports H.264 video compression in both CIF and SIF resolutions. An encoding and decoding rate of a high-quality 30 frames per second is achieved. H.264 may be used on the TANDBERG MCU for endpoint bandwidth of up to 768 kbps. NOTE: The TANDBERG MCU will automatically switch to H.263 in the following conditions:

• In case H.264 is unavailable for one of the connected systems, the TANDBERG MCU will select H.263 for the whole conference.

• If more than one conference is ongoing on the MCU • If other layouts than Voice Switched or CP4 is used • If Duo Video feature is used


D12925 Rev. 03 25

4.4.2 Video Formats The TANDBERG MCU supports the following video formats:

Native NTSC: • SIF, Source Input Format (352 x 240 pixels) • 4SIF (704 x 480 pixels) Native PAL: • CIF, Common Intermediate Format (352 x 288 pixels) • 4CIF (704 x 576 pixels) • QCIF, Quarter CIF (176 x 144 pixels) Native PC: • VGA, Video Graphics Array (640 x 480 pixels) • SVGA, Super VGA (800 x 600 pixels) • XGA, eXtended VGA (1024 x 768 pixels)

4.4.3 Asymmetric Video Formats The TANDBERG MCU can send and receive asymmetric video formats. This means any combination of the supported custom video formats may be sent/received to/from the MCU. Changes in the video formats during the conference are done automatically either when one of the sites changes its transmitting video format or if these formats are changed from the MCU itself.

4.4.4 Best Impression Best Impression is a TANDBERG feature that allows the MCU to automatically select the best impression for the user- without any user intervention. It will automatically select the optimal layout for the optimal resolution. Best Impression consists of three main parts:

• Dynamic/Auto Layout switching in CP mode This means the MCU will automatically switch to next layout (as described below) when connecting more participants in the meeting.

• Automatic resolution switching in CP mode • Video Transcoding

4.4.4.1 Dynamic/Auto Layout switching The MCU may transmit a variety of picture modes:

• Full screen picture - when Voice Switched mode is selected Current speaker is transmitted in full screen to all other participants. (The current speaker will see the previous speaker).


D12925 Rev. 03 26

• CP 4 - when Continuous Presence 4 mode is selected

The picture transmitted to all sites is divided into four (same size) sub-pictures. If there are more than four video sites in the conference, the last four speakers will be shown. If there are less than four video sites, the ‘empty’ sub picture(s) will be black.

• CP 9 - when Continuous Presence 9 mode is selected The picture transmitted to all sites is divided into nine (same size) sub-pictures. If there are more than nine video sites in the conference, the last nine speakers will be shown. If there are less than nine video sites, the ‘empty’ sub picture(s) will be black.

• CP 16 - when Continuous Presence 16 mode is selected The picture transmitted to all sites is divided into sixteen (same size) sub-pictures. If there are less than sixteen video sites, the ‘empty’ sub picture(s) will be black.

• CP 5+1 The transmitted picture will show one large picture of the current speaker and 5 small sub-pictures. If more than 6 participants, only the last speaking sites will be shown.

• CP 7+1

The transmitted picture will show one large picture of the current speaker and 7 small sub-pictures. If more than 8 participants, only the last speaking sites will be shown.

Note for CP5+1 and CP7+1: When floor to full screen is selected in the conference settings, whoever is requesting the floor will be shown in full screen view. When floor to full screen is not selected, whoever is speaking or requesting the floor will be shown in the one large CP picture. • Traditional CP mode

When picture mode is set to Traditional CP mode the following table describes the picture sent from the MCU: Number of video sites in conference

Picture mode used (When conference set to Traditional CP mode)

1 or 2 Full Screen 3 or 4 CP4 5 -> 9 CP9 > 9 CP16


D12925 Rev. 03 27

• Enhanced CP mode When picture mode is set to (or Enhanced CP mode) the following table describes the picture sent from the MCU: Number of video sites in conference

Picture mode used (When conference set to Enhanced CP)

1 or 2 Full Screen 3 -> 6 5+1 > 6 7+1

• The TANDBERG MCU allows for changing between any of these modes during the

conference. • Auto mode is defined to select Enhanced CP mode

4.4.4.2 Automatic Resolution switching Voice Switched Mode: In Voice Switched mode or when someone has the floor the MCU will send the same format as the one received if all the sites are capable of receiving it. If one of the sites cannot receive the preferred video format (or if a site asks for a video format not supported by MCU), the MCU will fallback according to the following table: Preferred Video Format Fall back Video Format XGA SVGA SVGA VGA VGA 4CIF 4SIF 4CIF 4CIF H.263 CIF ICIF H.263 CIF H.263 SIF H.263 CIF H.263 CIF H.261 CIF H.261 CIF H.263 QCIF H.263 QCIF H.261 QCIF


D12925 Rev. 03 28

Continuous Presence Mode (CP): In Continuous Presence mode the MCU administrator may set the conference up for Motion, Sharpness or Auto: MCU Video Format modes

CP mode Meeting Rate MCU will transmit the highest possible common Video Format according to:

MOTION Any Any H.263 CIF -> H.261 CIF -> H.263 QCIF -> H.261 QCIF

SHARPNESS Any Any H.263 4CIF -> H.263 CIF -> H.261 CIF -> H.263 QCIF -> H.261 QCIF

AUTO CP4 Any Same formats as for MOTION AUTO CP9/CP16 < 256 kpbs Same formats as for MOTION AUTO CP9/CP16 ≥ 256 kbps Same formats as for SHARPNESS Duo Video: Duo Video may be sent in both CP and Voice switched mode (ref. Ch.4.4.5). The MCU will transmit the same format as the one received if all the sites are capable of receiving it. The Video Format will fallback as described above (for Voice Switched mode).

4.4.4.3 Video Transcoding The TANDBERG MCU supports video transcoding of two bandwidths. The two bandwidths are not fixed, thus the MCU will define the two bandwidths according to highest ‘standard’ and lowest ‘low’ bandwidth when the conference is set up.

Example: If all participants are connected on 384 kbps and another participant joins the meeting at 128 kbps, the video rate of the 384 kbps participants will still be 384 kbps. The new participant will receive video at 128 kbps7. • Endpoints connected on lower rates than the standard rate, will receive video encoded at

the lower rate. But, if an endpoint is connected on <64 kbps below the standard rate, the highest video rate will be decreased to that rate.

Note: When Duo Video is used, all connected sites will receive the lowest video rate.

7 If Duo Video is active video transcoding is disabled and all sites receive the lowest common video rate.


D12925 Rev. 03 29

4.4.5 Duo Video The TANDBERG MCU is capable of receiving/transmitting two simultaneous H.320 video signals from/to all sites8. When one of the sites requests for Duo Video, the MCU will open Duo Video towards all the other video sites capable of receiving it. Now, if another site requests for Duo Video the MCU will automatically transmit this new site’s Duo Video the the rest of the sites. The MCU uses High Speed Data rates (HSD) for Duo Video. If any of the sites do not support HSD, Duo Video will still be transmitted to the sites capable of receiving this. The sites not supporting HSD will in that case receive the same video stream as the others see on their main video (and therefore not use all of their available meeting rate). Duo Video is available in both Continuous Presence mode (CP) and Voice Switched mode or when one site has the floor, regardless of which site is broadcasted on the main stream. The Video format of Duo Video is described in Ch.4.4.2. Automatic bandwidth adjustment When DuoVideo is sent to the sites, the MCU will automatically downspeed and use approximately 1/2 of the original bandwidth for Duo Video. When Duo Video is not transmitted, the MCU will automatically upspeed to its original bandwidth.

4.4.5.1 Duo Video Interoperability with other vendors The TANDBERG MCU is compatible with the Polycom feature ‘People & Contents’. The TANDBERG MCU can receive Duo Video (from a TANDBERG endpoint) and transmit it as People & Content to PolyCom iPower9 (on H.320). Note: This feature must be enabled in the MCU configuration (Web page or via Telnet) to work with the iPower. There is also a setting for enabling People & content on the iPower system.

8 Depending on the connected sites ability to transmit/receive Duo Video. 9 This features is tested with: Polycom iPower 680, 970 with software version 4.0.6.909 & Polycom MGC (MCU) with software version 4.01.448


D12925 Rev. 03 30

4.4.6 Custom pictures The TANDBERG MCU has a variety of pictures that may be changed by storing new files on the FTP file system of the MCU. Please, see ch.5.3 for details on file sizes.

Welcome picture The welcome image is shown when new participants enter the conference. (It is possible to disable this feature when setting up a conference). Password Enquiry picture This is an image asking the site(s) to enter password. Password Reject picture This is an image shown if wrong password is entered by the site. Encryption Required picture This image is shown to a site that does not support encryption (sent only if conference is encrypted).


D12925 Rev. 03 31

4.5 Audio Features

4.5.1 Audio levelling/ Automatic Gain Control (AGC) The TANDBERG MCU’s Automatic audio levelling feature Automatic Gain Control (AGC) will ensure that the audio sent out to all sites in the conference is at the same level.

4.5.2 Telephone Noise Suppression Connecting normal mobile telephones to a conference, normally introduces noticeable noise. To filter out this type of noise, the TANDBERG MCU has a special noise suppression algorithm implemented.

4.5.3 Custom Sounds The TANDBERG MCU has a variety of sounds that may be changed by storing new files on the FTP file system of the MCU. Ref. Ch.5 for details. 4.5.3.1.1 Welcome sound When endpoints are entering a conference, they will be greeted with a default welcome sound. It is possible to customize this welcome sound by storing a WAV-file in the system. (It is possible to disable this feature when setting up a conference). 4.5.3.1.2 Password sound When endpoints are entering a conference that is password protected, they will be asked to insert their password. It is possible to customize this password sound by storing a WAV-file in the system.

4.5.4 Entry/Exit tones The MCU will give clear sound indication to endpoints entering and exiting the conference. When a site is entering the conference, all participants will hear the entry tone. When a site is exiting the conference, all sites still in the conference will hear the exit tone. (It is possible to disable this feature when setting up a conference).

4.5.5 Muting of audio The MCU administrator is able to mute the audio from any of the connected sites during a conference. It is also possible for each site to mute its microphone. Clear indication that the microphone is muted will be shown on the screen of the relevant site as well as on the MCU web administator page.


D12925 Rev. 03 32

4.5.6 Telephony The MCU may be used as a telephone bridge only, supporting up to 16 telephone endpoints in the same conference. See also Ch. 4.1.7 for possible connected telephone sites in a conference. IP telephones: It is possible to use the TANDBERG MCU with IP telephones (G.711 audio algorithm).

4.5.7 Allow G.728 The MCU supports high quality audio even on low call rate. On low call rate the MCU will prioritize G.722.1. Video participants not supporting this, will receive low quality audio G.728 instead, when ‘Allow G.728’ is selected. To ensure high quality audio on low call rate, unselect ‘Allow G.728’ and video participants not able to support G.722.1, will receive G.722 instead.

4.5.8 Audio Compression Algorithms The following audio algorithms are supported on the TANDBERG MCU: • G.711 48/56/64 kbps, 3.1 kHz bandwidth. • G.728 16 kbps, 3.1 kHz bandwidth. • G.722 48/56/64 kbps, 7 kHz bandwidth. • G.722.1 24 kbps or 32 kbps, 7 kHz bandwidth.

The MCU is able to receive any of these algorithms from each of the sites. The connected sites may use different algorithms and the MCU is automatically selecting algorithms to send to the various sites depending on the site’s capabilities.

If 16 video sites and 16 audio sites are talking at the same time, the audio from all sites will be processed together. This means all the site’s audio (32-1=31) will be heard locally.


D12925 Rev. 03 33

4.6 System Management TANDBERG provides a comprehensive set of management tools, and is committed to the use of standards-based tools. The TANDBERG MCU can be managed in many ways: � The internal web server allows for remote control of the MCU using a web interface

from anywhere on the LAN/WAN/Internet (open browser http://MCU-ipaddress) � The Application Program Interface (API) allows for connecting a computer directly to

the system via the RS232 port or from anywhere on the LAN/WAN/Internet via Telnet or FTP.

� The TANDBERG Management Suite (TMS) may also be used to manage the system and the TANDBERG Scheduler may be used to schedule conference meetings (Optional).

4.6.1 Ethernet/LAN Interface There are two Ethernet/LAN interfaces on the TANDBERG MCU, of which only one is currently in use. The LAN interface supported on the TANDBERG MCU is 10base-T and 100base-T compatible, and is used for H.323 conferences as well as management features of the MCU, such as connecting to the internal web-server, Telnet and FTP-server. The system supports the following settings of this interface:

• Auto The MCU will auto-detect the speed/duplex on the LAN • 10/Half The MCU will connect to the LAN using 10Mbps speed/Half Duplex • 10/Full 10 Mbps speed/Full Duplex • 100/Half 100 Mbps speed/Half Duplex • 100/Full 100 Mbps speed/Full Duplex

‘DHCP’ (Dynamic Host Configuration Protocol) can be selected when a DHCP server is present. When using DHCP, IP-address and IP-subnet mask and IP gateway are not used since the DHCP server assigns these parameters. If ‘Static’ is selected, the system’s IP-address and IP-subnet mask must be specified in the IP configuration menu.

4.6.2 Platform Requirements The management tools are based on standard protocols, obviating the need for special programs running on the management computer. The management computer may be any computer running a standard operating system. I.e. the management computer may be a Personal Computer running the Windows 95/98/2000/NT operating system, which includes the necessary programs such as:


D12925 Rev. 03 34

• An FTP client (please see ‘Upgrading software in TANDBERG Videoconferencing units’- document D10238- for details)

• A web-browser (please see ‘TANDBERG MCU User Manual’- document D12911- for details)

• A Telnet client (please see ‘TANDBERG MCU API’- document D12930- for details) • A terminal emulator for the RS232 port (please see ‘TANDBERG MCU API’- for

details)

4.6.3 Protocols Supported TCP/IP - Transport Control Protocol/Internet Protocol, providing connectivity over

LAN/WAN to any networked computer. HTTP - HyperText Transport Protocol, providing a Web-browser interface to the

management computer. (‘Max. number of simultaneous connections’ = unlimited, although only one is processed at a time)

FTP - File Transfer Protocol, providing access to the ‘FTP file system’ of the MCU. (‘Max. number of simultaneous connections’ = 1) TELNET - providing a standard command-line interface to management functions. (‘Max.

number of simultaneous connections’ = 8) SNMP10 - Simple Network Management Protocol, standard for network management and

surveillance. (RFC1157 SNMPv1, RFC 1213 MIB-II). DHCP - Dynamic Host Configuration Protocol, enabling the system to automatically be

given IP address and Subnet Mask when connected to a network with a DHCP server.

In addition to the above, TCP/IP based protocols allowing management to be performed remotely; local management, control and software upgrade facilities are also available through a standard RS232 interface.

4.6.4 System Management Functionality

4.6.4.1 Remote software upgrades using FTP: This service is provided by the standard TCP/IP based FTP protocol. Any networked PC may perform software upgrades either locally or over the Internet depending on the LAN connectivity on the customer premises (firewalls etc.). By using any FTP-client software (such as the FTP-client bundled with the Windows operating system), it is possible to upload the new software release to the MCU. The software file is in binary format in order to decrease upload time. All settings of the MCU will be restored after a software upgrade.

4.6.4.2 Management using a standard Web-browser: The web-browser is the most common way to manage the TANDBERG MCU giving access to all managing features of the MCU. Using a standard Web-browser (Netscape, MS Internet Explorer 3.0 or later), the user may perform all forms of meeting set-up and control, but also diagnostics, troubleshooting and software upgrade. 10 For further info on SNMP refer to document ‘TANDBERG SNMP’ (D12190)


D12925 Rev. 03 35

4.6.4.3 Management using a standard Telnet-client: (I.e. a Telnet program bundled with the Windows operating system) This gives the user the same functionality as from the web interface and the RS232 port. It provides advanced debug capabilities such as ISDN layer 3 (D-channel) traces on the Primary Rate interfaces, low-level H.320 protocol diagnostics (e.g. H.221 traces), etc. This interface is a command-line type interface, not a graphical interface like the Web-browser interface. The system supports multiple simultaneous Telnet sessions. See chapter 4.3 and document ‘TANDBERG MCU API’ (D12930) for details of API commands available via RS232/Telnet.

4.6.4.4 Management using a terminal connected to the RS232 port: (I.e. using the HyperTerminal program bundled with the Windows operating system). Provides the same services and features as the Telnet-interface does, but locally. See chapter 4.3 and the document ‘TANDBERG MCU API’ (D12930) for details of API commands available via RS232/Telnet.

4.6.5 Security

4.6.5.1 HTTPS, TLS/SSL The TANDBERG MCU supports HTTPS in order to ensure secure transmission of the information displayed on the administrator’s PC. I.e. a secure connection between any Web browser and the MCU (the MCU web server) will be established if the HTTPS service on the MCU is enabled. HTTPS allows for password exchange which is especially important.

• SSL Secure Sockets Layer, protocol developed by Netscape for transmitting private documents via the Internet. SSL works by using a private key to encrypt data that is transferred over the SSL connection.

• HTTPS

Web pages that require an SSL connection start with https: instead of http:.

• TLS - Transport Layer Security To enable HTTPS, use the API command services https on. The HTTPS server will then be activated at next restart. If the MCU’s HTTP service also is activated, the user will automatically be redirected to HTTPS. If HTTP is de-activated, you will have to specify HTTPS. (In the latter case https://10.0.5.203 will work, but not http://10.0.5.203).


D12925 Rev. 03 36

4.6.5.2 Disable Services There is no router inside the system that can route between the ISDN side and the IP side of the TANDBERG system. This means it is not possible to get access to the Ethernet port via an ISDN conference. However, if wanted the following services may be disabled/enabled (with API commands):

• TELNET • HTTP • HTTPS • FTP • H323 • SNMP (may also be set to read only)

4.6.5.3 Security Alert The system will notify any management application when someone tries remote access over IP with illegal password (via SNMP traps). Information about the intruder’s IP-address and the service used (Web, Telnet and FTP) will be given. When the (optional) TANDBERG Managemen Suite (TMS) is used, an email notification may also be sent e.g. to the administrator of the network.

4.6.5.4 Authentication of Remote Management System – (Telnet Challenge) In order to increase network security, the TANDBERG system can force remote management systems such as the TANDBERG Management Suite (TMS) to authenticate. Authentication is performed via an MD5 challenge using a configurable TELNET port (port 57 by default). In the course of authentication, the TANDBERG system provides a "challenge" such as a text string to the management system. The management system must then compute a response using the MD5 hash algorithm from this string and a secret password. The response is used as the management password. It changes every time because the challenge is different every time.


D12925 Rev. 03 37

4.6.6 Layer 4 ports used by the system The following TCP and UDP ports are relevant for the TANDBERG MCU system. Function Port Type Direction Gatekeeper RAS 1719 UDP ⇔ Gatekeeper Discovery 224.0.1.41:1718 UDP ⇔ Q.931 Call Setup 1720 TCP* ⇔ H.245/Q.931 Range 5555—5587 TCP ⇔ Video Range 2326—2837 UDP ⇔ Audio Range 2326—2837 UDP ⇔ Data/FECC Range 2326—2837 UDP ⇔ FTP (control) 21 TCP* ⇔ Telnet 23 TCP* ⇔ Telnet11 57 TCP ⇔ HTTP 80 TCP* ⇔ HTTPS 443 TCP ⇔ NTP 123 UDP* ⇐ (incoming to MCU) SNMP (Queries) 161 UDP* ⇔ SNMP (Traps) 962 UDP ⇒ (outgoing from MCU) Netlog 963 TCP ⇔ FTP (data) 1026 TCP ⇔ Outgoing H.323 call: First call uses 5555 for outgoing Q.931 and 5556 for H.245, next uses 5557 for Q.931 and 5558 for H.245, etc. Incoming H.323 call: First uses call uses 5555 for H.245, second 5556 etc. Disconnecting a site in a meeting will not free up available 55XX ports until the whole conference is down. (*) Listening sockets

11 Default port for MD5 challenge authentication mechanism, configurable


D12925 Rev. 03 38

5 Miscellaneous features 5.1 Distributed MCUs The TANDBERG MCU can be cascaded with other TANDBERG MCUs to increase the number of participants in one conference. By simply dialling from one MCU to other MCUs one will achieve a distributed setup. In this case the MCU dialling out will be defined as the master MCU and all other MCUs as slaves (up to 16 slave MCUs are possible to connect). With 16 slaves connected to one master MCU one may achieve 240 participants @384kbps in the same conference. The connection between the MCUs (or the Endpoints) may be ISDN or IP. NOTE: The slave MCUs will automatically be set to Voice Switched while the master MCU may be set to one of the CP layouts or kept in Voice Switched mode. A distributed MCU scenario may add delays to the switching of the conference. Features supported within a distributed MCU scenario:

• DuoVideo from any site • Encryption (as long as all sites support this feature) • Request Floor from any site • View Site naming (of any site in the conference)

Administrator features (on MCU or TMS): • View site names (terminal list) of all participants • Configure the conference as Master, Slave or Auto

o Auto – The MCU dialing out will become Master o Master/Slave status on Web

• Picture Mode disabled on Slave MCU • Assign Floor from Master MCU

o shows the site in full screen for all participants • Assign Floor from Slave MCU

o shows the site in full screen for all participants o Only to sites on this MCU


D12925 Rev. 03 39

5.2 Phone book The TANDBERG MCU can store up to 100 numbers in the phonebook. The phonebook may be edited through the web interface or by editing the dir.prm file, stored on file system of the MCU (FTP).

5.2.1 Group Entries For easy set-up of regular MCU meetings, the system has 16 Group entries. Each of the Group entries may store up to 32 singel entries. The numbers used for Group dialling must first be stored in the MCU phonebook.

5.3 Maximum meeting duration When defining a conference, it is possible to specify the maximum meeting time for the conference. The timer will start when the first site in the conference is connected. 10 minutes, 5 minutes and 1 minute before the conference is disconnected, a clock is shown on the screen, indicating number of minutes left until the conference is being disconnected. At the specified time, the conference is disconnected, but the conference is not ended (e.g. cleared). It is possible to change the max. meeting duration during a conference - via the web page (Note: the new time must be longer than the already defined Maximum meeting duration). The allowed value range for the maximum meeting duration is from 0 (If timer set to 0, the end time notification will not appear) up to 999 minutes (i.e. approximately 17 hours).

5.4 File system (FTP) The TANDBERG MCU incorporates an internal FTP-server where various files can be stored. The MCU uses default files unless the administrator specifies/stores any of these custom files (the default files are hidden). All the files described below are stored with the filenames indicated in brackets. When storing any of these files directly from FTP the filenames specified must be used. However, storing from the web page will change filenames automatically. Legal File Formats: Pictures JPEG (.jpg) files that are not greyscale and non-progressive coded.

Recommended maximum size is 352x288.

Sounds 16bit 8Khz mono Wave (.wav) files.

System Settings TANDBERG parameter (.prm) files


D12925 Rev. 03 40

5.4.1 Picture files Welcome picture (welcome.jpg) The welcome image is shown when a new participant enter the conference. Password Enquiry picture (pwdreq.jpg) This is an image asking the site(s) to enter password. Password Reject picture (pwdrej.jpg) This is an image shown if wrong password is entered by the site. Encryption Required picture (encrypt.jpg) This image is shown to a site that does not support encryption (sent only if conference is encrypted).

5.4.2 Sound files Welcome sound (welcome.wav) This sound is sent to all participants when entering a conference. Password Enquiry sound (password.wav) This sound is sent to participants (upon entering) when a password is set for the conference.

5.4.3 Other files Parameter settings of MCU (all.prm) This file shows the current MCU parameter settings. Directory (dir.prm) This file contains the directory/phonebook of the MCU. Snapshots (confxxxx.jpg) During a conference a snapshot of the MCU transmitted image is displayed on the web page. By clicking on a connected site, the received image from that site may also be displayed. The snapshots are continuously being updated and accessed from FTP:\MCU-ip-address\tmp\snapshots\, where they may easily be downloaded on a PC. It is also possible to download the received MCU main stream as well as the transmitted/received duo stream from this FTP location.


D12925 Rev. 03 41

6 Environmental Issues 6.1 TANDBERG’s Environmental Policy

• TANDBERG’s Research and Development is continuously improving TANDBERG’s products towards less use of environmentally hazardous components and substances as well as to make the products easier to recycle.

• TANDBERG's products are Video Conferencing Solutions. The idea of Video Conferencing 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).

6.2 Environmental Considerations Like other electronic equipment, the TANDBERG MCU contains components that may have a detrimental effect on the environment. • Printed-wiring boards made of plastic, with flame-retardants like Chloride or Bromide. • Component soldering that contains lead. • 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 electronic equipment.


D12925 Rev. 03 42

7 Product Approvals The product has been approved by various international approval agencies, among others: UL, BABT 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 by the approval agencies show that the TANDBERG MCU complies with the following standards.

7.1 Connection of Tele-Terminal Equipment •

TBR 4 (Comply with EU’s Commission Decision 1999/5/EC).

7.2 EMC Emission - Radiated Electromagnetic Interference •

EN55022:1994 + A1:1995 + A2:1997 (CISPR 22:1993 + Corr. and Am.1 and Am.2) Class B (Comply with EU’s Commission Decision 89/336/EEC).

•

FCC Rules and Regulations Part 15, Subpart B, Class A.

7.3 EMC Immunity •

EN 55024:1998 •

EN 61000-3-2:1995 + A12:1995 •

EN 61000-3-3:1995 (Comply with EU’s Commission Decision 89/336/EEC).

7.4 Electrical Safety •

IEC 60950:1991 + Amd.1:1992 + Amd.2:1993 + Amd.3:1995 + Amd.4:1996 •

EN 60950:1992 + Amd.1:1993 + Amd.2:1993 + Amd.3:1995 + Amd.4:1997 + Amd.11:1997 (Comply with EU’s Commission Decision 73/23/EEC).

•

UL 1950 3. Edition • CSA C22.2 No. 950-M95

7.5 EMC Immunity • EN 55024:1998


D12925 Rev. 03 43

7.6 NEBS approval This product complies with the standards GR-63-CORE and GR-1089-CORE and is NEBS approved by UL. For NEBS compliance, the product should be installed in the following manner:

- Use the enclosed rack brackets marked "NEBS". - There should be a clearance of 9.1cm between the product and any other

product mounted in the rack.

8 Product Reliability The predicted reliability of the TANDBERG MCU is expressed in the expected random Mean Time Between Failures (MTBF) for the electronic components based on the Power On Hours (POH). • The POH for the TANDBERG MCU is > 69 000 hours. The MTBF value is dependent on correct handling (e.g.: ESD protective measures are used), installation and use of the TANDBERG MCU. • The Useful Life Cycle for the TANDBERG MCU is in excess of 6 years. • TANDBERG is in a position to identify batches of products with possibly less reliability than

stated above ('product tracking') and will in such an event inform their customers. • ISO 9001 certificate is available upon request from the manufacturer.


D12925 Rev. 03 44

9 Technical specification of TANDBERG MCU 9.1 Mechanical information12

MCU Height 4.4 cm 1.7 inWidth 44.2 cm 17.4 inDepth 31.8 cm 12.5 inWeight 5.15 kg 11.3 lbs

The TANDBERG MCU is a standard 19 inch rack mountable with 1U height.

Standard cables for TANDBERG MCU

Part no. Length

PRI cables (4) 111890 M1,M2,M3,M4 5.0 m 16.7 ft Ethernet cable 112083 5.0 m 16.7 ft RS232 cable 112489 3.0 m 10.0 ft Power cables (International package)

110207 (EU) 110208 (UK) 110209 (SW) 110212 (AUS)

2.5 m 8.3 ft

Power cable (US only) 110210 2.0 m 6.7 ft

9.2 Packaging The following table shows the approximate measurements on the cardboard packaging of the TANDBERG MCU system- as shipped from production.

Height 29 cm Width 68 cm Depth 56 cm Weight 13 kg

12 All figures are subject to change without any further notice.


D12925 Rev. 03 45

9.3 Operating Temperature and Humidity • 0° C to 35° C (32° F to 95° F) ambient temperature. • 10% to 90 % Relative Humidity (RH)

9.4 Storage and Transport Temperature • -20° C to 60° C (-4° F to 140° F) at RH 10-90 % (non-condensing)

9.5 System Power Consumption • Maximum power consumption for TANDBERG MCU is 90 W.


D12925 Rev. 03 46

10 Technical Specification sheet System Capacity Number of video conferencing endpoints: 16 Number of audio only endpoints: 16 Endpoints Supported H.320 conferencing endpoints H.323 conferencing endpoints Analouge/ IP telephony Bandwidth H.320 up to 2 Mbps H.323 up to 2 Mbps Video Standards H.261, H.263, H.263+, H.264 Audio Standards G.711, G.728, G.722, G.722.1 Live Video Resolutions Native PAL: QCIF (176 x 144 pixels) CIF (352 x 288 pixels) 4CIF (704 x 576 pixels) Native NTSC: SIF (352 x 240 pixels) 4SIF (704 x 480 pixels) Native PC resolutions: VGA (640 x 480 pixels) SVGA (800 x 600 pixels) XGA (1024 x 768 pixels) Transcoding Restricted/unrestricted interfaces and bandwidths from 56 kbits-2 Mbps in the same conference Network Interfaces 4 x E1/T1 G.703 (RJ-45) for ISDN PRI 2 x LAN/Ethernet (RJ-45) 10/100 Mbit Ethernet / Internet / Intranet Connectivity TCP/IP,DHCP,SSL,ARP,FTP,Telnet,HTTP, HTTPS SNMP Enterprise Management Embedded WEB server Support for TANDBERG Management Suite 10/100Mbit full/half duplex (manual or auto detect selection)

Other Supported ITU Standards H.320, BONDING (ISO 13871), H.231, H.243, H.221, H.242, H.245 MCU Features Dial in / dial out capabilities ISDN & IP* Downspeeding at call setup ISDN Downspeeding in call ContinuousPresence (CP4/CP9/CP16/CP5+1/CP7+1/auto) Voice Switched Best Impression – Automatic change of video image layout and resolution dependent on the number of participants 4 sites at 2 Mbps 16 video sites + 16 telephone sites H.243 Terminal names Request Floor from endpoints Assign Floor to endpoint Embedded Encryption Standards based on ISDN, IP and mixed ISDN / IP: H.233, H.234, DES 56 bit key, AES 128 bit key Automatic key generation and exchange Mix of DES / AES possible in the same conference Audio Features Automatic Gain Control Custom “Welcome” Sound (WAV) Custom “Password” sound (WAV) Entry/Exit tones Telephone noise suppression Mute of audio from any site Video Features Custom “Welcome” Pictures (JPEG) Custom “Password” Pictures (JPEG) Snapshot of ongoing conference (JPEG) Snapshot of ongoing Duo Video presentation (JPEG) Separate welcome page for encrypted conferences Frame Rates Up to 30fps in Continous Presence, Voice Switched and Presentation mode Duo Video Broadcast of a site’s presentation (all supported video resolutions) Supported in Continuous Presence and Voice Switched mode


D12925 Rev. 03 47

Security Features IP Administration passwords Password protected conference Password protected conference (H.243) DTMF Password Management via HTTPS IP password Services may be disabled: FTP, Telnet, Telnet Challenge, SNMP, HTTP, HTTPS, H.323 H.323 Network Features DiffServ IP Precedence TOS RSVP IPLR TF System Management Total management via embedded WEB server using HTTPS, SNMP, Telnet and FTP 1 x RS-232 for local software upgrades, local control and diagnostics Conference scheduling via TANDBERG Scheduler and TANDBERG Management Suite (Optional)

Embedded WEB server Total Conference and Call control System diagnostics Snapshot of ongoing conference Environmental Data Operating Temperature: 0° C to 35° C (32° F to 95° F) ambient temperature Relative Humidity(RH): 10% to 90% Storage and Transport Temperature: -20° C to 60° C (-4° F to 140° F) at RH 10-90 % (non-condensing) Physical Dimensions Height 4,4 cm (1,7 inches) Width 44,2 cm (17,4 inches) Depth 31,8cm (12,5 inches) Weight Net 5,15 kg (11,3lbs) Power 100-240 VAC, 50/60 Hz 90W max. power consumption 19 inch rack mountable

technical description of tandberg mcu with … description of tandberg mcu with software version d3...

Documents