- sr-users - kamailio.org

Regarding presence conference
by Surendra Pullaiah 28 May '15

28 May '15

Hello Daniel, I am implementing conference bridge using kamalio and RTP porxy without media mixing. Since for now we are ok with this. My question is as per the flow of RFC 4579, UA may send SUBSCRIBE to the conference URI with event as conference. In kamalio modules presence_conference where they mentioned such way that it will support the same what I am looking for. But I simulated using sipP by sending subscriber with conference event. I am not seeing any notify XML which will have the conference users list. One more doubt where it will pick the conference users, since I am not seeing any specific data base table for the same. Can you please clarify what exactly for presence_conference module. Note: I have loaded three modules presence, presence_xml, presence_conference, in route config I am calling handle_subscribe when SUBCRIBE method receives. Regards Surendra India: +91-8124625001

1 0

Kamailio drouting failure not working
by Ali Taher 28 May '15

28 May '15

Dears, I'm trying drouting module in kamailio , it's working good when first gateway in the list is up , yet when first gateway is unrecheable , it's not rerouted to second destination, meaning that fail over is not working. Kindly find attached wireshark trace I'm getting . Below is db entries I'm using : dr_gateways: Dr_gw_lists Dr_groups: Dr_rules: Below is routing block I'm using : request_route{ if (is_method("INVITE")) { if (!do_routing("0")) { send_reply("503", "Test No Rules matching the URI"); exit; } route(10); exit; } } route[10] { if (!do_routing("0")) { xlog("do_routing: No rules matching the URI\n"); send_reply("503","No rules matching the URI"); exit; } if (is_method("INVITE")) { t_on_failure("4"); } route(1); } failure_route[4] { xlog("DEBUG: DROUTING failure route active\n"); if (t_check_status("[34][0-9][0-9]")) { exit; } if (use_next_gw()) { t_relay(); exit; } else { t_reply ("503", "Service not available"); exit; } } route[1] { # send it out now; use stateful forwarding as it works # reliably even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; exit; } Appreciating your prompt reply and assistance. Ali Taher Technical Support Engineer T&F M W A +961-5-457437 Ext 215 +961-70-010600 <http://www.vanrise.com/> http://www.vanrise.com <https://maps.google.com/maps/ms?msa=0&msid=208243362929850217065.0004cbc8d6 12c5f9b4237&ie=UTF8&t=h&vpsrc=0&z=19&iwloc=0004cbc8e4652b4edf71cC:\Users\Mar ie\Documents\My%20Received%20Files> Vanrise Building, Facing Galerie Semaan Hazmiyeh Highway - Beirut, Lebanon Join us at <http://www.facebook.com/pages/Vanrise-Solutions-Offshore/128309743915533> <http://www.linkedin.com/company/vanrise-solutions> <http://twitter.com/VanriseSolution>

3 22

kamailio crash periodically in timer handler
by Péter Barabás 27 May '15

27 May '15

Hi, we have a serious problem with Kamailio v4.2.3, it crashes after some days. We have checked the core dump and the gdb output is the following for bt and full backtrace: #0 0x0000000000602291 in timer_list_expire (t=1432559962, h=0x7f64eb5b6bd0, slow_l=0x7f64eb5ba328, slow_mark=43873) at timer.c:877 #1 0x0000000000602746 in timer_handler () at timer.c:953 #2 0x0000000000602bb9 in timer_main () at timer.c:992 #3 0x00000000004a833c in main_loop () at main.c:1700 #4 0x00000000004ad857 in main (argc=13, argv=0x7fff96697d38) at main.c:2578 #0 0x0000000000602291 in timer_list_expire (t=1432559962, h=0x7f64eb5b6bd0, slow_l=0x7f64eb5ba328, slow_mark=43873) at timer.c:877 tl = 0x7f64ebc3a908 ret = 0 #1 0x0000000000602746 in timer_handler () at timer.c:953 saved_ticks = 1432559962 run_slow_timer = 0 i = 865 __FUNCTION__ = "timer_handler" #2 0x0000000000602bb9 in timer_main () at timer.c:992 No locals. #3 0x00000000004a833c in main_loop () at main.c:1700 i = 4 pid = 0 si = 0x0 si_desc = "udp receiver child=3 sock=127.0.0.1:5060\000\375\362\250/\313\345\v\004\000\000\000\000\000\000\000\004\257\263=\000\000\000\000\200TA\000\000\000\000\000\060}i\226\377\177", '\000' <repeats 19 times>, "{i\226\377\177\000\000\376\366R\000\000\000\000\000\377\377\377\377\377\177\000\000@\350\250\000\000\000\000" nrprocs = 4 __FUNCTION__ = "main_loop" #4 0x00000000004ad857 in main (argc=13, argv=0x7fff96697d38) at main.c:2578 cfg_stream = 0x1b94010 c = -1 r = 0 tmp = 0x7fff96699b17 "" tmp_len = 0 port = 1 proto = 32767 options = 0x703e08 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ret = -1 seed = 2591880768 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x0 p = 0x7fff96697c50 "" __FUNCTION__ = "main" In the logs it can be seen: Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4635]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 21 Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4612]: ALERT: <core> [main.c:784]: handle_sigs(): child process 4623 exited by a signal 11 Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4612]: ALERT: <core> [main.c:787]: handle_sigs(): core was generated Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4612]: INFO: <core> [main.c:799]: handle_sigs(): terminating due to SIGCHLD Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4631]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4628]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4634]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4615]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4617]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4626]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4625]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4624]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4632]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4622]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4621]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4620]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4619]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4618]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4616]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4635]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4614]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4629]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4627]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4633]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4630]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4612]: INFO: <core> [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7f64eca19950/0x7f64eca19988) - ignore Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4612]: INFO: <core> [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7f64ed587f20/0x7f64ed587f58) - ignore Kamailio runs on Ubuntu trusty. The interesting thing that we run Kamailio 4.2.3 in an other environment (on Debian Squeeze) and it works perfect, no crashes. The main difference is that in Debian environment we have less number of users and the firewall is not so strength. But the configuration and the source is the same for both. Please help us to solve this problem. Thanks. Dr. Péter Barabás Director of Software Development Arenim Technologies AB. Mob: +36 70 314 56 57 Tel: +36 1 8 555 602 E-mail: peter.barabas(a)arenim.com<mailto:peter.barabas@arenim.com> Postal: Sweden - 11435 Stockholm, Stureplan 4c, 4th. Floor [Arenim_logo]<http://www.arenim.com/> [CryptTalk_Logo]<http://www.crypttalk.com/>

2 11

Kamailio with public ip, users behind nat
by MtK - SmartMtK 27 May '15

27 May '15

Hi, I'm trying to install Kamailio on a server with a public IP, but my users are mostly at their homes (a.k.a behind NAT). I understood I need to install RTPproxy, but all tutorials out there are for servers behind nat, and they talk about the server's private IP, which does not exists in this case. how would I configure RTPproxy and Kamailio to allow users to subscribe to the server and have audio calls between them? MtK

3 2

dbcassandra schema files
by jay binks 26 May '15

26 May '15

Hi all, Im wondering if anyone can share their schema files for dbcassandra. Ive managed to construct a bunch based on what ive found in git, wiki all over the place, I just want to compare my ones, with some others. specifically the location table. -- Sincerely Jay

2 1

Development open again for master branch
by Daniel-Constantin Mierla 26 May '15

26 May '15

Hello, as branch 4.3 was created to host the upcoming release series 4.3, new features can be now pushed to master branch. They will be part of the next future release, likely to be numbered 4.4. Any fixes that affect existing code in branches 4.3 or older version have to be backported - push first to master and then cherry pick -- some guidelines exemplified with branch 3.2 are available at: - https://www.kamailio.org/wiki/devel/backporting-to-3.2.x As usual, the next future release will be out as stable version in like 8-10 months. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com

1 0

Branch 4.3 created
by Daniel-Constantin Mierla 26 May '15

26 May '15

Hello, the GIT branch 4.3 was created, it will host the release series 4.3.x. To get this branch from GIT, you can use: git clone https://github.com/kamailio/kamailio.git kamailio cd kamailio git checkout -b 4.3 origin/4.3 Notes about installing Kamailio from this branch are available at: - http://www.kamailio.org/wiki/install/4.3.x/git Hopefully in about two weeks or so the full release of 4.3.0 will be out. >From now on, any corresponding fix has to be pushed first to master branch and then cherry-picked to branch 4.3. No new features can get in branch 4.3. Enhancements to documentation or helping tools are still allowed. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com

1 0

Using $avp in evapi:message-received
by DanB 25 May '15

25 May '15

Hey Guys, Was wondering what would be the recommended way to share information between $evapi(msg) received and transaction processors? I have tried $avp() but they do not appear to be available in evapi:message-received route. Trying to avoid here $sht() so I don't need to do extra management to destroy them. Is there any way to "activate" the $avp or $dlg_var based on dialog index, label maybe? Thanks in advance for any kind of tip! DanB //

3 7

info
by Walter Josef 25 May '15

25 May '15

Hi, Do you have any phonenumber for info about your iptel voip phone service ?

2 1

Creating branch 4.3
by Daniel-Constantin Mierla 25 May '15

25 May '15

Hello, I am planning to branch the code for upcoming major release on next Monday, May 25. Testing went fine so far in my side and I don't expect new consistent changes. Any fixes afterwards will be backported as usual to a stable branch. From that moment, master branch will be open again for new features. If someone else has different proposal, let's discuss it on sr-dev mailing list. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com

1 1

Re: [SR-Users] Getting 404 From Kamailio for PRACK
by DanB 24 May '15

24 May '15

Hi Austin, Kamailio will not reject by himself (nor handle) PRACK (or any other methods) unless you tell him so. The logic for handling it should be in your .cfg file. I suggest adding xlog statements through your config script and see where that is rejected. 404 would tell me you are trying to locate your endpoint and send the PRACK there but the endpoint is not registered. DanB

1 0

Re: [SR-Users] Increase Simultaneous Registration
by DanB 24 May '15

24 May '15

Hi Austin, Kamailio should be pretty fast on these things. Here are things which you can check: * Increase number of TCP workers/make sure you are using async TCP. * Use in-memory store for your registrations, not DB ones (at least dump async your contacts in DB). * Make sure you allow enough files to be opened in case of TCP connections (I suspect this is your issue there). Regarding performance tests, not sure if you saw already these links: http://www.kamailio.org/docs/openser-performance-tests/ https://sip-router.org/wiki/performance/v3.0-capacity Hope these help! DanB

1 0

disabling Server header in kamailio
by NITESH BANSAL 22 May '15

22 May '15

Hello, I noticed that Kamailio adds a Server header in the replies generated by it, is there anyway to disable it? Thanks in advance for your help, Nitesh

2 1

Find if client is connected.
by Dmytro Bogovych 22 May '15

22 May '15

Greetings. I want to modify INVITE answers processing in this way: 1) receive INVITE answer 2) check if recipient is registered but has no TCP/TLS connection now 3) suspend answer for 30 seconds (for example) 4) resume answer if REGISTER comes from lost client in these 30 seconds 5) terminate INVITE session if 30 seconds are expired What I do not understand - is it possible to find if client is connected now to kamailio? I talk about TCP/TLS connection only - not about registration record. Thank you!

