- sr-users - kamailio.org

http_client_query API of http_client module issue.
by vivek＠advaitamtech.com 21 Apr '17

21 Apr '17

Hi All, Am executing the curl GET request using the API http_client_query(url, [post-data], result) like its mentioned in the http_client module page. In the result part of the called API, I am receiving only the first line of the response to the GET request sent. How do I get or access the full response? Thanks, Vivek.

1 0

Kamailio World 2017 - grants for students and underrepresented people
by Daniel-Constantin Mierla 21 Apr '17

21 Apr '17

Hello, with a bit of delay, given that had to accommodate and accept some requests from the last year queue, I am glad to announces that we can offer two more seats at Kamailio World Conference, May 8-10, 2017, in Berlin. Therefore we are continuing the program from last years, based on the roots and the tight relation of Kamailio project with the academic environment, the eligible people being students enrolled in universities or research institutes (both bachelor and PhD programs qualify) as well as people from underrepresented groups. If you think you are eligible and want to participate, email me directly (miconda(a)gmail.com) or to registration(a)kamailio.org . Participation to all the content of the event (workshops, conference and social event) is free, but you will have to take care of expenses for traveling and accommodation. Write a short description about your interest in real time communications and, when it is the case what is the university or the research institute you are affiliate to. Also, if you are not a student, but you are in touch with some or have access to students forums/mailing lists, it will be very appreciated if you forward these details. Time is short, we already received few requests based on my remark in a message sent out few weeks ago, therefore in a matter of days we will do the selection, so you have to hurry up a bit. More information about Kamailio World is available on the web site: - http://www.kamailioworld.com Many thanks to the event sponsors that allowed to continue this program, respectively: FhG Fokus, Asipto, Flowroute, Telnyx, Sipwise, Sipgate, Simwood, Obihai, NG-Voice, Evariste Systems, Digium, VoiceTel, Pascom and Core Network Dynamics. Expect a full house event! Looking forward to meeting many of you in Berlin! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - May 22-24 (USA) - www.asipto.com Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com

1 0

New developer: Guillaume Bour
by Daniel-Constantin Mierla 21 Apr '17

21 Apr '17

