Hi,
after resolving the field type issue :-), i changed the params in kamctlrc
to point to the right DB.
now, i notice that when i use the command "kamctl cr show" iget an error
that it does not find the table "carrierroute".
in the cfg file it is all set and works fine, cr dump is working as
expected as well.
in the kamctl file i can find the param - CARRIERROUTE_TABLE. but where is
it set from?
anyone knows where do i make tha change in order for the kamctl to "know"
the names of the tables i use?
thanks,
Uri
Hello list,
I`ve found a negative phenomenon during startup of kamailio 3.1.x
(orgininally found in version 3.1.5) that results in a core dump,
triggered by the snmpstats module.
During startup of the SIP proxy server machine the linux service
"heartbeat" is responsible for starting required ressources like mysql,
kamailio and snmpd. These services are monitored by the tool "monit".
Monit is supervising the state of the named services and if kamailio is
not up and running, monit is trying to restart the service. During
startup the mysql database takes some time until it is ready to use and
therefore kamailio can`t connect to the database. Monit is detecting
this and restarting kamailio. This is done so often until kamailio is up
and running.
Finally all services are up and running and the machine is working fine.
However, I do not like the core dump that was created during this
"restart phase". As soon as the module "snmpstats" is not used, no core
dump is created any more.
Information about the core dump looks as follows:
(1) output of kamailio log files:
<prefix> kamailio: INFO: <core> [tcp_main.c:4726]: init_tcp: using
epoll_lt as the io watch method (auto detected) <prefix>
/usr/sbin/kamailio[3027]: ERROR: db_mysql [km_my_con.c:109]: driver
error: Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2) <prefix> /usr/sbin/kamailio[3027]:
ERROR: <core> [db.c:289]: could not add connection to the pool <prefix>
/usr/sbin/kamailio[3027]: ERROR: lcr [lcr_mod.c:359]: unable to connect
to the database <prefix> /usr/sbin/kamailio[3027]: ERROR: lcr
[lcr_mod.c:571]: unable to open database connection <prefix>
/usr/sbin/kamailio[3027]: ERROR: <core> [sr_module.c:875]: init_mod():
Error while initializing module lcr (/usr/lib/kamailio/modules/lcr.so)
<prefix> /usr/sbin/kamailio[3027]: INFO: snmpstats [snmpstats.c:387]:
The SNMPStats module got the kill signal <prefix> kamailio: ERROR:
<core> [daemonize.c:307]: Main process exited before writing to pipe
<prefix> kamailio: INFO: <core> [tcp_main.c:4726]: init_tcp: using
epoll_lt as the io watch method (auto detected) <prefix> kamailio:
WARNING: <core> [daemonize.c:352]: pid file contains old pid, replacing
pid <prefix> /usr/sbin/kamailio[3322]: INFO: usrloc [hslot.c:53]: locks
array size 512 <prefix> /usr/sbin/kamailio[3322]: INFO: auth
[auth_mod.c:312]: auth: qop set, but nonce-count (nc_enabled) support
disabled <prefix> /usr/sbin/kamailio[3322]: INFO: pua [pua.c:360]: the
query returned no result <prefix> /usr/sbin/kamailio[3322]: INFO: pike
[ip_tree.c:88]: probing 256 set size <prefix> /usr/sbin/kamailio[3322]:
INFO: <core> [udp_server.c:178]: INFO: udp_init: SO_RCVBUF is initially
111616 <prefix> /usr/sbin/kamailio[3322]: INFO: <core>
[udp_server.c:229]: INFO: udp_init: SO_RCVBUF is finally 262142 <prefix>
/usr/sbin/kamailio[3329]: INFO: mi_datagram [mi_datagram.c:326]: a new
child 0/3329
(2) output of GDB / core file:
Core was generated by `/usr/sbin/kamailio -P
/var/run/kamailio/kamailio.pid -m 1024 -u kamailio -g kama'. Program
terminated with signal 11, Segmentation fault.
[New process 3027]
#0 0xb775539c in freeInterprocessBuffer () at interprocess_buffer.c:354
354 interprocess_buffer.c: No such file or directory.
in interprocess_buffer.c
(gdb)
I know that it is not a fine method in killing kamailio during
initialisation. But I have not found a better way yet. The other modules
like LCR have no problem with the kill signal during initialisation. My
main question is now: how could these core dumps being avoided? Did
anybody have the same experience as me?
Thanks in advance,
Klaus
Hi,
I am trying to get Kamailio to work with CDRTool. In the step of installing
freeradius and adding kamailio's dictionary dictionary.kamailio to
freeradius, I get the following error when starting freeradius -X, which
fails to start:
Error: Errors reading dictionary: dict_init: No ATTRIBUTE "Sip-Method"
defined for VALUE "Other"
Replacing Kamailio's dictionary with OpenSips' one, freeradius starts
correctly. I assume then that there's something missing in Kamailio's
dictionary.
I am using Kamailio v3.2.0 and it's dictionary file.
Any help ?
Thanks :)
RA
Hi All,
I've just installed 3.2.2. I'm using a config that was working fine with
3.1 and all seems ok.
I get one error that I don't get on 3.1 at startup.
kamailio: ERROR: <core> [ppcfg.c:79]: ### added subst expression: /DB/mysql
This is repeated for all SUBST statements in the config.
I get these errors also:
[1293000.484026] INFO: task kamailio:19912 blocked for more than 120
seconds.
[1293000.484081] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[1293000.484169] kamailio D c4608e58 0 19912 19899 0x00000000
[1293000.484173] f6b5d980 00000082 40827cc6 c4608e58 000006cf c1441e20
c1441e20 000000fd
[1293000.484177] f6b5db3c c4608e20 00000000 4085cc46 00049753 ffe3a684
ffffffff f7077bac
[1293000.484180] f6b5d9ac f6b5db3c f6b5d980 c102b2b7 00000001 c4608e20
00000004 00000005
[1293000.484184] Call Trace:
[1293000.484191] [<c102b2b7>] ? check_preempt_wakeup+0x18c/0x202
[1293000.484195] [<c127f55f>] ? __mutex_lock_common+0xe8/0x13b
[1293000.484198] [<c127f5c1>] ? __mutex_lock_slowpath+0xf/0x11
[1293000.484200] [<c127f652>] ? mutex_lock+0x17/0x24
[1293000.484202] [<c127f652>] ? mutex_lock+0x17/0x24
[1293000.484205] [<c123f68b>] ? unix_dgram_recvmsg+0x49/0x1e4
[1293000.484207] [<c10268bd>] ? __wake_up_common+0x34/0x59
[1293000.484210] [<c102a97c>] ? __wake_up_sync_key+0x33/0x49
[1293000.484213] [<c11dd3b0>] ? __sock_recvmsg+0x50/0x58
[1293000.484215] [<c11dd8e7>] ? sock_recvmsg+0x9d/0xb6
[1293000.484218] [<c104a652>] ? autoremove_wake_function+0x0/0x2d
[1293000.484221] [<c1092950>] ? __alloc_pages_nodemask+0xf3/0x4d9
[1293000.484224] [<c108e16b>] ? find_lock_page+0x1b/0x36
[1293000.484227] [<c1025769>] ? kmap_atomic_prot+0xd7/0xfc
[1293000.484230] [<c113cd18>] ? cpumask_any_but+0x20/0x2b
[1293000.484232] [<c11de830>] ? sys_recvfrom+0xc0/0x120
[1293000.484235] [<c1143b63>] ? copy_from_user+0x27/0x10e
[1293000.484237] [<c1025769>] ? kmap_atomic_prot+0xd7/0xfc
[1293000.484240] [<c10a2deb>] ? handle_mm_fault+0x982/0xa22
[1293000.484243] [<c104a652>] ? autoremove_wake_function+0x0/0x2d
[1293000.484246] [<c10baa1d>] ? fsnotify_access+0x5a/0x61
[1293000.484248] [<c11decee>] ? sys_socketcall+0x123/0x1aa
[1293000.484251] [<c100813b>] ? sysenter_do_call+0x12/0x28
19912 is MI datagram. I have been getting these errors since 1.x and what I
normally do is echo 0 > /proc/sys/kernel/hung_task_timeout_secs to get rid
of it.
It must be a module that I am loading. Is this possible to debug? I can
again get rid of the messages but would love to know whats causing it.
BR
Shena
Hi , Sorry for previous email. Hit send too soon .
Good morning,
On my system i've a structure similar to:
SIP Clients SIP Platform
[-------------------] [---------------------------------]
S1 @IP2
S2 @IP3
SIP UACs SIP LB ...
[NATted and @IP1
non Nattted]
SN @IPN
SIP LB is based on Kamailio dispatcher and is responsible of distributing
the load between different Servers SIP UAS.
S1, S2,... SN Servers have a Kamailio Server too which will forward
received balanced traffic to appropiate service (Presence , registrar,...)
Considering SIP LB and all SIP UAS have Public IP, how NAT from the UACs
could be handled on this scenario?
Initially I thought NAT should be handled on SIP LB however I would like
the most simple possible load balancer with no need to read user locations
. Responsible of location users should be S1,S2,..:SN
Then, would it be possible to handle NAT of the SIP UACs *from the SIP UAS
*with NAT Helper module? What i'm afraid is: If all traffic to
S1,S2,..SN comes from SIP LB then nat_helper could think all clients are
NATTed because top most via will be SIP LB.
What I need, I think, is that NAT Helper decides if there is NAT looking
the Via Header added originally by UAC , and not the top most via (which
would be SIP LB). Is that possible? If possible how should i configure Nat
helper for that?
BR
Albert
Hi
I think I got the tcp_crlf_ping and the tcp_keepalive parameters mixed up.
So for tcp_crlf_ping, Kamailio will only respond. While for
tcp_keepalive parameters, if enabled on both server and client, both
will be sending the keepalives, and the receiver will respond.
In order to use tcp_crlf_ping, client's app level rather than TCP level
would have to send the crlfcrlf (pings) and process the crlf (pongs) in
order to detect if Kamailio is up. Is this right?
Yufei
On 03/02/12 11:00, sr-users-request(a)lists.sip-router.org wrote:
> Send sr-users mailing list submissions to
> sr-users(a)lists.sip-router.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
> or, via email, send a message with subject or body 'help' to
> sr-users-request(a)lists.sip-router.org
>
> You can reach the person managing the list at
> sr-users-owner(a)lists.sip-router.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of sr-users digest..."
>
>
> Today's Topics:
>
> 1. TCP keepalive on server and client (Yufei Tao)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 3 Feb 2012 10:33:11 +0000
> From: Yufei Tao <yufei.tao(a)redembedded.com>
> Subject: [SR-Users] TCP keepalive on server and client
> To: <sr-users(a)lists.sip-router.org>
> Message-ID: <4F2BB7E7.2090601(a)redembedded.com>
> Content-Type: text/plain; charset="ISO-8859-1"
>
> Hi
>
> I want to use TCP keepalive to detect dead connections between Kamailio
> and my SIP clients. I've got some questions about this:
>
> 1. If I enable it on Kamailio by setting for example:
>
> tcp_crlf_ping = yes
> tcp_keepalive = yes
> tcp_keepidle = 60
> tcp_keepintvl = 10
> tcp_keepcnt = 3
>
> >From what I read by gooling, that means Kamailio only responds to the
> crlfcrlf sent by the client, but can't be configured to send the
> crlfcrlf. Is this right?
>
> 2. On my client, if I use setsockopt to set the corresponding values:
>
> SO_KEEPALIVE
> TCP_KEEPCNT
> TCP_KEEPIDLE
> TCP_KEEPINTVL
>
> would it make the client send crlfcrlf?
>
> The reason I'm confused is, with these settings, if Kamailio can only
> respond to crlfcrlf, but not send, then would the client only respond
> too, as in 1. and 2., they seem to configure the same set of parameters?
> Please help me clarify this. Thanks very much!
>
> Yufei
>
> --
> Yufei Tao
> Red Embedded
>
> This E-mail and any attachments hereto are strictly confidential and intended solely for the addressee. If you are not the intended addressee please notify the sender by return and delete the message.
>
> You must not disclose, forward or copy this E-mail or attachments to any third party without the prior consent of the sender.
>
> Red Embedded Design, Company Number 06688253 Registered in England: The Waterfront, Salts Mill Rd, Saltaire, BD17 7EZ
>
>
>
> ------------------------------
>
> _______________________________________________
> sr-users mailing list
> sr-users(a)lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
> End of sr-users Digest, Vol 81, Issue 7
> ***************************************
--
Yufei Tao
Red Embedded
This E-mail and any attachments hereto are strictly confidential and intended solely for the addressee. If you are not the intended addressee please notify the sender by return and delete the message.
You must not disclose, forward or copy this E-mail or attachments to any third party without the prior consent of the sender.
Red Embedded Design, Company Number 06688253 Registered in England: The Waterfront, Salts Mill Rd, Saltaire, BD17 7EZ
Hi,
I am trying to make kamailio PCSCF working with rtpproxy (for NAT traversal).
I would like to ask, if there is any tutorial for this, or if you can
give me any advice.
I also have installed rtpproxy package; #!define WITH_NAT, and defined
rtpproxy port in config file...
But this is not working. I noticed, that in default config file of
pcscf is nothing in routing logic with rtpproxy (or it is unnecessary
?), so I try to copy route[RELAY] route[NAT] route[RTPPROXY] modules
from kamailio (no pcscf) config file... but also with no success.
Can you help me please ? What I am doing wrong ? Do you have any
configuration working with rtpproxy ?
Best wishes
Lubo
I am not familiar with Centos but I suspect there is another script being
run from somewhere. What I would do is move the /etc/init.d/kamailio script
somewhere safe (your home directory for eg). Then reboot and see if
kamailio still starts - if it does you need to find out whihc script is
being called and where it is.
If you are not running X by default you are prob in runlevel 3. If you are
running X, then it will be 5. check where you runlevel scripts are
pointing. e.g.
ls -al /etc/rc3.d/SXXkamailio (X = [0-9])
Cheers
Jason
On Wed, Feb 1, 2012 at 4:26 PM, Uri Shacked <uri.shacked(a)gmail.com> wrote:
> Hi,
>
> when i reboot the machine, it starts with 32Mb and i do not understand
> why...
> so, does it use a startup file that i am not familiar with?
> what is the appropriate runlevel? how do i set it and where?
>
> thanks,
> Uri
>
>
> >Hi Sammy,
> >
> >When you use the init script, it is starting Kamailio with the correct
> >arguments to get the environment you wish (-m 2048 probably). If however,
> >you just call kamailio these args are not there. Im not sure why you are
> >running with kamailio command directly. Why don't you add your init script
> >to the appropriate runlevel for auto startup?
> >
> >Cheers
> >Jason
>
> On Wed, Feb 1, 2012 at 3:06 PM, Uri Shacked <ushacked at gmail.com<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>>
> wrote:
>
> >* Hi again....
> *>*
> *>* i installed kamailio 3.2.2 today.
> *>* i used the chkconfig tool to get kamailio run at boot.
> *>* i edited both /etc/init.d/kamailio and /etc/default/kamailio files to
> run
> *>* with 2048Mg of memory.
> *>* now, when i run /etc/init.d/kamailio start, it starts with the right
> *>* amount of memory.
> *>* when i rum "kamailio" only, it starts with 32Mb....
> *>*
> *>* i use centos 6.2 64bit.
> *>* any ideas?
> *>*
> *>*
> *>*
> *>*
> *>*
> *>* On Tue, Oct 25, 2011 at 1:18 PM, Uri Shacked <ushacked at gmail.com<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>>
> wrote:
> *>*
> *>>* Hi.
> *>>* I already checked it all. The kamailio start and stop command did not
> *>>* work. The init script i used was for debian. Now i use another
> script,
> *>>* for centos. It works. I add the kamailio proccess with chkconfig
> tool.
> *>>* Thanks.
> *>>*
> *>>* On 10/25/11, Sammy Govind <govoiper at gmail.com<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>>
> wrote:
> *>>* > Thanks Alex,
> *>>* >
> *>>* > Hey Uri, can you check if you've /etc/init.d/kamailio file exists
> - open
> *>>* > that file if exists and cross verify few parameters.
> *>>* > Few of these are as follows
> *>>* >
> *>>* > PATH=/sbin:/bin:/usr/sbin:/usr/bin
> *>>* > DAEMON=*/usr/local/sbin/kamailio*
> *>>* > NAME=kamailio
> *>>* > DESC=kamailio
> *>>* > HOMEDIR=/var/run/
> *>>* > *PIDFILE*=$HOMEDIR/$NAME.pid
> *>>* > DEFAULTS=*/etc/default/kamailio.default*
> *>>* > RUN_KAMAILIO=yes
> *>>* >
> *>>* > Make sure /etc/default/kamailio.default file exits. here are the
> *>>* contents of
> *>>* > my file.
> *>>* >
> *>>* > RUN_KAMAILIO=yes
> *>>* > USER=kamailio
> *>>* > GROUP=kamailio
> *>>* > MEMORY=64
> *>>* > DUMP_CORE=no
> *>>* >
> *>>* > On Tue, Oct 25, 2011 at 3:38 AM, Klaus Darilion <
> *>>* > klaus.mailinglists at pernau.at<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>>
> wrote:
> *>>* >
> *>>* >> Test the startupscript if they work:
> *>>* >>
> *>>* >> /etc/init.d/kamailio start
> *>>* >> /etc/init.d/kamailio stop
> *>>* >>
> *>>* >> If this works, then make sure to have proper symlinks from the
> *>>* >> corresponding runlevel to the startup script. Do it manually or
> use the
> *>>* >> chkconfig tool.
> *>>* >>
> *>>* >> klaus
> *>>* >>
> *>>* >>
> *>>* >> On 24.10.2011 08:00, Uri Shacked wrote:
> *>>* >>
> *>>* >>> hi again,
> *>>* >>> i found out that on my centos 5.4 the command start-stop-daemon
> that
> *>>* the
> *>>* >>> /etc/init.d/kamailio uses is not recognized.
> *>>* >>> it is kamailio3.2 any ideas?
> *>>* >>>
> *>>* >>>
> *>>* >>> On Mon, Oct 24, 2011 at 3:03 PM, Uri Shacked <ushacked at
> gmail.com <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>
> *>>* >>> <mailto:ushacked at gmail.com<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>>>
> wrote:
> *>>* >>>
> *>>* >>> Hi,
> *>>* >>> what is the best way to start kamailio at boot?
> *>>* >>> the example in the install is not working for me....
> *>>* >>>
> *>>* >>>
> *
>
This email is subject to the disclaimer of Smile Communications (PTY) Ltd. at http://www.smilecoms.com/disclaimer
