sr-users November 2013

sr-users@lists.kamailio.org

100 participants
161 discussions

Re: [SR-Users] #cfgutils: sleep(x) does not work in failure_route
by klaus.lists#inode.at 07 Nov '13

07 Nov '13

Hello, I have an update: today I´ve tested with kamailio version 4.0.4, but the behaviour is still the same: it is working fine only when no response has been received; as soon as a provisional response is received, the failure route is ignoring the "sleep" function. Klaus > Hello list, > > I have troubles using the function "usleep(x)" or "sleep(x)" (the behaviour > is the same) of the "cfgutils" module > (<http://kamailio.org/docs/modules/3.2.x/modules_k/cfgutils.html#… [View More]idp76968> ) > in the failure_route. According documentation, this function could be used in > any route, including the failure_route, too. However, when I call this > function, it does not show any reaction, if a transaction was already answered > with a provisional response. It is still working fine, when a transaction is > timing out, as no target socket is reachable. This is confusing me! > > Please find below some xlog messages from my configuration file in two > scenarios (function "t_set_fr(20000, 10000);" is identic in both scenarios): > (1) scenario 1 is including a primary target, looked up in the registrar DB, > which is unreachable; after transaction timeout I have inserted the function > "sleep()" in the failure_route for forcing a delay > => here it is working fine (see timestamp) > > (2) scenario 2 is including a primary target which is responding, but not > establishing the session; after transaction timeout the procedure is still the > same as in scenario (1) > => here is no delay visible in the log and practically detectable > > From my point of view, this is a malfuntion! Does anybody see it different? > I´ve tested these scenarios with kamailio-3.2.x and kamailio-3.3.x - no > difference. > > Thanks for any hints! > > Klaus > > ################# SCENARIO (1) ORIG TARGET IS UNREACHABLE > ########################## > Nov 6 15:58:25 sipsrvnode1 /usr/sbin/kamailio[28879]: INFO: -<|XLOG|>-: > <RELAY> is reached for RU:<sip:117002@10.16.48.226:5678> , > From:<sip:1101015555@10.16.48.71> , To:<sip:115300@10.16.48.44> , Method: > INVITE, Call-ID: 1107651805(a)10.16.48.71 <mailto:1107651805@10.16.48.71> > > Nov 6 15:58:35 sipsrvnode1 /usr/sbin/kamailio[28880]: INFO: -<|XLOG|>-: > <FAILRELAY> is reached with Code: 408 From:<sip:1101015555@10.16.48.71> > To:<sip:115300@10.16.48.44> > > Nov 6 15:58:35 sipsrvnode1 /usr/sbin/kamailio[28880]: INFO: -<|XLOG|>-: > failure_route <FAILRELAY> is reached because of a BRANCH_TIMEOUT of > RU:<sip:117002@10.16.48.226:5678> > > Nov 6 15:58:35 sipsrvnode1 /usr/sbin/kamailio[28880]: INFO: -<|XLOG|>-: > <FAILRELAY> s l e e p 2000ms / 2s > > Nov 6 15:58:37 sipsrvnode1 /usr/sbin/kamailio[28880]: INFO: -<|XLOG|>-: > <FAILRELAY> s l e p t 2000ms / 2s > > Nov 6 15:58:37 sipsrvnode1 /usr/sbin/kamailio[28879]: INFO: -<|XLOG|>-: > <RELAYFB> is reached for RU:<sip:117003@10.16.48.226:7001> , > From:<sip:1101015555@10.16.48.71> , To:<sip:115300@10.16.48.44> , Method: > INVITE, Call-ID: 1107651805(a)10.16.48.71 <mailto:1107651805@10.16.48.71> > > ################# SCENARIO (2) ORIG TARGET IS REACHABLE > ########################## > > Nov 6 16:02:14 sipsrvnode1 /usr/sbin/kamailio[29034]: INFO: -<|XLOG|>-: > <RELAY> is reached for RU:<sip:117002@10.16.48.226:5678> , > From:<sip:1101015555@10.16.48.71> , To:<sip:115300@10.16.48.44> , Method: > INVITE, Call-ID: 553330101(a)10.16.48.71 <mailto:553330101@10.16.48.71> > > Nov 6 16:02:34 sipsrvnode1 /usr/sbin/kamailio[29036]: INFO: -<|XLOG|>-: > <FAILRELAY> is reached with Code: 408 From:<sip:5555@10.16.48.71> > To:<sip:4000@10.16.48.44> > > Nov 6 16:02:34 sipsrvnode1 /usr/sbin/kamailio[29036]: INFO: -<|XLOG|>-: > failure_route <FAILRELAY> is reached because of a BRANCH_TIMEOUT of > RU:<sip:117002@10.16.48.44> > > Nov 6 16:02:34 sipsrvnode1 /usr/sbin/kamailio[29036]: INFO: -<|XLOG|>-: > <FAILRELAY> s l e e p 2000ms / 2s > > Nov 6 16:02:34 sipsrvnode1 /usr/sbin/kamailio[29036]: INFO: -<|XLOG|>-: > <FAILRELAY> s l e p t 2000ms / 2s > > Nov 6 16:02:34 sipsrvnode1 /usr/sbin/kamailio[29036]: INFO: -<|XLOG|>-: > <RELAYFB> is reached for RU:<sip:117003@10.16.48.44> , > From:<sip:5555@10.16.48.71> , To:<sip:4000@10.16.48.44> , Method: INVITE, > Call-ID: 553330101(a)10.16.48.71 <mailto:553330101@10.16.48.71> > [View Less]

2 1

Email alert
by phillman25 07 Nov '13

07 Nov '13

Hi I was wondering which module i could use to configure an email alert upon an event in kamailio.cfg file i.e. if ...... then send to email address xxxx any ideas? thanks! Phillip

3 2

IM Broadcasting
by sipatse＠in.gr 07 Nov '13

07 Nov '13

1 0

408 callee hangup problem
by kamailio＠AaronLux.com 07 Nov '13

07 Nov '13

2 3

Google search
by Carlos Ruiz Díaz 06 Nov '13

06 Nov '13

Hi guys, this happens to me all the time: when I search for documentation about a specific Kamailio module on Google, I always land on outdated entries usually from Kamailio 1.6.x. Although this seems trivial and I could simply update the URL to the current version of Kamailio, this may be not so obvious for new users and they may end up reading expired documentation and/or implementing non-optimal solutions to their problems. is there a way to only allow indexation of the last documentation?… [View More]

3 2

#cfgutils: sleep(x) does not work in failure_route
by Klaus Feichtinger 06 Nov '13

06 Nov '13

Hello list, I have troubles using the function "usleep(x)" or "sleep(x)" (the behaviour is the same) of the "cfgutils" module (http://kamailio.org/docs/modules/3.2.x/modules_k/cfgutils.html#idp76968) in the failure_route. According documentation, this function could be used in any route, including the failure_route, too. However, when I call this function, it does not show any reaction, if a transaction was already answered with a provisional response. It is still working fine, when a … [View More]transaction is timing out, as no target socket is reachable. This is confusing me! Please find below some xlog messages from my configuration file in two scenarios (function "|t_set_fr(20000, 10000);" is identic in both scenarios|): (1) scenario 1 is including a primary target, looked up in the registrar DB, which is unreachable; after transaction timeout I have inserted the function "sleep()" in the failure_route for forcing a delay => here it is working fine (see timestamp) (2) scenario 2 is including a primary target which is responding, but not establishing the session; after transaction timeout the procedure is still the same as in scenario (1) => here is no delay visible in the log and practically detectable From my point of view, this is a malfuntion! Does anybody see it different? I´ve tested these scenarios with kamailio-3.2.x and kamailio-3.3.x - no difference. Thanks for any hints! Klaus ################# SCENARIO (1) ORIG TARGET IS UNREACHABLE ########################## Nov 6 15:58:25 sipsrvnode1 /usr/sbin/kamailio[28879]: INFO: -<|XLOG|>-: <RELAY> is reached for RU: sip:117002@10.16.48.226:5678, From: sip:1101015555@10.16.48.71, To: sip:115300@10.16.48.44, Method: INVITE, Call-ID: 1107651805(a)10.16.48.71 Nov 6 15:58:35 sipsrvnode1 /usr/sbin/kamailio[28880]: INFO: -<|XLOG|>-: <FAILRELAY> is reached with Code: 408 From: sip:1101015555@10.16.48.71 To: sip:115300@10.16.48.44 Nov 6 15:58:35 sipsrvnode1 /usr/sbin/kamailio[28880]: INFO: -<|XLOG|>-: failure_route <FAILRELAY> is reached because of a BRANCH_TIMEOUT of RU: sip:117002@10.16.48.226:5678 Nov 6 15:58:35 sipsrvnode1 /usr/sbin/kamailio[28880]: INFO: -<|XLOG|>-: <FAILRELAY> s l e e p 2000ms / 2s Nov 6 15:58:37 sipsrvnode1 /usr/sbin/kamailio[28880]: INFO: -<|XLOG|>-: <FAILRELAY> s l e p t 2000ms / 2s Nov 6 15:58:37 sipsrvnode1 /usr/sbin/kamailio[28879]: INFO: -<|XLOG|>-: <RELAYFB> is reached for RU: sip:117003@10.16.48.226:7001, From: sip:1101015555@10.16.48.71, To: sip:115300@10.16.48.44, Method: INVITE, Call-ID: 1107651805(a)10.16.48.71 ################# SCENARIO (2) ORIG TARGET IS REACHABLE ########################## Nov 6 16:02:14 sipsrvnode1 /usr/sbin/kamailio[29034]: INFO: -<|XLOG|>-: <RELAY> is reached for RU: sip:117002@10.16.48.226:5678, From: sip:1101015555@10.16.48.71, To: sip:115300@10.16.48.44, Method: INVITE, Call-ID: 553330101(a)10.16.48.71 Nov 6 16:02:34 sipsrvnode1 /usr/sbin/kamailio[29036]: INFO: -<|XLOG|>-: <FAILRELAY> is reached with Code: 408 From: sip:5555@10.16.48.71 To: sip:4000@10.16.48.44 Nov 6 16:02:34 sipsrvnode1 /usr/sbin/kamailio[29036]: INFO: -<|XLOG|>-: failure_route <FAILRELAY> is reached because of a BRANCH_TIMEOUT of RU: sip:117002@10.16.48.44 Nov 6 16:02:34 sipsrvnode1 /usr/sbin/kamailio[29036]: INFO: -<|XLOG|>-: <FAILRELAY> s l e e p 2000ms / 2s Nov 6 16:02:34 sipsrvnode1 /usr/sbin/kamailio[29036]: INFO: -<|XLOG|>-: <FAILRELAY> s l e p t 2000ms / 2s Nov 6 16:02:34 sipsrvnode1 /usr/sbin/kamailio[29036]: INFO: -<|XLOG|>-: <RELAYFB> is reached for RU: sip:117003@10.16.48.44, From: sip:5555@10.16.48.71, To: sip:4000@10.16.48.44, Method: INVITE, Call-ID: 553330101(a)10.16.48.71 [View Less]

1 0

dispatcher: ds_options_callback, Setting the state failed
by Seudin Kasumovic 06 Nov '13

06 Nov '13

Hi, Test configuration uses OPTION for ping method. In log below host 198.51.100.68 probed first but reply come latter then 192.0.2.4. Seams that only last probed uri tried for setting state other hosts. Also, DEBUG log is broken. (kamailio version: kamailio 4.1.0-pre1 (i386/linux)). Nov 5 12:48:01 localhost kamailio[23729]: DEBUG: dispatcher [dispatch.c:2420]: ds_check_timer(): probing set #28, URI sip: 198.51.100.68:5060 Nov 5 12:48:01 localhost kamailio[23729]: DEBUG: tm [uac.c:243]: … [View More]t_uac_prepare(): DEBUG:tm:t_uac: next_hop=<sip:172.16.23.130> Nov 5 12:48:01 localhost kamailio[23729]: DEBUG: tm [uac.c:182]: dlg2hash(): DEBUG: dlg2hash: 33871 Nov 5 12:48:01 localhost kamailio[23729]: DEBUG: tm [uac.c:345]: t_uac_prepare(): executing event_route[tm:local-request] Nov 5 12:48:01 localhost kamailio[23729]: INFO: <script>: 1280:tm:local-request OPTIONS sip:198.51.100.68:5060 --ID= 77db7ea0-23729(a)172.16.23.5 Nov 5 12:48:01 localhost kamailio[23729]: DEBUG: tm [uac.c:410]: t_uac_prepare(): apply new updates to sip msg Nov 5 12:48:01 localhost kamailio[23729]: DEBUG: dispatcher [dispatch.c:2420]: ds_check_timer(): probing set #0, URI sip:192.0.2.4:5090 Nov 5 12:48:01 localhost kamailio[23729]: DEBUG: tm [uac.c:243]: t_uac_prepare(): DEBUG:tm:t_uac: next_hop=<sip:172.16.23.130> Nov 5 12:48:01 localhost kamailio[23729]: DEBUG: tm [uac.c:182]: dlg2hash(): DEBUG: dlg2hash: 33872 Nov 5 12:48:01 localhost kamailio[23729]: DEBUG: tm [uac.c:345]: t_uac_prepare(): executing event_route[tm:local-request] Nov 5 12:48:01 localhost kamailio[23729]: INFO: <script>: 1280:tm:local-request OPTIONS sip:192.0.2.4:5090 --ID= 77db7ea1-23729(a)172.16.23.5 Nov 5 12:48:01 localhost kamailio[23725]: DEBUG: tm [t_lookup.c:1071]: t_check_msg(): DEBUG: t_check_msg: msg id=54 global id=53 T start=(nil) Nov 5 12:48:01 localhost kamailio[23725]: DEBUG: tm [t_lookup.c:949]: t_reply_matching(): DEBUG: t_reply_matching: hash 33871 label 0 branch 0 Nov 5 12:48:01 localhost kamailio[23725]: DEBUG: tm [t_lookup.c:1003]: t_reply_matching(): DEBUG: t_reply_matching: reply matched (T=0xb492a8a8)! Nov 5 12:48:01 localhost kamailio[23725]: DEBUG: tm [t_lookup.c:1140]: t_check_msg(): DEBUG: t_check_msg: msg id=54 global id=54 T end=0xb492a8a8 Nov 5 12:48:01 localhost kamailio[23725]: DEBUG: tm [t_reply.c:2205]: reply_received(): DEBUG: reply_received: org. status uas=0, uac[0]=0 local=2 is_invite=0) Nov 5 12:48:01 localhost kamailio[23725]: DEBUG: tm [t_reply.c:1309]: t_should_relay_response(): ->>>>>>>>> T_code=0, new_code=200 Nov 5 12:48:01 localhost kamailio[23725]: DEBUG: tm [t_reply.c:2085]: local_reply(): DEBUG: local_reply: branch=0, save=0, winner=0 Nov 5 12:48:01 localhost kamailio[23725]: DEBUG: tm [t_reply.c:2122]: local_reply(): DEBUG: local transaction completed Nov 5 12:48:01 localhost kamailio[23725]: DEBUG: tm [t_hooks.c:288]: run_trans_callbacks_internal(): DBG: trans=0xb492a8a8, callback type 1024, id 0 entered Nov 5 12:48:01 localhost kamailio[23725]: DEBUG: dispatcher [dispatch.c:2359]: ds_options_callback(): OPTIONS-Request was finished with code 200 (to 192.0.2.4:5090> Nov 5 12:48:01 localhost kamailio[23725]: ERROR: dispatcher [dispatch.c:2372]: ds_options_callback(): Setting the state failed ( 192.0.2.4:5090> Nov 5 12:48:01 localhost kamailio[23725]: DEBUG: tm [t_reply.c:1667]: cleanup_uac_timers(): DEBUG: cleanup_uac_timers: RETR/FR timers reset Nov 5 12:48:01 localhost kamailio[23726]: DEBUG: tm [t_lookup.c:1071]: t_check_msg(): DEBUG: t_check_msg: msg id=50 global id=49 T start=(nil) Nov 5 12:48:01 localhost kamailio[23726]: DEBUG: tm [t_lookup.c:949]: t_reply_matching(): DEBUG: t_reply_matching: hash 33872 label 0 branch 0 Nov 5 12:48:01 localhost kamailio[23726]: DEBUG: tm [t_lookup.c:1003]: t_reply_matching(): DEBUG: t_reply_matching: reply matched (T=0xb492c918)! Nov 5 12:48:01 localhost kamailio[23726]: DEBUG: tm [t_lookup.c:1140]: t_check_msg(): DEBUG: t_check_msg: msg id=50 global id=50 T end=0xb492c918 Nov 5 12:48:01 localhost kamailio[23726]: DEBUG: tm [t_reply.c:2205]: reply_received(): DEBUG: reply_received: org. status uas=0, uac[0]=0 local=2 is_invite=0) Nov 5 12:48:01 localhost kamailio[23726]: DEBUG: tm [t_reply.c:1309]: t_should_relay_response(): ->>>>>>>>> T_code=0, new_code=200 Nov 5 12:48:01 localhost kamailio[23726]: DEBUG: tm [t_reply.c:2085]: local_reply(): DEBUG: local_reply: branch=0, save=0, winner=0 Nov 5 12:48:01 localhost kamailio[23726]: DEBUG: tm [t_reply.c:2122]: local_reply(): DEBUG: local transaction completed Nov 5 12:48:01 localhost kamailio[23726]: DEBUG: tm [t_hooks.c:288]: run_trans_callbacks_internal(): DBG: trans=0xb492c918, callback type 1024, id 0 entered Nov 5 12:48:01 localhost kamailio[23726]: DEBUG: dispatcher [dispatch.c:2359]: ds_options_callback(): OPTIONS-Request was finished with code 200 (to sip:192.0.2.4:5090, group 0) ds_list shows: SET_NO:: 2 SET:: 28 URI:: sip:198.51.100.68:5060 flags=TX priority=1 attrs= SET:: 0 URI:: sip:192.0.2.4:5090 flags=AP priority=1 attrs= -- Seudin Kasumovic [View Less]

2 2

use append_hf() and remove_hf() on the same message
by Camille Oudot 06 Nov '13

06 Nov '13

Hi, I'm using remove_hf() and append_hf() to manipulate the sip headers on my application. Apparently, calling insert_hf("foo") after remove_hf("bar") if bar is the last header (not including Content-Length) is a bad idea, foo doesn't get inserted (I understand that the append_hf() command tries to insert foo after bar, and since bar just disappeared, well, it fails) What is the safest way to both remove and append headers on the same message? Regards -- Camille

2 4

dialog stats reported by app_perl
by mayamatakeshi 06 Nov '13

06 Nov '13

Hello, I am using kamailio 4.0. I am experimenting with module app_perl. Actually, I am not using it, I am just loading it because it solves this problem when loading snmpstats: /usr/lib/libnetsnmpagent.so.10: undefined symbol: boot_DynaLoader However, before using app_perl i was seeing this: # kamctl fifo get_statistics dialog active_dialogs dialog:active_dialogs = 1 But with app_perl loaded, I see this: # kamctl fifo get_statistics dialog active_dialogs app_perl:active_dialogs = 1 So, … [View More]

2 2

TLS - No ServerHello
by Coy Cardwell 05 Nov '13

05 Nov '13

Hi all. We are using Kamailio 4.0.4 in an Edge Proxy to Central Registrar configuration. The system is in a functional state. Oddly, when we enable TLS, the Kamailio server never responds with a Server Hello to the Client Hello for TLS, so a connection is never established. Has anyone seen anything like this? There are no errors anywhere, the server just never responds to the initial TLS Client Hello. We know the packet arrives and is acknowledged at the TCP level. Just a bit stumped.

2 2

Jump to page:

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 November 2013