Jump to: navigation, search

Core Component Installation

After the server has been prepared, continue with installing the Genesys Video Gateway components.

Important
You must install the platform with zenon_maint user. However, you need root/super-user access for the post-installation scripts (as specified below).

Step 1: Install Collaboration Notification Server

  1. Get the Collaboration Notification Server IP.
  2. Run the install.sh file. The Genesys Installation starts (sudo access is not required to install the IP).
  3. When prompted, enter the following details to complete the installation:
    1. Your public domain name or the hostname of the machine if no public domain name is available.
    2. The destination folder, which is the temporary folder where the installation files will be unzipped. Make sure that the user performing the installation has write access to this temporary folder.
  4. If the installation is successful, the console displays the following message:
    Installation of Collaboration Notification Server, version 9.0.00x.yy has completed successfully.
    Note: The installer output is written to the zs_install.log file, located in the same folder from where the installer is run. If you encounter any installation issues, be sure to check this log file.
  5. When the installation is complete, go to the temporary folder that is entered and run the post_install_zs.sh script (requires sudo access), with the following argument:
    sudo post_install_zs.sh

Step 2: Install Collaboration Application Server

  1. Get the Collaboration Application Server IP.
  2. Run the install.sh file. The Genesys Installation starts (sudo access is not required to install the IP).
  3. When prompted, enter the following details to complete the installation:
    1. The private/internal IP of the box.
    2. Your public domain name or the hostname of the machine if no public domain name is available.
    3. The destination folder, which is the temporary folder where the installation files will be unzipped. Make sure that the user performing the installation has write access to this temporary folder.
  4. If the installation is successful, the console displays the following message:
    Installation of Collaboration Application Server, version 9.0.00x.yy has completed successfully.
    Note: The installer output is written to the zas_install.log file, located in the same folder from where the installer is run. If you encounter any installation issues, be sure to check this log file.
  5. When the installation is complete, go to the folder where zas_install.log is run from and run the post_install_zas.sh script (requires super-user access), with the following argument:
    sudo post_install_zas.sh [MySQL Password]

Step 3: Install Collaboration MCU

  1. Get the Collaboration MCU IP.
  2. Run the install.sh file. The Genesys Installation starts (sudo access is not required to install the IP).
  3. When prompted, enter the following details to complete the installation:
    1. The destination folder, which is the temporary folder where the installation files will be unzipped. Make sure that the user performing the installation has write access to this temporary folder.
  4. If the installation is successful, the console displays the following message:
    Installation of Collaboration MCU, version 9.0.00x.yy has completed successfully.
    Note: The installer output is written to the install.log file, located in the same folder from where the installer is run. If you encounter any installation issues, be sure to check this log file.

Step 4: Platform Start-up

  1. Start the Genesys Video Gateway by running the following commands:
    /etc/init.d/zenon_zs
    /etc/init.d/snmp_start
    Important
    The user may be asked to enter the zenon_maint user password if the scripts are run from that account.
  2. Check if the NS has started:
    ps -elf | grep zs.prop
    0 S 501      31460 30524  1  80   0 - 891051 futex_ Sep14 ?       00:45:17 /usr/share/jdk1.7.0_07/bin/java -Xbootclasspath/p:/opt/zenon/zenonserver/lib/npn-boot-1.1.1.v20121030.jar -Dfile.encoding=UTF-8 -Xms256M -Xmx1024M -XX:+UseParallelGC -XX:-UseGCOverheadLimit com.blackboard.zs.Main zs.properties log4j.properties
  3. Check if the two MCU related processes are running:
    ps -ef | grep maxmcu
    0 S 501      30597     1  0  80   0 - 253344 futex_ Sep14 ?       00:01:14 /opt/zenon/bin/maxmcu -c -x /opt/zenon/share/config/zenon/zenon_2100.cfg
    0 S 501      30628     1  0  80   0 - 550644 futex_ Sep14 ?       00:03:05 /opt/zenon/bin/maxmcu -c -x /opt/zenon/share/config/saypage/saypage_2130.cfg
  4. To re-start the components, run:
    /opt/zenon/sh/stop_genesys_video.sh

    Followed by:

    /etc/init.d/zenon_zs
  5. After the installation is done, you can set SELINUX to enforcing in /etc/sysconfig/selinux, and then reboot the server.

Step 5: Validate the Platform

After all of the components have been configured, you can check if the system is functioning by running some simple tests from a browser.

  1. Type http://yourdomain.com/ to return the start page in a browser.
  2. To test WebRTC operation, a loopback tester is at the following URL, which echos back audio and video in a WebRTC-capable browser.
    http://yourdomain.com/user/demo/w.jsp
  3. To test Flash operation, use the following URL from a browser other than Chrome. Click voice/video call and it should echo back audio/video.
    http://yourdomain.com/user/demo/index.jsp
  4. On the server itself, you can verify the MCU operation by using the following command. This command returns valid HTML for the MCU status page.
    wget http://localhost:2131
  5. On the server itself, you can verify the NS operation by using the following command. This command returns false if the platform is up and running. Note that wget is pre-installed as part of Common.
    wget http://127.0.0.1:14040/?command=ZSSICK

Note: The Genesys Video meeting room feature is disabled by default, and by going to https://yourdomain.com, the following message displays:

Genesys Video Gateway

The feature you requested is currently not available.

Next Steps

Configure and customize the platform.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on 2 October 2016, at 08:23.