ccrtp-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ccrtp-devel] about rtpsend and rtplisten


From: karl
Subject: Re: [Ccrtp-devel] about rtpsend and rtplisten
Date: Mon, 23 Dec 2002 20:26:59 +0800

Yes, you are right. 
Now I update the ccRTP to 1.0pre1 and recompiled demos.
At majority time, it is normal. But sometimes when I send 2 packets,
rtplisten received 1 only and been sending out following information all the 
time, never stop:
I got a SDES chunk from address@hidden:1067
I got an RR RTCP report from address@hidden:1067
....
Besides these in the above,  there is another problem:
When I receive   RTP streaming with rtplisten and store it to a file, the noise 
is very great.


 I want to write a program that  receive a RTP packet , remove it's header ,   
get it's data
 (no matter what format it is) and deposit the data in a file. 
Another program finish opposite function , that is , open a file,
 make it's data into RTP packets, then send out them, no matter what format the 
data in the file are.

Can the ccRTP finish these?  if it can, how should my program write ?
Would you like to write a demo for me?

I download a rtp-1.4.0 from www.vovida.org. 
 it can record and play voice very good. But it convert codes form one format 
to another.
However, I do not need these functions.
Would  you like to tell me a good method?

Thanks for your long-term help.


> 
> Ah, it may be that you have upgraded ccRTP but dit not
> recompile the demos or somehow the demos have been compiled with an
> older library/headers. I think that because I saw the following line
> in the output:
> 
> > > >     Goodby reason:"RTP session being destoryed,GNU ccRTP stack 
> > > > finishing"
>                                                ^^
> 
> and that typo was fixed some weeks ago, more or less at the
> same time that the problem with sequence numbers was fixed :).
> 
> Take into account that ccRTP uses inlines and templates
> extensively, and some dependencies on the library headers may not be
> correctly handled by the makefiles generated with some versions of the
> autotools. In these cases is generally a good idea to clean and
> rebuild everything from scratch.
> 
> On Sun, Dec 22, 2002 at 03:35:14PM +0800, karl wrote:
> > Thanks for your help!
> > But I'm using ccrtp-1.0pre1 now.
> > Would you like to tell me what's the problem?
> > > 
> > > Are you using ccrtp 1.0pre0? There was a subtle bug in the
> > > sequence number verification code in that release that could cause
> > > problems like the one you describe. If so, upgrade to 1.0pre1, which
> > > should deliver packets correctly.
> > > 
> > > On Sat, Dec 21, 2002 at 04:39:12PM +0800, karl wrote:
> > > > Hello,
> > > > I'm sorry for brother you again.
> > > > I do it as you said. But when I send 10 packets, the rtplisten received 
> > > > 8 only and sended informations as follow:
> > > > 
> > > > *New synchronization source:82f5e25
> > > > I got an RR RTCP report from address@hidden :1056
> > > > I got a SDES chunk from address@hidden :1056
> > > > I got an app. data unit with 7 payload octets from 
> > > > I got an app. data unit with 7 payload octets from address@hidden :1056
> > > > I got an app. data unit with 7 payload octets from address@hidden :1056
> > > > I got an app. data unit with 7 payload octets from address@hidden :1056
> > > > I got an app. data unit with 7 payload octets from address@hidden :1056 
> > > > I got an app. data unit with 7 payload octets from address@hidden :1056
> > > > I got an app. data unit with 7 payload octets from address@hidden :1056
> > > > I got an app. data unit with 7 payload octets from address@hidden :1056
> > > > I got an RR RTCP report from address@hidden :1056
> > > > I got a Goodbye packet from address@hidden :1056
> > > >     Goodby reason:"RTP session being destoryed,GNU ccRTP stack 
> > > > finishing"
> > > > 
> > > > Karl
> > > 
> > > > _______________________________________________
> > > > Ccrtp-devel mailing list
> > > > address@hidden
> > > > http://mail.gnu.org/mailman/listinfo/ccrtp-devel
> > > 
> > > 
> 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]