Hello, I would like to announce that Guillaume Bour (https://github.com/gbour) has now developer privileges on Kamailio's gihub project. He has contributed recently a new module named keepalive: - http://kamailio.org/docs/modules/devel/modules/keepalive.html There is also a pull request from him waiting to be merge to drouting module, adding capability of detecting active/inactive gateways used by the module. Thanks for the contributions so far and looking forward to collaborate in the future! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - May 22-24 (USA) - www.asipto.com Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com

1 0

http_async_query in event_route[dialog:start] does not work
by Pranathi Venkatayogi 21 Apr '17

21 Apr '17

Hi, I wanted to make an http_async_query in event_route[dialog:start] after the call the confirmed. I see that flow does not even get to making "async_send_query". Perhaps it is failing at the first line "if (msg==null)" in w_http_async_post as I don't see any other error messages from the module. I can confirm that my setup and api server are fine as other calls I make from request_route and event_route[dialog:end] are working. I am attaching herewith my config files and Kamailio.log file. Relevant prob spot is below- Apr 20 17:37:17 devsip00 /sbin/kamailio[6286]: {2 3094 INVITE d9695149ce484811ab98ca41a4e8c694} INFO: <script>: Translation: TextBroker - Making CallAnswered for d9695149ce484811ab98ca41a4e8c694 If you notice we don't see any further progress of this call in http_async_client module. Can someone suggest what I am missing/where else can I know for sure dialog is confirmed and make this call. Pranathi Venkatayogi System Developer II (520) 745-9447 x4466 www.cyracom.com<http://www.cyracom.com/> Join us: [cid:image001.gif@01D1C9C9.C4E8B6D0] <https://www.facebook.com/pages/CyraCom-LLC/134704783312720> [cid:image002.gif@01D1C9C9.C4E8B6D0] <https://twitter.com/cyracom> [cid:image003.gif@01D1C9C9.C4E8B6D0] <http://www.linkedin.com/company/cyracom> [cid:image004.gif@01D1C9C9.C4E8B6D0] <http://www.cyracom.com/blog/> [cid:image005.png@01D1C9C9.C4E8B6D0] DISCLAIMER: This e-mail and any attached content may contain confidential or privileged material delivered for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender immediately by reply e-mail and delete all copies of this message. It is the recipient's responsibility to scan this e-mail and any attachments for viruses. The content of this e-mail message, including any attachments, does not comprise a contract or a portion of a contract, and so does not bind CyraCom International, Inc. or any of its agents or subsidiaries. CyraCom, LLC and Voiance Language Services, LLC are wholly owned subsidiaries of CyraCom International, Inc.

2 1

Kamailio 5.0 doesn't forward Authorization (Digest username) to Asterisk
by gh 21 Apr '17

21 Apr '17

Hi Marko, i work on the same scenario. It should work with: if(uac_reg_request_to("$fU", 0)) { xlog("L_NOTICE", "Found remote user [$rU] on [$rd] via [$du]"); t_on_failure("REMOTE_AUTH"); t_relay(); } But in my case xlog() currently does not print out the variables, so i am not able to debug:-( Can you try this code and tell me if xlog() works for you? Best regards Georg

3 7

Planning next IRC devel meeting - Apr 20, 2017
by Daniel-Constantin Mierla 20 Apr '17

20 Apr '17

Hello, probably it is the time to have another IRC devel meeting to discuss the plans for the project and the roadmap to next major release, v5.1. First proposed date would be Apr 20, with secondary options for Apr 24 or 25, but other dates can be taken in consideration if more convenient for a consistent group of developers. I created the wiki page for it at: * https://www.kamailio.org/wiki/devel/irc-meetings/2017a Feel free to add there the subjects you want to discuss, I also have several other topics to add. It would be good to list yourself if you are going to participate (or want to participate) in a specific day in order to see who are we relying on being present. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - May 22-24 (USA) - www.asipto.com Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com

1 4

Reply to Incoming SIP Options Pings from Kamailio
by SIP Tech 20 Apr '17

20 Apr '17

Hello, I have a simple Kamailio server built that acts as a stateless load balancer for incoming SIP calls. All kamailio does here is receive the incoming call and route it round robin to a Freeswitch machine behind it. All configuration in Kamailio is done in local config files including the use of dispatcher.list. I have an external 3rd party partner sending my Kamailio machine SIP options pings. Because my Kamailio sends all incoming calls stateless to a FS machine behind it (round robin) the FS machines behind Kamailio get the incoming ping requests and generate the 200 OK reply back to kamailio. I would like the 3rd party to get a 200 OK for pings directly from my Kamailio and not from freeswitch behing it. I have the need to scale FS machines on the fly so I don't want FS machines to be responsible for the sip options ping replies. I want Kamailio itself to reply with a static 200 OK to incoming ping requests. I have looked into nathelper and siputils options_reply to see if I could get a simple static config to handle this 200 OK directly from Kamailio. I cant get it to fully work as the incoming sip pings still hit freeswitch. How can I configure this in the kamailio.cfg to get kamailio itself to reply with a 200 OK to SIP Options Pings and NOT forward the ping request to freeswitch? Here is my current simple stateless LB config in kamailio that works great for what it is and for what I need for loadbalancing incoming call requests. route{ if ( !mf_process_maxfwd_header("10") ) { sl_send_reply("483","To Many Hops"); drop(); }; ds_select_dst("1", "4"); forward(); #stateless forward # t_relay(); #stateful relay } Here is a sample of what the incoming pings look like that hit Kamailio. U 2017/04/19 21:21:00.89 192.168.168.168:5060 -> 172.31.31.31:5060 OPTIONS sip:172.31.31.31:5060 SIP/2.0. Via: SIP/2.0/UDP 192.168.168.168:5060;branch=z9hG. Call-ID: 536f9b34c(a)192.168.168.168. To: sip:ping@172.31.31.31. From: <sip:ping@192.168.168.168>;tag=2b769f. Max-Forwards: 70. CSeq: 91160 OPTIONS. Route: <sip:172.31.31.31:5060;lr>. Using the above info what would a route look like in kamailio.cfg for this? What specific modules need to be installed/enabled to make your suggested route functional? Thanks guys

2 1

How to print out all variables in case we reach this line?
by gh 19 Apr '17

19 Apr '17

If i call a mobil number: t: <sip:+4917625251111@sip.heissa.de>. i get 404, but would expect rewrite to carrier route: sip:+4917625251111@sip.nexxtmobile.de Is there a way to print out all variables at this moment? ########################################################### if ( is_method("ACK") ) { if ( t_check_trans() ) { # no loose-route, but stateful ACK; # must be an ACK after a 487 # or e.g. 404 from upstream server route(RELAY); exit; } else { # ACK without matching transaction ... ignore and discard exit; } } sl_send_reply("404", "Not here"); #How to print out all variables in case we reach this line??? exit; ###########################################################

4 11

to tag length
by Diego Nadares 19 Apr '17

19 Apr '17

Hi guys, Does exist a max length for to tag? Because I'm saving dialogs in mysql and yesterday a message had a to tag greater than varchar 64. db_mysql_submit_query(): driver error on query: Data too long for column 'to_tag' at row 1 The length of the to tag was 65 (SDu81l799-7f56830f3e18-100007f-13c4-6009-73d4c9b-10f3d231-73d4c9b) Cheers, Diego

2 1

Re: [SR-Users] problem with avpops and mongodb modules
by hdssdsdsdsfsdf hdssdsdsdsfsdf 18 Apr '17

18 Apr '17

>On 22/02/2017 14:35, hsdsdssdfsdf dsasd wrote: >> I implemented call forwarding according to >> https://www.kamailio.org/wiki/tutorials/mini-howto-admin/call_forwarding, >> which is working fine. When I replace db_mysql with db_mongodb >> however, I receive an error on "if (avp_db_load("$ruri/username", >> "$avp(s:fwd_blind)")) {": >> >> ERROR: db_mongodb [mongodb_dbase.c:381]: db_mongodb_get_columns(): >> field [attribute] not found in result iterator >> ERROR: db_mongodb [mongodb_dbase.c:739]: db_mongodb_store_result(): >> failed to set the columns >> ERROR: db_mongodb [mongodb_dbase.c:918]: db_mongodb_query(): failed to >> store result >> ERROR: db_mongodb [mongodb_dbase.c:927]: db_mongodb_query(): failed to >> do the query >> ERROR: avpops [avpops_impl.c:381]: ops_dbload_avps(): db_load failed >can you set debug=3 in kamailio.cfg, restart kamailio and test again? >Then grab the log messages from syslog and send them here. It should >provide more debug information. > >Is there a record for this query? Or should be an empty response (no >record returned)? > >Cheers, >Daniel I used the following to store a forward: avp_db_store("$from/username","$avp(s:fwd_blind)"); Which in this case resulted in (after replacing the true forward info): > db.usr_preferences.find() { "_id" : ObjectId("58ac40f7e498420e0703a2e1"), "uuid" : "", "attribute" : "fwd_blind", "value" : "sip:0003@x.x.x;user=phone", "type" : 0, "username" : "0002", "domain" : null } After setting: debug=3 ... xlog("bla00"); if (avp_db_load("$ruri/username", "$avp(s:fwd_blind)")) { xlog("bla01" ... } xlog("bla02"); ... The syslog shows (after replacing the true username): Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: ERROR: <script>: bla00 Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: DEBUG: db_mongodb [mongodb_dbase.c:851]: db_mongodb_query(): query to collection [usr_preferences] Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: DEBUG: db_mongodb [mongodb_dbase.c:885]: db_mongodb_query(): query filter: { "username" : "0002", "attribute" : "fwd_blind" } Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: DEBUG: db_mongodb [mongodb_dbase.c:904]: db_mongodb_query(): columns filter: { "value" : 1, "attribute" : 1, "type" : 1 } Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: DEBUG: <core> [db_res.c:116]: db_new_result(): allocate 56 bytes for result set at 0x7fa03e54a6a0 Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: DEBUG: db_mongodb [mongodb_dbase.c:349]: db_mongodb_get_columns(): 3 columns returned from the query Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: DEBUG: <core> [db_res.c:154]: db_allocate_columns(): allocate 24 bytes for result names at 0x7fa03e54a798 Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: DEBUG: <core> [db_res.c:165]: db_allocate_columns(): allocate 12 bytes for result types at 0x7fa03e549848 Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: DEBUG: db_mongodb [mongodb_dbase.c:377]: db_mongodb_get_columns(): Found a field[0] named: value Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: DEBUG: db_mongodb [mongodb_dbase.c:396]: db_mongodb_get_columns(): allocate 16 bytes for RES_NAMES[0] at 0x7fa03e549798 Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: DEBUG: db_mongodb [mongodb_dbase.c:431]: db_mongodb_get_columns(): use DB1_STRING result type Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: DEBUG: db_mongodb [mongodb_dbase.c:460]: db_mongodb_get_columns(): RES_NAMES(0x7fa03e549798)[0]=[value] (2) Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: DEBUG: db_mongodb [mongodb_dbase.c:377]: db_mongodb_get_columns(): Found a field[1] named: attribute Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: ERROR: db_mongodb [mongodb_dbase.c:381]: db_mongodb_get_columns(): field [attribute] not found in result iterator Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: ERROR: db_mongodb [mongodb_dbase.c:739]: db_mongodb_store_result(): failed to set the columns Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: ERROR: db_mongodb [mongodb_dbase.c:918]: db_mongodb_query(): failed to store result Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: ERROR: db_mongodb [mongodb_dbase.c:927]: db_mongodb_query(): failed to do the query Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: DEBUG: <core> [db_res.c:79]: db_free_columns(): freeing 3 columns Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: DEBUG: <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[0] at 0x7fa03e549798 Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: DEBUG: <core> [db_res.c:92]: db_free_columns(): freeing result names at 0x7fa03e54a798 Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: DEBUG: <core> [db_res.c:97]: db_free_columns(): freeing result types at 0x7fa03e549848 Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: DEBUG: <core> [db_res.c:134]: db_free_result(): freeing result set at 0x7fa03e54a6a0 Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: ERROR: avpops [avpops_impl.c:381]: ops_dbload_avps(): db_load failed Feb 24 10:42:18 slb04 /usr/local/sbin/kamailio[20311]: ERROR: <script>: bla02 When changing to db_mysql the error does not occur. I got the following record there: MariaDB [kamailio]> select * from usr_preferences; +----+------+-------------+--------+-----------+------+-------------------------------------------+---------------------+ | id | uuid | username | domain | attribute | type | value | last_modified | +----+------+-------------+--------+-----------+------+-------------------------------------------+---------------------+ | 26 | | 0002 | | fwd_blind | 0 | sip:0003@x.x.x;user=phone | 1900-01-01 00:00:01 | +----+------+-------------+--------+-----------+------+-------------------------------------------+---------------------+ With the same kamailio.cfg (except for replacing mongodb with mysql) resulting in: Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: ERROR: <script>: bla00 Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: <core> [db_res.c:116]: db_new_result(): allocate 56 bytes for result set at 0x7fd17c349800 Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: db_mysql [km_res.c:66]: db_mysql_get_columns(): 3 columns returned from the query Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: <core> [db_res.c:154]: db_allocate_columns(): allocate 24 bytes for result names at 0x7fd17c32f400 Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: <core> [db_res.c:165]: db_allocate_columns(): allocate 12 bytes for result types at 0x7fd17c33fae8 Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: db_mysql [km_res.c:84]: db_mysql_get_columns(): allocate 16 bytes for RES_NAMES[0] at 0x7fd17c349350 Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: db_mysql [km_res.c:91]: db_mysql_get_columns(): RES_NAMES(0x7fd17c349350)[0]=[value] Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: db_mysql [km_res.c:135]: db_mysql_get_columns(): use DB1_STRING result type Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: db_mysql [km_res.c:84]: db_mysql_get_columns(): allocate 16 bytes for RES_NAMES[1] at 0x7fd17c349458 Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: db_mysql [km_res.c:91]: db_mysql_get_columns(): RES_NAMES(0x7fd17c349458)[1]=[attribute] Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: db_mysql [km_res.c:135]: db_mysql_get_columns(): use DB1_STRING result type Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: db_mysql [km_res.c:84]: db_mysql_get_columns(): allocate 16 bytes for RES_NAMES[2] at 0x7fd17c3493a8 Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: db_mysql [km_res.c:91]: db_mysql_get_columns(): RES_NAMES(0x7fd17c3493a8)[2]=[type] Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: db_mysql [km_res.c:99]: db_mysql_get_columns(): use DB1_INT result type Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: <core> [db_res.c:184]: db_allocate_rows(): allocate 16 bytes for rows at 0x7fd17c33fb98 Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: <core> [db_row.c:117]: db_allocate_row(): allocate 96 bytes for row values at 0x7fd17c33f778 Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: <core> [db_val.c:118]: db_str2val(): converting STRING [sip:0003@x.x.x;user=phone] Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: <core> [db_val.c:118]: db_str2val(): converting STRING [fwd_blind] Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: <core> [db_val.c:74]: db_str2val(): converting INT [0] Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: avpops [avpops_impl.c:132]: dbrow2avp(): db_flags=3, flags=12 Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: avpops [avpops_db.c:265]: db_close_query(): close avp query Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: <core> [db_res.c:79]: db_free_columns(): freeing 3 columns Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[0] at 0x7fd17c349350 Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[1] at 0x7fd17c349458 Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[2] at 0x7fd17c3493a8 Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: <core> [db_res.c:92]: db_free_columns(): freeing result names at 0x7fd17c32f400 Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: <core> [db_res.c:97]: db_free_columns(): freeing result types at 0x7fd17c33fae8 Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: <core> [db_res.c:52]: db_free_rows(): freeing 1 rows Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: <core> [db_row.c:95]: db_free_row(): freeing row values at 0x7fd17c33f778 Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: <core> [db_res.c:60]: db_free_rows(): freeing rows at 0x7fd17c33fb98 Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: <core> [db_res.c:134]: db_free_result(): freeing result set at 0x7fd17c349800 Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: DEBUG: avpops [avpops_impl.c:415]: ops_dbload_avps(): loaded avps = 1 Feb 24 11:27:51 slb04 /usr/local/sbin/kamailio[21056]: ERROR: <script>: bla01

2 5

Re: [SR-Users] IPV6 kamailio 4.0.2
by Angel Elena 18 Apr '17

18 Apr '17

Ok, thanks Daniel. Tonight, I will activate ipv6 again and review the kamailio process with ps auxw. when I make a /etc/init.d/networking restart , kamailio still working and processing calls without problems (this night I make the test). thanks -------------------------------- Ángel Elena Medina _o) craem(a)craem.net / \\ http://blog.craem.net _(___V @craem_ -------------------------------- -----Mensaje original----- De: Daniel-Constantin Mierla <miconda(a)gmail.com> Enviado: Mar 18-04-2017 14:50 Asunto: Re: [SR-Users] IPV6 kamailio 4.0.2 Para: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>; > Hello, > > > > I think there is some problem and kamailio is not actually running after you > start it so the fifo file is created. > > > > Can you do 'ps auxw | grep kamailio' after you start kamailio with ipv6 and see > if it is running? > > > Cheers, > Daniel > > > On 17.04.17 16:20, Angel Elena wrote: > > > > Hello, good moorning. > > I have a Kamailio 4.0.2 with debian 7.0 and this days I'm configuring dual > stack ipv4 & ipv6 in all servers. > > I have configured ipv6 today in my kamailio server and when I make a > /etc/init.d/networking restart, everything seems to be working fine (ipv6 > works), but when I make a "kamctl mi dlg_list", the next error appears: > > root@sipproxy:/etc/network# kamctl mi dlg_list > ERROR: Error opening Kamailio's FIFO /tmp/kamailio_fifo > ERROR: Make sure you have the line 'modparam("mi_fifo", "fifo_name", > "/tmp/kamailio_fifo")' in your config > ERROR: and also have loaded the mi_fifo module. > > Disable ipv6 and now works fine. > > > restart kamailio service is "complicated" to test anythink. > > Any ideas ? > > thanks > > -------------------------------- > Ángel Elena Medina _o) > craem(a)craem.net / \\ > http://blog.craem.net _(___V > @craem_ > -------------------------------- > > > > > > _______________________________________________ > Kamailio (SER) - Users Mailing List > sr-users(a)lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > > > > > -- > Daniel-Constantin Mierla > www.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio Advanced Training - May 22-24 (USA) - www.asipto.com > Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com > > > > _______________________________________________ > > Kamailio (SER) - Users Mailing List > > sr-users(a)lists.kamailio.org > > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > > >

1 0

IPV6 kamailio 4.0.2
by Angel Elena 18 Apr '17

18 Apr '17

Hello, good moorning. I have a Kamailio 4.0.2 with debian 7.0 and this days I'm configuring dual stack ipv4 & ipv6 in all servers. I have configured ipv6 today in my kamailio server and when I make a /etc/init.d/networking restart, everything seems to be working fine (ipv6 works), but when I make a "kamctl mi dlg_list", the next error appears: root@sipproxy:/etc/network# kamctl mi dlg_list ERROR: Error opening Kamailio's FIFO /tmp/kamailio_fifo ERROR: Make sure you have the line 'modparam("mi_fifo", "fifo_name", "/tmp/kamailio_fifo")' in your config ERROR: and also have loaded the mi_fifo module. Disable ipv6 and now works fine. restart kamailio service is "complicated" to test anythink. Any ideas ? thanks -------------------------------- Ángel Elena Medina _o) craem(a)craem.net / \\ http://blog.craem.net _(___V @craem_ --------------------------------

