RTPEngine does not respond to a "delete" after a "play media" with the "block egress" flag

[Norm Brandinger]

When using the "block egress" flag in a "play media" message, the subsequent "delete" message is not responded to.

The logs show that this message is not being emitted:

[core] Deleting call branch ‘888114273’ (via-branch ‘br0’)

I've looked at monologue_delete_iter() as that is where the above log message is being written from. Will be happy to dig deeper to try to get to the bottom of the problem, but need a little direction.

I will be happy to test any possible fixes.

Regards,

Norm

The RTPEngine debug logs show:

[1733926135.056452] INFO: [B2B.113.6861687.1733926131.1858877025]: [control] Received command 'delete' from 100.127.6.111:58829
[1733926135.056490] DEBUG: [B2B.113.6861687.1733926131.1858877025]: [control] Dump for 'delete' from 100.127.6.111:58829: { "call-id": "B2B.113.6861687.1733926131.1858877025", "via-branch": "br0", "received-from": [ "IP4", "0.0.0.0" ], "from-tag": "d469a2e1464e6403b836512408a7eb12-7fe2", "to-tag": "868381717", "command": "delete" }
[1733926135.056539] DEBUG: [B2B.113.6861687.1733926131.1858877025]: [core] 0 packets removed from send queue

A capture of the control port from the sending system shows a "delete" is sent. When no response is received, another "delete" is sent. The second "delete" gets a response indicating that the call (monologue) appears to have been deleted.

#
U 100.127.6.111:35456 -> 100.127.6.106:22222 #19
43_3332_3 d7:call-id35:B2B.113.8197460.1733927984.6465717510:via-branch3:br013:received-froml3:IP47:0.0.0.0e8:from-tag37:a0f4c113d6483795b04428d8830af30d-7fe26:to-tag9:9103690087:command6:deletee
#
U 100.127.6.111:35456 -> 100.127.6.106:22222 #20
43_3332_3 d7:call-id35:B2B.113.8197460.1733927984.6465717510:via-branch3:br013:received-froml3:IP47:0.0.0.0e8:from-tag37:a0f4c113d6483795b04428d8830af30d-7fe26:to-tag9:9103690087:command6:deletee
#
U 100.127.6.106:22222 -> 100.127.6.111:35456 #21
43_3332_3 d7:warning38:Call-ID not found or tags didn't match6:result2:oke
#

The RTPEngine debug logs when not using "block egress" is:

[1733927034.904419] INFO: [B2B.113.38841.1733927030.1703970125]: [control] Received command ‘delete’ from 100.127.6.111:47435  
[1733927034.904444] DEBUG: [B2B.113.38841.1733927030.1703970125]: [control] Dump for ‘delete’ from 100.127.6.111:47435: { “call-id”: “B2B.113.38841.1733927030.1703970125”, “via-branch”: “br0”, “received-from”: [ “IP4”, “0.0.0.0” ], “from-tag”: “1dd6f6689bab4e15d707290814ad2ff0-7fe2”, “to-tag”: “888114273”, “command”: “delete” }  
[1733927034.904533] DEBUG: [B2B.113.38841.1733927030.1703970125]: [core] 0 packets removed from send queue  
[1733927034.904556] INFO: [B2B.113.38841.1733927030.1703970125]: [core] Deleting call branch ‘888114273’ (via-branch ‘br0’)

A control port capture from a similar flow that does not use "block egress" is:

#
U 100.127.6.111:52438 -> 100.127.6.107:22222 #31
46_9842_9 d7:call-id36:B2B.113.625345.1733927856.122192111010:via-branch3:br013:received-froml3:IP47:0.0.0.0e8:from-tag37:16943b22cb1038d4ef459f5f2ef0fcb6-7fe26:to-tag9:9070437647:command6:deletee
#
U 100.127.6.107:22222 -> 100.127.6.111:52438 #32
46_9842_9 d7:createdi1733927857e10:created_usi69221e11:last signali1733927858e17:last redis update ...