- sr-users - kamailio.org

4.0.4 SEGFAULT again
by Kelvin Chua 05 Dec '13

05 Dec '13

the previous segfault was fixed, now this is a different, i cannot replicate this consistently. randomly crashes. full backtrace: #0 qm_detach_free (frag=0x27d926b4da0, qm=<optimized out>) at mem/q_malloc.c:269 prev = 0x27d923ad0a8 next = 0x0 #1 qm_malloc (qm=0x27d923ad000, size=48) at mem/q_malloc.c:386 f = 0x27d926b4da0 hash = -1841639256 #2 0x0000027d99431c76 in insert_tmcb () from /usr/local/lib64/kamailio/modules/tm.so No symbol table info available. #3 0x0000027d96c0420b in dlg_set_tm_callbacks () from /usr/local/lib64/kamailio/modules/dialog.so No symbol table info available. #4 0x0000027d96c04508 in dlg_onreq () from /usr/local/lib64/kamailio/modules/dialog.so No symbol table info available. #5 0x0000027d9943101b in ?? () from /usr/local/lib64/kamailio/modules/tm.so No symbol table info available. #6 0x0000027d9940f052 in build_cell () from /usr/local/lib64/kamailio/modules/tm.so No symbol table info available. #7 0x0000027d9943bfc6 in t_newtran () from /usr/local/lib64/kamailio/modules/tm.so No symbol table info available. #8 0x0000027d99420cc3 in t_relay_to () from /usr/local/lib64/kamailio/modules/tm.so No symbol table info available. #9 0x000000000041d58b in do_action (h=0x3ff745086c0, a=0x27d9a40c170, msg=0x27d9a458be0) at action.c:1074 ret = -5 v = <optimized out> dst = {send_sock = 0x3ff74507b70, to = {s = {sa_family = 35808, sa_data = "E\232}\002\000\000\370{Pt\377\003\000"}, sin = {sin_family = 35808, sin_port = 39493, sin_addr = {s_addr = 637}, sin_zero = "\370{Pt\377\003\000"}, sin6 = { sin6_family = 35808, sin6_port = 39493, sin6_flowinfo = 637, sin6_addr = {__in6_u = { __u6_addr8 = "\370{Pt\377\003\000\000\340\213E\232}\002\000", __u6_addr16 = {31736, 29776, 1023, 0, 35808, 39493, 637, 0}, __u6_addr32 = {1951431672, 1023, 2588249056, 637}}}, sin6_scope_id = 6372243}}, id = 0, proto = -77 '\263', send_flags = { f = 138 '\212', blst_imask = 74 'J'}} tmp = <optimized out> new_uri = <optimized out> end = <optimized out> crt = <optimized out> cmd = 0x27d9a3eddd8 len = <optimized out> user = <optimized out> uri = {user = {s = 0x3ff74507810 "H", len = -1706983472}, passwd = { s = 0x27d97473a60 "\220\202E\232}\002", len = -1759063584}, host = { s = 0x3000000018 <Address 0x3000000018 out of bounds>, len = 44882432}, port = { s = 0x27d9a3e6be0 "gw::current", len = 11}, params = {s = 0x1 <Address 0x1 out of bounds>, len = -1706983328}, sip_params = {s = 0x3ff74507810 "H", len = -1706718240}, headers = { s = 0x3ff74507b40 "\001", len = -1}, port_no = 39664, proto = 39492, type = 637, flags = 4885171, transport = {s = 0x3ff74508050 "\037\067c", len = 44882432}, ttl = { s = 0x3ff74507b40 "\001", len = 1951431488}, user_param = {s = 0x3ff745086c0 "\003", len = 5148184}, maddr = {s = 0x63371f "", len = -1759094110}, method = { s = 0x27d9a449af0 "0\265?\232}\002", len = 4310469}, lr = {s = 0x27d9a458be0 "F]8", len = -1706761360}, r2 = {s = 0x48 <Address 0x48 out of bounds>, len = -1841596304}, gr = { s = 0x3ff74507890 "@x>\232}\002", len = -1706720624}, transport_val = {s = 0x27d926121a0 "", len = -1707182016}, ttl_val = {s = 0x27d9a449af0 "0\265?\232}\002", len = -1706968808}, user_param_val = {s = 0x27d9a41b918 "\002", len = -1706967088}, maddr_val = { s = 0x27d9a458be0 "F]8", len = 1951434432}, method_val = {s = 0x3ff74507b50 "\037\067c", len = 5170540}, lr_val = {s = 0x0, len = -1713638448}, r2_val = { s = 0x27d9a3e7840 "gw::current", len = 11}, gr_val = {s = 0x0, len = -1706968832}} next_hop = {user = {s = 0x3ff74507b68 "\305\305A", len = -1706718240}, passwd = { s = 0x3ff745086c0 "\003", len = 1951431528}, host = {s = 0x3ff74507b20 "", len = 4885171}, port = {s = 0x13 <Address 0x13 out of bounds>, len = -1706968848}, params = { s = 0x3ff74507b40 "\001", len = -1706718240}, sip_params = {s = 0x3ff745086c0 "\003", len = 5165842}, headers = {s = 0x27d92804290 "\020", len = 5746748}, port_no = 32448, proto = 29776, type = 1023, flags = 0, transport = {s = 0x27d92b1a090 "\002", len = -1765734391}, ttl = {s = 0x0, len = 0}, user_param = { s = 0x3ff74507b60 "\360\232D\232}\002", len = 1951431520}, maddr = { s = 0x800000000 <Address 0x800000000 out of bounds>, len = 9689456}, method = { s = 0x3ff74507a70 "", len = 9598498}, lr = {s = 0x2 <Address 0x2 out of bounds>, len = -1833852784}, r2 = {s = 0x0, len = -1706718240}, gr = {s = 0x27d9a41b8f8 "\a", len = -1765730574}, transport_val = {s = 0x27d96e3c890 "", len = -1765795157}, ttl_val = { s = 0xffffffff00000000 <Address 0xffffffff00000000 out of bounds>, len = -1765722972}, user_param_val = {s = 0x27d98330d4a "<script>: ", len = -1713638448}, maddr_val = { s = 0x27d9a456f00 "@", len = 5746748}, method_val = {s = 0x27d9a469df8 "\006", len = -1707093008}, lr_val = {s = 0x27d9a458be0 "F]8", len = 44882432}, r2_val = { s = 0x27d9a458be0 "F]8", len = -1706965328}, gr_val = {s = 0x27d9a458be0 "F]8", len = 1951434432}} u = <optimized out> port = <optimized out> dst_host = <optimized out> i = <optimized out> flags = <optimized out> avp = <optimized out> st = {flags = 1951432672, id = 1023, name = {n = 0, s = {s = 0x0, len = -1706779920}, re = 0x0}, avp = 0x4ee90f} sct = <optimized out> sjt = <optimized out> rve = <optimized out> mct = <optimized out> rv = <optimized out> rv1 = <optimized out> c1 = {cache_type = 2588249056, val_type = 637, c = {avp_val = {n = 1, s = { s = 0xc00000001 <Address 0xc00000001 out of bounds>, len = 0}, re = 0xc00000001}, pval = { rs = {s = 0xc00000001 <Address 0xc00000001 out of bounds>, len = 0}, ri = -1765782691, flags = 637}}, i2s = "\001\000\000\000\000\000\000\000\244\064\301\226}\002\000\000\037\067c\000\000"} s = {s = 0x1 <Address 0x1 out of bounds>, len = -1765690355} srevp = {0x92763d, 0x27d96c134a4} mod_f_params = {{type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NUMBER_ST, u = {number = 2, string = 0x2 <Address 0x2 out of bounds>, str = {s = 0x2 <Address 0x2 out of bounds>, len = 0}, data = 0x2, attr = 0x2, select = 0x2}}, {type = RVE_FREE_FIXUP_ST, u = { number = 0, string = 0x0, str = {s = 0x0, len = 5}, data = 0x0, attr = 0x0, select = 0x0}}, { type = RVE_FREE_FIXUP_ST, u = {number = 0, string = 0x0, str = {s = 0x0, len = 4}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = { s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = { number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, { type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = { s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}} __FUNCTION__ = "do_action" #10 0x000000000041c5c5 in run_actions (h=0x3ff745086c0, a=0x27d9a405e80, msg=0x27d9a458be0) at action.c:1573 t = <optimized out> ret = <optimized out> mod = <optimized out> ms = 0 __FUNCTION__ = "run_actions" #11 0x000000000041daaa in do_action (h=0x3ff745086c0, a=0x27d9a4498f0, msg=0x27d9a458be0) at action.c:690 ret = -5 v = <optimized out> dst = {send_sock = 0x27d9969e080, to = {s = {sa_family = 0, sa_data = "\000\000\000\000\000\000\037\067c\000\000\000\000"}, sin = {sin_family = 0, sin_port = 0, sin_addr = {s_addr = 0}, sin_zero = "\037\067c\000\000\000\000"}, sin6 = { sin6_family = 0, sin6_port = 0, sin6_flowinfo = 0, sin6_addr = {__in6_u = { __u6_addr8 = "\037\067c\000\000\000\000\000\001\000\000\000\f\000\000", __u6_addr16 = { 14111, 99, 0, 0, 1, 0, 12, 0}, __u6_addr32 = {6502175, 0, 1, 12}}}, sin6_scope_id = 2453371216}}, id = 637, proto = -94 '\242', send_flags = {f = 163 '\243', blst_imask = 67 'C'}} tmp = <optimized out> new_uri = <optimized out> end = <optimized out> crt = <optimized out> cmd = <optimized out> len = <optimized out> user = <optimized out> uri = {user = {s = 0x27d9ab95fb0 "\200\235\024\002", len = 1951432016}, passwd = { s = 0x27d9ab95720 "", len = 34928992}, host = {s = 0x109 <Address 0x109 out of bounds>, len = 44882432}, port = {s = 0x120 <Address 0x120 out of bounds>, len = -1706721952}, params = {s = 0x1 <Address 0x1 out of bounds>, len = 0}, sip_params = {s = 0x63371f "", len = 100}, headers = {s = 0x937560 "", len = 4310469}, port_no = 0, proto = 0, type = ERROR_URI_T, flags = URI_USER_NORMALIZE, transport = { s = 0xfffffffb <Address 0xfffffffb out of bounds>, len = 44882432}, ttl = { s = 0x15 <Address 0x15 out of bounds>, len = -1707088000}, user_param = {s = 0x0, len = 0}, maddr = {s = 0x63371f "", len = -1}, method = {s = 0x27d923b7950 "`\315b\222}\002", len = 4310469}, lr = {s = 0x27d9a458be0 "F]8", len = -1706721952}, r2 = { s = 0x7100000000 <Address 0x7100000000 out of bounds>, len = -1706721696}, gr = { s = 0x1 <Address 0x1 out of bounds>, len = 0}, transport_val = {s = 0x63371f "", len = 100}, ttl_val = {s = 0x937560 "", len = 4315438}, user_param_val = {s = 0x3ff74507e70 "\001", len = 1951432192}, maddr_val = {s = 0x27d9a458be0 "F]8", len = -1707088000}, method_val = { s = 0x1 <Address 0x1 out of bounds>, len = 1951434432}, lr_val = {s = 0x0, len = 1951434432}, r2_val = {s = 0x3ff74508530 "\001", len = -1}, gr_val = {s = 0x27d923b7950 "`\315b\222}\002", len = 4346308}} next_hop = {user = {s = 0x0, len = 1}, passwd = {s = 0x3ff745086c0 "\003", len = -1671675758}, host = {s = 0x3ff745086c0 "\003", len = 1951434032}, port = { s = 0xffffffff <Address 0xffffffff out of bounds>, len = -1841596080}, params = { s = 0xe8d81dd966fc4092 <Address 0xe8d81dd966fc4092 out of bounds>, len = 154943634}, sip_params = {s = 0x3ff00000000 <Address 0x3ff00000000 out of bounds>, len = 8187}, headers = { s = 0x1 <Address 0x1 out of bounds>, len = 1}, port_no = 1, proto = 0, type = ERROR_URI_T, flags = 11, transport = {s = 0xffffffffffffffa0 <Address 0xffffffffffffffa0 out of bounds>, .... cut off Kelvin Chua

