THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#466 - our Record-Route is doubled on subsequent branches
User who did this - Andrew Pogrebennyk (marduk)
----------
Daniel, yes I am calling record_route() first time before creating the transaction and then again when routing new branch (after failure route). It didn't occur to me yet so thanks for the hint. My preliminary tests show that I should do if(!t_is_failure_route()) { record_route(); }
In fact, we have backported that internal msg_flag for detecting double record_route from master to 4.1 just 2 weeks ago: https://github.com/sipwise/kamailio/commit/1a6523a7793f8478445b311859682b43…
But it seems this doesn't work after failure route.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=466#comment1617
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.
Hi Daniel,
dbtext deals with DB1_BLOB in every place i see with the exception
of dbt_result_free
we still having the issue with the "internal structure not freed" but
memory is stable with the attached patch.
we were testing it with a table that has a blob column.
Best
Hello,
development (master) branch of Kamailio enters now in pre-release phase
for version 4.2.0. Therefore, no new feature should be pushed to master
until we create a dedicated branch for 4.2 (expected to be in about 4
weeks or so).
If in doubt to push or not a commit to master, push it first on a
personal branch (or attach to an email) and discuss it on sr-dev. The
new modules can be a bit more dynamic if there is need to get them to
the right shape (e.g., like decision to rename functions, parameters or
adjust database structure).
We hope to get many people involved in testing, to rich a stable state
before releasing 4.2.0. If you want to get involved and need assistance,
don't hesitate to write to mailing lists.
Help with updating the wiki page for migration from 4.1 to 4.2 as well
as what is new in 4.2 is very appreciated. I will post updates about the
very soon.
Many thanks to everyone involved in development of 4.2 and the early
testers that played with master branch.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Next Kamailio Advanced Trainings 2014 - http://www.asipto.com
Sep 22-25, Berlin, Germany
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#466 - our Record-Route is doubled on subsequent branches
User who did this - Daniel-Constantin Mierla (miconda)
----------
Are calling record_route() first time before creating the transaction and then again when routing new branches (in failure route or branch route)?
There is a internal msg_flag that marks a request when record route is added (not sure if in 4.1, but in devel for sure).
Also, in devel version, there is a new function from rr module that removes added record route lumps.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=466#comment1616
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.