2 1

too long mysql table key
by Juha Heinanen 15 Apr '17

15 Apr '17

I tried to install kamailio mysql db on Debian Stretch. Create of domain_attrs table failed with this kind of error message: ERROR 1071 (42000) at line 26: Specified key was too long; max key length is 767 bytes domain-create.sql contains this: CREATE TABLE `domain_attrs` ( `id` INT(10) UNSIGNED AUTO_INCREMENT PRIMARY KEY NOT NULL, `did` VARCHAR(64) NOT NULL, `name` VARCHAR(32) NOT NULL, `type` INT UNSIGNED NOT NULL, `value` VARCHAR(255) NOT NULL, `last_modified` DATETIME DEFAULT '2000-01-01 00:00:01' NOT NULL, CONSTRAINT domain_attrs_idx UNIQUE (`did`, `name`, `value`) ); Looks like default charset is something (e.g. utf8), where one char takes more than 1 byte and 767 limit is exceeded. Any suggestions on how to solve this? -- Juha

2 9

kamcli doesn't function
by Marko Tirs 14 Apr '17

14 Apr '17

Hello all, I can't find any answer why my kamcli doesn't function. I'm using Kamailio 5.0.0 at the Debian Jessy 8.7 and it functions well. # kamctl ul show functions well but when I use kamcli I get error: # kamcli ul show 13(7452) ERROR: jsonrpcs [jsonrpcs_sock.c:542]: jsonrpc_dgram_send_data(): failed to send the response - ret: -1, len: 2443 (131072), err: 1 - Operation not permitted) (log): Timeout receiving response on unix sock The relevant parts of kamailio.cfg: #------------------------------------------------------------------------ #!define WITH_DEBUG #!define WITH_NAT #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB loadmodule "jsonrpcs.so" # ----- jsonrpcs params ----- modparam("jsonrpcs", "pretty_format", 1) /* set the path to RPC fifo control file */ modparam("jsonrpcs", "fifo_name", "/var/run/kamailio/kamailio_rpc.fifo") /* set the path to RPC unix socket control file */ modparam("jsonrpcs", "dgram_socket", "/var/run/kamailio/kamailio_rpc.sock") # ----- ctl params ----- modparam("ctl", "binrpc", "unix:/var/run/kamailio/kamailio_ctl") #-------------------------------------------------------------------------- # ll /var/run/kamailio/ total 0 srw------- 1 root root 0 Mar 22 11:36 kamailio_ctl prw-rw---- 1 root root 0 Mar 22 12:30 kamailio_rpc.fifo srw-rw---- 1 root root 0 Mar 22 11:36 kamailio_rpc.sock Can somebody tell me what is the problem? Thank you! Regards Marko

