Hi,
We would like to propose to change rtpengine_tout granularity from seconds to milliseconds as for example INVITE retransmissions occur faster than this (e.g. 500ms) We would benefit from kamailio falling back to another rtpengine in case one is not responsive before the retransmission. Should you appreciate this idea, I attach a patch with the small changes.
Thank you, Lucian
On 10/02/15 12:21 PM, Lucian Balaceanu wrote:
Hi,
We would like to propose to change rtpengine_tout granularity from seconds to milliseconds as for example INVITE retransmissions occur faster than this (e.g. 500ms) We would benefit from kamailio falling back to another rtpengine in case one is not responsive before the retransmission. Should you appreciate this idea, I attach a patch with the small changes.
Fine with me. I wonder if the parameter should be renamed (suffix _ms or something) to keep people from stepping into a trap when upgrading?
cheers
In my opinion it would be enough to document the change here: http://www.kamailio.org/wiki/install/upgrade/stable-to-devel
On 10.02.2015 19:52, Richard Fuchs wrote:
On 10/02/15 12:21 PM, Lucian Balaceanu wrote:
Hi,
We would like to propose to change rtpengine_tout granularity from seconds to milliseconds as for example INVITE retransmissions occur faster than this (e.g. 500ms) We would benefit from kamailio falling back to another rtpengine in case one is not responsive before the retransmission. Should you appreciate this idea, I attach a patch with the small changes.
Fine with me. I wonder if the parameter should be renamed (suffix _ms or something) to keep people from stepping into a trap when upgrading?
cheers
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-
Lucian Balaceanu -
Pawel Kuzak -
Richard Fuchs