sr-dev

sr-dev@lists.kamailio.org

15 participants
44233 discussions

by Olle E. Johansson

There's a mix of commands that will look very confusing kamctrl kamdbctrl sercmd We need to clean this up for release - regardless of distribution. The README files points to all kind of names, include openserctl. Just a note and a suggestion. /O

15 years, 3 months

git:master: Starting conversion of tm module to doxygen documentation

by Olle E. Johansson

Module: sip-router Branch: master Commit: 43b929cb48fecfd80b63a055412ef439a0a76e47 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=43b929c… Author: oej <oej(a)edvina.net> Committer: oej <oej(a)edvina.net> Date: Sat Oct 10 22:07:11 2009 +0200 Starting conversion of tm module to doxygen documentation - including Jiri's memorial in doxygen docs. --- modules/tm/callid.c | 17 +++++++------ modules/tm/callid.h | 18 ++++++++------ modules/tm/config.c | 18 ++++++++------ modules/tm/config.h | 17 +++++++------ modules/tm/defs.h | 17 +++++++------ modules/tm/dlg.c | 17 +++++++------ modules/tm/dlg.h | 18 ++++++++------ modules/tm/h_table.c | 17 +++++++------ modules/tm/h_table.h | 18 ++++++++------ modules/tm/tm.c | 63 +++++++++++++++++++++++++++++++++++++++++++------ 10 files changed, 140 insertions(+), 80 deletions(-) Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=43b…

15 years, 3 months

git:master: Documentation update

by Olle E. Johansson

Module: sip-router Branch: master Commit: 85da6c04c445ee052241d5992de485a546e73fd3 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=85da6c0… Author: oej <oej(a)edvina.net> Committer: oej <oej(a)edvina.net> Date: Sat Oct 10 21:40:38 2009 +0200 Documentation update --- modules/db_berkeley/README | 520 +++++++++++++------------ modules/db_berkeley/bdb_cmd.c | 16 +- modules/db_berkeley/bdb_cmd.h | 13 +- modules/db_berkeley/bdb_con.c | 10 +- modules/db_berkeley/bdb_con.h | 14 +- modules/db_berkeley/bdb_fld.c | 10 +- modules/db_berkeley/bdb_fld.h | 13 +- modules/db_berkeley/bdb_lib.c | 13 +- modules/db_berkeley/bdb_lib.h | 13 +- modules/db_berkeley/bdb_mod.c | 13 +- modules/db_berkeley/bdb_mod.h | 13 +- modules/db_berkeley/bdb_res.c | 18 +- modules/db_berkeley/bdb_res.h | 18 +- modules/db_berkeley/bdb_uri.c | 15 +- modules/db_berkeley/bdb_uri.h | 21 +- modules/db_berkeley/doc/db_berkeley_admin.xml | 26 +- modules/db_berkeley/km_bdb_lib.c | 13 +- modules/db_berkeley/km_bdb_lib.h | 13 +- modules/db_berkeley/km_bdb_mi.c | 13 +- modules/db_berkeley/km_bdb_mi.h | 12 +- modules/db_berkeley/km_bdb_res.c | 13 +- modules/db_berkeley/km_bdb_res.h | 12 +- modules/db_berkeley/km_bdb_util.c | 13 +- modules/db_berkeley/km_bdb_util.h | 12 +- modules/db_berkeley/km_bdb_val.c | 12 +- modules/db_berkeley/km_bdb_val.h | 12 +- modules/db_berkeley/km_db_berkeley.c | 13 +- modules/db_berkeley/km_db_berkeley.h | 11 +- 28 files changed, 518 insertions(+), 377 deletions(-) Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=85d…

15 years, 3 months

README-MODULES intro (please review)

by Olle E. Johansson

SIP-ROUTER modules ================== This is the first release of the combined project. In order to be able to support an upgrade path for both Kamailio/OpenSER and SER current users, we have been forced to provide some modules in two versions, which means that we have three set of modules: - modules: the SIP router modules - modules_k: Kamailio modules - modules_s: SER modules All modules are compatible with the core, so regardless if you are a new user or an existing, you are free to make a choice between the three sets. Note that if you are currently using one product, you want to select the module that exists in the K/S directories first to get a smooth upgrade path. As sip-router development progress, we will move as many modules as possible into the core and only keep k/s modules for backwards compatibility when required.