3 9

RFC: kamailio-announce mailing list
by Daniel-Constantin Mierla 14 Apr '17

14 Apr '17

Hello, for a while in the past (like 2008-2011) the kamailio-announce(a)lists.kamailio.org mailing list was used for very sporadic announcements: - https://lists.kamailio.org/cgi-bin/mailman/listinfo/kamailio-announce It was intended to be used to announce only relevant news about the project (releases, major events, etc.), which most of them go also on sr-users, but targeting community members than which prefer to avoid high traffic, which is specific for the usual discussions here. Also, for people in sr-users, can be a place to spot easier the major announcements. Because we migrated back to lists.kamailio.org domain, this list is now presented on the page of mailman index: - https://lists.kamailio.org/cgi-bin/mailman/listinfo I just marked it as 'inactive', but I am wondering if it should be revived somehow (as some people wanted to have a place where to inform about relevant security issues, etc...) or be closed (removed/made private). Even it was not used/promoted for more than 5 years, I noticed that it has over 200 subscribers, therefore it seems to be enough people interested in it. Reply here if you consider it to be useful and eventually give some suggestions for what kind of announcements should be used. Note that there is already business(a)lists.kamailio.org (with larger subscriber base) for business related announcement or discussions. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - May 22-24 (USA) - www.asipto.com Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com

