TANDBERG MCU Technical Description
TANDBERG MCU Technical Description

TANDBERG MCU Technical Description

With software version d3
Hide thumbs Also See for MCU:
Table of Contents

Advertisement

Quick Links

Technical Description of TANDBERG MCU with software version D3
Technical Description
of TANDBERG MCU
with software version D3
TANDBERG
D12925 Rev. 03
D12925 Rev. 03
1

Advertisement

Table of Contents
loading

Summary of Contents for TANDBERG MCU

  • Page 1 Technical Description of TANDBERG MCU with software version D3 Technical Description of TANDBERG MCU with software version D3 TANDBERG D12925 Rev. 03 D12925 Rev. 03...
  • Page 2: Table Of Contents

    Technical Description of TANDBERG MCU with software version D3 Table of contents INTRODUCTION ............................5 PRODUCT DESCRIPTION..........................6 ............................. 6 OFTWARE ERSIONS OPERATION AND USER INTERFACE ...................... 6 MCU INTERFACES & FEATURES ......................7 ......................7 ETWORK NTERFACES AND EATURES 4.1.1...
  • Page 3 Technical Description of TANDBERG MCU with software version D3 4.4.5.1 Duo Video Interoperability with other vendors ..................... 29 4.4.6 Custom pictures ............................30 ............................31 UDIO EATURES 4.5.1 Audio levelling/ Automatic Gain Control (AGC)..................31 4.5.2 Telephone Noise Suppression ......................... 31 4.5.3...
  • Page 4 Technical Description of TANDBERG MCU with software version D3 ....................45 TORAGE AND RANSPORT EMPERATURE ........................45 YSTEM OWER ONSUMPTION TECHNICAL SPECIFICATION SHEET ....................46 D12925 Rev. 03...
  • Page 5: Introduction

    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.
  • Page 6: Product Description

    Technical Description of TANDBERG MCU with software version D3 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: •...
  • Page 7: Mcu Interfaces & Features

    Technical Description of TANDBERG MCU with software version D3 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. 2 LAN ports...
  • Page 8: Mixed Isdn And Ip Conferences

    (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).
  • Page 9: 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.
  • Page 10 Technical Description of TANDBERG MCU with software version D3 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.
  • Page 11: Ethernet / Lan Interface (H.323)

    Technical Description of TANDBERG MCU with software version D3 4.1.4 Ethernet / LAN Interface (H.323) The TANDBERG MCU have two RJ-45 jacks 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.
  • Page 12: Automatic Selection Of H.323 Or H.320 Outgoing Calls

    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 •...
  • Page 13: Diagnostic Tools For Ip

    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.
  • Page 14: Ip Packet Sizes

    • 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.
  • Page 15: Leds Description

    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.
  • Page 16: Intelligent Call Management (Icm)

    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.
  • Page 17: Mcu Capacity

    (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.
  • Page 18: Mcu Capacity - Typical Scenarios

    *) 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’...
  • Page 19: Secure Conference (Encryption)

    - 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.
  • Page 20: Number Of Encrypted Sites (Software Option 16+16)

    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.
  • Page 21: Password

    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.
  • Page 22: Aggregation Standards

    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.
  • Page 23: Rs232 Interface/Application Programmable Interface (Api)

    Clear to send, CTS From DCE Ring indicator, RI From DCE 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.
  • Page 24: Video Features

    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.
  • Page 25: Video Formats

    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.
  • Page 26 Technical Description of TANDBERG MCU with software version D3 • 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’...
  • Page 27: Automatic Resolution Switching

    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...
  • Page 28: Video Transcoding

    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).
  • Page 29: Duo Video

    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...
  • Page 30: Custom Pictures

    Technical Description of TANDBERG MCU with software version D3 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.
  • Page 31: Audio Features

    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.
  • Page 32: Telephony

    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’...
  • Page 33: System Management

    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.
  • Page 34: Protocols Supported

    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.
  • Page 35: Management Using A Standard Telnet-Client

    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.
  • Page 36: 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): •...
  • Page 37: Layer 4 Ports Used By The System

    Technical Description of TANDBERG MCU with software version D3 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 ⇔ Gatekeeper Discovery 224.0.1.41:1718...
  • Page 38: Miscellaneous Features

    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.
  • Page 39: Phone Book

    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.
  • Page 40: Picture Files

    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.
  • Page 41: Environmental Issues

    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.
  • Page 42: Product Approvals

    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 •...
  • Page 43: Nebs Approval

    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.
  • Page 44: Technical Specification Of Tandberg Mcu

    17.4 in 31.8 cm 12.5 in Depth Weight 5.15 kg 11.3 lbs The TANDBERG MCU is a standard 19 inch rack mountable with 1U height. Standard cables for Part no. Length TANDBERG MCU PRI cables (4) 111890 M1,M2,M3,M4 5.0 m 16.7 ft...
  • Page 45: Operating Temperature And Humidity

    • 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...
  • Page 46: Technical Specification Sheet

    Technical Description of TANDBERG MCU with software version D3 10 Technical Specification sheet System Capacity Other Supported ITU Standards Number of video conferencing endpoints: 16 H.320, BONDING (ISO 13871), H.231, H.243, Number of audio only endpoints: 16 H.221, H.242, H.245...
  • Page 47 Technical Description of TANDBERG MCU with software version D3 Security Features Embedded WEB server IP Administration passwords Total Conference and Call control Password protected conference System diagnostics Password protected conference (H.243) Snapshot of ongoing conference DTMF Password Management via HTTPS...

Table of Contents