Thanks!
I figured it out. It came to how we were implementing integration with
FusionPBX. We have a process that syncs the FusionPBX domains to the Kamailio
domains module. By default, one of the domains in FusionPBX is the default
domain, which has the IP address of the physical server. So
Hello,
My mistake, sngrep did not display SIP/TLS OPTIONS because siptrace was not
configured to catch local messages...
чт, 29 сент. 2022 г. в 20:26, Henning Westerholt :
> Hello,
>
>
>
> this sounds strange. There is no TLS specific code in the dialog module.
>
> As a workaround, you could u
Hello,
you should rung with debug=3 and see if you spot anything in the logs
that could provide hints about what happens.
Cheers,
Daniel
On 29.09.22 15:18, Denys Pozniak wrote:
> Hello!
>
> In order to keep the SIP/TCP connection alive for some specific
> clients (more precisely, specific firewa
Hello!
I also met a similar case and I had to manually handle this behavior.
It is likely that the loose_route() function has determined that you have a
strict routing scenario.
But then, in theory, RURI should have its own domain, which is not visible
in your trace.
чт, 29 сент. 2022 г. в 14:40
I would check ksr_request_route() first if it contains any blocking
operations like http_client or long database queries before sending a
response to the sender
пт, 30 сент. 2022 г. в 08:37, Muhammad Danish Moosa :
> Hi,
>
> With Kamailio 5.5.3 (with KEMI/Lua) I noticed it apparently had stopped
