I noticed that Daniel had a macro called &kamailio for the software
name.
I would like one for in text with the name "SIP-router" and one for
the binary "sr" or whatever you want.
What's the best current practise?
/O
Revision: 5937
http://openser.svn.sourceforge.net/openser/?rev=5937&view=rev
Author: mariuszbihlei
Date: 2009-10-12 12:06:07 +0000 (Mon, 12 Oct 2009)
Log Message:
-----------
Strip is 0 in the case the user is "<null>", and should be ignored.
Modified Paths:
--------------
branches/1.5/modules/carrierroute/cr_func.c
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Revision: 5936
http://openser.svn.sourceforge.net/openser/?rev=5936&view=rev
Author: mariuszbihlei
Date: 2009-10-12 11:14:58 +0000 (Mon, 12 Oct 2009)
Log Message:
-----------
If the user parameter is "<null>" (e.g a empty username in the request URI), do not copy this value to the rewritten uri.
This is the case of a REGISTER request. Added statements that the parameters to the actually_rewrite func may not be null.
Modified Paths:
--------------
branches/1.5/modules/carrierroute/cr_func.c
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Hi all,
My SER process had crashed today with the following logs
in /var/log/messages :
ser[378]: child process 418 exited by a signal 11
ser[378]: core was generated
ser[378]: INFO: terminating due to SIGCHLD
ser[421]: INFO: signal 15 received
...
Can someone help me to determine what kind of problem is it ? I think I
need to use gdb to extract some information from the core dump. How can
I use it to extract the uses informations ?
Regards,
Adrien
Module: sip-router
Branch: master
Commit: cbfe9a14fdb05e8212ba4a0b24472f5239850a77
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=cbfe9a1…
Author: oej <oej(a)edvina.net>
Committer: oej <oej(a)edvina.net>
Date: Sat Oct 10 21:48:04 2009 +0200
Changing legal template to sip-router standard
Daniel - please check that this is ok for you.
---
modules/mi_rpc/mi_rpc_mod.c | 36 ++++++++++++++++++++++++++----------
1 files changed, 26 insertions(+), 10 deletions(-)
diff --git a/modules/mi_rpc/mi_rpc_mod.c b/modules/mi_rpc/mi_rpc_mod.c
index b678f25..de9db37 100644
--- a/modules/mi_rpc/mi_rpc_mod.c
+++ b/modules/mi_rpc/mi_rpc_mod.c
@@ -5,19 +5,35 @@
*
* Copyright (C) 2009 Daniel-Constantin Mierla (asipto.com).
*
- * Permission to use, copy, modify, and distribute this software for any
- * purpose with or without fee is hereby granted, provided that the above
- * copyright notice and this permission notice appear in all copies.
+ * This file is part of SIP-router, a free SIP server.
*
- * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
- * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
- * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
- * ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
- * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
- * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
- * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+ * 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
+
+ */
+
+/*!
+ * \file
+ * \brief Management interface :: RPC support
+ * \ingroup mi_rpc
+ */
+
+/*!
+ * \defgroup mi_rpc Management interface :: RPC support
*/
+
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
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
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.
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.