RTPengine PCAP Capture – Only One Direction Recorded

[Ilyass Rhejjou]

I am currently using RTPengine with Kamailio as a media proxy between a private and a public network. The architecture includes two interfaces on RTPengine and Kamailio: one internal and one external.

Everything is working well in terms of call setup and audio — both endpoints can hear each other correctly. However, I’m experiencing an issue with the PCAP files generated by RTPengine using the --recording-dir feature.

Problem:

The PCAP files only contain RTP packets in one direction:

• From the private endpoint to RTPengine

• From the public endpoint to RTPengine

But they do not contain the RTP packets sent from RTPengine to either endpoint (egress direction). This results in one-way traces, which makes analysis incomplete.

What I’ve Tried:

• Verified that the RTP flows are working bidirectionally during the call.

• RTPengine is configured correctly with both internal and external interfaces.

• I am not using tcpdump — the captures are generated directly by RTPengine.

• I suspect the issue may be related to the default behavior of RTPengine capturing only inbound RTP packets.

Thank you for your support.

[Richard Fuchs]

There's a setting, `record-egress`, to capture egress packets in the pcap.

But: capturing is always done either ingress or egress, never both. This is by design.

You can patch the code if you want to do both. Pull request welcome.

Cheers

--
You received this message because you are subscribed to the Google Groups "Sipwise rtpengine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtpengine+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/rtpengine/d2f6cea8-fd70-4794-b771-c665e7da0d5bn%40googlegroups.com.