pcap recording fiilename format

[Sam Machin]

I'm recording audio to pcaps, but the filename has an additional section of random characters.
For example in call-id
313735333334313537353136353533-fzamzg9brud3

The recording is 
313735333334313537353136353533-fzamzg9brud3-e333a4fca153e058.pcap

whats this final e333a4fca153e058 string, it doesn't appear to be the tag or anything I can find in the call?

Is there any way to get this passed back in the response to the start recording or stop recording commands?

[Richard Fuchs]

On 24/07/2025 03.26, Sam Machin wrote:

I'm recording audio to pcaps, but the filename has an additional section of random characters.
For example in call-id
313735333334313537353136353533-fzamzg9brud3

The recording is 
313735333334313537353136353533-fzamzg9brud3-e333a4fca153e058.pcap

whats this final e333a4fca153e058 string, it doesn't appear to be the tag or anything I can find in the call?

This is the "random tag" formed from the '%r' token in the output pattern, see `output-pattern` here: https://rtpengine.readthedocs.io/en/latest/rtpengine-recording.html#options

Cheers

[Sam Machin]

Thanks,

I'm just using rtpengine not the rtpengine-recording to do this as I'm happy with the pcap format, but I don't seem to be able to set output-patter in rtpengine.conf to have any effect?

[Richard Fuchs]

On 25/07/2025 02.44, Sam Machin wrote:
> I'm just using rtpengine not the rtpengine-recording to do this as I'm
> happy with the pcap format, but I don't seem to be able to set
> output-patter in rtpengine.conf to have any effect?

Ah, I missed the part about this being pcap recording. For pcap
recording we don't have a setting like that and the filename pattern is
currently fixed to include the random tag. Also it's not reported back
in the response to the command.

Patches and pull requests welcome.

Cheers