- sr-users - kamailio.org

Re: [SR-Users] Question about in call both side redirection
by Андрей Ярин 22 Sep '15

22 Sep '15

sr-users-request(a)lists.sip-router.org пишет: > Hello On 04/09/15 07:57, ?????? ???? wrote: >> >Hello (sorry for my bad english) - i try to create voice record >> >service by request. User A call to user B. In call by pressing >> >combination like *55 Kamailio must redirect both sides to asterisk, >> >whitch create dynamic conference room with recording. As i understand >> >i need to use dlg_refer() from dialog module, but in log file i get: >> >Konsole output >> >Sep 4 10:45:14 voipc-node2 /usr/local/sbin/kamailio[18941]: ERROR: >> >dialog [dlg_req_within.c:85]: build_dlg_t(): no contact available >> >Sep 4 10:45:14 voipc-node2 /usr/local/sbin/kamailio[18941]: ERROR: >> >dialog [dlg_transfer.c:188]: dlg_refer_callee(): failed to create dlg_t >> > >> > >> >In script i try to refer with: >> >dlg_refer("callee","sip:100@10.10.9.209"); >> >dlg_refer("caller","sip:100@10.10.9.209"); >> > > in what context do you use the above actions? In other words, do you > execute them when you process a specific request? If yes, which one? > > Another question, how do you capture when *55 is pressed? Is dtmf sent > via sip info request? > > Cheers, > Daniel > > -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - > http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - > http://www.asipto.com Kamailio Advanced Training, Sep 28-30, 2015, in > Berlin - http://asipto.com/u/kat For now i try to use event_route[dialog:start] - i testing - can kamailio redirect both sides to external service, and will it work with event_route[dispatcher:dst-down]. If it will work, i will add SIP INFO processing for service codes -- Ярин Андрей Инженер ООО "И.С.-Телеком" 8(351)7786878 доб 113 8(351)2555724 доб 113 8(351)2555787 доб 113

2 2

carrierroute module cannot use prefix that start with +
by José Seabra 21 Sep '15

21 Sep '15

Hello there, I'm using carrierroute module to route calls based on prefix, everything was working until i tried use prefixes that start with +, kamailio core doesn't allow me use the + on carrierroute prefix, i get the following message from kamailio logs: INFO: carrierroute [cr_carrier.c:100]: add_domain_data(): adding domain 1 'main' to carrier 1 'carriers'35(17196) DEBUG: carrierroute [cr_carrier.c:101]: add_domain_data(): domain position 0 (domain_num=1, first_empty_domain=0)35(17196) INFO: carrierroute [cr_data.c:414]: get_domain_data_or_add(): added domain 1 'main' to carrier 1 'carriers'35(17196) INFO: carrierroute [cr_data.c:470]: add_route(): found carrier and domain, now adding route 35(17196) ERROR: <core> [dtrie.c:130]: dtrie_insert(): cannot insert non-numerical character 35(17196) ERROR: carrierroute [cr_domain.c:168]: add_route_to_tree(): cannot insert route flags into d-trie anyone can help in order allow use + in carrierroute prefix. Best regards José Seabra

3 4

dispatcher.list reversed by dispatch.c reindex_dests()
by Giovanni Maruzzelli 21 Sep '15

21 Sep '15

