Resources.Install History

Hide minor edits - Show changes to markup

April 24, 2013, at 12:04 PM by 109.99.235.212 -
Changed line 1 from:

(: redirect Documentation.Install quiet=1 :)

to:

(:redirect Documentation.Install quiet=1:)

April 24, 2013, at 12:04 PM by 109.99.235.212 -
Changed lines 1-149 from:

Resources -> Install


(:toc-float Table of Content:)

Looking for the fastest way for setting up your OpenSIPS instance?


OpenSIPS installation

Go for the OpenSIPS install instructions - this is a link directly to the INSTALL file from the SVN repository, which contains the up-to-date version.

The INSTALL file provides information about:

  1. . Supported Architectures and Requirements
  2. . Howto Build openser From Source Distribution
  3. . Quick-Start Installation Guide
    1. ) Getting Help
    2. ) Disclaimers
    3. ) Quick Start
    4. ) OpenSER with Persistent Data Storage
  4. . Troubleshooting

NOTE that the above file will help only for setting up OpenSIPS and not for how to configure or use it. If you are looking for such documentation, please see the Documentation section of the site.


OpenSIPS Console (osipsconsole) installation

osipsconsole is a console like utility for provisioning OpenSIPS. It is to replace opensipsctl and opensipsdbctl.

osipsconsole is available only starting with OpenSIPS version 1.5.0 .

Perl requirements

For the osipsconsole tool the following perl modules are needed:

  • DBI
  • DBD::mysql
  • DBD::Pg
  • DBD::Oracle
  • BerkeleyDB
  • Frontier::RPC2

Debian/Ubuntu Installation

In order for the script to work, there are listed bellow the modules needed and their debian package correspondent, a brief description of each package and whether it is mandatory to install it or not. ( To be mentioned the fact that these packages have been tested in Debian and Ubuntu distros. )

Perl moduleDebian PackageDescriptionUse
perlperlPractical Extraction and Report Languagemandatory
DBIlibdbi-perlPerl database interfacemandatory
DBD::mysqllibdbd-mysql-perlMySQL driver for the Perl5 Database Interface (DBI)*optional
DBD::Pglibdbd-pg-perlPostgreSQL database driver for the DBI module*optional
**DBD::Oracle Oracle database driver for the DBI module*optional
Frontier::RPC2libfrontier-rpc-perlencode/decode RPC2 format XMLmandatory
Term::ReadLine::Gnulibterm-readline-gnu-perlPerl extension for the GNU Readline/History Librarymandatory
BerkeleyDBlibberkeleydb-perlPerl extension for Berkeley DB version 2, 3 or 4mandatory

Install these packages using apt-get:

apt-get install perl libdbi-perl libdbd-mysql-perl libdbd-pg-perl libfrontier-rpc-perl libterm-readline-gnu-perl libberkeleydb-perl

NOTE: * at the user's choice. At least one of the packages is mandatory, depending on the DB type used by OpenSIPS. The other ones have no need of being installed.

**For the DBD::Oracle module there is no debian package. This will be installed as follows:
  • Download the .tar.gz archive from: http://search.cpan.org/~pythian/DBD-Oracle-1.22/Oracle.pm
  • Decompress and unpack it
  • cd DBD-Oracle-1.22
  • perl Makefile.PL
  • make
  • make test
  • make install
Creating your own Debian packages for CPAN libriaries

As many Debian users probably don't really like to install modules the CPAN way, here how to achieve the desired effect following "the Debian way":

 apt-get install dh-make-perl

Usually running

 dh-make-perl --build --cpan DBD-Whatever

should be enough. For CPAN libraries where this doesn't work please try as follows:

wget http://search.cpan.org/CPAN/.../DBD-Whatever-1.0.tar.gz
tar xfz DBD-Whatever-1.0.tar.gz
dh-make-perl DBD-Whatever-1.0/
cd DBD-Whatever-1.0

Adjust files in the newly created debian folder to fit your needs (if required) and build the package using dpkg-buildpackage, debuild or whatever you prefer.

 cd ..

Here is your new libdbd-whatever-perl_1.0-1_all.deb :-) One last suggestion: I'm usually not building packages on my live systems but elsewhere. This helps keeping productional systems slim and "clean".


Graphical Interface (menuconfig) installation

Menuconfig is a graphical tool that allows in an easy way to configure, compile and generate OpenSIPS configuration files - all by simply running

    make menuconfig

