sorry with the mess i did with this issue, i had the digest configured
in my subscription and i was not getting the response, so i created 3
mails for the same
:(
El mié, 29-06-2016 a las 13:58 +0200, david escribió:
> hello all
>
> i have been taking a look to the rtpengine.c code and i found
sorry with the mess i did with this issue, i had the digest configured
in my subscription and i was not getting the response, so i created 3
mails for the same
:(
El mié, 29-06-2016 a las 13:58 +0200, david escribió:
> hello all
>
> i have been taking a look to the rtpengine.c code and i found
hello all
i have been taking a look to the rtpengine.c code and i found that the
issue has relation with the queried_nodes_limit which had 50 defalut
value, so before it was reached in the loop, we received a
request/response retransmision doing all the same.
anycase, the issue it's because when
hello all
i have observed an issue using this parameter, which is useful in case
you deactivate a node from the rtpengine sets, to let the calls to
finish the negotiation.
but i have tested that if a node fails down in the middle of a call,
with that option activated, the kamailio gets blocked wai
