Re: [SR-Users] RTPEngine-Recording-daemon
I underestand your meaning. Thank you. On Mon, Jul 9, 2018 at 1:54 PM, Pawel Kuzak wrote: > Hi, > > You can. For every new call a new connection is established using the UNIX > socket. So different connections means different calls. > > Regards, > Paul > > > > Am 09.07.2018 um 10:43 schrieb Mojtaba: >> >> Hello, >> In RTPEngine recording-daemon, I enabled "forward-to" option to >> unix_socket. All things work right, I got metadata at first, then >> media packets (RTP-UDP-IP). >> The metadata for each calls is received just at first packet, but i >> want to know, if i have more than one concurrent active call in >> RTPEngine, How can i distinct which media packet was from which call? >> Thanks with Regards. >> --Mojtaba Esfandiari.S >> >> ___ >> Kamailio (SER) - Users Mailing List >> sr-users@lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > > > ___ > 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
Re: [SR-Users] RTPEngine-Recording-daemon
Hi, You can. For every new call a new connection is established using the UNIX socket. So different connections means different calls. Regards, Paul Am 09.07.2018 um 10:43 schrieb Mojtaba: Hello, In RTPEngine recording-daemon, I enabled "forward-to" option to unix_socket. All things work right, I got metadata at first, then media packets (RTP-UDP-IP). The metadata for each calls is received just at first packet, but i want to know, if i have more than one concurrent active call in RTPEngine, How can i distinct which media packet was from which call? Thanks with Regards. --Mojtaba Esfandiari.S ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] RTPEngine-Recording-daemon
Hello, In RTPEngine recording-daemon, I enabled "forward-to" option to unix_socket. All things work right, I got metadata at first, then media packets (RTP-UDP-IP). The metadata for each calls is received just at first packet, but i want to know, if i have more than one concurrent active call in RTPEngine, How can i distinct which media packet was from which call? Thanks with Regards. --Mojtaba Esfandiari.S ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPEngine Recording does not work
I solved it, it just update kernel module. apt-get install -t jessie-backports linux-image-amd64 Thanks On Sun, Jul 1, 2018 at 2:37 PM, Mojtaba wrote: > What do you mean? > > On Sun, Jul 1, 2018 at 2:27 PM, Domenico Briganti wrote: >> ll >> >> Il 01 lug 2018 11:48 AM, "Mojtaba" ha scritto: >> >> I have strange issue, >> the output of of `uname -r` command is "3.16.0-4-amd64", while all the >> debs file are "4.9.0-0.bpo.6-amd64". >> ngcp-rtpengine_6.4.0.0+0~mr6.4.0.0_all.deb >> ngcp-rtpengine-daemon_6.4.0.0+0~mr6.4.0.0_amd64.deb >> ngcp-rtpengine-iptables_6.4.0.0+0~mr6.4.0.0_amd64.deb >> ngcp-rtpengine-kernel-dkms_6.4.0.0+0~mr6.4.0.0_all.deb >> ngcp-rtpengine-kernel-source_6.4.0.0+0~mr6.4.0.0_all.deb >> ngcp-rtpengine-recording-daemon_6.4.0.0+0~mr6.4.0.0_amd64.deb >> ngcp-rtpengine-utils_6.4.0.0+0~mr6.4.0.0_all.deb >> Is it the reason of my issue? >> >> On Fri, Jun 29, 2018 at 9:57 PM, Aqs Younas wrote: >>> you can check by starting your rtpengine with this parameter "--table=0". >>> If >>> kernal modules is properly installed you will not face any error. >>> >>> Best Regards, >>> >>> Aqs Younas >>> >>> >>> >>> On Fri, 29 Jun 2018 at 03:33, Mojtaba wrote: 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 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)
Re: [SR-Users] RTPEngine Recording does not work
What do you mean? On Sun, Jul 1, 2018 at 2:27 PM, Domenico Briganti wrote: > ll > > Il 01 lug 2018 11:48 AM, "Mojtaba" ha scritto: > > I have strange issue, > the output of of `uname -r` command is "3.16.0-4-amd64", while all the > debs file are "4.9.0-0.bpo.6-amd64". > ngcp-rtpengine_6.4.0.0+0~mr6.4.0.0_all.deb > ngcp-rtpengine-daemon_6.4.0.0+0~mr6.4.0.0_amd64.deb > ngcp-rtpengine-iptables_6.4.0.0+0~mr6.4.0.0_amd64.deb > ngcp-rtpengine-kernel-dkms_6.4.0.0+0~mr6.4.0.0_all.deb > ngcp-rtpengine-kernel-source_6.4.0.0+0~mr6.4.0.0_all.deb > ngcp-rtpengine-recording-daemon_6.4.0.0+0~mr6.4.0.0_amd64.deb > ngcp-rtpengine-utils_6.4.0.0+0~mr6.4.0.0_all.deb > Is it the reason of my issue? > > On Fri, Jun 29, 2018 at 9:57 PM, Aqs Younas wrote: >> you can check by starting your rtpengine with this parameter "--table=0". >> If >> kernal modules is properly installed you will not face any error. >> >> Best Regards, >> >> Aqs Younas >> >> >> >> On Fri, 29 Jun 2018 at 03:33, Mojtaba wrote: >>> >>> 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 >>> 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.]
Re: [SR-Users] RTPEngine Recording does not work
ll Il 01 lug 2018 11:48 AM, "Mojtaba" ha scritto: I have strange issue, the output of of `uname -r` command is "3.16.0-4-amd64", while all the debs file are "4.9.0-0.bpo.6-amd64". ngcp-rtpengine_6.4.0.0+0~mr6.4.0.0_all.deb ngcp-rtpengine-daemon_6.4.0.0+0~mr6.4.0.0_amd64.deb ngcp-rtpengine-iptables_6.4.0.0+0~mr6.4.0.0_amd64.deb ngcp-rtpengine-kernel-dkms_6.4.0.0+0~mr6.4.0.0_all.deb ngcp-rtpengine-kernel-source_6.4.0.0+0~mr6.4.0.0_all.deb ngcp-rtpengine-recording-daemon_6.4.0.0+0~mr6.4.0.0_amd64.deb ngcp-rtpengine-utils_6.4.0.0+0~mr6.4.0.0_all.deb Is it the reason of my issue? On Fri, Jun 29, 2018 at 9:57 PM, Aqs Younas wrote: > you can check by starting your rtpengine with this parameter "--table=0". If > kernal modules is properly installed you will not face any error. > > Best Regards, > > Aqs Younas > > > > On Fri, 29 Jun 2018 at 03:33, Mojtaba wrote: >> >> 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 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.04 sec) >> >> [15
Re: [SR-Users] RTPEngine Recording does not work
I have strange issue, the output of of `uname -r` command is "3.16.0-4-amd64", while all the debs file are "4.9.0-0.bpo.6-amd64". ngcp-rtpengine_6.4.0.0+0~mr6.4.0.0_all.deb ngcp-rtpengine-daemon_6.4.0.0+0~mr6.4.0.0_amd64.deb ngcp-rtpengine-iptables_6.4.0.0+0~mr6.4.0.0_amd64.deb ngcp-rtpengine-kernel-dkms_6.4.0.0+0~mr6.4.0.0_all.deb ngcp-rtpengine-kernel-source_6.4.0.0+0~mr6.4.0.0_all.deb ngcp-rtpengine-recording-daemon_6.4.0.0+0~mr6.4.0.0_amd64.deb ngcp-rtpengine-utils_6.4.0.0+0~mr6.4.0.0_all.deb Is it the reason of my issue? On Fri, Jun 29, 2018 at 9:57 PM, Aqs Younas wrote: > you can check by starting your rtpengine with this parameter "--table=0". If > kernal modules is properly installed you will not face any error. > > Best Regards, > > Aqs Younas > > > > On Fri, 29 Jun 2018 at 03:33, Mojtaba wrote: >> >> 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 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.04 sec) >> >> [1530178537.176906] INFO: >> >> [MWFhMWM4MmVhYjFmYjY3MzV
Re: [SR-Users] RTPEngine Recording does not work
you can check by starting your rtpengine with this parameter "--table=0". If kernal modules is properly installed you will not face any error. Best Regards, Aqs Younas On Fri, 29 Jun 2018 at 03:33, Mojtaba wrote: > 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 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.04 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.84 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.04 sec) >
Re: [SR-Users] RTPEngine Recording does not work
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 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.04 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.84 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.04 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]: >>
Re: [SR-Users] RTPEngine Recording does not work
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.04 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.84 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.04 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? _
[SR-Users] RTPEngine Recording does not work
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.04 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.84 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.04 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? -- --Mojtaba Esfandiari.S ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPEngine recording
On 12/08/17 03:49 PM, Alex Balashov wrote: Also, the "proc" recording method has an interesting pipeline, involving an ephemeral metadata file and a memory sink exposed through /proc, and a userspace daemon picking up the data and writing it to disk (if this doesn't happen, audio frames going into the sink are discarded). This pipeline leads to two or three philosophical questions: 1. Is the purpose of this design to allow for writing audio frames in a scatter-gather fashion, so that audio is written serially to storage? The main idea behind this approach was that it makes it feasible with only minimal overhead to enable recording for all calls and then let the recording daemon decide which calls to actually record and in what way. if the recording daemon is not interested in the call at all, then having recording enabled anyway would only have negligible impact on the overall performance. And if the recording daemon is interested, then it has a variety of options on how to deal with the data: write to pcap, decode to playable audio, send off to external system, etc. It should be noted that the included recording daemon doesn't support all of these options (yet?) and should only be seen as a reference implementation. The interface should be sufficiently simple that other recording solutions can be implemented on top of it. 2. Is the other purpose of a RTP sink to allow the possibility of real-time call intercept and diversion to live playback? If so, are there any plans for the recording daemon to expose an RTSP interface or similar to make this easier? No plans from our side so far, but as I said above, it should be fairly simple to create an implementation for such a mechanism. 3. What happens if, under high load and I/O wait conditions, the userspace recording daemon cannot read frames from the sink fast enough, or the CPU encoding workload (-> WAV/MP3) is too high? You would start to lose network frames (RTP packet data). According to the documentation, the depth of the sink is only 10 frames: Packet data is held in kernel memory until retrieved by the userspace component, but only a limited number of packets (default 10) per media stream. If packets are not retrieved in time, they will be simply discarded. This makes it possible to flag all calls to be recorded and then leave it to the userspace component to decided whether to use the packet data for any purpose or not. Is it possible to increase that depth? Or is this not a concern because the userspace component is implemented in an asynchronous/threaded manner, so frames are retrieved quickly for processing and then enqueued into a local blocking queue? The kernel module supports changing this limit on a per-stream basis when recording is enabled (however, such a switch isn't present in the rtpengine main daemon as of yet), as well as changing the default value of 10 as a module option that can be set when the module is loaded (e.g. through modprobe.d config options). The included recording daemon is multi threaded, but the possibility that it cannot keep up with the work load exists nevertheless. If you simply queue up everything until it can be processed when there isn't enough processing (or I/O) power available, then you would simply run out of memory at some point. Cheers ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPEngine recording
Also, the "proc" recording method has an interesting pipeline, involving an ephemeral metadata file and a memory sink exposed through /proc, and a userspace daemon picking up the data and writing it to disk (if this doesn't happen, audio frames going into the sink are discarded). This pipeline leads to two or three philosophical questions: 1. Is the purpose of this design to allow for writing audio frames in a scatter-gather fashion, so that audio is written serially to storage? Conventional recording solutions suffer from the problem that under high volume, a large number of file handles are written in parallel. This thrashes the disk. In the days of mechanical disks, this would lead to frequent disk burn-out. In the SSD era the situation is slightly improved, but is still very taxing on the SSD, as I understand it, in terms of write wear/write levelling. This usually leads to a solution like writing recordings to a tmpfs area and then serially copying them out of there, one at a time. Would I be correct to assume that this pipeline is designed to address this same problem, but in a different and novel manner? 2. Is the other purpose of a RTP sink to allow the possibility of real-time call intercept and diversion to live playback? If so, are there any plans for the recording daemon to expose an RTSP interface or similar to make this easier? 3. What happens if, under high load and I/O wait conditions, the userspace recording daemon cannot read frames from the sink fast enough, or the CPU encoding workload (-> WAV/MP3) is too high? According to the documentation, the depth of the sink is only 10 frames: Packet data is held in kernel memory until retrieved by the userspace component, but only a limited number of packets (default 10) per media stream. If packets are not retrieved in time, they will be simply discarded. This makes it possible to flag all calls to be recorded and then leave it to the userspace component to decided whether to use the packet data for any purpose or not. Is it possible to increase that depth? Or is this not a concern because the userspace component is implemented in an asynchronous/threaded manner, so frames are retrieved quickly for processing and then enqueued into a local blocking queue? -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPEngine recording
I have succeeded in prototyping a recording setup using the 'proc' method. However, I've got one issue I can't seem to figure out. On inbound calls only, the inbound (caller) leg on the PSTN side seems to show up interleaved/stuttered in the recording, and also slowed down considerably. This does not happen on outbound calls to the same endpoint, only inbound. The anomalies do not manifest when playing back the audio in Wireshark. The anomalies persist regardless of whether WAV or MP3 output is used. RTPEngine & recording-daemon are running on a KVM VM. I haven't tried running on bare metal or other VM technology to reproduce. Build is with ffmpeg libraries from rpmfusion for the reasons discussed here: https://github.com/sipwise/rtpengine/issues/372 -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPEngine recording
On 10/08/17 12:23 PM, Alex Balashov wrote: On Thu, Aug 10, 2017 at 12:22:32PM -0400, Richard Fuchs wrote: There's actually two distinct recording methods implemented. The one you're describing simply outputs pcap files containing the raw packets involved in the call. The other method involves the aforementioned external recording daemon, which is able to output recordings in a variety of formats. Currently supported is audio output in WAV or MP3 files. Video is also not yet supported (but will be in the future). I see. Thank you for that insight. Where is this distinction, and the modalities of the latter option, addressed in the documentation? The relevant config option is called `recording-method`. The recording daemon itself is not documented yet as this is a fairly new feature and there might still be bugs lurking - use at your own risk. Cheers ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPEngine recording
On Thu, Aug 10, 2017 at 12:22:32PM -0400, Richard Fuchs wrote: > There's actually two distinct recording methods implemented. The one you're > describing simply outputs pcap files containing the raw packets involved in > the call. The other method involves the aforementioned external recording > daemon, which is able to output recordings in a variety of formats. > Currently supported is audio output in WAV or MP3 files. Video is also not > yet supported (but will be in the future). I see. Thank you for that insight. Where is this distinction, and the modalities of the latter option, addressed in the documentation? -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPEngine recording
On 10/08/17 11:40 AM, Alberto Llamas wrote: Hi Alex, I had the opportunity to play around with this recording and it works very well. We have it implemented on production by the way. The information about how it works, recording formats you can find in the README here (https://github.com/sipwise/rtpengine). Once you have the recording you need a third-party tool to convert those files to a wav format for instance. It depends on the codec the call is being recorded the convert tool you have to use like ffmpeg. There's actually two distinct recording methods implemented. The one you're describing simply outputs pcap files containing the raw packets involved in the call. The other method involves the aforementioned external recording daemon, which is able to output recordings in a variety of formats. Currently supported is audio output in WAV or MP3 files. Video is also not yet supported (but will be in the future). Cheers ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPEngine recording
On Thu, Aug 10, 2017 at 11:40:28AM -0400, Alberto Llamas wrote: > Once you have the recording you need a third-party tool to convert those > files to a wav format for instance. It depends on the codec the call is > being recorded the convert tool you have to use like ffmpeg. Thank you for your feedback, Alberto. Extracting the audio payload from RTP frames and mixing them together with 'sox' is not an incredibly difficult task. It works for 90% of simple calls. The problem with this approach to call recording is that certain calls have non-straightforward RTP timing scenarios which would lead to unintelligible garbage if simply interleaving the audio frames together. This is what sets the sophisticated call recording systems apart; they are RTP-aware, and emit playable recordings in an RTP-aware way that takes these nuances into account. RTP can get quite complex. -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPEngine recording
Hi Alex, I had the opportunity to play around with this recording and it works very well. We have it implemented on production by the way. The information about how it works, recording formats you can find in the README here (https://github.com/sipwise/rtpengine). Once you have the recording you need a third-party tool to convert those files to a wav format for instance. It depends on the codec the call is being recorded the convert tool you have to use like ffmpeg. Another thing to say is for video calls it does not record the video stream just the audio stream. Regards, On Thu, Aug 10, 2017 at 11:27 AM, Alex Balashov wrote: > I have gathered that RTPEngine has recently, or perhaps some time ago, > evolved a recording feature set: > > https://kamailio.org/docs/modules/5.0.x/modules/ > rtpengine.html#rtpengine.f.start_recording > > Does anyone have any experience using it with Kamailio? How does it > work? Any gotchas or pitfalls? > > It looks like recording is done via a separate daemon specifically for > that purpose. Does it emit directly in a playable format, or more or > less just dump the raw, RTP-encapsulated frames? > > -- > Alex Balashov | Principal | Evariste Systems LLC > > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Alberto Llamas Telecommunications Engineer dCAP | KPAC | SSCA *"Internet is all about share"* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] RTPEngine recording
I have gathered that RTPEngine has recently, or perhaps some time ago, evolved a recording feature set: https://kamailio.org/docs/modules/5.0.x/modules/rtpengine.html#rtpengine.f.start_recording Does anyone have any experience using it with Kamailio? How does it work? Any gotchas or pitfalls? It looks like recording is done via a separate daemon specifically for that purpose. Does it emit directly in a playable format, or more or less just dump the raw, RTP-encapsulated frames? -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users