1 0

Logging and debugging
by Keith 05 Dec '13

05 Dec '13

Hi guys, Does anyone have any advice to good Kamailio logging and debugging? When you switch on debugging the file grows quickly and with information that isn't really required. My initial idea is to run through the code and make lots of comments but just wanted other peoples ideas/views. Thanks, as always. Keith

2 1

Re: [SR-Users] COR
by Keith 04 Dec '13

04 Dec '13

Thanks, but I need to restrict based on registered user, i.e. some users will be able to dial those numbers others wont. Thanks, Keith

2 1

Considering to release v4.1.0 on Dec4, 2014
by Daniel-Constantin Mierla 04 Dec '13

04 Dec '13

Hello, I have few issues on my list to fix for 4.1 before the full release, but I consider one week being enough time. Therefore I plan to release 4.1.0 next Wednesday, Dec 4, 2014. If anyone would prefer a different plan, expose it on the mailing list for further discussions. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 4

IPv4, IPv6, RTPProxy and Kamailio
by Mark Zeman 04 Dec '13

04 Dec '13

Hello all, The subject says most of it, I think. We set up our Kamailio and RTPProxy according to http://kb.asipto.com/kamailio:kamailio-mixed-ipv4-ipv6 with the addition of an alias (siplab.ch), and the DNS to go with it, as well as TLS and SRTP. However, we only get working calls IPv4-IPv4 and IPv6-IPv6! IPv4-IPv6 we get a proper connection, secured with SRTP, but no audio. Looking at the network, RTP packets go from the caller to the server, but nothing leaves the server and no RTP packets go from callee to server. Do you have any idea how to fix this? Cheers, Mark