Hello, dispatcher gives me destination sets with entries in reverse order: I have installed from Kamailio deb repository packages version 4.3.2+jessie. # kamailio -V version: kamailio 4.3.2 (x86_64/linux) flags: 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, F_MALLOC, DBG_F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 4.9.2 I configured dispatcher: modparam("dispatcher", "use_default", 1) modparam("dispatcher", "list_file", "/etc/kamailio/dispatcher.list") modparam("dispatcher", "flags", 3) modparam("dispatcher", "dst_avp", "$avp(AVP_DST)") modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)") modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)") modparam("dispatcher", "sock_avp", "$avp(AVP_SOCK)") modparam("dispatcher", "ds_ping_interval", 5) modparam("dispatcher", "ds_probing_mode", 1) I have this dispatcher.list: 1 sip:192.168.1.144:5060 2 1 sip:192.168.1.145:5060 2 1 sip:192.168.1.146:5060 2 2 sip:192.168.1.146:5060 2 2 sip:192.168.1.145:5060 2 So, I expect dispatcher to have: set 1 first two destinations in distribution via hash on callid, and third destination as failover (192.168.1.146 <http://192.168.1.146:5060>) . set 2 all traffic on first destination, and if first fails, all traffic will failover to second destination (192.168.1.145 <http://192.168.1.146:5060>). Instead reindex_dests shuffle the sets upside down: DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/1] <sip: 192.168.1.144:5060> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/2] <sip: 192.168.1.145:5060> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/3] <sip: 192.168.1.146:5060> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [2/1] <sip: 192.168.1.146:5060> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [2/2] <sip: 192.168.1.145:5060> DEBUG: dispatcher [dispatch.c:494]: reindex_dests(): found [2] dest sets DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 2 sip: 192.168.1.145:5060 2 0 (,0,0) DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 2 sip: 192.168.1.146:5060 2 0 (,0,0) DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1 sip: 192.168.1.146:5060 2 0 (,0,0) DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1 sip: 192.168.1.145:5060 2 0 (,0,0) DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1 sip: 192.168.1.144:5060 2 0 (,0,0) DEBUG: dispatcher [dispatcher.c:347]: mod_init(): loaded dispatching list So, Kamailio give me set 1 and set 2 as per post-reindex_dests, and failover is 192.168.1.144 for set 1, and 192.168.1.146 for set 2. Is this the expected behavior? Am I doing something wrong in configuration? Thank you all in advance, -giovanni Sincerely, Giovanni Maruzzelli Cell : +39-347-2665618

2 3

Compiling Kamailio for Cubie/RaspberryPi/others ARM arch from main repos
by nadie 21 Sep '15

21 Sep '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 #!/bin/bash # Compiling Kamailio for Cubie/RaspberryPi/others ARM arch from main repos: echo 'deb-src http://deb.kamailio.org/kamailio43 jessie main' > /etc/apt/sources.list.d/kamailio.list wget -O- http://deb.kamailio.org/kamailiodebkey.gpg | sudo apt-key add - dpkg --add-architecture i386 apt-get update apt-get install bison debhelper erlang-dev gcj-jdk libconfuse-dev libdb-dev libev-dev libfreeradius-client-dev libgeoip-dev libhiredis-dev libjansson-dev libjson-c-dev liblua5.1-0-dev libmemcached-dev libmono-2.0-dev libmysqlclient-dev libperl-dev libpq-dev libpurple-dev librabbitmq-dev libreadline-dev libsasl2-dev libsctp-dev libsnmp-dev libsqlite3-dev libunistring-dev libval-dev libxml2-dev python-dev unixodbc-dev uuid-dev adduser python libc6 libncurses5 libpcre3 libreadline6 libtinfo5 snmpd mkdir kamailio && cd kamailio/ apt-get -b source kamailio dpkg --remove-architecture i386 rm /etc/apt/sources.list.d/kamailio.list apt-get update dpkg -i *.deb cd .. && rm -rf kamailio/ # end :-) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJV+BKUAAoJEG5DH1ilMeeenM8P/jqzMKtxmRheDDT4pqxzo9W1 lSNpg+UhYr5CC/IXCgGXkP5Sup87/qiAVYz/u902pS9hdIBfdbup2PUsvTX4QK+1 Dybxli9ym4Fup9m6MuB+VLIjkiOOwtGnvChbnPgjJnMxDjzBbDFEmositlfAeiFU XcyIfjYDndvd2+0a1UkTVVuGBEbY6BdVkANvINy2BkZUkolstTgVr7jirYUSTEsa U9M+lX98Dbau5gfvyx87a6CkcW8fyKCgZGBYqjBIyr1TrPgtGcXdcgC77iD2pziW wkU9DIRX0sOaIiAb76hX64SL8U9b+dJr2t17PXjiEEcVWuc7YtV2R0YURAfquw9O ycSh+PWFJgc1PZx5dFZlWceDXjdffnPiWt3Fys3HuVNWLY6iVfOSFv7sMcJ4NyaT N+u81Dr4T9blZ2yRmibRUzlmSlcq4at2yKE19/AsejphXI7mnaARuNlHZUq+4RY9 EF4zlr5zTHmPhvLoh7rjzqWGLmun4g7a7mCnbMDUKKbndqb24QKhO9czvkTvYLGR vbAK56kM96jh3OBLenjl58YzK4qBbJ5sM+UCw6DA5HnF+/jh+oK4zeKL28yqEaG0 SxS/xuG4xxi2wPvGJ36Rg6gIB5cHAxizGLMEPGUPTKCPhKLFIbtunabNu2gj+6nh bpe/fyLw0ZKHF8R4tifU =Ty41 -----END PGP SIGNATURE-----

