THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#330 - debugger: new RPC command dbg.reset_msgid
User who did this - Víctor Seva (linuxmaniac)
----------
I just need to be able to reset the msgid ( $mi ) without restart kamailio.
I have a logger parser that exports the info ( route, var_dump, sip_in, sip_out ) for every message relaying on the $mi. So, I have test cases for every message $mi.yml in a sipp scenario and several sipp scenarios. So for each one I have to be able to reset $mi.
This is the first idea that came to my mind. Add a debugger parameter to enable the functionality, a callback at receive and a new debugger RPC command to reset the id.
Can you explain me how can I do this without messing around in a normal environment? What is that debbuger pre-script function?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=330#comment1045
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#330 - debugger: new RPC command dbg.reset_msgid
User who did this - Daniel-Constantin Mierla (miconda)
----------
Can you detail a bit more about this need? Adding this condition in core does not seem the right way just for some test cases.
If it is not too late, maybe is ok to do it in pre-script callback function done in debugger module, so in config gets with the msg id you want.
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=330#comment1044
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,
I am considering to package soon a new version out of branch 3.3. If
anyone has spotted fixes that should be backported to that branch, reply
here. I'm not sure yet of an exact date, but should be rather soon,
being just a patch update.
A new release out of branch 4.0 will be done short after this one.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A Project Manager has denied the request pending for the following task:
FS#319 - Possible memory leak in srdb1
User who did this - Daniel-Constantin Mierla (miconda)
Reason for denial:
Commented in the issue.
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=319
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#329 - SCA - Primary line appearance hangs when secondary is picked up.
User who did this - Andrew Mortensen (admorten)
----------
I've tested this myself now with the admorten/sca branch, and it appears to be working correctly. I'll commit the changes to the 4.x branch, and will let you know when it's done.
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=329#comment1043
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.