- sr-users - kamailio.org

Dialplan Module
by Nelson Migliaro 05 Sep '17

05 Sep '17

Hello, Do you know if its possible to

2 2

Re: [SR-Users] Incorrect value when setting number like values in Htable using Kamcmd
by Tony - Telecomy 05 Sep '17

05 Sep '17

Prefixing the numbers with "s:" fixed the issue. Thank you for your help. Tony

1 0

Incorrect value when setting number like values in Htable using Kamcmd
by Tony - Telecomy 05 Sep '17

05 Sep '17

Hello, I'm having an issue setting phone numbers values in htable using kamcmd when the phone number is above the integer range 2147483647. Initially I planned to set the values as strings but this is not working as expected as well. Please find below some examples: root@tst:~/tst/test# kamcmd htable.seti tst_sim integer_limit "2147483647" root@tst:~/tst/test# kamcmd htable.seti tst_sim integer_exceeded_limit "2147483648" root@tst:~/tst/test# kamcmd htable.sets tst_sim integer_as_string_valid "2147483647" root@tst:~/tst/test# kamcmd htable.sets tst_sim integer_as_string_invalid "2147483648" root@tst:~/tst/test# kamcmd htable.dump tst_sim | grep -A 1 integer name: integer_as_string_valid value: 2147483647 -- name: integer_limit value: 2147483647 -- name: integer_as_string_invalid value: 18446744071562067968 -- name: integer_exceeded_limit value: -2147483648 my ctl params are as follow: modparam("ctl", "binrpc", "unix:/var/run/kamailio/kamailio_ctl") modparam("ctl", "binrpc_max_body_size", 1024) modparam("ctl", "binrpc_struct_max_body_size", 1024) Thanks, Tony

3 2

telcosuite3-crm sql
by Kordován Szabolcs 05 Sep '17

05 Sep '17

Hi, I would like to try the IMS according to the Kamailio World 2017: Kamailio For IMS And VoLTE presentation. Unfortunately I have problem with telcosuite, the sql structure is missing. Where can I find the whole create.sql? Thanks for help. Regards, Szabolcs

3 7

Kamailio SIP protocol over WSS
by Washington Costa 05 Sep '17

05 Sep '17

Hi, I solved my problem. I was missing load some modules and routers. I saw this file as example: https://gist.github.com/jesusprubio/4066845 but is important to know that every module the begin "mi" they aren't supporte on Kamailio 5.0. You will need replace for the module relative the version 5.0. Washington L da Costa Analista de Sistemas (82) 9 9823-4782

2 1

Question about fix_nated_contact.
by Володимир Іванець 04 Sep '17

04 Sep '17

Hello everyone, I have system setup where there are few Asterisk servers behind Kamailio that is behind the firewall. There is a problem with call initiation. When phone from outside sends INVITE to Kamailio, it then passes it to one of Asterisk servers. Asterisk server eventually replies to Kamailio with 200 OK. Contact header contains Asterisk's local IP address and port. Kamailio executes function *fix_nated_contact* before sending reply to the phone. However Contact header will still have Asterisk's local socket. *fix_nated_contact* is being executed with no doubt. I can see xlog output that I set before and after it. Can someone tell how exactly *fix_nated_contact* gets "*request's source address:port pair*" and if it can be printed to the log? Thank you!

1 0

Homer confusion ....
by Mark Boyce 04 Sep '17

04 Sep '17

Hi All Trying to get a basic version of homer working on Kamailio V5. So far I have sipcapture throwing everything in to a single mysql table. So first question; Should I be using sipcapture or siptrace? I’m not sure I can see the difference. Second question; On what I have working so far using sipcapture, I’m seeing the invites, subscribes, cancels, act’s all end up in the database. What I’m missing is any responses from Kamailio back to the handset (AUTh Challenges etc) modparam("sipcapture", "db_url", "mysql://sipcapture:secretpassword@localhost/homer_data") modparam("sipcapture", "capture_on", 1) modparam("sipcapture", "hep_capture_on", 1) modparam("sipcapture", "insert_retries", 5) modparam("sipcapture", "insert_retry_timeout", 10) plus a sprinkling of "sip_capture(); “ in the “xxx_route {“ blocks What am I missing? Mark