2 2

Kamailio ACK retransmission
by Yasin CANER 21 Sep '15

21 Sep '15

1 0

Kamailio - Asterisk ACK retransmission problem
by Yasin CANER 21 Sep '15

21 Sep '15

1 0

Kamailio presence shared DB_text
by Ewgeny 21 Sep '15

21 Sep '15

Hi list! We use Kamailio 4.2 for presence BLF with DB_TEXT. And i want to make cluster with a few Kamailio's presences, to load balance. Can you please tell me - is that possible to use same shared DB_TEXT database with 2 or more Kamailio servers ? modparam("presence", "subs_db_mode", 3) modparam ("presence","dburl","/tmp/share/dbtext") 1-st server will handle SUBSCRIBE's and this Subscribe's should be accessible also from 2-nd server. Then PUBLISH'es will be sent to both servers in round robin algorithm. Will Kamailio's work with one shared DB or - i'll got some errors ? Maybe i'm wrong somewhere ? Thanks in advance. Kind regards Ewgeny

2 3

Proxy-Require: privacy error
by Chad 21 Sep '15

21 Sep '15

When a call comes in with a SIP header: "Proxy-Require: privacy" line kamailio throws this error: Aug 21 14:27:57 load1 /usr/sbin/kamailio[29447]: ERROR: <core> [parser/hf.c:224]: dump_hdr_field(): DEBUG: dump_hdr_field: type=18, name=Proxy-Require, body=privacy, parsed=(nil), next=0x7efc42f15150 Aug 21 14:27:57 load1 /usr/sbin/kamailio[29446]: ERROR: <core> [parser/hf.c:224]: dump_hdr_field(): DEBUG: dump_hdr_field: type=18, name=Proxy-Require, body=privacy, parsed=(nil), next=0x7efc42f0a7b0 Aug 21 14:27:58 load1 /usr/sbin/kamailio[29447]: ERROR: <core> [parser/hf.c:224]: dump_hdr_field(): DEBUG: dump_hdr_field: type=18, name=Proxy-Require, body=privacy, parsed=(nil), next=0x7efc42f13180 Aug 21 14:27:58 load1 /usr/sbin/kamailio[29446]: ERROR: <core> [parser/hf.c:224]: dump_hdr_field(): DEBUG: dump_hdr_field: type=18, name=Proxy-Require, body=privacy, parsed=(nil), next=0x7efc42f0dfb8 Anyone know why that happens or how to fix it? -- ^C Chad

2 5

Fw: Re: Busy Tone.. Call not coming
by Mr ankush 19 Sep '15

19 Sep '15

1 0

Dialog module isn't decreasing the profile size, and isn't entering on event routes
by José Seabra 18 Sep '15

18 Sep '15

Hi there, I'm using a dialog module in a small kamailio script that only does routing based on prefix, and relay the invite from one ipaddr to another ip addr (diferent interfaces) using $fs variavel. Now i was introducing the dialog module to limit the number of concurrent calls, and i noticed that it only can increasing the number of dialogs, and it isn't decreasing when receives the "BYE", I also noticed that when kamailio receives "BYE" the dialog event route for state "end" is not executed. To count the number of concurrent calls I'm using the following logic in main route: if (is_method("INVITE")) { setflag(FLT_ACC); # do accounting dlg_manage(); if(get_profile_size("concurrentcalls","local","$avp(s:size)")) { if($avp(s:size) != $null) { xlog("L_INFO", "Number of calls for this server : $avp(s:size) - ID=$ci\n"); if($avp(s:size) >= 15000) { xlog("L_INFO", "Concurrent_max calls exceeded $avp(s:size) for caller '$fU' - R=$ru ID=$ci\n"); sl_send_reply("503", "Channel limit exceeded\n"); exit; } } } set_dlg_profile("concurrentcalls","local"); } Please check out the attachment with logs. Best Regards -- José Seabra

2 5

Issue with too many "listen" statements
by Sven Neuhaus 18 Sep '15

18 Sep '15

Hi, we've observed a bug with Kamailio (we are using 4.3.1): When using more than 81 "listen" statements, Kamailio starts acting up. In our case, it handles ACK packets (that follow "200 OK" messages) incorrectly: It forwards them to itself (src ip == dst ip) in a garbled form (on the loopback interface). We need more than 80 "listen" statements at the moment so I hope there's a way to increase the limit substantially. The number of file handles has been set to 32000 btw. Regards, -Sven Neuhaus