3 6

(no subject)
by Abdelkader Allam 04 Dec '13

04 Dec '13

Hello Guys, I am using Kamailio 4.1.0. I am trying to get Kamailio to rotate the cdr log through command kamcmd flatstore.rotate but it keeps sending log to the renamed files, I use the following parameter #!define WITH_ACCFILE # ----- acc params ----- /* what special events should be accounted ? */ modparam("acc", "early_media", 1) modparam("acc", "report_ack", 1) modparam("acc", "report_cancels", 1) /* by default ww do not adjust the direct of the sequential requests. if you enable this parameter, be sure the enable "append_fromtag" in "rr" module */ modparam("acc", "detect_direction", 0) /* account triggers (flags) */ modparam("acc", "log_flag", FLT_ACC) modparam("acc", "log_missed_flag", FLT_ACCMISSED) modparam("acc", "log_extra", "src_user=$fU;src_domain=$fd;src_ip=$si;" "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd") modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) /* enhanced DB accounting */ modparam("acc", "db_flag", FLT_ACC) modparam("acc", "db_missed_flag", FLT_ACCMISSED) #!ifdef WITH_ACCFILE modparam("acc", "db_url", "flatstore:/var/log/kamailio") modparam("db_flatstore", "flush", 1) modparam("acc", "cdr_enable", 1) #modparam("acc", "cdr_flag", 3) modparam("acc", "db_extra","ds=$DLG_lifetime") modparam("acc", "log_extra", "src_user=$fU;src_domain=$fd;src_ip=$si;" "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;" "duration=$DLG_lifetime") modparam("acc", "db_extra", "src_user=$fU;src_domain=$fd;src_ip=$si;" "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;" "duration=$avp(i:256)") #!endif

1 0

Re: [SR-Users] COR
by Keith 04 Dec '13

04 Dec '13

Hi, I want to build in a Class of Restriction in Kamailio so I can allow/deny calls to numbers (countries) based on the caller CLI. Ideally I want to do this in the db but not sure the best way or if there is something to do this already? Cheers. Keith

2 1

"new_t: out_of_mem" errors, yet core.shmmem reports >60% shmmem free
by elactrum＠jamailca.com 04 Dec '13

04 Dec '13