4 6

presence_xml mod_init(): Can't bind xcap_client
by Borislav Gergov 04 Sep '17

04 Sep '17

*Hi I have presence_xml parameter force_active set to 1 and still i get **error** presence_xml:mod_init: Can't bind xcap_client* *kamailio 5.1.0-dev6 (x86_64/linux) *

2 3

MWI forwarding between Kamailio and Freeswitch
by Wang, Wallace 04 Sep '17

04 Sep '17

Hello We're using Kamailio & freeswitch as my company voice system. So far, everything is good, except the MWI. I tried to find out how to forward MWI between Kamailio and Freeswitch, or let the Presence_MWI module can work with the freeswitch behind Kamailio. If it was possiable, could anyone give me an idea or some links or demo configure for this. I really appreciate your help. Best Regards Wallace Wang

2 1

uac +kamailio + dispatcher + asterisk
by Жан Базаров 04 Sep '17

04 Sep '17

Hello! provider trunks registration on kamailio UAC?! it's clear. but how does asterisk find out through which trunk the call should be made? I tried to set the header from asterisk dialplan. for example: if (is_method("INVITE")) { #record_route_preset("109.195.102.122"); route(DIRECTION); setflag(FLT_ACC); # do accounting } # ------ LOADBALANCE ROUTE ------------ # if(!ds_is_from_list()) { route(DISPATCH); } route[DISPATCH] { #round robin dispatching on gateways group '1' if(!ds_select_dst("1", "4")) { send_reply("404", "No destination"); exit; } xlog("L_DBG", "--- SCRIPT: going to <$ru> via <$du>\n"); t_on_failure("RTF_DISPATCH"); route(NATMANAGE); route(DRELAY); exit; } route[DIRECTION] { if ($hdr(x-trunk) != $null) { if (!is_method("BYE")){ $fu=""; t_on_failure("MANAGE_FAILURE"); $dlg_ctx(timeout_route) = "DIALOG_END"; $avp(i:10)=43200; $dlg_ctx(timeout_bye) = 0; sql_pvquery("ca", "select l_uuid, auth_username, auth_password, realm, l_domain, r_domain from uacreg where id='$hdr(x-trunk)'", "$avp(uuid), $avp(uname), $avp(passwd), $avp(realm), $avp(src_ipaddr), $avp(dst_ipaddr)"); t_on_failure("MANAGE_FAILURE"); $dlg_ctx(timeout_route) = "DIALOG_END"; $avp(i:10)=43200; $dlg_ctx(timeout_bye) = 0; $fu=""; uac_replace_from("sip:$avp(uname)@$avp(dst_ipaddr)"); $tu="sip:"+$tU+"@"+$avp(dst_ipaddr); $ru="sip:"+$tU+"@"+$avp(dst_ipaddr); remove_hf("Contact"); $var(contact)="sip:"+$avp(uname)+"@10.49.9.2:5060"; insert_hf("Contact: <$var(contact)>\r\n"); #insert_hf("Contact: "); msg_apply_changes(); fix_nated_register(); xlog("L_INFO","Contact header $var(contact) 111111111111111111111111111111111111111 is $ct {$ct}\n"); route(RELAY); } #### BYE } ### XTRUNK But in this configuration I do not come bye but when I register providers trunks on asterisk - problem with BYE not visible. but I can not register provider-trunks on all the asterisks, because incoming invite arrives at the link + address, and all the asteriscs ring. All my asterisk's behind nat

2 1

jsonrpcs execution error
by David Villasmil 04 Sep '17

