Hi Henning,
i think I've got a solution for this. I just make a check
is_known_dialog. If not i reply with 481
I'm just testing, but it seem to work. The carrier is not sending
retransmission of the BYE and the call seems to be stable.
By the way, the carrier is Telekom so discussions about
,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
-Original Message-
From: sr-users On Behalf Of Björn Klasen
Sent: Friday, September 11, 2020 2:12 PM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] How to handle BYE in case
Hi Hennning,
loose_route() is what we are using.
But we use also dialog module for call counting etc.
We did not really change the default config.
This is the snippet in our config.
if (has_totag()) {
# sequential requests within a dialog should
# take
Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
-Original Message-
From: sr-users On Behalf Of Björn Klasen
Sent: Friday, September 11, 2020 12:19 PM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] How to handle BYE in case of serial fork
Hi Henning
Hi Henning,
the question is, where to route the BYE, because the first fork is
terminated. It's a call-forward not reachable (CFNR) scenario.
So your proposal is to route the BYE to callee B after it got already a
CANCEL?
The BYE is routet in-dialog. But if the Dialog is not known it could
rg
Subject: [SR-Users] How to handle BYE in case of serial fork
Hi
we are using Kamailio 4.3.7 and I have a question concerning BYE handling.
We have the following situation:
A carrier a call to us. We are forwarding the call to the destination, but it
does not pick up the call. We have call-forw
Hi
we are using Kamailio 4.3.7 and I have a question concerning BYE handling.
We have the following situation:
A carrier a call to us. We are forwarding the call to the destination,
but it does not pick up the call. We have call-forward active with use
of tm module, so we forward the call to
