Re: Question Regarding Flags Behavior in Dialog Callback

Hello,

it might just be implemented for the pua module to do the propagation; I have not checked the code.

Are you sure that you are using the same type of flags? There are e.g. also dialog flags, which are different than the standard script flags you are using.

Cheers,

Henning

> -----Original Message-----
> From: Serdar GUCLUER via sr-users <[email protected]>
> Sent: Donnerstag, 7. August 2025 15:11
> To: [email protected]
> Cc: [email protected]
> Subject: [SR-Users] Question Regarding Flags Behavior in Dialog Callback
> 
> Hi all,
> 
> I'm using the pua_dialoginfo module to publish peer state changes to target
> servers. I was hoping to control which states are published by using the
> disable_caller_publish_flag and disable_callee_publish_flag parameters.
> To debug this, I added some logs in pua_dialoginfo.c, and it seems that the
> flags information coming from the dialog callback does not reflect the updated
> flag settings from the script configuration.
> 
> Here is a simplified scenario from my configuration:
> 
> route[WITHINDLG] {
>     if (has_totag()) {
>         if (loose_route()) {
>             if(!isdsturiset()) handle_ruri_alias();
>             if (is_method("REFER")) {
>                 sl_send_reply("403", "Not allowed");
>                 exit;
>             }
>             if (is_method("ACK")) route(NATMANAGE);
>             if (is_method("BYE|ACK")) {
>                 xlog("L_WARN", "[$ci] - WITHINDLG worked for $rm -> script flag : $sF
> --- branch flags : $bF --- Transaction flags : $mF \r\n");
>                 setflag(PDLGINFO_CALLEE);
>                 xlog("L_WARN", "[$ci] - WITHINDLG worked for $rm -> script flag : $sF
> --- branch flags : $bF --- Transaction flags : $mF \r\n");
>             }
>             route(RELAY);
>         } else {
>             if (is_method("SUBSCRIBE") && uri == myself) exit;
>             if (is_method("ACK")) {
>                 if (t_check_trans()) t_relay();
>                 else exit;
>             }
>             sl_send_reply("404","Not here");
>         }
>         exit;
>     }
> }
> 
> DEBUG: pua_dialoginfo [pua_dialoginfo.c:461]: __dialog_sendpublish():
> confirmed - from_uri: sip:[email protected]
> DEBUG: pua_dialoginfo [pua_dialoginfo.c:462]: __dialog_sendpublish():
> confirmed - to_uri: sip:yyy@mydomain
> DEBUG: pua_dialoginfo [pua_dialoginfo.c:463]: __dialog_sendpublish():
> confirmed - callid: 43005250998501278412250319c7836b
> DEBUG: pua_dialoginfo [pua_dialoginfo.c:464]: __dialog_sendpublish():
> confirmed - from_tag: xk3431808229
> DEBUG: pua_dialoginfo [pua_dialoginfo.c:465]: __dialog_sendpublish():
> confirmed - req_uri: sip:yyy@mydomain
> DEBUG: pua_dialoginfo [pua_dialoginfo.c:466]: __dialog_sendpublish():
> confirmed - from_contact: sip:[email protected]:1111
> DEBUG: pua_dialoginfo [pua_dialoginfo.c:467]: __dialog_sendpublish():
> confirmed - uuid: padi-68946f96-3beb95-1
> DEBUG: pua_dialoginfo [pua_dialoginfo.c:469]: __dialog_sendpublish():
> confirmed - lifetime: 3600
> DEBUG: pua_dialoginfo [pua_dialoginfo.c:470]: __dialog_sendpublish():
> confirmed - disable_caller_publish: 0
> DEBUG: pua_dialoginfo [pua_dialoginfo.c:471]: __dialog_sendpublish():
> confirmed - disable_callee_publish: 0
> DEBUG: pua_dialoginfo [pua_dialoginfo.c:477]: __dialog_sendpublish():
> confirmed - pubruris_caller: sip:xxx@mydomain
> DEBUG: pua_dialoginfo [pua_dialoginfo.c:483]: __dialog_sendpublish():
> confirmed - pubruris_callee: sip:yyy@mydomain
> DEBUG: pua_dialoginfo [pua_dialoginfo.c:487]: __dialog_sendpublish():
> confirmed - checking caller publish conditions...
> DEBUG: pua_dialoginfo [pua_dialoginfo.c:488]: __dialog_sendpublish():
> confirmed - dlginfo->disable_caller_publish: 0
> DEBUG: pua_dialoginfo [pua_dialoginfo.c:489]: __dialog_sendpublish():
> confirmed - disable_caller_publish_flag: 8
> DEBUG: pua_dialoginfo [pua_dialoginfo.c:490]: __dialog_sendpublish():
> confirmed - request is NOT NULL
> DEBUG: pua_dialoginfo [pua_dialoginfo.c:492]: __dialog_sendpublish():
> confirmed - request->flags: 0x20
> DEBUG: pua_dialoginfo [pua_dialoginfo.c:494]: __dialog_sendpublish():
> confirmed - bit checked: (1 << 8) = 0x100, result = NOT SET
> WARNING: <script>: [43005250998501278412250319c7836b] - WITHINDLG
> worked for ACK -> script flag : 00000000 --- branch flags : 00000040 ---
> Transaction flags : 00000020
> WARNING: <script>: [43005250998501278412250319c7836b] - WITHINDLG
> worked for ACK -> script flag : 00000000 --- branch flags : 00000040 ---
> Transaction flags : 00000220
> 
> My question is:
> Is there a mistake in how I’m using or setting the flags? Or, if not, how can I
> ensure that the updated flag values are correctly propagated to the dialog
> callback events?
> 
> Any insights would be greatly appreciated.
> Thanks in advance!
> Serdar
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions -- sr-
> [email protected] To unsubscribe send an email to sr-users-
> [email protected]
> Important: keep the mailing list in the recipients, do not reply only to the
> sender!
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- [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!