Hi Federico,
Yes, I tried to rewrite ruri after the http async reply and was able to
send the call to the failover provider as expected. Thank you for your help
:-)
Regards
*Maharaja Azhagiah*
On Wed, Aug 7, 2024 at 10:26 AM Federico Cabiddu
wrote:
> Hi,
> changing version won't "fix',
Hi,
changing version won't "fix', due to kamailio internals you have to
rewrite the ruri after the async reply.
Did you try what I suggested in the previous reply?
Regards,
Federico
On Wed, Aug 7, 2024 at 3:13 PM Maharaja Azhagiah via sr-users <
sr-users@lists.kamailio.org> wrote:
> Hi
>
> I h
Hi,
a http_async_client resume route is internally a failure_route so the
message is the one. of the first branch.
You can try either to change $ru and $rd after the http reply or/and to do
it in a branch_route.
Hope this helps.
Regards,
Federico
On Tue, Aug 6, 2024 at 5:33 PM Maharaja Azhagiah
Additional information. I have even upgraded to the latest kamailio version
5.8.2 with no luck in resolution on this issue.
Regards
*Maharaja Azhagiah*
On Tue, Aug 6, 2024 at 10:11 AM Maharaja Azhagiah
wrote:
> Hi
>
> I have upgraded kamailio to 5.7.6 and I still see the issue when call
>
Hi
I have upgraded kamailio to 5.7.6 and I still see the issue when call
failover to the provider configured carrierfailureroute, RURI changed back
to the first / primary carrier
Call fails due to 488 and rewrites to next carrier
36(194) INFO: {1 32676 INVITE P4GVS5mWnATVHneyX047QAx6Zv0ivpw3}
Hello,
Using http_async_query can change some script behaviour due to some side
effects, I noticed this also e.g. on rtpengine functions.
I did not looked into your cfg in details, but one easy option from your side
would be to try a maintained Kamailio version (e.g. 5.7.x) and see if the
prob
