Compiling on FreeBSD. Should IMS moduels really be part of default build?
/O
CC (gcc) [M ims_auth.so] cxdx_avp.o
cxdx_avp.c: In function 'cxdx_get_capabilities':
cxdx_avp.c:433: warning: format '%lx' expects type 'long unsigned int', but argument 7 has type 'unsigned int'
cxdx_avp.c:433: warning: format '%lx' expects type 'long unsigned int', but argument 5 has type 'unsigned int'
cxdx_avp.c:433: warning: format '%lx' expects type 'long unsigned int', but argument 6 has type 'unsigned int'
…
[View More]cxdx_avp.c:433: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'unsigned int'
cxdx_avp.c:433: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'unsigned int'
cxdx_avp.c:439: warning: format '%lx' expects type 'long unsigned int', but argument 7 has type 'unsigned int'
cxdx_avp.c:439: warning: format '%lx' expects type 'long unsigned int', but argument 5 has type 'unsigned int'
cxdx_avp.c:439: warning: format '%lx' expects type 'long unsigned int', but argument 6 has type 'unsigned int'
cxdx_avp.c:439: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'unsigned int'
cxdx_avp.c:439: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'unsigned int'
cxdx_avp.c:445: warning: format '%lx' expects type 'long unsigned int', but argument 7 has type 'unsigned int'
cxdx_avp.c:445: warning: format '%lx' expects type 'long unsigned int', but argument 5 has type 'unsigned int'
cxdx_avp.c:445: warning: format '%lx' expects type 'long unsigned int', but argument 6 has type 'unsigned int'
cxdx_avp.c:445: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'unsigned int'
cxdx_avp.c:445: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'unsigned int'
CC (gcc) [M ims_auth.so] cxdx_mar.o
CC (gcc) [M ims_auth.so] rfc2617.o
CC (gcc) [M ims_auth.so] stats.o
CC (gcc) [M ims_auth.so] utils.o
gmake[2]: `libkcore.so.1.0' is up to date.
CC (gcc) [L libkamailio_ims.so.0.1] ims_getters.o
ims_getters.c: In function 'cscf_get_max_expires':
ims_getters.c:260: warning: dereferencing type-punned pointer will break strict-aliasing rules
ims_getters.c: In function 'cscf_get_last_via':
ims_getters.c:763: warning: format '%lx' expects type 'long unsigned int', but argument 7 has type 'unsigned int'
ims_getters.c:763: warning: format '%lx' expects type 'long unsigned int', but argument 5 has type 'unsigned int'
ims_getters.c:763: warning: format '%lx' expects type 'long unsigned int', but argument 6 has type 'unsigned int'
ims_getters.c:763: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'unsigned int'
ims_getters.c:763: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'unsigned int'
LD (gcc) [L libkamailio_ims.so.0.1] libkamailio_ims.so.0.1
LD (gcc) [M ims_auth.so] ims_auth.so
CC (gcc) [M ims_icscf.so] cxdx_avp.o
cxdx_avp.c: In function 'cxdx_get_capabilities':
cxdx_avp.c:431: warning: format '%lx' expects type 'long unsigned int', but argument 7 has type 'unsigned int'
cxdx_avp.c:431: warning: format '%lx' expects type 'long unsigned int', but argument 5 has type 'unsigned int'
cxdx_avp.c:431: warning: format '%lx' expects type 'long unsigned int', but argument 6 has type 'unsigned int'
cxdx_avp.c:431: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'unsigned int'
cxdx_avp.c:431: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'unsigned int'
cxdx_avp.c:437: warning: format '%lx' expects type 'long unsigned int', but argument 7 has type 'unsigned int'
cxdx_avp.c:437: warning: format '%lx' expects type 'long unsigned int', but argument 5 has type 'unsigned int'
cxdx_avp.c:437: warning: format '%lx' expects type 'long unsigned int', but argument 6 has type 'unsigned int'
cxdx_avp.c:437: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'unsigned int'
cxdx_avp.c:437: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'unsigned int'
cxdx_avp.c:443: warning: format '%lx' expects type 'long unsigned int', but argument 7 has type 'unsigned int'
cxdx_avp.c:443: warning: format '%lx' expects type 'long unsigned int', but argument 5 has type 'unsigned int'
cxdx_avp.c:443: warning: format '%lx' expects type 'long unsigned int', but argument 6 has type 'unsigned int'
cxdx_avp.c:443: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'unsigned int'
cxdx_avp.c:443: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'unsigned int'
CC (gcc) [M ims_icscf.so] cxdx_lir.o
In file included from registration.h:49,
from mod.h:68,
from cxdx_lir.c:51:
scscf_list.h:53:20: warning: values.h: No such file or directory
cxdx_lir.c: In function 'async_cdp_lir_callback':
cxdx_lir.c:181: error: 'MAXINT' undeclared (first use in this function)
cxdx_lir.c:181: error: (Each undeclared identifier is reported only once
cxdx_lir.c:181: error: for each function it appears in.)
gmake[1]: *** [cxdx_lir.o] Error 1
gmake: *** [modules] Error 1
jarl#
[View Less]
Hi ,
I am using kamailio 3.3 version. I got the following issue. Please help me.
1) Registered a SIP end point, kamailio added row in location table
2) Now restarted kamailio and registered with another endpoint same account
details so instead of overwriting the previous contact by new one it
inserts another new row in the location table
3) The old entry is not deleted even after the expire time is over because
we are using modparam("usrloc", "db_mode", 1) option.
Anyway we are using save("…
[View More]location", "0x04") so before inserting new row it
should check whether already entry is there or not and then take action.
I look forward to your reply.
Thanks
Ram
[View Less]
Hello!
Just a kind reminder of things discussed that I haven't seen a resolution on:
- Merging modules into *one* directory (my proposal, backed by Juha)
Any pro's and con's?
- The DMQ module status - now "released". Should be "early alpha" is my personal view (my proposal)
Should propably be in a branch or at least marked as under development and needs help.
- Moving core source code into /main directory away from root directory in the source tree (Juha's proposal, backed by me)
…
[View More]Would make it easier for people to discover the README, INSTALL etc :-)
For discussion on one of these topics - please change the topic when you reply so we can follow each thread.
Thanks,
/O
[View Less]
Module: sip-router
Branch: master
Commit: 3cec800fb8e48b6f2dbc880c5a991e9d636c9f5c
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=3cec800…
Author: Jason Penton <jason.penton(a)smilecoms.com>
Committer: Jason Penton <jason.penton(a)smilecoms.com>
Date: Fri Jan 18 14:33:53 2013 +0200
modules_k/statistics: fixed bug when using pvar as stat value (fixup function was broken)
---
modules_k/statistics/statistics.c | 2 +-
1 files changed, 1 insertions(…
[View More]+), 1 deletions(-)
diff --git a/modules_k/statistics/statistics.c b/modules_k/statistics/statistics.c
index 045bd02..3940dde 100644
--- a/modules_k/statistics/statistics.c
+++ b/modules_k/statistics/statistics.c
@@ -172,7 +172,7 @@ static int fixup_stat(void** param, int param_no)
}
if (err==0){
- if (n==0) {
+ if (n==0 && (s.s[0]!='$')) { //we can't check the value of the pvar so have to ignore this check if it is a pvar
LM_ERR("update with 0 has no sense\n");
return E_CFG;
}
[View Less]
Module: sip-router
Branch: master
Commit: a865b622be84ddc1dacff35401adbb6937ec86b3
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=a865b62…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Fri Jan 18 13:32:55 2013 +0100
README - converted to Kamailio
---
README | 58 +++++++++++++++++++++++++++++++++-------------------------
1 files changed, 33 insertions(+), 25 deletions(-)
diff --git a/README b/…
[View More]README
index 6d342ca..e1ee0ba 100644
--- a/README
+++ b/README
@@ -1,11 +1,12 @@
$Id$
- SIP Router (sip-router)
- http://www.sip-router.org/
+ Welcome to Kamailio v4.0!
+
+ http://www.kamailio.org/
==========================
-I. About SIP Router (sip-router)
+I. About Kamailio
II. Feature List
III. Getting started
IV. About the project
@@ -13,28 +14,31 @@ V. Obtaining Help
VI. More Information
-SIP Router (sip-router) is an industrial-strength, free VoIP server based
-on the Session Initiation Protocol (SIP RFC3261).
+Kamailio is an industrial-strength, free server for realtime communication,
+based on the Session Initiation Protocol (SIP RFC3261).
+
It is engineered to power Realtime Communications such as IP telephony and presence
-infrastructures up to large scale.
+infrastructures up to large scale. With embedded support for WebSockets, HTTP,
+MSRP and XMLrpc as well as Json-rpc it's a modern server, up to date with current
+standards.
-The server keeps track of users, sets up multimedia sessions, relays instant
+Kamailio keeps track of users, sets up multimedia sessions, relays instant
messages and creates space for new plug-in applications. Its proven interoperability
guarantees seamless integration with components from other vendors, eliminating the
-risk of a single-vendor trap. SIP Router has successfully participated in various
+risk of a single-vendor trap. Kamailio has successfully participated in various
interoperability tests in which it worked with the products
of other leading SIP vendors.
-The SIP Router software enables a flexible plug-in model for new applications: Third parties
+The Kamailio software enables a flexible plug-in model for new applications: Third parties
can easily link their plug-ins with the server code and provide thereby advanced and
customized services. With a modern RPC interface, 3rd party application can integrate
-and interact with services provided by SIP Router.
+and interact with services provided by Kamailio.
-SIP Router's performance and robustness allows it to serve millions of users and accommodate needs
-of very large operators. With a low-cost dual-CPU, the SIP Router server is able to power
+Kamailio's performance and robustness allows it to serve millions of users and accommodate needs
+of very large operators. With a low-cost dual-CPU, the Kamailio server is able to power
IP telephony services in an area as large as the Bay Area during peak hours.
-The SIP Router is extremely configurable to allow the creation of various routing and
+The Kamailio is extremely configurable to allow the creation of various routing and
admission policies as well as setting up new and customized services. Its configurability
allows it to serve many roles: network security barrier, presence server, application server,
IMS server or PSTN gateway guard (Session Border Controller) for example.
@@ -43,39 +47,43 @@ IMS server or PSTN gateway guard (Session Border Controller) for example.
II. Feature List
================
-See http://www.sip-router.org/ for an updated feature list.
+Please visit http://www.kamailio.org/ for the most up-to-date feature list.
Note that as features easily are added as modules, changes can occur quickly.
-Most of SIP-router's features are implemented as plug-in modules. See
+Most of Kamailio's features are implemented as plug-in modules. See
our web site for a current list.
III. Getting started
====================
-The INSTALL document will guide you through the installation of sip-router.
-SIP-router is composed of a core and additional modules. For each module
+The INSTALL document will guide you through the installation.
+
+Kamailio is composed of a core and additional modules. For each module
there is a README with documentation on how to configure and use the
module. These are available in each modules source code directory as well
-as on the sip-router.org web site.
+as on the kamailio.org web site.
We recommend that you continue with reading README-MODULES and then the
document named INSTALL.
-IV. About sip-router.org
+IV. About kamailio.org
========================
-The SIP Router project was started during the fall of 2008 by developers from
-the OpenSER project, recently renamed to Kamailio.org and SIP Express Router (SER)
-from iptel.org. SIP Router is the result of a merge of the code base and years
+The Kamailio project has roots in a line of projects starting with SIP Express
+Router, then OpenSER and now Kamailio. A merge project was started during the fall
+of 2008 by developers from the OpenSER project, recently renamed to Kamailio.org
+and SIP Express Router (SER) from iptel.org.
+
+Kamailio is the result of a merge of the code base and years
of experience from both developer teams. In release 4.0, during the spring of 2013, the
merger of the products was completed and a unified product was released.
-See http://www.sip-router.org/ for the story of SER, OpenSER/Kamailio and sip-router.org.
+See http://www.sip-router.org/ for the story of SER, OpenSER/Kamailio and kamailio.org.
V. Obtaining Help
=================
-We offer best-effort free support for sip-router. "best-effort" means
+We offer best-effort free support for Kamailio. "best-effort" means
that we try to solve your problems via email as soon as we can,
subject to available manpower.
@@ -89,7 +97,7 @@ VI. More Information
====================
Most up-to-date information is always available at our website,
- http://www.sip-router.org/
+ http://www.kamailio.org/
Particularly, it includes:
- administrator's guide
[View Less]