Re: Retrieving RTCP receiver info

Federico Montesino Pouzols <[email protected]>
Newsgroups gmane.comp.gnu.ccrtp.devel
Message-ID <20051212134216.GD3961@paraguas>
I guess it right what you are trying to get is the info in RR packets
received at the responders?

On Thu, Dec 01, 2005 at 12:37:07PM +0100, Gianluca Martiniello wrote:
> Hi all,
> 
> I'm using ccRTP support for RTCP to implement a QoS monitoring tool at
> application layer.
> This monitoring tool is a fairly simple application which sequentially
> establishes RTP audio session (using SIP) with preconfigured automatic
> responders.
> During a session my application sends and receives PCMU-coded audio
> samples to the automatic responder with which the session has been
> established. Moreover, thanks to the RTCP support provided by ccRTP :-),
> my application automatically sends and receives RTCP sender/receiver
> reports and using onGotSR and onGotRR I am able to track the reception
> of SR and RR packets. Then, manipulating the information incapsulated
> inside RRs I am able to estimate various QoS parameters (jitter and loss
> for instance) which give me an indication of the QoS that would be
> perceived by the other side if the other side were a human interlocutor
> (actually it is just an automatic responder! ;-) ).
> 
> Now I am wondering if there is a simple way to track the transmission of
> RRs by my application because I am interested in estimating the same QoS
> parameters in order to have an indication of the QoS perceived by my
> application as if it were a human person (actually it is just a simple
> application! :-) ).
> 
> Do you have any idea? I don't know if I have been clear enough in
> exposing my problem, in case I'll try to expose it better with practical
> examples! :-D
> 
> 
> Thanks for help.
> 
> Gianluca
> 
> 
> _______________________________________________
> Ccrtp-devel mailing list
> [email protected]
> http://lists.gnu.org/mailman/listinfo/ccrtp-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.