The Interface allows the user to do the following :

1. Configure OpenSIPS compilation related options such as :

    - Compilation Flags. For example, the user can now easily compile in TCP
      support from within the GUI, or enable memory allocation debugging, etc.
      Each compilation flag functionality is explained in short in the GUI.
    - Module Compilation Selection. The user can now easily select to compile
      modules that have external dependencies, and that are not compiled in
      by default. For example, the user can choose to also enable the MySQL
      support by enabling the db_mysql module. The interface will also notify
      the user about the dependencies that must be installed based on the modules
      that the user has selected.
    - Installation Prefix. The user can use the GUI to configure the OpenSIPS
      installation path to be used

2. Install OpenSIPS and Cleanup OpenSIPS sources

    - Upon configuring OpenSIPS related options from above,
      the user can choose to install OpenSIPS directly from the GUI.

3. Generate OpenSIPS config files

    - The tool can also generate OpenSIPS configuration files based on the-
      user's preferences. So far, we have defined three main classes of OpenSIPS
      configuration files :
        - Residential
        - Trunking
        - Load-balancer

   For each type of configuration file, the user can choose to enable/disable-
   certain options. For example, for the Residential script, the user can choose
   to enable presence support, to handle NAT, and many more. After the user has
   properly configured it's desired OpenSIPS script in the GUI, it will have the
   option to generate and obtain the final OpenSIPS cfg.

If you have installed OpenSIPS from packages ( debs, rpms, etc ) and not from sources, you will still be able to use the graphical interface for generating configuration files, by running

	osipsconfig
to:

(: redirect Documentation.Install quiet=1 :)

March 22, 2012, at 12:19 PM by vlad_paiu -
Changed lines 143-149 from:
   option to generate and obtain the final OpenSIPS cfg.
to:
   option to generate and obtain the final OpenSIPS cfg.

If you have installed OpenSIPS from packages ( debs, rpms, etc ) and not from sources, you will still be able to use the graphical interface for generating configuration files, by running

	osipsconfig
February 15, 2012, at 04:19 PM by 109.99.235.212 -
Changed lines 107-108 from:

Menuconfig is a graphical tool that allows in an easy way to configure, compile and generate OpenSIPS configuration files - all by simply running

to:

Menuconfig is a graphical tool that allows in an easy way to configure, compile and generate OpenSIPS configuration files - all by simply running

Changed lines 111-112 from:

Currently, the Interface allows the user to do the following :

to:

The Interface allows the user to do the following :

Changed lines 115-118 from:
    - Compilation Flags. For example, the user can now easily compile in TCP support from within the GUI, or enable memory allocation debugging, etc. Each compilation flag functionality is explained in short in the GUI.
    - Module Compilation Selection. The user can now easily select to compile modules that have external dependencies, and that are not compiled in by default. For example, the user can choose to also enable the MySQL support by enabling the db_mysql module. The interface will also notify the user about the dependencies that must be installed based on the modules that the user has selected.
    - Installation Prefix. The user can use the GUI to configure the OpenSIPS installation path to be used
to:
    - Compilation Flags. For example, the user can now easily compile in TCP
      support from within the GUI, or enable memory allocation debugging, etc.
      Each compilation flag functionality is explained in short in the GUI.
    - Module Compilation Selection. The user can now easily select to compile
      modules that have external dependencies, and that are not compiled in
      by default. For example, the user can choose to also enable the MySQL
      support by enabling the db_mysql module. The interface will also notify
      the user about the dependencies that must be installed based on the modules
      that the user has selected.
    - Installation Prefix. The user can use the GUI to configure the OpenSIPS
      installation path to be used
Changed lines 128-129 from:
    - Upon configuring OpenSIPS related options from above, the user can choose to install OpenSIPS directly from the GUI.
to:
    - Upon configuring OpenSIPS related options from above,
      the user can choose to install OpenSIPS directly from the GUI.
Changed lines 132-134 from:
    - The tool can also generate OpenSIPS configuration files based on the user's preferences. So far, we have defined three main classes of OpenSIPS configuration files :
to:
    - The tool can also generate OpenSIPS configuration files based on the-
      user's preferences. So far, we have defined three main classes of OpenSIPS
      configuration files :
Changed lines 139-143 from:

For each type of configuration file, the user can choose to enable/disable certain options. For example, for the Residential script, the user can choose to enable presence support, to handle NAT, and many more. After the user has properly configured it's desired OpenSIPS script in the GUI, it will have the option to generate and obtain the final OpenSIPS cfg.