3 7

issues with domain names in the record route
by NITESH BANSAL 22 May '15

22 May '15

Hello, I am trying to play with domain names in the Record-Route header. This is for a case when kamailio is doing the translation between UDP and TLS, so it is doing double record routing. I want to use the ip addresses on inbound UDP leg and domain names on the outbound TLS leg in record-route headers. I'm doing this by calling the following function -- record_route_preset("xyz.com;transport=tls", "1.1.1.1"); ---- This does the trick of adding a Record-Route in initial TLS invite on the outbound leg: ----------------- Record-Route: <sip:xyz.com;transport=tls;lr=on> Record-Route: <sip:1.1.1.1;lr=on> ---------------- My problems start when the calling party sends a ACK to kamailio over UDP with the Route header Route: <sip:1.1.1.1;lr=on>,<sip:xyz.com;transport=tls;lr=on> I call loose_route() function in config file and as per my expectation, Kamailio should see that both these Route headers belong to Kamailio and it should use Request URI for forwarding the ACK, but unfortunately, Kamailio thinks that xyz.com is some other entity and tries to forward the ACK to xyz.com doing a DNS query. What can i do to avoid this problem, i need kamailio to recognize that "xyz.com" is kamailio as i have a defined an alias in the config file too as follows: alias=xyz.com:5060 Thanks for your help in advance, Nitesh

