Hi Stas,
Hard to day :) ...indeed, it is not right, in the same time I see no
easy "fix" here .... But we have have a ticket, to keep track of this.
Worst case we document it :)
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.com
On 29.01.2026 18:09, Stas Kobzar wrote:
Hi Bogdan,
Thank you for your answer.
It seems so. I see in logs that "push_reply_in_dialog" is called after
final reply 503 (see below).
I guess this is a bug, no? Should I create an issue on github?
Regards,
Stas
====================================== dialog module logs
==========================================
INFO:dialog:w_create_dialog: bye on timeout activated
INFO:dialog:build_new_dlg: new dialog 0x7fbda2b9ec88
(c=7f27c7b0-944e-425a-b2a6-4542df5887b1,f=sip:[email protected]
<mailto:sip%[email protected]>,t=sip:[email protected]
<mailto:sip%[email protected]>,ft=gTMFDIbNOylaQcl9) on hash 4044
INFO:dialog:update_leg_info: route_set , contact
sip:[email protected]:36715;transport=udp, cseq 2147483548 and
bind_addr udp:127.0.0.1:5060 <http://127.0.0.1:5060>
INFO:dialog:dlg_update_leg_info: set leg 0 for 0x7fbda2b9ec88:
tag=<gTMFDIbNOylaQcl9> rcseq=<0>
INFO:dialog:link_dlg: ref dlg 0x7fbda2b9ec88 with 3 -> 3 in h_entry
0x7fbda2b7bb20 - 4044
INFO:dialog:dlg_onreq: t hash_index = 23522, t label = 352414250
NOTICE:new branch at sip:[email protected]:5060
<http://sip:[email protected]:5060>
INFO:dialog:dlg_update_contact: Using the same contact
<sip:[email protected]:36715;transport=udp> for dialog 0x7fbda2b9ec88
on leg 0
INFO:dialog:dlg_onreq_out: pushing new leg 1/1
INFO:dialog:pv_get_dlg_status: =============> pv_get_dlg_status:
dlg->state = DLG_STATE_UNCONFIRMED
NOTICE:=====> incoming reply T_reply_code=100, DLG_status=1
INFO:dialog:pv_get_dlg_status: =============> pv_get_dlg_status:
dlg->state = DLG_STATE_UNCONFIRMED
NOTICE:=====> incoming reply T_reply_code=503, DLG_status=1
NOTICE:ACC: call missed:
timestamp=1769700287;created=0;setuptime=1769700287;method=INVITE;from_tag=gTMFDIbNOylaQcl9;to_tag=a3c41695-b5fc-4f28-bf31-1af33b6837b6;call_id=7f27c7b0-944e-425a-b2a6-4542df5887b1;code=503;reason=Failed
foo
INFO:dialog:push_reply_in_dialog: 0x7fbda2b9ec88 totag in rpl 503 is
<a3c41695-b5fc-4f28-bf31-1af33b6837b6> (36)
INFO:dialog:push_reply_in_dialog: new branch with tag
<a3c41695-b5fc-4f28-bf31-1af33b6837b6>, leg_idx=1
INFO:dialog:update_leg_info: route_set , contact , cseq 2147483548 and
bind_addr udp:127.0.0.1:5060 <http://127.0.0.1:5060>
INFO:dialog:dlg_update_leg_info: set leg 1 for 0x7fbda2b9ec88:
tag=<a3c41695-b5fc-4f28-bf31-1af33b6837b6> rcseq=<2147483548>
INFO:dialog:next_state_dlg: ============> next_state_dlg: begin with
state 'DLG_STATE_UNCONFIRMED' on event: 'DLG_EVENT_RPL3xx'
INFO:dialog:next_state_dlg: ============> next_state_dlg: dialog
0x7fbda2b9ec88 changed from state 'DLG_STATE_UNCONFIRMED' to state
'DLG_STATE_DELETED', due event 'DLG_EVENT_RPL3xx'
INFO:dialog:next_state_dlg: dialog 0x7fbda2b9ec88 changed from state 1
to state 5, due event 4
INFO:dialog:dlg_onreply: dialog 0x7fbda2b9ec88 failed (negative reply)
INFO:dialog:pv_get_dlg_status: =============> pv_get_dlg_status:
dlg->state = DLG_STATE_DELETED
NOTICE:=====> incoming reply T_reply_code=180, DLG_status=5
INFO:dialog:next_state_dlg: ============> next_state_dlg: begin with
state 'DLG_STATE_DELETED' on event: 'DLG_EVENT_TDEL'
INFO:dialog:next_state_dlg: ============> next_state_dlg: dialog
0x7fbda2b9ec88 changed from state 'DLG_STATE_DELETED' to state
'DLG_STATE_DELETED', due event 'DLG_EVENT_TDEL'
INFO:dialog:next_state_dlg: dialog 0x7fbda2b9ec88 changed from state 5
to state 5, due event 1
INFO:dialog:_unref_dlg: Destroying dialog 0x7fbda2b9ec88 due to unref
INFO:dialog:destroy_dlg: destroying dialog 0x7fbda2b9ec88
INFO:dialog:destroy_dlg: dlg expired or not in list - dlg
0x7fbda2b9ec88 [4044:2104306243] with clid
'7f27c7b0-944e-425a-b2a6-4542df5887b1' and tags 'gTMFDIbNOylaQcl9'
'a3c41695-b5fc-4f28-bf31-1af33b6837b6'
On Thu, Jan 29, 2026 at 10:56 AM Bogdan-Andrei Iancu
<[email protected]> wrote:
Hi Stas,
I think the reply_route is triggered (by TM module) before running
the TM callbacks used by dialog module to do the status update :(
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.com
On 28.01.2026 22:23, Stas Kobzar wrote:
Hi all,
Variable /$DLG_status/ returns "1" in the response route after
provisional responses are received.
Here is extraction of the logs:
//-------------------------------------------------------------
NOTICE:=====> incoming reply T_reply_code=100, DLG_status=1
NOTICE:=====> incoming reply T_reply_code=180, DLG_status=1
NOTICE:=====> incoming reply T_reply_code=200, DLG_status=2
//-------------------------------------------------------------
Reply route code with log:
//-------------------------------------------------------------
onreply_route[main_reply] {
xlog("=====> incoming reply T_reply_code=$T_reply_code,
DLG_status=$DLG_status\n");
}
//-------------------------------------------------------------
Doc says:
1 - Dialog unconfirmed (created but no reply received at all)
So, I expect to see "DLG_status=2" when first 100 response
received (Dialog in early state).
The script is very simple and generated with "make menuconfig"
(please, see attached)
I have tried with ver 3.4 and 3.6
My question: is it a bug or am I missing some configuration?
Thank you!
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
