Keep a close eye on the number of file descriptors in use. Have seen cases where the os ran out of descriptors using this tool.
Norm Brett Nemeroff wrote: > I know this isn't really "call recording" but I've used a really cool > tool called "pcapsipdump" that dumps each call, rtp and SIP into it's > own pcap file. > > I made some modifcations so it doesn't log OPTIONS dialogs. If you're > very resourceful, you can make it dump a recording of sorts. And it'd > be pretty passive, if that's desirable. > > -Brett > > > On Sun, Jan 25, 2009 at 5:12 AM, Jimmy Svensson <[email protected] > <mailto:[email protected]>> wrote: > > Hi! > > I'm looking for a pure call recording solution that generates > pcap-files of the data from one specific call. I've been looking > at using the a merged OpenSIPS+rtpproxy solution to achieve this. > The rtpproxy would not be proxying any RTP traffic in this case, > just terminating and recording. Does anyone have experience with > this kind of solution? > > Now I found that rtpproxy seems to be replaced by mediaproxy but I > can't find any call recording features on the mediaproxy. Does > anyone know if there are any plans to implement call recording in > mediaproxy or do I have to go for the rtpproxy? > > Thanks! > /Jimmy > > _______________________________________________ > Users mailing list > [email protected] <mailto:[email protected]> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > ------------------------------------------------------------------------ > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
