sr-dev November 2013

sr-dev@lists.kamailio.org

29 participants
220 discussions

[tracker] Comment added: location not updated correctly when using GRUUs (Attachment added)

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#368 - location not updated correctly when using GRUUs User who did this - Hugh Waite (hugh.waite) ---------- I believe the attached patch fixes this issue. The change to usrloc will update the contact in the DB when performing an UPDATE. The change to registrar checks if there is an instance value and will invalidate all stored contacts with that instance if the call-id has changed - in accordance with RFC5627. I can commit this to master and branch 4.1 (ready for 4.1.0) if no-one has any comments. ---------- One or more files have been attached. More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=368#comment1169 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

11 years

git:tmp/ims_usrloc_pcscf_db_support: modules/ims_usrloc_pcscf: initial support for DB storage

by Jason Penton

Module: sip-router Branch: tmp/ims_usrloc_pcscf_db_support Commit: 26bfeae4c0f4aef1eb4fcd330c19351ae30e7958 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=26bfeae… Author: Jason Penton <jason.penton(a)gmail.com> Committer: Jason Penton <jason.penton(a)gmail.com> Date: Wed Nov 20 16:55:55 2013 +0200 modules/ims_usrloc_pcscf: initial support for DB storage --- modules/ims_usrloc_pcscf/pcontact.c | 10 +- modules/ims_usrloc_pcscf/udomain.c | 37 ++++ modules/ims_usrloc_pcscf/ul_mod.c | 72 +++++++- modules/ims_usrloc_pcscf/usrloc.h | 6 +- modules/ims_usrloc_pcscf/usrloc_db.c | 333 ++++++++++++++++++++++++++++++++++ modules/ims_usrloc_pcscf/usrloc_db.h | 79 ++++++++ 6 files changed, 533 insertions(+), 4 deletions(-) Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=26b…

11 years

git:tmp/ims_usrloc_pcscf_db_support: modules/sca: fix hash entry deletion

by Jason Penton

Module: sip-router Branch: tmp/ims_usrloc_pcscf_db_support Commit: 56e4f4518028e73f9ebd053242a100a5c3b7eb53 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=56e4f45… Author: Timo Teräs <timo.teras(a)iki.fi> Committer: Timo Teräs <timo.teras(a)iki.fi> Date: Fri Nov 15 16:06:25 2013 +0200 modules/sca: fix hash entry deletion sca_hash_table_slot_kv_delete_unsafe() uses internally sca_hash_entry but incorrectly called sca_hash_table_slot_kv_find_unsafe() to initialize the entry. That function returns the node value, not the node itself. Use instead sca_hash_table_slot_kv_find_entry_unsafe(). Should fix the crash in FS#366. --- modules/sca/sca_hash.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/modules/sca/sca_hash.c b/modules/sca/sca_hash.c index 996acd9..a92b6c4 100644 --- a/modules/sca/sca_hash.c +++ b/modules/sca/sca_hash.c @@ -264,7 +264,7 @@ sca_hash_table_slot_kv_delete_unsafe( sca_hash_slot *slot, str *key ) { sca_hash_entry *e; - e = sca_hash_table_slot_kv_find_unsafe( slot, key ); + e = sca_hash_table_slot_kv_find_entry_unsafe( slot, key ); if ( e == NULL ) { return( -1 ); }

11 years

