hello Daniel
patch seems to be working ok, at least for the test i was making to
duplicate the issue, works OK!
best regards
david
On 13/11/18 13:06, David Escartín wrote:
Hello
sorry for the delay
Yes Daniel we see the incorrect value using $T_rpl($rb) on the
failure_route.
Alex we
Hello
sorry for the delay
Yes Daniel we see the incorrect value using $T_rpl($rb) on the
failure_route.
Alex we actually see the issue when using the same PID for processing
all the responses of the different branches.
Let me test the patch and i will let you know Daniel
best regards
Hello,
for clarification, it is actually the $T_rpl($rb) not giving the
expected value, right? Not the pure $rb...
If yes, then can you try with the patch from the next commit:
*
https://github.com/kamailio/kamailio/commit/e2ca5516ae086cf33c61dbb9e653a5484cca2074
When all ok, I will
Ah, wait. I missed the fact that this only fails to work with multiple PIDs.
You don't have your branch failover mode overridden, do you?
--
Sent from mobile. Apologies for brevity and errors.
-Original Message-
From: Alex Balashov
To: "David Escartín" , "Kamailio (SER) - Users
Hi,
Unlike onreply_routes, failure_routes do not directly correspond to a
discrete SIP reply, because a SIP reply is only one of the things that
can cause a failure_route to trigger. Other possibilities include a
branch timeout, and possibly some other errors of an internal nature.
In other
Hello all
we are seeing what we think is quite strange behaviour
We have expecienced this on 5.0 and 5.1 version.
this is the call flow
INV-->
<-- 302 (SDP)
INV-->
<-- 503 (SDP) (or another 302)
When we receive a 302 and we load contacts and create a new branch, when
we receive the second