04 Sep '17

Hello guys, i configured jsonrpc on kamailio.cfg and RPCFIFOPATH on kamctlrc to the same file, seems to work for some commands, but not for others: root@ip-172-31-30-160:/home/admin# kamctl trusted show +----+--------------+-------+--------------+--------------+------+----------+ | id | src_ip | proto | from_pattern | ruri_pattern | tag | priority | +----+--------------+-------+--------------+--------------+------+----------+ | 1 | 1.2.3.4 | udp | | NULL | | 0 | | 2 | 5.4.3.2 | udp | | NULL | | 0 | +----+--------------+-------+--------------+--------------+------+----------+ root@ip-172-31-30-160:/home/admin# kamctl trusted dump { "jsonrpc": "2.0", "error": { "code": -32000, "message": "Execution Error" }, "id": 32022 } root@ip-172-31-30-160:/home/admin# kamctl trusted reload { "jsonrpc": "2.0", "error": { "code": -32000, "message": "Execution Error" }, "id": 32041 } Any help? Thanks! Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 ᐧ

2 2

Carrierroute, uac_*, failure_route.
by yu＠yu-boot.ru 04 Sep '17

04 Sep '17

Hello. Have a following task. Select carrier by carrierroute module from db, try to route (dial, relay, bridge - you name it) call there and if call is failed/rejected due to any reason, go to failure_route(?), perform carrierroute lookup again for another carrier and route call there. Main problem is that different carriers require different From/To format. And Kamailio don't allow to use uac* functions in failure_route. How to resolve this? Maybe entire routing method is wrong for my task? Any advice? -- sent from myMail for Android

3 3

Re: [SR-Users] [Freeswitch-users] Fwd: Call drops after 32 seconds with ACK Timeout
by Karsten Horsmann 02 Sep '17

02 Sep '17

Hi Mykyta, since you are plain sip without encryption you can see your sip-traffic on the wire, use sngrep on the kamailio box to figure out whats with the sip-dialogs - it helps a lot. https://github.com/irontec/sngrep and if its more an kamailio config problem, it would be better to stay at sr-users@. Or you can setup an webhomer for debugging. Kind Regards 2017-09-01 17:49 GMT+02:00 Sean Ingham <sean(a)missionlabs.co.uk>: > Once a call is answered FreeSWITCH sends a 200 OK SIP message to your > Kamailio loadbalancer. As per the SIP spec your kamailio box should respond > to a 200 OK with an ACK. The FS logs show that it never receives an ACK, > and it repeatedly tries sending the 200 OK with no response. After 30 > seconds without an ACK FS will assume the call has failed and hangup. > > Looking at your Kamailio SIP logs you can see the 200 OKs getting through > okay, and no attempt to send an ACK back to FS. I think this indicates an > issue with your kamailio.cfg rather than FreeSWITCH. > > > Sean > www.wirex-precision.co.uk > > On Fri, Sep 1, 2017 at 3:40 PM, Микита Нікітенко < > nikitanikitenko(a)gmail.com> wrote: > >> >> Hello! I have server at digital ocean with a floating ip address and I >> have routed sip traffic to this floating ip. At this server installed >> kamailio which balancing between freeswitch servers. I have a problem that >> call drops after 32 seconds with error ACK Timeout. Traffic comming throug >> the kamailio proxy. >> >> kamailio.cfg - https://pastebin.com/x0CL3TEZ >> kamailio sip messages log - https://pastebin.com/wyT3cBbD >> freeswitch logs with sip debug - https://pastebin.com/zPysfQkV >> >> I'm struggling for a week and have no idea how to fix it. >> Thank you very much. >> Mykyta Nikitenko >> >> >> >> -- Mit freundlichen Grüßen *Karsten Horsmann*

2 1

Call drops after 32 seconds with ACK Timeout
by Микита Нікітенко 01 Sep '17

01 Sep '17