15 years, 3 months

git:master: Add Juha's clarification

by Olle E. Johansson

Module: sip-router Branch: master Commit: bf33ef069bb4a6bae03d4fff101cb993757428b0 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=bf33ef0… Author: oej <oej(a)edvina.net> Committer: oej <oej(a)edvina.net> Date: Sat Oct 10 17:51:30 2009 +0200 Add Juha's clarification --- README-MODULES | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/README-MODULES b/README-MODULES index 358ada1..c61cfdc 100644 --- a/README-MODULES +++ b/README-MODULES @@ -12,7 +12,9 @@ provide some modules in two versions, which means that we have three set of modu - modules_s: SER modules All modules are compatible with the core, so regardless if you are a new user or -an existing, you are free to make a choice between the three sets. +an existing, you are free to make a choice between the three sets as well as +mix and match between them. + Note that if you are currently using one product, you want to select the module that exists in the K/S directories first to get a smooth upgrade path.

15 years, 3 months

doc/ser-radius.xml

by Olle E. Johansson

<simpara> If you need RADIUS accounting then edit also sip_router/ modules/acc/Makefile and uncomment lines containing: </simpara> <programlisting> DEFS+=-DRAD_ACC LIBS=-L$(LOCALBASE)/lib -lradiusclient </programlisting> What's the current status? I think that it would be good that someone who knows the status cleans up this file... It seems old. We have the following modules now: drwxr-xr-x 13 olle wheel 442 10 Okt 13:32 modules/auth_radius drwxr-xr-x 11 olle wheel 374 10 Okt 13:32 modules/misc_radius drwxr-xr-x 4 olle wheel 136 10 Okt 16:58 modules_s/acc_radius The document mentions group_radius.so which I can't find... Made a few small changes in the file, but not enough for release. /O

15 years, 3 months

git:master: Updating xml doc

by Olle E. Johansson

