Hi Daniel,
The location was always wrong, but it wasn't noticed because it doesn't
cause calls to fail straight away. It's only after a while that encryption
stops working. This can be verified by watching to see if the values in
/proc/rtpengine/0/list change, or do not change which indicates the
Hello,
thanks for sharing, very useful to know.
Was the wrong location of the iptables module a result of ugrading some
packages (like kernel or iptables)? I assume the initial installation
deploys the module in the right location. Asking to see if one needs to
do a re-install of the rtpengine af
Hello all,
We solved this issue with the help of Richard Fuchs. There were two issues:
1. The iptables module was in the wrong location and thus wasn't loaded.
The daemon thought that the kernel was handling packets and took the ROC
updates from it, but didn't actually see any packets and so the
Hello,
We're having an issue with rtpengine (used by Kamailio) where audio works
initially, but then after an apparently random amount of time stop working.
We see that when audio stops working rtpengine logs this:
Dec 10 09:58:57 hostname rtpengine[376]: WARNING: [Pl1SeGDssOsDNWQdvey4lg..
port 4
