BYE message, Call-Id and Can't find dialog for dialog id

When we sent to drachtio uas.destroy() we got this:

2023-06-22 14:07:52.548733 Client::read_handler read: 3ee16114-a3ad-43b1-b84d-23830f933dc0|sip||0gQAAC8WAAACBAAALxYAAE2AKiy93/JrQA1cxE56CxuSm+RLgY1dxWsyG+79i31FQ4TpJpVicy1+eARvtiy4FA--@x.x.200.142;from-tag=x.x.200.142+3+1c9076ab+6f056701
BYE sip:placeholder SIP/2.0
Content-Length: 0

and after that we getting error:

2023-06-22 14:07:52.548825 Client::processMessage - got request with 4 tokens
2023-06-22 14:07:52.548902 Client::processMessage - request id 3ee16114-a3ad-43b1-b84d-23830f933dc0, request type: sip transaction id: , dialog id: 0gQAAC8WAAACBAAALxYAAE2AKiy93/JrQA1cxE56CxuSm+RLgY1dxWsyG+79i31FQ4TpJpVicy1+eARvtiy4FA--@x.x.200.142;from-tag=x.x.200.142+3+1c9076ab+6f056701
2023-06-22 14:07:52.548958 Client::processMessage - sending a request inside a dialog (dialogId provided)
2023-06-22 14:07:52.549036 ClientController::addAppTransaction: transactionId de4aee8b-5237-441b-909e-d5c0506b32b3; size: 1
2023-06-22 14:07:52.549098 ClientController::addApiRequest: clientMsgId 3ee16114-a3ad-43b1-b84d-23830f933dc0; size: 1
2023-06-22 14:07:52.549225 ClientController::removeNetTransaction: transactionId 4d53a1ab-7f60-48a3-abda-56c5db60c399; size: 0
2023-06-22 14:07:52.549324 SipDialogController::doSendRequestInsideDialog dialog id: 0gQAAC8WAAACBAAALxYAAE2AKiy93/JrQA1cxE56CxuSm+RLgY1dxWsyG+79i31FQ4TpJpVicy1+eARvtiy4FA--@x.x.200.142;from-tag=x.x.200.142+
2023-06-22 14:07:52.549387 Can't find dialog for dialog id 0gQAAC8WAAACBAAALxYAAE2AKiy93/JrQA1cxE56CxuSm+RLgY1dxWsyG+79i31FQ4TpJpVicy1+eARvtiy4FA--@x.x.200.142;from-tag=x.x.200.142+

We think drachtio have a problem with parsing Dialogid and they cutting a From-Tag and it makes it impossible to find the right one.

Attaching full log for this communication.

drachtio.log

drachtio / drachtio-server

BYE message, Call-Id and Can't find dialog for dialog id #292