Re: Logging the total number of fragments that make up a message

Hi Alexander!

How exactly can this be done? It's not very clear to me. As far as I
understand, the MO concatenated messages are logged as one long
message only after receiving all parts and stitching them together,
there's no flag in the access-log-format that shows the total number
of parts. Maybe I wrong and missing something.

--
Regards,
Denis

On Wed, Oct 9, 2024 at 10:50=E2=80=AFAM Alexander Malysh <[email protected]=
g> wrote:
>
> Hi,
>
> you can use custom access log format and log parts amount. After that jus=
t parse the log line and put into Elastic.
>
> Regards, Alexander Malysh
> Am 24. Sept. 2024, 11:38 +0200 schrieb =D0=94=D0=B5=D0=BD=D0=B8=D1=81 =D0=
=94=D0=B0=D0=B2=D1=8B=D0=B4=D0=BE=D0=B2 <[email protected]>:
>
> 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 p=
art of such a composite message is charged by the upstream SMSC operator. I=
 will collect such information in Elasticsearch for subsequent analysis aft=
er the billing period.
>
> How do you solve this problem? If I am not mistaken, MO messages coming f=
rom the SMS service will always have a "[udh:0:]" entry in the log file, si=
nce, apparently, Kannel deletes information in the SMS.udhdata format after=
 assembling the message.
>
> --
> Regards,
> Denis