sr-dev June 2014

sr-dev@lists.kamailio.org

21 participants
152 discussions

git:4.1: auth: enhanced log message when method param fails to be retrieved

by Daniel-Constantin Mierla

Module: sip-router Branch: 4.1 Commit: 3997dcccf36579442cb92222fe0868accd64b537 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=3997dcc… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Wed Jun 11 19:01:17 2014 +0200 auth: enhanced log message when method param fails to be retrieved (cherry picked from commit 35329870fe22115fd24a396b743e4814278ce46a) --- modules/auth/auth_mod.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/modules/auth/auth_mod.c b/modules/auth/auth_mod.c index cdfe459..a148053 100644 --- a/modules/auth/auth_mod.c +++ b/modules/auth/auth_mod.c @@ -687,7 +687,7 @@ static int pv_www_authenticate2(struct sip_msg *msg, char* realm, } if (get_str_fparam(&smethod, msg, (fparam_t*)method) < 0) { - LM_ERR("failed to get method value\n"); + LM_ERR("failed to get method value from msg %p var %p\n", msg, method); goto error; }

10 years, 6 months

git:master: auth: enhanced log message when method param fails to be retrieved

by Daniel-Constantin Mierla

Module: sip-router Branch: master Commit: 35329870fe22115fd24a396b743e4814278ce46a URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=3532987… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Wed Jun 11 19:01:17 2014 +0200 auth: enhanced log message when method param fails to be retrieved --- modules/auth/auth_mod.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/modules/auth/auth_mod.c b/modules/auth/auth_mod.c index cdfe459..a148053 100644 --- a/modules/auth/auth_mod.c +++ b/modules/auth/auth_mod.c @@ -687,7 +687,7 @@ static int pv_www_authenticate2(struct sip_msg *msg, char* realm, } if (get_str_fparam(&smethod, msg, (fparam_t*)method) < 0) { - LM_ERR("failed to get method value\n"); + LM_ERR("failed to get method value from msg %p var %p\n", msg, method); goto error; }

10 years, 6 months

[tracker] Comment added: maddr broken in 4.1.x?

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#433 - maddr broken in 4.1.x? User who did this - Daniel-Constantin Mierla (miconda) ---------- Request to close by submitter, -DHONOR_MADDR has to be enabled. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=433#comment1529 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.

10 years, 6 months

[tracker] Task closed: maddr broken in 4.1.x?

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#433 - maddr broken in 4.1.x? User who did this - Daniel-Constantin Mierla (miconda) Reason for closing: Not a bug More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=433 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.

10 years, 6 months

[tracker] Comment added: CRASH: segmentation fault after INVITE

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#439 - CRASH: segmentation fault after INVITE User who did this - Daniel-Constantin Mierla (miconda) ---------- The fix for this issue looks like the same for #440. Can you try with it and see if this case is ok? ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=439#comment1528 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.

10 years, 6 months

Reloading kamailio.cfg on the fly

by Rahul MathuR

Hello, Is it possible to reload kamailio.cfg at the runtime after doing few modifications on the business rules laid under CNXCC module. Eg: #!ifdef CNXCC_CHANNEL xlog("L_INFO", "Setting up channel based credit control"); $var(max_chan) = 2; $var(retcode) = cnxcc_set_max_channels("$var(client)", "$var(max_chan)"); if ($var(retcode) == -1) { xlog("Error setting up credit control"); return; } $var(count) = -1; if (!cnxcc_get_channel_count("$var(client)", "$var(count)")) { xlog("Error getting customer's channel count"); } xlog("L_INFO", "CNXCC ROUTE: $var(client) has $var(count) call(s)"); if ($var(retcode) < -1) { xlog("Too many channels for customer"); sl_send_reply(403, "Forbidden"); if (!cnxcc_terminate_all("$var(client)")) { xlog("Error terminating customer's calls"); } exit; } #!endif ****************************************************** Now I want to change the value of max_chan on the fly. Does this step neccassitates a restart of kamailio process as a whole ? If no, then could somebody please guide me how to achieve this ? Thanks ! -- Warm Regds. MathuRahul

