Re: [Ccrtp-devel] SymmetricRTPSession

[Glenn MacGregor]

Federico,

Thanks! So say I create an RTPThread class which derives from Thread and
contains one RTPSession object.

Is it correct to assume that in the run method I want to continuaslly call
rtpsession->getData and rtpsession->putData?

This is the only way I can see to implement both a sender and a receiver in one
RTPSession. Or is the preferred way to derive from RTPSession instead? If so
what advantages do I get from that?

 Thanks

  Glenn

Quoting Federico Montesino Pouzols <address@hidden>:

> 
> Hi, see responses inline...
> 
> On Wed, May 10, 2006 at 01:48:45PM -0400, Glenn MacGregor wrote:
> > Hi All,
> > 
> > I am new to ccrtp, trying to implement a softphone. If I want to receive
> data
> > and transmit data (all voice) from my application i assume I need 2
> RTPSessions,
> > correct? 
> 
> Not necessarily. Actually, the usual way is to use just 1 RTPSession
> for both transmission and reception. Each RTPSession has a particular
> space of SSRC identifiers.
> 
> > One to receive and one to transmit, can I do this with one RTPSession?
> > I did see the SymmetricRTPSession but very unsure how to use that?
> > 
> 
> The difference between them is that RTPSession uses different sockets
> for transmission and reception, while SymmetricRTPSession uses the
> same socket for both receiving and transmitting packets (which is
> particularly useful against NATs and friends).
> 
> So with one RTPSession/SymmetricRTPSession you can implement a
> participant that sends and receives voice packets.
> 
> HTH.
> 
> > Can anyone guide me in the correct direction?
> > 
> >  Thanks
> > 
> >   Glenn
> > 
> > Glenn MacGregor
> > HighStreet Networks
> > 
> > -------------------------------------------------
> > This mail sent through IMP: http://horde.org/imp/
> > 
> > 
> > _______________________________________________
> > Ccrtp-devel mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/ccrtp-devel
> 


Glenn MacGregor
HighStreet Networks

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/