Thank you. I installed RTPEngine from git
(https://github.com/sipwise/rtpengine).
Let me know how can i  be sure kernel module is loaded? and how can i load it?
Thanks

On Thu, Jun 28, 2018 at 6:20 PM, Richard Fuchs <rfuchs@sipwise.com> wrote:
> Looks like you haven't set up the kernel module properly. For the "proc"
> method of recording to work, the kernel module must be loaded and in use.
>
> Cheers
>
>
> On 2018-06-28 05:47, Mojtaba wrote:
>>
>> Hi all,
>> I installed RTPEngine (Version: 6.4.0.0+0~mr6.4.0.0
>> git-master-4eb80da) in my VM machine (Debian GNU/Linux 8 (jessie), i
>> also installed kamailio 5.1.
>>
>> In kamailio routes, i have:
>> route {
>>          ...
>>          #rtpengine_manage("record-call")
>>          rtpengine_manage();
>>          start_recording();
>>          ...
>> }
>> Here is all other configuration files:
>>
>> In /etc/default/ngcp-rtpengine-daemon file:
>> RUN_RTPENGINE=yes
>> CONFIG_FILE=/etc/rtpengine/rtpengine.conf
>> CONFIG_SECTION=rtpengine
>> PIDFILE=/var/run/ngcp-rtpengine-daemon.pid
>> MANAGE_IPTABLES=yes
>> TABLE=0
>>
>> In /etc/default/ngcp-rtpengine-recording-daemon file:
>> RUN_RTPENGINE_RECORDING=yes
>> CONFIG_FILE=/etc/rtpengine/rtpengine-recording.conf
>> CONFIG_SECTION=rtpengine-recording
>> PIDFILE=/var/run/ngcp-rtpengine-recording-daemon.pid
>> MUST_NFS=no
>> NFS_HOST=192.168.1.1
>> NFS_REMOTE_PATH=/var/recordings
>> NFS_LOCAL_MOUNT=/var/lib/rtpengine-recording # must match output-dir if
>> used
>> NFS_OPTIONS=hard,intr,tcp
>>
>> In /etc/rtpengine/rtpengine.conf file:
>> [rtpengine]
>> table = 0
>> interface = 192.168.122.200
>> listen-ng = 127.0.0.1:2223
>> recording-dir = /var/spool/rtpengine/
>> recording-method = proc
>>
>> In
>> [rtpengine-recording]
>> table = 0
>> # output-storage = db (use default)
>> # output-format = mp3 (use default)
>> # output-mixed = 1
>> spool-dir = /var/spool/rtpengine/metadata
>> output-dir = /var/spool/rtpengine/recording
>>
>> But the recording is not work, I have these issues in syslog:
>> [1530178531.860171] INFO:
>> [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Received command
>> 'start recording' from 127.0.0.1:38654
>> [1530178531.860191] NOTICE:
>> [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Turning on call
>> recording.
>> [1530178531.860239] WARNING:
>> [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Call recording through
>> /proc interface requested, but kernel table not open
>> [1530178531.860262] ERR:
>> [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Failed to open
>> recording metadata file '(null)' for writing: Bad address
>> [1530178531.860269] ERR:
>> [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Failed to open
>> recording metadata file '(null)' for writing: Bad address
>> [1530178531.860275] ERR:
>> [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Failed to open
>> recording metadata file '(null)' for writing: Bad address
>> [1530178531.860281] ERR:
>> [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Failed to open
>> recording metadata file '(null)' for writing: Bad address
>> [1530178531.860287] ERR:
>> [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Failed to open
>> recording metadata file '(null)' for writing: Bad address
>> [1530178531.860292] ERR:
>> [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Failed to open
>> recording metadata file '(null)' for writing: Bad address
>> [1530178531.860303] INFO:
>> [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Replying to 'start
>> recording' from 127.0.0.1:38654 (elapsed time 0.000112 sec)
>> [1530178531.969040] INFO:
>> [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Received command
>> 'start recording' from 127.0.0.1:39374
>> [1530178531.969069] INFO:
>> [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Replying to 'start
>> recording' from 127.0.0.1:39374 (elapsed time 0.000004 sec)
>> [1530178537.176906] INFO:
>> [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Received command
>> 'delete' from 127.0.0.1:40258
>> [1530178537.177003] INFO:
>> [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Scheduling deletion of
>> call branch '9052b05a' (via-branch '') in 30 seconds
>> [1530178537.177026] INFO:
>> [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Replying to 'delete'
>> from 127.0.0.1:40258 (elapsed time 0.000084 sec)
>> [1530178537.178368] INFO:
>> [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Received command
>> 'start recording' from 127.0.0.1:40258
>> [1530178537.178392] INFO:
>> [MWFhMWM4MmVhYjFmYjY3MzVlZDlmZWMyYjNmNGVhNmY.]: Replying to 'start
>> recording' from 127.0.0.1:40258 (elapsed time 0.000004 sec)
>> ^C[1530178543.752740] INFO: Version 6.4.0.0+0~mr6.4.0.0
>> git-master-4eb80da shutting down
>>
>> Also when i start RTPEngine, I have  FATAL error about module
>> xt_RTPENGINEer in syslog:
>> Jun 28 05:44:58 debian8 systemd[1]: Starting NGCP RTP/media Proxy
>> Daemon...
>> Jun 28 05:44:58 debian8 ngcp-rtpengine-iptables-setup[10203]:
>> modprobe: FATAL: Module xt_RTPENGINE not found.
>> Jun 28 05:44:58 debian8 ngcp-rtpengine-iptables-setup[10203]:
>> iptables: No chain/target/match by that name.
>> Jun 28 05:44:58 debian8 ngcp-rtpengine-iptables-setup[10203]:
>> ip6tables: No chain/target/match by that name.
>> Jun 28 05:44:58 debian8 systemd[1]: Started NGCP RTP/media Proxy Daemon.
>> Jun 28 05:44:58 debian8 rtpengine[10219]: [1530179098.989322] INFO:
>> Generating new DTLS certificate
>> Jun 28 05:44:59 debian8 rtpengine[10219]: [1530179099.033499] ERR:
>> FAILED TO CREATE KERNEL TABLE 0 (No such file or directory), KERNEL
>> FORWARDING DISABLED
>> J
>>
>> Let me know what is the problem and how can i solve it?
>>
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users



--
--Mojtaba Esfandiari.S

_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users