|
@@ -3,30 +3,30 @@ $Id$
|
|
|
|
|
|
===========================================
|
|
===========================================
|
|
|
|
|
|
- SIP Express Router (ser) Installation Notes
|
|
|
|
|
|
+ SIP Router (sip-router) Installation Notes
|
|
|
|
|
|
- http://www.iptel.org/ser/
|
|
|
|
|
|
+ http://sip-router.org
|
|
|
|
|
|
===========================================
|
|
===========================================
|
|
|
|
|
|
- This memo gives you hints how to set up SER quickly. To
|
|
|
|
- understand how SER works and how to configure it properly,
|
|
|
|
- read admin's guide available from SER website. We also
|
|
|
|
- urge you to read latest ISSUES (available from SER website
|
|
|
|
|
|
+ This memo gives you hints how to set up SIP Router quickly. To
|
|
|
|
+ understand how SIP Router works and how to configure it properly,
|
|
|
|
+ read admin's guide available from SIP Router website. We also
|
|
|
|
+ urge you to read latest ISSUES (available from SIP Router website
|
|
too) and check for potential problems in this release.
|
|
too) and check for potential problems in this release.
|
|
Users of previous releases are encouraged to read NEWS to
|
|
Users of previous releases are encouraged to read NEWS to
|
|
- learn how to move to this new SER version.
|
|
|
|
|
|
+ learn how to move to this new SIP Router version.
|
|
|
|
|
|
|
|
|
|
TOC
|
|
TOC
|
|
|
|
|
|
1. Supported Architectures and Requirements
|
|
1. Supported Architectures and Requirements
|
|
-2. Howto Build ser From Source Distribution
|
|
|
|
|
|
+2. Howto Build sip-router From Source Distribution
|
|
3. Quick-Start Installation Guide
|
|
3. Quick-Start Installation Guide
|
|
A) Getting Help
|
|
A) Getting Help
|
|
B) Disclaimers
|
|
B) Disclaimers
|
|
C) Quick Start
|
|
C) Quick Start
|
|
- D) ser with Persistent Data Storage
|
|
|
|
|
|
+ D) sip-router with Persistent Data Storage
|
|
4. Troubleshooting
|
|
4. Troubleshooting
|
|
|
|
|
|
|
|
|
|
@@ -35,10 +35,10 @@ TOC
|
|
-------------------------------------------
|
|
-------------------------------------------
|
|
|
|
|
|
Supported operating systems: Linux, FreeBSD, NetBSD, OpenBSD, Solaris, Darwin
|
|
Supported operating systems: Linux, FreeBSD, NetBSD, OpenBSD, Solaris, Darwin
|
|
-Partially supported: Windows+Cygwin (core + static modules only, no IPv6,
|
|
|
|
- no TCP, no dynamic modules)
|
|
|
|
|
|
+Partially supported: Windows+Cygwin (core + static modules only, no
|
|
|
|
+ IPv6, no TCP, no dynamic modules)
|
|
Supported architectures: i386, x86_64 (amd64), armv4l, sparc64, powerpc,
|
|
Supported architectures: i386, x86_64 (amd64), armv4l, sparc64, powerpc,
|
|
- powerpc64
|
|
|
|
|
|
+ powerpc64
|
|
Experimental architectures: mips1, mips2, sparc32, alpha
|
|
Experimental architectures: mips1, mips2, sparc32, alpha
|
|
|
|
|
|
(for other architectures the Makefiles might need to be edited)
|
|
(for other architectures the Makefiles might need to be edited)
|
|
@@ -53,7 +53,7 @@ Requirements:
|
|
- bison or yacc (Berkley yacc)
|
|
- bison or yacc (Berkley yacc)
|
|
- flex
|
|
- flex
|
|
- GNU make (on Linux this is the standard "make", on *BSD and Solaris is
|
|
- GNU make (on Linux this is the standard "make", on *BSD and Solaris is
|
|
- called "gmake") version >= 3.80 (recommended 3.81).
|
|
|
|
|
|
+ called "gmake") version >= 3.80 (recommended 3.81).
|
|
- sed and tr (used in the makefiles)
|
|
- sed and tr (used in the makefiles)
|
|
- GNU tar ("gtar" on Solaris) and gzip if you want "make tar" to work
|
|
- GNU tar ("gtar" on Solaris) and gzip if you want "make tar" to work
|
|
- GNU install, BSD install or Solaris install if you want "make
|
|
- GNU install, BSD install or Solaris install if you want "make
|
|
@@ -61,9 +61,9 @@ Requirements:
|
|
- libmysqlclient & libz (zlib) if you want mysql support (the mysql module)
|
|
- libmysqlclient & libz (zlib) if you want mysql support (the mysql module)
|
|
- libexpat if you want the jabber gateway support (the jabber module)
|
|
- libexpat if you want the jabber gateway support (the jabber module)
|
|
- libxml2 if you want to compile the cpl-c (CPL support) or pa (presence)
|
|
- libxml2 if you want to compile the cpl-c (CPL support) or pa (presence)
|
|
-modules
|
|
|
|
|
|
+ modules
|
|
- libradiusclient-ng (> 5.0) if you need radius support (the auth_radius,
|
|
- libradiusclient-ng (> 5.0) if you need radius support (the auth_radius,
|
|
-group_radius, uri_radius and avp_radius modules)
|
|
|
|
|
|
+ group_radius, uri_radius and avp_radius modules)
|
|
- libpq if you need postgres support (the postgres module)
|
|
- libpq if you need postgres support (the postgres module)
|
|
|
|
|
|
|
|
|
|
@@ -84,7 +84,7 @@ OS Notes:
|
|
NOTE: you'll need to add radiusclient_ng=4 to the gmake command line if you
|
|
NOTE: you'll need to add radiusclient_ng=4 to the gmake command line if you
|
|
use the 0.4.* version.
|
|
use the 0.4.* version.
|
|
|
|
|
|
- Compile example (all the modules and ser in a tar.gz):
|
|
|
|
|
|
+ Compile example (all the modules and sip-router in a tar.gz):
|
|
gmake bin radiusclient_ng=4 include_modules="mysql jabber cpl-c auth_radius group_radius uri_radius postgres pa"
|
|
gmake bin radiusclient_ng=4 include_modules="mysql jabber cpl-c auth_radius group_radius uri_radius postgres pa"
|
|
|
|
|
|
OpenBSD 3.7
|
|
OpenBSD 3.7
|
|
@@ -95,7 +95,7 @@ OS Notes:
|
|
http://download.berlios.de/radiusclient-ng/radiusclient-ng-0.5.1.tar.gz
|
|
http://download.berlios.de/radiusclient-ng/radiusclient-ng-0.5.1.tar.gz
|
|
(you need to download and install it, since there is no "official"
|
|
(you need to download and install it, since there is no "official"
|
|
openbsd port for it) for libradiusclient-ng
|
|
openbsd port for it) for libradiusclient-ng
|
|
- Compile example (all the modules and ser in a tar.gz):
|
|
|
|
|
|
+ Compile example (all the modules and sip-router in a tar.gz):
|
|
gmake bin include_modules="mysql jabber cpl-c auth_radius group_radius uri_radius pa"
|
|
gmake bin include_modules="mysql jabber cpl-c auth_radius group_radius uri_radius pa"
|
|
|
|
|
|
NetBSD 2.0
|
|
NetBSD 2.0
|
|
@@ -104,7 +104,7 @@ OS Notes:
|
|
- libxml2-2.6.19 (/usr/pkgsrc/textproc/libxml2) for libxml2
|
|
- libxml2-2.6.19 (/usr/pkgsrc/textproc/libxml2) for libxml2
|
|
- radiusclient-ng-0.5.1 (see OpenBSD)
|
|
- radiusclient-ng-0.5.1 (see OpenBSD)
|
|
|
|
|
|
- Compile example (all the modules and ser in a tar.gz):
|
|
|
|
|
|
+ Compile example (all the modules and sip-router in a tar.gz):
|
|
gmake bin include_modules="mysql jabber cpl-c auth_radius group_radius uri_radius pa"
|
|
gmake bin include_modules="mysql jabber cpl-c auth_radius group_radius uri_radius pa"
|
|
|
|
|
|
Solaris 10
|
|
Solaris 10
|
|
@@ -118,7 +118,7 @@ OS Notes:
|
|
Needed packages:
|
|
Needed packages:
|
|
[TODO]
|
|
[TODO]
|
|
|
|
|
|
- Compile example (all the modules and ser in a tar.gz):
|
|
|
|
|
|
+ Compile example (all the modules and sip-router in a tar.gz):
|
|
gmake bin INSTALL=install include_modules="mysql jabber cpl-c auth_radius group_radius uri_radius postgres pa"
|
|
gmake bin INSTALL=install include_modules="mysql jabber cpl-c auth_radius group_radius uri_radius postgres pa"
|
|
|
|
|
|
Linux
|
|
Linux
|
|
@@ -131,20 +131,21 @@ OS Notes:
|
|
- libxml2-dev for libxml2
|
|
- libxml2-dev for libxml2
|
|
- libradiusclient-ng-dev for libradiusclient (you can download the
|
|
- libradiusclient-ng-dev for libradiusclient (you can download the
|
|
package from http://apt.sip-router.org/debian/dists/unstable/main/binary-i386/libradiusclient-ng-dev_0.5.1-0.5_i386.deb ).
|
|
package from http://apt.sip-router.org/debian/dists/unstable/main/binary-i386/libradiusclient-ng-dev_0.5.1-0.5_i386.deb ).
|
|
- NOTE: you can get up-to-date ser packages or libradiusclient packages
|
|
|
|
|
|
+ NOTE: you can get up-to-date sip-router packages or libradiusclient packages
|
|
from http://apt.sip-router.org: add to your /etc/apt/sources.list the
|
|
from http://apt.sip-router.org: add to your /etc/apt/sources.list the
|
|
following lines:
|
|
following lines:
|
|
deb http://apt.sip-router.org/debian testing main contrib non-free
|
|
deb http://apt.sip-router.org/debian testing main contrib non-free
|
|
deb http://apt.sip-router.org/debian unstable main contrib non-free
|
|
deb http://apt.sip-router.org/debian unstable main contrib non-free
|
|
and then: apt-get update; apt-get install libradiusclient-ng-dev
|
|
and then: apt-get update; apt-get install libradiusclient-ng-dev
|
|
(or, if you want to use the pre-built modules:
|
|
(or, if you want to use the pre-built modules:
|
|
- apt-get install ser ser-cpl-module ser-jabber-module ser-mysq-module ser-pa-module ser-postgres-module ser-radius-modules )
|
|
|
|
|
|
+ apt-get install sip-router sip-router-cpl-module sip-router-jabber-module sip-router-mysq-module sip-router-pa-module sip-router-postgres-module sip-router-radius-modules )
|
|
|
|
|
|
Cygwin (alpha state, partial support)
|
|
Cygwin (alpha state, partial support)
|
|
|
|
|
|
- make sure make, bison, flex, minires and minires-devel (needed for the resolver functions) are installed.
|
|
|
|
|
|
+ make sure make, bison, flex, minires and minires-devel (needed for the
|
|
|
|
+ resolver functions) are installed.
|
|
|
|
|
|
- Only building ser's core and some static modules is supported for now.
|
|
|
|
|
|
+ Only building sip-router's core and some static modules is supported for now.
|
|
Stuff known not to work:
|
|
Stuff known not to work:
|
|
- IPv6 (cygwin doesn't support it yet)
|
|
- IPv6 (cygwin doesn't support it yet)
|
|
- TCP (the tcp code heavily depends on file descriptor passing
|
|
- TCP (the tcp code heavily depends on file descriptor passing
|
|
@@ -153,20 +154,21 @@ OS Notes:
|
|
backlinking doesn't work in windows by design)
|
|
backlinking doesn't work in windows by design)
|
|
|
|
|
|
|
|
|
|
- Compile example (all the modules and ser in a tar.gz):
|
|
|
|
|
|
+ Compile example (all the modules and sip-router in a tar.gz):
|
|
make bin include_modules="mysql jabber cpl-c auth_radius group_radius uri_radius postgres pa"
|
|
make bin include_modules="mysql jabber cpl-c auth_radius group_radius uri_radius postgres pa"
|
|
|
|
|
|
|
|
|
|
-2. Howto Build ser From Source Distribution
|
|
|
|
|
|
+2. Howto Build sip-router From Source Distribution
|
|
-------------------------------------------
|
|
-------------------------------------------
|
|
|
|
|
|
(NOTE: if make doesn't work try gmake instead)
|
|
(NOTE: if make doesn't work try gmake instead)
|
|
|
|
|
|
-SER is split in four main parts: The core, the modules, the utilties, and scripts/examples
|
|
|
|
-When you build, you can decide to build only the core, the modules, both, or all.
|
|
|
|
|
|
+SIP Router is split in four main parts: The core, the modules, the
|
|
|
|
+utilties, and scripts/examples. When you build, you can decide to build
|
|
|
|
+only the core, the modules, both, or all.
|
|
|
|
|
|
-Compile SER core only:
|
|
|
|
-make #builds only ser core, equivalent to make ser
|
|
|
|
|
|
+Compile SIP Router core only:
|
|
|
|
+make #builds only sip-router core, equivalent to make sip-router
|
|
|
|
|
|
Compile modules except some explicitly excepted (see below)
|
|
Compile modules except some explicitly excepted (see below)
|
|
make modules
|
|
make modules
|
|
@@ -183,11 +185,11 @@ avp_radius, postgres, pa.
|
|
Including groups of modules (available in >0.9.x):
|
|
Including groups of modules (available in >0.9.x):
|
|
Instead of compiling the default modules only, you can specify groups of
|
|
Instead of compiling the default modules only, you can specify groups of
|
|
modules to include, according to their status:
|
|
modules to include, according to their status:
|
|
-standard - Modules in this group are considered a standard part of SER (due to widespread usage)
|
|
|
|
|
|
+standard - Modules in this group are considered a standard part of SIP Router (due to widespread usage)
|
|
but they have no dependencies (note that some of these interplay with external systems.
|
|
but they have no dependencies (note that some of these interplay with external systems.
|
|
However, they don't have compile or link dependencies).
|
|
However, they don't have compile or link dependencies).
|
|
|
|
|
|
-standard-dep - Modules in this group are considered a standard part of SER (due to widespread usage)
|
|
|
|
|
|
+standard-dep - Modules in this group are considered a standard part of SIP Router (due to widespread usage)
|
|
but they have dependencies that most be satisfied for compilation.
|
|
but they have dependencies that most be satisfied for compilation.
|
|
NOTE! All presence modules (dialog, pa, presence_b2b, rls, xcap) have been included in this
|
|
NOTE! All presence modules (dialog, pa, presence_b2b, rls, xcap) have been included in this
|
|
group due to interdependencies
|
|
group due to interdependencies
|
|
@@ -224,14 +226,18 @@ You can also explicitly skip modules using skip_modules. Let's say you want all
|
|
and standard-dep modules except domain:
|
|
and standard-dep modules except domain:
|
|
make group_include="standard standard-dep" skip_modules="domain" all
|
|
make group_include="standard standard-dep" skip_modules="domain" all
|
|
|
|
|
|
-NOTE!!! As this mechanism is very powerful, you may be uncertain which modules wwill be included.
|
|
|
|
-Just replace all (or modules) with print-modules and you will see which modules will be included
|
|
|
|
-and excluded, ex:
|
|
|
|
|
|
+NOTE!!! As this mechanism is very powerful, you may be uncertain which
|
|
|
|
+modules wwill be included.
|
|
|
|
+Just replace all (or modules) with print-modules and you will see which
|
|
|
|
+modules will be included and excluded, ex:
|
|
|
|
+
|
|
make print-modules
|
|
make print-modules
|
|
|
|
+
|
|
will show which modules are excluded by default.
|
|
will show which modules are excluded by default.
|
|
|
|
|
|
-If you want to install or to build a binary package (a tar.gz with ser and
|
|
|
|
- the modules), substitute "all" in the above command with "install" or "bin".
|
|
|
|
|
|
+If you want to install or to build a binary package (a tar.gz with
|
|
|
|
+sip-router and the modules), substitute "all" in the above command with
|
|
|
|
+"install" or "bin".
|
|
|
|
|
|
|
|
|
|
More compile examples:
|
|
More compile examples:
|
|
@@ -421,22 +427,23 @@ make prefix=/usr/local install
|
|
|
|
|
|
Note: If you use prefix parameter in make install then you also need
|
|
Note: If you use prefix parameter in make install then you also need
|
|
to use this parameter in previous make commands, i.e. make, make modules,
|
|
to use this parameter in previous make commands, i.e. make, make modules,
|
|
-or make all. If you fail to do this then SER will look for the default
|
|
|
|
|
|
+or make all. If you fail to do this then SIP Router will look for the default
|
|
configuration file in a wrong directory, because the directory of the
|
|
configuration file in a wrong directory, because the directory of the
|
|
-default configuration file is hard coded into ser during compile time.
|
|
|
|
|
|
+default configuration file is hard coded into sip-router during compile time.
|
|
When you use a different prefix parameter when installing then the
|
|
When you use a different prefix parameter when installing then the
|
|
-directory hard coded in ser and the directory in which the file will be
|
|
|
|
|
|
+directory hard coded in sip-router and the directory in which the file will be
|
|
installed by make install will not match. (You can specify exact location
|
|
installed by make install will not match. (You can specify exact location
|
|
-of the configuration file using -f parameter of ser).
|
|
|
|
|
|
+of the configuration file using -f parameter of sip-router).
|
|
|
|
|
|
For example, if you do the following:
|
|
For example, if you do the following:
|
|
make all
|
|
make all
|
|
make prefix=/ install
|
|
make prefix=/ install
|
|
|
|
|
|
Then the installation will put the default configuration file into
|
|
Then the installation will put the default configuration file into
|
|
-/etc/ser/ser.cfg (because prefix is /), but ser will look for the file
|
|
|
|
-in /usr/local/etc/ser/ser.cfg (because there was no prefix parameter
|
|
|
|
-in make all and /usr/local is the default value of prefix).
|
|
|
|
|
|
+/etc/sip-router/sip-router.cfg (because prefix is /), but sip-router
|
|
|
|
+will look for the file in /usr/local/etc/sip-router/sip-router.cfg
|
|
|
|
+(because there was no prefix parameter make all and /usr/local is the
|
|
|
|
+default value of prefix).
|
|
|
|
|
|
Workaround is trivial, use the same parameters in all make commands:
|
|
Workaround is trivial, use the same parameters in all make commands:
|
|
make prefix=/ all
|
|
make prefix=/ all
|
|
@@ -452,17 +459,18 @@ That applies to other make parameters as well (for example parameters
|
|
|
|
|
|
A) Getting Help
|
|
A) Getting Help
|
|
|
|
|
|
-This guide gives you instructions on how to set up the SIP Express
|
|
|
|
-Router (ser) on your box quickly. In case the default configuration
|
|
|
|
-does not fly, check documentation at ser site
|
|
|
|
- http://www.iptel.org/ser/
|
|
|
|
-to learn how to configure SER for your site.
|
|
|
|
|
|
+This guide gives you instructions on how to set up the SIP Router
|
|
|
|
+(sip-router) on your box quickly. In case the default configuration
|
|
|
|
+does not fly, check documentation at sip-router site
|
|
|
|
+ http://sip-router.org
|
|
|
|
+to learn how to configure SIP Router for your site.
|
|
|
|
|
|
If the documentation does not resolve your problem you may try contacting
|
|
If the documentation does not resolve your problem you may try contacting
|
|
-our user forum by E-mail at [email protected] -- that is the mailing
|
|
|
|
-list of ser community. To participate in the mailing list, subscribe at the
|
|
|
|
-following web address:
|
|
|
|
- http://lists.iptel.org/mailman/listinfo/serusers
|
|
|
|
|
|
+our user forum by E-mail at [email protected] -- that is the
|
|
|
|
+mailing list of ser community. To participate in the mailing list,
|
|
|
|
+subscribe at the following web address:
|
|
|
|
+
|
|
|
|
+ http://lists.sip-router.org/cgi-bin/mailman/listinfo
|
|
|
|
|
|
To participate in our commercial support program, contact [email protected].
|
|
To participate in our commercial support program, contact [email protected].
|
|
The support program will provide you with most timely and accurate help
|
|
The support program will provide you with most timely and accurate help
|
|
@@ -482,14 +490,19 @@ dependencies on MySQL which is needed for storing user credentials.)
|
|
C) Quick Start
|
|
C) Quick Start
|
|
|
|
|
|
The following step-by step guide gives you instructions how to install the
|
|
The following step-by step guide gives you instructions how to install the
|
|
-sql-free distribution of ser. If you need persistence and authentication,
|
|
|
|
-then you have to install additional MySql support -- proceed to section D)
|
|
|
|
-after you are finished with C).
|
|
|
|
-
|
|
|
|
-1) Download an RPM or debian package from our site
|
|
|
|
- http://www.iptel.org/ser
|
|
|
|
-If you don't use an rpm or debian based distribution, try our tar.gz'ed binaries
|
|
|
|
- (ser-$(version)_$(os)_$(arch).tar.gz, e.g: ser-0.8.8_linux_i386.tar.gz).
|
|
|
|
|
|
+sql-free distribution of sip-router. If you need persistence and
|
|
|
|
+authentication, then you have to install additional MySql support --
|
|
|
|
+proceed to section D) after you are finished with C).
|
|
|
|
+
|
|
|
|
+1) Download an RPM or debian package from site
|
|
|
|
+
|
|
|
|
+ ****** site not available yet
|
|
|
|
+
|
|
|
|
+If you don't use an rpm or debian based distribution, try our tar.gz'ed
|
|
|
|
+binaries
|
|
|
|
+
|
|
|
|
+ ******* not available yet
|
|
|
|
+
|
|
If you use Solaris 8 you can try our solaris package.
|
|
If you use Solaris 8 you can try our solaris package.
|
|
If you use Gentoo Linux you do not have to download a package.
|
|
If you use Gentoo Linux you do not have to download a package.
|
|
|
|
|
|
@@ -499,13 +512,13 @@ RPM:
|
|
debian:
|
|
debian:
|
|
dpkg -i <package_name>
|
|
dpkg -i <package_name>
|
|
gentoo:
|
|
gentoo:
|
|
- emerge ser
|
|
|
|
|
|
+ emerge sip-router
|
|
(or if use only stable packets:
|
|
(or if use only stable packets:
|
|
- ACCEPT_KEYWORDS="~x86" emerge ser)
|
|
|
|
|
|
+ ACCEPT_KEYWORDS="~x86" emerge sip-router)
|
|
tar.gz:
|
|
tar.gz:
|
|
cd /; tar zxvf <package_name>_os_arch.tar.gz
|
|
cd /; tar zxvf <package_name>_os_arch.tar.gz
|
|
(it will install in /usr/local/, and the configuration file in
|
|
(it will install in /usr/local/, and the configuration file in
|
|
- /usr/local/etc/ser/ser.cfg)
|
|
|
|
|
|
+ /usr/local/etc/sip-router/sip-router.cfg)
|
|
Solaris:
|
|
Solaris:
|
|
gunzip <package_name>.gz ; pkgadd -d <package_name>
|
|
gunzip <package_name>.gz ; pkgadd -d <package_name>
|
|
*BSD:
|
|
*BSD:
|
|
@@ -513,15 +526,15 @@ Solaris:
|
|
|
|
|
|
3) start the server
|
|
3) start the server
|
|
RPM + gentoo:
|
|
RPM + gentoo:
|
|
- /etc/init.d/ser start
|
|
|
|
|
|
+ /etc/init.d/sip-router start
|
|
debian:
|
|
debian:
|
|
- ser is started automatically after the install
|
|
|
|
- (in case something fails you can start it with /etc/init.d/ser start)
|
|
|
|
|
|
+ sip-router is started automatically after the install
|
|
|
|
+ (in case something fails you can start it with /etc/init.d/sip-router start)
|
|
tar.gz:
|
|
tar.gz:
|
|
the tar.gz does not include an init.d script, you'll have to create one of
|
|
the tar.gz does not include an init.d script, you'll have to create one of
|
|
your own or adapt one from the source distribution (debian/init.d,
|
|
your own or adapt one from the source distribution (debian/init.d,
|
|
- rpm/ser.init.*, gentoo/ser.init)
|
|
|
|
- You can start ser directly with /usr/local/sbin/ser.
|
|
|
|
|
|
+ rpm/sip-router.init.*, gentoo/sip-router.init)
|
|
|
|
+ You can start sip-router directly with /usr/local/sbin/sip-router.
|
|
Solaris:
|
|
Solaris:
|
|
see tar.gz.
|
|
see tar.gz.
|
|
|
|
|
|
@@ -552,20 +565,23 @@ Solaris:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-D) ser with Persistent Data Storage
|
|
|
|
|
|
+D) sip-router with Persistent Data Storage
|
|
|
|
|
|
The default configuration is very simple and features many simplifications.
|
|
The default configuration is very simple and features many simplifications.
|
|
In particular, it does not authenticate users and loses User Location database
|
|
In particular, it does not authenticate users and loses User Location database
|
|
on reboot. To provide persistence, keep user credentials and remember users'
|
|
on reboot. To provide persistence, keep user credentials and remember users'
|
|
-locations across reboots, ser can be configured to use MySQL. Before you proceed,
|
|
|
|
-you need to make sure MySQL is installed on your box. Your MySQL server must be
|
|
|
|
-configured to deal with a large number of connection. To increase it, set the
|
|
|
|
-following line in [mysqld] section of your configuration file:
|
|
|
|
|
|
+locations across reboots, ser can be configured to use MySQL. Before you
|
|
|
|
+proceed, you need to make sure MySQL is installed on your box. Your
|
|
|
|
+MySQL server must be configured to deal with a large number of
|
|
|
|
+connection. To increase it, set the following line in [mysqld] section
|
|
|
|
+of your configuration file:
|
|
|
|
|
|
set-variable = max_connections=500
|
|
set-variable = max_connections=500
|
|
|
|
|
|
-1) Download the package containing mysql support for ser from:
|
|
|
|
- http://www.iptel.org/ser/
|
|
|
|
|
|
+1) Download the package containing mysql support for sip-router from:
|
|
|
|
+
|
|
|
|
+ **** site not available yet
|
|
|
|
+
|
|
(rpm and deb provided, most of the binary tar.gz distributions and the
|
|
(rpm and deb provided, most of the binary tar.gz distributions and the
|
|
solaris package include it; if it is not present you'll have to rebuild
|
|
solaris package include it; if it is not present you'll have to rebuild
|
|
from the source).
|
|
from the source).
|
|
@@ -576,23 +592,23 @@ following line in [mysqld] section of your configuration file:
|
|
or
|
|
or
|
|
dpkg -i <package_name>
|
|
dpkg -i <package_name>
|
|
or
|
|
or
|
|
- emerge ser
|
|
|
|
|
|
+ emerge sip-router
|
|
(if do not want to put 'mysql' into your USE variable you can type:
|
|
(if do not want to put 'mysql' into your USE variable you can type:
|
|
- USE="mysql" emerge ser)
|
|
|
|
|
|
+ USE="mysql" emerge sip-router)
|
|
3) create MySQL tables
|
|
3) create MySQL tables
|
|
- - if you have a previously installed SER on your system, use
|
|
|
|
- /usr/sbin/ser_mysql.sh reinstall
|
|
|
|
- to convert your SER database into new structures
|
|
|
|
|
|
+ - if you have a previously installed SIP Router on your system, use
|
|
|
|
+ /usr/sbin/sip-router_mysql.sh reinstall
|
|
|
|
+ to convert your SIP Router database into new structures
|
|
- otherwise, if this is your very first installation, use
|
|
- otherwise, if this is your very first installation, use
|
|
- /usr/sbin/ser_mysql.sh create
|
|
|
|
- to create SER database structures
|
|
|
|
|
|
+ /usr/sbin/sip-router_mysql.sh create
|
|
|
|
+ to create SIP Router database structures
|
|
(you will be prompted for password of MySql "root" user)
|
|
(you will be prompted for password of MySql "root" user)
|
|
-4) configure ser to use SQL
|
|
|
|
- uncomment all lines in configuration file ser.cfg which are related to
|
|
|
|
|
|
+4) configure sip-router to use SQL
|
|
|
|
+ uncomment all lines in configuration file sip-router.cfg which are related to
|
|
authentication:
|
|
authentication:
|
|
- - loadmodule "/usr/lib/ser/modules/mysql.so"
|
|
|
|
- - loadmodule "/usr/lib/ser/modules/auth.so"
|
|
|
|
- - loadmodule "/usr/lib/ser/modules/auth_db.so"
|
|
|
|
|
|
+ - loadmodule "/usr/lib/sip-router/modules/mysql.so"
|
|
|
|
+ - loadmodule "/usr/lib/sip-router/modules/auth.so"
|
|
|
|
+ - loadmodule "/usr/lib/sip-router/modules/auth_db.so"
|
|
- modparam("usrloc", "db_mode", 2)
|
|
- modparam("usrloc", "db_mode", 2)
|
|
- modparam("auth", "calculate_ha1", yes)
|
|
- modparam("auth", "calculate_ha1", yes)
|
|
- modparam("auth_db", "password_column", "password")
|
|
- modparam("auth_db", "password_column", "password")
|
|
@@ -609,7 +625,7 @@ following line in [mysqld] section of your configuration file:
|
|
break;
|
|
break;
|
|
}
|
|
}
|
|
6) restart the server
|
|
6) restart the server
|
|
- /etc/init.d/ser restart
|
|
|
|
|
|
+ /etc/init.d/sip-router restart
|
|
7) you can now start managing the server using the serctl utility;
|
|
7) you can now start managing the server using the serctl utility;
|
|
you need to first set the environment variable SIP_DOMAIN to your
|
|
you need to first set the environment variable SIP_DOMAIN to your
|
|
local SIP realm, e.g.,
|
|
local SIP realm, e.g.,
|
|
@@ -633,17 +649,19 @@ challenged request at all and pops up authentication window again. If you
|
|
want to authenticate WM, you need to set up your realm value to equal server
|
|
want to authenticate WM, you need to set up your realm value to equal server
|
|
name. If your server has no name, IP address can be used as realm too.
|
|
name. If your server has no name, IP address can be used as realm too.
|
|
|
|
|
|
-Q: SIP requests are replied by ser with "483 Too Many Hops" or
|
|
|
|
|
|
+Q: SIP requests are replied by sip-router with "483 Too Many Hops" or
|
|
"513 Message Too Large"
|
|
"513 Message Too Large"
|
|
|
|
|
|
A: In both cases, the reason is probably an error in request routing script
|
|
A: In both cases, the reason is probably an error in request routing script
|
|
which caused an infinite loop. You can easily verify whether this happens
|
|
which caused an infinite loop. You can easily verify whether this happens
|
|
- by watching SIP traffic on loopback interface. A typical reason for misrouting
|
|
|
|
- is a failure to match local domain correctly. If a server fails to recognize
|
|
|
|
- a request for itself, it will try to forward it to current URI in believe it
|
|
|
|
- would forward them to a foreign domain. Alas, it forwards the request to itself
|
|
|
|
- again. This continues to happen until value of max_forwards header field reaches
|
|
|
|
- zero or the request grows too big. Solutions is easy: make sure that domain matching
|
|
|
|
- is correctly configured. A quick way to achieve that is to introduce a config
|
|
|
|
- option to ser.cfg: alias=domainname, where domainname shall be replaced with
|
|
|
|
- name of domain, which you wish to server and which appears in request-URIs.
|
|
|
|
|
|
+ by watching SIP traffic on loopback interface. A typical reason for
|
|
|
|
+ misrouting is a failure to match local domain correctly. If a server
|
|
|
|
+ fails to recognize a request for itself, it will try to forward it to
|
|
|
|
+ current URI in believe it would forward them to a foreign
|
|
|
|
+ domain. Alas, it forwards the request to itself again. This continues
|
|
|
|
+ to happen until value of max_forwards header field reaches zero or
|
|
|
|
+ the request grows too big. Solutions is easy: make sure that domain
|
|
|
|
+ matching is correctly configured. A quick way to achieve that is to
|
|
|
|
+ introduce a config option to sip-router.cfg: alias=domainname, where
|
|
|
|
+ domainname shall be replaced with name of domain, which you wish to
|
|
|
|
+ server and which appears in request-URIs.
|