sr-users December 2014

sr-users@lists.kamailio.org

84 participants
123 discussions

Kamailio Truncating timestamp of sip message?

by Heenan, Timothy Steven

Greetings, I've recently run into a rather strange issue where, in response to an INVITE sent by Kamailio, I'm receiving a 183 Session Progress and SIP 200 OK response about .000050 seconds apart (.05 miliseconds) . Kamailio is choosing to forward the SIP 200 OK ahead of the 183, as if they had arrived at the same time and is prioritizing the 200. Is there a truncate limit on timestamp values? Is this possibly adjustable? Thank you in advance, -Tim ---------------------------------------------------------------------- This email message and any attachments are for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message and any attachments.

9 years, 11 months

RFC: infrastructure upgrade - git, tracker, ...

by Daniel-Constantin Mierla

Hello, as most of you know, we have a rather distributed infrastructure, with servers provided from different companies or persons. We came to the time when one of the servers is too old and considered to be decommisioned, so we have to decide how to move on. It is about sip-router.org, who was offered/sponsored by courtesy of Jan Janak. From project point of view, the server hosts: - git repository - bug tracker - website and wiki under domain sip-router.org Given that no matter what we like, there is work to do, I am looking to see what are the best options out there for everyone involved in the project. The sip-router.or wbesite and wiki, which are not really updated anyhow, will be relocated as virtual host in kamailio.org server and made static for historic purposes. For git and tracker, I thought of two variants: 1) move to use an external hosting service - the first candidate and perhaps the only to be considered is GitHub, we have there already a real time mirror of git repository. Then we should get a read only mirror to kamailio.org. If the tracker on github is good enough for everyone, then we will use it. I could see quickly that lot of kamailio developers already have an account on github. 2) get a new server and relocate those components there. It will need to be configured from scratch and the components eventually updated to use latest versions. In case of tracker, we have eventually to re-evaluate if flyspray worth keeping, as we had several discussions, due to the fact that the project doesn't seem to be very active. My personal preference at this moment is 1), given that offloads administration works from project. For 2) we will need someone to commit to a sysadmin job for long time. As probably you noticed lately, serious security vulnerabilities can appear and someone needs to take care of proper maintenance of the server. I don't want to get all services on kamailio.org, as it has other critical components (mailing lists, releases, website, ...) and messing it or overloading doesn't make sense. There is no real pressure to come to a decision, we can still rely on the server for a while, but I would rather not postpone it for long. While users are encouraged to give their opinion, I feel that existing developers should have the main role in decision, being something that impacts them directly. Your preference? Any other opinions? Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Nov 24-27, Berlin - http://www.asipto.com

9 years, 11 months

Kamailio Crash when modifying username of Request Uri

by Timo Klecker

Hi all! Our Kamailio (3.1.4) crashed when modifying the username-Part of a Request URI using: $rU = $(rU{s.strip,6}); Initial Request URI: /sbin/kamailio[40658]: NOTICE: <script>: [ INVITE ] Got new Packet to sip:123456:pass@sip.custom.com The config-script now removed the first 6 chars from the username part and would replace them in one of the following lines, but Kamailio had problems here: /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40658]: NOTICE: <script>: Strip from Head: Request Username: <null> // $rU /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40658]: ERROR: <core> [action.c:801]: ERROR: do_action: bad uri <sip::passsip.custom.com>, dropping packet Is there maybe a error when modifying a uri with password this way? Do we have to change this? Ultimately Kamailio crashed: /sbin/kamailio[40658]: ERROR: <core> [action.c:1513]: run action error at: :0 /sbin/kamailio[40658]: ERROR: pv [pv_core.c:1761]: do action failed /sbin/kamailio[40658]: ERROR: <core> [lvalue.c:358]: setting pvar failed /sbin/kamailio[40658]: ERROR: <core> [lvalue.c:411]: assignment failed at pos: (319,10-319,34) /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI Like 5000 lines more of /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI Due to rerouting internal and trying to remove more parts of the request Uri using $rU = $(rU{s.strip,6}); Which then concluded to the following: /sbin/kamailio[40656]: ALERT: <core> [main.c:741]: child process 40660 exited by a signal 11 /sbin/kamailio[40656]: ALERT: <core> [main.c:744]: core was generated /sbin/kamailio[40656]: INFO: <core> [main.c:756]: INFO: terminating due to SIGCHLD /sbin/kamailio[40659]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40682]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40677]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40676]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40678]: INFO: <core> [main.c:807]: INFO: signal 15 received [...] I will try to recreate this using the new version (4.1.6) on monday. Kind regards Timo Klecker

