Closed #3138.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3138#event-12318243121
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) - Development Mailing
This PR is stale because it has been open 6 weeks with no activity. Remove
stale label or comment or this will be closed in 2 weeks.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3138#issuecomment-2005640606
You are receiving this because you
Reopened #3138.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3138#event-11694888131
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) - Development
Closed #3138.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3138#event-11694064425
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) - Development Mailing
This PR is stale because it has been open 6 weeks with no activity. Remove
stale label or comment or this will be closed in 2 weeks.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3138#issuecomment-1901652084
You are receiving this because you
Hello. Thank you for your reply. Re-based.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3138#issuecomment-1847951378
You are receiving this because you are subscribed to this thread.
Message ID: ___
@vlitvinov pushed 3 commits.
30f4133c8e39c22cba63466d11391b1cf443ecb6 branch_failure route in case 503 and
dns failover
9364ca5b71b42a528d88fe0ca4c275a3970c49a6 branch_failure route in case 503 and
dns failover
74babe6a41a54b528c697de01d2746b31f65e623 branch_failure route in case 503 and
Thank you for providing the update. Right now there seems to be some conflicts
probably after some refactoring changes that have been done. Could you maybe
re-base your changes and then developers could have another close look.
--
Reply to this email directly or view it on GitHub:
This is the main idea do not execute on_reply route in case 503 and available
failover endpoint. The same behavior as with timeout.
There is no possibility to know did we try all candidates. In our case when we
use the rtpengine we do delete but after that we can have successful reply from
This PR is stale because it has been open 6 weeks with no activity. Remove
stale label or comment or this will be closed in 2 weeks.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3138#issuecomment-1801301659
You are receiving this because you
This got somehow out of sight for pretty long, but looking now at combined diff
it seems that order of code execution changes and can have significant impact.
As I understand, the loop with `t_send_branch()` is now executed before
`onreply_route` handling. If I got it right, that can have
11 matches
Mail list logo
