OpenMCU-ru Administrator Guide 2015

OpenMCU-ru Administrator Guide 2015

Author:
Eugene Blanchard
SAIT Polytechnic
Calgary, Alberta
Canada
[email protected]

Version 1.0

Page 1 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

Table of Contents
1. Introduction............................................................................................................ 4
2. Test Environment Specifications............................................................................. 5
3. Features.................................................................................................................. 6
4. Operation............................................................................................................... 6
5. Command Line Options.......................................................................................... 7
6. Installation:............................................................................................................. 8
7. Exploring OpenMCU-ru........................................................................................ 10
8. Initial Settings..................................................................................................... 13
9a. Configuring a SIP video softphone client............................................................15
9b. Configuring a H.323 video softphone client........................................................19
10. Verifying disabled auto conference room creation..............................................20
11. The first conference room.................................................................................. 21
12. Recording a Conference..................................................................................... 24
13. Creating and deleting a Conference Room.........................................................26
14. Taking Control of a Conference Room.................................................................27
15. Creating a multiple display conference room.....................................................35
16. Voice Activity Detection (VAD)............................................................................38
17. Telnet to OpenMCU-ru Server.............................................................................39
18. Settings.............................................................................................................. 40
Settings - General.................................................................................................. 40
Settings - Advanced.............................................................................................. 41
Advanced - Conference...................................................................................... 41
Advanced - Export (named pipe)........................................................................42
Advanced - Registrar.......................................................................................... 42
Advanced - Control Codes.................................................................................. 42
Advanced - Video............................................................................................... 43
Advanced - Telnet............................................................................................... 43
Settings - Users..................................................................................................... 43
Users - Users...................................................................................................... 44
Version 1.0

Page 2 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

Users - Groups.................................................................................................... 44
Settings - H.323..................................................................................................... 44
H.323 - H323 parameters...................................................................................44
H.323 - H.323 Endpoints.................................................................................... 45
H.323 - Audio codecs (receive)...........................................................................45
H.323 - Video codecs (receive)...........................................................................46
H.323 - Audio codecs (transmit).........................................................................47
H.323 - Video codecs (transmit).........................................................................48
Settings - RTSP...................................................................................................... 48
RTSP - RTSP parameters..................................................................................... 48
RTSP - RTSP Servers........................................................................................... 48
RTSP - RTSP Endpoints........................................................................................ 49
Settings - SIP......................................................................................................... 49
SIP - SIP parameters........................................................................................... 49
SIP - SIP Endpoints............................................................................................. 50
SIP - Account information...................................................................................50
SIP - Audio codecs.............................................................................................. 50
SIP - Video codecs.............................................................................................. 52
19. Connecting to Asterisk....................................................................................... 53
Enable video support in FreePBX...........................................................................53
Configure Linphones as extensions on FreePBX...................................................53
Creating FreePBX extension for Conference Room 1001.......................................54
Configure Account Information for Conference Room 1001...................................54
20. Performance Results........................................................................................... 55
21. Display Matrix..................................................................................................... 59

Version 1.0

Page 3 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

1. Introduction
This manual is based on the original OpenMCU User Manual located here:
http://openmcu.ru/public/OpenMCU-ru/manual/user_guide_en.pdf
OpenMCU-ru is the fork of original OpenMCU with a lot of new features. OpenMCU is
a simple Mutli Conference Unit (Multipoint Control Unit) using the H.323 and SIP
protocols. It requires special version of H323plus library modified by Varnavskiy
Andrey Ivanovich. It is known to run on Linux, FreeBSD and Windows and should run
on any platform supported by H323plus and Sofia-SIP.
This guide is free to distribute, modify, edit, share as you see fit as long as you
reference the authors.

Version 1.0

Page 4 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

2. Test Environment Specifications

This user manual is based on testing using the following hardware and software
platforms, the testing was performed mainly using the SIP protocol. Sorry dont
have access to H.323 resources.

Proxmox 3.4-1 host :