2 6

Adding user to kamailio database
by Priyaranjan Nayak 17 Sep '15

17 Sep '15

Hi All, I wanted to use kamailio with authorization. How can I add public identity and private identity to kamailio database for a user ? Thanks Priyaranjan

2 1

Hex to Dec conversion
by Yufei Tao 17 Sep '15

17 Sep '15

Hi Daniel, I've tested the patch on top of v4.2.5 and it works. Thank you very much! Yufei

1 0

Re: [SR-Users] Hex to Dec conversion
by Yufei Tao 17 Sep '15

17 Sep '15

Hi, Thanks for the replies! The first thing I looked at was the encode/decode.hexa transformations but it only transforms between ASCII characters and Hex numbers. Then I used exec_avp to call a bash command (for example, 'echo $((0x123))' gives you 291) which works. But calling something external may not be optimal I thought? I found OpenSIPS has hex2dec and dec2hex transformations and wonder if we could have these in Kamailio as well? Cheers, Yufei

2 1

Authentication issue during registration
by Austin Einter 17 Sep '15

17 Sep '15

Hi All I have a typical requirement, where I have a forwarding SBC between an endpoint and kamailio as shown below. Endpoint ----> SBC ------> Kamailio >From endpoint I am sending REGISTER request. It reaches SBC. SBC sends the REGISTER request to Kamailio, Kamailio challenges it (401), and challenge response is received at endpoint through SBC. Next endpoint adds authorization header and sends REGISTER to SBC, SBC forwards it to Kamailio. Now Kamailio again responds with 401. When we analysed Kamailio logs, we can see Kamailio log authorization response token and response token that was sent by Endpoint are same. So my question is, why Kamailio sends 401 repeatedly even if it received proper Authorization header. Is it because Kamailio received REGISTER from IP address different from endpoint. Please guide, how can I avoid this issue. Thanks Austin

3 4

add to wishlist: htable.dump type of value
by Juha Heinanen 16 Sep '15

16 Sep '15

looks like htable.dump does not tell what is the type of the value, e.g. { entry: 53 size: 1 slot: { item: { name: foo::bar value: 0 } } } -- juha

2 7

Next IRC Devel Meeting - Sep 16, 2015
by Daniel-Constantin Mierla 16 Sep '15

16 Sep '15

Hello, I would like to propose organizing the next IRC devel meeting to sync on the plans for Kamailio short term evolution. A wiki page has been created to keep track of what should be discussed there. Feel free to add your suggestions there: * http://www.kamailio.org/wiki/devel/irc-meetings/2015b First proposed date is next week on Wednesday, September 16, at 14:00 UTC (15:00 London, 16:00 Berlin, ...). The date can be changed based on availability of people willing to attend -- add your preferred date and time there. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat

1 2

OT: IIT RTC Conference discount
by Daniel-Constantin Mierla 16 Sep '15

16 Sep '15

Hello, I have some discount code for IIT RTC Conference & Expo, taking place in Chicago, IL, USA, during October 6-8, 2015. It gives an 100USD discount, which can save a bit or make some of the available tickets completely free (like Expo Plus admission). Should someone be interested, contact me directly via email. More details about the event can be found at: * http://www.rtc-conference.com/ I will be at the event during Oct 7 and 8, presenting on the morning of Oct 8, if anyone here coming to the event or happening to be in Chicago area and want to meet and chat about Kamailio, drop me an email as well. Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com

1 0

assign_hf_value, hf_value_exists and exclude_hf_value broken in 4.3.2?
by Björn Bylander 15 Sep '15

15 Sep '15

