IMG 1010 - Starting GateControl EMS

Overview:

The procedure below will explain how to start the GCEMS application. At this point, the files IMG_10.5.x.xxx.bin and IMGUserInterface_10.5.x.xxx.bin files have been transferred to the GCEMS server and have been installed. There are two ways to start the GCEMS and ClientView processes on the GCEMS server. The first way is by using the icons on the desktop if access to the Linux server is allowed through VNC or some other remote desktop application. The second method is used if remote access to the desktop is not allowed. In this case, an SSH session can be used to access the server.

Related Topics:

IMG 1010 - GCEMS Installation Script

Using ICONS on Desktop.

  • Login to the GCEMS server as user excelsw.
    username: excelsw
    password: excelsw

  • Once logged into the server, double-click on the StartGCEMS icon on the desktop. A screen like below will appear and all the processes will start automatically. To configure the IMG open ClientView and start a new configuration by either using the Configuration Wizard or load an existing .csa file and allow ClientView to configure the IMG. See IMG 1010 - Starting ClientView - Overview

  • If however the GCEMS had already been controlling the IMG(s) there will be a system.cfg file located in
    /opt/dialogic/common/config (Software 10.5.1 +)
    /opt/cantata/common/config (Software 10.3.x - 10.5.0)
    and the start script will ask "Would you like to begin a new configuration?" See screen capture below.

  • If you select Yes (1), the GCEMS will start its processes without creating a connection to any IMG(s). After starting ClientView, you will have the option to either start a new configuration with the Configuration Wizard or load an existing .csa file and allow ClientView to configure the IMG.

When loading a configuration using the .csa file, the IMG(s) that are part of the configuration will be reset by GCEMS. The IMG's are reset so the configuration file will configure the IMG fully from startup. The IMG resetting will also allow the system software to be upgraded at the same time if need be.

  • If No (2) is selected, GCEMS will inform you that it is starting using the system.cfg file. The GCEMS will query the IMG(s) in the configuration and check the status of their configuration tags. If any Tags are cleared, the GCEMS will automatically configure the IMG with the settings in the existing system.cfg file. This is the method to use when restarting the GCEMS and you do not want to impact Call Processing on the IMG(s).  See Below.


     

    • GCEMS is now started. Verify that all processes are running by entering the following command:

$ ps -ef | grep Man


You should see the following output showing all the processes running for GCEMS

Starting GCEMS using Terminal:

  • Login to the GCEMS server as user excelsw.
    username: excelsw
    password: excelsw

    • To start the GCEMS processes through SSH or Terminal, go to:
      /opt/dialogic/IMG/GateControlEMS/bin (Software 10.5.1 +)
      /opt/cantata/IMG/GateControlEMS/bin (Software 10.3.3 to 10.5.0)
      In each you can find the StartGCEMS file. Execute the following command.

$ ./StartGCEMS

  • At this point GCEMS will begin the starting process. All the screen captures above apply when starting GCEMS through telnet or terminal program. The screen capture you will see will depend on whether the system has been configured previously or not.

    • Once GCEMS has been started, verify all the processes have started also by executing

ps -ef | grep Man

command shown above.

CRON Jobs:

The GCEMS includes a crontab that manages the GCEMS processes. This crontab runs automatically when the GCEMS is started (StartGCEMS), and stopped when the GCEMS is stopped (StopGCEMS). This file should not be edited.

There is a user crontab where cron jobs can be added tasks such as file or CDR management. The user cron file is located at /opt/dialogic/common/cron/usercron.

This crontab runs automatically when the GCEMS is started, and stopped when the GCEMS is stopped.

Return to Documentation Home I Return to Sangoma Support