Hi, I have a Kamailio 3.3.3 server that currently reports the following errors upon execution of t_relay() for certain initial INVITEs. daemon.err /usr/sbin/kamailio[26916]: ERROR: <core> [sip_msg_clone.c:505]: ERROR: sip_msg_cloner: cannot allocate memory daemon.err /usr/sbin/kamailio[26916]: ERROR: tm [t_lookup.c:1338]: ERROR: new_t: out of mem: daemon.err /usr/sbin/kamailio[26917]: ERROR: tm [t_lookup.c:1478]: ERROR: t_newtran: new_t failed I understand this error to be related to shared memory, based on [1]. However, sercmd reports normal shared memory utilization: # sercmd core.shmmem { total: 67108864 free: 43189728 used: 20505784 real_used: 23919136 max_used: 65948568 fragments: 36887 } These figures are quite similar to another server with the same configuration and Kamailio version, which is not reporting out-of-memory errors. # sercmd core.shmmem { total: 67108864 free: 40219536 used: 23241952 real_used: 26889328 max_used: 66306288 fragments: 37832 } I recently saw similar symptoms on a Kamailio 4.0.4 server, but Kamailio unfortunately crashed before I could get further details. In this case, I can consistently duplicate the problem with certain INVITEs. It seems that the failure is somehow related to the size of the SIP headers. For example, I have an INVITE from a Polycom phone which t_relay() routes successfully with 741 bytes of headers (total SIP length 1039 bytes). However, it seems that if I add one character to any of its SIP headers (742 bytes of headers; total SIP length 1039 bytes) the t_relay() will consistently fail. This binary doesn't have DBG_QM_MALLOC configured (I am working on getting it re-compiled). However, since I don't know what caused the problem, I would still like to get as much information as I can out of the running system. I have attached the output of mi_statistics, as well as mem_dump_pkg for the external UDP receivers and the ctl handler. Are there any other diagnostics that could be useful? -Andrew [1] http://www.kamailio.org/dokuwiki/doku.php/troubleshooting:faq#qwhat_does_er…

3 3

Trouble getting Siremis up and running
by Mark D. Montgomery II 04 Dec '13

04 Dec '13

I just did a fresh from git install of kamailio and a fresh install of Siremis. Everything seemed to go fine until Siremis gets to the initial login. When I try to login I get a popup window labeled Debug Window with the following contents: System Internal Error The detailed error message are below: [2013-12-01 00:14:08 (GMT)] An exception occurred while executing this script: Error message: #256, Cannot find the class with name as service. Script name and line number of error: /var/www/admin/siremis-4.0.0/openbiz/bin/ObjectFactory.php:157 function: errorHandler ( 256, "Cannot find the class with name as service.", "/var/www/admin/siremis-4.0.0/openbiz/bin/ObjectFactory.php", 157, Array(12) ) @ /var/www/admin/siremis-4.0.0/openbiz/bin/sysheader.inc 117 function: userErrorHandler ( 256, "Cannot find the class with name as service.", "/var/www/admin/siremis-4.0.0/openbiz/bin/ObjectFactory.php", 157, Array(12) ) @ function: trigger_error ( "Cannot find the class with name as service.", 256 ) @ /var/www/admin/siremis-4.0.0/openbiz/bin/ObjectFactory.php 157 function: constructObject ( "service.securityService" ) @ /var/www/admin/siremis-4.0.0/openbiz/bin/ObjectFactory.php 56 function: getObject ( "service.securityService", 0 ) @ /var/www/admin/siremis-4.0.0/openbiz/bin/BizSystem.php 252 function: getObject ( "service.securityService", 0 ) @ /var/www/admin/siremis-4.0.0/openbiz/bin/BizSystem.php 241 function: getService ( "service.securityService" ) @ /var/www/admin/siremis-4.0.0/openbiz/bin/BizController.php 57 function: processSecurityFilters ( ) @ /var/www/admin/siremis-4.0.0/openbiz/bin/BizController.php 31 function: include_once ( "/var/www/admin/siremis-4.0.0/openbiz/bin/BizController.php" ) @ /var/www/admin/siremis-4.0.0/siremis/bin/controller.php 6 Please ask system administrator for help... Report to admin Show Error Please wait a while ... ----------------- Any suggestions on what might be causing this? I'm not sure where to start looking. Thanks. Mark II -- Mark D. Montgomery II http://www.techiem2.net

2 1

How to build Kamailio without FUTEX reference (to use PTHREAD_MUTEX or POSIX_SEM instead)
by Sotas Development 04 Dec '13

04 Dec '13

Hi, I want to build a Kamailio version without the usage of futex. First of all I notice that the variable "use_futex" within Makefile.defs is hardcoded to the value "yes". Why is that? I want to get rid of this and build Kamailio without futex support. In the same file there are GCC options like -DUSE_PTHREAD_MUTEX, -DUSE_POSIX_SEM etc. So I disabled the line use_futex and and added -DUSE_PTHREAD_MUTEX as follows; #use_futex= yes C_DEFS+=-DUSE_PTHREAD_MUTEX After building Kamailio with these options: Although the output of "kamailio -I" indicates that FUTEX is not used (PTHREAD_MUTEX is used instead) it still uses futex sneaky as its locking mechanism. I can see this after catting the content of /proc/<pid>/wchan. This is because Kamailio hangs on futex after running it a while (see our other issue in the topic "Kamailio stability/timing problem w.r.t. registrations?"). Question is; How can I build Kamailio with a locking mechanism other than FUTEX? And why does the solution with Makefile.defs not work? PS: Kernel version is 2.6.30 on an ARM platform Thanks for your support. Kind regards, Orhan Yilmaz