o Dual 8 core Intel 3.4 GHz processors
o 72 GB RAM
o RAID 10 300 GB
o HP DL160 G6
OpenMCU-ru virtual machine guest:
o 1 GB memory
o 1 core
o 32 GB hard-drive
o Hardware x86_64
o OpenMCU-ru 4.1.3
o CentOS 6.6
SELinux disabled
Firewall disabled
o Linux 2.6.32
100 Mbps Ethernet network
Layer 3 switch with interVLAN routing (3 VLANs)
Tested across 5 routed networks
4 to 5 Video clients running at any time:
o 4x Linphone 3.8.4 Desktop client softphone for Windows
640x480 video out from phone
1280x720 video in to phone
H.264 codec
o Nortel 1535 IP phone
172x144 video out from phone
352x288 video in to phone

I used a virtualized environment just because it was easy to setup a virtual machine
in my lab. Having a dedicated server would work just as well if not better.

Version 1.0

Page 5 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

3. Features
OpenMCU contains the following features:

configured by a web interface on port 1420 (use http://host:1420 access)

requires no codec hardware to operate
supports all plugin audio codecs supported by OpenH323
supports H.261, H.263 and H.264 video
can accept multiple connections simultaneously
several different conferences can be talking place at the same time
using the 'rooms' feature
display statistics on calls in progress
initiate calls from the MCU to remote endpoints
support the use of a gatekeeper (for example gnuGk)

4. Operation
OpenMCU works by setting up a H.323 listener process, and then waiting for
incoming
connections. Whenever an incoming connection is established, it determines which
conference is
required via the 'rooms' feature and adds the call to that conference. You call the
MCU using the
format 'room_name@server_name' or 'server_name##room_name' depending on
the notation for
your hard/software client.
For Example for myphone3 type:
[email protected]
New rooms are created automatically and there is a default room for people who do
not specify a
room or cannot specify a room (eg NetMeeting). The default room is called room101
(this can be changed in the Settings Section).

Version 1.0

Page 6 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

5. Command Line Options

OpenMCU-ru can be run by the command line but it is not necessary as the
installer will automatically configure it to run properly. A web GUI interface is
normally used to configure OpenMCU-ru.
openmcu [-c] -v|-d|-h|-x
-h --help

output this help message and exit

-v --version

display version information and exit

-d --daemon

run as a daemon

-u --uid uid

set user id to run as

-g --gid gid

set group id to run as

-p --pid-file

name or directory for pid file

-t --terminate

orderly terminate process in pid file

-k --kill

preemptively kill process in pid file

-s --status

check to see if daemon is running

-c --console

output messages to stdout rather than syslog

-l --log-file file

output messages to file or directory instead of syslog

-x --execute

execute as a normal program

-i --ini-file

set the ini file to use, may be explicit file or

a ':' separated set of directories to search.

-H --handlemax n

set maximum number of file handles (set before uid/gid)

-C --core-size

set the maximum core file size

Version 1.0

Page 7 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

6. Installation:
OpenMCU-ru can be installed in Linux or Windows. This Administrator Guide focuses
on the Linux installation. The operation of OpenMCU-ru is similar for both operating
systems.

1. I installed CentOS 6.6 as a virtual machine under ProxMox 3.4.

Immediately did a Software Update of CentOS (twice to catch

everything)
SELinux was disabled
Firewall was disabled with plans to enable it and open the needed ports
later.

Note: CentOS was chosen as it is the absolute easiest installation method at

this time!

2. CentOS installation: open a web browser and go to

http://openmcu.ru/public/OpenMCU-ru/ and find the latest version of
OpenMCU-ru. At the time of writing, 4.1.3 was the latest:

3. Click on it and select Open with Package Installer. You will need root
privileges.

Version 1.0

Page 8 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

4. Package Installer will automatically check for dependencies and install if

needed.

5. OpenMCU-ru is installed in /opt/openmcu-ru directory:

[root@localhost openmcu-ru]# ls -l
total 80
-rw-r--r-- 1 root root
320 Jun 5
drwxr-xr-x 2 root root 4096 Jun 16
drwxr-xr-x 2 mcu mcu
4096 Jun 26
-rw-r--r-- 1 root root 18305 Jun 5
drwxr-xr-x 2 root root 4096 Jun 16
drwxr-xr-x 12 root root 4096 Jun 16
drwxr-xr-x 4 root root 4096 Jun 16
drwxr-xr-x 2 mcu mcu
4096 Jun 16
-rw-r--r-- 1 root root 1069 Jun 5
drwxr-xr-x 2 mcu mcu
4096 Jun 26
-rw-r--r-- 1 root root 2566 Jun 5
drwxr-xr-x 2 mcu mcu
4096 Jun 26
drwxr-xr-x 2 root root 4096 Jun 16
drwxr-xr-x 2 root root 4096 Jun 16
drwxr-xr-x 4 root root 4096 Jun 16
drwxr-xr-x 2 root root 4096 Jun 5

15:23
14:30
13:10
15:23
14:30
14:30
14:30
14:54
15:23
13:12
15:23
14:45
14:33
14:30
14:30
15:23

AUTHORS
bin
config
COPYING
font
include
lib
log
NEWS
pipe
README
records
resource
scripts
share
ssl

6. Once installed, check that OpenMCU-ru is running. As the root user, from a
terminal window type:
service openmcu-ru status
Or
/etc/init.d/openmcu-ru status

7. Starting and stopping the server (rarely ever need to):

service openmcu-ru start/stop
Or
/etc/init.d/openmcu-ru start/stop

Version 1.0

Page 9 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

7. Exploring OpenMCU-ru
8. Open up a web browser and point it to http://127.0.0.1:1420 on your server.
You will start at the Welcome Page of OpenMCU-ru:

9. The Welcome Page is divided into 4 sections:

The Menu Bar

Clicking on OpenMCU-ru returns to the Welcome Page

The Status option displays an information window on the
currently running conference rooms
The Control option opens up the Main Configuration window for
conference rooms
The Records option opens the Recording Management window
that displays and manages recorded conference rooms.
The Settings option is a pull-down menu consisting of submenus
for configuring OpenMCU-ru
The Help option directs you to the OpenMCU-ru wiki and forums.

Information Section

Version 1.0

Page 10 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

The Information Section informs you that the server is running and
general information.

Server Status

The Server Status section provides information on the configuration of

the server

Custom Logo Image Section

The Custom Logo Image section allows you to upload an image that
will be used in a conference room when a participant initially connects
and before the participants video starts.
I created a simple 640x480 image to use (you can add your company
logo):

Version 1.0

Page 11 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

Custom Logo Image Example

Version 1.0

Page 12 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

8. Initial Settings
OpenMCU-ru works very well right out of the box and there are very few
settings that need to be changed.

10. First step is to secure your server by configuring a password for the admin
user. Go to Settings Users Users:

11. Add a password to the admin user and select Accept. Now when you
connect to OpenMCU-ru, you will be asked for a username and password.

12. The default conference room name is room101. To make it easier to

integrate with FreePBX (asterisk based PBX), I changed the default room to
1001. Go to Settings General:

13. For security purposes, disable auto-create conference room on the wildcard
room. Go to Settings Advanced Conferences and disable Auto create
when connecting:

Version 1.0

Page 13 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

This will force all participants to connect to an existing conference room and
prevent a denial of service attack.

Version 1.0

Page 14 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

9a. Configuring a SIP video softphone client

The free Linphone SIP softphone (http://www.linphone.org) is a good tool for
testing OpenMCU-ru. It uses the H.264 codec which provides the best video
quality and it allows you to connect directly to the conference room without
needing to register with a PBX.

Most every other softphone requires that you register first with a PBX then dial
through the PBX to get to OpenMCU-ru. Which means that you have to have
routes configured between the PBX and OpenMCU-ru to test. This makes testing
very difficult use a Linphone and make your life easy. Later, well configure
integration with the FreePBX (Asterisk based PBX) and go down that road.

14. Install Linphone on a PC or laptop with a web cam. Install the Cisco H.264
codec as it is the preferred codec for video.

15. When Linphone first starts up, the Account Setup Assistant will pop up. Just
hit cancel for now.

16. Go to Options:

Version 1.0

Page 15 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

17. Make sure that Always start video is checked.

18. Go to Options Preferences Network settings:

19. Set the following parameters. These will be needed later for FreePBX
(Asterisk) interoperability:
SIP UDP port:
5060
SIP TCP port:
506
Audio RTP/UDP:
10000 - 20000
Video RTP/UDP
10000 - 20000

20. Next go to the Multimedia tab:

Version 1.0

Page 16 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

21. Check that the Audio devices are selected and work properly.
22. Select your Web Camera and a Prefered video resolution of vga 640x480.
23. Go to Manage SIP Accounts tab and change Your username. The default
username is toto, for testing purposes, I named my users after characters
from the movie The Wizard of Oz:

24. Go to the Codecs tab and disable the VP8 codec. The quality is very poor
compared to the H.264 and the resolution is restricted to a small window.

Version 1.0

Page 17 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

25. There is the option to Enable adaptive rate control but I havent evaluated
it to make a decision whether it is a good thing or not.

Version 1.0

Page 18 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

9b. Configuring a H.323 video softphone client

The free MyPhone3 h.323 softphone
(http://openmcu.ru/wiki/en/terminals/myphone) is a good tool for testing
OpenMCU-ru. It can use the H.264 codec which provides the best video quality
and it allows you to connect directly to the conference room without needing to
register with a PBX.
The MyPhone3 has a lot of video codecs and display formats available which is
great for testing and checking video quality with the Status window of OpenMCUru (more on this later).

26. After installing the MyPhone3, go to Settings - Video and configure for the
best video quality:

Set the In and Out Video for 4CIF (704x576). This will need to be finetuned to get the best video resolution for full screen.

Disable all video codecs except the H.264-4CIF3 codec for now.

Version 1.0

Page 19 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

Version 1.0

Page 20 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

10. Verifying disabled auto conference room creation

At this point, you are ready to join the default conference room.

27. From the Linphone, dial 1001@<ipaddress of MCU>, see green highlight:

28. You should receive a Forbidden error message (highlighted in red). This tells
us that auto creation of conference rooms is disabled!

29. From the MyPhone3, dial 1001@@<ipaddress of MCU>, see green highlight:

Version 1.0

Page 21 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

30. You should receive a Refuse error message (highlighted in red). This tells us
that auto creation of conference rooms is disabled!

11. The first conference room

31. On OpenMCU-ru, create the conference room by going to the Control Option
and selecting the Create Room button next to 1001. This will create
conference room 1001.

32. From the Linphone, now connect to sip:1001@<IP address of MCU. You will
see the Custom Logo Image momentarily flash on the screen while the
Linphone (participant) joins the conference:

Version 1.0

Page 22 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

33. Then your web cam will be displayed:

34. It is difficult to see at this time but behind the conference participants name
are two options: Full Screen and Hangup. Full Screen sets the video image to
full screen and hangup ends the conference call for this participant.

35. When another participant calls in to 1001@<IP address of MCU>, you will see
the Custom Image Logo while they are initially joining the conference.
OpenMCU-ru is operating in Auto mode at this time and will automatically
reconfigure the screen for the number of participants.

36. Monitor the Status of the conference room by going to the OpenMCU-ru
Status Option:

Version 1.0

Page 23 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

This shows:
audio (OPUS) and video (H.264) codecs and resolution (640x480) that
the participants are using.
the Video Out codec (H.264) and resolution (1280x720).
the Duration connected
bandwidth used (Packets, Bytes and Kbit/s)
frames per second (FPS) rate.

Version 1.0

Page 24 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

12. Recording a Conference

37. To record a conference, go to the Control option and press the Record button:

38. To monitor the recording, go to the Records Option:

You can download or delete the recording from this window. When you delete
a recording, you will be prompted to verify the deletion.

39. To stop recording, go back to the Control Option and press the

Version 1.0

Page 25 of 63

button.

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

40. The conference is recorded in .asf format and can be played back using VLC
media player.

41. NOTE: I was only able to record a conference rooms #0 display and not #1.
So if you have a multi-display conference room be aware.

Version 1.0

Page 26 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

13. Creating and deleting a Conference Room

42. To create room 1002, type 1002 in the textbox and select Create Room. A
second conference room named 1002 will be created.

43. Participants will join the new room 1002 by dialing 1002@<IP address of
MCU>. Room 1002 will run separately from room 1001.

44. To delete a room, press the delete room button

, any participants who are

connected will be disconnected.

Version 1.0

Page 27 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

14. Taking Control of a Conference Room

Taking control of a conference room is the term used when the room is changed
from automatic configuration mode to manual configuration mode.

45. Go to the Control Option and select the room button

46. This will open up room 1001 control:

47. Hovering over any of the icons or buttons will bring up a help box for that
item.

48. The

button is the Take Control button and is used to switch between

auto mode

Version 1.0

and manual configuration mode

Page 28 of 63

. In order to change the

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

configuration of the conference room, you must take control of it. When you
take control, you become the Operator.

49. If you attempt to change the configuration while in the auto mode, an error
message will flash at the top of the screen:

50. The button functions on the upper left side are as follows:

Take Control/Auto mode

Select room
The (3) indicates # of participants

Mute/Unmute invisible members

VAD parameters
(Voice Activity Detection)

Start/stop recording

Sort mode

51. Logging screen shows information concerning the conference rom:

Version 1.0

Page 29 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

52. Available video filtering algorithms available:

Openmcu-ru built-in
Libyuv
An open source project that includes YUV scaling and conversion
functionality.
Scale YUV to prepare content for compression, with point, bilinear or
box filter.
Convert to YUV from webcam formats.
Convert from YUV to formats for rendering/effects.
Rotate by 90/180/270 degrees to adjust for mobile devices in portrait
mode.
Options filtering algorithms available:
o kFilterNone
o KFilterBox
Swscale
Used to display the video at a different pixel size/aspect ratio than it
was encoded at when you don't have hardware video scaling support.
Swscale also performs colorspace conversion between various RGB and
YUV color formats, and conversion between packed (all channels in a
single buffer) and planar (each channel has its own buffer) formats. All
of these routines are highly optimized.

Swscale used for for transcoding video, if the source video is not
already in the format needed by the encoder. For instance, if your
source video is RGB, you'll need to convert it to the appropriate YUV
planar format, since most codecs work on YUV. This entails both
colorspace conversion (an affine transformation of the R,G,B vectors)
and actual scaling (resampling), since most YUV formats use halfresolution U and V planes (color planes) compared to the Y plane
(luma, i.e. intensity data).
Optional filtering algorithms available:
o SWS_FAST_BILINEAR
o SWS_BILINEAR
o SWS_BICUBIC
Page 30 of 63
Version 1.0
by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

o SWS_X
o SWS_POINT
o SWS_AREA
o SWS_BICUBIN
o SWS_GAUSS
o SWS_SNC
o SWS_LANCZOS
o SWS_SPLINE

53. Average CPU load is displayed:

54. The Display will show the current state of the conference room and
participants.

55. To remove a participant from a display position, click on the red X

in the

corner of their video.

56. Hovering over any of the participants highlighted in pink on the right side will
show their position on the display. I hovered over the tinman (highlighted in
red) and his video becomes highlighted:

Version 1.0

Page 31 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

57. At the top of each participants position is the

information icon. It lists the username and URI. Clicking on the
through the following options:

icon cycles

-?

-?
58. In Take Control mode, participants are not automatically added to the
conference. The conference operator has to assign participants to a display
position by dragging and dropping participants.

59. These options available at the bottom of the room display are described:

Identifies display number and allows you to add or delete

a display

Pull-down menu that allows you to change the display

matrix

Displays a pop-up window showing matrix choices (see

section 21)

Add all participants listed in pink to the display

Rotate participants diagonally across display matrix

Rotate participants position right to left, bottom to top

direction

Version 1.0

Page 32 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

Randomly position participants in display

Rotate participants position left to right , top to bottom

direction

Kick participants out of display

60. Indication that a participant has disconnected shows Gone Offline:

61. Participants can join the conference room by this section:

Use the Room tab to manually invite participants by typing their URI and
selecting the dial button . The participants video phone will ring and when
answered, they will join the room :

Tip! Before dialing, add the participant to the Address book by clicking on

Using the Address tab book members to invite participants:

Version 1.0

Page 33 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

You can invite all address members or individual by using the checkboxes.

The Account tab allows you to add existing participants to the Address book and
invite them to the room:

62. The buttons functions on the right side of the screen are as follows:

Mute all participants mics

Unmute all participants mics

Invite all active members

Run continuous dialing all members

Remove all inactive members

Drop all active connections

63. Participant parameters:

identifies the user Dorothy and their URI

indicates that the participant is active
controls the Voice Activity Detection:
o
indicates enabled (default)
o

Version 1.0

disabled
Page 34 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

Chosen Van: will take VAD position permanently even if no

voice comes from them.

is an audio volume level meter

allows you to adjust the audio input (mic) level and the audio
output (speaker) level for each participant if needed.

mutes the video of this participant to other participants. The other

participants in the room see a screen capture (picture) instead of a live
video feed. This would be used when there is a video problem with a
participant
mutes the rooms video to this particular participant and replaces it
with a black screen. Does not affect other participants.
toggles the orientation of the video from horizontal to vertical

removes users from video mixer

assigns which display the participant will view
invites participant to room by dialing their URI

indicates that the participant is connected to the room

disconnects the participant from room
removes participant from room list

64. Saving the conference room template:

After saving, the template will appear as a pull-down option for other rooms:

Selecting the room template will bring up the address book and participants.

65. The lock icon

is used to lock ____________? Once locked _________ are

allowed?

Version 1.0

Page 35 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

15. Creating a multiple display conference room

When creating a conference room where the participants are in two separate
locations, often each location only wants to see the other location. They dont want
to see themselves on screen. OpenMCU-ru allows the creation of additional displays
that participants can be assigned to.

66. Go to the Control Option and select the conference room. Select the
button to create a second display

67. The window will change to show the new display #1 with no participants:

Version 1.0

Page 36 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

In this example, Scarecrow and Toto are located in Calgary and Dorothy and
Tinman are located in Edmonton. The Calgary participants only want to see
Dorothy and Tinman who are located in Edmonton. While the Edmonton
participants only want to see Scarecrow and Toto.

68. Change the display matrix on both displays to 1|1 setting. This will show
each citys participants side by side. Drag and drop the Calgary participants
into the top display and the Edmonton participants into the bottom display:

Version 1.0

Page 37 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

69. Change the display that each participant sees so that they see the other
citys participants. Go to their account and click on the display # to change:

Each city will now see the other citys participants.

70. The Status Window will now show two video out streams each going to 2
participants:

Version 1.0

Page 38 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

Version 1.0

Page 39 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

16. Voice Activity Detection (VAD)

Voice activity detection is used to reduce the amount of background noise. The
audio input (mic level) from a participant is muted until a present level (threshold) is
reached before the mic is turned on. This reduces the background noise that the
participants hear.
The voice activity detection parameters are set separately for each conference
room and are accessed after taking control of the room. When the VAD button
is pressed the following options appear:

The parameters that can adjusted are:

Voice Activation Volume:
o Range: 25-25000, default: 100
Delay:
o Range: 0 65535 ms, default: 1000 (1 sec)
Timeout:
o Range: 0-65535 ms, default 10000 (10 sec)

Version 1.0

Page 40 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

17. Telnet to OpenMCU-ru Server

The Settings Advanced Telnet Server allows you to configure a telnet daemon so that you can
telnet into the OpenMCU-ru software and manually create rooms through a command line. This
is NOT the linux command line but a command line interface into the OpenMCU-ru server
application. The Telnet port number is configurable and the default port number is:
Telnet port: 1423
You will not normally be creating a room in this manner. The available instructions are
# room 'name' ...
create
delete
dial 'id'
invite 'address'
drop 'id'
show members
start_recorder
stop_recorder
ctrl c to exit

Version 1.0

Page 41 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

18. Settings
OpenMCU-ru provides complete control of the MCU with the option for the
administrator to fine tune the MCU to their specific needs:

71. Hovering over the Settings Option, displays the submenus:

Settings - General

Version 1.0

Page 42 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

Settings - Advanced

Advanced - Conference

Version 1.0

Page 43 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

Advanced - Export (named pipe)

Advanced - Registrar

Advanced - Control Codes

Version 1.0

Page 44 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

Advanced - Video

Advanced - Telnet

Settings - Users

Version 1.0

Page 45 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

Users - Users

Users - Groups

Settings - H.323

H.323 - H323 parameters

Version 1.0

Page 46 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

H.323 - H.323 Endpoints

H.323 - Audio codecs (receive)

Version 1.0

Page 47 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

H.323 - Video codecs (receive)

Version 1.0

Page 48 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

H.323 - Audio codecs (transmit)

Version 1.0

Page 49 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

H.323 - Video codecs (transmit)

Settings - RTSP

RTSP - RTSP parameters

RTSP - RTSP Servers

Version 1.0

Page 50 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

RTSP - RTSP Endpoints

Settings - SIP

SIP - SIP parameters

Version 1.0

Page 51 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

SIP - SIP Endpoints

SIP - Account information

SIP - Audio codecs

Version 1.0

Page 52 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

Version 1.0

Page 53 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

SIP - Video codecs

Version 1.0

Page 54 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

19. Connecting to Asterisk

The following steps document connecting to an Asterisk PBX using the FreePBX
distribution of Asterisk. It is assumed that you are familiar with FreePBX. The basic
steps are:

Enable video support in FreePBX

Create extensions for Linphones
Enable H.264 codec, disable VP8 codec
Create an extension for OpenMCU-ru in FreePBX
Configure OpenMCU-ru Account Information to use FreePBX extension

Enable video support in FreePBX

72. Go to FreePBX Settings - Asterisk SIP Settings Video Codecs and Enable
Video Support then Submit and Apply .

73. Go back to Enable Video Support and select H.264 only.

Max bit rate: 384 kb/s

74. Set Reinvite Behavior to Enable

75. Submit and Apply

Configure Linphones as extensions on FreePBX

76. Configure SIP extensions for the Linphones on FreePBX.
77. Set Canreinvite: YES
78. Disable VP8 codec so only H.264 codec is present.
79. Configure Linphone account to register to your PBX
80. After registering to your PBX, perform *65 (speak your extension) to verify that the
phone is registered.
81. Dial *43 (echo test) to verify that audio is properly being transmitted. Video should be
echoed also (wait, it takes a short time).
82. Make a video call from one Linphone to the other using the extension number.

Version 1.0

Page 55 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

Creating FreePBX extension for Conference Room 1001

83. Make a SIP extension in FreePBX for the conference room 1001.
Extension: 1001
Display name:
Conference 1001
Secret:
*******
Canreinvite: YES

Configure Account Information for Conference Room 1001

84. In OpenMCU-ru, go to Settings SIP Account Information:

Account:
1001@<PBX IP address>
Check Register box
Room name:
1001
Address SIP-proxy: <PBX IP address>
Password:
<extension secret>
Expires:
600

85. Make a phone call to extension 1001 from both your Linphones. You should connect into
conference room 1001 with excellent video quality.

Version 1.0

Page 56 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

20. Performance Results

This is section is to provide you with an idea of the computing resources used for a
conference server.
Test specifications:
4 participants 640x480 H.264 video codec, OPUS audio codec
Network 100 Mbps Ethernet
Proxmox 3.4-1 host :
o Dual 8 core 3.4 GHz processors
o 72 GB RAM
o RAID 10 300 GB
o HP DL160 G6
OenMCU-ru virtual machine guest:
o CentOS 6.6
o 1 GB memory
o 1 core
o 32 GB hard-drive

Version 1.0

Page 57 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

86. OpenMCU-ru status for room 1001:

87. Proxmox VM performance monitoring:

The initial jumps are indications of when participants are being added to the
conference room.

Version 1.0

Page 58 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

Two displays
This is the CPU usage after a 2nd display is configured. The CPU usage goes from
roughly 70% to 90%.

Version 1.0

Page 59 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

Stability
Ive run a conference room for hours at a time while testing and have had no issues.
It just keeps working. No memory creep or unusual CPU spikes or anomalies.

Version 1.0

Page 60 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

21. Display Matrix

When in a rooms control and after taking control. The
matrix window

button displays the

Available Display Matrix Choices:

Version 1.0

Page 61 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

Version 1.0

Page 62 of 63

by
Eugene Blanchard, June 2015

OpenMCU-ru Administrator Guide 2015

Version 1.0

Page 63 of 63

by
Eugene Blanchard, June 2015