Logging the total number of fragments that make up a message

--0000000000008939d00622da42d5
Content-Type: text/plain; charset="UTF-8"

Hi all,

Along with the message, it is necessary to register in the access_log the
total number of its parts (it doesn't matter, it's MO or MT), since each
part of such a composite message is charged by the upstream SMSC
operator. I will collect such information in Elasticsearch for subsequent
analysis after the billing period.

How do you solve this problem? If I am not mistaken, MO messages coming
from the SMS service will always have a "[udh:0:]" entry in the log file,
since, apparently, Kannel deletes information in the SMS.udhdata format
after assembling the message.

--
Regards,
Denis

--0000000000008939d00622da42d5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<div><br></div><div>Along with the message, it is n=
ecessary to register in the access_log the total number of its parts (it do=
esn&#39;t matter,=C2=A0it&#39;s MO or MT), since each part of such a compos=
ite message is charged by the upstream SMSC operator.=C2=A0I will collect s=
uch information in Elasticsearch for subsequent analysis after the billing =
period.<br><br>How do you solve this problem? If I am not mistaken, MO mess=
ages coming from the SMS service will always have a &quot;[udh:0:]&quot; en=
try in the log file, since, apparently, Kannel deletes information in the S=
MS.udhdata format after assembling the message.<div><br clear=3D"all"><div>=
<div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_signatur=
e">--<br>Regards,<br>Denis</div></div></div></div></div>

--0000000000008939d00622da42d5--