3 3

rtpproxy 2.0
by Klaus Darilion 22 May '15

22 May '15

Hi! I just found out that there is a new rtpproxy release: http://www.rtpproxy.org/post/v2release/ Has anybody tested it and want to share some experiences? Or have people turned to rtpengine meanwhile? (I am still using rtpproxy 1.2 as I do not need new features). regards Klaus

3 2

Re: [SR-Users] Kamailio proxy for far-end nat traversal
by rahul.ultimate 21 May '15

21 May '15

Hi Daniel I have rtpproxy to perform media relaying. The case where it just timeouts: 1. Client A behind NAT (wifi) calling Client B on 3G Sent from Samsung Mobile -------- Original message -------- From: Daniel-Constantin Mierla <miconda(a)gmail.com> Date:05/05/2015 12:52 (GMT+05:30) To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.sip-router.org> Subject: Re: [SR-Users] Kamailio proxy for far-end nat traversal Hello, do you have rtpproxy or rtpengine for relaying rtp packets? Kamailio is routing only sip packets, you need the rtp relay application to help with media streams. Cheers, Daniel On 01/05/15 13:15, rahul.ultimate wrote: Hello I need a small guidance on creating a light weight proxy which only forwards the msgs to my sip server and also does supports symmetrical nated clients. The way I have created the configuration is a slight modification of : https://github.com/xlab1/sipfe_kamailio/blob/master/kamailio.cfg Problem is unless the sip clients use STUN media packets are not routed. And sometimes even the signalling does not pass through. Should i not use fix_nated_register and switch to fix _ nated_contact always ? Because in all those cases where signalling does not pass through, I see RTO. My best guess is kamailio trying to communicate with private ip. Anything which I can try that you could suggest from the top of yourmind woyld be muc appreciated. Thanks Rahul Sent from Samsung Mobile _______________________________________________ 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 -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com

