Re: [Kamailio-Users] Dialog profile persistence - DB vs. memory.

Jerome, Jerome Martin wrote: That does, indeed, clarify. Thank you. I assumed that a "profile" is just an abstraction around certain properties of the dialog built into its hash information, but was suspecting that there may be more meta-data involved. But as you rightly observe, that does complicate my use case. In this case, if I fail over while a call is in progress and then the BYE for it arrives, while it may calculate $DLG_duration usefully for example, the proxy will not recognise it as belonging to an existing dialog and refuse to forward it or any other in-dialog messages. So, it seems that while "this allows to perform dialog-matching for subsequent requests," this is true in one type of use case but - critically and very importantly - not in another. Since is_in_profile() is the only way to check if a request belongs to a known dialog, authorisation is thus tied to profiles rather than mere awareness of certain dialogs. This is unfortunate. All I want to do is check if subsequent in-dialog requests belong to a known dialog; I care not whether this is done by dipping into "profiles" or simply asking the dialog module, "Do you know about this dialog?"