- sr-users - kamailio.org

Relay Latency
by Daniel Greenwald 03 May '18

03 May '18

We are using kamailio 5.0 as an inbound dispatcher. Sometimes in testing we see it take over half a second to relay a 200 OK. The logs show the new dialog being creating for the 200 OK within .0001 seconds of receiving the inbound 200 but it takes another .5 seconds for the relayed 200 to actually hit the wire. Here is a screenshot showing the timing of the packets. The box is an EC2 m3.medium under almost zero load (1-2 calls). Is this normal? What should I be looking at? Screenshot below: 10.0.23.34 is the kamailio box. Carrier IP obfuscated. You can see the carrier resends the 200 OK because of the delay.

3 6

Kamailio with dispatcher not send BYE to Asterisk.
by Jeferson Oliveira 03 May '18

03 May '18

Hello everyone, I have an error that I have not yet been able to solve and would like the help of colleagues to indicate a correct path. The problem that is occurring is that when the client disconnects the call kamailio is not sending the BYE forward until arriving at the asterisk. Both in the test scenario and in the production scenario the problem is the same and the message I see in the capture is 404 Not here, msg this coming from kamailio. Production scenario. PSTN <----------> Dialer --------->kamailio -----------> asterisk1 -----------> asterisk2 Test scenario. sipp generated calls ------> kamailio -------> asterisk1 -------> asterisk2 When this occurs, the calls that are disconnected by the client are in a "zombie" state in asterisk, and end up being terminated by timeout with the following message in the asterisk CLI: /[Apr 25 17:49:59] WARNING[2121]: chan_sip.c:4072 retrans_pkt: Retransmission timeout reached on transmission 22-6073(a)10.110.7.242 for seqno 1 (Critical Response) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions// //Packet timed out after 31999ms with no response/ In the sipp panel I see in the Retransmission column several incrementing counters, as per the attachment. If I take the kamailio from the move and point the sipp to only one of the asterisk, the retransmissions do not happen and BYE follows normally. My kamailio.cfg configuration file can be downloaded from this url: https://drive.google.com/file/d/1bBj4GEZSPrp1iJXSLWQ4Z6g59tEFjnNT/view?usp=… Thank you very much. --

4 8

Record-Route and received/rport parameters
by Asgaroth 03 May '18

03 May '18

Hi All, I've come accros a scenario where a proxy is sitting on a private address range and inserts a record-route specifying the the private address. This causes issues whereby the BYE to an INVITE attempts to relay to the private address defined in record-route. I was wondering, if we were inject a received and rport parameter into the record-route header of the original invite, whould kamailio relay the response (BYE) to the receive/rport destination instead of the uri defined in the record-route header. As an example, initial invite comes in with a record-route as follows: Record-Route: <sip:172.17.0.2:5062;lr;ftag=b4551d29> If we injected received and rport as follows: Record-Route: <sip:172.17.0.2:5062;lr;ftag=b4551d29;rport=33429;received=212.172.2.212> and relayed the message to the B2B. Then, I assume, when the B2B creates its BYE message, the Route header should look like this: Route: <sip:172.17.0.2:5062;lr;ftag=b4551d29;rport=33429;received=212.172.2.212> Once this hits the kamailio instance to relay to the last route header as mentioned above, would it set $du to received:rport like it does with Via headers? Thanks

2 4

DMQ and/or Database for dialogs, registrations, etc..
by Joel Serrano 03 May '18

03 May '18

Hi all, Just wanted to know what your opinions were on using DMQ modules over database for things like dialog replication, registrations, etc... Is DMQ the "new way to go"? I know that there lots of ways of doing things with each having pros/cons... But I was wondering... What does the community think on this topic? Are you guys taking advantage of the DMQ modules or are you still relying on database as much as possible? Maybe a combination of both? Cheers, Joel.

8 19

Seeing Large Waits
by Mack Hendricks 03 May '18

03 May '18

Hey All, We are load testing Kamailio 4.2.3 and we are seeing the waiting within the transaction manager increasing. I’ve increased the children from 8 to 16 to 24, but we are still seeing a large amount of waiting. I don’t see an errors in the logs. Can anyone give me a clue on where to look. 05-02-18_03:07:38 PM tm.stats { current: 390 waiting: 226 total: 2361 total_local: 0 replied_locally: 1406 6xx: 0 5xx: 0 4xx: 88 3xx: 0 2xx: 3180 created: 2361 freed: 1971 delayed_free: 0 } Mack Hendricks / Head of Support / dOpenSource web: http://dopensource.com <http://dopensource.com/> support: +888-907-2085 dSIPRouter <http://dsiprouter.org/> - GUI focused on implementing Kamailio to provide SIP Trunking and PBX Hosting Services

4 6

BLF+Asterisk+NAT
by John Bob 03 May '18

03 May '18

Phone sends Subscribe Kamailio Responds 202 OK Kamailio Responds with NOTIFY Via: SIP/2.0/TCP 66.66.66.66:5051;branch=z9hG4bKfe3e.e4fedb84000000000000000000000000.0 To: <sip:30041@66.66.66.66 <mailto:30041@66.66.66.66>>;tag=48ae253ab7 From: <sip:47701@66.66.66.66 <mailto:47701@66.66.66.66>>;tag=00c39aabf419ddeab4250cd65af8ef90-6fb2 CSeq: 2 NOTIFY Call-ID: 1493ef52c41b6c1a Content-Length: 0 User-Agent: kamailio (5.1.2 (x86_64/linux)) Max-Forwards: 70 Event: dialog Contact: <sip:192.168.1.30;transport=udp> Subscription-State: terminated;reason=timeout In that packet I see Subscription-state: terminated;reason=timeout Im not sure what I am missing or misconfigured. Any help would be great. I’ve attached my config. Thanks.

2 7

Seeing Large Waits
by Mack Hendricks 02 May '18

02 May '18

Hey All, We are load testing Kamailio 4.2.3 and we are seeing the waiting within the transaction manager increasing. I’ve increased the children from 8 to 16 to 24, but we are still seeing a large amount of waiting. I don’t see an errors in the logs. Can anyone give me a clue on where to look. 05-02-18_03:07:38 PM tm.stats { current: 390 waiting: 226 total: 2361 total_local: 0 replied_locally: 1406 6xx: 0 5xx: 0 4xx: 88 3xx: 0 2xx: 3180 created: 2361 freed: 1971 delayed_free: 0 } Mack Hendricks / Head of Support / dOpenSource web: http://dopensource.com <http://dopensource.com/> support: +888-907-2085 dSIPRouter <http://dsiprouter.org/> - GUI focused on implementing Kamailio to provide SIP Trunking and PBX Hosting Services

1 0

how to disable sip authentication
by BIPIN KUMAR Das 02 May '18

02 May '18

Hi, Is there any way in Kamailio where I can suppress sip registration authentication. I want, Kamailio can send 200 OK for sip registration without going for 401 Unauthorized. Please tell me if you have such configuration in Kamailio. thanks Bipin

2 1

Kamailio config file String Concatenation
by George Diamantopoulos 02 May '18

02 May '18

Hello, I'm a a bit confused as to when string concatenation will work in kamailio config file. So far I have identified the following cases: Working: As part of the right hand side of an assignment: $var(x) = "string1" + "string2"; String argument of some functions: xlog("L_ERR", "string1" + "string2" + DEFINED_STRING + '\n'); Conditional Statements: if ( ru =~ "$" + "sip:" + $var(user) ) { Not Working: In string transformations (the fact that quotes is not part of the argument should give a hint though: $var(x) = $(var(y){s.replace,match,"repl1" + "repl2"}); String argument of some other functions: append_hf_value("P-Asserted-Identity", "<" + "$var(new_pai)" + ">"); lookup("location", "sip:$var(username)@" + SIP_REALM_DEFINITION)); In module parameter definitions: modparam("nathelper", "sipping_from", "sip:keepalive@" + SIP_REALM_DEFINITION) So far, I have found this to be fairly consistent, except for use within functions. For example, string concatenation works for the second argument of xlog, but not for the string arguments of append_hf_value() or lookup(). Is there anyway to know this for each function beforehand, or is my only choice to go through trial and error here? Thanks! BR, George

3 4

Routing 10 Digit Inbound call to Registered User or VM server
by KamDev Essa 02 May '18

02 May '18

I have Kamailio 5.1 installed and running with 2 extensions, 201 and 202 registered. Both extensions can call each other perfectly. Next I am workin on inbound calls. I have an inbound call from a carrier that arrives perfectly but ends up in this area of the cfg case -3: send_reply("404", "Not Found"); exit; and sends a 404 not found. How do I : - Associate the 10 digit DID to the 201 or 202? Custom table I make or is there something native to Kamailio. - Relay the call to the 201 or 202. Thank in advance KamDev

1 0

Routing inbound call from carrier to user or voice mail
by KamDev Essa 02 May '18

02 May '18

I have Kamailio 5.1 installed and running with 2 extensions, 201 and 202 registered. Both extensions can call each other perfectly. I have an inbound call from a carrier that arrives perfectly but ends up in this area of the cfg case -3: send_reply("404", "Not Found"); exit; and sends a 404 not found. How do I : - Associate the 10 digit DID to the 201 or 202? - In the cfg, check if user is registered if - yes, relay call to user - no relay call to VM server. KamDev

2 1

Auto 100 Reply
by Duarte Rocha 02 May '18

02 May '18

Greetings, I have set the auto_inv_100() parameter from the TM module so i can get automatic "100" replies to the INVITE. However, in some cases i want to reply to the INVITE with provisional responses (181 for example) and i would like that "100" could be sent before the "181". In order to achieve this, on transactions that are going to be replied with 181 i'm turning off the parameter with t_set_auto_inv(0) and the sl_send_reply("100","Trying"). Is this the best way to do this? Thanks

2 1

I am not able to make a call from kam1 SIP Registered user to kam2 SIP Registered user.
by Suresh Talasaniya 02 May '18

02 May '18