2 1

Re: [SR-Users] [sr-dev] deb specs for 4.1
by Victor Seva 03 Dec '13

03 Dec '13

Hi there, this is my initial effort to get a new version [0]. This will create 4.2.0~dev0 packages for wheezy and jessie at master branch. I've just removed the older releases. I will maintain only this two. If everything is OK I will cherry-pick and create 4.1.0 packages at the 4.1 branch [0] https://github.com/linuxmaniac/kamailio/tree/vseva/deb PD: I've tried to create a personal branch without any luck. Is there any naming restriction on the git repo for that?

2 1

SIREMIS: Configure SIP Trunk/DID/Extension
by Stretchem 03 Dec '13

03 Dec '13

REPOST: Have successfully installed the latest stable Kamailio and Siremis. Have perused countless online Wiki's and other documentation, but can't seem to find any definitive tutorials or answers to the following: 1. Where would I set up a SIP registration to my carrier? (Server Services -> UACReg List?) 2. Where or how would I see the result of that registration? 3. Where would I set up DID's from the above carrier? 4. How would I inbound route those DID's to specific SIP extensions? (Have successfully registered extensions under Subscriber Services -> Subscriber List) 5. How would I outbound route calls from extensions to the carrier in #1? As I understand it, Kamailio settings are stored in a database; Siremis is a web gui to that database. If that is true, then I don't mind knowing the accompanying 'kamctl' commands to accomplish the above, since I'll see the respective settings in the Siremis web gui anyways. Also don't mind paying for the above tutorial, for which I'll turn into a Googlable blog entry. I need a routine or process for which non-CLI associates can make entries/edits. SIP Trunk with DIDs <--> Siremis on Kamailio <--> SIP Extension Thanks in advance.

1 0

deb specs for 4.1
by Daniel-Constantin Mierla 03 Dec '13

03 Dec '13

Initially sent to sr-dev, but maybe some people from users community can help as well... Hello, wondering if any debian/ubuntu fan has some time today/tomorrow morning for updating the specs to include the new modules coming with 4.1. The list is here: - http://www.kamailio.org/wiki/features/new-in-4.1.x Fortunately Peter updated the specs he maintains for rpm-based distros - the one for centos 6 might be useful to figure out dependencies - see in source tree pkg/kamailio/centos/6/. Reply quickly here if you start working on them -- there can be many people, I just want to know how I plan my effort to prepare the release. Thanks, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Hello everyone.
by Yurisbel Jimenez Bermudez 03 Dec '13

03 Dec '13

I'm trying to setup Kamailio everything install correctly but I can't connect to my server with the users created. Not even in my local network it seems like the machine doesn't respond to the packets or maybe the packets are not delivery to my server but when I ping the machine everything is good I'm redirecting the port 5060 to my server same as range ports from 10000 to 20000 but can't connect Any one knows which is the problem here? I'm using Kamailio 4.0 on a virtual machine with virtual box. A copy of the same machine its running a web server of course with a different mac and IP and everything works fine.

2 1

Help required regarding error in Installation
by Owais ul Haq 03 Dec '13

03 Dec '13

Hello all, Have a nice day. I am given a task in office to setup Kamailio-3.1.1 on Fedora 14 machine. Being new to this, I went online for guidance. I got a proper method on the link given below and followed the instructions given. http://www.kamailio.org/dokuwiki/doku.php/install:kamailio-3.1.x-from-git But problem occured when I reached on step 4 i.e "COMPILE KAMAILIO". When I run command "MAKE ALL". Error occurs that asks for file "pcre.h" as shown in photo attached. Can some one please guide me what to do now ? Any help will be appreciated. Thanks. Regards, Kamailio newbie, Owais.

2 2

401 Unauthorized
by Joli Martinez 02 Dec '13

02 Dec '13

Hello all, I am trying to register a sip client to Kamailio. I have added the username password to kamctl and verified it in the opeser db that the user and password are correct. I have other users registered but I am unable to add new users. I keep getting the message below from tcpdump. Also kamctl online is not accurate. I have two other users connected and they dont show up there. [bad udp cksum a8b7!] UDP, length 433 E.......@.......2..........hSIP/2.0 401 Unauthorized Please help Thanks,

2 2

New developer: Luis Martin Gil
by Daniel-Constantin Mierla 02 Dec '13

02 Dec '13

Hello, I want to announce that a new person got developer GIT write access to repository: Luis Martin Gil. He has developed a new module named ndb_cassandra, which offers a connector to cassandra no-sql system directly from configuration style (e.g., for getting/setting items). The module is already part of the master branch since few days ago. His git commit id is: luismartingil My warm welcome and looking forward to future work within the project! Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Next Kamailio World - April 2-4, 2014, in Berlin, Germany
by Daniel-Constantin Mierla 02 Dec '13

02 Dec '13

Hello, I would like to quickly announce the dates and place for next Kamailio World Conference: April 2-4, 2014, in Berlin, Germany. More information is available on the web site: - http://conference.kamailio.com/k01/2013/12/kamailio-world-2014-april-2-4-in… More details will be published in the near future. Looking forward to meeting many of you at the event in Berlin next year, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

forwarding doesn't work
by 1717 02 Dec '13

02 Dec '13

