Hello,
as you probably are aware of, the presence_dialoginfo module just enables the specific
dialog package support. Actually, sending out dialog-info needs support from other
modules.
You’ll will have more freedom in constructing the PUBLISH and subsequently the NOTIFY by
using pua_rpc or pua_json, maybe this might be interesting for your use case (which I did
not fully understood from the description below).
Cheers,
Henning
From: Stefan Mititelu via sr-users <sr-users(a)lists.kamailio.org>
Sent: Sunday, June 16, 2024 9:12 AM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Cc: Stefan Mititelu <stefan.mititelu(a)govoip.ro>
Subject: [SR-Users] Psresence dialoginfo question
Hello,
I am doing BLF but I want different users to be able to setup different dialog info
initial states. My question is if there's an already implemented way for doing that?
I've looked over docs and C code so far and this is what I've found:
1. modparam("presence_dialoginfo", "force_dummy_dialog", 1) => will
force sending initial NOTIFY with dialog state "terminated"
2. Function calls: dlginfo_agg_nbody()->dlginfo_agg_nbody_empty() which will build the
pre-defined xml body with that "terminated" state. If not implemented so far,
maybe this can be used to set a different initial state for a user (e.g. export a cfg
function or take that info from DB?) Any opinions on this?
Thank you,
Stefan