Hello! I have server at digital ocean with a floating ip address and I have routed sip traffic to this floating ip. At this server installed kamailio which balancing between freeswitch servers. I have a problem that call drops after 32 seconds with error ACK Timeout. kamailio.cfg - https://pastebin.com/x0CL3TEZ kamailio sip messages log - https://pastebin.com/wyT3cBbD freeswitch logs with sip debug - https://pastebin.com/zPysfQkV I'm struggling for a week and have no idea how to fix it. Thank you very much. Mykyta Nikitenko

2 1

Change on the fly logging verbosity - Kamailio v5.0.2
by Karsten Horsmann 01 Sep '17

01 Sep '17

Hello, at this moment i try to figure out the best way to add an "switch" for debug/log output. I use many xlog, like everyone that starts with kamailio too. Then i go further and add #!ifdef cases around to switch this via #!define. Is there any other way to turn on/off my "debug"-logging on the fly, while kamailio is still running? #!define TESTBED_MODE request_route{ ... #!ifdef TESTBED_MODE route(DEBUG); #!endif ... #!ifdef TESTBED_MODE xlog("L_INFO","---FIX_SIPS-after: ru:($ru)"); #!endif ... } -- Kind Regards *Karsten Horsmann*

3 3

Kamailio v5.0.3 Released
by Daniel-Constantin Mierla 01 Sep '17

01 Sep '17

Hello, Kamailio SIP Server v5.0.3 stable release is out! This is a maintenance release of the latest stable branch, 5.0, that includes fixes since the release of v5.0.2. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.0.x. Deployments running previous 5.0.x versions are strongly recommended to be upgraded to v5.0.3. For more details about version 5.0.3 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2017/09/kamailio-v5-0-3-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda

2 2

last pkg.stats entry
by Juha Heinanen 01 Sep '17

01 Sep '17

When I make pkg.stats query (latest master), I get a weird last entry. What is it? -- Juha ... { entry: 28 pid: 14675 rank: -4 used: 9450336 free: 2354944 real_used: 10227968 total_size: 12582912 total_frags: 310 } { entry: 29 pid: 0 rank: -128 used: 0 free: 0 real_used: 0 total_size: 12582912 total_frags: 0 }

2 5

Planning Kamailio v5.0.3
by Daniel-Constantin Mierla 01 Sep '17

01 Sep '17

Hello, I am considering to release Kamailio v5.0.3 sometime next week, therefore it is the time to backport patches with fixes from master that apply to 5.0 branch. If you are aware of such fix that has to be backported, reply here or make a pull request on github project. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com

2 3

Kamailio SIP protocol over WSS
by Washington Costa 31 Aug '17

31 Aug '17

Hello, I'm using kamailio 5.0.2 (x86_64/linux). And it works with WS. Regards, Washington Costa

1 0

Kamailio SIP protocol over WSS
by Washington Costa 31 Aug '17

31 Aug '17

