Iñaki Baz Castillo wrote:
> Hi, I'm using start_recording() function of nathelper module. I use
> "-R" option in rtpproxy daemon in order not to record RTCP.
> start_recording() is called in route and onreply_route.
>
> After the call ends I see the following files in the recording directory:
>
> 283K 2009-07-06 13:41
> [email protected]=38a3b929-co1782-ins001;1.a.rtp
> 275K 2009-07-06 13:41
> [email protected]=38a3b929-co1782-ins001;1.o.rtp
> 0 2009-07-06 13:41
> [email protected]=38a3b929-co1782-ins001;2.a.rtp
> 0 2009-07-06 13:41
> [email protected]=38a3b929-co1782-ins001;2.o.rtp
>
> Some questions:
>
> - "1.a.rtp" is one direction and "1.o.rtp" the other, right?
Yes, that's right. Those are streams in two different directions. If my
memory serves, ".a.rtp" is stream from caller, while ".o.rtp" is stream
from callee. By the way, you might want to check PCAP recording instead
of recording in custom format ("-P" option). It's little less compact
but allows using third-party tools to analyze and decode streams.
> - What are the last two files? In this case they are 0 length, but in
> longer calls the are some bytes length.
Those should be files for the second stream in media session (video?).
If you don't have video enabled then something is wrong, it would help
if you can send SDP of the offer and SDP of the corresponding answer.
> PS: Is there any way to start the recording when 200 OK arrives (so
> early media is not recorded)?
> I cannot imagine how to do it since "start_recording()" must be called
> in the INVITE request (and also in the response).
Yes, you are correct. The current nathelper API doesn't allow this to be
done. What we can do in this regard, is to implement some flag for
start_recording() to request recording of stream going in different
direction, so that you can do two subsequent calls in the 200 OK
handler, one with that flag and one without. Should be trivial thing to
do - just swap out to/from tags before passing them to the RTPproxy. I
will take a look in the next few days if nobody beats me on that.
Regards,
--
Maksym Sobolyev
Sippy Software, Inc.
Internet Telephony (VoIP) Experts
T/F: +1-646-651-1110
Web: http://www.sippysoft.com
MSN: [email protected]
Skype: SippySoft
_______________________________________________
Devel mailing list
[email protected]
http://lists.rtpproxy.org/mailman/listinfo/devel