Hello, Is it possible to configure two Kamailio servers with shared registration database? Any SIP UA can be registered on any server but it must transparently call another SIP UA which can be registered on the same or on another Kamailio server. *I configured usrloc module with below params.* ## ---------- usrloc params ------------------- #!ifdef WITH_USRLOCDB modparam("usrloc", "db_url", DBURL) *modparam("usrloc", "db_mode", 3)* modparam("usrloc", "use_domain", MULTIDOMAIN) modparam("usrloc", "timer_interval", 30) modparam("usrloc", "matching_mode", 1) modparam("usrloc", "cseq_delay", 10) modparam("usrloc", "fetch_rows", 3000) modparam("usrloc", "hash_size", 12) modparam("usrloc", "timer_procs", 4) modparam("usrloc", "handle_lost_tcp", 1) modparam("usrloc", "close_expired_tcp", 1) modparam("usrloc", "db_timer_clean", 1) modparam("usrloc", "skip_remote_socket", 0) modparam("usrloc", "server_id_filter", 0) modparam("usrloc", "preload", "location") #!endif I am not able to make a call from kam1 SIP Registered user to kam2 SIP Registered user. it would be appreciable if anyone helps me to resolve the issue. Thank you! -- Regards, Suresh Talasaniya. Contact : +91-9724264776 Skype : suresh.talsaniya

2 1

Nat_UAC
by Nicolas Breuer 02 May '18

02 May '18

Hello The list, What do you think of the purpose of this function Nat_Uac_test('16') 16 - Test if the source port is different from the port in the "Via" header Correct me if I'm wrong but compare the source port of the message with the source port of the via is only valid on the initial invite ? All subsequent messages or replies don't list the UAC anywhere in the via. Thanks for your replies,

2 1

Working with users using external server
by Arik Halperin 02 May '18

02 May '18

Hello, I have a project for which I need to get user data(username and password) from an external server with REST APIs. What is the best way to achieve this? Thanks, Arik Halperin

2 1

Send UPDATE to inform changes in SDP
by Alfonso Pinto 30 Apr '18

30 Apr '18

Hi guys, I'm trying to setup a Call Forward No Reply with Kamailio and I've run into this problem (that was expected): When A INVITEs B, B replies with 183 and some SDP. B doesn't answer so Kamailio triggers the timeout and sends the INVITE TO C. C replies with 200 OK and some SDP, but A side drops the call as the media session doesn't match with the expected one. To solve it, I'm trying to send to A an UPDATE before relaying the 200 OK from C. I tried to use UAC module (uac_req_send + $uac_req) but I don't see how I can UPDATE the existing dialog. uac_req_send seems to try to setup a new dialog always. Is there a way to indicate to uac_req_send that I wan't to use the existing dialog? Or maybe there is another mechanism I can use to send the UPDATE inside the dialog? Regards, Alfonso.

4 5

Issue while using jsonrpc-s module in kamailio 4.4.
by Deepen Patel 30 Apr '18

30 Apr '18

Hi All, I am configuring Kamailio version 4.4 with jsonrpc-s and xhttp module. My aim is to use Kamailio commands using RPC from a remote server. I need help to solve error. After send rpc command, I got execution error in response. I am attaching code in kamailio.cfg file for jsonrp. event_route[xhttp:request] { if(src_ip!=127.0.0.1){ xhttp_reply("403", "Forbidden", "text/html", "<html><body>Not allowed from $si</body></html>" ); exit; } if ($hu =~ "^/RPC"){ xlog("json rpc dispatch"); # xlog($jsonrpl(method)); jsonrpc_exec('{"jsonrpc": "2.0", "method": "dispatcher.reload", "id": 1}'); jsonrpc_dispatch(); # xlog($jsonrpl(code)); # xlog($jsonrpl(text)); # xlog($jsonrpl(body)); xhttp_reply("200", "OK", "text/html", "<html><body> $jsonrpl(text), $jsonrpl(body)</body></html>"); } else { xhttp_reply("200", "OK", "text/html", "<html><body>Wrong URL $hu</body></html>"); } return; } Also, I am attaching logs. which could help you. If you can dream it, we will deliver it. <https://www.facebook.com/linteltechnologies/> <https://www.linkedin.com/company/7045679/> <http://blog.lintel.in/> Deepen Patel Python Developer A 507, Ashwamegh Elegance-2, Beside Central Mall, Ahmedabad - 380015 Gujarat, India P +1(281) 205-9247 M +91-898-077-3553 E deepen(a)lintelindia.com Skype deepenpatel.lintel W <http://lintel.in>http://lintel.in The science of today is Technology of tomorrow.

1 0

nathelper issues
by Konstantin Polyakov 29 Apr '18

29 Apr '18

Hello All, Unfortunately we found two more bugs in the nathelper module in my favorite Kamailio! Oh my god! 1. nathelper doesn't send pings when db_mode=3 and db is mongodb. I will provide fix soon. The root cause is incorrect date format in get_all_db_ucontacts function in usrloc. We need to use datatime type instead string. 2. nathelper doesn't send pings if ping_nated_only=0 (default value). It looks like incorrect condition in nh_timer in nathelper. Definitely lack of testing. It is interesting how testing is organized in the Kamailio community? Best regards. Konstantin ping_nated_only

1 0

User agent is registered but location table doesn't contain its contact.
by Konstantin Polyakov 28 Apr '18

28 Apr '18

Hello All, Hello Daniel! We have met a new issue. We use db_mode=1 ( Write-Through scheme. All changes to usrloc are immediately reflected in database too ). timer_interval has default value 60 seconds. Problem description. Some user agent is registered successfully in Kamailio registrar. Its contact exists inside internal cache (ul.lookup command shows it). But location table doesn't contain this contact. After several minutes (5-6 min) it becomes available in the location table too. The issue is reproduced periodically. Most of the time everything is ok. Is that expected behavior when internal cache is used? Did somebody else observed such situation? Is there some workaround? Best regards Konstantin

2 2

SIP Registartion Sharing between two kamailio
by Suresh Talasaniya 27 Apr '18

27 Apr '18

Hello All, I have two Kamailio servers and shared the database between two Kamailio. Below are my usrloc configuration in kamailio.cfg # ----- usrloc params ----- modparam("usrloc", "db_url", DBURL) *modparam("usrloc", "db_mode", 3)* modparam("usrloc", "use_domain", MULTIDOMAIN) modparam("usrloc", "timer_interval", 30) modparam("usrloc", "matching_mode", 1) modparam("usrloc", "cseq_delay", 10) modparam("usrloc", "fetch_rows", 3000) modparam("usrloc", "hash_size", 12) modparam("usrloc", "timer_procs", 4) modparam("usrloc", "handle_lost_tcp", 1) modparam("usrloc", "close_expired_tcp", 1) modparam("usrloc", "db_timer_clean", 1) # ----- registrar params ----- modparam("registrar", "method_filtering", 1) modparam("registrar", "gruu_enabled", 0) modparam("registrar", "received_avp", "$avp(RECEIVED)") modparam("registrar", "default_expires", 3600) modparam("registrar", "min_expires", 1200) modparam("registrar", "max_expires", 3600) modparam("registrar", "default_q", 1000) modparam("registrar", "max_contacts", 10) modparam("registrar", "retry_after", 10) modparam("registrar", "xavp_cfg", "reg") modparam("registrar", "use_path", 1) modparam("registrar", "path_mode", 0) modparam("registrar", "path_use_received", 1) modparam("registrar", "contact_max_size", 1024) modparam("registrar", "path_check_local", 1) modparam("registrar", "sock_flag", 18) modparam("registrar", "sock_hdr_name", "Sock-Info") #------------------------------------------------------------ I have two users in same domain. 1. 1000(a)dev.domain.com --> Registered on kamailio 1 2. 1001(a)dev.domain.com --> Registered on kamailio 2 I am not able to make a call from 1000(a)dev.domain.com to 1001(a)dev.domain.com and vice versa. It will be appreciable if anyone help to resolve the issue. Thank you in advance! -- Regards, Suresh Talasaniya. Contact : +91-9724264776 Skype : suresh.talsaniya

2 1

Sending Notify With Custom Event Header
by strain17 27 Apr '18

27 Apr '18

Hi All, I'm trying to send a custom NOTIFY message to a list of users that are registered with Kamailio. The procedure would be invoked via HTTP (jsonrpc/xmlrpc over HTTP). 1. Should I be looking at the t_uac_start/t_uac_dlg MI commands to accomplish this? Is this the best way to do it if the NOTIFY sent to the phones are unsolicited? 2. I tried to use the xhttp_rpc module for testing out tm.t_uac_start but kept running into 400 invalid headers. I'm not sure if there is a syntax issue. The NOTIFY example is NOTIFY sip:123@192.168.5.5 . . From:333@1.1..1\r\nTo:test@2.2.2.2 - Request URL: http://x.x.x.x/http_rpc/tm/tm.t_uac_start?arg=NOTIFY+sip%3A123%40192.168.5.… - Request Method: GET - Status Code: 400 Invalid headers Thanks for any feedback!

2 1

I need some documentation :)
by Facchini Antoine 26 Apr '18

26 Apr '18

hello here ! I'm very newbie ... I search documentation (because I guess u can't explain that here like this) for create proxy. I want redirect all SIP traffic to an Asterisk instance. I search again and again but i don't find anything...

2 1

rare crash at kamailio 5.0.1
by David Escartin 26 Apr '18

26 Apr '18