Hello, 4.3.1 works well for us apart from the issue fixed by 93b297e16134b0e74cf83e3604da01355a52e700. Since 93b297e16134b0e74cf83e3604da01355a52e700 is included in 4.3.2 I tried upgrading one of our servers and now Kamailio won't even start as it apparently finds the way assign_hf_value, hf_value_exists and exclude_hf_value are used in our configuration to be incorrect. I enabled debug logging (WITH_DEBUG) and found the following: > 0(1894) DEBUG: <core> [route.c:872]: fix_actions(): fixing assign_hf_value() > 0(1894) ERROR: textopsx [textopsx.c:596]: fixup_hname_param(): ERROR: textops: cannot parse header near 'Privacy' > 0(1894) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:642 > 0(1894) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:644 > 0(1894) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:661 > ERROR: error -6 while trying to fix configuration Line 642 looks like this: assign_hf_value("Privacy", "id") Commenting it out leads to the following output: > 0(2217) DEBUG: <core> [route.c:872]: fix_actions(): fixing hf_value_exists() > 0(2217) ERROR: textopsx [textopsx.c:596]: fixup_hname_param(): ERROR: textops: cannot parse header near 'Privacy' > 0(2217) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:1016 > 0(2217) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:1019 > 0(2217) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:1023 > ERROR: error -6 while trying to fix configuration Line 1016 looks like this: if (hf_value_exists("Privacy", "none")) { Commenting it out leads to the following output: > 0(2292) DEBUG: <core> [route.c:872]: fix_actions(): fixing exclude_hf_value() > 0(2292) ERROR: textopsx [textopsx.c:596]: fixup_hname_param(): ERROR: textops: cannot parse header near 'Accept' > 0(2292) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:1020 > 0(2292) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:1023 > ERROR: error -6 while trying to fix configuration Lines 1020 and 1021 look like this exclude_hf_value("Accept", "application/media_control+xml"); exclude_hf_value("Accept", "application/x-broadworks-call-center+xml"); Commenting them out makes Kamailio start without complaining. Btw, "kamailio -c" thinks the configuration file is fine. So, is our use of assign_hf_value, hf_value_exists and exclude_hf_value incorrect (looking at the textopsx documentation I can't see how) or was a bug introduced with 4.3.2 which causes this behaviour? Regards, Björn Bylander

2 1

Kamailio challenges repeatedly
by Austin Einter 15 Sep '15

15 Sep '15

I am trying to register with Kamailio server from my custom endpoint. I have below call flows Register -> 401 Register -> 401 When I saw Kamailio log, I do not see any error. Looks auth response is fine. Then why 401 repeatedly. Log is given blow. Please guide to fix this issue. Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: auth_db [authorize.c:208]: get_ha1(): HA1 string calculated: 8749f9da135d71526725a337008df1d5 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: auth [api.c:211]: auth_check_response(): check_response: Our result = '4aa70d676021329550b3d17e17238fac' Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: auth [api.c:218]: auth_check_response(): check_response: Authorization is OK Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:81]: db_free_columns(): freeing 1 columns Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:85]: db_free_columns(): freeing RES_NAMES[0] at 0x7f8a24d5e1d0 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:94]: db_free_columns(): freeing result names at 0x7f8a24d7ceb0 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:99]: db_free_columns(): freeing result types at 0x7f8a24d7cef0 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:54]: db_free_rows(): freeing 1 rows Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_row.c:97]: db_free_row(): freeing row values at 0x7f8a24d5e260 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:62]: db_free_rows(): freeing rows at 0x7f8a24d5e218 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:136]: db_free_result(): freeing result set at 0x7f8a24d7ce18 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: auth [challenge.c:127]: get_challenge_hf(): build_challenge_hf: realm='10.10.64.125' Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: auth [challenge.c:269]: get_challenge_hf(): auth: 'WWW-Authenticate: Digest realm="10.10.64.125", nonce="VfbImFX2x2yEeE8kEuL2IXqW2TgKu+eC"#015#012' Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: sl [sl.c:296]: send_reply(): reply in stateless mode (sl) Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [msg_translator.c:206]: check_via_address(): check_via_address(10.3.2.18, 10.3.2.18, 0) Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [tcp_main.c:2283]: tcpconn_send_put(): tcp_send: send from reader (2650 (9)), reusing fd Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [tcp_main.c:2518]: tcpconn_do_send(): tcp_send: sending... Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [tcp_main.c:2552]: tcpconn_do_send(): tcp_send: after real write: c= 0x7f8a1c5dbe78 n=445 fd=9 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [tcp_main.c:2553]: tcpconn_do_send(): tcp_send: buf=#012SIP/2.0 401 Unauthorized#015#012Via: SIP/2.0/TCP 10.3.2.18:6970;branch=z9hG4bK1875333638#015#012From: < sip:262099922700000@10.10.64.125;user=phone>;tag=209355482#015#012To: < sip:+499922700000@10.10.64.125;user=phone>;tag=8345fd11d20ec1ca026994bf51313cb0.a2c6#015#012Call-ID: 1340939517(a)10.10.64.125#015#012CSeq: 3 REGISTER#015#012WWW-Authenticate: Digest realm="10.10.64.125", nonce="VfbImFX2x2yEeE8kEuL2IXqW2TgKu+eC"#015#012Server: kamailio (4.2.5 (x86_64/linux))#015#012Content-Length: 0#015#012#015#012 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) Sep 14 18:41:08 necs107 kamailio[2650]: message repeated 5 times: [ DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)]

