December 2014 - sr-dev - kamailio.org

[kamailio] Support for custom number of successful probing requests before moving a destination from 'inactive' to 'active' state (#12)
by Alessandro Arrichiello 23 Dec '14

23 Dec '14

Hi, I've added support for custom number of successful probing requests before moving a destination from 'inactive' to 'active' state. The feature is the same of probing_threshold but it counts the number of successful ping before moving back a destination from 'inactive' to 'active' state. Hope it could be useful to someone else. I've also edited README file inserting the new parameter. I've corrected somewhere in the code some misspelled words and changed some variables (I used the same counter for failure and successful requests, these features are mutually exclusive). Please note: I've developed and tested this feature over release 4.1.6 You can merge this Pull Request by running: git pull https://github.com/alezzandro/kamailio master Or you can view, comment on it, or merge it online at: https://github.com/kamailio/kamailio/pull/12 -- Commit Summary -- * Added support for custom number of successful probing requests before moving a destination from 'inactive' to 'active' state. * Added support for custom number of successful probing requests before moving a destination from 'inactive' to 'active' state. x2 * Added support for custom number of successful probing requests before moving a destination from 'inactive' to 'active' state. x3 * Added support for custom number of successful probing requests before moving a destination from 'inactive' to 'active' state. x3 * Added support for custom number of successful probing requests before moving a destination from 'inactive' to 'active' state. x5 * Added support for custom number of successful probing requests before moving a destination from 'inactive' to 'active' state. x6 * Added support for custom number of successful probing requests before moving a destination from 'inactive' to 'active' state. x7 * Added support for custom number of successful probing requests before moving a destination from 'inactive' to 'active' state. x8 * Added support for custom number of successful probing requests before moving a destination from 'inactive' to 'active' state. x9 * Added support for custom number of successful probing requests before moving a destination from 'inactive' to 'active' state. x10 * Added support for custom number of successful probing requests before moving a destination from 'inactive' to 'active' state. x10 * Added support for custom number of successful probing requests before moving a destination from 'inactive' to 'active' state. x10 * Added support for custom number of successful probing requests before moving a destination from 'inactive' to 'active' state. x11 -- File Changes -- M modules/dispatcher/README (118) M modules/dispatcher/config.c (7) M modules/dispatcher/config.h (3) M modules/dispatcher/dispatch.c (84) M modules/dispatcher/dispatch.h (7) M modules/dispatcher/dispatcher.c (17) M modules/dispatcher/doc/dispatcher_admin.xml (26) -- Patch Links -- https://github.com/kamailio/kamailio/pull/12.patch https://github.com/kamailio/kamailio/pull/12.diff --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/12

2 3

[kamailio] wrong determination of udp/tcp request (#11)
by lazedo 23 Dec '14

23 Dec '14

Hi, i noticed a weird behavior in 4.2 branch with this kamailio.cfg (snippet) #!substdef "!UDP_SIP!udp:MY_IP_ADDRESS:5060!g" #!substdef "!TCP_SIP!tcp:MY_IP_ADDRESS:5060!g" listen=UDP_SIP listen=TCP_SIP ####### Routing Logic ######## route { # log the basic info regarding this call xlog("L_INFO", "$ci|start|recieved $oP request $rm $ou"); ..... } when clients using TCP send a SUBSCRIBE we get log info that it is a UDP operation. when we send the first notify we get tcp errors. for reference, i'm using Bria 4 in testing. Dec 20 16:49:29 kamailio-05 kamailio[5085]: INFO: <script>: YzYwYWVlOTFiMGU0YmNjM2IyMDA1NmQ4NjdiMGEwZDY|start|recieved UDP request SUBSCRIBE sip:2135@sip.com Dec 20 16:49:29 kamailio-05 kamailio[5072]: INFO: <script>: received dialog update for sip:2135@sip.com Dec 20 16:49:29 kamailio-05 kamailio[5072]: INFO: presence [notify.c:1604]: send_notify_request(): NOTIFY sip:user_7z7b6s@sip.com via sip:user_7z7b6s@192.168.16.12:62285;transpop on behalf of sip:2134@sip.com for event dialog Dec 20 16:49:29 kamailio-05 kamailio[5072]: CRITICAL: <core> [pass_fd.c:157]: send_all(): send on 0 failed: Socket operation on non-socket Dec 20 16:49:29 kamailio-05 kamailio[5072]: ERROR: <core> [tcp_main.c:2303]: tcpconn_send_put(): failed to get fd(write):Socket operation on non-socket (88) Dec 20 16:49:29 kamailio-05 kamailio[5072]: ERROR: tm [../../forward.h:227]: msg_send(): tcp_send failed Dec 20 16:49:29 kamailio-05 kamailio[5072]: ERROR: tm [uac.c:598]: send_prepared_request_impl(): t_uac: Attempt to send to precreated request failed --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/11

4 15

[tracker] Task closed: Cfg parsing error for alias/listen and custom global parameter
by sip-router 23 Dec '14

23 Dec '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#56 - Cfg parsing error for alias/listen and custom global parameter User who did this - Daniel-Constantin Mierla (miconda) Reason for closing: Won't implement Additional comments about closing: The workaround with ; after listen/alias (valid for any global parameter assignment) should be enough for the time being. More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=56 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.

1 0

git:lazedo/4.2.1:9b655b6c: correction
by lazedo 23 Dec '14

23 Dec '14

Module: kamailio Branch: lazedo/4.2.1 Commit: 9b655b6cbdc6cebadac806c56d214833466caf4f URL: https://github.com/kamailio/kamailio/commit/9b655b6cbdc6cebadac806c56d21483… Author: lazedo <luis.azedo(a)factorlusitano.com> Committer: lazedo <luis.azedo(a)factorlusitano.com> Date: 2014-12-23T11:44:24Z correction --- Modified: modules/kazoo/kazoo.c --- Diff: https://github.com/kamailio/kamailio/commit/9b655b6cbdc6cebadac806c56d21483… Patch: https://github.com/kamailio/kamailio/commit/9b655b6cbdc6cebadac806c56d21483… --- diff --git a/modules/kazoo/kazoo.c b/modules/kazoo/kazoo.c index e41a690..3431c61 100644 --- a/modules/kazoo/kazoo.c +++ b/modules/kazoo/kazoo.c @@ -291,11 +291,11 @@ static int mod_child_init(int rank) if (rank==PROC_MAIN) { - pid=fork_process(1, "AMQP Manager", 0); + pid=fork_process(1, "AMQP Manager", 1); if (pid<0) return -1; /* error */ if(pid==0){ - kz_amqp_manager_loop(1); + kz_amqp_manager_loop(0); } else { for(i=0; i < dbk_consumer_processes; i++) {

1 0

[tracker] Task closed: crash when using append_body_part()
by sip-router 23 Dec '14

23 Dec '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#442 - crash when using append_body_part() User who did this - Víctor Seva (linuxmaniac) Reason for closing: Works for me Additional comments about closing: With current master version I see no crash with the same cfg and uac.xml More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=442 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.

1 0

[tracker] Task closed: to send notification to sender when the offline message is delivered
by sip-router 23 Dec '14

23 Dec '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#211 - to send notification to sender when the offline message is delivered User who did this - Daniel-Constantin Mierla (miconda) Reason for closing: Deferred Additional comments about closing: No follow up for long time. Attach requested patches on a github issue if you want this to be pursued. More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=211 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.

1 0

[tracker] Comment added: crash when using append_body_part()
by sip-router 23 Dec '14

23 Dec '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#442 - crash when using append_body_part() User who did this - Víctor Seva (linuxmaniac) ---------- AFAIK yes. I will migrate this with the backtrace to github ---------- More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=442#comment1743 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.

1 0

[tracker] Task closed: tcp_async=yes breaks connect_timeout (no effect) and TCP reject detection
by sip-router 23 Dec '14

23 Dec '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#136 - tcp_async=yes breaks connect_timeout (no effect) and TCP reject detection User who did this - Daniel-Constantin Mierla (miconda) Reason for closing: Won't implement Additional comments about closing: Should this still be addressed, given the timeout option, the item must be re-opened on github issues. More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=136 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.

1 0

[tracker] Task closed: t_reply 302 redirects use wrong to-tag after fr_inv_timer fires
by sip-router 23 Dec '14

23 Dec '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#152 - t_reply 302 redirects use wrong to-tag after fr_inv_timer fires User who did this - Daniel-Constantin Mierla (miconda) Reason for closing: Won't implement Additional comments about closing: Re-open on github issues if still considered useful to implement, with a patch adding the option to enable/disable the behaviour via module parameter. More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=152 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.

1 0

[tracker] Task closed: named flags not working for at least acc module
by sip-router 23 Dec '14

23 Dec '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#119 - named flags not working for at least acc module User who did this - Daniel-Constantin Mierla (miconda) Reason for closing: Won't implement Additional comments about closing: Given the solution with defines, if you still want the named flags, re-open on github issues. More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=119 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.

1 0