Re: [Ccrtp-devel] about rtplisten and rtpsend demo,for help

[karl]

Thanks for your help!
You are very great!


> 
> I see the problem. If you change the 3333 port for rtpsend to
> 3332, it will work. This is because rtplisten refuses to listen on an
> odd port and listens to 3332 instead, as specified in the old RTP
> spec.
> 
> This is an interesting issue. In newer revisions of RTP, the
> constraint that the RTP data port must be even has been relaxed. ccRTP
> allows to specify both data and control port, in which case the stack
> will use the two specified ports without modification. However,
> rtplisten does not specify the control port, but I think that a third
> optional parameter should be added for this. 
> 
> I believe older versions of ccRTP did the even/odd check also
> for the destination port, but since it is now possible to use an odd
> port for data packets whenever specified, that check has been
> removed. I think this explains why the same command lines could work
> with older ccRTP releases, with which both rtplisten and rtpsend used
> 3332 for data packets.
> 
> On Fri, Dec 20, 2002 at 05:09:19PM +0800, karl wrote:
> > Thanks for your reply!
> > I used command line as follow:
> > # rtplisten 192.168.0.15 3333
> > # rtpsend "jfkald;jkj" 192.168.0.15 3333 1000 100
> > 
> > In the version 0.9, the rtplisten and rtpsend worked correctly, but now the 
> > rtplisten received nothing.
> > 
>