3. Table of contents
Chapter 1 Introduction ............................................................................................................................ 1
This guide .................................................................................................................................................. 1
Assumptions .................................................................................................................................. 1
Related documentation ............................................................................................................ 1
Using this document .................................................................................................................. 2
Chapters in this guide ................................................................................................................ 3
Chapter 2 Video conferencing today ................................................................................................. 5
Introduction ............................................................................................................................................. 5
H.323 protocol ......................................................................................................................................... 5
Video conferencing elements ................................................................................................. 5
Video conferencing, networking and telephony protocols .................................................... 6
Chapter 3 The Codian video conferencing family ......................................................................... 9
Introduction ............................................................................................................................................. 9
MCU 4200 series ...................................................................................................................................... 9
IP VCR 2200 series ................................................................................................................................11
Gateway 3200 Series ...........................................................................................................................12
Chapter 4 Different video conferencing scenarios .....................................................................13
Introduction ...........................................................................................................................................13
Simple scenarios ...................................................................................................................................14
MCU with three or more endpoints ....................................................................................14
Streaming to a web browser with the MCU ....................................................................14
Sharing data with the MCU and two or more endpoints ............................................15
IP VCR recording a call or playing back a recording on an endpoint .....................16
Sharing data with the IP VCR .................................................................................................17
Recording a conference with an MCU, IP VCR and two or more endpoints ........18
ISDN GW and an ISDN endpoint video conferencing ..................................................19
Video conferencing with a gatekeeper ........................................................................................21
IP VCR recording a point-to-point call ...............................................................................21
MCU or IP VCR with a gatekeeper and two or more endpoints ...............................21
ISDN GW with a gatekeeper and IP and ISDN endpoints ...........................................22
Video conferencing with a gateway ..............................................................................................22
Video conferencing with a firewall ................................................................................................23
Chapter 5 First steps ...............................................................................................................................25
Introduction ...........................................................................................................................................25
Networking considerations ..............................................................................................................25
Configuring user accounts (all units) ............................................................................................25
Setting an administrator password ....................................................................................26
The guest user ............................................................................................................................26
Other user accounts and privilege levels ..........................................................................26
i
4. MCU specific user fields ..........................................................................................................27
Port reservation (MCU only) .............................................................................................................27
Configuring auto attendants (MCU and IP VCR) .......................................................................28
Auto attendants on the MCU ................................................................................................28
Auto attendants on the IP VCR .............................................................................................29
Customizing the auto attendant banner ..........................................................................30
Localized MCU units ............................................................................................................................30
Customizing voice prompts (MCU and IP VCR) .........................................................................30
Communicating with the unit .........................................................................................................30
Chapter 6 MCU administration ...........................................................................................................33
Introduction ...........................................................................................................................................33
Conferencing considerations ...........................................................................................................33
How participants access conferences ................................................................................33
Types of conference .................................................................................................................33
Scheduled vs. ad hoc conferences ......................................................................................34
Permanent vs. time limited conferences ..........................................................................34
Stopping scheduled conferences early .............................................................................34
Advantages of pre-configured endpoints ........................................................................35
Setting up and controlling conference layouts ..............................................................35
Who displays in the large pane ............................................................................................36
Conference PINs .........................................................................................................................36
Conference ownership ............................................................................................................36
Content channel support .......................................................................................................36
Selecting a video size (4CIF feature key only) .................................................................36
Summary information icon ....................................................................................................37
Enabling the MCU for H.239 .............................................................................................................37
Configuring endpoints .......................................................................................................................37
Setting up a H.323 gateway ..............................................................................................................37
Cascading MCUs ...................................................................................................................................38
Load balancing MCUs .........................................................................................................................38
Sending messages during a conference ......................................................................................38
Using the MCU with a gatekeeper .................................................................................................39
Displaying conference and participant statistics ......................................................................39
Chapter 7 IP VCR administration .......................................................................................................41
Introduction ...........................................................................................................................................41
Making recordings ...............................................................................................................................41
Recording settings ....................................................................................................................41
Displaying the connection status ...................................................................................................42
Enabling the IP VCR for H.239 ..........................................................................................................42
Configuring endpoints .......................................................................................................................42
Summary information icon ...............................................................................................................43
Setting up a H.323 gateway ..............................................................................................................43
Transferring recordings ......................................................................................................................43
Recording file formats .............................................................................................................43
ii
5. Transferring by re-recording .................................................................................................43
Using the IP VCR with a gatekeeper ..............................................................................................44
Displaying IP VCR statistics ...............................................................................................................44
Chapter 8 ISDN gateway administration ........................................................................................45
Introduction ...........................................................................................................................................45
Installing the ISDN gateway .............................................................................................................45
Establishing a connection with the ISDN network ...................................................................45
Routing calls between IP and ISDN networks ............................................................................45
Basic call routing ........................................................................................................................46
Advanced call routing ..............................................................................................................46
Setting up a gatekeeper ....................................................................................................................47
Using the ISDN gateway for voice-only calls ..............................................................................47
IP to ISDN calls ............................................................................................................................48
ISDN to IP calls ............................................................................................................................48
Monitoring calls ....................................................................................................................................48
Chapter 9 Using data .............................................................................................................................49
Introduction ...........................................................................................................................................49
Configuring content channel support ..........................................................................................49
PC-based streaming of the content channel ..............................................................................50
Using the main video channel as the content channel ..........................................................50
Recording the content channel in a conference .......................................................................51
Chapter 10 Streaming (MCU and IP VCR) ..........................................................................................53
Introduction ...........................................................................................................................................53
Configuring streaming .......................................................................................................................53
Multicast streaming on the MCU .........................................................................................53
Streaming ad hoc conferences .............................................................................................54
Port allocation when streaming ......................................................................................................54
Content channel streaming ..............................................................................................................54
Web conferencing option .................................................................................................................55
Customizing streaming ...........................................................................................................56
Chapter 11 Using a gatekeeper ............................................................................................................57
Why use a gatekeeper ........................................................................................................................57
Registering a unit with a gatekeeper ............................................................................................57
Registration types (MCU and IP VCR) .................................................................................57
Service and dial plan prefixes ...............................................................................................58
MCU Registrations, Prefixes and Conference IDs ......................................................................58
Registering conferences and recordings with a gatekeeper (MCU and IP VCR) ...........59
Registering auto attendants with the gatekeeper (MCU and IP VCR) ...............................59
Chapter 12 Using firewalls ......................................................................................................................61
Introduction ...........................................................................................................................................61
The Codian video firewall ..................................................................................................................61
Port functionality in the video firewall ..............................................................................61
Configuring the video firewall ..............................................................................................63
Example video firewall configuration ................................................................................63
iii
6. Working with third party firewalls ..................................................................................................65
Chapter 13 Call detail records (MCU-only) .......................................................................................67
Introduction ...........................................................................................................................................67
Configuring call detail records ........................................................................................................67
Chapter 14 General housekeeping .....................................................................................................69
Introduction ...........................................................................................................................................69
Setting the system time .....................................................................................................................69
System status and event logging ...................................................................................................69
Upgrading software versions ...........................................................................................................70
Using additional options (features keys) .....................................................................................70
Backing up the configuration file ...................................................................................................71
Shutting down a unit ..........................................................................................................................71
Index ..............................................................................................................................................................73
iv
7. Chapter 1 Introduction
This guide
Codian designs and manufactures the most advanced video conferencing products available in the market
today, bringing you the best in voice, video and data conferencing. Using a unique architecture and the
latest hardware technology, our products are both easy to use and powerful, offering outstanding quality,
performance and features.
This Guide for Administrators introduces you to video conferencing in general and the Codian family of
products in particular. The Guide for Administrators is a concepts document — it discusses the advantages
of the different configurations that Codian equipment makes possible. It also tells you where to find more
specific help on certain topics.
Assumptions
It is assumed that you understand computer networks but may not have used video conferencing equipment
before. If you have been the administrator of an MCU or other video conferencing equipment previously
you may want to go directly on to Chapter 3‚ “The Codian video conferencing family”.
Related documentation
Codian provides a large documentation suite and each type of documentation has a particular use:
The Getting Started Guide covers initial connection and configuration
The Tutorials run through the most commonly used features of the MCU and IP VCR series and
explain some common pitfalls by example
The Codian web site (www.codian.com) provides access to information and all our documents, which
you can download. Some examples are:
FAQs cover the most frequently asked configuration and troubleshooting topic
Endpoint guides tells you how to navigate with the endpoint’s remote control
Datasheets
Online help is available from the web interface of all Codian units. To display help at any time,
click the icon in the top right hand corner of the screen.
The online help provides both "how to" step-by-step instructions and separate pages of field
descriptions.
1
8. Introduction
However, if you still have a question about our products, send an email detailing the problem to our
technical support team at support@codian.com.
Include the following information in the email:
the serial number and product model number (for example: MCU 4210) of the unit
the software build number (to find this, in the web interface, go to Status > General)
where you purchased the unit
your contact telephone number
Using this document
The Codian Guide for Administrators is the starting point for information about Codian units. It refers to
all the other documents listed above. In particular, it provides titles of online help pages that tell you how
to carry out a task, or that provide detailed descriptions of fields on a page in the web interface. For
example: See the online help topic “Conference ownership”.
The instruction 'Go to Conferences > Move participants' means click the Conferences link on the menu
bar and then click the Move participants tab.
Figure 1: Conferences > Move participants
1 2
The instruction 'Go to Conferences and click Add new conference means click the Conferences link on
the menu bar and then click the Add new conference button.
2
9. Introduction
Figure 2: Conferences and click Add new conference
1 2
Chapters in this guide
The Codian Guide for Administrators has the following chapters:
Chapter 2‚ “Video conferencing today” provides a background to video conferencing and an
introduction to the units and protocols used
Chapter 3‚ “The Codian video conferencing family” introduces Codian video conferencing equipment
and highlights their main features
Chapter 4‚ “Different video conferencing scenarios” describes a number of ways of using video
conferencing equipment in general and the Codian products in particular in a number of scenarios
from the very simple to a large system
Chapter 5‚ “First steps” covers the typical questions and options that administrators have when they
first start video conferencing. The options and their advantages, disadvantages and consequences are
discussed
Chapter 6‚ “MCU administration” describes administrator tasks that are unique to the MCU
Chapter 7‚ “IP VCR administration” describes administrator tasks that are unique to the IP VCR
Chapter 8‚ “ISDN gateway administration”describes administrator tasks that are unique to the ISDN
gateway
Chapter 9‚ “Using data” discusses using a data channel as part of a conference or recording for example
to show a PowerPoint presentation and what you need to do as an administrator to set this up
Chapter 10‚ “Streaming (MCU and IP VCR)” covers what you need to do as an administrator if your
user will be streaming conferences or recordings
3
10. Introduction
Chapter 11‚ “Using a gatekeeper” discusses using a gatekeeper with any of our products and how you
register a unit with a gatekeeper
Chapter 12‚ “Using firewalls” discusses using the built-in firewall features in the Codian MCU and IP
VCRs
Chapter 13‚ “Call detail records (MCU-only)” discusses the use of call detail records with the MCU
Chapter 14‚ “General housekeeping” covers functions that you will require from time to time such as
upgrading your unit’s software
4
11. Chapter 2 Video conferencing today
Introduction
Video conferencing was first introduced in the 1960s but early systems were unreliable and difficult to
install, use and manage. The equipment and ISDN bandwidth were prohibitively expensive, audio and video
quality were poor.
Today IP-based video conferencing is an attractive and accessible face-to-face communications business
solution. Advances in video technology and the creation of industry standards have allowed for higher audio
and video quality, user-friendly web and desktop interfaces and seamless integration across networks.
Codian products are powerful and truly "plug and play", enabling quick and easy installation and effortless
integration into everyday business processes. Video conferencing is as easy as picking up the phone and
making a call. There is no need for prior arrangements, reservations or complex setup. There is an intuitive
on-screen audio-visual prompt, and an easy-to-use Web interface for scheduling a conference. Individual
users can use their endpoint’s remote to control their view of the conference.
H.323 protocol
One of the protocols used by Codian products for video conferencing is H.323. H.323 defines how a series
of network elements work together and the protocols to allow multimedia transmission across an unreliable
packet-based network such as the Internet. (The H.323 specification is published by the International
Telecommunications Union.)
Video conferencing elements
The H.323 specification defines a number of elements that are required for multimedia transmission.
However in everyday usage some of these element names are used more “loosely” and we try to distinguish
between the two:
H.323 Endpoint
Strictly an endpoint is an MCU, a terminal or a gateway (see below). However, the word endpoint is
usually used interchangeably with a terminal
H.323 Multipoint Control Unit or MCU
An MCU maintains the communications between all the participants in the conference call. An MCU
handles call control and the media exchange (for example voice and video) during a conference.
5
12. Video conferencing today
H.323 Terminal
The terminal is an endpoint on a network which provides for real-time, two-way communications. A
terminal may provide audio (speech) only, or audio in a combination of video and data.
H.323 Gatekeeper
A gatekeeper is optional and controls a zone. It provides a directory service allowing services to be
accessed via directory numbers (E.164 numbers) and alphanumeric names. It also provides call
control, routing services, bandwidth management and admission control. It also provides basic security
(authorization) for communications between H.323 elements within its zone.
H.323 Gateway
A gateway is any device that allows calls to be established between networks, whether of the same or
different types. It may also provide protocol conversion between H.323 endpoints and endpoints that
do not support H.323. For example:
The Codian ISDN GW can route calls to an H.320 ISDN network
The Codian ISDN gateway and VoIP gateways can perform H.323<->PSTN operations, routing
voice over IP (VoIP) calls from an H.323 terminal on to the public switched telephone network
(PSTN) allowing "normal" telephone calls to be made from an H.323 client
The elements can be software based and there can be more than one entity installed on a single computer.
The Codian MCU and IP VCR can act as a gateway to allow direct access to internal features such as
individual conferences or recordings. You can also set up gateway definitions on Codian MCUs and IP VCRs
so that outgoing calls can be routed to gateways.
Video conferencing, networking and telephony
protocols
H.323 encompasses a number of other protocols, including audio (voice) and video codecs, and standards
for passing data and control structures. The following are examples of some protocols supported by Codian
products and included in the H.323 framework that a video conferencing administrator is likely to come
across:
G.711, G.722, G.723.1, G.728 and G.729 are audio codecs
H.261, H.263(+) and H.264 are video codecs. H.264 is the most recent video compression standard.
It offers approximately twice the quality of H.263 at the same bandwidth, or the same quality at half
the bandwidth
H.239 which allows a secondary video channel. It defines how PC desktop graphics is converted in to a
separate media stream and transmitted in parallel with the video stream. This is the protocol that
Codian MCUs use for the data channel in a conference
H.225 and H.245 are signalling protocols
Siren14™ is a proprietary audio codec used by Polycom endpoints
6
13. Video conferencing today
Session Initiation Protocol (SIP) is a newer protocol, and an alternative to H.323. It is a simple signaling
protocol for Internet conferencing and telephony. SIP messages have a text format similar to HTTP, making
it more suited to Internet applications and easier to implement in software. However, it is not yet as
popular as H.323.
A number of networking and telephony standards can be involved: for example, ISDN, LAN, WAN,
Internet, ADSL (Asynchronous Digital Subscriber Lines) and VPN (Virtual Private Networks) are the
popular transport media used in desktop video conferencing.
Where necessary, these protocols are discussed in more detail later in the guide.
7
15. Chapter 3 The Codian video conferencing
family
Introduction
Codian produce a variety of units for video conferencing:
MCU 4200 series of multipoint control units
IP VCR 2200 series of video recorders for recording video conferences and point-to-point calls
ISDN GW 3200 series of video gateways that enable ISDN network connectivity from IP-based units
and endpoints
All units have a web interface and detailed, context-sensitive online help.
MCU 4200 series
The MCU 4200 series is the most powerful
multipoint control unit available and uses the latest
video technology. It is the first MCU ever to
maintain its port count (the number of people who
can access the conference bridge) regardless of how
users connect to a video conference, the speed at
which they connect, the layout they choose, and
their equipment. A seemingly expected feature, it is
unique in the video conferencing industry.
The unit streams both video and presentations to web browsers. Streaming sends conference audio and
video to a remote computer, allowing the user to watch and listen to a conference. The media flows in just
one direction, so it is not possible to contribute to a conference via streaming.
Optimized for use in IP networks, the MCU provides the best possible video and audio quality in real-
world network conditions and has proven compatibility with all major vendors.
The MCU has a firewall solution, integrated web server, scheduling, video auto attendant (also known as
an IVR) and additional voice ports.
9
16. The Codian video conferencing family
The MCU is available in a number of models:
Table 1: MCU models
Additional voice
Video ports Concurrent streaming ports
ports
MCU 4205 12 12 60
MCU 4210 20 20 100
MCU 4215 30 30 150
MCU 4220 40 40 200
Features and benefits of the MCU 4200 series include:
Conference scheduling as standard
Up to 200 conferences can be set up on the unit. The only thing that limits the number of conferences
actually running is the number of ports that are purchased.
One port per participant irrespective of setup. This makes scheduling and provisioning easy because
the port count is constant. There is no reduction in the number of MCU ports even using bandwidths
up to 4MB.
Encoding/decoding on a per user basis and not per conference: you can have any mix of bit rate,
resolution and codec within the same conference - with no loss of port count or functionality. At all
times every user sees the best possible video quality possible for their endpoint and connection. Also
one user's problems with the network do not affect others. This also simplifies conference
configuration because you do not need to know in advance all the characteristics of all endpoints.
Only one port is used for streaming irrespective of how many people join the conference as streaming
participants
The content channel e.g. a slide presentation using the H.239 protocol only uses one port even when
the content is sent to every participant who can receive it
A separate layout is generated for each endpoint. This means that participants can choose one of over
50 different continuous presence layouts to view during a conference without affecting anyone else.
This also means that participants never have to view themselves. (All streaming viewers see the same
layout chosen from the 50 available)
Support for 16:9 screens (wide screens)
On screen text messaging to individuals or to all sites
Support for every standard endpoint including Tandberg, Polycom, Aethra, Sony, Vtel and VCON
endpoints
10
17. The Codian video conferencing family
IP VCR 2200 series
The IP VCR 2200 series is a digital video
recorder for video conferencing, allowing video,
audio and content to be recorded from
standards-based video conferencing equipment.
It is the only product available today that can
preserve video and data (for example a
presenter's slides) for future viewing without
data needing to be uploaded in advance. The
content can be streamed live or played back on
demand at multiple bandwidths to a web
browser on a PC using QuickTime™, RealPlayer™ or Windows Media Player™ or to a video
conferencing endpoint.
The IP VCR plays back to H.323 endpoints (unique to Codian) and ISDN endpoints (via an ISDN gateway),
records conference calls and both ends of a point-to-point call, and streams to users' desktop machines at
multiple configurable bit rates. As well as connecting to the Codian MCU you can connect to any MCU on
the market because the IP VCR connects like a regular endpoint.
The video and data are recorded in their native formats with no loss in quality. Intelligent transcoding and
transrating are performed on the data at the time of retrieval to ensure that the video quality is always
optimal whether being played back, streamed or exported.
The IP VCR is available in a number of models:
Table 2: IP VCR models
Concurrent streaming ports
Recording ports H.323 playback ports
(unicast/multicast)
IP VCR 2210 1 100/unlimited 5
IP VCR 2220 5 200/unlimited 10
IP VCR 2240 10 400/unlimited 20
11
18. The Codian video conferencing family
Gateway 3200 Series
The ISDN GW 3200 series is a high
performance video gateway that permits calls
from IP endpoints to ISDN endpoints and vice
versa. The gateways work with E1, T1 and
Japanese T1 ISDN networks. It allows video
conferencing and telephone (voice) calls. See
the online help topic “Using the ISDN gateway
for voice calls”.
The ISDN GW 3200 series allows multi-
channel calls using ISO BONDING or H.221 aggregation, supports H.239 data sharing (a content channel)
and supports the following protocols: G711A/μu, G728, G722, G729, H261, H263, H263+ and H264.
Calls can be transmitted between 64kbps and 768kbps and you can restrict call duration and/or prevent
outgoing ISDN calls.
The ISDN GW 3200 series works perfectly with the Codian MCU. It can also work with a gatekeeper
allowing registration of an H.323 id and service prefix, and can call IP addresses with optional extensions.
There are three models with 1, 2 or 4 PRIs (Primary Rate Interfaces)/ISDN ports. IP services can be
enabled and disabled or moved between ports. The ISDN Gateway has one Ethernet port.
12
19. Chapter 4 Different video conferencing
scenarios
Introduction
Video conferencing can take place in quite simple scenarios and in very large and complex networks. The
following diagram shows a high level overview that encompasses many of the scenarios that Codian
supports, from the simplest three-way conference using the Codian MCU to conducting and recording a
conference with both IP and ISDN endpoints using the Codian MCU, VCR and ISDN Gateway as well as
possible third party MCUs. The following sections start with the three-way conference using the Codian
MCU and work back up to this diagram explaining each “step”.
Figure 3: Overview of video conferencing
ISDN
ISDN Gateway ISDN
ISDN
endpoint
H.323
Gatekeeper MCU
ISDN Gateway
IP
Port A Port B IP
endpoint
MCU
IP network
H.323
IP network
IP
endpoint
IP VCR IP VCR
IP
Port A Port B
endpoint
MCU
H.323
IP Gateway
endpoint
Firewall
IP network
IP
endpoint
13
20. Different video conferencing scenarios
Simple scenarios
MCU with three or more endpoints
Figure 4: MCU with three or more endpoints
IP
endpoint MCU
IP network
IP IP
endpoint endpoint
This is the simplest video conferencing scenario. Two endpoints could make a point-to-point call but when
three or more endpoints want to hold a video conference, they need an MCU to co-ordinate the conference
and to send the video and streams from all the endpoints to each endpoint.
Streaming to a web browser with the MCU
In this scenario three endpoints are contributing to the conference and the PCs are streaming. This means
they see and hear the three participants but they cannot contribute themselves.
Figure 5: Streaming with the MCU
IP IP
endpoint endpoint
MCU
IP network
IP
endpoint
14
21. Different video conferencing scenarios
Sharing data with the MCU and two or more endpoints
In this scenario two or more endpoints can be holding a video conference via the MCU (three in the
following diagrams). In addition several PCs may be streaming the conference. Another PC is contributing
a video content channel to the conference; for example to show a PowerPoint presentation.
The data channel can come from a PC connected directly to a Codian MCU using VNC (top diagram) or
connected to an endpoint which then sends the presentation using the H.239 protocol (not all endpoints
support the direct connection of a computer). Virtual Network Computing or VNC is an open standard
commonly used for remotely controling one PC from another.
To display the data channel, endpoints can watch using the H.239 protocol. For endpoints that do not
support H.239, Codian MCUs can display the data in a standard video pane.
Figure 6: Sharing data with the MCU and two or more endpoints
MCU
IP
IP network
Computer contributing
the data channel
via VNC
IP
IP endpoint
endpoint
IP
endpoint
15
22. Different video conferencing scenarios
MCU
IP
Computer contributing
IP network the data channel
directly connected
to an endpoint
IP
IP endpoint
endpoint
IP
endpoint
IP VCR recording a call or playing back a recording on an endpoint
An endpoint calls in to the IP VCR and selects the Record this session option from the auto attendant or
the endpoint calls in to the IP VCR after it has been configured to record incoming calls by default.
The IP VCR records the stream from the endpoint. It can also record a data channel at the same time.
There are other ways to record using the IP VCR:
Call out and record - the IP VCR, via its web interface, calls out to a H.323 endpoint and records its
media streams. In this case the recording console allows you to see what is being recorded which can be
especially useful when recording conferences on an MCU.
Using a gatekeeper - as described later in this chapter.
16
23. Different video conferencing scenarios
Figure 7: IP VCR recording a call or playing back a recording
IP VCR
IP
IP network
IP
IP
endpoint
The IP VCR can support several endpoints dialing in simultaneously; however they are
completely independent of one another - unlike endpoints holding a conference via the MCU.
Equally, recordings can be played back:
The IP VCR, via its web interface, can call out to a H.323 endpoint and play back a recording to it
The endpoint can call in to the IP VCR's auto attendant and select the recording to play back
In a similar scenario, you can use a PC to connect to the IP VCR and select a recording to play back using
streaming.
Sharing data with the IP VCR
The IP VCR can record the content channel as well as the main video and audio streams. (The IP VCR
cannot record a content channel in isolation, only alongside the video and audio streams. This is unlike the
MCU which can connect to a PC directly using VNC.)
17
24. Different video conferencing scenarios
Figure 8: Sharing data with the IP VCR
IP VCR
IP
IP network
IP
endpoint
IP
IP endpoint
endpoint
Recording a conference with an MCU, IP VCR and two or more endpoints
The IP VCR can record a conference being hosted on an MCU if the IP VCR is added as an endpoint in the
conference. Equally the IP VCR can call in direct to the conference. (Also see ‚ “Video conferencing with a
gateway” later in this chapter.)
Figure 9: Recording a conference on the IP VCR
IP
endpoint MCU
IP IP
IP network
IP
IP
IP
IP
endpoint IP
endpoint
IP VCR
One of the IP endpoints, or collection of endpoints could be replaced with an ISDN gateway and ISDN
endpoint(s) - see the next section. To the IP VCR it is exactly the same as an IP endpoint and the IP VCR
can record the conference in the normal ways.
18
25. Different video conferencing scenarios
ISDN GW and an ISDN endpoint video conferencing
The ISDN gateway is a protocol converter that allows calls between IP and ISDN endpoints. An ISDN
gateway and ISDN endpoint(s) can replace an IP endpoint in any of the previous scenarios and then can be
used in conferences, for point to point calls, and to call out and record from the VCR for example.
Figure 10: ISDN gateway with an IP endpoint and an ISDN endpoint
ISDN Gateway
ISDN ISDN ISDN
IP ISDN
IP endpoint
endpoint
IP network
In the following diagram a computer contributes a content channel and both IP and ISDN endpoints can see
the data being transmitted. Either computer can contribute the data channel, but because there is only one
data channel they cannot both do so at the same time. This is different to the main video and audio
channels: both endpoints can send and receive video and audio simultaneously.
Figure 11: Sharing data with the ISDN gateway with an IP endpoint and an ISDN endpoint
ISDN Gateway
ISDN ISDN ISDN
ISDN
endpoint
IP
IP
endpoint
IP network
The following diagram shows ISDN endpoints in a conference being hosted by the MCU.
19
26. Different video conferencing scenarios
Figure 12: ISDN endpoints in a conference
ISDN Gateway
ISDN
ISDN ISDN
ISDN
MCU endpoint
IP
ISDN
ISDN
endpoint
IP network
IP
endpoint
IP
endpoint
PSTN telephones (including mobile phones) can join the conference as audio-only participants, as shown
below. The Codian ISDN Gateway works with PSTN telephones: you do not need to change any settings.
Figure 13: IP, ISDN endpoints and PSTN telephones in a conference
ISDN Gateway
ISDN
ISDN/PSTN ISDN
MCU ISDN
endpoint
IP
PSTN
PSTN
IP network Mobile
telephone
IP
endpoint
Regular
telephone
(POTS)
IP
endpoint
20
27. Different video conferencing scenarios
Video conferencing with a gatekeeper
All Codian units can use a gatekeeper. A unit registers with the gatekeeper, then when the unit calls out it
queries the gatekeeper to find out where to connect to.
IP VCR recording a point-to-point call
If you use a gatekeeper, the IP VCR can be used to record both ends of a point-to-point call between two
endpoints. This is initiated from one of the endpoints, and cannot be done via the IP VCR’s Call out and
record function.
Figure 14: IP VCR with a point-to-point call
IP
endpoint IP VCR
IP IP
IP network
IP
H.323
IP Gatekeeper
endpoint
On the IP VCR you register a prefix for point-to-point calls, say 11, and the endpoint registers its number,
say 222. To call point-to-point another endpoint calls the registered endpoint by dialing 11222. This is
directed to the IP VCR, which knows to call out to 222 and record the call.
The IP VCR records both endpoints' media streams - unlike the earlier scenario in which only one endpoint
was recorded.
MCU or IP VCR with a gatekeeper and two or more endpoints
A gatekeeper also makes it easier for participants to join conferences or watch and make recordings on an IP
VCR because they can dial using directory numbers rather than having to know the IP address or host name
of the unit. For example a participant can call a specific gatekeeper ID that is configured to trigger
recording. Equally an existing recording can be registered on a gatekeeper and it can be played back
subsequently by calling its registered gatekeeper ID.
21
28. Different video conferencing scenarios
Figure 15: MCU or IP VCR with a gatekeeper and two or more endpoints
IP
endpoint MCU or IP VCR
IP IP
IP network
IP
IP
endpoint IP H.323
Gatekeeper
IP
endpoint
ISDN GW with a gatekeeper and IP and ISDN endpoints
You can configure the ISDN gateway to use a gatekeeper, which can make it easier for end-users to make
calls using directory numbers rather than requiring them to know the IP address or host name of the ISDN
gateway.
Figure 16: ISDN gateway with a gatekeeper, IP endpoints and an ISDN endpoint
ISDN Gateway
ISDN ISDN ISDN
IP ISDN
endpoint
IP
endpoint
IP network H.323
Gatekeeper
MCU
IP
endpoint
Video conferencing with a gateway
A gateway can be useful when you do not have a gatekeeper or the gatekeeper is not accessible, for example
because it is behind a company firewall. The gateway can be a protocol converter such as Codian’s ISDN
gateway discussed previously, but it can also be a interface between two networks using the same protocol.
22
29. Different video conferencing scenarios
The Codian MCU and IP VCR allow you to define a gateway and this H.323 gateway definition is used to
direct an outgoing call more specifically than just using an IP address. This means that the gateway definition
can often be used instead of a gatekeeper. Typical uses are:
When the MCU calls an ISDN endpoint in to a conference, the gateway definition directs the call to the
ISDN gateway. The ISDN gateway interprets the second part of the calling address (a telephone
number in this case) and directs it to the ISDN endpoint.
When the MCU calls the IP VCR in to a conference as described earlier in this chapter. The gateway is
needed because calling with the IP address only is ambiguous: the VCR can have several responses to an
incoming call depending on how it is set up. By using the gateway you can route the call directly to the
IP VCR’s recording port so the IP VCR will start recording the conference. The call address has two
parts: the IP address of the IP VCR and an “extension” that defines the port on the IP VCR.
The following diagram shows the MCU with the two H.323 gateways defined.
Figure 17: Video conferencing with gateway definitions
ISDN Gateway
H.323 Gateway Definitions
IP VCR: IP address
ISDN ISDN ISDN
MCU
ISDN GW: IP address
IP ISDN
endpoint
IP network
IP
endpoint
IP VCR
IP
endpoint
Video conferencing with a firewall
The MCU and IP VCR have an integral, optional firewall feature. This is designed to allow video calls to be
made between "internal" and "external" IP endpoints, as indicated in the figure “Overview of video
conferencing” on page 13.
This is quite different from a third party firewall which would typically be used for all traffic. If you want to
use your existing firewall and make calls between internal and external endpoints, then that firewall must
be "H.323 aware”.
For more information about both see Chapter 12‚ “Using firewalls”.
23
31. Chapter 5 First steps
Introduction
When your unit is delivered, it is activated and ready to be connected and used straight away. Follow the
steps in the Getting Started Guide that comes with the unit.
You may also like to work through the Tutorials which are available from Codian’s web site. This provides
step-by-step instructions for some of the most commonly used features.
We suggest that you read the appropriate sections in this chapter for the MCU, IP VCR or ISDN gateway
that you are working with and then go on to the chapter that covers other functionality for that specific unit.
Networking considerations
When you connect your unit you need to consider whether to use DHCP or set a static IP address — see
the Getting Started Guide for the unit you are working with and the online help topic “Configuring
network settings”.
The default settings for the networking options will work in most situations. They should only be altered by
administrators with networking experience. For example on the MCU or IP VCR:
You should only need to set up Ethernet settings and routes if you are using both ports. See the Chapter
12‚ “Using firewalls”,and the online help topics “Configuring network settings” and “Configuring IP
routes settings”.
You should choose whether to use the in-built video conferencing firewall in the MCU/IP VCR and a
third party firewall. See Chapter 12‚ “Using firewalls”
Configuring user accounts (all units)
By default when a unit is delivered there are two user accounts: admin and guest (see the online help topic
“System defined users”). These accounts are used to log in to the web interface: people wanting to stream a
conference or select a conference from an auto attendant do not need to log in and therefore do not require
a user account.
25
32. First steps
Setting an administrator password
When a unit is delivered the admin user account has no password. However, this is insecure and you should
change the password to something meaningful to you (but that will not be guessed by another person) as
soon as possible.
Go to Users and click the admin link. See the online help topic “Adding and updating users” (MCU and IP
VCR) or “Updating users” (ISDN Gateway).
The other features of the admin user cannot be changed; on each unit the admin user has full privileges.
You must be logged in as the admin user to be able to change another user's configuration or
add new users.
The guest user
By default, anyone logging in to the web interface logs in with the guest user account which does not have a
password. By changing the configuration of the guest user you can limit what they can do. You can:
Enter a password for the guest user account
Change their privilege level (MCU and IP VCR) — see the next section
Go to Users and click the guest link. See the online help topic “Adding and updating users” (MCU and IP
VCR) or “Updating users” (ISDN Gateway)
Other user accounts and privilege levels
On the MCU and IP VCR the administrator can set up additional user accounts for which there are a
number of privilege levels to choose from (see the online help topic “Privilege levels”):
The IP VCR has 4 levels from viewing the recording list to full administrator rights
The MCU has 7 levels from viewing the conference list to full administrator rights
Whether you need to set up additional accounts depends on how you intend to use the unit:
MCU: if you have users whose main task is to schedule and monitor conferences, you may want to set
up user accounts for them with one of the "conference creation" privilege levels
MCU: if you want to display a still photograph of a voice-only participant in a conference in one of the
video panes, this participant must be set up as a user and his or her photograph uploaded. (The
maximum number of photographs that can be stored depends on the unit type and model but is quite
large. For example the Codian MCU 4220 supports 50 user photographs.) See the online help topic
“Adding and updating users”
IP VCR: if you have users who only need to stream recordings, they will need a user account at the
lowest level
26
33. First steps
IP VCR: if you have users who need to upload recordings, configure active connections or change
settings, they will need a user account
The maximum number of user accounts on all Codian MCUs and IP VCRs is 200 user
accounts.
The maximum number of user accounts on the ISDN gateway is 10 and there are only two
privilege levels: admin and list only (for the guest user that allows you to see basic details
about active calls).
MCU specific user fields
A number of fields appear in the MCU Add User page only. These work together.
It is possible to associate voice-only endpoints (via the E.164 phone number) with a user. If the user
calls in from this number the MCU identifies the call as being from the user. If the following fields are
then also configured for the user account, the MCU will know how to treat the call
Associated video endpoint — if this is an endpoint that you configured previously, then the MCU will
call out to this video endpoint on receiving an audio-only call from the E.164 number. This allows the
user to fully participant in a conference by talking and listening on the telephone but viewing the
conference video on the configured video endpoint. Moreover, the audio and video streams are
associated - for example, the volume that the participant talks with on the telephone is considered in
the same way as other participants when the MCU decides who appears in the largest video pane.
(There are different types of endpoint - go to Endpoints and see the online help topic “Displaying
endpoint list”)
Upload bit map — if you upload an static image after the user has been created, the MCU will display
this picture of the user (instead of a video stream) if they are participating as an audio-only participant
Port reservation (MCU only)
MCU has two types of ports: voice-only and video ports (that accept both video and audio). By default,
port reservation is disabled and the MCU will allocate the most appropriate type of port to each endpoint
until all the ports of that type are allocated. It will then allocate an audio-only port to an endpoint that can
support both video and audio until all the ports on the MCU are in use — and equally, if only video ports
are available, it will allocate a video port to an audio-only device until all are in use. It is not possible to
guarantee how many participants will be able to join a conference at any time because you cannot guarantee
how many ports will be used by other conferences.
However, if port reservation is enabled then this behavior changes. When you schedule a conference you
must specify the number of audio-only and video ports to reserve. The MCU will not allow you to specify a
number that would take the total port count during the conference to more than the MCU has. When you
display the conference list the number of participants is displayed as A/B where A is the number of active
participants and B is the configured limit. See the online help topic “Displaying conference lists”.
27
34. First steps
Enabling port reservation prevents:
the Create new conference option being displayed, even on auto attendants that are set up to have this
option and therefore ad hoc conferences cannot be created when port reservation is enabled
you creating a new auto attendant with this option
users calling in to the MCU with an unknown E.164 number setting up a new conference, even if
Create new conference has been set in the Conference settings page. See the online help topic
“Configuring global conference settings”. In this case, the user is disconnected
We recommend that you do not change the setting while there are active conferences. If you
enable port reservation, all ad hoc conferences are destroyed and their participants are
disconnected. Also some participants of scheduled conferences may also be disconnected — if
the number of ports reserved for a conference is less than the number of active participants at
the time you change mode. See the online help topic “Reservation of MCU media ports”.
Port reservation is enabled on Settings > Conferences. See the online help topic “Port reservation” which
explains the advantages and consequences of enabling port reservation.
VNC connections are video-only and therefore will never be allocated an audio-only port.
Streaming requires one video port per conference but any number of viewers can steam the
same conference on that port.
When a participant connects to an auto attendant, a port is borrowed from the pool because
the MCU does not know which conference to allocate the connection to until a conference is
selected. This means that if that participant is using the last media port and another endpoint
connects directly to a conference, the auto attendant link will be dropped.
Even when port reservation is disabled, you can set a maximum for the number of video and
audio-only participants in a conference. See the online help topic “Adding and updating
conferences”.
Configuring auto attendants (MCU and IP VCR)
When an endpoint connects to the MCU or IP VCR, the default auto attendant may be displayed with a
menu of options and an audio prompt is heard (see the online help topic “Using an auto attendant”).
Whether the auto attendant is displayed depends on how the units are set up.
Auto attendants on the MCU
The Codian MCU can have many auto attendants (otherwise known as Interactive Voice Responses or IVRs)
and menu structures can be setup by configuring multiple linked auto attendants. See the online help topic
“Adding and updating an auto attendant”.
28
35. First steps
By default, all active conferences are displayed on the default auto attendant - the auto attendant that the
MCU is delivered with. Alternatively, you specify which conferences appear on a specific auto attendant.
By default, the option Create a new conference is displayed on the default auto attendant so participants
can create new ad hoc conferences when they dial in. This option can be turned off. It is not available if
Media port reservation is enabled. See ‚ “Port reservation (MCU only)”.
When an auto attendant is displayed
On the Settings > Conference page you can configure how the MCU will behave when it uses a prefix
registered with a gatekeeper and an endpoint dials a number starting with that prefix. The options on this
page are to set up a new conference, disconnect the call or display the default auto attendant. See the online
help topic “Configuring global conference settings”.
The default auto attendant is also displayed if an endpoint calls the IP address or H.323 ID of the unit or if
an endpoint dials a number assigned to it.
All auto attendants can have a numeric ID assigned to them and when the number is registered with a
gatekeeper, the auto attendant can be dialed directly (See the online help topic “Adding and Updating an
auto attendant”). In this way, you can provide an alternative number for your participants to dial so that
they go directly to the specific auto attendant of your choice and only see the menu options you want them
to.
Setting a PIN for the auto attendant (MCU only)
For security you can decide whether a PIN has to be entered before an auto attendant is displayed.
Note that on the MCU each conference you see on the auto attendant may have its own conference PIN —
and the two uses of a PIN should not be confused. See the online help topic “Adding and updating an auto
attendant”.
Auto attendants on the IP VCR
The IP VCR has only one auto attendant. The auto attendant is a menu of options from which you can
record the session or select a previously stored recording to play back. Displaying the auto attendant is the
default in Settings > Connections but you can change this to:
automatically answer incoming calls and start recording
disconnect the call
Like the MCU, auto attendants on the IP VCR can have telephone numbers assigned and be registered
with a gatekeeper so they can be dialed directly.
Recordings can be registered with a gatekeeper. They can then be dialled directly by calling
the number that has been registered (bypassing the auto attendant) and play back will start
automatically.
29
36. First steps
Customizing the auto attendant banner
You can add a custom banner image to any auto attendant configured on the MCU or IP VCR. The banner
is the image at the top of the auto attendant menu page and the default is the Codian company logo. The
image file must be in GIF or Windows BMP format with a maximum size of 352 x 64 pixels. If the image is
smaller than 352 x 64 pixels so that the background color is seen, you may also want to change the
background color.
Display the Banner page for the auto attendant you want to alter and see the online help topic “Adding a
custom banner” for more information. To display the page:
On the MCU go to Conferences > Auto attendants, select the auto attendant and click Banner
On the IP VCR, go to Settings > Banner
Localized MCU units
If you prefer to work on a Codian MCU in a language other than English, Codian or a reseller can localize
your unit by uploading a localization package. The web interface pages, online help pages and voice
prompts will be displayed/played in your local language. The default files are not deleted and you can
return to English at any time. See the online help topic “Customization”: more information.
However, you can customize voice prompts yourself as described in the next section.
Customizing voice prompts (MCU and IP VCR)
By default the IP VCR and MCU includes English voice prompts spoken by a female American voice. You
may wish to replace these prompts with your own in order to change the wording, language or accent used.
Alternate prompts may be uploaded individually using the web interface (go to Settings >
Customization). After the voice prompts have been uploaded you can create a resource package of them.
You can then upload the resource package on to other units in one go.
For detailed instructions and guidance on making good quality voice prompt recordings, display the online
help topic “Customizing the user interface”.
Communicating with the unit
To communicate with a unit you must have connected its ports and defined its IP address as described in the
Getting Started Guide.
There are a number of ways to communicate with Codian units:
Serial port or console port - see the Getting Started Guide for your unit.
30
37. First steps
Web interface: this is the main administrator interface for configuring and managing all the units.
Simply open a web browser and type in the IP address of the unit.
FTP: FTP is not for everyday administration. If FTP connections have been enabled, then some
functions, such as backing up configuration files are best achieved using FTP on all units. The most
common use of FTP is to up/download recordings from the IP VCR.
Far End Camera Control (MCU and IP VCR) can be used to:
Select an option from an auto attendant
Control the video layout during conferences
DTMF tones (MCU only): these can be used at the auto attendant for joining a conference by its
numeric id, and for changing layout with endpoints that have no Far End Camera Control capabilities
Management API (MCU only): can be used by software applications to monitor and control the MCU
31
39. Chapter 6 MCU administration
Introduction
This chapter covers general administrator tasks specific to the MCU.
Conferencing considerations
Unit-wide settings are configured in Settings > Conferences. See the online help topic “Configuring
global conference settings”.
Settings for a specific conferences are defined in the Conferences > Add new conference page. Also see
the online help topic “Adding and updating conferences”.
How participants access conferences
There are a number of ways that a participant can join a conference:
Participants can dial in to a conference or the MCU can dial out. See the online help topics “Calling in
to conferences” and “Being invited in to a conference”
When dialing in, they can dial a conference directly if you provide the conference details, or they can
connect via an auto attendant. See “Configuring auto attendants (MCU and IP VCR)” on page 28
Participants may be able to join a conference and participate fully, or they may be allowed to stream the
conference only i.e. they can watch and listen but not contribute
Types of conference
Conferences can be set up when you need them (these are called ad hoc conferences) or can be scheduled to
start at a particular time. They can have a specified duration or be set up to be permanent. Scheduled
conferences can also be set up to repeat for example on a weekly basis.
Conferences can appear in three categories on the web interface:
Active conferences: conferences that are currently in progress
Scheduled conferences: conferences that have a specified start time. They can be in progress or yet to
start. Note that a scheduled conference can also be in the active conferences list
33
40. MCU administration
Completed conferences: scheduled conferences that have finished and are not scheduled to repeat
You can reactivate a completed conference by displaying its properties and adding a new start
date/time in the future.
See the online help topic “Displaying conference lists”.
Scheduled vs. ad hoc conferences
Scheduled conferences are set up through the web interface and can start at a specified time or immediately.
Ad hoc conferences are set up "on the fly" from the auto attendant, if the Create new conference option
is displayed.Ad hoc conferences always start immediately. See the online help topic “Adding and updating
conferences”.
Scheduled conferences can be set up to dial out to pre-configured endpoints — see “Pre-configuring
endpoints” later in this chapter — (and participants can also dial in). Participants can dial in to ad hoc
conferences and the MCU can dial out while the ad hoc conference is active but you cannot pre-configure
an ad hoc conference to dial out.
Ad hoc conferences are not permitted if port reservation is enabled — see “Port reservation (MCU only)”
on page 27.
Permanent vs. time limited conferences
When you set up a scheduled conference you can select the Permanent check box or set the maximum
duration. See the online help topic “Adding and updating conferences”. Permanent conferences are not
recommended if you are using port reservation (“Port reservation (MCU only)” on page 27) because they
do not release their port allocation even when there are no participants.
Stopping scheduled conferences early
If a conference is scheduled for 2 hours but the participants have finished after an hour, you can stop the
conference in two ways:
You can disconnect all the participants — see the online help topic “Viewing conference participant
list”. The conference remains an active conference but with no active participants. If you are using port
reservation — see ‚ “Port reservation (MCU only)”— then the ports remain allocated to the
conference until the scheduled end time and are not available for other conferences until that time.
You can end the conference by clicking End conference in the Conferences pages — see the online help
topic “Viewing conference participant list”. In this case, the conference is no longer active. If it was a
repeating conference, the conference becomes a completed conference and then all future instances
will not happen unless you display the conference properties and reschedule the conference to start at
the next occurrence. The conference duration is also reduced — and you may want to return this to its
previous value if you are rescheduling the conference.
34
41. MCU administration
Advantages of pre-configured endpoints
You can configure endpoints and then when you configure a conference, select one or more of these
endpoints to be called automatically when the conference starts. Configured endpoints that are also
configured in one or more conference definitions are said to be pre-configured for these conferences.
Pre-configured endpoints are designed to save you time and are useful when a participant takes part in one
or more conferences regularly. For example, when the conference configuration is set up to call the pre-
configured endpoints automatically, this saves you having to set up the details of each endpoint each time.
When an endpoint dials in, a number of parameters including its E.164 number and IP address are checked.
If the MCU matches these call-in parameters to an endpoint’s configuration, it will use the “Conferencing
parameters” in that definition, such as bandwidth and default family view.
There are two types of endpoint: H.323 and VNC and both can be configured and then added to a
conference configuration as pre-configured endpoints. A VNC endpoint (Virtual Network Computing)
enables you to have software applications such as a set of slides running on a remote computer added to a
conference. Go to Endpoints and click Add H.323 or Add VNC as appropriate and see the online help
topics “Displaying endpoint list”, “Configuring H.323 endpoints” and “Configuring VNC endpoints”.
Setting up and controlling conference layouts
When a participant joins a conference the screen layout seen is determined by the combination of settings at
a number of levels:
The default view set for the MCU. Go to Settings > Conferences and select the Default view family.
This can be overridden by the layout selected for a conference per individual participant. See the online
help topic “Customizing layout views”
The layout for all the participants of a conference in the conference’s Custom layout page. See the
online help topic “Customizing layout views”
The participant's custom layout settings. Go to Conferences and select a conference, then a participant
and click Custom Layout. See the online help topic “Selecting a custom participant view”
The participant's Display page. This shows the conference and participant custom layout selections as
additional alternatives to the layout families. See the online help topic “Customizing a participant's
layout view”. In addition you can select whether:
the participant can change their view
the participant can contribute H.239 content channel video - see Chapter 9‚ “Using data”
to send normal or widescreen video format to the participant's endpoint.
The Custom layout pages for a conference and for a participant have the same layout selections. You can:
Enable custom view layout
Select a view
Make all participants see this view now
35
42. MCU administration
Make all participants see this view when they join the conference
Unless you specifically prevent it on the participant's display page, each participant can
override the view you select for them by using their remote control.
Also see the online help topic “Understanding how participants display in layout views”.
Who displays in the large pane
By default the person talking the loudest in a conference is displayed in the largest pane in layouts that have
such a thing. The view is then voice controlled and the person displayed in the largest pane will change as
different people speak.
This can be overridden by making a participant “Important” by clicking the Make important icon. This
makes them the focused participant and gives them priority in the layout views. This is done in the
participant list.
Conference PINs
A conference may be assigned a PIN so that only people who know the PIN can join the conference.
Conference ownership
The person (user account) that sets up a scheduled conference is the conference owner initially. This can be
changed by users with administrator privileges or conference ownership and full control. Being a
conference owner allows control over the conference - the amount of control depends on the privilege level
of the user’s account. See the online help topic “Conference ownership”.
Content channel support
When you set up a conference, you control whether the conference will support an H.239 content video
channel. This is discussed in Chapter 9‚ “Using data”.
Selecting a video size (4CIF feature key only)
If you have the 4CIF feature key enabled (go to Settings > Upgrade to check) you can select a maximum
and default video size for each conference. Go to Settings > Conference and see the online help topic
“Configuring global conference settings”. You can then also select a preferred video size per H.323
endpoint to limit the video size sent or received to that which the endpoint supports (see the online help
topic “Configuring H.323 endpoints”). This setting takes precedence over the conference settings but is
limited by the maximum video size set for the conference.
If you are using an H.323 gateway to connect to the endpoint, the video size is also limited by
the maximum video size that can be sent through the gateway. See the online help topic
“Adding and updating gateways”.
36
43. MCU administration
Summary information icon
Click the Summary information icon to display details about a conference that has been selected in the
web interface. This information can be copied to the clipboard for convenience; for example to inform
participants about conference details such as start time and instructions on how to view the conference
using streaming.
Enabling the MCU for H.239
Before you can include a content channel in a conference you need to enable the MCU to do so. Go to
Settings > H.239 and see the online help topic “Configuring H.239 settings”. For more information on the
H.239 content channel see Chapter 9‚ “Using data”.
Configuring endpoints
Configuring endpoints speeds up configuring conferences if the same endpoints are used repeatedly.
You can configure an H.323 endpoint on the MCU by going to Endpoints and then selecting the type of
endpoint to add. Then to add endpoints to a conference, you just select its name from a list.
See the online help topic “Displaying endpoint list” and the online help topic for adding the type of endpoint
you are added, for example “Adding an H.323 endpoint”.
Setting up a H.323 gateway
The MCU has a gateway function which allows you to define the IP address of a gateway: for example you
could set up a gateway definition called Record my conference and this would specify the IP address of an IP
VCR. When you then call out from the MCU you can choose to use this pre-configured gateway definition
and the call will be directed to the specified IP address. In this case the IP VCR acts as a gateway.
(You can also call an IP address and number where the number is understood by the gateway unit you are
dialing. See the explanation in “Video conferencing with a gateway” on page 22.
Reasons why you may want to use these gateway definitions include:
To create a direct link to another unit without requiring a gatekeeper
To cascade MCUs in a conference without a gatekeeper - see the next section
To save typing in the IP address each time
Go to Gateways > Add H.323 gateway. See the online help topic “Adding and updating gateways”.
37
44. MCU administration
The ability to define how to access a gateway should not to be confused with our ISDN Gateway which is a
protocol converter as well as a call director.
Cascading MCUs
If you require a dial out scheduled conference with more than 40 participants, multiple MCU units can be
cascaded together. This would lose two ports for each cascade, providing a total of 78 ports. Also some
functionality would be lost between the cascade - such as the ability to choose the layout on the second
MCU if you are connected to the first. It is possible to set up the units so they can automatically cascade
together as part of a scheduled conference: one can automatically dial the other and join a conference and
set the correct layout to send between the units. For best results the cascaded MCU should be displayed in
the largest pane.
Adding an H.239 content channel to the conference will take a port on each MCU rather than
one for the entire conference and therefore the maximum number of participants would be
reduced by two.
Load balancing MCUs
Dial-in ad hoc conferences can be load balanced using a gatekeeper with a "round robin” mode. If you have
two MCUs of the same size that are both registered with the same gatekeeper with the same prefix, then
ad-hoc conferences will be assigned to one or other MCU, balancing the load between them. See the online
help topic “Configuring Global Conference Settings”.
For more information about using a gatekeeper see Chapter 11‚ “Using a gatekeeper”.
Sending messages during a conference
You can send messages to one participant in a conference or to all of them simultaneously. The message can
be up to 256 characters long and you can set the time for which the message will overlay each participant’s
view.
To send a message to one participant: go to Conferences, select a participant and then click on the
Send message tab. See the online help topic “Sending a message to an individual participant”
To send a message to all participants, go to Conferences > Send message. See the online help topic
“Sending messages to all participants”
38
45. MCU administration
Using the MCU with a gatekeeper
You can configure the MCU to use a gatekeeper, which can make it easier for participants to join a
conference using directory numbers rather than requiring them to know the IP address or host name of the
MCU. See Chapter 11‚ “Using a gatekeeper”.
Displaying conference and participant statistics
You can display statistics for a conference which may be helpful when managing conferences (see the online
help topic “Displaying conference statistics”) or for an individual participant which shows the status of a
participant’s link (see the online help topic “Displaying statistics for a participant”).
39
47. Chapter 7 IP VCR administration
Introduction
This chapter covers general administrator tasks that are unique to the IP VCR.
Making recordings
Recordings can be made by the IP VCR calling out to the endpoint or by an endpoint calling in to the IP
VCR (and the endpoint can be a Codian MCU). In either case you can make recordings non-interactively
— with no feedback to the user — or using the Recording Console. With non-interactive recording the IP
VCR does not send video to your endpoint: typically your endpoint displays a blank screen (see the online
help topic “Non-interactive recording”). To see what the IP VCR is recording, use the Recording Console.
For example this may be useful if you are making a presentation and you want to see the view that your
audience is seeing. See the online help topic “Using the recording console”.
Recording settings
Default action for incoming calls with an unknown E.164 number
When receiving calls with a number that does not match a recording to play back, the IP VCR can behave in
a number of ways:
Connect to auto attendant: Users see the default auto attendant with the Record this session
option. This displays the Recording Console.
Record session: Users see the video recording screen and can record the video from their endpoint
Disconnect caller: Users may not call the IP VCR in this way; the call is terminated
You select which action will happen. Go to Settings > Connections and see the online help topic
“Configuring global connection settings”.
Other settings
You can set the default and maximum video size and the default connection bandwidth to and from the IP
VCR. Go to Settings > Connections and see the online help topic “Configuring global connection
settings”. There are also a number of more advanced settings on this page but we recommend that you do
not change these unless you are an expert or told to do so by Codian technical support.
41