4 5

XLOG Problem
by Nahum Nir 21 May '15

21 May '15

Hi All, I am using Kamailio 4.0.3 and can't logs. .cfg: #!define WITH_DEBUG ### LOG Levels: 3=DBG, 2=INFO, 1=NOTICE, 0=WARN, -1=ERR #!ifdef WITH_DEBUG debug=4 log_stderror=yes #!else debug=2 log_stderror=no #!endif memdbg=5 memlog=5 log_facility=LOG_LOCAL0 When the server starts there outputs about xlog: 0(20266) DEBUG: <core> [cfg.y:1791]: yyparse(): loading module xlog.so 0(20266) DEBUG: <core> [sr_module.c:499]: load_module(): load_module: module file not found </usr/local/lib/kamailio/modules_k/xlog.so> 0(20266) DEBUG: <core> [sr_module.c:522]: load_module(): load_module: module file not found </usr/local/lib/kamailio/modules_k/xlog/xlog.so> 0(20266) DEBUG: <core> [sr_module.c:564]: load_module(): load_module: trying to load </usr/lib64/kamailio/modules/xlog.so> 0(20266) DEBUG: <core> [sr_module.c:343]: register_module(): register PV from: xlog 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xdbg> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xdbg> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20268) DEBUG: <core> [sr_module.c:935]: init_mod(): DEBUG: init_mod: xlog 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() At the beginning of the Main routing block I put: log("~~~~~~~~~~~~route~~~~~~~~~~~~~~~~~~~~\n"); xdbg("~~~~~~~~~ xdbg - route~~~~~~~~~~~~~~~~~~~~\n"); xlog("L_ALERT","~~~~~~~~~ xlog - route~~~~~~~~~~~~~~~~~~~~\n"); But nothing is logging when I send INVITEs Any help? Thanks, Nir

4 3

Kamailio 4.2.4 segfault and crash
by Federico San Martín 21 May '15

21 May '15

Hi all, I just experienced a sudden crash from one of my Kamailio servers. I'm using v4.2.4 built from git repository (branch remotes/origin/4.2). The error logs show this at the time of the crash (I'm using debug=1 on config file) May 15 15:59:53 KAMAILIO-ERS1 kamailio[21162]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 19 May 15 15:59:53 KAMAILIO-ERS1 kamailio[21141]: ALERT: <core> [main.c:784]: handle_sigs(): child process 21149 exited by a signal 11 May 15 15:59:53 KAMAILIO-ERS1 kamailio[21141]: ALERT: <core> [main.c:787]: handle_sigs(): core was not generated May 15 15:59:53 KAMAILIO-ERS1 kernel: [2156637.186585] kamailio[21149]: segfault at 20b6 ip 00000000000020b6 sp 00007ffeb0c2bc88 error 14 in kamailio[400000+3c3000] May 15 15:59:53 KAMAILIO-ERS1 kernel: [2156637.214933] kamailio[21141]: segfault at 2290 ip 0000000000002290 sp 00007ffeb0c2c4d8 error 14 in kamailio[400000+3c3000] The modules I'm using are: loadmodule "mi_fifo.so" loadmodule "db_mysql.so" loadmodule "sqlops.so" loadmodule "tm.so" loadmodule "sl.so" loadmodule "pv.so" loadmodule "xlog.so" loadmodule "maxfwd.so" loadmodule "siputils.so" loadmodule "sanity.so" loadmodule "textops.so" loadmodule "rr.so" loadmodule "statsd.so" Have you noticed this error before? This server has a very simple config, for every invite received, it queries a MySQL database to replace the called number from 3 digits to 8-10 digits (for example 135 is translated to 1152751135) and sends back a 300 Redirect with the new number. Another thing to notice is that this server was working at 3-4% CPU load and when the issue happen it spiked to 53%... Let me know I can provide any other info that could be useful. Thanks! Federico Federico San Martín Ingeniería de Telefonía TeleCentro S.A. Cnel. Apolinario Figueroa 254 Piso 4to CABA - C1414EDF Fijo : +54 11 3977 10 45 Móvil : +54 9 11 5824 3240 e-mail : fsanmartin(a)telecentro.net.ar