Hello all last March 26th we experienced a crash on a 5.0.1 kamailio server and a core was generated. Seems that the call involved in the core generated was doing several retransmisions of a request (expected) and when it finally forwarded the request upstream, seems fter receiving a 481 from a-side, it crashed. here you have the backtrace <154>Mar 26 19:54:03 mad-proxy-inout-1 /usr/local/kamailio/sbin/kamailio[24992]: : <core> [core/mem/q_malloc.c:469]: qm_free(): BUG: qm_free: bad pointer 0x7f247acb5878 (out of memory block!) called from tm: h_table.c: free_cell_helper(187) - aborting (gdb) bt #0 0x00000036e8a32925 in raise () from /lib64/libc.so.6 #1 0x00000036e8a34105 in abort () from /lib64/libc.so.6 #2 0x0000000000654c24 in qm_free (qmp=0x7f23b9cba000, p=0x7f247acb5878, file=0x7f2479e3cd86 "tm: h_table.c", func=0x7f2479e3d070 "free_cell_helper", line=187, mname=0x7f2479e3c780 "tm") at core/mem/q_malloc.c:471 #3 0x00007f2479d6bf16 in free_cell_helper (dead_cell=0x7f23c54fea50, silent=0, fname=0x7f2479e4da80 "timer.c", fline=651) at h_table.c:187 #4 0x00007f2479db8148 in wait_handler (ti=1503818844, wait_tl=0x7f23c54fead0, data=0x7f23c54fea50) at timer.c:651 #5 0x0000000000629578 in timer_list_expire (t=1503818844, h=0x7f23b9d38dc0, slow_l=0x7f23b9d3b0c8, slow_mark=43533) at core/timer.c:874 #6 0x00000000006299d4 in timer_handler () at core/timer.c:939 #7 0x0000000000629e73 in timer_main () at core/timer.c:978 #8 0x0000000000422d4e in main_loop () at main.c:1690 #9 0x0000000000429732 in main (argc=13, argv=0x7fff2b9f8088) at main.c:2639 (gdb) frame 4 #4 0x00007f2479db8148 in wait_handler (ti=1503818844, wait_tl=0x7f23c54fead0, data=0x7f23c54fea50) at timer.c:651 651 UNREF_FREE(p_cell); (gdb) info locals p_cell = 0x7f23c54fea50 ret = 1 (gdb) p *p_cell $1 = {next_c = 0x0, prev_c = 0x0, hash_index = 28196, label = 341555146, flags = 4132, nr_of_outgoings = 2, ref_count = {val = 0}, from = { s = 0x7f23c87c79ed "From: <sip:932687220@100.100.100.177;user=phone;noa=national>;tag=50aa4a46-co11146-INS002\r\nCall-ID: b8997821-2814-46d3-b8f7-cf690f50f640\r\nCSeq: 1114601 BYE\r\nUser-Agent: ENSR3.0.67.10-IS2-RMRG1119-RG2040"..., len = 89}, callid = { s = 0x7f23c87c7a46 "Call-ID: b8997821-2814-46d3-b8f7-cf690f50f640\r\nCSeq: 1114601 BYE\r\nUser-Agent: ENSR3.0.67.10-IS2-RMRG1119-RG2040-CPI1-CPO2612\r\nContent-Length: 0\r\n\r\n", len = 47}, cseq_n = { s = 0x7f23c87c7a75 "CSeq: 1114601 BYE\r\nUser-Agent: ENSR3.0.67.10-IS2-RMRG1119-RG2040-CPI1-CPO2612\r\nContent-Length: 0\r\n\r\n", len = 13}, to = { s = 0x7f23c87c799e "To: \"34676893111\"<sip:34676893111@100.100.100.134;user=phone>;tag=64jNUpSZK8mSp\r\nFrom: <sip:932687220@100.100.100.177;user=phone;noa=national>;tag=50aa4a46-co11146-INS002\r\nCall-ID: b8997821-2814-46d3-b8f7"..., len = 79}, method = { s = 0x7f23c87c78c8 "BYE sip:34676893111@100.100.100.134:5080 SIP/2.0\r\nVia: SIP/2.0/UDP 200.200.200.78:5060;branch=z9hG4bK2d5c0cb4e11bb1503BYE50aa466c2b8a\r\nMax-Forwards: 34\r\nRoute: <sip:100.100.100.177;lr;ftag=64jNUpSZK8mSp;d"..., len = 3}, tmcb_hl = {first = 0x7f23bd9f7818, reg_types = 131714}, wait_timer = { next = 0x0, prev = 0x0, expire = 1503818844, initial_timeout = 80, data = 0x7f23c54fea50, f = 0x7f2479db8097 <wait_handler>, flags = 513, slow_idx = 0}, uas = {request = 0x7f23c87c71d8, end_request = 0x7f23c87c8288 "\300\300\300\300", response = {activ_type = 481, flags = 128, t_active = 0 '\000', branch = 0, buffer_len = 526, buffer = 0x7f23bef07b18 "SIP/2.0 481 Call Does Not Exist\r\nVia: SIP/2.0/UDP 200.200.200.78:5060;branch=z9hG4bK2d5c0cb4e11bb1503BYE50aa466c2b8a\r\nFrom: <sip:932687220@100.100.100.177;user=phone;noa=national>;tag=50aa4a46-co11146-I"..., my_T = 0x7f23c54fea50, timer = {next = 0x0, prev = 0x0, expire = 0, initial_timeout = 0, data = 0x0, f = 0x7f2479db7b4b <retr_buf_handler>, flags = 0, slow_idx = 0}, dst = {send_sock = 0x7f247a95be78, to = {s = { sa_family = 2, sa_data = "\023\304\325\300\313N\000\000\000\000\000\000\000"}, sin = {sin_family = 2, sin_port = 50195, sin_addr = { s_addr = 1321976021}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 1321976021, sin6_addr = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 0}}, id = 0, proto = 1 '\001', send_flags = {f = 0 '\000', blst_imask = 0 '\000'}}, retr_expire = 0, fr_expire = 0}, local_totag = { s = 0x0, len = 0}, cancel_reas = 0x0, status = 481}, uac = 0x7f23c54fec58, async_backup = {backup_route = 1, backup_branch = 4294967295, blind_uac = 0, ruri_new = 1}, fwded_totags = 0x0, uri_avps_from = 0x0, uri_avps_to = 0x0, user_avps_from = 0x0, user_avps_to = 0x0, domain_avps_from = 0x0, domain_avps_to = 0x0, xavps_list = 0x0, reply_mutex = {val = 0}, reply_locker_pid = {val = 0}, reply_rec_lock_level = 0, fr_timeout = 480, fr_inv_timeout = 1920, rt_t1_timeout_ms = 650, rt_t2_timeout_ms = 4000, end_of_life = 1503819200, relayed_reply_branch = 1, on_failure = 0, on_branch_failure = 0, on_reply = 0, on_branch = 0, on_branch_delayed = 0, md5 = 0x7f23c54fea50 ""} (gdb) frame 3 #3 0x00007f2479d6bf16 in free_cell_helper (dead_cell=0x7f23c54fea50, silent=0, fname=0x7f2479e4da80 "timer.c", fline=651) at h_table.c:187 187 sip_msg_free_unsafe(rpl); (gdb) info locals b = 0x0 i = 1 rpl = 0x7f247acb4fc0 tt = 0x0 foo = 0x7f23b9e2bd90 cbs = 0x0 cbs_tmp = 0x7f23c60c16b0 __FUNCTION__ = "free_cell_helper" (gdb) p *rpl $3 = {id = 2060145040, pid = 32548, tval = {tv_sec = 72, tv_usec = 139794652378712}, fwd_send_flags = {f = 1 '\001', blst_imask = 0 '\000'}, rpl_send_flags = { f = 0 '\000', blst_imask = 0 '\000'}, first_line = {type = -347, flags = 30263, len = 32548, u = {request = {method = {s = 0x2 <Address 0x2 out of bounds>, len = 1983381159}, uri = {s = 0x5 <Address 0x5 out of bounds>, len = 2}, version = {s = 0x2b <Address 0x2b out of bounds>, len = 2057435688}, method_value = 0}, reply = {version = {s = 0x2 <Address 0x2 out of bounds>, len = 1983381159}, status = {s = 0x5 <Address 0x5 out of bounds>, len = 2}, reason = {s = 0x2b <Address 0x2b out of bounds>, len = 2057435688}, statuscode = 0}}}, via1 = 0x0, via2 = 0x7f247acb5038, headers = 0x7fff2b9f3e50, last_header = 0x4, parsed_flag = 139794576763810, h_via1 = 0x1, h_via2 = 0x7f247616eba0, callid = 0x1, to = 0x270000000b, cseq = 0x1, from = 0x7f247aa1fa28, contact = 0x7f247acb5258, maxforwards = 0x7f247acb54d8, route = 0x0, record_route = 0x7fff2b9f3e50, content_type = 0x7f247acb5318, content_length = 0x0, authorization = 0x0, expires = 0x0, proxy_auth = 0x0, supported = 0x0, require = 0x0, proxy_require = 0x0, unsupported = 0x7f247acb5258, allow = 0x0, event = 0x7f247acb53d8, accept = 0x0, accept_language = 0x0, organization = 0x0, priority = 0x0, subject = 0x0, user_agent = 0x0, server = 0x0, content_disposition = 0x0, diversion = 0x0, rpid = 0x0, refer_to = 0x0, session_expires = 0x0, min_se = 0x0, sipifmatch = 0x0, subscription_state = 0x0, date = 0x0, identity = 0x0, identity_info = 0x0, pai = 0x0, ppi = 0x0, path = 0x7f247a98b6d0, privacy = 0x0, min_expires = 0x0, body = 0x7f247acb5258, eoh = 0x7fff2b9f3e50 "@f\313z$\177", unparsed = 0x0, rcv = {src_ip = {af = 0, len = 0, u = {addrl = {0, 0}, addr32 = {0, 0, 0, 0}, addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, addr = '\000' <repeats 15 times>}}, dst_ip = {af = 3233857728, len = 0, u = {addrl = {2882400237, 0}, addr32 = {2882400237, 0, 0, 0}, addr16 = {61421, 43981, 0, 0, 0, 0, 0, 0}, addr = "\355\357ͫ", '\000' <repeats 11 times>}}, src_port = 0, dst_port = 0, proto_reserved1 = 0, proto_reserved2 = 536, src_su = {s = {sa_family = 0, sa_data = "\000\000 \266\230z$\177\000\000\030\002\000"}, sin = {sin_family = 0, sin_port = 0, sin_addr = {s_addr = 2056828448}, sin_zero = "$\177\000\000\030\002\000"}, sin6 = {sin6_family = 0, sin6_port = 0, sin6_flowinfo = 2056828448, sin6_addr = {__in6_u = {__u6_addr8 = "$\177\000\000\030\002\000\000\000\000\000\000\210T\313z", __u6_addr16 = {32548, 0, 536, 0, 0, 0, 21640, 31435}, __u6_addr32 = {32548, 536, 0, 2060145800}}}, sin6_scope_id = 32548}}, bind_address = 0x7f247616ebb0, proto = 32 ' '}, buf = 0x7f247616eba6 "rtpengine", len = 139, new_uri = {s = 0xf0f0f0f0 <Address 0xf0f0f0f0 out of bounds>, len = 2060145720}, dst_uri = { s = 0x20 <Address 0x20 out of bounds>, len = 2060144576}, parsed_uri_ok = 1, parsed_uri = {user = { s = 0x7f247637fead "7:packetsi32e5:bytesi1896e6:errorsi0eeee5:flagsl11:initialized4:send4:recveeeee6:totalsd3:RTPd7:packetsi4951e5:bytesi158432e6:errorsi0ee4:RTCPd7:packetsi32e5:bytesi1896e6:errorsi0eee6:result2:oke", len = 2}, passwd = { s = 0x7f247637feaf "packetsi32e5:bytesi1896e6:errorsi0eeee5:flagsl11:initialized4:send4:recveeeee6:totalsd3:RTPd7:packetsi4951e5:bytesi158432e6:errorsi0ee4:RTCPd7:packetsi32e5:bytesi1896e6:errorsi0eee6:result2:oke", len = 7}, host = {s = 0x900000002 <Address 0x900000002 out of bounds>, len = 1}, port = { s = 0x7f247acb5038 "\004", len = 0}, params = {s = 0x0, len = 2060145336}, sip_params = {s = 0x7fff2b9f3e50 "@f\313z$\177", len = 2}, headers = { s = 0x7f247637feb6 "i32e5:bytesi1896e6:errorsi0eeee5:flagsl11:initialized4:send4:recveeeee6:totalsd3:RTPd7:packetsi4951e5:bytesi158432e6:errorsi0ee4:RTCPd7:packetsi32e5:bytesi1896e6:errorsi0eee6:result2:oke", len = 4}, port_no = 0, proto = 0, type = ERROR_URI_T, flags = 0, transport = { s = 0x400000001 <Address 0x400000001 out of bounds>, len = 32}, ttl = {s = 0x7f247acb5038 "\004", len = 0}, user_param = {s = 0x0, len = 2060145432}, maddr = {s = 0x7fff2b9f3e50 "@f\313z$\177", len = 1}, method = { s = 0x7f247637feba "5:bytesi1896e6:errorsi0eeee5:flagsl11:initialized4:send4:recveeeee6:totalsd3:RTPd7:packetsi4951e5:bytesi158432e6:errorsi0ee4:RTCPd7:packetsi32e5:bytesi1896e6:errorsi0eee6:result2:oke", len = 2}, lr = { s = 0x7f247637febc "bytesi1896e6:errorsi0eeee5:flagsl11:initialized4:send4:recveeeee6:totalsd3:RTPd7:packetsi4951e5:bytesi158432e6:errorsi0ee4:RTCPd7:packetsi32e5:bytesi1896e6:errorsi0eee6:result2:oke", len = 5}, r2 = {s = 0x700000002 <Address 0x700000002 out of bounds>, len = 1522079939}, gr = { s = 0x7f247acb5038 "\004", len = 0}, transport_val = {s = 0x0, len = 2060145528}, ttl_val = {s = 0x7fff2b9f3e50 "@f\313z$\177", len = 2}, user_param_val = { s = 0x7f247637fec1 "i1896e6:errorsi0eeee5:flagsl11:initialized4:send4:recveeeee6:totalsd3:RTPd7:packetsi4951e5:bytesi158432e6:errorsi0ee4:RTCPd7:packetsi32e5:bytesi1896e6:errorsi0eee6:result2:oke", len = 6}, maddr_val = {s = 0x0, len = 0}, method_val = {s = 0x600000001 <Address 0x600000001 out of bounds>, len = 1896}, lr_val = {s = 0x7f247acb5038 "\004", len = 0}, r2_val = {s = 0x0, len = 2060145624}, gr_val = {s = 0x7fff2b9f3e50 "@f\313z$\177", len = 1}}, parsed_orig_ruri_ok = 1983381191, parsed_orig_ruri = {user = {s = 0x2 <Address 0x2 out of bounds>, len = 1983381193}, passwd = { s = 0x6 <Address 0x6 out of bounds>, len = 2}, host = {s = 0x0, len = 2060144696}, port = {s = 0x0, len = 0}, params = {s = 0x7f247acb54d8 "\002", ---Type <return> to continue, or q <return> to quit--- len = 731856464}, sip_params = {s = 0x0, len = 0}, headers = {s = 0x0, len = 0}, port_no = 49344, proto = 49344, type = ERROR_URI_T, flags = 2882400237, transport = {s = 0x0, len = 0}, ttl = {s = 0x218 <Address 0x218 out of bounds>, len = 2060144520}, user_param = {s = 0x218 <Address 0x218 out of bounds>, len = 2060146440}, maddr = {s = 0x7f247616ebb0 "rtpengine: bencode.c", len = 1981214752}, method = {s = 0x7f247616eba6 "rtpengine", len = 139}, lr = { s = 0xf0f0f0f0 <Address 0xf0f0f0f0 out of bounds>, len = 2060146360}, r2 = {s = 0x20 <Address 0x20 out of bounds>, len = 2060145216}, gr = { s = 0x2 <Address 0x2 out of bounds>, len = 1983381199}, transport_val = {s = 0x3 <Address 0x3 out of bounds>, len = 0}, ttl_val = {s = 0x0, len = 1}, user_param_val = {s = 0x0, len = 2060144696}, maddr_val = {s = 0x0, len = 0}, method_val = {s = 0x0, len = 731856464}, lr_val = { s = 0x1 <Address 0x1 out of bounds>, len = 1983381205}, r2_val = {s = 0x2 <Address 0x2 out of bounds>, len = 1983381207}, gr_val = { s = 0x5 <Address 0x5 out of bounds>, len = 2}}, add_rm = 0x7f247acb5878, body_lumps = 0x7f247aa43300, reply_lump = 0x0, add_to_branch_s = "\000\000\000\000\000\000\000\000\230U\313z$\177\000\000P>\237+\377\177\000\000\003\000\000\000\000\000\000\000\244\353\026v$\177\000\000\001\000\000\000\000\000\000\000\240\353\026v$\177\000\000\001", add_to_branch_len = 0, hash_index = 8, msg_flags = 28, flags = 2060162240, set_global_address = { s = 0x7f247aa43300 "\004", len = 2060146168}, set_global_port = {s = 0x7f247acb5758 "\001", len = 0}, force_send_socket = 0x7fff2b9f3e50, path_vec = { s = 0x1 <Address 0x1 out of bounds>, len = 1983381213}, instance = {s = 0x3 <Address 0x3 out of bounds>, len = 1983381216}, reg_id = 11, ruid = { s = 0xe00000002 <Address 0xe00000002 out of bounds>, len = 0}, location_ua = {s = 0x7f247acb5598 "\003", len = 0}, ldv = {flow = {decoded = 0, rcv = { src_ip = {af = 2060146264, len = 32548, u = {addrl = {140733925244496, 30064771073}, addr32 = {731856464, 32767, 1, 7}, addr16 = {15952, 11167, 32767, 0, 1, 0, 7, 0}, addr = "P>\237+\377\177\000\000\001\000\000\000\a\000\000"}}, dst_ip = {af = 1983381227, len = 32548, u = {addrl = {2, 139794578931437}, addr32 = {2, 0, 1983381229, 32548}, addr16 = {2, 0, 0, 0, 65261, 30263, 32548, 0}, addr = "\002\000\000\000\000\000\000\000\355\376\067v$\177\000"}}, src_port = 4, dst_port = 0, proto_reserved1 = 0, proto_reserved2 = 2, src_su = { s = {sa_family = 6, sa_data = "\000\000P>\237+\377\177\000\000\230U\313z"}, sin = {sin_family = 6, sin_port = 0, sin_addr = {s_addr = 731856464}, sin_zero = "\377\177\000\000\230U\313z"}, sin6 = {sin6_family = 6, sin6_port = 0, sin6_flowinfo = 731856464, sin6_addr = {__in6_u = { __u6_addr8 = "\377\177\000\000\230U\313z$\177\000\000\000\000\000", __u6_addr16 = {32767, 0, 21912, 31435, 32548, 0, 0, 0}, __u6_addr32 = { 32767, 2060146072, 32548, 0}}}, sin6_scope_id = 0}}, bind_address = 0x0, proto = 88 'X'}}}} (gdb) (gdb) bt full #0 0x00000036e8a32925 in raise () from /lib64/libc.so.6 No symbol table info available. #1 0x00000036e8a34105 in abort () from /lib64/libc.so.6 No symbol table info available. #2 0x0000000000654c24 in qm_free (qmp=0x7f23b9cba000, p=0x7f247acb5878, file=0x7f2479e3cd86 "tm: h_table.c", func=0x7f2479e3d070 "free_cell_helper", line=187, mname=0x7f2479e3c780 "tm") at core/mem/q_malloc.c:471 qm = 0x7f23b9cba000 f = 0x7f23bc87a2c8 size = 528 next = 0x400 prev = 0x7fff2b9f7920 __FUNCTION__ = "qm_free" #3 0x00007f2479d6bf16 in free_cell_helper (dead_cell=0x7f23c54fea50, silent=0, fname=0x7f2479e4da80 "timer.c", fline=651) at h_table.c:187 b = 0x0 i = 1 rpl = 0x7f247acb4fc0 tt = 0x0 foo = 0x7f23b9e2bd90 cbs = 0x0 cbs_tmp = 0x7f23c60c16b0 __FUNCTION__ = "free_cell_helper" #4 0x00007f2479db8148 in wait_handler (ti=1503818844, wait_tl=0x7f23c54fead0, data=0x7f23c54fea50) at timer.c:651 p_cell = 0x7f23c54fea50 ret = 1 #5 0x0000000000629578 in timer_list_expire (t=1503818844, h=0x7f23b9d38dc0, slow_l=0x7f23b9d3b0c8, slow_mark=43533) at core/timer.c:874 tl = 0x7f23c54fead0 ret = 0 #6 0x00000000006299d4 in timer_handler () at core/timer.c:939 saved_ticks = 1503818844 run_slow_timer = 0 i = 525 __FUNCTION__ = "timer_handler" #7 0x0000000000629e73 in timer_main () at core/timer.c:978 No locals. #8 0x0000000000422d4e in main_loop () at main.c:1690 i = 1 pid = 0 si = 0x0 si_desc = "udp receiver child=0 sock=100.100.100.169:5060", '\000' <repeats 16 times>, "\001\000\000\000\340|\237+\377\177\000\000W\327e\000\000\000\000\000\200\335u\000\000\000\000\000\250\065\313zo\000\000\000\316\357u\000\000\000\000\000\205\335u\000\000\000\000\000\004\000\000\000\000\000\000\000\000\240˹#\177---Type <return> to continue, or q <return> to quit--- \000" nrprocs = 1 woneinit = 1 __FUNCTION__ = "main_loop" #9 0x0000000000429732 in main (argc=13, argv=0x7fff2b9f8088) at main.c:2639 cfg_stream = 0x1f8f010 c = -1 r = 0 tmp = 0x7fff2b9f8742 "" tmp_len = 54 port = -398323320 proto = 54 options = 0x732e78 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 3083103015 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x36e8a90687 p = 0x7fff2b9f7f88 "\200\200\237+\377\177" st = {st_dev = 2307, st_ino = 9183277, st_nlink = 3, st_mode = 16832, st_uid = 522, st_gid = 501, __pad0 = 0, st_rdev = 0, st_size = 4096, st_blksize = 4096, st_blocks = 8, st_atim = {tv_sec = 1496231473, tv_nsec = 0}, st_mtim = {tv_sec = 1520405673, tv_nsec = 0}, st_ctim = { tv_sec = 1520405673, tv_nsec = 0}, __unused = {0, 0, 0}} __FUNCTION__ = "main" (gdb) i dont know if you can help us to know the reason of the crash, because the call trace seemed quite normal, and we don't know if the cause was from the rtpengine responses of the bye requests, or was caused by the request retransmisions, which would be rare because we sometimes have those type of calls. thanks a lot and regards david