[tracker] Comment added: Crash in TCP Read on Kamailio 4.0.1 (Attachment added)

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#364 - Crash in TCP Read on Kamailio 4.0.1 User who did this - Vitaliy Aleksandrov (Vitaliy) ---------- I have one setup which crashed two time during the last week. It crashed when tried to accept TLS connection, but bt looks similar to the one in this report. Details: - Kamailio works as a gateway between WSS and TCP transports. - System version is 4.1.0-dev9 (x86_64/linux) 576dce-dirty. Compressed core file is in the attachment. Backtrace: (gdb) bt #0 qm_detach_free (frag=0x7ffb9f211040, qm=<optimized out>) at mem/q_malloc.c:269 #1 qm_malloc (qm=0x7ffb9e88e000, size=144) at mem/q_malloc.c:386 #2 0x00007ffba734cb02 in shm_malloc (size=136) at ../../mem/shm_mem.h:262 #3 ser_malloc (size=<optimized out>) at tls_init.c:285 #4 0x00007ffba88b15c4 in CRYPTO_malloc () from /usr/local/lib/libcrypto.so.1.0.0 #5 0x00007ffba70fd3dd in tls1_setup_key_block () from /usr/local/lib/libssl.so.1.0.0 #6 0x00007ffba70f4b64 in ssl3_do_change_cipher_spec () from /usr/local/lib/libssl.so.1.0.0 #7 0x00007ffba70f5771 in ssl3_read_bytes () from /usr/local/lib/libssl.so.1.0.0 #8 0x00007ffba70f6ac8 in ssl3_get_message () from /usr/local/lib/libssl.so.1.0.0 #9 0x00007ffba70e8d37 in ssl3_get_cert_verify () from /usr/local/lib/libssl.so.1.0.0 #10 0x00007ffba70ea4b0 in ssl3_accept () from /usr/local/lib/libssl.so.1.0.0 #11 0x00007ffba735ad4a in tls_accept (c=0x7ffb9f03cae0, error=0x7fffce0682d0) at tls_server.c:350 #12 0x00007ffba736039b in tls_read_f (c=0x7ffb9f03cae0, flags=<optimized out>) at tls_server.c:1033 #13 0x000000000055e8b3 in tcp_read_headers (c=0x7ffb9f03cae0, read_flags=<optimized out>) at tcp_read.c:428 #14 0x000000000055f37d in tcp_read_req (con=0x7ffb9f03cae0, bytes_read=0x7fffce088540, read_flags=0x7fffce088560) at tcp_read.c:1269 #15 0x0000000000560b3c in handle_io (fm=<optimized out>, events=<optimized out>, idx=-1) at tcp_read.c:1617 #16 0x0000000000563c74 in io_wait_loop_epoll (repeat=<optimized out>, h=<optimized out>, t=<optimized out>) at io_wait.h:1092 #17 tcp_receive_loop (unix_sock=<optimized out>) at tcp_read.c:1728 #18 0x000000000055ac5c in tcp_init_children () at tcp_main.c:4959 #19 0x0000000000485885 in main_loop () at main.c:1702 #20 0x000000000041cab0 in main (argc=<optimized out>, argv=<optimized out>) at main.c:2533 Frame0: (gdb) p *((char*)frag + sizeof(struct qm_frag)) $7 = 77 'M' (gdb) frame #0 qm_detach_free (frag=0x7ffb9f211040, qm=<optimized out>) at mem/q_malloc.c:269 269 FRAG_END(next)->prev_free=prev; (gdb) p frag->u.nxt_free $8 = (struct qm_frag *) 0x0 ---------- One or more files have been attached. More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=364#comment1168 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

11 years

[tracker] Task closed: SCA Crashes on sca_appearance_unregister ()

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#366 - SCA Crashes on sca_appearance_unregister () User who did this - Andrew Mortensen (admorten) Reason for closing: Fixed More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=366 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

11 years

[tracker] User took ownership: SCA Crashes on sca_appearance_unregister ()

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. Andrew Mortensen has taken ownership of the following task: FS#366 - SCA Crashes on sca_appearance_unregister () More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=366 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

11 years

[tracker] Comment added: SCA Crashes on sca_appearance_unregister ()

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#366 - SCA Crashes on sca_appearance_unregister () User who did this - Andrew Mortensen (admorten) ---------- Bug found by Timo Tëras. sca_hash_table_slot_kv_delete_unsafe was incorrectly calling sca_hash_table_slot_kv_find_unsafe instead of sca_hash_table_slot_kv_find_entry_unsafe. Fix committed to master, backported to 4.0 and 4.1 branches. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=366#comment1167 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

11 years

[tracker] Comment added: Out of memory when a request is sent to itself

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#372 - Out of memory when a request is sent to itself User who did this - Alekzander Spiridonov (alekz) ---------- 1. surprisingly out of pkg_memory. 2. kamctl shows no significant amount of transactions in use. ---------- More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=372#comment1166 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

11 years

[tracker] Comment added: Out of memory when a request is sent to itself

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#372 - Out of memory when a request is sent to itself User who did this - Daniel-Constantin Mierla (miconda) ---------- Which is out of memory, pkg or shm? If it is shm, can you give here the output for: kamctl mi get_statistics all The reason can be fragmentation. 3.1.x is rather old, recent versions have the option mem_join to avoid such issue. Newer version have also the option to print the usage statistics for pkg. ---------- More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=372#comment1165 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

11 years

[tracker] Task opened: Out of memory when a request is sent to itself

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Konstantin (Konstantin) Attached to Project - sip-router Summary - Out of memory when a request is sent to itself Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - Linux Severity - High Priority - Normal Reported Version - 3.1 Due in Version - Undecided Due Date - Undecided Details - Recently we found that if any request is looped back until Max-Forwards (70) is reached, all package memory will be taken. For example, in our case it was a PING request (request URI host part = that server address). For the such requests we used the following processing in the configuration script: record_route(); t_relay(); We are using kamailio 3.1.5 and start 50 child processes. Parameter -m is equal to 2048. We gave load about 100 requests per seconds and we causes out of memory after 15-20 minutes. Actually we expected that the kamailio will free memory for the messages after some time. However it looks like the memory was not released. More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=372 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

11 years

← Newer
1
...
6
7
8
9
10
11
12
...
22
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev November 2013