> 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 that issue, but the other way round. I started with a short
session timer, intending to extend it on every re-invite according to the timer
values in the sip message and reply. This turned out not to work, as the peer
nodes would not get an update on re-invites and thus fire the timeout and
expiring the dialog from memory, and also sync state 5 (delete) back to the
node handling the dialog causing the next in-dialog sip message hitting a 481
dialog not found.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2080#issuecomment-1825263391
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/2080/1825263...@github.com>
_______________________________________________
Kamailio (SER) - Development Mailing List
To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
