Hello List,
I am looking for a way to record the audio and video of a call. I am using Kamailio (latest) on Ubuntu.
Does anyone know if there's any existing modules that allow for recording or any other solution that can provide recording of calls on Kamailio?
Thank you!
You can use the rtpproxy module along with the rtpproxy server: http://kamailio.org/docs/modules/stable/modules/rtpproxy.html#id2529838 http://www.rtpproxy.org/
Regards, Ovidiu Sas
Unfortunately, I've had no luck with the rtpproxy module.
I have rtpproxy server running and support is enabled for it (verified by logs), however it doesn't seem to record any sessions.
This is my rtpproxy running:
/usr/sbin/rtpproxy -s udp:127.0.0.1 7722 -p /var/run/rtpproxy/rtpproxy.pid -R -a -P -r /tmp/rtppath -S /tmp/rtpspool
According to the docs:
"*-a* Record all sessions going through the RTPproxy unconditionally. By default the RTPproxy requires call control software (i.e. SER, OpenSER or B2BUA) to enable recording explicitly on per-session basis by sending appropriate record command."
Any ideas?
On Mon, Jun 4, 2012 at 2:07 PM, Ovidiu Sas osas@voipembedded.com wrote:
Hello,
what is the rtpproxy version? Have you run it in debug mode as well?
Cheers, Daniel
On 6/5/12 6:46 AM, Saul Waizer wrote:
Hello Daniel & List,
This is the relevant information:
rtpproxy -v Basic version: 20040107 Extension 20050322: Support for multiple RTP streams and MOH Extension 20060704: Support for extra parameter in the V command Extension 20071116: Support for RTP re-packetization Extension 20071218: Support for forking (copying) RTP stream Extension 20080403: Support for RTP statistics querying Extension 20081102: Support for setting codecs in the update/lookup command Extension 20081224: Support for session timeout notifications
/etc/default/rtpproxy config:
CONTROL_SOCK="udp:127.0.0.1:7722" EXTRA_OPTS=" -d DBUG:LOG_LOCAL5 -R -a -P -r /tmp/rtppath -S /tmp/rtpspool -u kamailio -l 127.0.0.1"
I am running Kamailio and rtpprox on ec2
I do have a DBUG log for it, one interesting thing to point out: On the above line notice how I have 127.0.0.1, I changed this from my external ip address because i was getting the following on the rtpproxy log:
Jun 5 15:42:55 ip-10-x-x-x rtpproxy[6526]: INFO:handle_command: new session NmJlNDNhOTA0YmYwZTZhYTEyMTQ4ZDIxY2IxNzQzYmM., tag 2c249068;1 requested, type strong Jun 5 15:42:55 ip-10-x-x-x rtpproxy[6526]: ERR:create_twinlistener: can't bind to the IPv4 port 59794: Cannot assign requested address Jun 5 15:42:55 ip-10-x-x-x rtpproxy[6526]: ERR:handle_command: can't create listener Jun 5 15:42:55 ip-10-x-x-x rtpproxy[6526]: DBUG:doreply: sending reply "6545_8 E10#012" Jun 5 15:43:01 ip-10-x-x-x rtpproxy[6526]: DBUG:handle_command: received command "6556_12 Lc0,8,101 NmJlNDNhOTA0YmYwZTZhYTEyMTQ4ZDIxY2IxNzQzYmM. some.ip 56536 2c249068;1 c51afb04;1" Jun 5 15:43:01 ip-10-x-x-x rtpproxy[6526]: INFO:handle_command: lookup request failed: session NmJlNDNhOTA0YmYwZTZhYTEyMTQ4ZDIxY2IxNzQzYmM., tags 2c249068;1/c51afb04;1 not found
This is expected because rtpproxy cant assign a port to the ec2 external ip instance, however I see that rtpproxy IS in fact trying to record but I just end up with a bunch of empty .rtp files.
Any suggestions are greatly appreciated.
On Tue, Jun 5, 2012 at 3:28 AM, Daniel-Constantin Mierla miconda@gmail.comwrote:
Anyone?
I've been also looking at http://www.voipmonitor.org/ which seems to be recording something, at least the .pcap files are a lot larger in size but no luck trying to extract sound with sox.
The end goal is to be able to record SIP calls (Audio and Video) for later review. Has anyone done this successfully with Kamailio?
Thank You
On Tue, Jun 5, 2012 at 2:21 PM, Saul Waizer saulwaizer@gmail.com wrote:
Hi,
On 06/05/2012 08:21 PM, Saul Waizer wrote:
Well, when starting rtpproxy, you need to tell it the address where it's listening for rtp packets to relay (and record), and rtpproxy uses this address as a response to kamailio, which in turn puts this information into the SDP of the SIP messages and forwards it to the end devices.
If you put 127.0.0.1 there, then your end devices will end up sending their RTP traffic to 127.0.0.1. Also, if you put the private IP of EC2 there (just to make rtpproxy happy and allow it to bind to this address), it won't lead you to anywhere because that address is not reachable from the end-devices. There is a patch floating around for rtpproxy which allows you to set the advertised address (your public ip mapped to your EC2 instance), which then will work with EC2.
In general, choosing EC2 for your SIP deployment is not a good idea if you aren't 100% fit with kamailio, rtpproxy and SIP in general, because EC2's NAT environment is quite tricky to handle in a SIP environment.
Andreas
-
Andreas Granig -
Daniel-Constantin Mierla -
Ovidiu Sas -
Saul Waizer