> From that I would like to use iLBC codec to start a call between users. (iLBC > seems to be the most supported format)
Note that the "LIVE555 Streaming Media" software does not include any codecs (encoding or decoding software). So you would need to supply your own iLBC codec. We do, however, support the RTP Payload Format for iLBC audio (as defined in RFC 3952), using the "SimpleRTPSink" class (for transmission) and the "SimpleRTPSource" class (for reception). > - Can we initiate a rtp/rtcp protocol with an already opened udp socket ? No. However, if you have a port *number*, you can create a "Groupsock" object to use that port number. Its constructor will create the UDP socket for the given port number. Once you have a "Groupsock" object, you can use this to create a "SimpleRTPSink" object (for RTP transmission), or a "SimpleRTPSource" object (for RTP reception). You can also use a separate "Groupsock" object - at each end - to create a "RTCPInstance" object (to implement the RTCP protocol). Note that by convention, RTP uses an even-numbered socket, and RTCP uses the next socket (i.e., an odd-numbered socket). This is not something that's universally enforced, but it's something that you should keep in mind, and try to follow if you can. > - In order to make a voip app, is it necessary to have a rtp server and rtp > client on both devices (client 1 connecting to server 2 / client 2 > connecting to server 1)? You would need both a "SimpleRTPSink" object and a "SimpleRTPSource" object on each device. > - Using live555, seems to me like using a bazooka to kill a fly. Live555 is > so much complete that it seems huge comparing to what I need to do, isn't it ? Yes. Much of the code deals with the RTSP protocol, which is not relevant for your application. Note also that we do not implement SIP, which is the most commonly used control protocol for VoIP. (We do have a rudimentary SIP client implementation, but it falls far short of what you'd need for VoIP.) So, if you're planning to use SIP, you should definitely look elsewhere. Ross Finlayson Live Networks, Inc. http://www.live555.com/
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
