Hello Joel,

these two topics (dialog expiration and send BYE) are handled individually.

Two proxies with this cfg:

modparam("dialog", "db_mode", 0)
modparam("dialog", "db_update_period", 10)
modparam("dialog", "enable_dmq", 1)
modparam("dialog", "default_timeout", 60);
modparam("dialog", "send_bye", 1)

• proxy1 restarted after call established - it will get the dialog data from proxy2, with a different timeout value set internally:

root@proxy-1:/etc/kamailio# kamcmd dlg.list |egrep "_ts|timeout"
start_ts: 1570005344
init_ts: 1570005344
end_ts: 0
timeout: 1570005404
root@proxy-1:/etc/kamailio# /etc/init.d/kamailio restart
[ ok ] Restarting kamailio (via systemctl): kamailio.service.
root@proxy-1:/etc/kamailio# kamcmd dlg.list |egrep "_ts|timeout"
start_ts: 1570005344
init_ts: 1570005344
end_ts: 0
timeout: 1570005415

• but call will be expired on time (from proxy2):

10:35:44.137 pjsua_app.c .....Call 1 state changed to CONFIRMED
root@proxy-1:/etc/kamailio# date
Wed Oct 2 10:36:46 CEST 2019
root@proxy-1:/etc/kamailio# kamcmd dlg.list |egrep "_ts|timeout"
root@proxy-1:/etc/kamailio#

• if proxy2 is stopped after proxy1 was restarted, call will be expired later (from proxy1):

10:43:09.950 pjsua_app.c .....Call 2 state changed to CONFIRMED
root@proxy-1:/etc/kamailio# date; kamcmd dlg.list |egrep "_ts|timeout"
Wed Oct 2 10:44:12 CEST 2019
start_ts: 1570005789
init_ts: 1570005789
end_ts: 0
timeout: 1570005860
root@proxy-1:/etc/kamailio# date; kamcmd dlg.list |egrep "_ts|timeout"
Wed Oct 2 10:44:30 CEST 2019

• proxy2 will not send a timeout for a dialog that does not belong to him

• proxy1 (after a restart) will not send a BYE at timeout, this might be related to the socket:

root@proxy-1:/etc/kamailio# date; kamcmd dlg.list | grep socket
Wed Oct 2 10:54:49 CEST 2019
socket: udp:116.203.XXX.XX:5060
socket: udp:116.203.XXX.XX:5060
root@proxy-1:/etc/kamailio# /etc/init.d/kamailio restart
[ ok ] Restarting kamailio (via systemctl): kamailio.service.
root@proxy-1:/etc/kamailio# date; kamcmd dlg.list | grep socket
Wed Oct 2 10:54:56 CEST 2019
socket:
socket:

There should be a new issue created for the last topic.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.