2 5

ASN.1 HI2- IRI-Parameters
by Mojtaba 26 Apr '18

26 Apr '18

Hello. I need to use HI2Operations for transfering IRI-Parameters in kamailio.Dose anybody have experience in this regards? Thanks. Mojtaba

2 1

Possibility of kemi lua to keep lua global vars
by Yuriy Gorlichenko 26 Apr '18

26 Apr '18

Hi For now as I see: every request that calls lua script reevables my global lua variables For example I trying to connect to DB via luasql driver and checking if connection already existis to avoid new connection I have function init() that calls in ksr_request_route() Inside i have ome check: if not CON then CON = assert(MYSQL:connect(DBdata.dbname,DBdata.username,DBdata.password,DBdata.host,DBdata.port)) if not CON then KSR.log("info","|init|log| DB NOT connected\n") KSR.sl.sl_send_reply(503,"Internal server error") KSR.x.exit() else KSR.log("info","|init|log| DB connected\n") end end So in this case if CON was already created it should not try to connect But for now it tries for every request. So means kemi not stores global lua variables between sessions (in one kamailio process) Also as I know INIT routes initiates before lua machine will be started so it not allowed to init some lua global variables in the init routes So my question is there is a way to keep global vars per kamailio process instead per kamailio request?

2 1