Module: sip-router Branch: master Commit: fc5840716b51d7817be52cefb203d96c380c35d0 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=fc58407… Author: oej <oej(a)edvina.net> Committer: oej <oej(a)edvina.net> Date: Sat Oct 10 17:13:24 2009 +0200 Updating xml doc --- doc/ser_radius/ser_radius.xml | 68 ++++++++++++++++++----------------------- 1 files changed, 30 insertions(+), 38 deletions(-) diff --git a/doc/ser_radius/ser_radius.xml b/doc/ser_radius/ser_radius.xml index d2bfb30..2b3e04c 100644 --- a/doc/ser_radius/ser_radius.xml +++ b/doc/ser_radius/ser_radius.xml @@ -1,6 +1,12 @@ <?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" - "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" +"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [ + + +<!ENTITY % docentities SYSTEM "../../docbook/entities.xml"> +%docentities; + +]> <section id="ser_radius" xmlns:xi="http://www.w3.org/2001/XInclude"> <sectioninfo> @@ -23,19 +29,19 @@ </revhistory> </sectioninfo> - <title>SER RADIUS Howto</title> + <title>SIP-router RADIUS Howto</title> <section id="radius_intro"> <title>Introduction</title> <simpara> - SER can be configured to use RADIUS server for authentication, + SIP-router can be configured to use RADIUS server for authentication, accounting, and group membership checking. Since configuration of RADIUS seems to be a common source of problems, we decided to put together this HOWTO. </simpara> <simpara> The HOWTO covers installation and configuration of FreeRADIUS - server only. There are also other RADIUS servers available and as + server only. There are other RADIUS servers available and as long as they support digest authentication, they should work too. Any volunteers willing to describe setup of other RADIUS servers are encouraged to contact the author. @@ -44,7 +50,7 @@ <section id="prerequisities"> <title>Prerequisites</title> <simpara> - To setup RADIUS support in SER you will need the following: + To setup RADIUS support in SIP-router you will need the following: </simpara> <itemizedlist> <listitem> @@ -66,13 +72,13 @@ </listitem> <listitem> <simpara> - SER, get it from <ulink url="http://iptel.org/ser">http://iptel.org/ser</ulink> + SIP-router, get it from <ulink url="&serhome;">&serhome;</ulink> </simpara> </listitem> <listitem> <simpara> You should also have some experience in configuring - SER. Before you enable RADIUS authentication or + SIP-router. Before you enable RADIUS authentication or accounting make sure that the basic server is running and that you know how to customize it to your taste. </simpara> @@ -80,13 +86,13 @@ <listitem> <simpara> If you want to use RADIUS accounting then you will have - to compile SER from sources so you should know how to + to compile SIP-router from sources so you should know how to do it. </simpara> </listitem> </itemizedlist> <simpara> - Various unix/linux distributions might include binary packages + Various Unix/Linux distributions might include binary packages of the mentioned applications. In that case you can safely use the packages, there shouldn't be any problem. Location of some files may be different, though. We will describe how to install @@ -192,7 +198,7 @@ acctserver localhost <simpara> Radiusclient library contains file called <filename>dictionary.ser</filename>. That file includes all the - attributes that are needed by SER. Include the file in the + attributes that are needed by SIP-router. Include the file in the main <filename>dictionary</filename> file. To include the file, put the following line at the end of <filename>dictionary</filename> file: @@ -376,7 +382,7 @@ root@/usr/local/src# radclient -f digest localhost auth <shared_secret> package. That also means that you have to enable access from localhost in your <filename>clients.conf</filename> file. Don't forget to replace <shared_secret> with - the shared secret configured for locahost clients in + the shared secret configured for localhost clients in <filename>clients.conf</filename>. </simpara> </note> @@ -392,18 +398,18 @@ Received response ID 224, code 2, length = 45 <section id="auth_configuration"> <title>Authentication Configuration</title> <simpara> - To create user "joe" in domain "iptel.org" with password + To create user "joe" in domain "sip-router.org" with password "heslo" put the following into file <filename>/usr/local/etc/raddb/users</filename>: </simpara> <programlisting> -joe(a)iptel.org Auth-Type := Digest, User-Password == "heslo" +joe(a)sip-router.org Auth-Type := Digest, User-Password == "heslo" Reply-Message = "Authenticated", Sip-Rpid = "1234" </programlisting> <simpara> Attribute "Sip-Rpid" is optional. The attribute - contains a phone number associated to the user. SER can be + contains a phone number associated to the user. SIP-router can be configured to put the phone number into Remote-Party-ID header field of the SIP message. The header field can be then used by PSTN gateways to display the number as the number of the @@ -415,7 +421,7 @@ joe(a)iptel.org Auth-Type := Digest, User-Password == "heslo" <section id="accounting_configuration_server"> <title>Accounting Configuration</title> <simpara> - By default FreeRADIUS server will log all accounting requests + By default the FreeRADIUS server will log all accounting requests into <filename>/usr/local/var/log/radius/radacct</filename> directory in form of plain text files. The server will create one file for each hostname in the directory. The @@ -470,43 +476,29 @@ Tue Jun 24 00:20:56 2003 <section id="group_checking"> <title>Group Checking Configuration</title> <simpara> - If you want to make user "joe" in domain "iptel.org" member of + If you want to make user "joe" in domain "sip-router.org" member of group "pstn" then add the following to your <filename>/usr/local/etc/raddb/users</filename> file: </simpara> <programlisting> -joe(a)iptel.org Sip-Group == "pstn", Auth-Type := Accept +joe(a)sip-router.org Sip-Group == "pstn", Auth-Type := Accept Reply-Message = "Authorized" </programlisting> </section> </section> <section id="ser_config"> - <title>SER Configuration</title> + <title>SIP-router Configuration</title> <simpara> We will describe installation from sources here. If you use binary packages then there is an additional package containing RADIUS related modules. You will need to install the package. </simpara> - <warning> - <simpara> - Due to a mistake the binary packages for RADIUS do not include - RADIUS-enabled version of acc (accounting) module. The packages - contain modules for RADIUS authentication and group membership - checking only. - </simpara> - <simpara> - If you need accounting over RADIUS then you will have to - compile RADIUS-enabled version of acc module from the - sources. This will be fixed in one of future releases, we - apologize for any inconvenience. - </simpara> - </warning> <simpara> RADIUS-related modules are not compiled by default. To compile them, edit <filename>Makefile</filename>, find variable <varname>exclude_modules</varname> and you should see - "auth_radius", "group_radius", and "uri_radius" among excluded + "auth_radius", "acc_radius", and "misc_radius" among excluded modules. Simply remove the three modules from the list. </simpara> <simpara> @@ -518,7 +510,7 @@ DEFS+=-DRAD_ACC LIBS=-L$(LOCALBASE)/lib -lradiusclient </programlisting> <simpara> - Then recompile and re-install SER: + Then recompile and re-install SIP-router: </simpara> <screen> root@localhost:/usr/local/src/sip_router# make proper @@ -529,7 +521,7 @@ root@localhost:/usr/local/src/sip_router# make install <section id="auth_configuration_client"> <title>Authentication Configuration</title> <simpara> - Edit configuration file of SER and instead of + Edit configuration file of SIP-router and instead of <filename>auth_db.so</filename> load <filename>auth_radius.so</filename> and also replace <function>www_authorize</function> with @@ -574,8 +566,8 @@ root@localhost:/usr/local/src/sip_router# make install <qandaentry> <question> <simpara> - I compiled SER RADIUS modules and installed - radiusclient library, but when I try to start ser I get + I compiled SIP-router RADIUS modules and installed + radiusclient library, but when I try to start the server I get the following error message: </simpara> <programlisting>

