THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#307 - modules/debugger: add dbg_pv_dump config function. It dumps on json format the content of pv_cache
User who did this - Víctor Seva (linuxmaniac)
----------
Reworked patch:
- added more values on the documentation example
- refresh the output on the documentation example
- free the str_list items after been used.
- removed commented debug log
----------
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=307#comment956
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#307 - modules/debugger: add dbg_pv_dump config function. It dumps on json format the content of pv_cache
User who did this - Víctor Seva (linuxmaniac)
----------
Reworked patch.
- avps: dump all the values as an array not just the last one
- xavps: dump all the content
----------
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=307#comment955
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#313 - DNS failover bugs
User who did this - Daniel-Constantin Mierla (miconda)
----------
I would find it also more consistent to use the receiving socket for new branches added by dns failover as done for the first forwarded branch. Anyhow we can add a mod param to control this if using '0' can bring benefits in some specific cases.
Just to mention here, afaik, by first socket selected is actually the first socket which is not loopback.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=313#comment954
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#313 - DNS failover bugs
User who did this - Jasmin Schnatterbeck (jasmin)
----------
if that is intended, what is the reason for the original (non failover) request to make it behave differently (= use received socket if possible)?
In my opinion it makes no sense to make orginal request behave differently than failover requests regarding the selection of send sockets.... failover means only contact another destination but do not change the rules for e.g. select the send socket.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=313#comment953
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#313 - DNS failover bugs
User who did this - Andrei Pelinescu-Onciul (andrei)
----------
The current failover behaviour is intended. If one does not force the socket, the socket will be elected on a per destination basis.
When mhomed=0, the first socket is always choosen (but that might change in the future). If mhomed=1 the socket is choosen using the routing table (at some performance expense).
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=313#comment952
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,
Kamailio SIP Server v4.0.2 stable release is out.
This is a maintenance release of the latest stable branch, 4.0, that
includes fixes since release of v4.0.0. There is no change to database
schema or configuration language structure that you have to do on
installations of v4.0.0. Deployments running previous v4.x.x versions
are strongly recommended to be upgraded to v4.0.2.
For more details about version 4.0.2 (including links and guidelines to
download the tarball or from GIT repository), visit:
* http://www.kamailio.org/w/2013/06/kamailio-v4-0-2-released/
RPM, Debian/Ubuntu packages will be available soon as well.
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.
The following task is now closed:
FS#287 - xavp. helper function to get a list of keys from a xavp
User who did this - Víctor Seva (linuxmaniac)
Reason for closing: Fixed
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=287
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.