The interface dependencies are

    - curses development library for compiling the GUI
    - m4 for generating OpenSIPS configs based on user preferences.
to:
   For each type of configuration file, the user can choose to enable/disable-
   certain options. For example, for the Residential script, the user can choose
   to enable presence support, to handle NAT, and many more. After the user has
   properly configured it's desired OpenSIPS script in the GUI, it will have the
   option to generate and obtain the final OpenSIPS cfg.
February 15, 2012, at 04:17 PM by 109.99.235.212 -
Added lines 106-130:

Menuconfig is a graphical tool that allows in an easy way to configure, compile and generate OpenSIPS configuration files - all by simply running

    make menuconfig

Currently, the Interface allows the user to do the following :

1. Configure OpenSIPS compilation related options such as :

    - Compilation Flags. For example, the user can now easily compile in TCP support from within the GUI, or enable memory allocation debugging, etc. Each compilation flag functionality is explained in short in the GUI.
    - Module Compilation Selection. The user can now easily select to compile modules that have external dependencies, and that are not compiled in by default. For example, the user can choose to also enable the MySQL support by enabling the db_mysql module. The interface will also notify the user about the dependencies that must be installed based on the modules that the user has selected.
    - Installation Prefix. The user can use the GUI to configure the OpenSIPS installation path to be used

2. Install OpenSIPS and Cleanup OpenSIPS sources

    - Upon configuring OpenSIPS related options from above, the user can choose to install OpenSIPS directly from the GUI.

3. Generate OpenSIPS config files

    - The tool can also generate OpenSIPS configuration files based on the user's preferences. So far, we have defined three main classes of OpenSIPS configuration files :
        - Residential
        - Trunking
        - Load-balancer

For each type of configuration file, the user can choose to enable/disable certain options. For example, for the Residential script, the user can choose to enable presence support, to handle NAT, and many more. After the user has properly configured it's desired OpenSIPS script in the GUI, it will have the option to generate and obtain the final OpenSIPS cfg.

The interface dependencies are

    - curses development library for compiling the GUI
    - m4 for generating OpenSIPS configs based on user preferences.
February 15, 2012, at 02:02 PM by vlad_paiu -
Changed line 105 from:

menuconfig installation

to:

Graphical Interface (menuconfig) installation

February 15, 2012, at 02:00 PM by vlad_paiu -
Changed lines 104-105 from:
to:

menuconfig installation

April 15, 2009, at 06:10 PM by Thomas -
Changed line 79 from:

Debian-like installation

to:
Creating your own Debian packages for CPAN libriaries
April 15, 2009, at 05:12 PM by Thomas -
Changed lines 92-93 from:

wget http://search.cpan.org/CPAN/.../DBD-Whatever-1.0.tar.gz

to:

wget http://search.cpan.org/CPAN/.../DBD-Whatever-1.0.tar.gz

April 15, 2009, at 05:09 PM by Thomas -
Changed lines 79-80 from:
to:

Debian-like installation

As many Debian users probably don't really like to install modules the CPAN way, here how to achieve the desired effect following "the Debian way":

 apt-get install dh-make-perl

Usually running

 dh-make-perl --build --cpan DBD-Whatever

should be enough. For CPAN libraries where this doesn't work please try as follows:

wget
http://search.cpan.org/CPAN/.../DBD-Whatever-1.0.tar.gz
tar xfz DBD-Whatever-1.0.tar.gz
dh-make-perl DBD-Whatever-1.0/
cd DBD-Whatever-1.0

Adjust files in the newly created debian folder to fit your needs (if required) and build the package using dpkg-buildpackage, debuild or whatever you prefer.

 cd ..

Here is your new libdbd-whatever-perl_1.0-1_all.deb :-) One last suggestion: I'm usually not building packages on my live systems but elsewhere. This helps keeping productional systems slim and "clean".

April 15, 2009, at 03:53 PM by iulia_bublea -
Changed lines 28-82 from:

OpenSIPS Console (osipconsole) installation

to:

OpenSIPS Console (osipsconsole) installation

osipsconsole is a console like utility for provisioning OpenSIPS. It is to replace opensipsctl and opensipsdbctl.

osipsconsole is available only starting with OpenSIPS version 1.5.0 .

Perl requirements

For the osipsconsole tool the following perl modules are needed:

  • DBI
  • DBD::mysql
  • DBD::Pg
  • DBD::Oracle
  • BerkeleyDB
  • Frontier::RPC2