15 years, 3 months

git:master: Typos, server name

by Olle E. Johansson

Module: sip-router Branch: master Commit: 95ec00f6ddc3b8e5b8059b1dce0d1f4c8ae29064 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=95ec00f… Author: oej <oej(a)edvina.net> Committer: oej <oej(a)edvina.net> Date: Sat Oct 10 16:48:02 2009 +0200 Typos, server name --- doc/dst_blacklist.txt | 66 ++++++++++++++++++++++++++----------------------- 1 files changed, 35 insertions(+), 31 deletions(-) diff --git a/doc/dst_blacklist.txt b/doc/dst_blacklist.txt index 8130ff4..93e914f 100644 --- a/doc/dst_blacklist.txt +++ b/doc/dst_blacklist.txt @@ -6,67 +6,71 @@ # Overview +-------- The destination blacklist (dst_blacklist) is used to try to mark bad - destination and avoid possible future expensive send operation to them. - A destination is added to the blacklist when trying to send to it fails (e.g. - timeout while trying to send or connect on tcp), or when a sip timeout occurs - while trying to forward statefully an invite (using tm) and the remote side + destinations and avoid possible future expensive send operation to them. + A destination is added to the blacklist when an attempt to send to it fails (e.g. + timeout while trying to send or connect on TCP), or when a SIP timeout occurs + while trying to forward statefully an INVITE (using tm) and the remote side doesn't send back any response. - The blacklist (if enabled) is checked before any send attempt. + The blacklist (if enabled) is checked before any send attempt. Drawbacks - +--------- Using the destination blacklist will cause some performance degradation, especially on multi cpu machines. If you don't need it you can easily - disable it, either in ser's config or at compile time. Disabling it at - compile time is slightly better (but not in a "measurable" way) then - disabling it at runtime, from the config file. - Whether the destination blacklist is better to be on or off depends a lot - on the setup. In general is better to turn it on when: - - sending to clients that don't respond is expensive (e.g. lots of clients - use tcp and they have the habit of silently discarding tcp traffic from time - to time) - - statefull forwarding is used (tm) and lower memory usage is desired - (a transaction will fail immediately if the destination is already - blacklisted by a previous transaction to the same destination that failed - due to timeout) - - faster dns failover is desired, especially when statefull forwarding (tm) - and udp are used - - better chances of DOS survival are important + disable it, either in sip-router's config or at compile time. Disabling it at + compile time is slightly better (but not in a "measurable" way) than + disabling it at runtime, from the config file. + Whether the destination blacklist is a good solution for you depends a lot + on the setup. In general it is better to turn it on when: + - sending to clients that don't respond is expensive (e.g. lots of clients + use tcp and they have the habit of silently discarding tcp traffic from time + to time) + - stateful forwarding is used (tm) and lower memory usage is desired + (a transaction will fail immediately if the destination is already + blacklisted by a previous transaction to the same destination that failed + due to timeout) + - faster dns failover is desired, especially when stateful forwarding (tm) + and UDP are used + - better chances of DOS attack survival are important Config Variables +---------------- use_dst_blacklist = on | off (default off) - enable the destination blacklist: - if on each failed send attempt will cause the destination to be blacklisted. - Before any send this blacklist will be checked and if a match is found the + If on each failed send attempt will cause the destination to be blacklisted. + Before any send operation this blacklist will be checked and if a match is found the send is no longer attempted (an error is returned immediately). Note: using the blacklist incurs a small performance penalty. dst_blacklist_mem = size in Kb (default 250 Kb) - maximum shared memory amount used for keeping the blacklisted destinations. - dst_blacklist_expire = time in s (default 60 s) - how much time a + dst_blacklist_expire = time in s (default 60 s) - how long time a blacklisted destination will be kept in the blacklist (w/o any update). dst_blacklist_gc_interval = time in s (default 60 s) - how often the garbage collection will run (eliminating old, expired entries). dst_blacklist_init = on | off (default on) - if off, the blacklist - is not initialized at startup and cannot be enabled runtime, - that saves some memory. + is not initialized at startup and cannot be enabled at runtime, + which saves some memory. -Compile Options +Compile Time Options +-------------------- USE_DST_BLACKLIST - if defined the blacklist support will be compiled-in (default). - Note: To remove a compile options, edit ser's Makefile.defs and remove it - form DEFS list. To add a compile options add it to the make command line, + Note: To remove a compile time option, edit the file Makefile.defs and remove + USE_DST_BLACKLIST from the list named DEFS. + To add a compile time option, just add it to the make command line, e.g.: make proper; make all extra_defs=-DUSE_DNS_FAILOVER - or for a permanent solution, edit Makefile.defs and add it to DEFS - (don't forget to prefix it with -D). + or for a permanent solution, edit Makefile.defs and add it to DEFS + (don't forget to prefix it with -D).