2 1

Using advertised_addres doesn't update the RR header
by Mridul B 13 Apr '17

13 Apr '17

Hi, Using *advertised_address *core parameter in the kamailio script doesn't update the address mentioned in the Record-Route header. We see this problem in the 200 OK message (of the INVITE msg), where the Record-Route header sent by the Kamailio contains socket address. We're using kamailio 4.4.5 (x86_64/linux) 239f3c Can you please tell if this core parameter is effective for changing the RR header ? Thanks Best regards, *MRIDUL*

3 3

How do i build MSRP chat bot?
by Pranathi Venkatayogi 13 Apr '17

13 Apr '17

I would like to place the customer connecting via SIP/MSRP on hold until I find the right destination. What is the best way to do this? One idea is to write a MSRP bot. Does anyone know how to go about this? Other smart ideas? Thanks, Pranathi Venkatayogi System Developer II (520) 745-9447 x4466 www.cyracom.com<http://www.cyracom.com/> Join us: [cid:image001.gif@01D1C9C9.C4E8B6D0] <https://www.facebook.com/pages/CyraCom-LLC/134704783312720> [cid:image002.gif@01D1C9C9.C4E8B6D0] <https://twitter.com/cyracom> [cid:image003.gif@01D1C9C9.C4E8B6D0] <http://www.linkedin.com/company/cyracom> [cid:image004.gif@01D1C9C9.C4E8B6D0] <http://www.cyracom.com/blog/> [cid:image005.png@01D1C9C9.C4E8B6D0] DISCLAIMER: This e-mail and any attached content may contain confidential or privileged material delivered for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender immediately by reply e-mail and delete all copies of this message. It is the recipient's responsibility to scan this e-mail and any attachments for viruses. The content of this e-mail message, including any attachments, does not comprise a contract or a portion of a contract, and so does not bind CyraCom International, Inc. or any of its agents or subsidiaries. CyraCom, LLC and Voiance Language Services, LLC are wholly owned subsidiaries of CyraCom International, Inc.

3 4

Install 5.0 with IMS module on single machine
by Jegadeesan 13 Apr '17

13 Apr '17

Hi , How to install Kamalio 5.0 with IMS module on single machine to support the RCS client development ? -- Jega

2 2

Rtpengine module. rtcp-mux-demux option does not work.
by Denys Pozniak 13 Apr '17

13 Apr '17

Hello, All! We are using Kamailio as Webrtc to SIP proxy. Clinet's Chrome browser needs to have rtcp-mux option to work correct, so we are adding it in RTPENGINE->WS direction as: rtpengine_manage("trust-address replace-origin replace-session-connection *rtcp-mux-offer rtcp-mux-accept* ICE=force RTP/SAVPF"); Also we need to remove it in RTPENGINE->PSTN direction, we are trying to do it like this: rtpengine_manage("trust-address replace-origin replace-session-connection * rtcp-mux-demux* ICE=remove RTP/AVP"); But it does not work for us and a=rtcp-mux option in SDP goes to the SIP provider. Please help us to solve this! BR, Denys PS. Versions: Kamailio 4.4.5, rtpengine 5.2.1.0

2 1

RAW_SOCKS with Kamaili 4.4.5
by Yasin CANER 13 Apr '17

13 Apr '17

3 6

Kamailio 5.0 can't get version of the RTP proxy
by Yebe diomande Keffa 13 Apr '17

13 Apr '17

Hello Getting this issu on Kamaiio 5.0 ( install from GIT): Apr 10 10:47:42 ns3033789 /usr/local/sbin/kamailio[11496]: WARNING: rtpproxy [rtpproxy.c:1366]: rtpp_test(): can't get version of the RTP proxy Apr 10 10:47:42 ns3033789 /usr/local/sbin/kamailio[11488]: WARNING: rtpproxy [rtpproxy.c:1403]: rtpp_test(): support for RTP proxy <udp:127.0.0.1:7722> has been disabled temporarily I done install of RTPproxy with: $ git clone -b master https://github.com/sippy/rtpproxy.git $ git -C rtpproxy submodule update --init --recursive $ cd rtpproxy $ ./configure $ make $ make install $ rtpproxy -l 5.135.177.203 -s udp:localhost:7722 Before i install mysql-server & kamdbctl create (rtpproxy table), it was working fine Someone to advise please! Keffa Y. Diomande Skype : keffadi Tel : +225 02 77 22 22 Office : Abidjan Ciad http://www.alcall.net

3 5

New developer: Mikko Lehto
by Daniel-Constantin Mierla 12 Apr '17

12 Apr '17