9 years, 11 months

Sanity Module - no 400 Bad Request message when no VIA header

by Kowalski Piotr 3 - Hurt

Hello everybody, We are facing a problem with Sanity Module. We need to use it to force Kamailio to send back 400 Bad Request message when there's no VIA header within INVITE. How can we achieve this? In our opinion there's no possibility to set this easy. We get no answer from Kamailio when sending corrupted INVITE (with no VIA headers). Many thanks for your help. Piotr Kowalski Starszy Architekt Techniczny Tel. +48 22 699 50 93 Kom. +48 519 123 289 Orange Orange Polska Hurt Badania i Rozwój Sieci i Platform Usługowych Wydział Usług Konwergentnych Obrzeżna 7 /p. 309, 02-691 Warszawa Fax. +48 22 857 99 86 www.hurt-orange.pl<http://www.hurt-orange.pl/> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Czy musisz drukować tę wiadomość? Pomyśl o środowisku. Korzystaj z e-faktury. Treść tej wiadomości jest własnością Orange Polska i zawiera informacje stanowiące tajemnicę przedsiębiorstwa Orange Polska. Jeżeli nie jesteście Państwo jej adresatem, bądź otrzymaliście ją przez pomyłkę, prosimy o powiadomienie o tym nadawcy oraz trwałe jej usunięcie. Orange Polska Spółka Akcyjna z siedzibą i adresem w Warszawie (02-326) przy Al. Jerozolimskich 160, wpisana do Rejestru Przedsiębiorców prowadzonego przez Sąd Rejonowy dla m.st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego pod numerem 0000010681; REGON 012100784, NIP 526-02-50-995; z pokrytym w całości kapitałem zakładowym wynoszącym 3.937.072.437 złotych.

9 years, 11 months

Registration at SCSCF Failed

by Kamal Palei

Hi All In 4.2.0 Kamailio (S-CSCF), when I try to register an IMS endpoint, I get 403 from P-CSCSF. When I checked the error logs, SCSCF logs look as below 1(5455) INFO: ims_auth [authorize.c:824]: authenticate(): uri=sip: group4-imslab11.in nonce=b9eec0ad9d6d186408541d8a23a7c7a5 response=df89adebbf28f25d38d2f993f7cde033 qop= nc= cnonce= hbody= 1(5455) INFO: ims_auth [authorize.c:872]: authenticate(): UE said: df89adebbf28f25d38d2f993f7cde033 and we expect df89adebbf28f25d38d2f993f7cde033 ha1 599fb074cf189867eed06f3b6ebc0b97 (REGISTER) 1(5455) INFO: ims_registrar_scscf [cxdx_sar.c:79]: create_return_code(): created AVP successfully : [saa_return_code] - [-2] 12(5466) INFO: ims_registrar_scscf [cxdx_avp.c:138]: cxdx_get_avp(): cxdx_get_experimental_result_code: Failed finding avp 12(5466) INFO: ims_registrar_scscf [cxdx_avp.c:138]: cxdx_get_avp(): cxdx_get_charging_info: Failed finding avp I have added an user necs_0 in hss_db, so why I get below error. Please let me know what is missed here. Is S-CSCF not able to contact HSS ?? Best Regards kamal

9 years, 11 months

Kamailio Crash

by Kristian Kielhofner

version: kamailio 4.1.6 (x86_64/linux) 58746c I looked through 4.1 commits but didn't catch anything that looked like a fix for this but it's a very real possibility this is a duplicate (again). Any thoughts (backtrace attached)? Thanks! -- Kristian Kielhofner

9 years, 11 months

Contact Header User

by Marc Soda

Can someone recommend a way to extract the user part of a Contact header URI? Right now I'm just trying to pass it to xlog(). I have tried: - xlog("L_NOTICE", "$(ct{uri.user})"); This gives me an empty string. - xlog("L_NOTICE", @contact.uri.user); This gives me an error starting Kamailio: "function xlog: parameter 2 is not constant". Note, I can't seem to get any select working, for example, @ruri gives me the same error. Any suggestions? Thanks, Marc

9 years, 11 months

[Kamailio -feature]

by Ludovic DURAND

