Using dlg_manage() on my ACK caused the dialog state to be updated to 4, and my dialogs are no longer timing out early!

The timeout column in my SQL database now contains the correct unix epoch as well, is it intended to be much less than the start_time when the dialog state is 3? I guess it isn't really used if the ACK has not arrived.

I am not using record-route headers; I think I had some trouble with the PBX preferring them over the contact header which resulted in lost packets. I will look at them again in the next stage of development, now that everything is working well enough as is.

My architecture relies heavily on an identifier in the URIs and contacts, this identifier is used to forward SIP to registered contacts associated with many PBXs contained behind NAT on physical hosts.
It just so happens that for in-dialog SIP like ACK/PRACK/UPDATE/BYE there are no headers which contain this identifier when sent from the user's device. So for those I have to resort to using the contact stored in the dialog variables.

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