Recording failed; no corresponding WAV file was generated.

[2954456878]

rtpengine version the issue has been seen with

Version: 13.5.1.2-1~bpo12+1

Used distribution and its version

Debian 12

Linux kernel version used

6.1.0-40-amd64

CPU architecture issue was seen on (see uname -m)

x86_64

Expected behaviour you didn't see

No response

Unexpected behaviour you saw

This is my configuration file:
output-format = wav
spool-dir = /var/spool/rtpengine
output-dir = /home/call/recording

One out of every 100 calls will fail to generate a recording file.I've enabled debug logging, and this is the error message related to the recording failure:
2025-11-13T08:58:17.496537+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496543+08:00 rtpengine-recording[1261597]: INFO: [core] New call for recording: 'a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta'
2025-11-13T08:58:17.496580+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496589+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496621+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496660+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496673+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496678+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496686+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496723+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496768+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496789+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496827+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496930+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.497013+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.497228+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.497498+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.497583+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:51.847198+08:00 rtpengine-recording[1261597]: INFO: [C a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta] [S tag-0-media-1-component-2-RTCP-id-3] [core] EOF on stream tag-0-media-1-component-2-RTCP-id-3
2025-11-13T08:58:51.847215+08:00 rtpengine-recording[1261597]: INFO: [C a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta] [S tag-0-media-1-component-1-RTP-id-2] [core] EOF on stream tag-0-media-1-component-1-RTP-id-2
2025-11-13T08:58:51.847232+08:00 rtpengine-recording[1261597]: INFO: [C a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta] [S tag-1-media-1-component-2-RTCP-id-1] [core] EOF on stream tag-1-media-1-component-2-RTCP-id-1
2025-11-13T08:58:51.847268+08:00 rtpengine-recording[1261597]: INFO: [C a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta] [S tag-1-media-1-component-1-RTP-id-0] [core] EOF on stream tag-1-media-1-component-1-RTP-id-0
2025-11-13T08:58:51.847324+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:29] inotify delete(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:51.847328+08:00 rtpengine-recording[1261597]: INFO: [core] Recording for call 'a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta' finished
2025-11-13T08:58:54.144143+08:00 rtpengine-recording[1261597]: DEBUG: [core] [metafile.c:29] freeing metafile info for a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta

Compared to normal logs：
Nov 13 11:27:51 ecs-crs-100 rtpengine-recording[2575716]: INFO: [core] New call for recording: '91d3e2e6-3ae3-123f-8c82-fa163eb0c030-7688a37b28f33fad.meta'
Nov 13 11:27:51 ecs-crs-100 rtpengine-recording[2575716]: INFO: [C 91d3e2e6-3ae3-123f-8c82-fa163eb0c030-7688a37b28f33fad.meta] [S tag-0-media-1-component-1-RTP-id-2] [0x8119a0cc] [core] Opened output media file '/home/call/recording/a14ff43d-ae78-406f-93ec-59509b72149b.wav' for writing
Nov 13 11:28:03 ecs-crs-100 rtpengine-recording[2575716]: INFO: [C 91d3e2e6-3ae3-123f-8c82-fa163eb0c030-7688a37b28f33fad.meta] [S tag-0-media-1-component-2-RTCP-id-3] [core] EOF on stream tag-0-media-1-component-2-RTCP-id-3
Nov 13 11:28:03 ecs-crs-100 rtpengine-recording[2575716]: INFO: [C 91d3e2e6-3ae3-123f-8c82-fa163eb0c030-7688a37b28f33fad.meta] [S tag-0-media-1-component-1-RTP-id-2] [core] EOF on stream tag-0-media-1-component-1-RTP-id-2
Nov 13 11:28:03 ecs-crs-100 rtpengine-recording[2575716]: INFO: [C 91d3e2e6-3ae3-123f-8c82-fa163eb0c030-7688a37b28f33fad.meta] [S tag-1-media-1-component-2-RTCP-id-1] [core] EOF on stream tag-1-media-1-component-2-RTCP-id-1
Nov 13 11:28:03 ecs-crs-100 rtpengine-recording[2575716]: INFO: [C 91d3e2e6-3ae3-123f-8c82-fa163eb0c030-7688a37b28f33fad.meta] [S tag-1-media-1-component-1-RTP-id-0] [core] EOF on stream tag-1-media-1-component-1-RTP-id-0
Nov 13 11:28:03 ecs-crs-100 rtpengine-recording[2575716]: INFO: [core] Recording for call '91d3e2e6-3ae3-123f-8c82-fa163eb0c030-7688a37b28f33fad.meta' finished
Nov 13 11:28:03 ecs-crs-100 rtpengine-recording[2575716]: INFO: [core] Closing output media file '/home/call/recording/a14ff43d-ae78-406f-93ec-59509b72149b.wav'

Steps to reproduce the problem

No response

Additional program output to the terminal or logs illustrating the issue

Anything else?

No response

[rfuchs]

This looks like as if just no RTP was received in that call?

[2954456878]

In fact, once the RTP was received, the conversation between the two parties could be clearly heard in the upstream recording.

[2954456878]

Additionally, is it impossible to generate audio files without RTP? Is it possible to insert a silence stream for data filling?

[2954456878]

This is the latest RTPengine log, showing 10.55.12.2:46706 <> 231.11.16.23:34220, SSRC b92d995a, in 1259 p, 216548 b, indicating that RTP was received：

2025-11-14T14:02:51.747488+08:00 rtpengine[2047700]: INFO: [45aca2fac63616c6caef1cdb2@192.168.0.249]: [core] Final packet stats:
2025-11-14T14:02:51.747503+08:00 rtpengine[2047700]: INFO: [45aca2fac63616c6caef1cdb2@192.168.0.249]: [core] --- Tag '18b45a0d036e1fe6' (label 'caller'), created 0:41 ago for branch ''
2025-11-14T14:02:51.747517+08:00 rtpengine[2047700]: INFO: [45aca2fac63616c6caef1cdb2@192.168.0.249]: [core] --- subscribed to media with monologue tag '0019-035413-f0407b647169b446' (index: 1)
2025-11-14T14:02:51.747529+08:00 rtpengine[2047700]: INFO: [45aca2fac63616c6caef1cdb2@192.168.0.249]: [core] --- subscription for media with monologue tag '0019-035413-f0407b647169b446' (index: 1)
2025-11-14T14:02:51.747555+08:00 rtpengine[2047700]: INFO: [45aca2fac63616c6caef1cdb2@192.168.0.249]: [core] ------ Media #1 (audio over RTP/AVP) using PCMA/8000
2025-11-14T14:02:51.747568+08:00 rtpengine[2047700]: INFO: [45aca2fac63616c6caef1cdb2@192.168.0.249]: [core] --------- Port 10.55.12.2:46706 <> 231.11.16.23:34220, SSRC b92d995a, in 1259 p, 216548 b, 0 e, 14 ts, out 0 p, 0 b, 0 e
2025-11-14T14:02:51.747581+08:00 rtpengine[2047700]: INFO: [45aca2fac63616c6caef1cdb2@192.168.0.249]: [core] --------- Port 10.55.12.2:46707 <> 231.11.16.23:34221 (RTCP), SSRC b92d995a, in 0 p, 0 b, 0 e, 41 ts, out 5 p, 300 b, 0 e
2025-11-14T14:02:51.747595+08:00 rtpengine[2047700]: INFO: [45aca2fac63616c6caef1cdb2@192.168.0.249]: [core] --- Tag '0019-035413-f0407b647169b446' (label 'callee'), created 0:41 ago for branch ''
2025-11-14T14:02:51.747607+08:00 rtpengine[2047700]: INFO: [45aca2fac63616c6caef1cdb2@192.168.0.249]: [core] --- subscribed to media with monologue tag '18b45a0d036e1fe6' (index: 1)
2025-11-14T14:02:51.747622+08:00 rtpengine[2047700]: INFO: [45aca2fac63616c6caef1cdb2@192.168.0.249]: [core] --- subscription for media with monologue tag '18b45a0d036e1fe6' (index: 1)
2025-11-14T14:02:51.747646+08:00 rtpengine[2047700]: INFO: [45aca2fac63616c6caef1cdb2@192.168.0.249]: [core] ------ Media #1 (audio over RTP/AVP) using unknown codec
2025-11-14T14:02:51.747663+08:00 rtpengine[2047700]: INFO: [45aca2fac63616c6caef1cdb2@192.168.0.249]: [core] --------- Port 10.55.12.2:53000 <> 231.131.39.32:55752, SSRC e25df986, in 0 p, 0 b, 0 e, 15 ts, out 1259 p, 216548 b, 0 e
2025-11-14T14:02:51.747680+08:00 rtpengine[2047700]: INFO: [45aca2fac63616c6caef1cdb2@192.168.0.249]: [core] --------- Port 10.55.12.2:53001 <> 231.131.39.32:55753 (RTCP), SSRC e25df986, in 9 p, 540 b, 0 e, 15 ts, out 0 p, 0 b, 0 e
2025-11-14T14:02:51.747873+08:00 rtpengine-recording[2047711]: INFO: [C 45aca2fac63616c6caef1cdb2%40192.168.0.249-40d3482e11637290.meta] [S tag-0-media-1-component-2-RTCP-id-3] [core] EOF on stream tag-0-media-1-component-2-RTCP-id-3
2025-11-14T14:02:51.747900+08:00 rtpengine-recording[2047711]: INFO: [C 45aca2fac63616c6caef1cdb2%40192.168.0.249-40d3482e11637290.meta] [S tag-0-media-1-component-1-RTP-id-2] [core] EOF on stream tag-0-media-1-component-1-RTP-id-2
2025-11-14T14:02:51.747917+08:00 rtpengine-recording[2047711]: INFO: [C 45aca2fac63616c6caef1cdb2%40192.168.0.249-40d3482e11637290.meta] [S tag-1-media-1-component-2-RTCP-id-1] [core] EOF on stream tag-1-media-1-component-2-RTCP-id-1
2025-11-14T14:02:51.747937+08:00 rtpengine-recording[2047711]: INFO: [C 45aca2fac63616c6caef1cdb2%40192.168.0.249-40d3482e11637290.meta] [S tag-1-media-1-component-1-RTP-id-0] [core] EOF on stream tag-1-media-1-component-1-RTP-id-0
2025-11-14T14:02:51.747959+08:00 rtpengine-recording[2047711]: INFO: [core] Recording for call '45aca2fac63616c6caef1cdb2%40192.168.0.249-40d3482e11637290.meta' finished
2025-11-14T14:02:51.748018+08:00 rtpengine[2047700]: INFO: [45aca2fac63616c6caef1cdb2@192.168.0.249]: [control] Replying to 'delete' from 36.133.232.71:15087 (elapsed time 0.000367 sec)

[rfuchs]

Additionally, is it impossible to generate audio files without RTP? Is it possible to insert a silence stream for data filling?

Recording is dictated by the RTP that is received, so without any RTP at all there would not be any output files.

2025-11-14T14:02:51.747663+08:00 rtpengine[2047700]: INFO: [45aca2fac63616c6caef1cdb2@192.168.0.249]: [core] --------- Port 10.55.12.2:53000 <> 231.131.39.32:55752, SSRC e25df986, in 0 p, 0 b, 0 e, 15 ts, out 1259 p, 216548 b, 0 e

This indicates a call with one-way audio. Is this the case for all affected calls?

[2954456878]

Sometimes, one-way calls will generate an audio file, which is 78 bytes in size. However, the actual size of the transmitted data is much larger than this.

[rfuchs]

Sometimes, one-way calls will generate an audio file, which is 78 bytes in size. However, the actual size of the transmitted data is much larger than this.

That would be just the WAV header.

The question was, do all affected calls have one-way audio like the example you've posted?

[2954456878]

Yes, this problem always occurs with one-way audio.

[rfuchs]

Can't really reproduce it even with one-way audio.

Enable debug logging for both daemons and post a full log.