Hi. I'm trying use the JSSIP cliente and Kamailio with WSS. On these sites I generated my certificates: https://letsencrypt.org/ and https://certbot.eff.org/ My browser identify the certificates but SIP client just say: failed: WebSocket opening handshake was canceled Do you have any idea how to fix it? Do you can say a checklist with everything I need to do for use Kamailio with WSS? Here is my log on Kamailio: Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 33(13239) DEBUG: <core> [core/ip_addr.c:229]: print_ip(): tcpconn_new: new tcp connection: 187.41.60.10 Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 33(13239) DEBUG: <core> [core/tcp_main.c:985]: tcpconn_new(): on port 44630, type 3 Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 33(13239) DEBUG: <core> [core/tcp_main.c:1291]: tcpconn_add(): hashes: 3062:1194:1491, 2 Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 33(13239) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa4ac60, 53, 2, 0x7f259df9cd80), fd_no=44 Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 33(13239) DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xa4ac60, 53, -1, 0x0) fd_no=45 called Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 33(13239) DEBUG: <core> [core/tcp_main.c:4139]: handle_tcpconn_ev(): sending to child, events 1 Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 33(13239) DEBUG: <core> [core/tcp_main.c:3818]: send2child(): selected tcp worker 1 26(13225) for activity on [tls:172.31.39.220:4443], 0x7f259df9cd80 Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 26(13225) DEBUG: <core> [core/tcp_read.c:1574]: handle_io(): received n=8 con=0x7f259df9cd80, fd=9 Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 26(13225) DEBUG: tls [tls_server.c:197]: tls_complete_init(): completing tls connection initialization Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 26(13225) DEBUG: tls [tls_server.c:226]: tls_complete_init(): Using initial TLS domain TLSs<default> (dom 0x7f259ddc4a80 ctx 0x7f259de03bc0 sn []) Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 26(13225) DEBUG: tls [tls_domain.c:715]: sr_ssl_ctx_info_callback(): SSL handshake started Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 26(13225) DEBUG: <core> [core/tcp_main.c:2430]: tcpconn_do_send(): sending... Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 26(13225) DEBUG: <core> [core/tcp_main.c:2464]: tcpconn_do_send(): after real write: c= 0x7f259df9cd80 n=2568 fd=9 Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 26(13225) DEBUG: <core> [core/tcp_main.c:2465]: tcpconn_do_send(): buf= Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: #026#003#001 Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 26(13225) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa93f00, 9, 2, 0x7f259df9cd80), fd_no=1 Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 26(13225) DEBUG: <core> [core/tcp_read.c:195]: tcp_emit_closed_event(): TCP closed event creation triggered Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 26(13225) DEBUG: <core> [core/tcp_read.c:202]: tcp_emit_closed_event(): no callback registering for handling TCP closed event - dropping! Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 26(13225) DEBUG: <core> [core/tcp_read.c:305]: tcp_read_data(): EOF on 0x7f259df9cd80, FD 9 ([187.41.60.10]:44630 ->26(13225) DEBUG: <core> [core/tcp_read.c:306]: tcp_read_data(): -> [172.31.39.220]:4443) Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 26(13225) DEBUG: <core> [core/tcp_read.c:1341]: tcp_read_req(): EOF Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 26(13225) DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xa93f00, 9, -1, 0x10) fd_no=2 called Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 26(13225) DEBUG: <core> [core/tcp_read.c:1495]: release_tcpconn(): releasing con 0x7f259df9cd80, state -1, fd=9, id=2 ([187.41.60.10]:44630 -> [187.41.60.10]:4443) Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 26(13225) DEBUG: <core> [core/tcp_read.c:1499]: release_tcpconn(): extra_data 0x7f259dfb6488 Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 33(13239) DEBUG: <core> [core/tcp_main.c:3250]: handle_tcp_child(): reader response= 7f259df9cd80, -1 from 1 Aug 31 09:10:10 ip-172-31-39-220 kamailio[13183]: 33(13239) DEBUG: tls [tls_server.c:665]: tls_h_close(): Closing SSL connection 0x7f259dfb6488 Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 33(13239) DEBUG: <core> [core/ip_addr.c:229]: print_ip(): tcpconn_new: new tcp connection: 187.41.60.10 Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 33(13239) DEBUG: <core> [core/tcp_main.c:985]: tcpconn_new(): on port 44692, type 3 Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 33(13239) DEBUG: <core> [core/tcp_main.c:1291]: tcpconn_add(): hashes: 2869:1129:1296, 3 Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 33(13239) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa4ac60, 53, 2, 0x7f259df9cd80), fd_no=44 Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 33(13239) DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xa4ac60, 53, -1, 0x0) fd_no=45 called Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 33(13239) DEBUG: <core> [core/tcp_main.c:4139]: handle_tcpconn_ev(): sending to child, events 1 Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 33(13239) DEBUG: <core> [core/tcp_main.c:3818]: send2child(): selected tcp worker 2 27(13226) for activity on [tls:172.31.39.220:4443], 0x7f259df9cd80 Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 27(13226) DEBUG: <core> [core/tcp_read.c:1574]: handle_io(): received n=8 con=0x7f259df9cd80, fd=9 Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 27(13226) DEBUG: tls [tls_server.c:197]: tls_complete_init(): completing tls connection initialization Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 27(13226) DEBUG: tls [tls_server.c:226]: tls_complete_init(): Using initial TLS domain TLSs<default> (dom 0x7f259ddc4a80 ctx 0x7f259de05708 sn []) Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 27(13226) DEBUG: tls [tls_domain.c:715]: sr_ssl_ctx_info_callback(): SSL handshake started Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 27(13226) DEBUG: <core> [core/tcp_main.c:2430]: tcpconn_do_send(): sending... Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 27(13226) DEBUG: <core> [core/tcp_main.c:2464]: tcpconn_do_send(): after real write: c= 0x7f259df9cd80 n=2568 fd=9 Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 27(13226) DEBUG: <core> [core/tcp_main.c:2465]: tcpconn_do_send(): buf= Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: #026#003#001 Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 27(13226) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa93f00, 9, 2, 0x7f259df9cd80), fd_no=1 Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 27(13226) DEBUG: <core> [core/tcp_read.c:195]: tcp_emit_closed_event(): TCP closed event creation triggered Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 27(13226) DEBUG: <core> [core/tcp_read.c:202]: tcp_emit_closed_event(): no callback registering for handling TCP closed event - dropping! Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 27(13226) DEBUG: <core> [core/tcp_read.c:305]: tcp_read_data(): EOF on 0x7f259df9cd80, FD 9 ([187.41.60.10]:44692 ->27(13226) DEBUG: <core> [core/tcp_read.c:306]: tcp_read_data(): -> [172.31.39.220]:4443) Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 27(13226) DEBUG: <core> [core/tcp_read.c:1341]: tcp_read_req(): EOF Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 27(13226) DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xa93f00, 9, -1, 0x10) fd_no=2 called Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 27(13226) DEBUG: <core> [core/tcp_read.c:1495]: release_tcpconn(): releasing con 0x7f259df9cd80, state -1, fd=9, id=3 ([187.41.60.10]:44692 -> [187.41.60.10]:4443) Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 27(13226) DEBUG: <core> [core/tcp_read.c:1499]: release_tcpconn(): extra_data 0x7f259dfb6488 Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 33(13239) DEBUG: <core> [core/tcp_main.c:3250]: handle_tcp_child(): reader response= 7f259df9cd80, -1 from 2 Aug 31 09:10:17 ip-172-31-39-220 kamailio[13183]: 33(13239) DEBUG: tls [tls_server.c:665]: tls_h_close(): Closing SSL connection 0x7f259dfb6488

