Hello,
I am trying to understand kamailio.cfg parameters. Can some one please help me in understanding what these parameters do exactly when set. tcp_keepalive, tcp_keepidle and tcp_connection_lifetime. I have a general understanding of tcp. Want to know exact role of these parameters in kamailio.cfg.
Thanking in advance.
Cheers
hey guys.
I was trying to add the htable routing rules here:
http://preview.tinyurl.com/nomqsls
but I need some help figuring our where they should go. See, I really like
how this guy bans users for 15 minutes for failing to auth 3 times in a
row. Where and how should I add this to my kam config?
Any help would be greatly appreciated.
Thanks
Hello Andrew,
I did not know this function. I am using it to determine the direction of the flow.
Thank you
> ----- Original Message -----
> From: Andrew Pogrebennyk
> Sent: 01/24/14 06:51 AM
> To: Kamailio (SER) - Users Mailing List
> Subject: Re: [SR-Users] Kamailio behind NAT
>
> On 01/23/2014 05:12 PM, Klaus Darilion wrote:
> >> It is necessary to use the cwie / cwei flags in the rtpproxy_manage call?
> >
> > If rtpproxy uses only a single listen-IP, then these flags are not
> > needed. Only if you operate rtpproxy in bridge mode, then you need these
> > flags. Bridge mode is necessary if you do not have IP routing between
> > the internal network and the "virtual external" network, or if you want
> > to bridge between IPv4 and IPv6.
>
> John,
> This function can be used to check the direction of every message:
> http://kamailio.org/docs/modules/4.0.x/modules/rr.html#idp223296
> You might also need to append the record-route parameters to remember
> the flags you have passed to the manage_rtpproxy() initially.
> Based on the direction of the request and initial flags you can
> determine what flags to use when calling manage_rtpproxy() for a given
> in-dialog requests and reply.
>
> Hope this helps.
> Andrew
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users(a)lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hello Fred,
calls are being bridged across two interfaces: one natted from the outside with one public IP and one directly connected to the Asterisk.
> ----- Original Message -----
> From: Fred Posner
> Sent: 01/24/14 06:55 AM
> To: Kamailio (SER) - Users Mailing List
> Subject: Re: [SR-Users] Kamailio behind NAT
>
> On 01/24/2014 09:51 AM, Andrew Pogrebennyk wrote:
> > On 01/23/2014 05:12 PM, Klaus Darilion wrote:
> >>> It is necessary to use the cwie / cwei flags in the rtpproxy_manage call?
> >>
> >> If rtpproxy uses only a single listen-IP, then these flags are not
> >> needed. Only if you operate rtpproxy in bridge mode, then you need these
> >> flags. Bridge mode is necessary if you do not have IP routing between
> >> the internal network and the "virtual external" network, or if you want
> >> to bridge between IPv4 and IPv6.
> >
> > John,
> > This function can be used to check the direction of every message:
> > http://kamailio.org/docs/modules/4.0.x/modules/rr.html#idp223296
> > You might also need to append the record-route parameters to remember
> > the flags you have passed to the manage_rtpproxy() initially.
> > Based on the direction of the request and initial flags you can
> > determine what flags to use when calling manage_rtpproxy() for a given
> > in-dialog requests and reply.
> >
> > Hope this helps.
> > Andrew
> >
>
> Are the calls being bridged across two interfaces or is the Kamailio
> just natted? (or is it both?)
>
> Fred Posner
> The Palner Group, Inc.
> 503-914-0999 (direct)
> 954-472-2896 (fax)
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users(a)lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
I am trying to manually rewrite the RURI for a certain scenario.
The RURI is currently:
sip:110219546496707@12.12.12.12;npdi;rate=0.000880
I want to re-write so it's just:
sip:110219546496707@12.12.12.12
I have the following snippet which isn't working:
xlog("L_INFO","sip:$(ruri{uri.user})@$(ruri{uri.host})");
$ru = "sip:$(ruri{uri.user})@$(ruri{uri.host})";
t_relay();
the log spits out exactly what I want, but writing the $ru variable results
in:
Jan 29 18:59:36 dev-sipgateway /usr/local/sbin/kamailio[23042]: ERROR:
<core> [resolve.c:1733]: sip_hostport2su(): ERROR: sip_hostport2su: could
not resolve hostname: "$(ruri{uri.host})"
Jan 29 18:59:36 dev-sipgateway /usr/local/sbin/kamailio[23042]: ERROR: tm
[ut.h:337]: uri2dst2(): failed to resolve "$(ruri{uri.host})"
Jan 29 18:59:36 dev-sipgateway /usr/local/sbin/kamailio[23042]: ERROR: tm
[t_fwd.c:1773]: t_forward_nonack(): ERROR: t_forward_nonack: failure to add
branches
Jan 29 18:59:36 dev-sipgateway /usr/local/sbin/kamailio[23042]: ERROR: tm
[tm.c:1502]: _w_t_relay_to(): ERROR: w_t_relay_to: t_relay_to failed
Jan 29 18:59:36 dev-sipgateway /usr/local/sbin/kamailio[23042]: ERROR: tm
[t_reply.c:1067]: run_failure_handlers(): ERROR: run_failure_handlers:
Error in run_top_route
Any hint would be greatly appreciated.
Hello,
the current server hosting the apt repositories for debian and ubuntu is
scheduled for replacement. It hasn't been updated with new packages in a
while.
Courtesy of Sipwise, a new build system is under development and should
be available in the near future.
Meanwhile, we plan to clone the existing packages to another server and
have them available till the new system is up and running.
As all these involve operations requiring DNS change and file transfer,
the repositories might be unavailable from time to time.
Many thanks to Jon Bonilla that took care of building the deb packages
so far and Inaki Baz Castillo for hosting the afferent repositories.
Note also that all Kamailio packages for latest version are also
available via the official repositories from Debian unstable (sid) -
thanks to Victor Seva for the work on it. Perhaps testing will get them
soon and with the next stable version, should be no longer needed to use
our repositories by users of Debian. We plan to keep ours as well.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Regarding the sem_post problem, here is an old email from Tomasz
Gebarowski which is interesting because it states that he had a
sem_post issue with cdp.so which he solved by modifying the
modules/cdp/Makefile. Now if we skip forward to right now, I notice that
cdp.so COMPILE and LINKS for me with no errors and I also notice that
Tomasz' fix is in place, but other ims modules that also use semaphore do
NOT link properly for me in ubuntu and are exhibiting the same *undefined
symbol: sem_post* error Tomasz had years ago in his ubuntu compiles. I
think (hope) this may be more than coincidence that these things are
related??? I have tried Tomasz' fix with an ubuntu compile but I still get
the sem_post error. I still think he is on to something here and I am NOT
modifying the Makefile correctly. Any suggestions on specifics to test this
theory are greatly welcome. Here is Tomansz' email.....
----------------------------------------------------------------------------------------------------------------------
https://lists.berlios.de/pipermail/openimscore-users/2011-December/007219.h…
[OpenIMSCore-Users] PROBLEM WITH ICSCF AND SCSCF STARTING
Tomasz Gebarowski gebarowski at gmail.com
Thu Dec 29 22:19:55 CET 2011
Previous message: [OpenIMSCore-Users] Fwd: How are you...
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello,
I've just googled some old post from October 2011, describing an issue
with crashing I-CSCF and S-CSCF. The log message was something like:
0(2142) ERROR: load_module: could not open module /opt/OpenIMSCore/ser_ims/
modules/cdp/cdp.so>: /opt/OpenIMSCore/ser_ims/modules/cdp/cdp.so:
undefined symbol: sem_post
I managed to fix this issue on Ubuntu 11.10. It seems that UBUNTU,
required linking cdp.so against pthread. Below you can find a simple patch:
Index: modules/cdp/Makefile
===================================================================
--- Makefile (revision 1175)
+++ Makefile (working copy)
@@ -20,7 +20,7 @@
endif
DEFS += -I/usr/include/libxml2
-LIBS += -L$(LOCALBASE)/lib -lxml2 -lrt
+LIBS += -L$(LOCALBASE)/lib -lxml2 -lrt -lpthread
include ../../Makefile.modules
===================================================================
Regards,
Stuart Feeser
Hi all,
I'm wondering if someone can help me get a little unstuck.
I followed the guide here:
http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb
And I now have kamailio running, but I have two problems.
Number 1
When I do kamctl add user password and make two users, they register fine.
But any attempt to call between the users times out.
Number 2
Anytime I have my kamailo.cfg file begin as
#!KAMAILIO
#!define WITH_MYSQL#!define WITH_AUTH#!define WITH_USRLOCDB#!define
WITH_ASTERISK
I am unable to start kamctl. I get the following error.
ERROR: PID file /var/run/kamailio.pid does not exist -- Kamailio start
failed
If I run kamailio I get
ERROR: bad config file (3 errors)
The moment I remove the define lines at the start, kamctl starts fine, but
I can't authenticate with asterisk.
Any ideas?
Thanks
Chirag
Hello there,
I just ran the static analyser "cppcheck" over the source code
of ser-0.9.6
It said many things, including
1.
[parser/parse_uri.c:566] -> [parser/parse_uri.c:568]: (warning) Variable 'state' is reassigned a value before the old one has been used. 'break;' missing?
Source code is
case 'r':
case 'R':
b=p;
state=PR2_R;
default:
state=URI_PARAM_P;
Suggest add missing break.
2.
> [parser/parse_uri.c:624] -> [parser/parse_uri.c:624]: (warning) Variable 'state' is reassigned a value before the old one has been used. 'break;' missing?
> [parser/parse_uri.c:628] -> [parser/parse_uri.c:628]: (warning) Variable 'state' is reassigned a value before the old one has been used. 'break;' missing?
> [parser/parse_uri.c:631] -> [parser/parse_uri.c:631]: (warning) Variable 'state' is reassigned a value before the old one has been used. 'break;' missing?
> [parser/parse_uri.c:636] -> [parser/parse_uri.c:636]: (warning) Variable 'state' is reassigned a value before the old one has been used. 'break;' missing?
Duplicates.
Regards
David Binderman
Hello Everyone,
We are currently using the DR module for routing and failover, and would
like to replace it with
equivalent functionality using perl script. What we would like is to:
* Order the gateways in a strict list given some constraints (Completed)
* Build the RURI with the gateway IP, and prefix from the dr_gateways table
(Similar to what do_routing does with the FROM tag and dr_gateways
information)
* Failover to the next gateway in strict order.
I would really like to know what our options are, and the most
graceful/scalable way of implementing
this.
PS An example would be highly appreciated!
Kind Regards,
Nick
