@mekya, @burak-58 ,
In the LTE camera settings, setting the Frame Rate (FPS) to 20 and GOP (100ms) to 20 provides the expected results. Also ts file size was not same. Any other Frame Rate and GOP values lead to incorrect duration and program date time in the .m3u8 file.

Hi @oleul05
Could you please do a test with ffmpeg like that:

• Run this command to convert RTMP ingest to HLS:
  ffmpeg -listen 1 -i rtmp://IP_ADDRESS:1935/live -c copy -hls_flags program_date_time -f hls output.m3u8

• Then stream your camera to:
  rtmp://IP_ADDRESS:1935/live

Then check HLS files.

I've encountered the same problem and it causes the server to return wrong internal when asking m3u8 with start and end query parameters. I mean it causes that issue #6308

This issue may be the same with that one mentioned above

Hello @oleul05,

How long into the streaming do you encounter this issue? Is it reproducible after a few minutes?

Have you tested the problematic camera with non-integer GOP and frame rate values, such as 36/30? What were the GOP and FPS settings when you experienced the problem?

When using integer GOP FPS ratio, like GOP: 30 FPS: 30 or GOP: 60 FPS: 30, do you still encounter this issue?

We suspect that a non-integer GOP/ FPS ratio might be causing this problem. I am attempting to reproduce the issue with ffmpeg but haven't had success so far.

@lastpeony We get this issue immediately after starting the stream.
When using the GOP FPS ration 20/20 in this case it was working fine. On the all other ration like 30/20 we got unexpected results.

We conducted a test with @oleul05 using different GOP and FPS combinations.

We were able to reproduce the issue on version 2.8, but could not replicate it on version 2.11.3.

If you're experiencing this problem, please upgrade to version 2.11.3 (the latest as of today).

I am closing this because didn't get response from @oleul05 and any further report with this scenario.