2 1

question for best way to remove sips uris - TLS and sips in $ru - get_send_socket2(): protocol/port mismatch
by Karsten Horsmann 31 Aug '17

31 Aug '17

Hello List, of course - best way is not to use sips: uri scheme. But i have to deal with that. I try to configure an multihomed kamailio (public/private IP) in front of my SIP-Servers. One of my softphones variants used TLS for connection but the INVITES of this softphone use the "sips" URI scheme. As i saw in other posts, this seems to be an issue for many people. In my case it breaks the routing to my internal sip-server (only plain udp). Most of my config is similar to havfos example + TLS. https://github.com/havfo/WEBRTC-to-SIP/blob/master/etc/kamailio/kamailio.cfg I tried to fixed that with this extra route - but this breaks the dialog somewhere - after 60 seconds i have no audio and the BYE becomes another CSeq: in the request_route right after route(AUTH) i add my route(FIX_SIPS) if (is_method("INVITE|SUBSCRIBE")) { if ($ru =~ "^sips:") { route(FIX_SIPS); } else { record_route(); } } route[FIX_SIPS] { if ($ru =~ "^sips:") { xlog("L_INFO","---FIX_SIPS-before: ru:($ru)"); $var(orig_uri) = $ru; $ru = "sip:" + $rU + "@" + $td; xlog("L_INFO","---FIX_SIPS-now: $rU $td ru:($ru) orig_uri:($var(orig_uri))"); record_route(); #$ru = $var(orig_uri); xlog("L_INFO","---FIX_SIPS-after: ru:($ru)"); } } 172.20.120.81 = Kamailio private IP 172.20.120.79 = My internal SIP-Server (B2BUA) I used kamailio with CentOS 7 and RTPENGINE 63bdd615 from master kamailio-5.0.2-3.1.x86_64 kamailio-tls-5.0.2-3.1.x86_64 kamailio-mysql-5.0.2-3.1.x86_64 kamailio-websocket-5.0.2-3.1.x86_64 -- Kind Regards *Karsten Horsmann*

