17 Dec
2024
17 Dec
'24
3:37 a.m.
Hi, if we don't send a t_relay and don't use the failure_route we get
the behaviour shown in the image. The 302 gets ACKed, but there is no
CANCEL.
Cancel_b_method isn't set.
Thank you very much
Christian
Am 16.12.24 um 15:41 schrieb Alex Balashov via sr-users:
Hi,
On this point:
--
Christian Berger - berger(a)sipgate.de
Telefon: +49 (0)211-63 55 55-0
Telefax: +49 (0)211-63 55 55-22
sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf
HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois
Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391
www.sipgate.de - www.sipgate.co.uk
On Dec 16, 2024, at 8:38 am, Christian Berger via
sr-users <sr-users(a)lists.kamailio.org> wrote:
BTW, could there have been a change in the default behavior of Kamailio? We think it used
to "just work" in the past.
You may wish to consider the literature here:
https://kamailio.org/docs/modules/5.8.x/modules/tm.html#idm403
t_reply() will cause Kamailio to generate a novel, endogenous 302. If you want to pass
back the one received from upstream, you'll have to actually pass the received 302
back.
To trigger default reply-passing behaviour, just exit from the failure_route. As for
CANCEL'ing the other branches, the parameter above should help with that.
-- Alex