Hello, just to let everyone know that I invited Mikko Lehto into the developer group on Kamailio gihub project. He has made a lot of good pull requests over the time, specially to documentation and unit tests that could have been just committed directly without delay on waiting for a review, saving also time from the other developers. Taking time to express my thanks for all his contributions so far and reviving those unit tests, and I am looking forward to future collaboration! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - May 22-24 (USA) - www.asipto.com Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com

3 2

Use mysql view to load data into htable
by Jan Hazenberg 12 Apr '17

12 Apr '17

Hello, I'm trying to load data from a mysql table into a htable using a mysql view. But when i start kamailio i get the following error: ERROR: htable [ht_db.c:345]: ht_db_load_table(): Wrong db type [3] for key_type column Here a example of a view i'm trying to use: CREATE OR REPLACE VIEW `view_blacklist_prefix` AS SELECT prefix AS key_name, '0' AS key_type, '0' AS value_type, '1' AS key_value, '0' AS expires FROM openser.blacklist_prefix GO Should it be possible to use a mysql view as input for a htable? Thanks, Jan Hazenberg

2 2

snmpstats issue
by Igor Potjevlesch 12 Apr '17

12 Apr '17

Hello, On one of my Kamailio server, I don't have data returned by KAMAILIO-MIB::. KAMAILIO-SIP-COMMON-MIB and KAMAILIO-SIP-SERVER-MIB look to work good. Everything is configured as the other Kamailio instances, but there is nothing about current dialog even if the module is loaded into Kamailio and called into kamailio.cfg. Any idea? Here is an output of snmpwalk: snmpwalk -c legosnoc -v 1 <HOST> 1.3.6.1.4.1.34352 KAMAILIO-SIP-COMMON-MIB::kamailioSIPProtocolVersion.0 = STRING: SIP/2.0 KAMAILIO-SIP-COMMON-MIB::kamailioSIPServiceStartTime.0 = Timeticks: (0) 0:00:00.00 KAMAILIO-SIP-COMMON-MIB::kamailioSIPEntityType.0 = BITS: 20 proxyServer(2) KAMAILIO-SIP-COMMON-MIB::kamailioSIPTransportRcv.ipv4."IP_HOST".5060 = BITS: 40 udp(1) KAMAILIO-SIP-COMMON-MIB::kamailioSIPTransportRcv.ipv4."IP_HOST".5060 = BITS: 40 udp(1) KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.1 = STRING: METHOD_INVITE KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.2 = STRING: METHOD_CANCEL KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.3 = STRING: METHOD_ACK KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.4 = STRING: METHOD_BYE KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.5 = STRING: METHOD_INFO KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.6 = STRING: METHOD_OPTIONS KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.7 = STRING: METHOD_UPDATE KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.8 = STRING: METHOD_REGISTER KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.9 = STRING: METHOD_MESSAGE KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.10 = STRING: METHOD_SUBSCRIBE KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.11 = STRING: METHOD_NOTIFY KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.12 = STRING: METHOD_PRACK KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.13 = STRING: METHOD_REFER KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.14 = STRING: METHOD_PUBLISH KAMAILIO-SIP-COMMON-MIB::kamailioSIPSummaryInRequests.0 = Counter32: 2680 KAMAILIO-SIP-COMMON-MIB::kamailioSIPSummaryOutRequests.0 = Counter32: 1050 KAMAILIO-SIP-COMMON-MIB::kamailioSIPSummaryInResponses.0 = Counter32: 3102 KAMAILIO-SIP-COMMON-MIB::kamailioSIPSummaryOutResponses.0 = Counter32: 1630 KAMAILIO-SIP-COMMON-MIB::kamailioSIPSummaryTotalTransactions.0 = Counter32: 1518 KAMAILIO-SIP-COMMON-MIB::kamailioSIPCurrentTransactions.0 = Gauge32: 7 KAMAILIO-SIP-COMMON-MIB::kamailioSIPNumUnsupportedUris.0 = Counter32: 16 KAMAILIO-SIP-COMMON-MIB::kamailioSIPNumUnsupportedMethods.0 = Counter32: 0 KAMAILIO-SIP-COMMON-MIB::kamailioSIPOtherwiseDiscardedMsgs.0 = Counter32: 0 KAMAILIO-SIP-SERVER-MIB::kamailioSIPProxyStatefulness.0 = INTEGER: callStateful(3) KAMAILIO-SIP-SERVER-MIB::kamailioSIPProxyRecordRoute.0 = INTEGER: true(1) KAMAILIO-SIP-SERVER-MIB::kamailioSIPProxyAuthMethod.0 = BITS: 20 digest(2) KAMAILIO-SIP-SERVER-MIB::kamailioSIPNumProxyRequireFailures.0 = Counter32: 0 KAMAILIO-SIP-SERVER-MIB::kamailioSIPRegMaxContactExpiryDuration.0 = Gauge32: 3600 seconds KAMAILIO-SIP-SERVER-MIB::kamailioSIPRegMaxUsers.0 = Gauge32: 4294967295 KAMAILIO-SIP-SERVER-MIB::kamailioSIPRegCurrentUsers.0 = Gauge32: 325416 KAMAILIO-SIP-SERVER-MIB::kamailioSIPRegDfltRegActiveInterval.0 = Gauge32: 3600 seconds KAMAILIO-SIP-SERVER-MIB::kamailioSIPUserUri.1 = STRING: DefaultUser KAMAILIO-SIP-SERVER-MIB::kamailioSIPUserAuthenticationFailures.1 = Counter32: 0 KAMAILIO-SIP-SERVER-MIB::kamailioSIPContactDisplayName.1.1 = STRING: DefaultUser KAMAILIO-SIP-SERVER-MIB::kamailioSIPContactURI.1.1 = STRING: DefaultUser KAMAILIO-SIP-SERVER-MIB::kamailioSIPContactLastUpdated.1.1 = STRING: 0-0-0,0:0:0.0 KAMAILIO-SIP-SERVER-MIB::kamailioSIPContactExpiry.1.1 = STRING: 0-0-0,0:0:0.0 KAMAILIO-SIP-SERVER-MIB::kamailioSIPContactPreference.1.1 = STRING: -0.01 KAMAILIO-SIP-SERVER-MIB::kamailioSIPRegUserLookupCounter.0 = Counter32: 4 KAMAILIO-SIP-SERVER-MIB::kamailioSIPRegAcceptedRegistrations.0 = Counter32: 21 KAMAILIO-SIP-SERVER-MIB::kamailioSIPRegRejectedRegistrations.0 = Counter32: 0 KAMAILIO-MIB::kamailioSrvMaxMemory.0 = Gauge32: 738197504 KAMAILIO-MIB::kamailioSrvFreeMemory.0 = Gauge32: 358262600 KAMAILIO-MIB::kamailioSrvMaxUsed.0 = Gauge32: 380013984 KAMAILIO-MIB::kamailioSrvRealUsed.0 = Gauge32: 379934904 KAMAILIO-MIB::kamailioSrvMemFragments.0 = Gauge32: 70 KAMAILIO-MIB::kamailioSrvCnfFullVersion.0 = STRING: kamailio 4.2.8 (x86_64/linux) 4507b8 KAMAILIO-MIB::kamailioSrvCnfVerName.0 = STRING: kamailio KAMAILIO-MIB::kamailioSrvCnfVerVersion.0 = STRING: 4.2.8 KAMAILIO-MIB::kamailioSrvCnfVerArch.0 = STRING: x86_64 KAMAILIO-MIB::kamailioSrvCnfVerOs.0 = STRING: linux KAMAILIO-MIB::kamailioSrvCnfVerId.0 = STRING: 4507b8 KAMAILIO-MIB::kamailioSrvCnfVerCompTime.0 = STRING: 12:34:45 Feb 17 2017 KAMAILIO-MIB::kamailioSrvCnfVerCompiler.0 = STRING: gcc 4.4.6 KAMAILIO-MIB::kamailioSrvCnfVerFlags.0 = STRING: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES KAMAILIO-MIB::kamailioMsgQueueDepth.0 = Gauge32: 0 KAMAILIO-MIB::kamailioMsgQueueMinorThreshold.0 = INTEGER: -1 KAMAILIO-MIB::kamailioMsgQueueMajorThreshold.0 = INTEGER: -1 KAMAILIO-MIB::kamailioMsgQueueDepthAlarmStatus.0 = BITS: 00 KAMAILIO-MIB::kamailioMsgQueueDepthMinorAlarm.0 = INTEGER: clear(0) KAMAILIO-MIB::kamailioMsgQueueDepthMajorAlarm.0 = INTEGER: clear(0) KAMAILIO-MIB::kamailioCurNumDialogs.0 = Gauge32: 0 KAMAILIO-MIB::kamailioCurNumDialogsInProgress.0 = Gauge32: 0 KAMAILIO-MIB::kamailioCurNumDialogsInSetup.0 = Gauge32: 0 KAMAILIO-MIB::kamailioTotalNumFailedDialogSetups.0 = Counter32: 0 KAMAILIO-MIB::kamailioDialogLimitMinorThreshold.0 = INTEGER: -1 KAMAILIO-MIB::kamailioDialogLimitMajorThreshold.0 = INTEGER: -1 KAMAILIO-MIB::kamailioTotalNumDialogSetups.0 = Counter32: 0 KAMAILIO-MIB::kamailioDialogUsageState.0 = INTEGER: idle(0) KAMAILIO-MIB::kamailioDialogLimitAlarmStatus.0 = BITS: 00 KAMAILIO-MIB::kamailioDialogLimitMinorAlarm.0 = INTEGER: clear(0) KAMAILIO-MIB::kamailioDialogLimitMajorAlarm.0 = INTEGER: clear(0) KAMAILIO-MIB::kamailioNetTcpConnEstablished.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetTcpConnFailed.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetTcpConnReset.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetTcpConnSuccess.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetTcpConnOpen.0 = Gauge32: 0 KAMAILIO-MIB::kamailioNetTcpConnPassiveOpen.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetTcpConnReject.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetTcpEnabled.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetTcpMaxConns.0 = INTEGER: 2048 KAMAILIO-MIB::kamailioNetTcpConnTimeout.0 = INTEGER: 10 KAMAILIO-MIB::kamailioNetTcpSendTimeout.0 = INTEGER: 160 KAMAILIO-MIB::kamailioNetTcpConnLifetime.0 = INTEGER: 1920 KAMAILIO-MIB::kamailioNetTcpNoConnect.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetTcpFdCache.0 = INTEGER: 1920 KAMAILIO-MIB::kamailioNetTcpAsync.0 = INTEGER: true(1) KAMAILIO-MIB::kamailioNetTcpAsyncConnWait.0 = INTEGER: true(1) KAMAILIO-MIB::kamailioNetTcpAsyncConnWqMax.0 = INTEGER: 32768 KAMAILIO-MIB::kamailioNetTcpAsyncWqBlkSize.0 = INTEGER: 10485760 KAMAILIO-MIB::kamailioNetTcpRdBufSize.0 = INTEGER: 16384 KAMAILIO-MIB::kamailioNetTcpDeferAccept.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetTcpDelayedAck.0 = INTEGER: true(1) KAMAILIO-MIB::kamailioNetTcpSynCnt.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetTcpLinger.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetTcpKeepAlive.0 = INTEGER: true(1) KAMAILIO-MIB::kamailioNetTcpKeepIdle.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetTcpKeepIntvl.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetTcpKeepCnt.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetTcpCrlfPing.0 = INTEGER: true(1) KAMAILIO-MIB::kamailioNetTcpAcceptAliases.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetTcpAcceptNoCl.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetWsConnsActive.0 = Gauge32: 0 KAMAILIO-MIB::kamailioNetWsConnsActiveMax.0 = Gauge32: 0 KAMAILIO-MIB::kamailioNetWsConnsFailed.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetWsConnsClosedLocal.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetWsConnsClosedRemote.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetWsFramesRx.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetWsFramesTx.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetWsHandshakeSuccess.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetWsHandshakeFailed.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetConfUdpTransport.0 = INTEGER: true(1) KAMAILIO-MIB::kamailioNetConfUdpDtlsTransport.0 = INTEGER: -1 KAMAILIO-MIB::kamailioNetConfTcpTransport.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetConfTcpTlsTransport.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetConfSctpTransport.0 = INTEGER: true(1) KAMAILIO-MIB::kamailioNetConfSctpTlsTransport.0 = INTEGER: -1 KAMAILIO-MIB::kamailioNetConfWsTransport.0 = INTEGER: -1 KAMAILIO-MIB::kamailioNetConfWsTlsTransport.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetConfHttpServer.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetConfMsrpRelay.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetConfStunServer.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetConfOutbound.0 = INTEGER: 0 Regards, Igor. --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus

2 7

issue with sip path support between asterisk and kamailio
by gerry kernan 12 Apr '17

12 Apr '17

Hi Thanks in advanced if anyone can help me on this. I have kamailio -4.2.3-1.1 running in front of asterisk 13.13.1. I'm using Path support with asterisk so that I can forward Sip requests via kamailio to the asterisk server running on a LAN IP. Kamailio is configured with a WAN and LAN IP. All works well I can register a sip endpoint to the asterisk server via kamailio and make an receive calls, SIP OPTIONs from the asterisk server are received and relayed by kamailio to endpoints. But I'm having issues when a call is hung up asterisk appears to be trying to send the BYE via its own IP address rather that the IP of the LAN interface on the kamailio server. Should I be looking at the issue being on asterisk as it is not sending the BYE via correct IP? Y.Y.Y.Y = WAN IP of client endpoint 192.10.10.216 = LAN IP of asterisk Example of BYE from sip debug on asterisk --- (10 headers 0 lines) --- Really destroying SIP dialog '5d3ae6944a08b42c2078e237141e0e40@192.10.10.216:5060' Method: OPTIONS -- <SIP/1001-00000011> Playing 'digits/17.ulaw' (language 'en') -- Executing [*250@cos-all:8] Wait("SIP/1001-00000011", "1") in new stack -- Executing [*250@cos-all:9] SayUnixTime("SIP/1001-00000011", ",,IMp") in new stack -- <SIP/1001-00000011> Playing 'digits/4.ulaw' (language 'en') -- <SIP/1001-00000011> Playing 'digits/oh.ulaw' (language 'en') -- <SIP/1001-00000011> Playing 'digits/4.ulaw' (language 'en') -- <SIP/1001-00000011> Playing 'digits/p-m.ulaw' (language 'en') -- Executing [*250@cos-all:10] Hangup("SIP/1001-00000011", "") in new stack == Spawn extension (cos-all, *250, 10) exited non-zero on 'SIP/1001-00000011' Scheduling destruction of SIP dialog 'OGRjYzJlYmE5MDhjYTdkMTM1ZTAxNTk2YWYwNDg5MTA.' in 6400 ms (Method: ACK) set_destination: Parsing <sip:1001@Y.Y.Y.Y:16078;transport=UDP> for address/port to send to set_destination: set destination to Y.Y.Y.Y:16078 Reliably Transmitting (no NAT) to Y.Y.Y.Y:16078: BYE sip:1001@Y.Y.Y.Y:16078;transport=UDP SIP/2.0 Via: SIP/2.0/UDP 192.10.10.216:5060;branch=z9hG4bK46ed8549 Max-Forwards: 70 From: <sip:*250@sip.domain.ie;transport=UDP>;tag=as60c5965b To: <sip:1001@sip.domain.ie;transport=UDP>;tag=471c3a31 Call-ID: OGRjYzJlYmE5MDhjYTdkMTM1ZTAxNTk2YWYwNDg5MTA. CSeq: 102 BYE User-Agent: OMBUTEL PBX Proxy-Authorization: Digest username="1001", realm="asterisk", algorithm=MD5, uri="sip:sip.domain.ie", nonce="4aaa41f3", response="136fac72a799f9507a7466b578786110" X-Asterisk-HangupCause: Normal Clearing X-Asterisk-HangupCauseCode: 16 Content-Length: 0 KAMAILIO LAN IP = 192.10.10.202 SIP status of peer on asterisk * Name : 1001 Description : Infinity-Test Secret : <Set> MD5Secret : <Not set> Remote Secret: <Not set> Context : cos-all Record On feature : automon Record Off feature : automon Subscr.Cont. : <Not set> Language : en Tonezone : uk AMA flags : Unknown Transfer mode: open CallingPres : Presentation Allowed, Not Screened Callgroup : Pickupgroup : Named Callgr : Nam. Pickupgr: MOH Suggest : ringback Mailbox : 1001@ombutel-voicemail VM Extension : asterisk LastMsgsSent : 0/0 Call limit : 2147483647 Max forwards : 0 Dynamic : Yes Callerid : "Infinity-Test" <1001> MaxCallBR : 384 kbps Expire : 3228 Insecure : no Force rport : No Symmetric RTP: No ACL : Yes DirectMedACL : No T.38 support : No T.38 EC mode : Unknown T.38 MaxDtgrm: 4294967295 DirectMedia : Yes PromiscRedir : No User=Phone : No Video Support: No Text Support : No Ign SDP ver : No Trust RPID : Yes Send RPID : Yes Path support : Yes Path : <sip:192.10.10.202;lr;received=sip:Y.Y.Y.Y:16078> TrustIDOutbnd: Legacy Subscriptions: Yes Overlap dial : Yes DTMFmode : rfc2833 Timer T1 : 500 Timer B : 32000 ToHost : Addr->IP : 192.168.200.122:5060 Defaddr->IP : (null) Prim.Transp. : UDP Allowed.Trsp : UDP Def. Username: 1001 SIP Options : norefersub replaces replace timer Codecs : (ulaw|alaw|g729) Auto-Framing : No Status : OK (19 ms) Useragent : Zoiper for Windows 2.43 r24984 Reg. Contact : sip:1001@192.168.200.122:5060;rinstance=3798b50d10d60d84;transport=UDP Qualify Freq : 60000 ms Keepalive : 0 ms Sess-Timers : Accept Sess-Refresh : uas Sess-Expires : 1800 secs Min-Sess : 90 secs RTP Engine : asterisk Parkinglot : Use Reason : No 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

2 2

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