recording fails due to Duplicate entry 'X' for key 'call'

[Juha Heinanen]

When trying to record calls to database, I get Duplicate entry for key 'call' errors:

Oct 25 17:41:07 siika /usr/bin/sip-proxy[79497]: INFO: ===== rtpengine_offer(ICE=default replace-session-connection replace-origin generate-RTCP rtcp-mux-demux trust-address record-call=on)
Oct 25 17:41:09 siika /usr/bin/sip-proxy[79482]: INFO: ===== rtpengine_answer(ICE=default replace-session-connection replace-origin trust-address)
Oct 25 17:41:09 siika rtpengine-recording[1947]: ERR: [C dbb5820f0b34e00b-fb0f804c02db879c.meta] [S tag-1-media-1-component-1-RTP-id-0] [0x6cc07bd8] [core] Failed to bind or execute prepared statement: Duplicate entry '4' for key 'call'
Oct 25 17:41:09 siika rtpengine-recording[1947]: ERR: [C dbb5820f0b34e00b-fb0f804c02db879c.meta] [S tag-0-media-1-component-1-RTP-id-2] [0xf2ed8a78] [core] Failed to bind or execute prepared statement: Duplicate entry '4' for key 'call'

Recording files are OK in /var/lib/rtpengine-recording directory.  There is also entry in rtpengine MySql recording_streams table that matches the key in the error message, but its stream column value is NULL.

rtpengine-recording.conf does not have anything different from the example.

Version of rtpengine is 10.5.1.4+0~mr10.5.1.4 and it is running on Debian 11.

Any ideas why the errors and NULL stream column value?  Some time ago (don't remember exactly when) call recording worked fine with the same configuration.

[Richard Fuchs]

What does your DB schema look like?

Cheers

[Juha Heinanen]

That is exactly what I started to check after sending the message.  Looks like my table keys do not match with what is in https://github.com/sipwise/rtpengine/blob/master/recording-daemon/db.c comment.  I'll investigate and will report back.

[Juha Heinanen]

I dropped all three rtpengine tables and re-created them based on the comment in recording-daemon/db.c file.  After that the error messages disappeared, but stream column values are still NULL in recording_streams table.

[Richard Fuchs]

On 25/10/2022 11.26, [EXT] 'Juha Heinanen' via rtpengine wrote:
> I dropped all three rtpengine tables and re-created them based on the
> comment in recording-daemon/db.c file.  After that the error messages
> disappeared, but stream column values are still NULL in
> recording_streams table.
>

The `stream` is populated only when the file storage is set to DB (or
"both") in the config. I assume you have that set?

[Juha Heinanen]

'Richard Fuchs' via rtpengine writes:

> The `stream` is populated only when the file storage is set to DB (or
> "both") in the config. I assume you have that set?

I had the commented out entry

### where to store recordings: file (default), db, both
# output-storage = db

and had assumed (wrongly) that that was the default.

When I removed #, recording to db worked fine.

Thanks for help.