Sha2 self-signed certs config in Kamilio
by Kiran Gaddam 25 Apr '18

25 Apr '18

Hello All, I want to enable certificate validation on the server. I am only using self-signed certs. I have the same cert/key in the client and server and want to only allow connection from clients with this cert/key. I have turned on the following in tls.cfg and done all the steps required in kamailio.cfg file. But it's failed to verify certs and allowing the clients which doesn't have same certs. Please help to configure the cert/key in right way. [server:default] method = TLSv1 verify_certificate = yes require_certificate = yes private_key = /usr/local/etc/kamailio/selfsigned.key certificate = /usr/local/etc/kamailio/selfsigned.pem ca_list = /usr/local/etc/sip-router/cacert.pem [client:default] verify_certificate = yes require_certificate = yes In advance Thank you. Thanks, Kiran

2 2

TLS support and certificate validation
by Jignesh Gandhi 24 Apr '18

24 Apr '18

I want to enable certificate validation on the server. I am only using self-signed certs. I have the same certificate/key in the client and server and want to only allow connection from clients with this cert/key. I have turned on the following in tls.cfg and done all the steps required in kamailio.cfg file. [server:default] method = TLSv1 verify_certificate = yes require_certificate = yes private_key = /usr/local/etc/kamailio/selfsigned.key certificate = /usr/local/etc/kamailio/selfsigned.pem ca_list = /usr/local/etc/sip-router/cacert.pem [client:default] verify_certificate = yes require_certificate = yes Any help is appreciated. Thanks, --Jignesh

2 1

TCP packet relay delayed (Kamailio 4.1.5)
by Andrew Chen 24 Apr '18

24 Apr '18

Hi Kamailio community, I need your urgent help regarding a situation where the Kamailio TCP packet delayed in relaying SIP packets. They delay between the time Kamailio logs the relay to the time it left the system was ~20 seconds difference, which is huge in SIP world. Any ideas, thoughts or suggestions on how I can narrow down to the problem? We have about 30 cases of this today Thanks in advance. -- Andy Chen Sr. Telephony Lead Engineer achen@ <achen(a)thinkingphones.com>fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

3 7

Diversion Headers
by Duarte Rocha 24 Apr '18

24 Apr '18

Greetings, Does the function "add_diversion() present in the "Diversion" module allows me to introduce other parameters (privacy, counter, etc) or is it only for the "diversion-reason"? If it doesn't let me do that, how can I add the Diversion with insert_hf() and make sure the headers are added in the right order? Cheers

2 1

Any ideas on how to implement prepaid calling function which is persistent after restart
by Kit Lim 24 Apr '18

24 Apr '18

Hi Everyone, My project involves keeping track of the allowable duration for the caller to talk, and keeping track of the status of the call with the back end database. Currently i have implemented using the following modules (aside from the default modules in the sample config script). * http_async_client.so - to communicate with the backend DB * dialog.so - mainly use to detect the 200 ok answer in relation to invite, and the end of the call * cnxcc.so - to release the call when the allowable talk time is reached The flow is as below:- Invite -- > http to backend DB to ask for talk time <-- DB returns value 200 ok (answer) ---> http backend DB to update that the call has answered <-- DB returns ok dialog end or Cnxcc terminate --> http backend DB to update that the call has hangup My problem is that if there is a need to restart the kamailio config there is no 'graceful' way to hangup all the calls and inform the backend, or deny any new calls from coming in. If kamailio is restarted then cnxcc would have forgotten that there is a maximum talk time allowed to be called or recover from the restart. How to I make the system resilience to failures/restarts. Appreciate any good suggestions. regards CK

2 1

Re: [SR-Users] Kamailio doesn't start with db_mongodb and usrloc.
by Konstantin Polyakov 24 Apr '18

24 Apr '18

