Module: kamailio
Branch: master
Commit: a253b84b608e874cba164f1b5f497e67ee3abbf7
URL: 
https://github.com/kamailio/kamailio/commit/a253b84b608e874cba164f1b5f497e67ee3abbf7

Author: Kamailio Dev <[email protected]>
Committer: Kamailio Dev <[email protected]>
Date: 2025-10-23T22:16:10+02:00

modules: readme files regenerated - dialog ... [skip ci]

---

Modified: src/modules/dialog/README

---

Diff:  
https://github.com/kamailio/kamailio/commit/a253b84b608e874cba164f1b5f497e67ee3abbf7.diff
Patch: 
https://github.com/kamailio/kamailio/commit/a253b84b608e874cba164f1b5f497e67ee3abbf7.patch

---

diff --git a/src/modules/dialog/README b/src/modules/dialog/README
index b2a7373bc85..33a831fa360 100644
--- a/src/modules/dialog/README
+++ b/src/modules/dialog/README
@@ -2571,11 +2571,18 @@ kamctl rpc dlg.briefing "ft"
 10.6. $dlg_var(key)
 
    This is a read/write variable that can be used to store custom values
-   assigned with a dialog (e.g. the URI of a billing-server, an assigned
-   emergency-server). This pseudo-variable will be available only for
-   subsequential requests after doing loose_route().
-
-   Note: You will receive "NULL", if there is no dialog for this request.
+   associated to a dialog (e.g. the URI of a billing-server, an assigned
+   emergency-server). The value has to be a string. This pseudo-variable
+   will be available for subsequential requests only after loose_route()
+   or dlg_manage().
+
+   Note: "NULL" is returned, if there is no dialog for this request.
+
+   Note: dialog variables set before the dialog is created for the initial
+   INVITE can be associated to the dialog only when the dialog is created
+   by the same Kamailio process. They are lost if the variables are set in
+   a process that calls an asynchronous function that resumes the
+   processing in another process, which then creates the dialog.
 
 11. Event Routes
 

_______________________________________________
Kamailio - Development Mailing List -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the 
sender!

Reply via email to