1 2

sql_do_query_async(): the db driver module doesn't support async query
by Juha Heinanen 31 Aug '17

31 Aug '17

sqlops README tells: 4.5. sql_query_async(connection, query) Make an async SQL query using 'connection', if implemented by db driver module (e.g., db_mysql) my sqlops sqlcon parameter specifies mysql driver, but still i get to syslog: Aug 24 08:02:05 rox1 /usr/bin/sip-proxy[13886]: ERROR: sqlops [sql_api.c:427]: sql_do_query_async(): the db driver module doesn'tsupport async query any idea why? -- juha

2 7

kamailio asterisk + provider sip trunks
by Жан Базаров 31 Aug '17

31 Aug '17

Good morning! kamailio + dispatcher + provider trunks. How to make RR for incoming calls from pstn? my trunks are authorized on an asterisk, but i have problem with multiple calls on each asterisk. If I do through uac then I have a problem with BYE, and in general the module is uncomfortable. Please tell me how to implement a bunch: kamailio + asterisk + provider trunks..

2 1

Kamailio failover - dialog (transaction) that is available on different proxies
by Donat Zenichev 30 Aug '17

30 Aug '17

Hi. I came up with idea to set up stand with two kamailio and one b2bua server (for routing). The idea consists of failover for dialogs, transactions. So if one of kamailio nodes is down, another one is able to catch up the dialog and let users to properly end up the session. For better realizing of it, I will try to describe the idea step by step: 1. UAC invites UAS, they've done three-way-handshake, media stream is up. 2. Kamailio that processed this dialog is down. 3. Users decided to end the session with BYE method, but proxy that processed their three-way-handshake recently is down, so one of ua sends BYE to the destination route that contains domain name (that both kamailio serve), BYE achieves the second kamailio to let him properly end the dialog. But, there is a big but, this second kamailio hasn't ever known about this dialog, he doesn't support any transactions for it and furthermore he doesn't know anything about this call-id. So the solution for it, as I think, is hidden in db mode for user location (columns that contain call-ids, branches etc. But I need to be sure, if I'm on the right way. For purpose, where one ip is served by two nodes, I have two solutions: -First one. I want to create heartbeat cluster with two kamailio nodes, they will have one shared ip address, so when one node gets down, another one brings up shared ip interface and implements the same actions that master does. -Another method is to assign a few ip addresses to one domain name (ip addresses of different kamailio proxies). So the goal looks simple, if someone has ever done something like that, I will be glad to read the ideas. -- -- BR, Donat Zenichev Wnet VoIP team Tel: +380(44) 5-900-808 http://wnet.ua

3 5

Simultaneous calls in kamailio
by Logeshwaran G 30 Aug '17

30 Aug '17

Hi, Is there any way(tools) to place Simultaneous Calls in kamailio: For Example: 1000 calls simultaneously in Kamailio. Input Please?? Thanks & Kind Regards, Logeshwaran G

4 6

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