2 3

Clear To-tag on '181 Call Is Being Forwarded'
by John Murray 21 May '15

21 May '15

Hello, I am forwarding an incoming call to a destination and on time-out forward to another and them another. I need to send a '181 Call Is Being Forwarded' to my SBC to reset the early media stream when forwarding to the next destiation which I can do with sl_send_reply("181","Call Is Being Forwarded"). However the SBC vendor requires that the To-tag in the 181 is cleared for this to work. How can I clear the To-tag from this 181 response? Thanks John

2 1

setup dbtext issues
by jaflong jaflong 21 May '15

21 May '15

I need some instructions on how to setup dbtext properly I generated dbtext files through "./kamdbctl create" I then add user through "./kamctrl add user1 user1" It seems to have added the user because when I do the show './kamctl show user1' command it displays [1, ' user1', '10.1.1.1', ' user1', '', 'ee2820706921ce44a3f760e03ff19a22', '9e2c9e7df27f474d2b995c7e94ab32f2', ''] However viewing the subscriber file /usr/local/etc/kamailio/dbtext/subscriber id(int,auto) username(string) domain(string) password(string) email_address(string,null) ha1(string,null) ha1b(string,null) rpid(string,null) There is no entry for 'user1'. Where is it storing the user data and why is it not in the subscriber file?. user1 is not recognised when trying to register 3(20432) DEBUG: db_text [dbt_api.c:80]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[0] at 0x7f9e0dd776c0 3(20432) DEBUG: auth_db [authorize.c:196]: get_ha1(): no result for user 'user1@' Regards

2 1

Debian package kamailio-tls-modules potential bug ?
by jay binks 20 May '15

20 May '15

I just found something odd in the Debian package for kamailio-als-modules and I'm looking for someone to verify it for me. I verified that I'm using Kamailio 4.2 # Kamailio -v version: kamailio 4.2.0 (x86_64/linux) 36e695 the docs http://kamailio.org/docs/modules/4.2.x/modules/tls.html#tls.p.tls_method show that I should be able to use "*TLSv1+" however Kamailio crashes on startup with * [tls_mod.c:287]: mod_init(): Invalid tls_method parameter value I have verified that TLSv1.1 and TLSv1.2 both work, but I can not use TLSv1.1+ or TLSv1+ I also tried TLSv1.0+ ( I found it somewhere on the web ) but this doesn't work either. I used strings against tls.so to see what was available, and this is what I found. strings ~/tls.so | grep TLSv1 TLSv1_client_method TLSv1_server_method TLSv1_method TLSv1_1_client_method TLSv1_1_server_method TLSv1_1_method TLSv1_2_client_method TLSv1_2_server_method TLSv1_2_method TLSv1 TLS method used (TLSv1, SSLv3, SSLv2, SSLv23) TLSv1.1 TLSv1.2 Any idea why this is differs from the docs, or what I'm doing wrong ? -- Sincerely Jay

2 1

Kamailio v4.2.5 Released
by Daniel-Constantin Mierla 19 May '15

19 May '15

Hello, Kamailio SIP Server v4.2.5 stable release is out. This is a maintenance release of the latest stable branch, 4.2, that includes fixes since release of v4.2.5. There is no change to database schema or configuration language structure that you have to do on installations of v4.2.x. Deployments running previous v4.x.x versions are strongly recommended to be upgraded to v4.2.5. For more details about version 4.2.5 (including links and guidelines to download the tarball or from GIT repository), visit: * http://www.kamailio.org/w/2015/05/kamailio-v4-2-5-released/ RPM, Debian/Ubuntu packages will be available soon as well. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com

2 1

log_prefix not working in reply_route
by Klaus Darilion 19 May '15

19 May '15

Hi! Should log_prefix also work for xlog in reply routes? In my case it doesn't (Kamailio 4.2.2) Thanks Klaus

2 3

rtpproxy-ng and late SDP
by Sebastian Damm 19 May '15

19 May '15

Hi, I'm working on a setup, where I have to support late SDP. It is working right now, but I have to use an explicit rtpproxy_offer() when processing the reply to an INVITE without SDP. Is there a way to have rtpproxy_manage() handle those calls automatically? I was thinking of setting a flag in the request which is used by the rtpproxy_manage() function later. Best Regards, Sebastian

3 3

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