10 years, 6 months

[tracker] Comment added: CRASH: segmentation fault if there is no dispatcher available

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#440 - CRASH: segmentation fault if there is no dispatcher available User who did this - Daniel-Constantin Mierla (miconda) ---------- I pushed a fix for it, can you try it? Now it is only in master, I will backport if you confirm it works. To test it, if you have kamailio 4.1.x from git branch 4.1, do: <code> git pull origin git cherry-pick -x 88a9ffee284338d536b6f7e072e5c99b29d983ee make all make install </code> Restart kamailio and retest. Let me know the result. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=440#comment1527 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.

10 years, 6 months

git:master: dialog: execute internal event_route blocks under local_route type

by Daniel-Constantin Mierla

Module: sip-router Branch: master Commit: 88a9ffee284338d536b6f7e072e5c99b29d983ee URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=88a9ffe… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Wed Jun 11 17:12:37 2014 +0200 dialog: execute internal event_route blocks under local_route type - request_route type triggers additional script callbacks that could reset the transaction and can cause crashing - reported by Nuno Miguel Reis, FS#440 --- modules/dialog/dlg_handlers.c | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/modules/dialog/dlg_handlers.c b/modules/dialog/dlg_handlers.c index aaa1ab79..8e7b967 100644 --- a/modules/dialog/dlg_handlers.c +++ b/modules/dialog/dlg_handlers.c @@ -1481,15 +1481,15 @@ void dlg_run_event_route(dlg_cell_t *dlg, sip_msg_t *msg, int ostate, int nstate else fmsg = msg; - if (exec_pre_script_cb(fmsg, REQUEST_CB_TYPE)>0) + if (exec_pre_script_cb(fmsg, LOCAL_CB_TYPE)>0) { dlg_ref(dlg, 1); dlg_set_ctx_iuid(dlg); LM_DBG("executing event_route %d on state %d\n", rt, nstate); - set_route_type(REQUEST_ROUTE); + set_route_type(LOCAL_ROUTE); run_top_route(event_rt.rlist[rt], fmsg, 0); dlg_reset_ctx_iuid(); - exec_post_script_cb(fmsg, REQUEST_CB_TYPE); + exec_post_script_cb(fmsg, LOCAL_CB_TYPE); dlg_unref(dlg, 1); } }

10 years, 6 months

[tracker] Comment added: CRASH: segmentation fault if there is no dispatcher available (Attachment added)

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#440 - CRASH: segmentation fault if there is no dispatcher available User who did this - Nuno Miguel Reis (nmreis) ---------- Hi Daniel. I was able to recreate the initial situation corresponding the bug title and my first description. Basically if i have kamailio without any freeswitch instance up and running (corresponding to one of the entries in dispatcher) and i try to place a call kamailio segfaults. Please find attached a new full backtrace for a new core dump and the correspondent kamailio.log with debug=3. The PID in the log is between square brackets after the timestamp. In the meanwhile i'm figuring out presence and the way i deal with SIP PUBLISH messages. I'll get back here if a see new crashes related with presence handling. Looking forward to hear from you. ---------- 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=440#comment1526 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.

10 years, 6 months

[tracker] Comment added: CRASH: segmentation fault after INVITE

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#439 - CRASH: segmentation fault after INVITE User who did this - Olle Johansson (oej) ---------- Interestingly enough, using t_release after t_relay failure fixes the problem. t_relay returns a strange error code: -478. According to the docs from 1.5 tm module (which still documents t_relay error codes) it should be -4 for unresolvable address... ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=439#comment1525 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.

10 years, 6 months

← Newer
1
...
5
6
7
8
9
10
11
...
16
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev June 2014