Dear All, It looks like there is a serious error inside db_mongodb module in the latest versions of Kamailio 4.4.7 and 5.1.2. During query operations string fields inside result structure db1_res_t could be corrupted because of incorrect usage of bson memory. The issue is located in the function db_mongodb_convert_bson() around line 614. This issue is reproduced when we need to read more than 150 documents from the database. So that is why this issue still exists. Firstly bson_iter_utf8 function returns pointer to memory which is allocated inside bson memory and which is used multiple times. So the data must be copied into Kamailio memory instead storing that pointer. The pointer becomes invalid after some time. Secondly, this pointer must not be freed by the caller of bson_iter_utf8 . At the current version bson allocated pointer is freed by Kamailio function pkg_free like it is was allocated by pkg_malloc . So I am going to create ticket in the github and propose the fix. It looks like nobody uses mongodb with Kamailio in db_mode=1 :) Best regards Konstantin >---------------------------------------------------------------------- > >Message: 1 >Date: Sat, 21 Apr 2018 23:37:26 +0300 >From: Konstantin Polyakov < piligrim_pk(a)mail.ru > >To: sr-users(a)lists.kamailio.org >Subject: [SR-Users] Kamailio doesn't start with db_mongodb and usrloc. >Message-ID: < 1524343046.238272820(a)f356.i.mail.ru > >Content-Type: text/plain; charset="utf-8" > > >Hello! > >Similar issue but with different symptoms. > >kamailio 4.4.7 (tried to use db_mongodb module from 5.1.2) >usrloc is configured to use db_mode=1 and db_insert_null=1. > >MongoDB 3.6.3 >mongo-c-driver was tested 1.9.2 and 1.9.4. > >location table contains 300 records. > >The issue was not reproduced since February when we started a new feature. Now it is reproduced constantly, but on some machines. > >Logs: > >[0;39;49m[0;39;49m 1(13958) DEBUG: usrloc [udomain.c:313]: dbrow2info(): non-local socket <all.com>...ignoring >[0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:476]: preload_udomain(): empty username record in table location...skipping >[0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:256]: dbrow2info(): bad callid >[0;39;49m[0;31;49m 1(13958) ERROR: usrloc [udomain.c:484]: preload_udomain(): skipping record for agent in table location >[0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:476]: preload_udomain(): empty username record in table location...skipping >[0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:231]: dbrow2info(): bad contact >[0;39;49m[0;31;49m 1(13958) ERROR: usrloc [udomain.c:484]: preload_udomain(): skipping record for cflags in table location >[0;39;49m[0;39;49m 1(13958) DEBUG: usrloc [udomain.c:313]: dbrow2info(): non-local socket <��keepalive>...ignoring >[0;39;49m[0;35;49m 1(13958) WARNING: usrloc [../../ut.h:717]: shm_str_dup(): shm_str_dup fallback; dup called for src->s == NULL or src->len < 0 >[0;39;49m[0;35;49m 1(13958) WARNING: usrloc [../../ut.h:731]: shm_str_dup(): shm_str_dup fallback; skip memcpy for src->s == NULL >[0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:476]: preload_udomain(): empty username record in table location...skipping >[0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:231]: dbrow2info(): bad contact >[0;39;49m[0;31;49m 1(13958) ERROR: usrloc [udomain.c:484]: preload_udomain(): skipping record for cseq in table location >[0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:231]: dbrow2info(): bad contact >[0;39;49m[0;31;49m 1(13958) ERROR: usrloc [udomain.c:484]: preload_udomain(): skipping record for 5.17.xxx in table location >[0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:231]: dbrow2info(): bad contact >[0;39;49m[0;31;49m 1(13958) ERROR: usrloc [udomain.c:484]: preload_udomain(): skipping record for .17.x in table location >[0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:476]: preload_udomain(): empty username record in table location...skipping >[0;39;49m[0;39;49m 1(13958) DEBUG: usrloc [udomain.c:313]: dbrow2info(): non-local socket <nce>...ignoring >[0;39;49m[0;35;49m 1(13958) WARNING: usrloc [../../ut.h:717]: shm_str_dup(): shm_str_dup fallback; dup called for src->s == NULL or src->len < 0 >[0;39;49m[0;35;49m 1(13958) WARNING: usrloc [../../ut.h:731]: shm_str_dup(): shm_str_dup fallback; skip memcpy for src->s == NULL >[0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:476]: preload_udomain(): empty username record in table location...skipping >[0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:476]: preload_udomain(): empty username record in table location...skipping >[0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:476]: preload_udomain(): empty username record in table location...skipping >[0;39;49m[0;39;49m 1(13958) DEBUG: usrloc [udomain.c:313]: dbrow2info(): non-local socket <c-89-5ada654b-35a2-42>...ignoring >[0;39;49m[0;39;49m 1(13958) DEBUG: usrloc [udomain.c:313]: dbrow2info(): non-local socket <>...ignoring >[0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:231]: dbrow2info(): bad contact >[0;39;49m[0;31;49m 1(13958) ERROR: usrloc [udomain.c:484]: preload_udomain(): skipping record for 38.146:5360 in table location >[0;39;49m[0;39;49m 1(13958) DEBUG: usrloc [udomain.c:313]: dbrow2info(): non-local socket <ified>...ignoring >[0;39;49m[0;31;49m 1(13958) ERROR: usrloc [ucontact.c:94]: new_ucontact(): no ruid for aor: lQ.com@5.17.60@8/Ղusername >[0;39;49m[0;31;49m 1(13958) ERROR: usrloc [urecord.c:149]: mem_insert_ucontact(): failed to create new contact >[0;39;49m[0;31;49m 1(13958) ERROR: usrloc [udomain.c:517]: preload_udomain(): inserting contact failed >[0;39;49m[0;31;49m 1(13958) ERROR: usrloc [ul_mod.c:457]: child_init(): child(1): failed to preload domain 'location' >[0;39;49m[0;31;49m 1(13958) ERROR: <core> [sr_module.c:923]: init_mod_child(): Error while initializing module usrloc (/usr/ecsp/lib64/kamailio/modules/usrloc.so) >[0;39;49m[0;31;49m 1(13958) ERROR: <core> [pt.c:329]: fork_process(): init_child failed for process 1, pid 13958, "udp receiver child=0 sock=5.17.138.137:5060 (5.17.138.137:5060)" >[0;39;49m[0;33;49m 1(13958) CRITICAL: <core> [main.c:1615]: main_loop(): Cannot fork >[0;39;49m[1;31;49m 0(13956) ALERT: <core> [main.c:740]: handle_sigs(): child process 13958 exited normally, status=255 >[0;39;49m[0;36;49m 0(13956) INFO: <core> [main.c:768]: handle_sigs(): terminating due to SIGCHLD >[0;39;49m[0;39;49m 0(13956) DEBUG: <core> [main.c:770]: handle_sigs(): terminating due to SIGCHLD > > >Could you please help us to resolve the issue? >Thank you in advance. >Best regards >Konstantin >

1 0

UAC with HA1
by Ben Hood 24 Apr '18

24 Apr '18

Hi, Does the UAC module support ha1 passwords for the remote registrar? The DDL for the uacreg table indicates the might be the case, but it’s unclear which one the UAC module would use by default. Is there a parameter to set this? Cheers, Ben

2 1

Planning the release of Kamailio v5.1.3
by Daniel-Constantin Mierla 24 Apr '18

24 Apr '18

Hello, I am considering to package a new release from branch 5.1, respectively v5.1.3 sometime next week, likely on Tuesday or Wednesday (April 24 or 25). I any issue is not yet reported on github tracker, do it as soon as possible to have a chance to be investigated. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

1 1

Use of MariaDB to replace MySQL
by Ginhoux, Patrick 23 Apr '18

23 Apr '18

Hi, Currently, my Kamailio proxy uses a MySql DB to get configuration data. We have a plan to migrate MySQL to MariaDB. Is there MariaDB modules with Kamailio ? Thanks in advance for your answer. P. Ginhoux

2 2

Kamailio not listening to proper ipv6 address
by selak Dev 23 Apr '18

23 Apr '18

Hi, I need to enable Kamailio to work with ipv6 also, and I enabled auto_bind_ipv6=1 and when restarted I can see that it is listening to ipv6 ip addresses also. The problem is that it stripped the ip address at the end and it is listening to the wrong one. When I try to register I get timeout, since it is not listening the correct address. ip address of the server is 2604:a880:400:d0::yyyy:xxxx and when I execute "sudo netstat -plnt" too see which app is listening to which address/port I can see: .... tcp6 0 0 2604:a880:400:d0:::5085 :::* LISTEN 17748/kamailio tcp6 0 0 2604:a880:400:d0:::5061 :::* LISTEN 17748/kamailio It somehow stripped the last part of the address (yyyy:xxxx). I dont know if it is related to :: which would be all zeros, but it doesn't work even if i explicitly specify which address to listen with listen=[2604:a880:400:d0:0000:0000:yyyy:xxxx] or listen=tcp:[2604:a880:400:d0:0000:0000:yyyy:xxxx]:5061 or listen=tcp:[2604:a880:400:d0::yyyy:xxxx]:5061 I tried all combinations and the results are always the same... Have anybody had this problem before? Do you know how to fix this? Best regards, Marko Selakovic

3 3

select outgoing interface
by Laurent Schweizer 23 Apr '18

23 Apr '18

Dear all, I have a config with multiple interface( multiple IP in same subnet) and want to know how I can select the interface used to send a request (UDP). The best is the possibility to choose for each request the outgoing interface but if it's not possible I think I can also work with a solution where the outgoing interface is defined globally ? I need this because one provider request one IP for inbound call and one IP for outbound call . Thanks Laurent

2 2

Variables in database
by Nelson Migliaro 22 Apr '18

22 Apr '18

Hello, I am palnning to set variables to limit the number of channels but I would like to set up them in database in order to upload them without needing to restart the service. I also would like to have that db information to be loaded in memory. So far I only thought in dialplan module but i am looking for a more "fancy" way. Can someone recommend me a module? thank you

5 5

Kamailio relays ACK itself
by Volkan Oransoy 22 Apr '18

22 Apr '18

Hi all, I have a Kamailio box which I use as a uac_client. We register a bunch of accounts to remote providers. The box relays incoming calls to a FreeSwitch box. We encountered a strange problem on one account. Kamailio relays the call to my FreeSwitch box successfully but routes the ACK itself which is the reply of 200Ok. I believe this is a provider related issue but I need a technical explanation. Does anyone have any idea? Here is the packet capture: https://pastebin.com/PA8StiWY Thanks, -- Volkan Oransoy

3 2

TCP core parameters and TLS
by Alex Balashov 22 Apr '18

22 Apr '18

Hi, Is it reasonable to assume that the various tcp_* core parameters (keepalive behaviour, connection limits, buffer sizes, etc.) also regulate the behaviour of TLS connections, since TLS is encapsulated in TCP? -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

2 1

CLID blacklist
by Nelson Migliaro 21 Apr '18

21 Apr '18

Hello, I am looking for a module to block number based on CLID. If the module allows REG expresions it would really make my day. I need to block some callers and I would like to use a module and database to avoid restarting kamailio service everytime a new number appears. Thank you Nelson.-

2 2

Kamailio doesn't start with db_mongodb and usrloc.
by Konstantin Polyakov 21 Apr '18

21 Apr '18

Hello! Similar issue but with different symptoms. kamailio 4.4.7 (tried to use db_mongodb module from 5.1.2) usrloc is configured to use db_mode=1 and db_insert_null=1. MongoDB 3.6.3 mongo-c-driver was tested 1.9.2 and 1.9.4. location table contains 300 records. The issue was not reproduced since February when we started a new feature. Now it is reproduced constantly, but on some machines. Logs: [0;39;49m[0;39;49m 1(13958) DEBUG: usrloc [udomain.c:313]: dbrow2info(): non-local socket <all.com>...ignoring [0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:476]: preload_udomain(): empty username record in table location...skipping [0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:256]: dbrow2info(): bad callid [0;39;49m[0;31;49m 1(13958) ERROR: usrloc [udomain.c:484]: preload_udomain(): skipping record for agent in table location [0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:476]: preload_udomain(): empty username record in table location...skipping [0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:231]: dbrow2info(): bad contact [0;39;49m[0;31;49m 1(13958) ERROR: usrloc [udomain.c:484]: preload_udomain(): skipping record for cflags in table location [0;39;49m[0;39;49m 1(13958) DEBUG: usrloc [udomain.c:313]: dbrow2info(): non-local socket <��keepalive>...ignoring [0;39;49m[0;35;49m 1(13958) WARNING: usrloc [../../ut.h:717]: shm_str_dup(): shm_str_dup fallback; dup called for src->s == NULL or src->len < 0 [0;39;49m[0;35;49m 1(13958) WARNING: usrloc [../../ut.h:731]: shm_str_dup(): shm_str_dup fallback; skip memcpy for src->s == NULL [0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:476]: preload_udomain(): empty username record in table location...skipping [0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:231]: dbrow2info(): bad contact [0;39;49m[0;31;49m 1(13958) ERROR: usrloc [udomain.c:484]: preload_udomain(): skipping record for cseq in table location [0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:231]: dbrow2info(): bad contact [0;39;49m[0;31;49m 1(13958) ERROR: usrloc [udomain.c:484]: preload_udomain(): skipping record for 5.17.xxx in table location [0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:231]: dbrow2info(): bad contact [0;39;49m[0;31;49m 1(13958) ERROR: usrloc [udomain.c:484]: preload_udomain(): skipping record for .17.x in table location [0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:476]: preload_udomain(): empty username record in table location...skipping [0;39;49m[0;39;49m 1(13958) DEBUG: usrloc [udomain.c:313]: dbrow2info(): non-local socket <nce>...ignoring [0;39;49m[0;35;49m 1(13958) WARNING: usrloc [../../ut.h:717]: shm_str_dup(): shm_str_dup fallback; dup called for src->s == NULL or src->len < 0 [0;39;49m[0;35;49m 1(13958) WARNING: usrloc [../../ut.h:731]: shm_str_dup(): shm_str_dup fallback; skip memcpy for src->s == NULL [0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:476]: preload_udomain(): empty username record in table location...skipping [0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:476]: preload_udomain(): empty username record in table location...skipping [0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:476]: preload_udomain(): empty username record in table location...skipping [0;39;49m[0;39;49m 1(13958) DEBUG: usrloc [udomain.c:313]: dbrow2info(): non-local socket <c-89-5ada654b-35a2-42>...ignoring [0;39;49m[0;39;49m 1(13958) DEBUG: usrloc [udomain.c:313]: dbrow2info(): non-local socket <>...ignoring [0;39;49m[0;33;49m 1(13958) CRITICAL: usrloc [udomain.c:231]: dbrow2info(): bad contact [0;39;49m[0;31;49m 1(13958) ERROR: usrloc [udomain.c:484]: preload_udomain(): skipping record for 38.146:5360 in table location [0;39;49m[0;39;49m 1(13958) DEBUG: usrloc [udomain.c:313]: dbrow2info(): non-local socket <ified>...ignoring [0;39;49m[0;31;49m 1(13958) ERROR: usrloc [ucontact.c:94]: new_ucontact(): no ruid for aor: lQ.com@5.17.60@8/Ղusername [0;39;49m[0;31;49m 1(13958) ERROR: usrloc [urecord.c:149]: mem_insert_ucontact(): failed to create new contact [0;39;49m[0;31;49m 1(13958) ERROR: usrloc [udomain.c:517]: preload_udomain(): inserting contact failed [0;39;49m[0;31;49m 1(13958) ERROR: usrloc [ul_mod.c:457]: child_init(): child(1): failed to preload domain 'location' [0;39;49m[0;31;49m 1(13958) ERROR: <core> [sr_module.c:923]: init_mod_child(): Error while initializing module usrloc (/usr/ecsp/lib64/kamailio/modules/usrloc.so) [0;39;49m[0;31;49m 1(13958) ERROR: <core> [pt.c:329]: fork_process(): init_child failed for process 1, pid 13958, "udp receiver child=0 sock=5.17.138.137:5060 (5.17.138.137:5060)" [0;39;49m[0;33;49m 1(13958) CRITICAL: <core> [main.c:1615]: main_loop(): Cannot fork [0;39;49m[1;31;49m 0(13956) ALERT: <core> [main.c:740]: handle_sigs(): child process 13958 exited normally, status=255 [0;39;49m[0;36;49m 0(13956) INFO: <core> [main.c:768]: handle_sigs(): terminating due to SIGCHLD [0;39;49m[0;39;49m 0(13956) DEBUG: <core> [main.c:770]: handle_sigs(): terminating due to SIGCHLD Could you please help us to resolve the issue? Thank you in advance. Best regards Konstantin

1 0

question on TM transaction matching
by Kelvin Chua 19 Apr '18

19 Apr '18

i am monitoring an issue with 5.1.2 where a cancel is not being propagated after a 183 is received the packet dump doesn't show anything anomalous. some notes: 1. the invite went out through t_relay(), transaction is tracked 2. cancel is handled this way if (is_method("CANCEL")) { xlog("CANCEL received"); if (t_check_trans()) { route(RELAY); } exit; } 3. if the UAC who is sending the call to kamailio is configured to send invite with RURI without a port i.e. 14087654321(a)w.x.y.z instead of 14087654321@w.x.y.z:6050, then this does not happen 4. can be argued that this is not an issue, and that the client should just be configured properly with outbound proxy and ruri without port. but i am just being difficult here and wanted to understand what is going on with the matching algo. TM debug, in case it helps 2018-04-18T07:29:50.984652+00:00 pinkman /usr/sbin/kamailio[17670]: ERROR: <script>: 100 Trying received 2018-04-18T07:29:50.984746+00:00 pinkman /usr/sbin/kamailio[17670]: DEBUG: tm [t_reply.c:1263]: t_should_relay_response(): ->>>>>>>>> T_code=100, new_code=100 2018-04-18T07:29:50.984752+00:00 pinkman /usr/sbin/kamailio[17670]: DEBUG: tm [t_reply.c:1786]: relay_reply(): branch=1, save=0, relay=-1 icode=0 2018-04-18T07:29:53.564979+00:00 pinkman /usr/sbin/kamailio[17678]: DEBUG: tm [h_table.c:129]: free_cell_helper(): freeing transaction 0x7f820b6b8a60 from timer.c:651 2018-04-18T07:29:53.752387+00:00 pinkman /usr/sbin/kamailio[17678]: DEBUG: tm [h_table.c:129]: free_cell_helper(): freeing transaction 0x7f820b6bbcd8 from timer.c:651 2018-04-18T07:29:54.002501+00:00 pinkman /usr/sbin/kamailio[17678]: DEBUG: tm [h_table.c:129]: free_cell_helper(): freeing transaction 0x7f820b6bf130 from timer.c:651 2018-04-18T07:29:54.184438+00:00 pinkman /usr/sbin/kamailio[17671]: DEBUG: tm [t_lookup.c:1019]: t_check_msg(): msg (0x7f8212d77e28) id=3 global id=2 T start=0xffffffffffffffff 2018-04-18T07:29:54.184454+00:00 pinkman /usr/sbin/kamailio[17671]: DEBUG: tm [t_lookup.c:897]: t_reply_matching(): t_reply_matching: hash 6057 label 0 branch 1 2018-04-18T07:29:54.184468+00:00 pinkman /usr/sbin/kamailio[17671]: DEBUG: tm [t_lookup.c:951]: t_reply_matching(): reply (0x7f8212d77e28) matched an active transaction (T=0x7f820b6cc988)! 2018-04-18T07:29:54.184474+00:00 pinkman /usr/sbin/kamailio[17671]: DEBUG: tm [t_lookup.c:1088]: t_check_msg(): msg (0x7f8212d77e28) id=3 global id=3 T end=0x7f820b6cc988 2018-04-18T07:29:54.184485+00:00 pinkman /usr/sbin/kamailio[17671]: DEBUG: tm [t_reply.c:2207]: reply_received(): org. status uas=100, uac[1]=100 local=0 is_invite=1) 2018-04-18T07:29:54.184544+00:00 pinkman /usr/sbin/kamailio[17671]: ERROR: <script>: 183 Session Progress received 2018-04-18T07:29:54.184825+00:00 pinkman rtpengine[1660]: INFO: [EqRkPDiOFOOhFg_3018V8A..]: Received command 'answer' from 127.0.0.1:41084 2018-04-18T07:29:54.184918+00:00 pinkman rtpengine[1660]: INFO: [EqRkPDiOFOOhFg_3018V8A..]: answer time = 0.000074 sec 2018-04-18T07:29:54.184931+00:00 pinkman rtpengine[1660]: INFO: [EqRkPDiOFOOhFg_3018V8A..]: Replying to 'answer' from 127.0.0.1:41084 2018-04-18T07:29:54.185049+00:00 pinkman /usr/sbin/kamailio[17671]: DEBUG: tm [t_reply.c:1263]: t_should_relay_response(): ->>>>>>>>> T_code=100, new_code=183 2018-04-18T07:29:54.185066+00:00 pinkman /usr/sbin/kamailio[17671]: DEBUG: tm [t_reply.c:1786]: relay_reply(): branch=1, save=0, relay=1 icode=0 2018-04-18T07:29:54.252450+00:00 pinkman /usr/sbin/kamailio[17678]: DEBUG: tm [h_table.c:129]: free_cell_helper(): freeing transaction 0x7f820b6c2540 from timer.c:651 2018-04-18T07:29:54.377492+00:00 pinkman rtpengine[1660]: WARNING: [EqRkPDiOFOOhFg_3018V8A.. port 18598]: RTP packet with unknown payload type 95 received 2018-04-18T07:29:54.564924+00:00 pinkman /usr/sbin/kamailio[17678]: DEBUG: tm [h_table.c:129]: free_cell_helper(): freeing transaction 0x7f820b6c57a8 from timer.c:651 2018-04-18T07:29:55.627429+00:00 pinkman /usr/sbin/kamailio[17678]: DEBUG: tm [h_table.c:129]: free_cell_helper(): freeing transaction 0x7f820b6c8bf8 from timer.c:651 2018-04-18T07:29:55.939949+00:00 pinkman /usr/sbin/kamailio[17678]: DEBUG: tm [h_table.c:129]: free_cell_helper(): freeing transaction 0x7f820b6cc988 from timer.c:651 2018-04-18T07:29:56.404385+00:00 pinkman /usr/sbin/kamailio[17673]: ERROR: <script>: CANCEL received 2018-04-18T07:29:56.404411+00:00 pinkman /usr/sbin/kamailio[17673]: DEBUG: tm [t_lookup.c:711]: t_lookupOriginalT(): searching on hash entry 6057 2018-04-18T07:29:56.404424+00:00 pinkman /usr/sbin/kamailio[17673]: DEBUG: tm [t_lookup.c:435]: matching_3261(): RFC3261 transaction matching failed 2018-04-18T07:29:56.404429+00:00 pinkman /usr/sbin/kamailio[17673]: DEBUG: tm [t_lookup.c:801]: t_lookupOriginalT(): no CANCEL matching found! 2018-04-18T07:29:56.404434+00:00 pinkman /usr/sbin/kamailio[17673]: DEBUG: tm [t_lookup.c:803]: t_lookupOriginalT(): lookup completed 2018-04-18T07:29:56.404441+00:00 pinkman /usr/sbin/kamailio[17673]: DEBUG: tm [tm.c:1096]: ki_t_lookup_cancel_flags(): lookup_original: t_lookupOriginalT returned: (nil) Kelvin Chua

3 9

Info: Kamailio Unit Testing Framework using Docker
by Daniel-Constantin Mierla 19 Apr '18

19 Apr '18

Hello, a while ago, I started to put together a unit testing framework for Kamailio. It was more or less inspired from the old shell-based testing framework added by Henning Westerholt many years ago (which still resides in source tree path test/unit/), but now leveraging docker to have an isolated environment for running the tests. The new testing framework is available on github at: * https://github.com/kamailio/kamailio-tests Giacomo Vacca helped a bit so far, he is actually going to present more about it at Kamailio World 2018 (https://www.kamailioworld.com/k06/schedule/). But we want now to get more feedback from community, eventually to adjust the framework to become something easy to use and even more important, to be easy to contribute to. One of the main benefits from my point of view it would be to have the reports of the issues that can be reproduced submitted along with a unit test. It would make it easier to troubleshoot and then after fixing it, would be tested always before releases in order to avoid regressions. Right now, a good help from community would represent converting the old unit tests to the new framework, afterwards we can decommission test/unit. The conversion should be rather easy, as we still rely on shell and the sip tools like sipp/sipsak ... If you want to help here by you need clarifications or get stuck somewhere, just write to mailing list and I would be more than happy to assist. Such contributions should be submitted as pull requests in order to be easy to review: * https://github.com/kamailio/kamailio-tests/pulls Looking forward to your feedback, comments or contributions! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

1 0

Help needed to compile and install kamailio 5.1.2
by vinay kumar 18 Apr '18

18 Apr '18

Hi All, I want to compile kamailio 5.1.2 for debian packages amd install on ubuntu 16.04. And i have couple of queries. 1. can i compile and run kamailio 5.1.2 on ubuntu 16.04(Xenial)? 2. Im currently using kamailio 4.3.6 with polaris configuration. And the same way can i use kamailio 5.1.2 with polaris configuration files and scripts to bringup kamailo 5.1.2? and if yes, please share me steps and scripts to bringup kamailio 5.1 2 with Open HSS( i need to use CX and RX interface). Please help me out. Thanks in advance. Regards, vinay

2 1

Kamailio support for IPv6 VoLTE Calls
by Sairam Subramanian 18 Apr '18

18 Apr '18

Hi All, Can anyone tell me which version of the Kamailio Open IMS supports IPv6 VoLTE Calls? Thanks, Sairam S

1 1

Branching and rejects.
by Kjeld Flarup 18 Apr '18

18 Apr '18

Hello What is the correct way to handle, if a branched call reaches a 404 on one of the branches. Currently I discard all 404 in onreply_route, but if all branches has 404, then this is never send to the caller. -- -------------------- Med Liberalistiske Hilsner ---------------------- Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog Sofienlundvej 6B, 7560 Hjerm, Tlf: 40 29 41 49 Den ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk

2 2

Failure Route Issue
by mack＠dopensource.com 18 Apr '18

18 Apr '18

Hey All, I have a weird issue. I’m sending a SIP INVITE to a SIP Service that send’s me back a 433, which let’s me know that the number is invalid. I then send an INVITE to a media server (FreeSwitch) to play a message that the number can’t be called, which looks to be working. But, the final ACK from the SIP client is sent back to the SIP Service versus the media server. The following diagram below depicts this: https://snag.gy/qMWfvk.jpg. The code snippet in the failure_route for the the SIP Service has this: if (t_check_status("403|433")) { if ($avp(s:teleblock_media_enabled) == "1") { # make sure media server can route back to kamailio record_route(); revert_uri(); $ru = "sip:" + $T_reply_code + $rU + "@" + $sel(cfg_get.teleblock.media_ip) + ":" + $sel(cfg_get.teleblock.media_port); append_branch(); t_relay(); exit; }

2 5

Kamailio Websocket Questions
by Nagorny, Dimitry 17 Apr '18

17 Apr '18

Hi List, two questions regarding Kamailio Websockets: 1. How do I send INVITE request TO the listening Websocket? I usually used for UDP/TCP/TLS these format, but somehow this is not working for Websocket because it gets in an endless loop: if ($rU=~"^(\+|00|0)?[1-9][0-9]{4,20}$") { $ru = "sip:" + $rU + "@" + $sel(cfg_get.pstn.gw_ip) + ";user=phone;transport=udp"; force_send_socket(udp:MY_EXTERN_IP:MY_EXTERN_PORT); rtpengine_offer("internal trust-address RTP AVP"); route(RELAY); exit; } 2. Why do I get these errors every time my Websocket Client is registering, but it still works and DB is inserted with registered location: ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 22) ERROR: <core> [parser/msg_parser.c:690]: parse_msg(): ERROR: parse_msg: message=<HTTP/1.1 101 Switching Protocols#015#012Sia: SIP/2.0/TCP 10.250.5.17:51283#015#012Sec-WebSocket-Protocol: sip#015#012Upgrade: websocket#015#012Connection: upgrade#015#012Sec-WebSocket-Accept: 6uLXlD/aBrzu/j3PYP3DWO7rvLE=#015#012Server: kamailio (4.3.5 (x86_64/linux))#015#012Content-Length: 0#015#012#015#012> I am using Kamailio 4.3.5 + CentOS 7.2. I appreciate every help I can get. Best Regards Dimitry Nagorny Trainee

3 4

Dialog module's keep-alive feature uses wrong CSeq?
by Oded Arbel 17 Apr '18

17 Apr '18

Hi all. I'm trying to use the dialog module's keep alive feature (ka_interval() and dlg_set_property()), and the documentation (under dlg_set_property) says this: If keep alive is enabled for a dialog, the module will send SIP OPTIONS requests with CSeq lower or equal than last request within dialog This is seems really weird to me, but the problem is worse than that - when setting dlg_set_property("ka-src"), the OPTIONS messages sent to the caller always have CSeq set to "0", regardless of what CSeq the UA sent on its invite. The problem is that while some UAs respond to these purposefully broken messages with some kind of a 5xx reply (for example, Linphone funnily sends "500 Internal Server Error"), several UAs don't respond at all. Worse than that - some of the UAs that send back 5xx replies to OPTIONS with a non-zero but invalid CSeq will completely ignore the OPTIONS keep-alive message that is sent to the caller with a CSeq 0 - for example, PJSIP responds with "503 Invalid CSeq" to a "ka-dst" OPTIONS message but will ignore a "ka-src" OPTIONS message with CSeq 0. My questions: 1. Why are keep-alive messages sent with a wrong CSeq? 2. If we're keeping the "wrong CSeq" approach, can we at least not send CSeq "0"? 3. Is there a way to change any of the above behaviors with a configuration (i.e. without patching the sources)? Thanks in advance -- Oded Arbel odeda(a)cloudonix.io

3 5

Kamailio with 2 Public and Private IPs- SIP Call flow issues
by arik halperin 16 Apr '18

16 Apr '18

Hello, I have the following setup: Kamailio: Public Interface 70.36.25.65 Private Interface 10.168.10.227 Freeswitch: Private Interface 10.168.10.200 I’m routing calls from kamailio to freeswitch, but when I try to hang up the call the freeswitch sends the BYE to the public address(70.36.25.65) and not to the private address 10.168.10.227. 200OK and ACK work correctly. It’s only the BYE that has an issue. Showing INVITES: Client Invite: T 82.80.164.63:53871 -> 70.36.25.65:5099 [AP] INVITE sip:+972549428460@70.36.25.65:5099 SIP/2.0. Via: SIP/2.0/TCP 10.0.0.42:51619;branch=z9hG4bK-524287-1---52dcc73ec891de14;rport. Max-Forwards: 70. Contact: <sip:972545234585@82.80.164.63:51620;rinstance=1f9d21b54116df89;transport=tcp>. To: <sip:+972549428460@70.36.25.65:5099>. From: "972545234585"<sip:972545234585@70.36.25.65:5099>;tag=902c5325. Kamailio to FS: T 10.168.10.227:46506 -> 10.168.10.200:5080 [AP] INVITE sip:+972549428460@70.36.25.65:5099 SIP/2.0. Record-Route: <sip:70.36.25.65:5099;transport=tcp;lr=on;ftag=902c5325;nat=yes>. Via: SIP/2.0/TCP 70.36.25.65:5099;branch=z9hG4bK1117.1b91cfe0632bd6f036b308f85898e862.1;i=1. Via: SIP/2.0/TCP 10.0.0.42:51619;received=82.80.164.63;branch=z9hG4bK-524287-1---9b6758521ff0f528;rport=53871. Max-Forwards: 69.

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