2 1

Hex to Dec conversion
by Yufei Tao 14 Sep '15

14 Sep '15

Hi, I want to convert a Hex number string into a Dec number string, e.g. Hex number "123" into Dec number "291". What is the best way? I didn't find any transformation for this. Thank you! Yufei

5 4

Very high load average after upgrade to Kamailio v4.3.2
by M S 14 Sep '15

14 Sep '15

Hi, Over last weekend i upgraded one of my test servers from Kamailio v4.3.1-4d1b65 to latest stable release v4.3.2-07690f and now kamailio goes crazy even with single call (I am using same db and configuration of course). As soon as call establishes system load average (as seen in top command) starts increasing and soon it increases beyond 6.0 and system becomes completely unresponsive, sip messages are no longer being processed by kamailio service. Even after call hangup, system remains under high load. The "htop" indicates that IO Wait time has increased substantially. Any idea what is causing this? For now i have reverted by to v4.3.1-4d1b65 but can go to v4.3.2-07690f again if you need further info or testing. Thank you.

2 6

Concurrent calls after forked invite
by Lukas Hauser 14 Sep '15

14 Sep '15

Hello, I have two UACs registered to kamailio v4.0.4 with the same URI. (bob(a)example.com) Then a third registered UAC (alice(a)example.com) sends an invite to bob(a)example.com. Both bob UACs accept the call and respond with a 200 Ok. The statefull proxy now takes the first one and cancels the second one. In my case I need both responses to be send back to alice through the proxy. I want the Invite to be forked in parallel (works) and both calls to get connected concurrently (does not work). Is there such a feature in the statefull proxy? Can this be done using a stateless proxy? I stumbled on some proposal about a "New Dialog Module Design" [1]. This is excetly what I'm looking for. Is this still just a proposal? Thanks! Lukas PS: I also posted this question in stackoverflow [2] [1] http://www.kamailio.org/dokuwiki/doku.php/modules-new-design:dialog-module-… [2] http://stackoverflow.com/questions/32519551/kamailio-concurrent-calls-after…

2 1

ha1 password authentication without plain text password
by Nabeel 14 Sep '15

14 Sep '15

Hi, My SIP client only uses the 'ha1' password column from the database to authenticate users. It does not require the 'password' column. However, I am not able to register without having the plain text password present in the 'password' column in the database. I need to change this behaviour so that user registration will occur using only the ha1 encoded password column. How can I make this change? I tried commenting out and changing the 'password_column' attribute in the config but could not get it to work.

2 1

selecting memory manager at startup
by Daniel-Constantin Mierla 14 Sep '15

14 Sep '15

Hello, (cross-posting as it is relevant to user community as well). I just pushed a bunch of patches to master branch that will allow selecting the memory manger at kamailio startup, no longer needed to re-compile sources. There are two new command line parameters: * -x name: select the memory manager for shm * -X name: select the memory manager for pkg * if -x is provided but -X is not provided, then pkg uses same memory manager as shm * name can be: * fm - fast malloc (f_malloc) * qm - quick malloc (q_malloc) * default memory manager is fm (what was default so far) Both f_malloc and q_malloc are now compiled, selecting one or the other being possible. Other managers expected to be added in the list soon, especially TLSF, added not that long ago by Camille Oudot. Maybe reviving Doug Lea malloc (existing in dl_malloc.c) worth a try now that can be easily used. The debugging mode for each memory manager is controlled by DB_SR_MEMORY define via Makefile.defs -- right now it is enabled. All enabled memory mangers must be compiled either with or without DB_SR_MEMORY (it won't work to have one memory manger with DB_SR_MEMORY and another one without). Using system malloc for private (pkg) memory is possible by removing the define of PKG_MALLOC from Makefile.defs (same as it was before). This is a mode suitable for troubleshooting using external tools such as valgrind, because it does inline replacement of pkg_malloc() with malloc(), so those tools can track the place of allocation. I plan to add a system malloc custom manager, to allow selecting it with -X (system malloc won't work for shm management, because it is only for private memory). There is no performance impact at runtime, it is only the startup procedure that replaces the pointers to memory management functions. Hopefully with the new mechanism will be able to track easier memory issues -- e.g., qm malloc is better for troubleshooting, using it no longer requires recompilation, just starting kamailio with -x qm. Feedback, especially testing, will be very appreciated! Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat

1 0

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