> > Greetings > > 1. Calling sip: mail(a)idd1717.com doesn't ring the forwarded sip uri, any idea? > 2. Can an sip alias name be enabled to be used for sip registration, just like the original user name? > > Thanks > James Wong

2 1

SIREMIS: Configure SIP Trunk/DID/Extension
by Stretchem 01 Dec '13

01 Dec '13

Have successfully installed the latest stable Kamailio and Siremis. Have perused countless online Wiki's and other documentation, but can't seem to find any definitive tutorials or answers to the following: 1. Where would I set up a SIP registration to my carrier? (Server Services -> UACReg List?) 2. Where or how would I see the result of that registration? 3. Where would I set up DID's from the above carrier? 4. How would I inbound route those DID's to specific SIP extensions? (Have successfully registered extensions under Subscriber Services -> Subscriber List) 5. How would I outbound route calls from extensions to the carrier in #1? As I understand it, Kamailio settings are stored in a database; Siremis is a web gui to that database. If that is true, then I don't mind knowing the accompanying 'kamctl' commands to accomplish the above, since I'll see the respective settings in the Siremis web gui anyways. Also don't mind paying for the above tutorial, for which I'll turn into a Googlable blog entry. I need a routine or process for which non-CLI associates can make entries/edits. SIP Trunk with DIDs <--> Siremis on Kamailio <--> SIP Extension Thanks in advance.

1 0

Kamailio for route traffic only
by driver 30 Nov '13

30 Nov '13

Hello, I have such infrastructure: Asterisk1 (provider 1) - IP1 Asterisk2 (provider 2) - IP2 Softphones on client computers with configured two IPs to two Asterisk servers. User has to manually switch between each server. I need to change this that user will have only one account configured (eg. Kamailio) and Kamailio will be used only to forward to Ast1 or Ast2 by previously defined rules. How is it possible? comp1 --------> Kamailio -------> Ast1 comp2 --------> Kamailio -------> Ast1 comp3 --------> Kamailio -------> Ast2 comp4 --------> Kamailio -------> Ast2 Thank you, Marcin

4 3

Some Help with Kamailio v4.0
by Tom Allen 30 Nov '13

30 Nov '13

I am spinning up my first instance of Kamailio and I can't seem to get it to start. I think my issue lies in the kamailio.cfg file, but I don't want to smash that entire file here, it is basically the default. I try to start and get this... root@kh1:/usr/local/etc/kamailio# /etc/init.d/kamailio debug start Starting Kamailio: loading modules under /usr/local/lib/kamailio/modules_k/:/usr/local/lib64/kamailio/modules/ Listening on udp: 127.0.0.1:5060 udp: xxx:5060 udp: 192.168.xxxx:5060 tcp: 127.0.0.1:5060 tcp: xxxx:5060 tcp: 192.168.xxx:5060 Aliases: tcp: kh1:5060 tcp: kh1.xxxx.com:5060 tcp: localhost:5060 udp: kh1:5060 udp: kh1.xxxx.com:5060 udp: localhost:5060 kamailio error, failed to start. I am running a fresh load of Debian .. Linux kh1 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux I am using a mysql backend. Nothing is in production. What else can I provide you to help me figure this out? Thank you. Respectfully, Tom Allen Virtual Technologies Group

2 3

kamailio 4.0.3 - contact header in ACK
by Adnan 29 Nov '13

29 Nov '13

