RTP Engine error

14 views
Skip to first unread message

Chris Strickland

unread,
Oct 22, 2025, 2:19:35 PM (11 days ago) Oct 22
to Sipwise rtpengine
I am seeing the error "Failed to open recording metadata file" in the rtpengine logs for some calls.  This is causing an error on the client side "Response not sent due to unknown transaction", and RTP stream not being established.  Is anyone familiar with this error and know what causes it/how to resolve it? I am attaching rtp engine log snippet containing the lifetime of the call.  Call ID is c249e5c782b732b52...@100.113.240.99
rtpenginesys_callsnippet.log

Richard Fuchs

unread,
Oct 23, 2025, 3:31:46 AM (10 days ago) Oct 23
to rtpe...@googlegroups.com
On 22/10/2025 14.19, Chris Strickland wrote:
> I am seeing the error "Failed to open recording metadata file" in the
> rtpengine logs for some calls.  This is causing an error on the client
> side "Response not sent due to unknown transaction", and RTP stream
> not being established.  Is anyone familiar with this error and know
> what causes it/how to resolve it? I am attaching rtp engine log
> snippet containing the lifetime of the call.

I'm guessing you don't have a /tmp/recording/ directory? If you're
running under the standard systemd unit, then the process would likely
have its own private /tmp/ and so a previously created /tmp/recording/
by yourself won't be visible to it.

Cheers

Chris Strickland

unread,
Oct 23, 2025, 10:28:14 AM (10 days ago) Oct 23
to Sipwise rtpengine
Yep, that was the issue.  Can't believe I did not check that first thing.  Sorry to waste your time 
Reply all
Reply to author
Forward
0 new messages