Hi, The purpose of projet is to implement a VoIP secure solution with Kamailio as core IMS network. In this project VoIP call will be established with zRTP. SBC is transparent for zRTP call, zRTP is establish between 2 end point (terminals), SBC don't decrypt or encrypt the call. Thus SBC don't modify codec. Is there a SBC solution provided by Kamailio ? How is managed the SBC failover mecanism ? is there SBC backup ? What is the status of context registered in Kamailio (P-CSCF & S-CSCF) in case of SBC failure ? - Is it deleted automatically ? - dispatched to another SBC (backup SBC) ? Is there mecanism in Kamailio to check SBC overload and manage a dispatching of zRTP call to available SBC ? Question related to P-CSCF and S-CSCF : - Is there redundant function (such as active/active or active/standby solution) of contextual data (customer data stored at the registration REGISTER on P-CSCF and S-CSCF) ? Best Regards Ludovic DURAND SII

9 years, 11 months

acc.so segfault using 4.3.0-dev2 (6daafdb5b6c9fc72698d43f81656bd511cacce69)

by Anthony Messina

I get repeatable segfaults with acc.so in 4.3.0-dev2. Fedora 20 x86_64. Debug log attached. -A -- Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery 8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E

9 years, 11 months

Kamailio 4.2 crash

by Rahul MathuR

Hello, I have recently moved some traffic to kamailio-4.2 (installed on a seperate box) and it crashes quite often. Below is the backtrace of the core files - <CORE#1> (gdb) bt #0 0x00000033d8c32635 in raise () from /lib64/libc.so.6 #1 0x00000033d8c33e15 in abort () from /lib64/libc.so.6 #2 0x000000000049add5 in sig_alarm_abort (signo=14) at main.c:689 #3 <signal handler called> #4 0x00000033d8ce50c7 in syscall () from /lib64/libc.so.6 #5 0x00007f7ca2ea0a1e in futex_get (lock=0x7f7ca3334388) at ../../mem/../futexlock.h:110 #6 0x00007f7ca2ea1e99 in remove_dialog_timer (tl=0x7f7ca3384c98) at dlg_timer.c:168 #7 0x00007f7ca2e83e9b in destroy_dlg (dlg=0x7f7ca3384c40) at dlg_hash.c:357 #8 0x00007f7ca2e84e19 in destroy_dlg_table () at dlg_hash.c:438 #9 0x00007f7ca2e50b89 in mod_destroy () at dialog.c:773 #10 0x000000000058dfd5 in destroy_modules () at sr_module.c:818 #11 0x0000000000499ad3 in cleanup (show_status=1) at main.c:564 #12 0x000000000049b096 in shutdown_children (sig=15, show_status=1) at main.c:706 #13 0x000000000049d66c in handle_sigs () at main.c:797 #14 0x00000000004a4e57 in main_loop () at main.c:1757 #15 0x00000000004a8a43 in main (argc=2, argv=0x7fff58d21368) at main.c:2609 (gdb) quit <CORE#2> (gdb) bt #0 0x00007f7ca2ea22d7 in update_dlg_timer (tl=0x58, timeout=10) at dlg_timer.c:203 #1 0x00007f7ca2e824f3 in dlg_clean_run (ti=44865910) at dlg_hash.c:253 #2 0x00007f7ca2e566fc in dlg_clean_timer_exec (ticks=44865910, param=0x0) at dialog.c:1250 #3 0x00000000005f93e8 in fork_sync_timer (child_id=-1, desc=0x7f7ca2eb3a71 "Dialog Clean Timer", make_sock=1, f=0x7f7ca2e566e3 <dlg_clean_timer_exec>, param=0x0, interval=90) at timer_proc.c:232 #4 0x00007f7ca2e50476 in child_init (rank=0) at dialog.c:730 #5 0x000000000058e385 in init_mod_child (m=0x7f7ca8c09eb8, rank=0) at sr_module.c:930 #6 0x000000000058e0c0 in init_mod_child (m=0x7f7ca8c0b000, rank=0) at sr_module.c:927 #7 0x000000000058e68f in init_child (rank=0) at sr_module.c:957 #8 0x00000000004a435c in main_loop () at main.c:1705 #9 0x00000000004a8a43 in main (argc=2, argv=0x7fff58d21368) at main.c:2609 (gdb) quit kamailio -v version: kamailio 4.2.0-pre0 (x86_64/linux) a78764-dirty flags: STATS: Off, USE_TCP, 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 4MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: a78764 -dirty Kindly let me know which version to move. -- Warm Regds. MathuRahul -- Warm Regds. MathuRahul

9 years, 11 months

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

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 December 2014