Hi, We are migrating from our openser 1.4 to kamailio 4.0.3 and have run into a couple of issues. One of them is described below and we need to know if it is a known bug or not. Kamailio receives an INVITE from a gateway and finally responds with 200 OK. Then an ACK is generated by the gateway towards the Kamailio that some how does not get relayed to the next hop. The only special aspect here is that the ACK does not contain a Contact header. Is that something that could confuse kamailio and make it unable to relay? According to SIP RFC, a contact header in ACK is not a must have. Our case is the one where ACK is sent by the UAC after receiving a 200 OK final response. Everything else about the ACK looks OK e.g. ACK has a branch different from the the branch value in the UAC INVITE. Is it a a known bug in 4.0.3? In the configuration, we handle ACK as below: if (is_method("ACK")) { if (t_check_trans()) { t_relay(); exit; } else { exit; } Br Adnan

3 4

Dialog module columns not found in .c files
by Grant Bagdasarian 29 Nov '13

29 Nov '13

Hello, Using 4.0.4: I'm getting the following error (removed the values part of the query): 3(2931) ERROR: db_unixodbc [dbase.c:133]: db_unixodbc_submit_query(): rv=-1. Query= insert into Dialogs (HashEntry,HashID,CallID,FromURI,FromTag,ToURI,ToTag,CallerSock,CalleeSock,StartTime,State,Timeout,CallerCSeq,CalleeCSeq,CallerRouteSet,CalleeRouteSet,CallerContact,CalleeContact,SFlags,ToRouteName,req_uri,xdata,iflags ) 3(2931) ERROR: db_unixodbc [con.c:220]: db_unixodbc_extract_error(): unixodbc:SQLExecDirect=42S22:1:207:[FreeTDS][SQL Server]Invalid column name 'req_uri'. The dialog.c file infact doesn't contain the req_uri_column, x_data_column and the iflags_column in static param_export_t mod_params[],static int mod_init(void). The dlg_db_handler.c files does contain them in the beginning of the file and in static int select_entire_dialog_table(db1_res_t ** res, int fetch_num_rows). I haven't checked the other remaining files, but I think the only problem is the renaming of these columns in the kamailio script. Just wondering if anyone else has noticed this?

1 0

what could be the problem here? 500 Invalid routeset?
by Kelvin Chua 29 Nov '13

29 Nov '13

U 2013/11/28 09:06:09.411796 6X.2X1.4.1X5:5060 -> 2X8.1X1.3X.2X:5060 INVITE sip:+18X88X441X1@2X8.1X1.3X.2X SIP/2.0. Record-Route: <sip:6X.2X1.4.1X5;lr=on;ftag=gK0662d671>. Record-Route: <sip:6X.2X1.4.9X;lr=on;ftag=gK0662d671>. Accept: application/sdp. Allow: INVITE,ACK,CANCEL,BYE. Via: SIP/2.0/UDP 6X.2X1.4.1X5;branch=z9hG4bKcff3.da8920b2.0. Via: SIP/2.0/UDP 6X.2X1.4.9X;branch=z9hG4bKcff3.66c425c4.0. Via: SIP/2.0/UDP 192.168.47.68:5060;branch=z9hG4bK06Bbcfc5fb404048790. From: <sip:+18X16X620X3@192.168.47.68;isup-oli=0>;tag=gK0662d671. To: <sip:+18X88X441X1@6X.2X1.4.9X>. Call-ID: 1443253238_103264169(a)192.168.47.68. CSeq: 525 INVITE. Max-Forwards: 47. Contact: <sip:+18X16X620X3@192.168.47.68:5060>. Content-Length: 327. Content-Disposition: session; handling=required. Content-Type: application/sdp. Remote-Party-ID: <sip:+18X16X620X3@192.168.47.68:5060 >;privacy=off;screen=no. . v=0. o=Sonus_UAC 30934 15833 IN IP4 192.168.47.68. s=SIP Media Capabilities. c=IN IP4 6X.2X1.4.9X. t=0 0. m=audio 5770 RTP/AVP 0 18 96 101. a=rtpmap:0 PCMU/8000. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:96 iLBC/8000. a=fmtp:96 mode=30. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=sendrecv. a=maxptime:30. U 2013/11/28 09:06:09.413388 2X8.1X1.3X.2X:5060 -> 6X.2X1.4.1X5:5060 SIP/2.0 183 Session Progress. Record-Route: <sip:6X.2X1.4.1X5;lr=on;ftag=gK0662d671>. Record-Route: <sip:6X.2X1.4.9X;lr=on;ftag=gK0662d671>. Via: SIP/2.0/UDP 6X.2X1.4.1X5;branch=z9hG4bKcff3.da8920b2.0;rport=5060. Via: SIP/2.0/UDP 6X.2X1.4.9X;branch=z9hG4bKcff3.66c425c4.0. Via: SIP/2.0/UDP 192.168.47.68:5060;branch=z9hG4bK06Bbcfc5fb404048790. From: <sip:+18X16X620X3@192.168.47.68;isup-oli=0>;tag=gK0662d671. To: <sip:+18X88X441X1@6X.2X1.4.9X >;tag=bbd932f8f9dbf9743f9b7cadcbf622ac.10eb. Call-ID: 1443253238_103264169(a)192.168.47.68. CSeq: 525 INVITE. Server: kamailio (4.0.4 (x86_64/linux)). Content-Length: 0. . U 2013/11/28 09:06:09.413936 2X8.1X1.3X.2X:5060 -> 6X.2X1.4.1X5:5060 SIP/2.0 100 trying -- your call is important to us. Via: SIP/2.0/UDP 6X.2X1.4.1X5;branch=z9hG4bKcff3.da8920b2.0;rport=5060. Via: SIP/2.0/UDP 6X.2X1.4.9X;branch=z9hG4bKcff3.66c425c4.0. Via: SIP/2.0/UDP 192.168.47.68:5060;branch=z9hG4bK06Bbcfc5fb404048790. From: <sip:+18X16X620X3@192.168.47.68;isup-oli=0>;tag=gK0662d671. To: <sip:+18X88X441X1@6X.2X1.4.9X>. Call-ID: 1443253238_103264169(a)192.168.47.68. CSeq: 525 INVITE. Server: kamailio (4.0.4 (x86_64/linux)). Content-Length: 0. . U 2013/11/28 09:06:10.672460 2X8.1X1.3X.2X:5060 -> 6X.2X1.4.1X5:5060 SIP/2.0 180 Ringing. Via: SIP/2.0/UDP 6X.2X1.4.1X5;rport=5060;branch=z9hG4bKcff3.da8920b2.0. Via: SIP/2.0/UDP 6X.2X1.4.9X;branch=z9hG4bKcff3.66c425c4.0. Via: SIP/2.0/UDP 192.168.47.68:5060;branch=z9hG4bK06Bbcfc5fb404048790. Record-Route: <sip:2X8.1X1.3X.2X;lr;did=873.7d91;nat=yes>. Record-Route: <sip:6X.2X1.4.1X5;lr;ftag=gK0662d671>. Record-Route: <sip:6X.2X1.4.9X;lr;ftag=gK0662d671>. Call-ID: 1443253238_103264169(a)192.168.47.68. From: <sip:+18X16X620X3@192.168.47.68;isup-oli=0>;tag=gK0662d671. To: <sip:+18X88X441X1@6X.2X1.4.9X>;tag=3pOAt1HRTOy9Xfi4Rsbbz9gf73MsuXge. CSeq: 525 INVITE. Contact: <sip:1X5.6X.1X6.2X3:9439>. Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS. Content-Length: 0. . U 2013/11/28 09:06:12.931892 2X8.1X1.3X.2X:5060 -> 6X.2X1.4.1X5:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 6X.2X1.4.1X5;rport=5060;branch=z9hG4bKcff3.da8920b2.0. Via: SIP/2.0/UDP 6X.2X1.4.9X;branch=z9hG4bKcff3.66c425c4.0. Via: SIP/2.0/UDP 192.168.47.68:5060;branch=z9hG4bK06Bbcfc5fb404048790. Record-Route: <sip:2X8.1X1.3X.2X;lr;did=873.7d91;nat=yes>. Record-Route: <sip:6X.2X1.4.1X5;lr;ftag=gK0662d671>. Record-Route: <sip:6X.2X1.4.9X;lr;ftag=gK0662d671>. Call-ID: 1443253238_103264169(a)192.168.47.68. From: <sip:+18X16X620X3@192.168.47.68;isup-oli=0>;tag=gK0662d671. To: <sip:+18X88X441X1@6X.2X1.4.9X>;tag=3pOAt1HRTOy9Xfi4Rsbbz9gf73MsuXge. CSeq: 525 INVITE. Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS. Contact: <sip:1X5.6X.1X6.2X3:9439>. Supported: replaces, 100rel, timer, norefersub. Content-Type: application/sdp. Content-Length:238. . v=0. o=- 3594636366 3594636367 IN IP4 2X8.1X1.3X.2X. s=pjmedia. i=(o=IN IP4 10.0.193.243). c=IN IP4 1X5.6X.1X6.2X3. t=0 0. m=audio 10246 RTP/AVP 0. c=IN IP4 2X8.1X1.3X.2X. a=rtcp:10247. a=sendrecv. a=rtpmap:0 PCMU/8000. a=nortpproxy:yes. U 2013/11/28 09:06:12.960342 6X.2X1.4.1X5:5060 -> 2X8.1X1.3X.2X:5060 ACK sip:1X5.6X.1X6.2X3:9439 SIP/2.0. Record-Route: <sip:6X.2X1.4.1X5;lr=on;ftag=gK0662d671>. Record-Route: <sip:6X.2X1.4.9X;lr=on;ftag=gK0662d671>. Via: SIP/2.0/UDP 6X.2X1.4.1X5;branch=z9hG4bKcff3.da8920b2.2. Via: SIP/2.0/UDP 6X.2X1.4.9X;branch=z9hG4bKcff3.66c425c4.2. Via: SIP/2.0/UDP 192.168.47.68:5060;branch=z9hG4bK06Bbd0344f60e48a125. From: <sip:+18X16X620X3@192.168.47.68;isup-oli=0>;tag=gK0662d671. To: <sip:+18X88X441X1@6X.2X1.4.9X>;tag=3pOAt1HRTOy9Xfi4Rsbbz9gf73MsuXge. Call-ID: 1443253238_103264169(a)192.168.47.68. CSeq: 525 ACK. Max-Forwards: 68. Route: <sip:2X8.1X1.3X.2X:5060;lr;did=873.7d91;nat=yes>. Content-Length: 0. . ------------------------ call goes on a for a while --------------------------- U 2013/11/28 09:06:24.358786 2X8.1X1.3X.2X:5060 -> 6X.2X1.4.1X5:5060 BYE sip:+18X16X620X3@6X.2X1.4.1X5:5060 SIP/2.0. Via: SIP/2.0/UDP 2X8.1X1.3X.2X;branch=z9hG4bKbb1b.267a7326.0. Via: SIP/2.0/UDP 1X5.6X.1X6.2X3:9439;rport=9439;branch=z9hG4bKPj6XR.AckX-G8lRIN4ZuDvjaPB6ZnUpHUa. Max-Forwards: 16. From: <sip:+18X88X441X1@6X.2X1.4.9X>;tag=3pOAt1HRTOy9Xfi4Rsbbz9gf73MsuXge. To: <sip:+18X16X620X3@192.168.47.68;isup-oli=0>;tag=gK0662d671. Call-ID: 1443253238_103264169(a)192.168.47.68. CSeq: 5685 BYE. Route: <sip:6X.2X1.4.1X5;lr;ftag=gK0662d671>. Route: <sip:6X.2X1.4.9X;lr;ftag=gK0662d671>. User-Agent: CSipSimple_m0-16/r2330. Content-Length: 0. . U 2013/11/28 09:06:24.372741 6X.2X1.4.1X5:5060 -> 2X8.1X1.3X.2X:5060 SIP/2.0 500 Invalid routeset. Via: SIP/2.0/UDP 2X8.1X1.3X.2X;branch=z9hG4bKbb1b.267a7326.0. Via: SIP/2.0/UDP 1X5.6X.1X6.2X3:9439;rport=9439;branch=z9hG4bKPj6XR.AckX-G8lRIN4ZuDvjaPB6ZnUpHUa. From: <sip:+18188244111@6X.2X1.4.9X>;tag=3pOAt1HRTOy9Xfi4Rsbbz9gf73MsuXge. To: <sip:+18X16X620X3@192.168.47.68;isup-oli=0>;tag=gK0662d671. Call-ID: 1443253238_103264169(a)192.168.47.68. CSeq: 5685 BYE. Server: Bandwidth.com CLEC. Content-Length: 0. . Kelvin Chua

4 15

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