Installing Prophecy 9 on Linux

Download the latest Linux build from here to your Home directory. Open a terminal as root and run:

sh ./prophecy-9.0.xxxxx.xxxxx-small-tts-ds-vm.bin

Replacing xxxxx.xxxxx with the build number you downloaded.

Note: You must be logged into root to install Prophecy. Using sudo may cause some services to be installed as your user, which could cause permission problems when starting, stopping or checking the status of those services. Using sudo to manipulate services after the installation is perfectly acceptable, however. If you are using a clean install of CentOS, sudo is likely not enabled for your user. For more information on using sudo, a more secure alternative to sudo, see here.

In a moment, you should be presented with a graphical install window. Click next, accept the EULA, and continue to click next. If everything went as planned, we should see the success screen:

Return to the command prompt and run:

sudo /opt/voxeo/prophecy start

We should see the output:



user@centos:~$ sudo /opt/voxeo/prophecy start

Service 'Voxeo Prophecy Log Search' started.

Service 'Voxeo Prophecy Log Indexer' started.

Starting  MC:

Service 'Voxeo Prophecy Management Console' started.

Starting  VXML:

Service 'Voxeo Prophecy VoiceXML Browser' started.

Starting  VCS:

Service 'Voxeo Prophecy Server' started.

Starting  SIPMethod:

Service 'Voxeo Prophecy SIPMethod Server' started.

Starting  Designer:

Service 'Voxeo Prophecy Designer Server' started.

CentOS - add your user to the sudoers file

If you've installed CentOS, you may notice that you'll need to use su in order to install/start/stop/restart Prophecy services. This isn't the most secure option, so you'll want to enable sudo instead.

First, go to System > Administration > Users and Groups. Enter your root password. Select your user and click Properties. Select the Groups tab and scroll down and check the wheel group. Click Ok and close out the Users and Groups window.

Next, open a terminal and type su, press Enter and enter your root password. Next, type visudo. Scroll down to the bottom and you should see the line # %wheel ALL=(ALL) ALL. Press i then delete the #. Press Escape then ZZ(caps required).

That's it. You can now perform any admin functions by typing sudo [command] and entering your user password instead of the root password.

CentOS - Add common utils and Prophecy's start script to the default $PATH

Next, you'll notice that the default CentOS path does not include the paths for some of the more useful Linux commands, such as ifconfig. As well, Prophecy's start/stop/restart script is located in /opt/voxeo, which is not part of $PATH. If you'd like to start/stop/restart Prophecy without having to navigate to this directory everytime, simply edit /home/username/.bashrc to look like this:



# .bashrc



# Source global definitions

if [ -f /etc/bashrc >]; then

        . /etc/bashrc

fi



# User specific aliases and functions

PATH=$PATH:/usr/sbin:/sbin:/opt/voxeo

This change will take effect next restart. To make it take effect immediately, type:



PATH=$PATH:/usr/sbin:/sbin:/opt/voxeo

export $PATH

Now you can manipulate Prophecy services from anywhere with:
./prophecy.sh start/stop/restart {service}

ANNOTATIONS: EXISTING POSTS

bpcamac

3/4/2010 5:58 AM (EST)

When installing P-9.0.40094.0-small-tts-ds-vm on a Centos 5.4 (2.6.24) headless server I also found it necessary to install the following packages:

$yum install libidn-devel libcap libxml2

to avoid the installer complaining about:

The following libraries are missing and will need to be installed separately.

Prophecy services will not be started.

Checking library dependency:
VCS FAILED
VCS depends on the following libraries:
libidn.so.11

vxlaunch FAILED
vxlaunch depends on the following libraries:
libidn.so.11

BsSndRpt FAILED
BsSndRpt depends on the following libraries:
libidn.so.11

named FAILED
named depends on the following libraries:
libcap.so.1
libxml2.so.2

voxeoJeffK

3/4/2010 7:04 AM (EST)

Hello,

Thank you for this detailed information. I have opened an internal exploration of the matter for our engineers to investigate. We will post back here with additional findings and information, but please do not hesitate to ask if we can help with any questions in the meantime.

Regards,
Jeff Kustermann
Voxeo Support

pampa

6/1/2010 6:41 PM (EDT)

Almost the same on my own CentOS (5.3)
Installer vers: prophecy-9.0.40094.0-small-tts-ds-vm.bin

The following libraries are missing and will need to be installed separately.
Prophecy services will not be started.

Checking library dependency:07:31 p.m. 01/06/2010
VCS FAILED
VCS depends on the following libraries:
libidn.so.11

vxlaunch FAILED
vxlaunch depends on the following libraries:
libidn.so.11

BsSndRpt FAILED
BsSndRpt depends on the following libraries:
libidn.so.11

named PASSED
Done.

VoxeoDustin

6/2/2010 11:59 AM (EDT)

Hello,

You'll need to install the Internationalized Domain Name support library.

Running 'sudo yum install libidn.i386' at the command prompt should do the trick.

Let me know if you have further difficulty.

Regards,
Dustin Hayre
Solutions Engineer
Voxeo Corporation

Come join us at our Voxeo Customer Summit, June 21st - June 23rd at the Hard Rock Hotel.
Register today for your [url=http://www.voxeo.com/summits/customer]All Access Pass[/url].

pampa

6/2/2010 3:00 PM (EDT)

Hey Dustin,

Before you post I followed 'bpcamac' instructions and got it to run.

This is the output:

# /opt/voxeo/prophecy start
Service 'Voxeo Prophecy Log Search' started in 4.6 seconds.
Service 'Voxeo Prophecy Log Indexer' started in 3.3 seconds.
Service 'Voxeo Prophecy Directory' started in 1.3 seconds.
Service 'Voxeo Prophecy Management Console' started in 36.4 seconds.
Service 'Voxeo Prophecy SIPMethod Server' started in 17.4 seconds.
Service 'Voxeo Prophecy Server' started in 1.3 seconds.
#

Now, another question arises: How can I access to manage it? In windows it was easy, but how can I access the server from my own LAN, with the server IP? Port(s)?

Thanks!

VoxeoDante

6/2/2010 4:22 PM (EDT)

Hello,

Yes, you should be able to access the server from you local lan via the server's IP address. The management console (Commander) should be running on port 9996.

I hope this answers your question.

Regards,
Dante Vitulano

Appendix C: Windows Specifics

| TOC

| Appendix E: OSX Specifics