Module: sip-router
Branch: master
Commit: f9ab230357fcd551252a6bc151b278e792bcb54e
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=f9ab230…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Mon Oct 15 19:45:02 2012 +0200
textopsx - typo fixes, minor corrections
---
modules/textopsx/README | 20 ++++++++++----------
modules/textopsx/doc/functions.xml | 12 ++++++------
modules/textopsx/doc/textopsx.xml | 6 +++---
3 files changed, 19 insertions(+), 19 deletions(-)
diff --git a/modules/textopsx/README b/modules/textopsx/README
index 104638a..e654e05 100644
--- a/modules/textopsx/README
+++ b/modules/textopsx/README
@@ -23,17 +23,17 @@ Daniel-Constantin Mierla
1.1. Overview
- This is a module implementing funtions for text operations over SIP
- messages in configuration files. It comes to add new features similar
- to textops module (textops eXtentions).
+ This module implements functions for SIP message text operations in
+ routing block configurations. It adds new features similar to the
+ textops module (textops eXtentions).
1.2. Functions
1.2.1. msg_apply_changes()
Use this function to apply changes performed on SIP request content. Be
- careful when using this function; due to special handling of changes
- done to SIP message buffer so far, using this function might change the
+ careful when using this function; due to special handling of changes to
+ the SIP message buffer so far, using this function might change the
behaviour of your config. Do test your config properly!
This function can be used from REQUEST_ROUTE.
@@ -54,7 +54,7 @@ if(msg_apply_changes())
1.2.2. change_reply_status(code, reason)
Intercept a SIP reply (in an onreply_route) and change its status code
- and reason phrase prior to propogating it.
+ and reason phrase prior to forwarding it.
Meaning of the parameters is as follows:
* code - Status code.
@@ -74,7 +74,7 @@ onreply_route {
1.2.3. remove_body()
- Use this function to remove body of SIP requests or replies.
+ Use this function to remove the body of SIP requests or replies.
This function can be used from ANY_ROUTE.
@@ -99,11 +99,11 @@ keep_hf("User-Agent");
1.2.5. fnmatch(value, expr [, flags])
- Match the value against the expr using the shell-style pattern for file
+ Match the value against the expr using shell-style pattern for file
name matching (see man page for C function fnmatch()). It is known to
- be faster and uses less-memory than regexp.
+ be faster and use less-memory than regular expressions.
- Parameters flags is optional and can be 'i' to do case insensitive
+ Parameter 'flags' is optional and can be 'i' to do case insensitive
matching.
This function can be used from ANY_ROUTE.
diff --git a/modules/textopsx/doc/functions.xml b/modules/textopsx/doc/functions.xml
index ab4eb06..3fb5736 100644
--- a/modules/textopsx/doc/functions.xml
+++ b/modules/textopsx/doc/functions.xml
@@ -12,7 +12,7 @@
<para>
Use this function to apply changes performed on SIP request content. Be
careful when using this function; due to special handling of changes
- done to SIP message buffer so far, using this function might change
+ to the SIP message buffer so far, using this function might change
the behaviour of your config. Do test your config properly!
</para>
<para>
@@ -42,7 +42,7 @@ if(msg_apply_changes())
</title>
<para>
Intercept a SIP reply (in an onreply_route) and change its status code
- and reason phrase prior to propogating it.
+ and reason phrase prior to forwarding it.
</para>
<para>Meaning of the parameters is as follows:</para>
<itemizedlist>
@@ -78,7 +78,7 @@ onreply_route {
<function moreinfo="none">remove_body()</function>
</title>
<para>
- Use this function to remove body of SIP requests or replies.
+ Use this function to remove the body of SIP requests or replies.
</para>
<para>
This function can be used from ANY_ROUTE.
@@ -122,12 +122,12 @@ keep_hf("User-Agent");
<function moreinfo="none">fnmatch(value, expr [, flags])</function>
</title>
<para>
- Match the value against the expr using the shell-style pattern
+ Match the value against the expr using shell-style pattern
for file name matching (see man page for C function fnmatch()).
- It is known to be faster and uses less-memory than regexp.
+ It is known to be faster and use less-memory than regular expressions.
</para>
<para>
- Parameters flags is optional and can be 'i' to do case insensitive
+ Parameter 'flags' is optional and can be 'i' to do case insensitive
matching.
</para>
<para>
diff --git a/modules/textopsx/doc/textopsx.xml b/modules/textopsx/doc/textopsx.xml
index 25c4f26..a78811e 100644
--- a/modules/textopsx/doc/textopsx.xml
+++ b/modules/textopsx/doc/textopsx.xml
@@ -31,9 +31,9 @@
<section id="textops.overview">
<title>Overview</title>
<para>
- This is a module implementing funtions for text operations over
- SIP messages in configuration files. It comes to add new features
- similar to textops module (textops eXtentions).
+ This module implements functions for SIP message text operations
+ in routing block configurations.
+ It adds new features similar to the textops module (textops eXtentions).
</para>
</section>
In the root directory we have two files that look old and not maintained.
AUTHORS - lists CVS/SVN/GIT committers
We either delete the file or encourage all committers to add themselves.
ISSUES
I have no idea on how old this is, if the issues are in the bug tracker or fixed earlier.
/O
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-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: 3.3
Commit: 35c1a5fb75c52f1adcdf4c3938530751b63a2007
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=35c1a5f…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Mon Oct 15 14:35:10 2012 +0200
INSTALL - Fixing spelling error
---
INSTALL | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/INSTALL b/INSTALL
index aed811a..8519add 100644
--- a/INSTALL
+++ b/INSTALL
@@ -51,7 +51,7 @@ The two major SIP server flavours are:
- Kamailio (former OpenSER)
Starting with version 3.0.0, the two SIP server flavours are built from
-same source code three.
+same source code tree.
SER flavor is the one built by default - historically speaking, it is the
first open source SIP server started in 2001. Kamailio forked from SER in
Hello Kamailio Team,
We have been using kamailio successfully for some time now to test the
functionality of our S/W. Recently we started facing an issue with kamailio
(I don't know whether it's a known issue or not). So thought to drop an
email with the details to see whether we can get a fix for that. The
scenario for the problem set is as follows.
We are running the latest KAMAILIO release 3.3.1 (02nd Aug 2012) release.
When we send out the REGISTER request from the client, the server it turn
returns 200 OK messages to us then we start the call i.e. INVITE with SDP
to other client which is also sends REGISTER request to the same SIP
Server. The call gets CONNECTED and the RTP flow starts both ways peer - to
- peer from one side to another. Now if we move from one subnet of the
same network to another subnet of the same network so the last field of the
private IP address changes from say 192.168.1.XXX to 192.168.1.YYY then at
this time kamailio crashes and this we can see happening all the time with
this scenario. Can you please help us fix this problem. If logs are
required then please tell us how can we generate those and then we can send
out these to you (if required).
Thanks & Best Regards
Saurabh Srivastava
Module: sip-router
Branch: master
Commit: 7d4ed54b5748d70761f2c574a05b7df1c07010b6
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=7d4ed54…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Mon Oct 15 14:35:10 2012 +0200
INSTALL - Fixing spelling error
---
INSTALL | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/INSTALL b/INSTALL
index aed811a..8519add 100644
--- a/INSTALL
+++ b/INSTALL
@@ -51,7 +51,7 @@ The two major SIP server flavours are:
- Kamailio (former OpenSER)
Starting with version 3.0.0, the two SIP server flavours are built from
-same source code three.
+same source code tree.
SER flavor is the one built by default - historically speaking, it is the
first open source SIP server started in 2001. Kamailio forked from SER in
Module: sip-router
Branch: master
Commit: d926b2f942e8fd207c9f50ff9e1edd27a39866bd
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=d926b2f…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Sun Oct 14 21:57:24 2012 +0200
registrar Fix typos in README
---
modules_k/registrar/README | 4 ++--
modules_k/registrar/doc/registrar_admin.xml | 2 +-
modules_k/registrar/doc/registrar_faq.xml | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/modules_k/registrar/README b/modules_k/registrar/README
index 488c068..bff756d 100644
--- a/modules_k/registrar/README
+++ b/modules_k/registrar/README
@@ -302,7 +302,7 @@ modparam("registrar", "default_expires", 1800)
Example 1.2. Set default_expires_range parameter
...
-modparam("registrar", "default_expires", 30) # +- 30% from default_expires
+modparam("registrar", "default_expires_range", 30) # +- 30% from default_expires
...
3.3. min_expires (integer)
@@ -991,5 +991,5 @@ Chapter 2. Frequently Asked Questions
What happened to the desc_time_order parameter?
- It was removed, as its functionality was mmigrate into usrloc module,
+ It was removed, as its functionality was migrated into usrloc module,
were there is a parameter with the same name.
diff --git a/modules_k/registrar/doc/registrar_admin.xml b/modules_k/registrar/doc/registrar_admin.xml
index 79f76bc..91b2832 100644
--- a/modules_k/registrar/doc/registrar_admin.xml
+++ b/modules_k/registrar/doc/registrar_admin.xml
@@ -171,7 +171,7 @@ modparam("registrar", "default_expires", 1800)
<title>Set <varname>default_expires_range</varname> parameter</title>
<programlisting format="linespecific">
...
-modparam("registrar", "default_expires", 30) # +- 30% from default_expires
+modparam("registrar", "default_expires_range", 30) # +- 30% from default_expires
...
</programlisting>
</example>
diff --git a/modules_k/registrar/doc/registrar_faq.xml b/modules_k/registrar/doc/registrar_faq.xml
index 92dc63f..77410a1 100644
--- a/modules_k/registrar/doc/registrar_faq.xml
+++ b/modules_k/registrar/doc/registrar_faq.xml
@@ -109,7 +109,7 @@
</question>
<answer>
<para>
- It was removed, as its functionality was mmigrate into usrloc
+ It was removed, as its functionality was migrated into usrloc
module, were there is a parameter with the same name.
</para>
</answer>