Hi Alex,
answer inline below
Am 02.09.19 um 10:04 schrieb Alex Balashov:
>> just looked briefly into the code. There is only one place in the
>> dialog module that ends a dialog with "dlg_bye_all" - and this happens
>> in the dlg_ontimeout routine, if there is the proper flag set for the
>>
On Mon, Sep 02, 2019 at 04:04:59AM -0400, Alex Balashov wrote:
> On Sun, Sep 01, 2019 at 09:35:43AM +, Henning Westerholt wrote:
>
> > just looked briefly into the code. There is only one place in the
> > dialog module that ends a dialog with "dlg_bye_all" - and this happens
> > in the
Hi Henning,
On Sun, Sep 01, 2019 at 09:35:43AM +, Henning Westerholt wrote:
> just looked briefly into the code. There is only one place in the
> dialog module that ends a dialog with "dlg_bye_all" - and this happens
> in the dlg_ontimeout routine, if there is the proper flag set for the
>
Hello Alex,
just looked briefly into the code. There is only one place in the dialog module
that ends a dialog with "dlg_bye_all" - and this happens in the dlg_ontimeout
routine, if there is the proper flag set for the particular dialog.
Do you have the send_bye parameter set to 1 or use the
Hi Henning,
I am in fact using timeout_avp, but it's set to 2 hours (7200 sec).
However, to follow up on this, I have made the discovery that the caller
adulterates my RR cookie parameter value to something other than the
value my Kamailio instance injected. It's truncated.
This leads
Hi Alex,
sounds strange indeed. 4.3.5 is from March 2016, a lot happened since then..
One idea to investigate further - have you tried already to get more
debugging information from dialog? With debugger module you could
restrict it to dialog, if this is a loaded production instance.
Another
