I disabled anonymous usage of sourceforge tracker, which should not be
used anyhow, but got spammers' attention.
Cheers,
Daniel
On 10/22/12 11:48 AM, SourceForge.net wrote:
> Feature Requests item #1891148, was opened at 2008-02-11 05:58
> Message generated for change (Comment added) made by nobody
> You can respond by visiting:
> https://sourceforge.net/tracker/?func=detail&atid=743023&aid=1891148&group_…
>
> Please note that this message will contain a full copy of the comment thread,
> including the initial issue submission, for this request,
> not just the latest update.
> Category: modules
> Group: ver devel
> Status: Open
> Resolution: None
> Priority: 5
> Private: No
> Submitted By: Helmut Kuper (hekuper)
> Assigned to: Nobody/Anonymous (nobody)
> Summary: protection of open fifo/ socket files against removing
>
> Initial Comment:
> Hi,
>
> I found that starting a 2nd openser with same config as an already
> running openser on same machine using module mi_datagram leads to a deletion of the
> socket file of the already running openser process.
>
> This is very bad when u use openser as a frontend for sems for example. :(
>
> If this is a bug, maybe the check, whether there is
> an already running openser using same network resources, should be placed *befor* starting modules.
> Alternative modules should be able to handle those problematic scenarios ...
>
> My mi_datagram config is this:
>
> loadmodule "mi_datagram.so"
> modparam("mi_datagram", "socket_name", "/tmp/openser_ansagen_sock")
> modparam("mi_datagram", "children_count", 1)
> modparam("mi_datagram", "unix_socket_mode", 0660)
> modparam("mi_datagram", "unix_socket_group", "voip")
> modparam("mi_datagram", "unix_socket_user", "ruth")
> modparam("mi_datagram", "socket_timeout", 2000)
>
> regards
> Helmut
>
> ----------------------------------------------------------------------
>
> Comment By: Nobody/Anonymous (nobody)
> Date: 2012-10-22 02:48
>
> Message:
> Hi there! This is my first visit to your blog! We are a team of volunteers
> and starting a new project in a community in the same niche. Your blog
> provided us useful information to work on. You have done a marvellous job!
> <a
> href="http://thenorthfacebackpacksf.blogspot.com/2012/10/cheap-north-face-jackets…"
> title="north face jackets clearance">north face jackets clearance</a>
>
> ----------------------------------------------------------------------
>
> Comment By: Nobody/Anonymous (nobody)
> Date: 2012-10-15 09:23
>
> Message:
> Today, I went to the beachfront with my children. I found a sea shell and
> gave it to my 4 year old daughter and said "You can hear the ocean if you
> put this to your ear." She placed the shell to her ear and screamed. There
> was a hermit crab inside and it pinched her ear. She never wants to go
> back! LoL I know this is totally off topic but I had to tell someone!
> [url=http://northfacevest.blogbaker.com/]Parry[/url]
> <a href="http://northfacevest.blogbaker.com/" title="Parry">Parry</a>
>
> ----------------------------------------------------------------------
>
> Comment By: Nobody/Anonymous (nobody)
> Date: 2012-08-26 01:24
>
> Message:
> Hey there this is kind of of off topic but I was wondering if blogs use
> WYSIWYG editors or if you have to manually code with HTML. I'm starting a
> blog soon but have no coding expertise so I wanted to get advice from
> someone with experience. Any help would be enormously appreciated!
> http://www.sunglasses4summer.net/
>
> ----------------------------------------------------------------------
>
> Comment By: Henning Westerholt (henningw)
> Date: 2008-07-08 06:47
>
> Message:
> Logged In: YES
> user_id=337916
> Originator: NO
>
> Hi all,
>
> the problem with checking the existence of the fifo/ socket is that the old
> file is not deleted during the shutdown. Even if we change this then the
> problem would be still present in the event of a server crash.
>
> As Helmut aggreed that this can be closed, i've moved this to the feature
> request section. The startup code in main.c could be modified to check for
> available network resources before doing the module initialization to
> achieve this functionality.
>
> Cheers,
>
> Henning
>
> ----------------------------------------------------------------------
>
> Comment By: Ovidiu Sas (osas)
> Date: 2008-02-12 07:58
>
> Message:
> Logged In: YES
> user_id=1395524
> Originator: NO
>
> It happened to me too. I wanted to check the version of openser and
> instead of running 'openser -V' I ran 'openser -v' and my fifo file was
> gone.
> Maybe a quick fix would be to check the existence of the fifo file. If
> exists, exit with an error, if not, proceed as normal.
> Just my 2c.
>
>
> Regards,
> Ovidiu sas
>
> ----------------------------------------------------------------------
>
> Comment By: Nobody/Anonymous (nobody)
> Date: 2008-02-12 07:53
>
> Message:
> Logged In: NO
>
> Hi,
>
> well, I agree too. This is an operation error by admin. But it is annoying
> that it is so easy to destroy the media server. This will quit often occurs
> if you are using bash shell with command history combined with nervous
> fingers ;) ...
>
> I think that checking network resources in openser befor doing rest of
> configuration is safer. It should work allways, cause no second openser
> will user same address and port on same machine at same time.
>
> On the other Hand saving the PID of first openser in a PID should be an
> acceptable work around.
>
> So we can close this case if you want.
>
> regards
> Helmut
>
>
> ----------------------------------------------------------------------
>
> Comment By: Nobody/Anonymous (nobody)
> Date: 2008-02-12 07:40
>
> Message:
> Logged In: NO
>
> is it possible to delete a FIFO which is currently used? E.g by mistake I
> start openser a second time. If it deletes the FIFO then it may cause
> problems to the current running openser instance.
>
> klaus
>
> ----------------------------------------------------------------------
>
> Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
> Date: 2008-02-12 05:33
>
> Message:
> Logged In: YES
> user_id=1275325
> Originator: NO
>
> Hi Henning,
>
> I agree here - the fix should not be in openser, but rather in whatever
> scripts/admins are managing openser. From my point of view, this is a
> openser operation error.
>
> Regards,
> Bogdan
>
> ----------------------------------------------------------------------
>
> Comment By: Henning Westerholt (henningw)
> Date: 2008-02-12 03:24
>
> Message:
> Logged In: YES
> user_id=337916
> Originator: NO
>
> I think this can be fixed by other means:
>
> Just add some checks to openserctl to not start openser two times, like the
> init script does (i think).
> This would be easier than to fix the OpenSER start process to not start at
> all (or fail just in the beginning) if another process is already running.
>
> Henning
>
> ----------------------------------------------------------------------
>
> Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
> Date: 2008-02-12 03:06
>
> Message:
> Logged In: YES
> user_id=1275325
> Originator: NO
>
> Hi Helmut,
>
> This is the normal/expected bahviour of the module - to avoid any security
> problems (using a fake or malicious already existing unixsocket) openser
> removes it first (if exists) and then creates its own with proper
> permissions and security restrictions.
>
> So, it is not a bug :).
>
> Regards,
> Bogdan
>
> ----------------------------------------------------------------------
>
> Comment By: Helmut Kuper (hekuper)
> Date: 2008-02-11 06:53
>
> Message:
> Logged In: YES
> user_id=1851349
> Originator: YES
>
> Hi Bogdan,
>
> yes I use same socket file name for both opensers, cause both are using
> same config file.
>
> Befor we misunderstand: I don't want to run 2 opensers with same config on
> same machine!! I rather strumbled about that bug/problem, when I accidently
> started same openser without openserctl twice
>
> ----------------------------------------------------------------------
>
> Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
> Date: 2008-02-11 06:45
>
> Message:
> Logged In: YES
> user_id=1275325
> Originator: NO
>
> Hi Helmut,
>
> so you use the same socket_name for both openser's ??
>
> Regards,
> Bogdan
>
> ----------------------------------------------------------------------
>
> You can respond by visiting:
> https://sourceforge.net/tracker/?func=detail&atid=743023&aid=1891148&group_…
>
> _______________________________________________
> sr-dev mailing list
> sr-dev(a)lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - http://asipto.com/u/katu
Feature Requests item #1891148, was opened at 2008-02-11 05:58
Message generated for change (Comment added) made by nobody
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=743023&aid=1891148&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: ver devel
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Helmut Kuper (hekuper)
Assigned to: Nobody/Anonymous (nobody)
Summary: protection of open fifo/ socket files against removing
Initial Comment:
Hi,
I found that starting a 2nd openser with same config as an already
running openser on same machine using module mi_datagram leads to a deletion of the
socket file of the already running openser process.
This is very bad when u use openser as a frontend for sems for example. :(
If this is a bug, maybe the check, whether there is
an already running openser using same network resources, should be placed *befor* starting modules.
Alternative modules should be able to handle those problematic scenarios ...
My mi_datagram config is this:
loadmodule "mi_datagram.so"
modparam("mi_datagram", "socket_name", "/tmp/openser_ansagen_sock")
modparam("mi_datagram", "children_count", 1)
modparam("mi_datagram", "unix_socket_mode", 0660)
modparam("mi_datagram", "unix_socket_group", "voip")
modparam("mi_datagram", "unix_socket_user", "ruth")
modparam("mi_datagram", "socket_timeout", 2000)
regards
Helmut
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2012-10-22 02:48
Message:
Hi there! This is my first visit to your blog! We are a team of volunteers
and starting a new project in a community in the same niche. Your blog
provided us useful information to work on. You have done a marvellous job!
<a
href="http://thenorthfacebackpacksf.blogspot.com/2012/10/cheap-north-face-jackets…"
title="north face jackets clearance">north face jackets clearance</a>
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2012-10-15 09:23
Message:
Today, I went to the beachfront with my children. I found a sea shell and
gave it to my 4 year old daughter and said "You can hear the ocean if you
put this to your ear." She placed the shell to her ear and screamed. There
was a hermit crab inside and it pinched her ear. She never wants to go
back! LoL I know this is totally off topic but I had to tell someone!
[url=http://northfacevest.blogbaker.com/]Parry[/url]
<a href="http://northfacevest.blogbaker.com/" title="Parry">Parry</a>
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2012-08-26 01:24
Message:
Hey there this is kind of of off topic but I was wondering if blogs use
WYSIWYG editors or if you have to manually code with HTML. I'm starting a
blog soon but have no coding expertise so I wanted to get advice from
someone with experience. Any help would be enormously appreciated!
http://www.sunglasses4summer.net/
----------------------------------------------------------------------
Comment By: Henning Westerholt (henningw)
Date: 2008-07-08 06:47
Message:
Logged In: YES
user_id=337916
Originator: NO
Hi all,
the problem with checking the existence of the fifo/ socket is that the old
file is not deleted during the shutdown. Even if we change this then the
problem would be still present in the event of a server crash.
As Helmut aggreed that this can be closed, i've moved this to the feature
request section. The startup code in main.c could be modified to check for
available network resources before doing the module initialization to
achieve this functionality.
Cheers,
Henning
----------------------------------------------------------------------
Comment By: Ovidiu Sas (osas)
Date: 2008-02-12 07:58
Message:
Logged In: YES
user_id=1395524
Originator: NO
It happened to me too. I wanted to check the version of openser and
instead of running 'openser -V' I ran 'openser -v' and my fifo file was
gone.
Maybe a quick fix would be to check the existence of the fifo file. If
exists, exit with an error, if not, proceed as normal.
Just my 2c.
Regards,
Ovidiu sas
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2008-02-12 07:53
Message:
Logged In: NO
Hi,
well, I agree too. This is an operation error by admin. But it is annoying
that it is so easy to destroy the media server. This will quit often occurs
if you are using bash shell with command history combined with nervous
fingers ;) ...
I think that checking network resources in openser befor doing rest of
configuration is safer. It should work allways, cause no second openser
will user same address and port on same machine at same time.
On the other Hand saving the PID of first openser in a PID should be an
acceptable work around.
So we can close this case if you want.
regards
Helmut
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2008-02-12 07:40
Message:
Logged In: NO
is it possible to delete a FIFO which is currently used? E.g by mistake I
start openser a second time. If it deletes the FIFO then it may cause
problems to the current running openser instance.
klaus
----------------------------------------------------------------------
Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
Date: 2008-02-12 05:33
Message:
Logged In: YES
user_id=1275325
Originator: NO
Hi Henning,
I agree here - the fix should not be in openser, but rather in whatever
scripts/admins are managing openser. From my point of view, this is a
openser operation error.
Regards,
Bogdan
----------------------------------------------------------------------
Comment By: Henning Westerholt (henningw)
Date: 2008-02-12 03:24
Message:
Logged In: YES
user_id=337916
Originator: NO
I think this can be fixed by other means:
Just add some checks to openserctl to not start openser two times, like the
init script does (i think).
This would be easier than to fix the OpenSER start process to not start at
all (or fail just in the beginning) if another process is already running.
Henning
----------------------------------------------------------------------
Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
Date: 2008-02-12 03:06
Message:
Logged In: YES
user_id=1275325
Originator: NO
Hi Helmut,
This is the normal/expected bahviour of the module - to avoid any security
problems (using a fake or malicious already existing unixsocket) openser
removes it first (if exists) and then creates its own with proper
permissions and security restrictions.
So, it is not a bug :).
Regards,
Bogdan
----------------------------------------------------------------------
Comment By: Helmut Kuper (hekuper)
Date: 2008-02-11 06:53
Message:
Logged In: YES
user_id=1851349
Originator: YES
Hi Bogdan,
yes I use same socket file name for both opensers, cause both are using
same config file.
Befor we misunderstand: I don't want to run 2 opensers with same config on
same machine!! I rather strumbled about that bug/problem, when I accidently
started same openser without openserctl twice
----------------------------------------------------------------------
Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
Date: 2008-02-11 06:45
Message:
Logged In: YES
user_id=1275325
Originator: NO
Hi Helmut,
so you use the same socket_name for both openser's ??
Regards,
Bogdan
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=743023&aid=1891148&group_…
Module: sip-router
Branch: master
Commit: 9683068672ffb4679b6caa3d1a3a8b51aeedffd9
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=9683068…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Sun Oct 21 19:02:56 2012 +0200
sipcapture Fixing typos in documentation
---
modules/sipcapture/README | 20 ++++++++++----------
modules/sipcapture/doc/sipcapture_admin.xml | 14 +++++++-------
2 files changed, 17 insertions(+), 17 deletions(-)
diff --git a/modules/sipcapture/README b/modules/sipcapture/README
index 1b3bf1f..28b7da9 100644
--- a/modules/sipcapture/README
+++ b/modules/sipcapture/README
@@ -63,8 +63,8 @@ Alexandr Dubovikov
1.9. Set raw_moni_capture_on parameter
1.10. Set raw_socket_listen parameter
1.11. Set raw_socket_listen parameter
- 1.12. Set raw_socket_listen parameter
- 1.13. Set hep_capture_on parameter
+ 1.12. Set raw_sock_children parameter
+ 1.13. Set promiscous_on parameter
1.14. Set raw_moni_bpf_on parameter
1.15. Set capture_node parameter
@@ -105,13 +105,13 @@ Chapter 1. Admin Guide
1. Overview
- Offer a possibility to store incoming/outgoing SIP messages in
+ The sipcapture module stores incoming/outgoing SIP messages in
database.
- Kamailio can capture SIP messages in three mode
+ Kamailio can capture SIP messages in three modes
* IPIP encapsulation. (ETHHDR+IPHDR+IPHDR+UDPHDR).
* Monitoring/mirroring port.
- * Homer encapsulation protocl mode (HEP v1).
+ * Homer encapsulation protocol mode (HEP v1).
The capturing can be turned on/off using fifo commad.
@@ -166,7 +166,7 @@ modparam("sipcapture", "db_url", "mysql://user:passwd@host/dbname")
3.2. table_name (str)
- Name of the table's name where to store the SIP messages. Can contain
+ Name of the table's name used to store the SIP messages. Can contain
multiple tables, separated by "|".
Default value is "sip_capture".
@@ -300,12 +300,12 @@ modparam("sipcapture", "raw_interface", "eth0")
3.12. raw_sock_children (integer)
- Parameter define how much children must be created to listen the raw
- socket.
+ Parameter define how many children that must be created to listen the
+ raw socket.
Default value is "1".
- Example 1.12. Set raw_socket_listen parameter
+ Example 1.12. Set raw_sock_children parameter
...
modparam("sipcapture", "raw_sock_children", 6)
...
@@ -317,7 +317,7 @@ modparam("sipcapture", "raw_sock_children", 6)
Default value is "0".
- Example 1.13. Set hep_capture_on parameter
+ Example 1.13. Set promiscous_on parameter
...
modparam("sipcapture", "promiscuous_on", 1)
...
diff --git a/modules/sipcapture/doc/sipcapture_admin.xml b/modules/sipcapture/doc/sipcapture_admin.xml
index 1e0f9df..8c0f3da 100644
--- a/modules/sipcapture/doc/sipcapture_admin.xml
+++ b/modules/sipcapture/doc/sipcapture_admin.xml
@@ -16,10 +16,10 @@
<section>
<title>Overview</title>
<para>
- Offer a possibility to store incoming/outgoing SIP messages in database.
+ The sipcapture module stores incoming/outgoing SIP messages in database.
</para>
<para>
- Kamailio can capture SIP messages in three mode
+ Kamailio can capture SIP messages in three modes
<itemizedlist>
<listitem>
<para>
@@ -33,7 +33,7 @@
</listitem>
<listitem>
<para>
- Homer encapsulation protocl mode (HEP v1).
+ Homer encapsulation protocol mode (HEP v1).
</para>
</listitem>
</itemizedlist>
@@ -104,7 +104,7 @@ modparam("sipcapture", "db_url", "mysql://user:passwd@host/dbname")
<section>
<title><varname>table_name</varname> (str)</title>
<para>
- Name of the table's name where to store the SIP messages. Can contain multiple tables, separated by "|".
+ Name of the table's name used to store the SIP messages. Can contain multiple tables, separated by "|".
</para>
<para>
<emphasis>
@@ -312,7 +312,7 @@ modparam("sipcapture", "raw_interface", "eth0")
<section>
<title><varname>raw_sock_children</varname> (integer)</title>
<para>
- Parameter define how much children must be created to listen the raw socket.
+ Parameter define how many children that must be created to listen the raw socket.
</para>
<para>
<emphasis>
@@ -320,7 +320,7 @@ modparam("sipcapture", "raw_interface", "eth0")
</emphasis>
</para>
<example>
- <title>Set <varname>raw_socket_listen</varname> parameter</title>
+ <title>Set <varname>raw_sock_children</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("sipcapture", "raw_sock_children", 6)
@@ -340,7 +340,7 @@ modparam("sipcapture", "raw_sock_children", 6)
</emphasis>
</para>
<example>
- <title>Set <varname>hep_capture_on</varname> parameter</title>
+ <title>Set <varname>promiscous_on</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("sipcapture", "promiscuous_on", 1)
Module: sip-router
Branch: master
Commit: 4ba7d41bc078e554d48316b2c3e0b6435b55f60a
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=4ba7d41…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Sun Oct 21 18:54:33 2012 +0200
SDPops Typo fixes in documentation
---
modules/sdpops/README | 10 +++++-----
modules/sdpops/doc/sdpops_admin.xml | 11 +++++------
2 files changed, 10 insertions(+), 11 deletions(-)
diff --git a/modules/sdpops/README b/modules/sdpops/README
index 893b4ee..931f80d 100644
--- a/modules/sdpops/README
+++ b/modules/sdpops/README
@@ -79,13 +79,13 @@ Chapter 1. Admin Guide
1. Overview
- This module provides function for checking and managing the SDP
+ This module provides functions for checking and managing the SDP
payloads of SIP messages.
- Examples of what this module offers: remove codecs from SDP, check the
- media stream types, return attributes of SDP document. For the full
- least of the features provided by this module and the implementation
- state, read further to the list of exported functions.
+ Examples of functions this module offers: remove codecs from SDP, check
+ the media stream types, return attributes of SDP document. For the full
+ list of the features provided by this module and the implementation
+ state, read the list of exported functions.
2. Dependencies
diff --git a/modules/sdpops/doc/sdpops_admin.xml b/modules/sdpops/doc/sdpops_admin.xml
index 81f0f4d..14525b7 100644
--- a/modules/sdpops/doc/sdpops_admin.xml
+++ b/modules/sdpops/doc/sdpops_admin.xml
@@ -16,15 +16,14 @@
<section>
<title>Overview</title>
<para>
- This module provides function for checking and managing the SDP
+ This module provides functions for checking and managing the SDP
payloads of SIP messages.
</para>
<para>
- Examples of what this module offers: remove codecs from SDP,
+ Examples of functions this module offers: remove codecs from SDP,
check the media stream types, return attributes of SDP document.
- For the full least of the features provided by this module and
- the implementation state, read further to the list of exported
- functions.
+ For the full list of the features provided by this module and
+ the implementation state, read the list of exported functions.
</para>
</section>
@@ -78,7 +77,7 @@
parameter can be a static string or a variable holding the
list of numeric codec IDs.
</para>
- <para>
+ <para>
This function can be used from ANY_ROUTE.
</para>
<example>
Module: sip-router
Branch: master
Commit: 2aa02e80cd76f38e812bfddf32326248e9b74cf8
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=2aa02e8…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Sun Oct 21 18:49:43 2012 +0200
Ratelimit: Fixing typos
---
modules/ratelimit/README | 10 +++++-----
modules/ratelimit/doc/ratelimit_admin.xml | 10 +++++-----
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/modules/ratelimit/README b/modules/ratelimit/README
index 84aa33c..d8e6ebb 100644
--- a/modules/ratelimit/README
+++ b/modules/ratelimit/README
@@ -207,11 +207,11 @@ Chapter 1. Admin Guide
4.1. Feedback Algorithm (FEEDBACK)
- When running openser on different machines, one has to adjust the drop
+ When running Kamailio on different machines, one has to adjust the drop
rates for the static algorithms to maintain a sub 100% load average or
packets start getting dropped in the network stack. While this is not
in itself difficult, it isn't neither accurate nor trivial: another
- server taking a notable fraction of the cpu time will require re-tuning
+ server taking a notable fraction of the CPU time will require re-tuning
the parameters.
While tuning the drop rates from the outside based on a certain factor
@@ -226,7 +226,7 @@ Chapter 1. Admin Guide
adjusted dynamically based on the load factor so that the load factor
always drifts towards the specified limit (or setpoint, in PID terms).
- As reading the cpu load average is relatively expensive (opening
+ As reading the CPU load average is relatively expensive (opening
/proc/stat, parsing it, etc), this only happens once every
timer_interval seconds and consequently the FEEDBACK value is only at
these intervals recomputed. This in turn makes it difficult for the
@@ -421,7 +421,7 @@ modparam("ratelimit", "pipe", "4:NETWORK:10000")
8.1. rl.stats
- Lists the parameters and variabiles in the ratelimit module.
+ Lists the parameters and variables in the ratelimit module.
Name: rl.stats
@@ -507,7 +507,7 @@ modparam("ratelimit", "pipe", "4:NETWORK:10000")
8.8. rl.push_load
- Force the value of the load parameter. This methos is usefull for
+ Force the value of the load parameter. This method is useful for
testing the Feedback algorithm.
Name: rl.push_load
diff --git a/modules/ratelimit/doc/ratelimit_admin.xml b/modules/ratelimit/doc/ratelimit_admin.xml
index 5e37fdc..5b6e40a 100644
--- a/modules/ratelimit/doc/ratelimit_admin.xml
+++ b/modules/ratelimit/doc/ratelimit_admin.xml
@@ -112,11 +112,11 @@
<section>
<title>Dynamic Rate Limiting Algorithms</title>
<para>
- When running openser on different machines, one has to adjust the drop
+ When running &kamailio; on different machines, one has to adjust the drop
rates for the static algorithms to maintain a sub 100% load average or
packets start getting dropped in the network stack. While this is not
in itself difficult, it isn't neither accurate nor trivial: another
- server taking a notable fraction of the cpu time will require re-tuning
+ server taking a notable fraction of the CPU time will require re-tuning
the parameters.
</para>
<para>
@@ -136,7 +136,7 @@
in PID terms).
</para>
<para>
- As reading the cpu load average is relatively expensive (opening /proc/stat,
+ As reading the CPU load average is relatively expensive (opening /proc/stat,
parsing it, etc), this only happens once every timer_interval seconds and
consequently the FEEDBACK value is only at these intervals recomputed. This
in turn makes it difficult for the drop rate to adjust quickly. Worst case
@@ -379,7 +379,7 @@ modparam("ratelimit", "pipe", "4:NETWORK:10000")
<function moreinfo="none">rl.stats</function>
</title>
<para>
- Lists the parameters and variabiles in the ratelimit module.
+ Lists the parameters and variables in the ratelimit module.
</para>
<para>
Name: <emphasis>rl.stats</emphasis>
@@ -542,7 +542,7 @@ modparam("ratelimit", "pipe", "4:NETWORK:10000")
<function moreinfo="none">rl.push_load</function>
</title>
<para>
- Force the value of the load parameter. This methos is usefull
+ Force the value of the load parameter. This method is useful
for testing the Feedback algorithm.
</para>
<para>
Module: sip-router
Branch: master
Commit: ca3f80f76ca5be83407f8d8b542c8390982459d4
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=ca3f80f…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Sun Oct 21 18:32:33 2012 +0200
Merge branch 'master' of ssh://git.sip-router.org/sip-router
* 'master' of ssh://git.sip-router.org/sip-router:
modules/rtpproxy: some README improvements
pkg/kamailio/fedora/16: More tweaks to .spec
pkg/kamailio/(centos|fedora): Updated boxgrinder appliance definitions
pkg/kamailio/fedora/16: added SCTP dependencies to .spec
pkg/kamailio/fedora/16: Updated .spec file
Makefiles: Updated Makefiles to use db2x_docbook2man when docbook2x-man is not installed
pkg/kamailio/fedora/16: Updated .spec to set ownership of /etc/kamailio to kamailio.kamailio
modules/websocket: Updated example configuration file
modules/msrp: Updated MSRP configuration example
rtpproxy: allow flags parameter to rtpproxy_destroy()
---
Module: sip-router
Branch: master
Commit: 6135c98b472a755015aacc640b65e9a5c202c122
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=6135c98…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Sat Oct 20 17:47:32 2012 +0200
Documentation updates
---
modules_k/xcap_server/xcap_misc.h | 4 ++--
modules_k/xmpp/README | 4 ++--
modules_k/xmpp/doc/openser-xmpp.cfg | 4 ++--
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/modules_k/xcap_server/xcap_misc.h b/modules_k/xcap_server/xcap_misc.h
index 05476ba..d6cff04 100644
--- a/modules_k/xcap_server/xcap_misc.h
+++ b/modules_k/xcap_server/xcap_misc.h
@@ -7,12 +7,12 @@
*
* This file is part of kamailio, a free SIP server.
*
- * openser is free software; you can redistribute it and/or modify
+ * Kamailo 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
*
- * openser is distributed in the hope that it will be useful,
+ * Kamailo 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.
diff --git a/modules_k/xmpp/README b/modules_k/xmpp/README
index dce2e97..a5605a1 100644
--- a/modules_k/xmpp/README
+++ b/modules_k/xmpp/README
@@ -391,7 +391,7 @@ alias=sip-xmpp.kamailio.org
# ------------------ module loading ----------------------------------
-mpath="/usr/local/openser-1.1.0-xmpp/lib/kamailio/modules/"
+mpath="/usr/local/lib/kamailio/modules/"
loadmodule "sl.so"
loadmodule "tm.so"
loadmodule "rr.so"
@@ -415,7 +415,7 @@ modparam("xmpp", "backend", "server")
# -- mi_fifo params --
-modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo_xmpp")
+modparam("mi_fifo", "fifo_name", "/tmp/kamailio_fifo_xmpp")
# -- usrloc params --
diff --git a/modules_k/xmpp/doc/openser-xmpp.cfg b/modules_k/xmpp/doc/openser-xmpp.cfg
index 1a11a76..106aca2 100644
--- a/modules_k/xmpp/doc/openser-xmpp.cfg
+++ b/modules_k/xmpp/doc/openser-xmpp.cfg
@@ -28,7 +28,7 @@ alias=sip-xmpp.kamailio.org
# ------------------ module loading ----------------------------------
-mpath="/usr/local/openser-1.1.0-xmpp/lib/kamailio/modules/"
+mpath="/usr/local/lib/kamailio/modules/"
loadmodule "sl.so"
loadmodule "tm.so"
loadmodule "rr.so"
@@ -52,7 +52,7 @@ modparam("xmpp", "backend", "server")
# -- mi_fifo params --
-modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo_xmpp")
+modparam("mi_fifo", "fifo_name", "/tmp/kamailio_fifo_xmpp")
# -- usrloc params --