15 years, 3 months

/tmp/ser_ctl (CTL module)

by Olle E. Johansson

Should we rename this file? /tmp/sr_ctl /tmp/siprouter.ctl /tmp/sip-router.ctl The more descriptive it is, the better. /O

15 years, 3 months

git:master: Adding license to the doxygen documentation

by Olle E. Johansson

Module: sip-router Branch: master Commit: cc68f171deae22a3a6b65e7146e77955c1c7d3c8 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=cc68f17… Author: oej <oej(a)edvina.net> Committer: oej <oej(a)edvina.net> Date: Sat Oct 10 16:37:45 2009 +0200 Adding license to the doxygen documentation --- doc/doxygen/main.dox | 20 ++++++++++++++++++++ main.c | 12 +++--------- 2 files changed, 23 insertions(+), 9 deletions(-) diff --git a/doc/doxygen/main.dox b/doc/doxygen/main.dox index 924323d..a59cc15 100644 --- a/doc/doxygen/main.dox +++ b/doc/doxygen/main.dox @@ -11,4 +11,24 @@ * are used by all SIP Router modules that need to access a database. * * \section sr_modules SIP Router Modules + * Please click on the "modules" tab above for more information about the modules + * + * The documentation can be generated using doxygen by running "make doxygen" + * + * \section License SIP-router license + * SIP-router is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License as published by + * the Free Software Foundation; either version 2 of the License, or + * (at your option) any later version + * + * SIP-router is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + * + * You should have received a copy of the GNU General Public License + * along with this program; if not, write to the Free Software + * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + * */ + diff --git a/main.c b/main.c index aa3a6d6..b50a75b 100644 --- a/main.c +++ b/main.c @@ -3,19 +3,14 @@ * * Copyright (C) 2001-2003 FhG Fokus * - * This file is part of ser, a free SIP server. + * This file is part of SIP-router, a free SIP server. * - * ser is free software; you can redistribute it and/or modify + * SIP-router is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation; either version 2 of the License, or * (at your option) any later version * - * For a license to use the ser software under conditions - * other than those described here, or to purchase support for this - * software, please contact iptel.org by e-mail at the following addresses: - * info(a)iptel.org - * - * ser is distributed in the hope that it will be useful, + * SIP-router is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. @@ -94,7 +89,6 @@ * */ - #include <stdio.h> #include <stdlib.h> #include <errno.h>

15 years, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev