On 1/5/2011 6:25 AM, Alexandre Abreu wrote: > I wonder if these statistics is clear to anyone.. Right now, the only way to > know is looking at the source code and I think you are right. “C” stands for > RTCP. > The lack of understandable RTP information is the only thing that keeps me > still using the mediaproxy 2.X. I really have several reasons to switch to > the RTPProxy. The media-relay component in MP2 lists the sessions and > attributes in a way that we can easily understand and parse [1 example]. > > The RTP Proxy Protocol is indeed a very powerful tool, but IMHO the today's > RTP Session Information really needs some improvements -- mainly to make > the information clearer. > > [1 example] > 1...@sipproxy (source) 02233334...@sipproxy (destination) PBX (source > user-agent) Sippy (destination user-agent) 33'42" (duration) G729 (codec > being used) Áudio (media type) 5.82M (in) 5.83M (out)
Alexandre, Flavio, Yes, indeed, current statistics reporting is not very informative. If you guys can work list of things that the RTPproxy should be reporting instead, we can look into implementing that and making specification available on the rtpproxy.org. Thanks! Regards, -- Maksym Sobolyev Sippy Software, Inc. Internet Telephony (VoIP) Experts T/F: +1-646-651-1110 Web: http://www.sippysoft.com MSN: sa...@sippysoft.com Skype: SippySoft _______________________________________________ Users mailing list Users@rtpproxy.org http://lists.rtpproxy.org/mailman/listinfo/users
