This file was generated using the following command. If you are already looking at this from a web browser, then please ignore this message. cd doc;ant text-doc ----------------------------------------------------------
These instructions apply to Enterprise and Fedora systems unless explicitly noted
Common to all Fedora systems, you need to add the following packages:
yum install tftp-server httpd postgresql-server
Redhat enterprise:
yum install tftp-server httpd rh-postgresql-server
You can add jpackage to your yum repository as follows (see http://www.mksearch.mkdoc.org/howto/jpackage-fc3/ for more information.)
Remove previous ant if you have it installedrpm -e apache-antNow setup yum
wget -P /tmp http://jpackage.org/jpackage.asc
rpm --import /tmp/jpackage.asc
wget -P /etc/yum.repos.d http://jpackage.org/jpackage.repo
Now you can update your system to the required packages
yum install ant ant-nodeps junit ant-junit checkstyle checkstyle-optional ant-trax jakarta-commons-beanutils jakarta-commons-collections
Although you can get RPMs from JPacakge, SIPfoundy has an RPM will all the necesary tools you'll need. NOTE: This will also work on FC3 if you run into trouble with using JPackage
wget http://www.sipfoundry.org/pub/sipX/depends/FC/2/apache-ant-1.6.2-2.noarch.rpm
rpm -ivh apache-ant-1.6.2-2.noarch.rpm
Download and install the following RPMs from http://www.sipfoundry.org/pub/sipX/
Install the following software packages. Follow the installation instructions for your OS. If there is any special installation instructions, they will be noted.
Set the following environment variables:
sipx-config --jdk
is used
to find java dynamically. That means you can upgrade your java
and not break your installation
Example:
export JAVA_HOME=/usr/java/j2sdk1.4.2_03
Example:
export ANT_HOME=/opt/apache-ant-1.6.2
Example:
export JBOSS_HOME=/opt/jboss-4.0.1
If you've obtained your source from subversion, and not from a tar file, run this command:
autoreconf -if
Now compile and install sipXconfig by running this command:
./configure
make
make install
If you've installed JBoss from the RPM found on sipfoundry website then add user 'sipx' (or user defined SIPXPBXUSER) to the jboss user group and skip the next few steps about patching JBoss and skip to setting up your database
JBoss 4.0 is distributed with several server configurations. They are located under $JBOSS_HOME/server directory. By default sipXconfig components will run under "default" configuration. One can change it by creating a custom configuration:
cp -rp $JBOSS_HOME/server/default $JBOSS_HOME/server/sipx
export env JBOSS_SERVER_CONF=sipx
Standard JBoss installation needs to be patched to use Postgres database and to enable sipX provided authentication modules.
patch -d ${JBOSS_HOME}/server/${JBOSS_SERVER_CONF} -p0 < meta/sipx-jboss4-configure.patchIf you use custom JBoss server configuration use its name instead of
default. Every configuration has to be patched separately.
rm -rf ${JBOSS_HOME}/server/${JBOSS_SERVER_CONF}/deploy/jboss-hibernate.deployerHibernate 2.1 required by sipXconfig is included in the source distribution.
cp meta/ssl.pkcs12 ${JBOSS_HOME}/server/${JBOSS_SERVER_CONF}/conf
${JBOSS_HOME}
If you are runnning sipXconfig 2.6.x (or older) on the same machine as version 2.7 you have to reconfigure your JBOSS_HOME every time you switch between 2.6 and 2.7.
Postgres needs to always be running on your system. If you've installed sipXconfig from RPM, you shouldn't have to do this.
To start Postgres on Redhat 9 or Fedora systems run this command.
service postgresql start
To start Postgres on Enterprise 3 systems run this command.
service rhdb start
To start Postgres on Debian, and perhaps other linux distributions, if you don't already have a /etc/init.d/postgresql you may need to get the example from the contrib directory in the postgres distibution:
cp contrib/start-scripts/linux /etc/init.d/postgresql
It's recommended you should have Postgres start automatically when your machine restarts (usually in runlevels 3 and 5).
Fedora and Redhat 9 users should run this command:
chkconfig postgresql on
Redhat Enterprise 3 users should run this command:
chkconfig rhdb on
Edit Postgres config files to work. This will open up TCP connections and allow localhost to connect to Postgres
/usr/local/sipx/bin/sipxdbmgr --setup
/usr/local/sipx/bin/sipxdbmgr --create PDS
/usr/local/sipx/bin/sipxdbmgr --create SDS
Run the following commands
${EDITOR} /etc/xinetd.d/tftp
make the following edits, if you've installed via
RPM, then {where you installed sipXconfig}
is empty:
disable = no
server_args = -s {where you installed sipXconfig}/var/sipxdata/configserver/phone/profile/tftproot
Run the following commands for your edits to take affect
# ensure tftp server is not already running
ps aux | grep tftp
# if so, stop it
kill -15 {tftp pid}
# restart xinit.d that in turn will start tftp on demand
service xinetd restart
Run the following commands
emerge net-misc/tftp-hpa
${EDITOR} /etc/conf.d/in.tftpd
make the following edits
INTFTPD_PATH="{where you installed sipXconfig}/var/sipxdata/configserver/phone/profile/tftproot"
then run the following command
/etc/init.d/in.tftp start
Set up an SSL key using the instructions in sipXcommserverLib/doc/INSTALL.ssl or /usr/share/doc/sipxcommserverlib-version/INSTALL.ssl.
This is the normal configuration. It's where all the sipx servers
like the proxy, status server, mediaserver, etc. are running on the
same machine. In this case you will want to follow the instructions in
the sipXpbx project for starting the sipxpbx
service.
This will control the starting and stopping of the necessary
components of the configuration system. The sipXproxy will direct SIP
messages to the Profile Publisher automatically. If you are using
another SIP proxy other than the sipXproxy, or running the sipXproxy on
another machine, follow next section "Running Standalone".
This is when you are running just the sipXconfig server on one machine. You can follow the instructions for running with all the other sipX servers after making the following configurations changes:
etc/sipxpbx/config.defs
and set following setting
to read the following values:
CONFIG_SERVER_SIP_PORT=5060
etc/sipxpbx/ProcessDefinitions.xml
and remove sections
<group name="CommServer" >
...
</group>
<group name="MediaServer" >
...
</group>
Currently there is no support for windows but here is a list of steps towards supporting Windows. Please submit your findings and patches back to mailing list
config.properties.in
and replace all variables
with @VAR@
symbol with where you have dependencies
installedant
then ant install
on all the
build.xml
files in these directories and in this
order:
First, see the INSTALL instructions in sipXportLib on adding glib and pcre to the MSVC 6 environment. Next, you must add Java's JNI include and library paths to your MSVC 6 environment following the same process.
Assuming that you installed the SDK in C:\Program
Files\Java\j2sdk1.4.2_03
you will need to add the
following: