- sr-users - kamailio.org

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

Problem with resuming suspended transacation
by Arik Halperin 16 Apr '18

16 Apr '18

Hello, I’m trying to resume a suspended transaction, but keep getting this error: WARNING: tm [t_suspend.c:193]: t_continue(): transaction is not suspended [20608:1256194941] WARNING: tmx [tmx_mod.c:686]: w_t_continue(): resuming the processing of transaction [20608:1256194941] failed WARNING: tm [t_lookup.c:1483]: t_unref(): script writer didn't release transaction I’m implementing push handling, in INVITE I do the following: route[INVITE] { if (!lookup("location")) { send_reply("100", "Trying"); record_route(); route(SUSPEND); } else { # NAT detection route(NATMANAGE); if(!t_is_set("onreply_route")) t_on_reply("MANAGE_REPLY"); record_route(); t_relay(); ts_store(); $sht(vtp=>stored::$rU) = 1; } route(SENDPUSH); } # suspend the transaction route[SUSPEND] { if(!t_suspend()) //Transaction is suspended! { exit; } $sht(vtp=>join::$rU) = "" + $T(id_index) + ":" +$T(id_label); } In Register I call the PUSHJOIN route: # append branches or resume the transaction route[PUSHJOIN] { $var(hjoin) = 0; lock("$tU"); $var(hjoin) = $sht(vtp=>join::$tU); $var(hstored) = $sht(vtp=>stored::$tU); $sht(vtp=>join::$tU) = $null; unlock("$tU"); if ($var(hjoin)==0) { if ($var(hstored)) ts_append("location", "$tu"); return; } $var(id_index) = $(var(hjoin){s.select,0,:}{s.int}); $var(id_label) = $(var(hjoin){s.select,1,:}{s.int}); ($var(hjoin))\n"); t_continue("$var(id_index)", "$var(id_label)", "INVRESUME"); } For some reason I keep getting: Apr 12 12:37:11 kamprod /usr/local/sbin/kamailio[6039]: ERROR: <script>: 1111 suspended transaction [20608:1256194941] FreeSWITCH => 972587102881 pr 12 12:37:19 kamprod /usr/local/sbin/kamailio[6092]: ERROR: <script>: 1111 tU=972587102881 20608:1256194941 0 Apr 12 12:37:19 kamprod /usr/local/sbin/kamailio[6092]: ERROR: <script>: 1111 resuming trasaction [20608:1256194941] 972587102881 (20608:1256194941) Apr 12 12:37:19 kamprod /usr/local/sbin/kamailio[6092]: WARNING: tm [t_suspend.c:193]: t_continue(): transaction is not suspended [20608:1256194941] Apr 12 12:37:19 kamprod /usr/local/sbin/kamailio[6092]: WARNING: tmx [tmx_mod.c:686]: w_t_continue(): resuming the processing of transaction [20608:1256194941] failed Apr 12 12:37:19 kamprod /usr/local/sbin/kamailio[6092]: WARNING: tm [t_lookup.c:1483]: t_unref(): script writer didn't release transaction

3 2

Audio stops after resuming call from hold
by gerry kernan 16 Apr '18

16 Apr '18

Hi Hoping someone can point me in the right direction. I have a Kamailio Ver: 4.2.3-1.1 running in front of a few asterisk servers Ver: 13.17.2 sip is routed to an asterisk server depending the domain name in the sip request, all working as expected . but if a call is put on hold after resuming the call the party that placed the call on hold can't hear any audio. The other party can hear . do I need to do anything special to handle re-invites for calls put on hold? Gerry Kernan Infinity IT | 17 The Mall | Beacon Court | Sandyford | Dublin D18 E3C8 | Ireland Tel: +353 - (0)1 - 293 0090 | E-Mail: <mailto:gerry.kernan@infinityit.ie> gerry.kernan(a)infinityit.ie Managed IT Services Infinity IT - <http://www.infinityit.ie/> www.infinityit.ie IP Telephony Asterisk Consulting - <http://www.asteriskconsulting.com> www.asteriskconsulting.com Contact Centre Total Interact - <http://www.totalinteract.com> www.totalinteract.com

3 8

Help me!
by Do Quang Trung 15 Apr '18

15 Apr '18

I use kamailio 5.1.1 with openssl-1.0.2n. I built openssl with gost engine supported and the result when i list cipher list as follow: .................... GOST2001-GOST89-GOST89:GOST94-GOST89-GOST89:ECDH-RSA-AES256-GCM-SHA384:ECDH-ECDSA-AES256-GCM-SHA384:ECDH-RSA-AES256-SHA384:ECDH-ECDSA-AES256-SHA384:ECDH-RSA-AES256-SHA:ECDH-ECDSA-AES256-SHA:AES256-GCM-SHA384:AES256-SHA256:AES256-SHA::GOST94-GOST89-GOST89:ECDH-RSA-AES256-GCM-SHA384:ECDH-ECDSA-AES256-GCM-SHA384:ECDH-RSA-AES256-SHA384:ECDH-ECDSA-AES256-SHA384:ECDH-RSA-AES256-SHA:ECDH-ECDSA-AES256-SHA:AES256-GCM-SHA384:AES256-SHA256:AES256-SHA: ................ i must use exactly GOST2001-GOST89-GOST89 in kamailio to protect sip protocol. Please help me to resolve my problem. Best regards, Trung.

3 2

Kamailio 4.2.8 has crashed
by igor.potjevlesch＠gmail.com 13 Apr '18

13 Apr '18

Hello, I had a crash on one Kamailio instance with the following backtrace: Core was generated by `/usr/local/sbin/kamailio -m 704 -M 128 -P /run/kamailio/kamailio.pid'. Program terminated with signal 6, Aborted. #0 0x00007f92366761f7 in raise () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.6-13.el7.x86_64 elfutils-libelf-0.168-8.el7.x86_64 glibc-2.17-196.el7_4.2.x86_64 keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-8.el7.x86_64 libacl-2.2.51-12.el7.x86_64 libattr-2.4.46-12.el7.x86_64 libcap-2.22-9.el7.x86_64 libcom_err-1.42.9-10.el7.x86_64 libdb-5.3.21-21.el7_4.x86_64 libgcc-4.8.5-16.el7_4.1.x86_64 libselinux-2.5-11.el7.x86_64 libstdc++-4.8.5-16.el7_4.1.x86_64 lm_sensors-libs-3.4.0-4.20160601gitf9185e5.el7.x86_64 lua-5.1.4-15.el7.x86_64 mariadb-libs-5.5.56-2.el7.x86_64 net-snmp-agent-libs-5.7.2-28.el7_4.1.x86_64 net-snmp-libs-5.7.2-28.el7_4.1.x86_64 nspr-4.13.1-1.0.el7_3.x86_64 nss-3.28.4-15.el7_4.x86_64 nss-softokn-freebl-3.28.3-8.el7_4.x86_64 nss-util-3.28.4-3.el7.x86_64 openssl-libs-1.0.2k-8.el7.x86_64 pcre-8.32-17.el7.x86_64 perl-libs-5.16.3-292.el7.x86_64 popt-1.13-16.el7.x86_64 rpm-libs-4.11.3-25.el7.x86_64 tcp_wrappers-libs-7.6-77.el7.x86_64 xz-libs-5.2.2-1.el7.x86_64 zlib-1.2.7-17.el7.x86_64 (gdb) backtrace #0 0x00007f92366761f7 in raise () from /lib64/libc.so.6 #1 0x00007f92366778e8 in abort () from /lib64/libc.so.6 #2 0x000000000061fb2c in qm_free (qm=0x7f91f4eaf000, p=0x7f92110d0300, file=0x7f9226dd7072 "dialog: dlg_hash.c", func=0x7f9226dd9aeb <__FUNCTION__.12761> "destroy_dlg", line=381) at mem/q_malloc.c:474 #3 0x00007f9226d6fb62 in destroy_dlg (dlg=0x7f920f775598) at dlg_hash.c:381 #4 0x00007f9226d75681 in dlg_unref (dlg=0x7f920f775598, cnt=2) at dlg_hash.c:874 #5 0x00007f9226da14d5 in dlg_ontimeout (tl=0x7f920f7755f8) at dlg_handlers.c:1488 #6 0x00007f9226db1e67 in dlg_timer_routine (ticks=8621904, attr=0x0) at dlg_timer.c:283 #7 0x00000000004af537 in compat_old_handler (ti=137950479, tl=0x7f91f7ad8cc8, data=0x7f91f7ad8cc8) at timer.c:1011 #8 0x00000000004aff14 in slow_timer_main () at timer.c:1145 #9 0x000000000052a2af in main_loop () at main.c:1684 #10 0x000000000052fe71 in main (argc=7, argv=0x7fff51f21418) at main.c:2581 (gdb) Is there enough information to understand the reason of the crash? Regards, Igor.

3 5

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

13 Apr '18

Hi All, can anyone share me the installtion steps for kamailio 5.1.2? can i compile and run kamailio 5.1.2 on ubuntu 14.04? i have already used 4.3.6 with polaris configuration to bringup kamailio and i wanna upgrade to kamailio 5.1.2 and the same way can i use 5.1.2 with polaris configuration? I have used polaris scripts to bringup kamailio 5.1.2 and its failing with status kamailio service with Result resources. if i use latest debian packages , are polaris configurations are compatible with latest packages?? Please help me out. Thanks in advance. Regards, vinay

1 0

Is RTPProxy the way to go?
by Robert Johnson 12 Apr '18

12 Apr '18

I'm encountering a situation where an endpoint will renegotiate it's RTP ports but RTPProxy does not honor the new ports and continues to send audio to the old ports. I realize that I'm running a (very) old version of RTPProxy and that I should upgrade before submitting any bugs or asking for help with the program. My question is, is RTPProxy still the way to go? And if so, is v2.0.0 the best version to go with? https://github.com/sippy/rtpproxy/releases At a basic level, the network looks like this +---------------+ +--------------+ | | | | | Priv. Network | | Pub. Network | | | | | +------+ +---------+--+ +---+-------+--+ +--+--------+ | | | | | | | | | PSTN <---> Softswitch <--------> Kamailio + <--------> EndPoints | | | | | | RTPProxy | | | +------+ +---------+--+ | | +--+--------+ | +---+-------+--+ | | | | | +---------------+ +--------------+

2 1

Kamailio + tls
by Do Quang Trung 12 Apr '18

12 Apr '18

Plz help me. I want config kamailio 5.1 support tls using gost89 cipher to protect data.

2 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