Ping to remove stale label
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3656#issuecomment-2122055212
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) -
Hmm, would modparam("dialog", "dlg_filter_mode", 1) fix the issue by not arming
the timer?
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3656#issuecomment-2042863292
You are receiving this because you are subscribed to this thread.
Message ID:
keep alive
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3656#issuecomment-1983264261
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) - Development Mai
Unfortunately not as I'm working with an older version.
But the fix also was for the problem I found with my work-around.
A fix for the original issue that the node not in charge of a dialog might
delete it, is not solved by this fix.
So the issue that a timer is armed on a 'slave' node still is p
Just a short warning to anyone considering using my work-around. I experienced
dialog data corruption which could be due to this or maybe the duplicate key. I
reverted this change to my config.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/365
I guess I stumbled over some other issue or bug...
`[1 dialog 0f57b21a4ca92561-1371066@x.x.x.x 10 KDMQ]jansson
[jansson_funcs.c:47]: janssonmod_get_helper(): json error at line 1, col 3154:
duplicate object key near '"tag1"'`
Indeed, when looking at the JSON structure sent with dialog action 1,
> But still I can see scenarios where the current behaviour can cause problems.
> Imagine a small dialog timeout combined with SIP Session Timer keep-alive
> re-INVITEs. The proxy 1 would not expire the dialog, but proxy2 (which did
> not got the re-INVITE) would expire it.
I also came across
Situation: Two Kamailio nodes syncing dialog profiles via DMQ
Observation: When a dialog timeout is encountered, about half of the time, the
timeout is triggered on the peer node not handling the dialog preventing the
call to be correctly terminated and also leaving entries in the dialog databas
Closed #3655 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3655#event-11049140451
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) - Devel
Somehow hit enter at wrong time.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3655#issuecomment-1824639111
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (
### Description
### Troubleshooting
Reproduction
Debugging Data
```
(paste your debugging data here)
```
Log Messages
```
(paste your log messages here)
```
SIP Traffic
```
(paste your sip traffic here)
```
### Possible Solutions
### Additional Informatio
11 matches
Mail list logo
