sr-users

sr-users@lists.kamailio.org

42 participants
37519 discussions

debuger, debug level and log
by Uri Shacked 08 Feb '12

08 Feb '12

hi, i didn't fully understand the differences between the debug level set at the Global Parameters section and the debugger module. i would like to start kamailio with debug level 0, and to be able to raise or lower the level in command line. the log is set to be writen to /var/log/kamailio, and i can trace it using "tail". so, anyideas how to use the debug options with the option to change level at runtime? BR, Uri

2 1

High Availability for ongoing calls
by Mariana Arduini 07 Feb '12

07 Feb '12

Hi guys! I'm facing some problems with dialog information while trying to implement a HA environment. We have 2 clustered SIP servers working as a Active/Standby failover and the use of a Virtual IP address. We want to make sure that if proxy #1 goes down during a call, proxy #2 would be able to handle the sequential requests for that call, since both proxies are using the same database for dialog module information and we have set the db_mode dialog parameter to 1 (REALTIME - any dialog information changes will be reflected into the database immediately). Instead, what happened is proxy #2 was not aware of the dialog and gave us a "500 Server error occurred" message after receiving the BYE. Here are the log errors: /usr/local/sbin/opensips[12617]: New request: BYE /usr/local/sbin/opensips[12617]: The request has TO tag /usr/local/sbin/opensips[12617]: cannot match request to a dialog /usr/local/sbin/opensips[12617]: ERROR:dialog:w_validate_dialog: null dialog /usr/local/sbin/opensips[12617]: in-dialog bogus request /usr/local/sbin/opensips[12617]: validate_dialog return: -4 /usr/local/sbin/opensips[12617]: loose_route() performed, rr headers were decoded /usr/local/sbin/opensips[12617]: ERROR:core:parse_uri: uri too short: <0> (1) /usr/local/sbin/opensips[12617]: ERROR:core:parse_sip_msg_uri: bad uri <0> /usr/local/sbin/opensips[12617]: ERROR:tm:new_t: uri invalid /usr/local/sbin/opensips[12617]: ERROR:tm:t_newtran: new_t failed /usr/local/sbin/opensips[12617]: Could not execute t_relay() Virtual IP address is working, a new call goes through with no problem. Apparently, the dialog module is not saving all dialogs information to the database right away. Does anyone know about any other info we should be storing in the database, using some sort of module parameter or exported function from config file? In other words, what do I need to do in order to send an initial INVITE to one server and, when that server goes down, send the BYE to another server with the same call dialog? Thanks in advance. Mariana.

2 2

FreeBSD comiling problem
by Serhat AKCA 07 Feb '12

07 Feb '12

Hello I want to run Kamailio under FreeBSD. I compiled with the makefiles under freebsd packages. But It gives alotof errors. I want to use 3.2.2 version but I cannot compile. Could you help me To compile in FreeBSD ? Another question, which is the best OS for Kamailio ? In the forums, they are saying FreeBSD is more stable and More performans. Regards Serhat

4 3

Proxy topology question
by Greg Mannie 06 Feb '12

06 Feb '12

Hello After much reading I have come to the realization that after years of using Asterisk I know very little about Sip. I have my Kamailio box up, I have Asterisk 1.8.x running with realtime working. I thought it would be just a case of registering SIP trunks from my provider to the kamailio and registering our internal asterisk servers to the kamailio. Much of what I read talks about using Asterisk as the PSTN interface, but that interface is through a sip trunk purchased from a provider. Won't Kamailio be the PSTN gateway? The idea here is to pool all the sip trunks from the various hosted asterisk solutions (VM running asterisk) and point them all to a proxy to facilitate the aggregation of traffic. I have been reading SIP tutorials and the mailing list archives. If anyone has a sample config and perhaps a little direction it would be highly appreciated. Thank you Greg

2 5

loading carrierroute failes using another DB
by Uri Shacked 06 Feb '12

06 Feb '12

Hi, I changed the location of the DB kamailio works with. i copied the relevalt tables and changed the relevant names in the cfg file. while trying to load kamailio i realized that it misses the "veresion" table. first - can someone explain the version table usage? second, after creating and copying that data from the version table. i tried to load kamailio again and got the follwing: " DEBUG: carrierroute [cr_db.c:345]: loading, cycle 0 0(24689) ERROR: <core> [daemonize.c:307]: Main process exited before writing to pipe" any help? thanks, Uri

2 3

"kamctl cr show" when carrierroute table has another name
by Uri Shacked 06 Feb '12

06 Feb '12

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

1 0

Kamailio 3.1.5 core dump from the snmpstats module
by Klaus Feichtinger 06 Feb '12

06 Feb '12

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

2 2

Kamailio, Freeradius and CDRTool
by Reda Aouad 05 Feb '12

05 Feb '12

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

1 1

3.2.2
by dotnetdub 03 Feb '12

03 Feb '12

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

1 1

question about NAT being behind of a Load Balancer
by Albert Petit 03 Feb '12

03 Feb '12

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

2 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users