[SR-Users] How to handle BYE in case of serial fork
hw at skalatan.de
Fri Sep 11 12:26:18 CEST 2020
I was not referring to dialog stateful routing e.g. with dialog module. I was referring to the loose_route() function in your kamailio.cfg (e.g. compare to the default cfg in github).
Maybe you can quote the problematic BYE SIP message here.
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
From: sr-users <sr-users-bounces at lists.kamailio.org> On Behalf Of Björn Klasen
Sent: Friday, September 11, 2020 12:19 PM
To: Kamailio (SER) - Users Mailing List <sr-users at lists.kamailio.org>
Subject: Re: [SR-Users] How to handle BYE in case of serial fork
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 not be routet.
Am 11.09.20 um 11:47 schrieb Henning Westerholt:
> Hello Björn,
> if I understood your scenario correct: what about just forwarding the BYE normally? It should be usually routed as in-dialog request without any transaction matching.
> What do you mean with "Kamailio doesn't know anything about it, so it does not reply".
> BTW, you should think about upgrading your Kamailio. 😉
Björn Klasen, Specialist
TNG Stadtnetz GmbH, Network Management (VoIP) Projensdorfer Straße 324
T +49 431/ 530530
F +49 431/ 7097-555
mailto: bklasen at tng.de
Register: Amtsgericht Kiel HRB 6002 KI
Executive board (Geschäftsführung): Dr.-Ing. Volkmar Hausberg, Sven Schade, Carsten Tolkmit, Dr. Sven Willert Tax-Id (Steuernr.): 2029047020, VAT-Id (USt-Id): DE225201428
Kamailio (SER) - Users Mailing List
sr-users at lists.kamailio.org
More information about the sr-users