Hi alle
I think I have an issue with the dialogue and session timer module with Kamailio 5.4
I sync the Session Expire Timer with the dialogue timeout via a common AVP.
When I check a dialogue via kamcmd dlg.list
start_ts: 1682066352 init_ts: 1682066346 end_ts: 0 timeout: 1682066952 lifetime: 600
Timeout is increased on the first session refreshing re-invite, as expected (in this case after 300 seconds). But it looks like the dialogue just disappears (from kamcmd dlg.list, not from the backing database) when the lifetime ist reached, leaving an orphan database entry.
I would like to digg deeper into this. Is there a way to log more details from the dialogue module like when it triggers dialogue expiry?
Short update while doing more testing, I guess I figured out the cause.
We have two core nodes using the dialog module and:
modparam("dialog", "enable_dmq", 1)
If the call is handled on core1 and the session timer is increased, indeed there is no hint of the dialogue expiring.
But now I had a look on core2 and this is where the call is expiring.
So I guess the refreshing of the session timer via AVP is not DMQ synced to the other node? Should I replace the AVP by a DLG var?
Hi,
You could log something in an event route: https://kamailio.org/docs/modules/devel/modules/dialog.html#idm1691
event_route[dialog:end] { xlog("$dlg(h_id):$dlg(h_entry) / $dlg(callid): Call ended with - state $dlg(state)\n") }
That could give you at least some pointers.
Thanks, Carsten -- Carsten Bock I CTO & Founder
ng-voice GmbH
Trostbrücke 1 I 20457 Hamburg I Germany T +49 179 2021244 I www.ng-voice.com
Registry Office at Local Court Hamburg, HRB 120189 Managing Directors: Dr. David Bachmann, Carsten Bock, Quirin Maderspacher
Am Fr., 21. Apr. 2023 um 10:56 Uhr schrieb Benoît Panizzon < benoit.panizzon@imp.ch>:
Hi alle
I think I have an issue with the dialogue and session timer module with Kamailio 5.4
I sync the Session Expire Timer with the dialogue timeout via a common AVP.
When I check a dialogue via kamcmd dlg.list
start_ts: 1682066352 init_ts: 1682066346 end_ts: 0 timeout: 1682066952 lifetime: 600Timeout is increased on the first session refreshing re-invite, as expected (in this case after 300 seconds). But it looks like the dialogue just disappears (from kamcmd dlg.list, not from the backing database) when the lifetime ist reached, leaving an orphan database entry.
I would like to digg deeper into this. Is there a way to log more details from the dialogue module like when it triggers dialogue expiry?
-- Mit freundlichen Grüssen
-Benoît Panizzon- @ HomeOffice und normal erreichbar
I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________
Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________ __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
-
Benoît Panizzon -
Carsten Bock