THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#298 - modules/debugger: activate/deactivate via cfg framework
User who did this - Víctor Seva (linuxmaniac)
----------
Sorry for my last comment. I'll try to explain myself in a better way. :-)
This change is not needed if mod_level_mode has to be 1 on the initial config in order to be able to activate/deactivate via cfg framework.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=298#comment889
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#298 - modules/debugger: activate/deactivate via cfg framework
User who did this - Víctor Seva (linuxmaniac)
----------
AFAIK if it's needed that mod_level_mode is 1 on start. No, it's not needed.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=298#comment888
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#298 - modules/debugger: activate/deactivate via cfg framework
User who did this - Daniel-Constantin Mierla (miconda)
----------
Is this change needed?
@@ -1100,7 +1104,14 @@ int dbg_get_mod_debug_level(char *mname, int mnlen, int *mlevel)
*/
void dbg_enable_mod_levels(void)
{
- if(_dbg_mod_table==NULL)
- return;
set_module_debug_level_cb(dbg_get_mod_debug_level);
}
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=298#comment887
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.
Hello,
Crocodile is having a launch event this evening for our new SIP network
and SDK (making use of Kamailio with SIP over WebSocket and outbound).
The launch will be broadcast live from 18:30 BST. Anyone interested can
view the broadcast at http://lnx.so/croc (the link currently points to our
blog but will go live properly shortly before the broadcast).
Regards,
Peter
--
Peter Dunkley
Technical Director
Crocodile RCS Ltd
Hi I am sending a request to kamailio server with tel uri as a part of
request uri. I am getting "478 Unresolvable destination" from the server.
Please let me know what are the changes required to handle TEL URI in
kamailio
Here is the request which i am sending to kamailio:
INVITE tel:229;phone-context=domain.com SIP/2.0
From: "228"<sip:228@domain.com>;tag=xxxxx
To: "229"<tel:229;phone-context=domain.com>
Thanks in advance
Regards
Raman
Hello,
When I run this:
kamctl fifo dlg_list | grep '^dialog' | wc -l
I get 38 dialogs.
When I run this:
sercmd -s unixs:/tmp/kamailio_ctl dlg.list | egrep '^hash' | wc -l
I get 8 dialogs, rain or shine.
Has anyone heard of this bug? Running the latest 3.3 pull...
Thanks,
-- Alex
--
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
United States
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#298 - modules/debugger: activate/deactivate via cfg framework
User who did this - Víctor Seva (linuxmaniac)
----------
Ok. But now with this changes activate/deactivate only works if debugger parameter mod_level_mode is 1 on the initial start.
----------
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=298#comment886
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#298 - modules/debugger: activate/deactivate via cfg framework
User who did this - Daniel-Constantin Mierla (miconda)
----------
hash_size makes no sense to be changed at run time, because it is set for fixed number of modules (those loaded). Changing the hash table will require adding locks to protect it, introducing more performance penalties for something that could be heavily used (i.e., for each log message).
It can be in cfg structure read only, just for purpose of displaying it with kamcmd, but no runtime change.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=298#comment885
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#298 - modules/debugger: activate/deactivate via cfg framework
User who did this - Víctor Seva (linuxmaniac)
----------
But is this change needed if we want to change hash_size via cfg?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=298#comment884
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#298 - modules/debugger: activate/deactivate via cfg framework
User who did this - Daniel-Constantin Mierla (miconda)
----------
The patch is rather intrusive without a good reason - there is no need to change the pointer and size of the hash table even if you define hash_size via cfg framework as read only.
In other words, the next two definitions in debugger_api.c should stay the same:
static dbg_mod_slot_t *_dbg_mod_table = NULL;
static unsigned int _dbg_mod_table_size = 0;
The patch should be rather minimal, mainly around mod_level_mode changes.
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=298#comment883
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.