Debian/Ubuntu Installation

In order for the script to work, there are listed bellow the modules needed and their debian package correspondent, a brief description of each package and whether it is mandatory to install it or not. ( To be mentioned the fact that these packages have been tested in Debian and Ubuntu distros. )

Perl moduleDebian PackageDescriptionUse
perlperlPractical Extraction and Report Languagemandatory
DBIlibdbi-perlPerl database interfacemandatory
DBD::mysqllibdbd-mysql-perlMySQL driver for the Perl5 Database Interface (DBI)*optional
DBD::Pglibdbd-pg-perlPostgreSQL database driver for the DBI module*optional
**DBD::Oracle Oracle database driver for the DBI module*optional
Frontier::RPC2libfrontier-rpc-perlencode/decode RPC2 format XMLmandatory
Term::ReadLine::Gnulibterm-readline-gnu-perlPerl extension for the GNU Readline/History Librarymandatory
BerkeleyDBlibberkeleydb-perlPerl extension for Berkeley DB version 2, 3 or 4mandatory

Install these packages using apt-get:

apt-get install perl libdbi-perl libdbd-mysql-perl libdbd-pg-perl libfrontier-rpc-perl libterm-readline-gnu-perl libberkeleydb-perl

NOTE: * at the user's choice. At least one of the packages is mandatory, depending on the DB type used by OpenSIPS. The other ones have no need of being installed.

**For the DBD::Oracle module there is no debian package. This will be installed as follows:
  • Download the .tar.gz archive from: http://search.cpan.org/~pythian/DBD-Oracle-1.22/Oracle.pm
  • Decompress and unpack it
  • cd DBD-Oracle-1.22
  • perl Makefile.PL
  • make
  • make test
  • make install
April 15, 2009, at 03:16 PM by iulia_bublea -
Changed lines 3-5 from:
to:

(:toc-float Table of Content:)

Changed line 28 from:

OpenSIPS Console (osipconsole) installation

to:

OpenSIPS Console (osipconsole) installation

April 15, 2009, at 03:15 PM by iulia_bublea -
Added lines 6-8:

OpenSIPS installation

Changed lines 25-26 from:
to:

OpenSIPS Console (osipconsole) installation

October 03, 2008, at 11:57 AM by 81.180.102.217 -
Changed lines 2-3 from:
to:

July 21, 2008, at 04:08 PM by 81.180.102.217 -
Added lines 1-2:

Resources -> Install

July 19, 2008, at 06:02 PM by 81.180.102.217 -
Changed lines 3-4 from:

Go for the OpenSIPS install instructions? - this is a link directly to the INSTALL file from the SVN repository, which contains the up-to-date version.

to:

Go for the OpenSIPS install instructions - this is a link directly to the INSTALL file from the SVN repository, which contains the up-to-date version.

July 19, 2008, at 05:59 PM by 81.180.102.217 -
Changed lines 3-5 from:

Table Of Contents

to:

Go for the OpenSIPS install instructions? - this is a link directly to the INSTALL file from the SVN repository, which contains the up-to-date version.

The INSTALL file provides information about:

Changed lines 17-19 from:
 To understand how OpenSER works and how to configure it properly, read admin's guide available from OpenSER website. We also urge you to read latest ISSUES (available from OpenSER website too) and check for potential problems in this release. Users of previous releases are encouraged to read NEWS to learn how to move to this new OpenSER version.
to:

NOTE that the above file will help only for setting up OpenSIPS and not for how to configure or use it. If you are looking for such documentation, please see the Documentation section of the site.

July 19, 2008, at 05:48 PM by 81.180.102.217 -
Added lines 1-18:

Looking for the fastest way for setting up your OpenSIPS instance?

Table Of Contents

  1. . Supported Architectures and Requirements
  2. . Howto Build openser From Source Distribution
  3. . Quick-Start Installation Guide
    1. ) Getting Help
    2. ) Disclaimers
    3. ) Quick Start
    4. ) OpenSER with Persistent Data Storage
  4. . Troubleshooting
    To understand how OpenSER works and how to configure it properly, read admin's guide available from OpenSER website. We also urge you to read latest ISSUES (available from OpenSER website too) and check for potential problems in this release. Users of previous releases are encouraged to read NEWS to learn how to move to this new OpenSER version.

Page last modified on April 24, 2013, at 12:04 PM